linux install...the saga continues

(FYI for newcomers, I had to re-install some linux servers a while back, and took it as an opportunity to tree different distros latest versions to see what happened. Redhat “Fedora” failed miserably, Mandrake is too proprietary for me to risk it, and I ended up with Debian after a great deal of pain).

(Hope this is of use for some people; I’m bored senseless @ 3 am having now spent about 5 hours trying to fix some moron’s mistake, so I thought I might as well write this whilst waiting for a CD to install…)

I just installed my laptop from scratch with Debian - in under 30 minutes!

I was seriously impressed. OK, so there are problems (more later), but hey - not only did it actually work but it even instructed you on everything as you did it (so you knew what was happening) AND you could keep going back and re-making old decisions!

(and, for anyone who doesn’t know apt [the plain/crap debian package-management tool], when you install packages, each one gives you an information screen about that package AFTER you installed, asking you any specific config it needs to do, or including warnings etc)

Only, the **** who wrote the debian installer is a complete ****ing ****: I then had to spend 4 hours discovering what a jerk this person/(people?) is. In their infinite moon-gazing wisdom they decided that - unlike all other linux distros - mere mortals who install debian are only ALLOWED a kernel with a tiny subset of the possible kernel modules. Doesn’t matter that all the others were on the CD. This person prevented debian users from installing ANY USB DEVICES when you install debian (have a system that requires USB? Ha! No chance! You’ll have to find non-USB hardware and then spend an hour or so compiling a new kernel with sane defaults) and other such madness. So if you need any of (rather a lot of things) in order to run your computer you have to start again from scratch once it’s installed and compile your own kernel.

User friendly? No frickin way!

Why do I care? Well, apart from the fact that my mouse is USB (sob) my network card is too - and is included in the linux kernel source! (it’s a pretty mainstream device!). But I can’t use it - so no LAN access, no possibilty of installing extra modules, no chance to fix all the other broken bits of the install, or to download FAQ’s etc (lucky I had a second spare computer here, really).

Anyway, on to the “there are problems” bit. Debian seems to be summarisable thus:

  • it’s like a masterpiece that the painter died halfway through: a lot of it is excellent, the rest looks like no-one’s got around to looking at it yet
  • there’s no documentation, but everything you try to do has extensive context-sensitive help (and I mean EVERYTHING: not just when you are choosing what to install, as with other distros, but whenever you do anything to your system - it’s like using Windows Wizards. Lovely. Except there’s no “back” and you can’t view the information afterwards. Which is especially sad since you get exposed to dozens of pages of text you need to write down by hand in order to refer to later :()
  • they hacked a lot of standard packages and broke them. E.g. they broke Bugzilla. This is because they removed things they felt were unecessary but “forgot” to finish the job and remove the REFERENCES to those things (and forgot to tell anyone what they’d done!) so that the app breaks when it gets to the relevant point
  • X-windows doesn’t work out-of-the-box on an nVidia GF2Go. Never a good sign!

Now some examples of the “masterpiece” aspect (the nasty installer was an example of the hackery + not quie finishing the job you started):

  • you can install a new kernel (get this, ladies and gentlemen) by TYPING TWO LINES OF TEXT! Literally! From scratch!
    • …except the instructions, in 3 different sources INCLUDING THE DAMN F.A.Q.! start with the text:
      “cd to the kernel directory. If you don’t, this won’t work”.
      for the record, this is the only time I’ve ever encountered kernel-compilation instructions that DIDN’T BOTHER TO TELL YOU WHERE THE KERNEL DIRECTORY IS. (FYI for linux newbies: you have to do this bit by hand, which is not mentioned in all of the three places, and so it could be “anywhere you chose to put it”).
    • but, when you do, it automatically:
      • does the “Linus made a strategic error when deciding how you compile kernels” multi-stage make stuff all automatically
      • creates the image automatically (although IIRC it has the wrong initrd setting by default, which is bad)
      • installs the image into the boot dir
      • runs LILO
  • aptitude is probably the best package-mgmt system I’ve ever seen on linux (I’ve seen better stuff on commercial UNIX IIRC).
    • it’s like SuSe’s (which is much much easier to use than anything from RedHat) except:
      • it isn’t full of bugs and keeps crashing/screwing up
      • it’s much better at automatically resolving things, and showing you what’s going on
    • it’s almost easy enough to use that a normal PC user could cope with it first time. The only problem is the insistence on using cryptic case-sensitive commands all over the keyboard for doing everything. You have to press ? for help about once every 10 seconds for the first 5 minutes :frowning: because there’s so much to memorize
    • BUT…it’s not even mentioned in the official FAQ
    • …and it’s not used by default
    • …and they don’t exactly go out of their way to tell you it exists
    • …and it won’t let you re-view the installation notes for anything you installed (as mentioned earlier, so you have to write it down, or take a photo of the screen, or something!)

Blah, just do yourself and everyone else a favor and install FreeBSD. You can run all your Linux programs faster, configure your system how YOU want it, and it will even be nice and stable. No odd bugs like Optical Mice cutting out, or disk drives getting corrupted. No hardware going undetected that should have been detected. No confusing HOWTOs on how to configure some feature implemented by a four(teen) year old. Just plain old Unix. That is, the simplest Unix short of OS X.

[quote]…configure your system how YOU want it…
[/quote]
3Blah’s article and this statement make clear why this Unix stuff will never make it to the desktop.

Persons like me, representing the common, mass market user, don’t want to configure our systems. We want them - or better we NEED them to be already configured!!

When I use a n00b to freebsd, i spent the best part of 6 months in the “already configured” standard installation. And I must say, even when I didn’t use the optimisations, it still ran faster than linux and windows combined.

AAANNND, it wont swap out eclipse when you minimise it :wink:

Aye to that! Bring back BeOS!

Cas :slight_smile:

sure bring it back. then after an hour, youd get bored, because there are no applications to run on it ;D

Surely not so hard to get a JVM and GL drivers on it eh? In fact it already had a JVM and GL drivers… just both were incomplete when it bought the farm.

Cas :slight_smile:

There are some dudes working on Java for BeOS - they demoed some AWT stuff some months ago - it is a 1.4+ port, sanctioned by Sun AFAIK. It will run on BeOS and HaikuOS. When it goes public, I’ll look into getting lwjgl to compile on it (there is a BeOS OAL port too). Unfortunately I don’t have the OpenGL HW distribution, nor a supported card so it will be SW :confused:
FWIW, there are tons of BeOS applications - and even though there weren’t there are all those you need - it’s not like I download 10+ apps a day just to run them… - give me IRC, IM’s a browser and a Console, all of which BeOS has ;), and I’m good to go :slight_smile:

