linux install...the saga continues

[quote]You’ve probably forgotten by now, but I’m here mainly for a single specific reason: Microsoft has not yet released a version of Windows that works (…with a USB network card).
[/quote]
I did forget (if I ever knew)… but that’s odd, since I know of people that use USB network ‘cards’ on Windows. I’m sure you posted the problems somewhere… but I can’t be bothered to look now.

In any case I didn’t recommend Windows as the alternative :slight_smile:

[quote]Finally, there has always been a practical reason for me to use linux where feasible: I often encounter linux systems in my day-job (and even in my free time - e.g. setting up and running websites) and need to be skilled and experienced in getting them to work.
[/quote]
Perhaps given your success so far, this is an indication that you should find a day-job which requires a different skill set :slight_smile:
I don’t mean to poke fun at you… I feel bad for anyone whose job requires them to get Linux to work.

Given that you want a Linux distro that works well with Java and networking… I might suggest what has been mentioned above - The Java Desktop System from Sun. I only briefly looked at version 1 with a demo disk from Sun, so I can only write one of those one-line reviews you mention above… “It worked for me when I booted from the demo CD and looked like it might be worth exploring further.”

I don’t have to do it, it just saves time if I can.

For stuff like running JGF, then yes I do have to since there’s no budget to pay for someone else to do it :).

Until it gets widely adopted by ISP’s, customers, build farms, etc or I have the budget to co-lo my personal servers I’m still going to have to use other ones :(.

Ditto solaris - although I’m still waiting for my free solaris CD set :slight_smile:

Actually, a coffee now in hand, come to think of it this is part of why I post here: I’m not a professional sysadmin, so my experiences are much more relevant to other non-sysadmins who nevertheless want to (or need to) admin linux systems - e.g. if you get yourself a dedicated or virtual server to run your java gameserver on :).

I’m giving people a flavour of what happens when a linux power-user (just sufficiently ahead of linux newbies that I can probably deduce the causes of problems I encounter if not always fix them) tries to use these things - and who is prepared and capable of doing about the same amount of stuff that a normal user can. e.g. I’m not capable of porting some C++ and manually fixing a bug in the source code. But I am capable of following instructions and doing some limited amount of common-sense error correction on broken / out of date instructions :).

Yeah… I get where you are at. But it seems to get you worked up based on the number of asterisks in your posts :slight_smile:

Me, I try Linux once and a while… I have SuSe installed on my Windows box and occasionally boot into it just for kicks. But I can’t use it on a daily basis - it’s too much work to make things work if you know what I mean.

I do read you rants hoping that some day there will be a Linux that “just works” and you will have found it for me :slight_smile:

[quote]No. Impossible. Debian installer writer made a broken 2.4.x kernel. The “dies after 2 minutes” problem applies to the installer’s kernel (if you tell it to use 2.4)
[/quote]
Update: seems the 2-minute crash MIGHT be due to debian probing PCMCIA - although there are no cards and it sholdn’t be probing minutes after boot! AND I’d not told it to enable PCMCIA. So maybe not…but otherwise, that fits the pattern. Apparently Dell laptops crash when a certain range is probed, and Debian-stable (despite being named “stable”) was a little too aggressive in probing, whereas the supposedly less stable “testing” version of debian is more intelligent and doesn’t dare so much.

Update 2: Debian “testing” has quite a few installer bugs which I’ve been accidentally discovering and making workarounds for. The biggest is that it is even more arrogant about network cards - the installer STOPS if you don’t give it a network card: installation without a network card is not allowed!

However…there is a small chance I might have found a workaround to all these debian problems. This whole thread could turn out to be worthwhile, if I’m able to turn around in an hour or so and give you all a pearl of Debian wisdom :). But don’t get your hopes too high :wink: - I’ve thought I had a workaround 5 or 6 times and each time had my hopes shattered :(.

[quote] All the BSD references I could find (mini tutorials, advocacy, etc) only talked about doing software installation via make - if you could point me to a page talking about a more modern tool I’d be grateful. Obviously, I’m not going to spend 12+ hours installing xBSD just to run one command you cited just to find out what it does! :slight_smile:
[/quote]
Well, the Handbook has both packages (binary files) and ports (source files) in the same section. I’ll grant you that not quite all the information is in the handbook (for example ‘pkg_add -r’ does an auto-FTP fetch), but most of the missing info is in the MAN pages.

The post-install sysinstall stuff is described here. You’re probably most interested in section 2.9.14 Install Packages. This presents you with a curses-like GUI interface for selecting binary packages. They can come from a public FTP site, CDROM, or your own internal network.

[quote]Think more about what I’m saying, dude! In linux, you have GUI’s to do this stuff…
[/quote]
And how many of those GUI’s are broken? How many leave you with a non-functioning system? How many take longer than just typing a single command at the CLI prompt? How many are REALLY worth the effort at the end of the day?

[quote]What does this wonderful CLI do, play musical tones every time you type a key? ;D AFAICS it’s a CLI, i.e. it’s an outdated and grossly unusable (in HCI terms) interface suited only for basic and simple work - and there’s not much difference between one and another, once you’ve got basics like history and tab auto-complete working.
[/quote]
Just because something is old, doesn’t mean that it should be thrown away. The CLI is still so useful, that I often open terminal windows on my Mac. My Mac has a GUI for EVERYTHING. Yet it sometimes takes less time and effort to just type something.

I don’t know where you got the idea that CLIs are highly unusable. There are still companies who’s users use Unix or Mainframe CLIs and absolutely refuse to give it up because it’s so efficient. As for whether it’s less intuitive, that’s debatable. Back when I first started using computers, people found CLIs to be highly intuitive. It wasn’t until an entire generation grew up with nothing but GUIs that people started saying that GUIs are better for everything. It’s all about what you’re used to.

[quote]No, you’re missing the point. The nv linux drivers keep changing because THE OLD ONES DON’T FRICKING WORK! Yes, that’s right, nVidia has historically provided very buggy crappy drivers which have slowly (recently) been coming up to an “acceptable” standard.
[/quote]
Do you know if anything is broken in the FreeBSD drivers? If so, can you point it out and say that it’s a show stopper? While I’ve been busy for the last several months, I’m pretty sure that NVidia drivers got most of their bugs worked out a year or two ago.

[quote]I’ve not even run BSD yet I’ve already encountered numerous references by BSD users to the incidence of this not working - including in nVidia’s own BSD driver release notes!
[/quote]
??? You’re not referring to this text, are you?

“Known Issues: the Linux OpenGL library, when run in linux compatibility mode on FreeBSD, may have difficulties determining if the application is multithreaded. As the resulting warning suggestions, it may help to set the environment variable __GL_SINGLE_THREADED (eg: setenv __GL_SINGLE_THREADED 1). Please see the FAQ entry “Why can the Linux compatibility libraries not correctly determine if they are used in a multithreaded application?” for details and a better solution.”

That’s not a list of applications that don’t work. It’s just a known issue that is rare and easily worked around.

[quote]We seem to be moving back to the problem of *nix users slagging me off because *nix has always worked fine for them, despite the fact that it manifestly does NOT work for many other people. I’m fed up of the whole “works for me, therefore everyone else is wrong” attitude so please lets not go there.
[/quote]
I’m not really trying to project that. I’ve used just about every OS in existence at this point, and I know what works and what doesn’t. To date, FreeBSD has been the best choice on the x86 for users who don’t want to use Windows. This has been reinforced countless times by other users who have switched. You asked for the best solution, I gave it.

BTW, if you really want to go the Debian route, you might look at Knoppix. You can take two routes with it:

  1. Carry the CD and a USB key to every machine you use. This is actually a decent option and works quite well. The only issue is that you can never change the configuration.

  2. Take the Knoppix CD to the machine you wish to use, and install Knoppix on the disk. This will provide you with a no hassle, complete and updated Debian installation. Installation instructions are on the Knoppix website.

If you really like option 1, but wish you could customize it, you can always go the Morphix route.

[quote]Because I don’t have days to spare! I cannot think of non-vulgar words describe to you how much of problem this debian install has been for me, quite how much damage it has done. Suffice it to say that I’m in severe danger of violating as many as 3 contractually obligated deadlines because of this ****.
[/quote]
Well, I can’t help you there. Tight deadlines are usually not the best time to be trying out new OSes. :-/

That would be OK, except it looks like it could easily be just as bad as RH’s linuxconf: only partially effective, and frequently having to delegate to “manually edit the conf file”.

IMHO, Debian is on the right track here, with customization and configuration GUI built-in to the packages themselves. Just like the underlying principle behind OOP: the packages know best how to configure themselves!

Debian’s approach just isn’t mature enough - they haven’t taken it anywhere near to it’s logical perfect extremes. And it’s hard to re-access the GUIs post-install, until you become a debian expert :(.

That is a fair question. However, most CLI’s have the same number of problems IME - mainly consisting of unhandled errors and implicit unhandled assumptions/assertions in the (usually script-driven) CLI.

Usability is not only about time taken to click/type/press. Even if it were, then GUI’s would STILL be best, since it’s been proven that it’s generally faster to initiate actions with a mouse than with keyboard given appropriately(sensible)-sized GUI buttons (if you had a resizable keyboard that could add/remove physical keys at speed-of-electricity then they’d be as good as each other).

Your argument sounds vaguely reminiscent of when C++ programmers talking about java say that complex pointer-arithmetic is an inherently faster programming paradigm - both in “time taken to code” and in “time taken to execute”. They are correct, of course - for a sufficiently narrow definition of each of those. In practice, time taken to code needs to include maintenance, debugging, and reading other people’s code; time taken to execute needs to include what happens when you unleash a runtime optimizing compiler (which can do better without pointers).

i.e. I believe you have a valid point, but also believe that on balance generally it’s subsumed by the practicalities that mean a CLI is generally a poor intereface EXCEPT as I said when it’s a sufficiently simple system it’s interfacing too. e.g. if all you ahve is yes/no questions, there’s no inherent advantage to a CLI (except that the code can execute faster) over a mouse GUI (the latter is faster for the user, but almost insignificantly so).

Java’s commercial succes is largely driven by the vast number of corporate legacy systems that are godawful and expensive to maintain but it’s even more vastly expensive to replace. Just because you’ve always done something and still do doesn’t mean it’s best - it may just be that the barrier to exit is too high. I’m not saying you’re wrong, just pointing out that there are other highly possible explanations underlying their decision…

GUI’s generally have some major advantages, (NB: depending upon how you define “GUI” of course!), along the lines of being able to present vastly more information simultaneously than a typical CLI does.

Of course, a bad CLI and a bad GUI are just as bad as each other :(. Modern 3D modellers are an example of how confusing a GUI can be, and old text adventures an example of how confusing a CLI can be - I played games where I never managed to pick anything up!

Well, obviously not, since I spent 6 years using CLI’s before I even saw a GUI :D.

Given the rest of this thread, that has to be a rhetorical question :). I know the (lack of) quality of nvidia-authored drivers - so good that linux support lists (used to) get very evangelical about “don’t use the nvidia driver, use the open source one instead - it’s so much better!”.

Thanks for the opinion. It’s very useful to know how much other people have been through before settling on a particular OS (variety).

Thanks for the pointer. Probably weill skip it though since I’ve had great success with tiny distros before, come to rely on them, and then they disappeared :(.

Yeah. But…you have to get really really mad at your OS before you can gather sufficient courage to do it :). And the realization that you’re going to miss a deadline anyway because OO + X + mandrake deleted/corrupted/lost your hard work is a great motivator to starting. :slight_smile:

I didn’t read everything, but regarding Debian you can call “modconf” to enable kernel modules, especially USB drivers. If you installed an older 2.2.20 kernel you should use “apt-get install kernel-image-2.4.18-bf2.4” to install a newer kernel before.

This message is the demonstration that I managed to get a copy of debian to install!

FYI I had to install in verbose mode *, workaround some other install bugs that I just randomly managed to fix, and then had to jump to the installer shell (alt-f2) and “modprobe pegasus” (the driver for my network card) at the appropriate time on the 2.4.x kernel for testing (not stable) and then re-run the detect-network-card menu option.

  • NB: actually, it might be that it only worked when not in verbose mode. I remember thinking “I’ve used verbose all the time - perhaps there is a bug in verbose mode?” but was so tired by that point I don’t recall if I was using it or not.

Although there are many many problems to resolve, this is not RedHat. It is not Mandrake (or any other RH-based distro). It is not Suse. So…I have a 98% confidence I shall be able to fairly easily resolve all problems - apart from those which can only be solved by upgrading to latest drivers :(. e.g. debian tantalizingly has a package for nVidia drivers which has the version number of the drivers released only a few weeks ago - however, when you attempt to install it, some of the components are missing and aptitude ends up instead installing an earlier version. This could be an incomplete-apt-mirror problem, but I now have a lot of “so complete I can’t tell the difference” mirrors so probably not.

Main problems are things like:

  • I’m now running KDE, which takes 10 times as long to start as my old WM (icewm)
  • no mozilla :frowning:
  • etc

Since this is debian (not redhat) it’s actually safe to uninstall such things, and easy, and won’t break your entire system :).

Anyway, I’m now off to sufficiently fix my system that I have mozilla + email, then write down all the bugs I found when trying to install debian, and send em a mail with my experiences (in case it’s of any help).

If I have the time + energy, I’ll put up a webpage detailing what broke, how to fix it, and why I kept trying debian even when it kicked me in the teeth.

I’m not actually looking for this data, but keep running into it by accident. E.g. I just noticed that I wouldn’t have a mouse if I installed FreeBSD - my graphics tablet (the most common, most popular, best supported Wacom Intuos series) driver won’t work because, according to the authors, there is some problem with getting FreeBSD to run linux-compiled stuff that uses USB within XFree86. Shrug. This is why I mentioned some time ago that whenever I see OS-level emulation I get worried; I’ve been down this path before and know the game ;).

[quote]That would be OK, except it looks like it could easily be just as bad as RH’s linuxconf: only partially effective, and frequently having to delegate to “manually edit the conf file”.
[/quote]
That’s kind of a rude comparison, blah. Sysinstall simply manages the installation of your system. Nothing more, nothing less. There are no files to edit manually, no fragile scripts to break. In fact, there really isn’t any area of the system that’s hacked up with large chains of scripts like RedHat or a similar distro. About the only system scripts are the rc.conf scripts. These scripts are actually easier to manage than the System V design of Linux.

[quote]That is a fair question. However, most CLI’s have the same number of problems IME - mainly consisting of unhandled errors and implicit unhandled assumptions/assertions in the (usually script-driven) CLI.
[/quote]
Not everything is about something being script driven. For example, I could run a fetch or wget on a set of packages I need downloaded from an FTP server, then run a ‘pkg_add *.tgz’. That’s going to be way faster than pointing and clicking each file.

[quote]Usability is not only about time taken to click/type/press. Even if it were, then GUI’s would STILL be best, since it’s been proven that it’s generally faster to initiate actions with a mouse than with keyboard given appropriately(sensible)-sized GUI buttons (if you had a resizable keyboard that could add/remove physical keys at speed-of-electricity then they’d be as good as each other).
[/quote]
That’s not my observations from watching data entry departments. It takes the key punchers far, far less time to type everything in a CLI and hit ‘transmit’ than it does to enter it into a Webpage or GUI and click submit. The problem is that GUIs are designed for a combination of keyboard and mouse and can often slow down someone who’s efficiency depends on keeping their hands on the keyboard at all times.

In any case, this is academic. The FreeBSD interface works. I and many others have used it and can attest to that. Arguing something you haven’t tried just results in a lot of speculation being thrown around. Trust me. FreeBSD is not Linux. If you want a stable OS that Just Works™, FreeBSD is the way to go. :slight_smile:

[quote]Your argument sounds vaguely reminiscent of when C++ programmers talking about java say that complex pointer-arithmetic is an inherently faster programming paradigm - both in “time taken to code” and in “time taken to execute”.
[/quote]
Actually, this is more like Java vs. C/C++. Java can do just about everything, but there do exist places where it is better (or sometimes the only option) to write code in C/C++. An example of this is JOGL. Someone had to write C code to interface Java with the underlying hardware. Even if OpenGL was written in Java in the first place, it would still need C or C++ code to send the commands to the hardware. Java doesn’t have that ability, and that’s not necessarily a bad thing. :slight_smile:

[quote]Given the rest of this thread, that has to be a rhetorical question :). I know the (lack of) quality of nvidia-authored drivers - so good that linux support lists (used to) get very evangelical about “don’t use the nvidia driver, use the open source one instead - it’s so much better!”.
[/quote]
Ack! You’ve definitely been spending too much time in the Linux camp. The NV driver is 2D only, and must use MESA software rendering to accomplish OpenGL. If anyone tells you to use the NV driver, tell them to take a long walk off a short pier. They’re probably gullible enough to do it! ;D