[quote]Blah, just do yourself and everyone else a favor and install FreeBSD.
[/quote]
Please forgive me if I’m wrong, but weren’t you one of those strongly suggesting I move to debian last time I was doing this? ::slight_smile:

I might have to try BSD now (c.f. next post) :(. Although, interestingly, I did actually evaluate Open and FreeBSD before going with Debian this time - can’t remember what I found, but I found enough signs of a mongolian clusterfuck that I thought “Sod it; I at least know Debian isn’t plagued by that ****”. Little did I know Debian had a dirty little secret… :frowning: >:(

AFAICS I’m doing everyone a favour by spending significant time with each OS, trying really hard to get it to work - it means I’m able to give everyone else a deep and meaningful view of what they’re each like, and so give a much better taste than all the moron-reviews on linux websites that go “Well I installed with all the defaults and it restarted and I could run mozilla. -endofreview]” which explains partly why some things like redhat are so crap for real people - they optimized for moron-reviews :(.

My conclusion: Debian sucks. Not as bad as Mandrake, nowhere near as much as RedHat, but … worse than both, it’s good at NOT INSTALLING AT ALL on very common machines (modern Dell laptop). This is sad, because otherwise it wouldn’t suck at all and be a wonderful OS that’s only 3-5 years from nirvana.

Further to my previous pain, I’m now going to have to give up because of Mr. Moron Debian Developer who decided that USB network cards are “the Devil” and should be forcibly kept off any installed Debian.

Think I’m over-reacting? Get this: Not only does it refuse to let you put it in your install kernel (previous post - so you cannot use your system until you’ve learnt how to make custom kernels - and you can’t even run 1/6 of the install process because it requires a net connection!), but…

They hacked (****ed up would be more accurate term) the 2.4.18 kernel so that it WILL NOT LET YOU install any USB network cards. “make menuconfig” “make config” etc DENY access to the USB net card options.

Prior experience with Debian would suggest there is a secret file somewhere called something like “wibblemyfish.txt” that if you delete, all USB network cards are instantly enabled in every Debian kernel without recompiling. This is typical of them: they obviate the need for some part of the standard linux system, but turn it off by defualt, don’t tell you how to turn it on, and don’t even tell you they did it. Then probably laugh at you when the original authors refuse to help bcause you’re using a hacked copy of their source.

Seriously, this sucks butt.

I tried manually editing the make config for the kernel and manually inserting the line for my USB net card, and recompiled. Doesn’t seem to have worked. Then again, perhaps there’s some fundamental piece of network setup that the install system decided not to install because it failed to find a network card (because you wouldn’t let me enable it at install time, you ****ers!).

All I know is that even after a successful recompile I still can’t get the system to accept the existence of the network card :(. Sob. They’ve also ****ed up the kernel in other ways - e.g. my recompile crashes the computer after something like 120 seconds after booting, so I only have a minute or two to try fixing the networking before I have to remove the battery and cut the mains power (complete hardware hang :().

Now, I don’t know WHAT or WHY they’ve done this, but I’ve been using 2.4.18 kernels for years and I KNOW this shouldn’t be happening. Maybe they have a good reason, but IMHO any distro that deliberately hacks and then breaks a kernel is a distro to avoid at all costs.

Goodbye, Debian! I’ll miss aptitude; really - so much so that if I can find anyway to get you to work I will, just to get that decent package-manager.

Behold! I was completely wrong! (sort of). I made a single incorrect assumption…

I thought it was running the 2.4.18 kernel.

It said it was running that kernel
It only comes with the source for that kernel
It’s a well-known fact that this version of debian uses that kernel
But…

The installer uses a 2.0.x kernel, apparently (!! Very buggy and old!), which doesn’t even recognise the existence of USB (wasn’t added to linux until much later!) and hence wouldn’t install.

Apparently, if you’re an old hand at debian, you know NEVER to follow the installation instrcutions (which tell you to hit enter) but to force it to use the modern, less buggy, should-work-for-almost-everyone-if-not-everyone, kernel.

IMHO it was a very sad day that they decided to put the up-to-date working debugged kernel NOT as the default, and to instead default to (and advise the user to go with) the so-old-it-has-no-chance-of-supporting-half-your-hardware kernel.

EDIT: I’m sure they have a reason. It’s just that I suspect it’s something like “but there’s a bloke in Poughkeepsie who has an 8086 from 1989 that is no longer supported even by linux, and we just HAD to favour him over everyone else, cos we think it’s cool that debian still supports out-of-the-box hardware that even other linux distros started using as doorstops 5 years ago” ;D. I think you know what I mean…

So, I’m re-installing again (8 hours so far, and counting)…

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) - although this is NOT a problem with normal 2.4.18 kernels, and it didn’t happen with the (allegedly) 2.4.18 kernel installed by the 2.2.x installer.

Nothing I can do. Short of re-writing the debian installer. Am I annoyed? Yes. 8+ hours down the drain because of an apparently-broken hacked kernel. Gits.

Nope, that wasn’t me. If I was suggesting a Linux distro, I would have recommended SuSE. Believe it or not, it is actually the best of the Linux distros. If that doesn’t work for you, you need a new OS.

Debian hasn’t been updated in several YEARS. I don’t know the reasons, but apparently development is severely lagging. I think the problem may have something to do with lack of stability in recent kernels.

BTW, my last recommendation was in this order:

  1. Mac
  2. FreeBSD
  3. At least use ReiserFS

[quote]I might have to try BSD now (c.f. next post) :(. Although, interestingly, I did actually evaluate Open and FreeBSD before going with Debian this time - can’t remember what I found, but I found enough signs of a mongolian clusterfuck that I thought “Sod it; I at least know Debian isn’t plagued by that ****”. Little did I know Debian had a dirty little secret… :frowning: >:(
[/quote]
Now you’ve got me curious. If you remember, let us know what you found. Maybe it’s just that something works a bit different?

You have two major choices for FreeBSD. The 4.x series is the absolute best in stability, but lacks decent multiprocessor support. The 5.x series is slightly less stable, but is designed for better performance and to run easily with 2 or more processors.

[quote]AFAICS I’m doing everyone a favour by spending significant time with each OS, trying really hard to get it to work - it means I’m able to give everyone else a deep and meaningful view of what they’re each like, and so give a much better taste than all the moron-reviews on linux websites that go “Well I installed with all the defaults and it restarted and I could run mozilla. -endofreview]” which explains partly why some things like redhat are so crap for real people - they optimized for moron-reviews :(.
[/quote]
It’s actually amazing how many of those “articles” I’ve heard. Linuxworld even publishes some of them! I once saw an article that said “Lycoris looked cool, but when I installed it the screen went green. [End of Article]”

BTW, you might find these reviews to be a bit more helpful.

Just spent a few hours checking out FreeBSD in detail.

Brief conclusions:

  1. Documentation is one of the best of any linux(esque) I’ve seen - the website’s “FreeBSD Handbook” is great

  2. Looks like the mechanism for installing apps and upgrading the kernel is the best technological solution

  3. BUT (and this is a great big two-volvos-parked-next-to-each-other sized butt) … it looks like 99% of everything is via manual typing at a bash prompt, and that is totally unacceptable. All the docs and FAQ’s and guides I could find always just went through endless amounts of make paramters you had to type in. This is 20th century - no-one should ever use Make these days. For anything. Using it to maintain an entire system is disturbing.

  4. Also, you are still dependent upon the generosity of others - e.g. nVidia’s Geforce drivers are close to a year out of date, and since their linux drivers were only just getting up to scratch in the last few months I doubt the BSD ones are good. As with Debian, it’s the age-old “if you’re using a headless server, or a middle-of-the-road Dell desktop, you’ll be fine. Everyone else should expect (possibly insurmountable) problems”. But BSD has a bigger problem with this than Debian - with Debian, you can guarantee to get other linux stuff working somehow (though it might screw up your system) but BSD cannot run ALL linux software.

Perhaps, one day, Debian and BSD could merge? :slight_smile:

Anyway, FreeBSD looks a damn good choice for servers.

But … what about the Java Desktop System? Or even … Solaris??

Make?! Who uses ‘make’? I usually grab the precompiled package off the CD or FTP server. Just run ‘/stand/sysinstall’ and use the post installation tools to add whatever packages you want.

As for the command-line, it works better than Linux. So why complain? Especially since you can get so much more done over SSH than Windows would ever let you do.

[quote]4. Also, you are still dependent upon the generosity of others - e.g. nVidia’s Geforce drivers are close to a year out of date, and since their linux drivers were only just getting up to scratch in the last few months I doubt the BSD ones are good.
[/quote]
Blah, you’re starting to reach. I’ve used the NVidia drivers for FreeBSD. They’re every bit as fast (if not a bit faster) than the Linux drivers. The Linux drivers keep getting updated because the Linux kernel keeps changing (and breaking). FreeBSD doesn’t have that problem. Kernel interfaces rarely change, and if they do they only change between major revisions. Thus a FreeBSD module is far more portable across versions than a Linux module. As far as Linux is concerned, you have to recompile a module specifically for your exact version and configuration of the kernel!

[quote]As with Debian, it’s the age-old “if you’re using a headless server, or a middle-of-the-road Dell desktop, you’ll be fine. Everyone else should expect (possibly insurmountable) problems”. But BSD has a bigger problem with this than Debian - with Debian, you can guarantee to get other linux stuff working somehow (though it might screw up your system) but BSD cannot run ALL linux software.
[/quote]
Why can’t BSD run ALL Linux software? It’s all worked fine for me. Just make sure you install the Linux GL compatibility stuff so that you can use Linux OpenGL software.

Honestly Blah, you’ve spent days installing RedHat, Mandrake, Debian, and other horrors of OSes. Why not give FreeBSD a fair shake?

[quote]Perhaps, one day, Debian and BSD could merge? :slight_smile:
[/quote]
You mean like this monstrosity? Trust me, FreeBSD’s userland is already plenty clean and useful. And since they can already run Linux programs, I don’t see what the point would be.

Seriously Blah^3 haven’t you learned the lesson yet. “Don’t bother with Linux. It is shit.”

That much should be obvious to you by now.

Having used Windows, Linux, Mac OS X, even briefly BeOS… I have to say that without question Linux is likely to have the most problems. I don’t mean to bash it for all those people that like it… but quite frankly they probably just lucked out. Mind you I can find bad things to say about the other OS’s as well (mainly Windows of course).

So you are already starting out choosing to run the OS (regardless of distribution it seems) that is likely to have the most problems… and then you post here because by-golly it really does have problems. This isn’t news. Stop bashing your head against the wall.

Unfortunately, it’s still required by a lot of GNU software, including linux kernel builds :(. 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:

Think more about what I’m saying, dude! In linux, you have GUI’s to do this stuff…

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.

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.

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!

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.

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]Seriously Blah^3 haven’t you learned the lesson yet. “Don’t bother with Linux. It is shit.”
[/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). As long as I need to print (!) or use any MS apps (!) windows is no good to me.

I also have development tools that don’t run on windows. I have the source, but I don’t have the time to re-learn C++ and windows programming and enough of the MS unix services layer to compile/port them over to windows so that I can do any work!

And I can’t seem to get any Sun JVM to install itself on this windows 2k machine WITH webstart, which cancels the advantages I ought to have from using java tools for 90% of my work :(.

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.

My never-ending quest to find a linux distro that is better than a hole in the head ;D. Seriously, bar this problem with a miscompiled kernel, debian has done pretty well so far. Although it does have a serious problem in that you often encounter software that is not distributed as DEB files. So far, I’ve managed to find conversion scripts written by 3rd parties every time I needed - but the apps that come with debian for doing this automatically (Alien I think one is called) don’t tend to work :(.

I have to do the process anyway. Given the number of people undecided about linux, or thinking of trying it, my experiences ought to be of some help in understanding what you’re getting in for (especiallly helpful given the radical differences in usability between distros, that their proponents try to brush under the carpet).

I used to think a lot of SuSe, until it destroyed one too many systems - e.g. bugs in suseconfig that rendered the system unusable and easier to reformat than fix :(. I’ve been long watching successive versions to see if they sufficiently fixed the problems, but every time I do I check the online support / docs and find stuff like the suse site still doesn’t work properly (which is - or at least used to be - the only source of help, troubleshooting, etc) and given up.