[quote]Thanks for the pointer. Probably weill skip it though since I’ve had great success with tiny distros before, come to rely on them, and then they disappeared :(.
[/quote]
Knoppix is not small. It’s currently considered a major distro. However, if it worries you, Mandrake puts out a Knoppix-like CD called MandrakeMove. There’s also Morphix which is software that allows you to do a very easy “roll your own Knoppix”.

The one other advantage to a CD based distro is that all your info stays safe on a CD key or shared file system. The OS cannot become trashed, and it won’t trash your files in the process of trashing itself (i.e. Your data is on a separate and safe file system). Upgrades are as easy as burning/rewriting a new CD, and you can always move to a more permanent OS at any point in time.

[quote]Yeah. But…you have to get really really mad at your OS before you can gather sufficient courage to do it :). And the realization that you’re going to miss a deadline anyway because OO + X + mandrake deleted/corrupted/lost your hard work is a great motivator to starting. :slight_smile:
[/quote]
Actually, it sounds like a great time to pop in a Knoppix or Java Desktop System Demo CD and finish your work. THEN you can play with new distros. :wink:

In any case, I’m glad to hear your system is working. I hope you haven’t lost too much time.

[quote] I’m not actually looking for this data, but keep running into it by accident. E.g. I just noticed that I wouldn’t have a mouse if I installed FreeBSD - my graphics tablet (the most common, most popular, best supported Wacom Intuos series) driver won’t work because, according to the authors, there is some problem with getting FreeBSD to run linux-compiled stuff that uses USB within XFree86. Shrug. This is why I mentioned some time ago that whenever I see OS-level emulation I get worried; I’ve been down this path before and know the game .
[/quote]
Actually, it looks like USB tablets don’t work period (or don’t work correctly, there seem to be conflicting reports). That has nothing to do with the “emulation” (which isn’t emulation) and everything to do with FreeBSD’s hardware support. It does appear to support the Serial models. You MAY be able to get the USB model to work by downloading a binary XFree86 driver from http://linuxwacom.sourceforge.net/. XFree86 used OS independent binary modules, so the “Linux Wacom” name is a bit misleading.

I’m afraid I don’t have a tablet, so I can’t tell you if it works or not. All I can say is that FreeBSD, USB, and XFree86 get along fine otherwise. I use a Microsoft USB Optical mouse, and Linux is the only OS that doesn’t support it correctly. :slight_smile:

I was going by the excerpt quote on the page you linked to - it showed a situation where you were being asked to manually edit some config files?

Why assume you’d need to point and click each file? That’s just cheating, by saying you’d compare a bad GUI against your CLI :).

Sure. I’m not interested in data-entry though, I’m interested in normal usage. Data-entry is all well and good, but again is a very narrow subset of actual usage.

I see what you mean; If I had confidence it would be 5-minutes to get working, rather than 5 hours of discovering and correcting lots of quirks and use of inappropriate drivers etc, then yes. But experience suggests that it won’t be 5 minutes, and if I’m going to invest that time right now (when I need to be minimizing time expenditure) it’s better to invest it in something I’ll definitely be keeping.

The linuxwacom group you quote say that FreeBSD is impossible because of the alleged USB - X86 - FreeBSD problem I cited.

[quote]I was going by the excerpt quote on the page you linked to - it showed a situation where you were being asked to manually edit some config files?
[/quote]
That’s just part of the interface. After you set everything up, you can optionally view the configuration and manually tweak it if necessary. It’s one of those “power user” features that some people find useful, but it’s not a requirement in any way. :slight_smile:

[quote]Why assume you’d need to point and click each file? That’s just cheating, by saying you’d compare a bad GUI against your CLI :).
[/quote]
Actually, I’m assuming that no “standard” interface exists for the task. With GUI apps, you’re SOL without a specially designed GUI. With the command line I can accomplish the task by stringing together generic commands. The end result is that the command line can allow you to accomplish tasks faster and easier.

[quote]Sure. I’m not interested in data-entry though, I’m interested in normal usage. Data-entry is all well and good, but again is a very narrow subset of actual usage.
[/quote]
It’s still a use. You pointed out that the CLI was dead and was useless in ALL cases. I merely pointed out that data entry is an example of an area where the CLI remains king. It’s probably worth mentioning that data entry is by no means a “specialized” area either. Just about every major company needs key punchers for some form of data entry or another.

[quote]The linuxwacom group you quote say that FreeBSD is impossible because of the alleged USB - X86 - FreeBSD problem I cited.
[/quote]
I said it could work. The reports are a bit conflicting. Officially, only the Serial version is supported. :-/ As I said though, this has nothing to do with Linux programs.

blar*3, is the machine in question a Dell Laptop?

Linux support isn’t as good on laptops as it is desktops due to less-standard hardware that’s normally used. You have a fighting chance on the big name brands at least. Dell hardware I’m guessing is not as good as IBM etc, so it could be a bit harder - at least however you have a lot of other people with the same machine. The problem with my old laptop was that I think only about 3 were ever sold so getting stuff like the internal modem working was very hard.

I have given up on Linux on laptops - too much effort, so I now have a PowerBook (zero effort - everything is supported and supported well!) :slight_smile:

Linux on desktops is a piece of cake these days, I use Fedora and have not had any problems (beyond a faulty IBM HDD). My linux desktop machine and Mac laptop communicate very nicely so I think I’ll keep the current setup (mac for the laptop, linux for home).

Red Hat Enterprise Linux is a good option too - it’s stable, and supported and a little more up to date than Debian. White-box enterprise linux exists if you don’t need the support and don’t want to pay, but I havn’t tried it out.

Will.

[quote]I have given up on Linux on laptops - too much effort
[/quote]
This depends entirely on the laptop. Problems are more likely than on a PC (because of exotic hardware), but if you search the net for possible problems before you buy the laptop you probably won’t have install troubles. That said a PowerBook isn’t a bad choice either. :slight_smile:

http://www.linux-laptop.net/

[quote]blar*3, is the machine in question a Dell Laptop?
[/quote]
Yes. But these days that’s largely irrelevant for three reasons.

  1. Laptops are now almost exclusively using ultra-common components; I guess partly because of the huge price competition (forces them to source as many common parts as possible).

  2. It seems as though completely new types of hardware have been created more slowly than linux has been adding drivers for them. This is just a guess, based on the fact that it’s now been a long time since I installed linux on a machine where all it’s hardware - no matter how bizarre (and not even supported in windows!) - is considered “run of the mill” by linux (and which includes stuff that I know wasn’t just a few years ago).

  3. The broken nVidia linux drivers - cause of many of the Dell problems, e.g. the fact that they deliberately disabled ALL system power management for several years, to work around bugs nV couldn’t be bothered to fix! - have finally been brought up to scratch, by the looks of things. At least, I’ve noticed power management suddenly actually working in linux (e.g. suspend when I clsoe the lid, restore afterwards. Suspend-to-disk when on low battery, etc), and all I changed was to upgrade the nVidia driver…

I agree theoretically, but c.f. above - it seems that linux now has practically all the non-standard stuff covered too :).

c.f. the previous linux thread. Installed latest supposedly stable and working Fedora on a desktop server (Dual Pentium-3, but with only one CPU, approx 1 gb RAM, a very common SCSI card, etc) and it broke itself on install. Even with experience of every redhat back to 5.2 I still could NOT fix the major screwup performed by the Fedora install. I could run X, but almost nothing else. The package database was broken on install! Networking was broken because the install program had used the wrong damn syntax for it’s own config files! This is not small problems :(…

Haven’t tried it, but it makes sense. I’m more than a little suspicious that Fedora is deliberately (and subtly) crippleware as far as RH are concerned. Wouldn’t be surprised to see a corporate memo leaked in a few years telling staff to mildly damage stuff whenever creating new patches :).

Not true, it could be done entirely in Java. Just as you can have an OS or a JVM written entirely in Java.
Ok, so the Jikes VM isn’t quite entirely in Java, but that was a matter of convenience rather than necessity.

[quote]Not true, it could be done entirely in Java. Just as you can have an OS or a JVM written entirely in Java.
[/quote]
“Could” being a nebulous concept that doesn’t actually exist yet. I quite agree that you could write an OS entirely in Java, and then you could implement OpenGL drivers in Java. But until someone writes such a system, Java needs to push everything through an operating-system specific binary layer - usually written in C/C++ - to get at the hardware.

Blar,

Personally I like the idea of the RHEL/Fedora combo - the former is a professional, stable, supported system (we use it at work, and I can vouch for the stability and the good support staff). The latter is more community orientated and cutting edge, great for my home PC :slight_smile: They serve different goals, it’s not like they get RHEL, remove stuff from it and tada: Fedora. I was critical of their decision at first too, that is until I started using both operating systems and realised there is a place for both.

Jens & Blar,

I am aware it’s quite possible to get Linux running on a laptop - I had a very hard time finding a laptop with a half decent graphics card from a brand which advertises Linux support (e.g. IBM). Some had the “pro” OpenGL cards, but I wanted a gamer card (I’m writing games after all).

I actually ordered and paid for a Dell laptop before I decided that I was sick of stuffing around trying to get things working and cancelled the order (that is another story…).

I researched the Dell laptop I was getting, and a lot of people reported success with it - but there was always one gray area - something that didn’t work. Things like the trackpad not behaving, lack of power management, stays on when you close the lid, no internal modem.

Getting stuff like Internal modems to work is just an uphill battle - yeah 56k modems are crap, and internal ones even more so. But… It’s annoying having hardware that you cannot use in the operating system of your choice! There are times when that is all you have.

Why I picked a PowerBook is I decided I would be no less productive - and I wouldn’t have to waste all the time struggling with hardware when setting it up, and it had an awesome graphics card (as I said, the better IBM’s have the pro OpenGL cards which were not what I was after).

I’m not trying to argue here, I think Linux is truly great. On my PC, I can have Fedora installed in under 30min, with full hardware support - far less time to install/patch/get-3rd-party-software&drivers with Windows. However, I’m not going to waste hours setting up a laptop only to have partial hardware support when I can have a PowerBook up and running in with all my favourite linux and java tools in no time. I look forward to the day more laptops are Linux certified.

Will.

As cfdobbie said, “could” is a bit nebulous. Yes, you can write an OS in Java. That’s what the JNode people are doing. But they’re also creating non-standard hardware interfaces (using JNI & assembly) along the way. In the standard version of Java, no such hardware interfaces exist, and Sun has no plans of adding them. Until such hardware interfaces are added, you cannot directly access hardware without native code.