Slashdot Mirror


Getting Grubby & Demystifying Linux Booting

davidmwilliams writes "Linux users can boast long times between reboots, but even so, the startup screens will grace your display at some time. Here's just what your computer is doing during this process, what the messages mean, and how you can take control."

105 comments

  1. Redhat specific by Janosh · · Score: 3, Informative

    The aritcle is wery redhat specific.

    --
    When i Moderate something -1 Flamebait, why do i not get another modpoint?
    5--1 = 6
    1. Re:Redhat specific by freeweed · · Score: 3, Informative

      Yeah. chkconfig, eh. :)

      It's also rather light on content. 3 pages to say "yeah, this runs, and a bunch of other stuff that I won't talk about happens".

      This might have been useful in 1999.

      --
      Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
    2. Re:Redhat specific by vidarlo · · Score: 1, Informative

      The aritcle is wery redhat specific.

      You must be kidding

      And yet the article claims

      Linux users, almost by definition, like to get their hands dirty, and understand how their computer really works under the hood.

      The article won't help, however... It is not nearly detailed enough for learning anything.

    3. Re:Redhat specific by Procasinator · · Score: 5, Funny

      Be wery, wery quiet.... I'm hunting grubby webhats!

    4. Re:Redhat specific by Anonymous Coward · · Score: 0

      Ye'r wery pert, cully. Wery pert, indeed.

    5. Re:Redhat specific by fymidos · · Score: 1

      ... while at present there are many more ubuntu users who might actually be interested in this information.

      --
      Washington bullets will simply be known as the "Bulle
    6. Re:Redhat specific by CaptDeuce · · Score: 1

      The aritcle is wery redhat specific

      It's all the fault of that screwy wabbit.

      --
      "Where's my other sock?" - A. Einstein
    7. Re:Redhat specific by dbIII · · Score: 1

      This might have been useful in 1999.

      About then (or maybe a lot later) the only grub documentation was: GRAND UNIFIED BOOT LOADER - we rox and LILO sux. Thankfully there's a lot more than that now and even a man page (was "info" only for not invented here reasons for a while).

    8. Re:Redhat specific by ScrappyLaptop · · Score: 1

      ...or s/he was typing too close to the nuclear wessels...

  2. Bad article by vidarlo · · Score: 4, Informative

    Nothing new, and the author has apparently not used any other distros than the Redhat based ones. Nor has he heard about lilo or syslinux. First page of article looks like the man page of grub, listing the format for the menu.lst file of grub. Since it mentions selinux and redhat, I bet most of that page is copied more or less in verbatim from Redhat's manual. And since such a short article is split over 3 pages, and last page is laden with icons for digg, slashdot etc. I believe this is just an attempt to get some readers... Just don't bother to RTFA!

    1. Re:Bad article by dkleinsc · · Score: 2, Informative

      Just don't bother to RTFA!
      I don't think you have to worry: we won't RTFA anyways.

      But seriously, it's not that confusing: BIOS finds and starts grub, which finds and starts kernel, which finds and starts init, which finds and starts everything else listed in the correct sets of /etc/init.d scripts.
      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    2. Re:Bad article by weeboo0104 · · Score: 3, Informative

      I'm not sure I agree about this being a bad article. Sure the things the author goes into are things that are second nature for experienced linux users, but people who have only been exposed to Red Hat or Fedora might not be familiar with all of the logs that are collected in /var/log and might not really know just how useful grep and dmesg can be. It might not warrant it's own webpage, but I hope the author considers posting it as a sticky to Linuxquestions.net

      --
      It is easier to build strong children than to repair broken men. -Frederick Douglass
    3. Re:Bad article by KillerBob · · Score: 4, Informative

      Yeah, but that's very *very* distro-specific.

      Slackware-based distros, for example, use runlevel 4 for X instead of RL 5. They also have *all* init scripts in /etc/rc.d, and the scripts are started on basis of whether they're executable. Anything runlevel-specific, like login managers and X servers are then loaded from /etc/rc.d/rcX.S where X is the runlevel.

      that's to say nothing of distros that aren't even using SysV init, like the current version of Ubuntu and anything BSD-based.

      It was pretty obvious that the author hasn't done his research, and that it's a pretty poor attempt at explaining stuff. I was rather hoping for an article where the author would actually parse the output of dmesg and explain, line for line, what everything meant. That would actually be informative. Instead, he gave information that was specific to RedHat Linux, a lot of which doesn't apply to other distros. I wouldn't even be complaining so much, except that he didn't even bother to write it specific to the most popular Linux distro. RedHat was the most popular when I started with Linux, over a decade ago. These days, that crown belongs to Ubuntu. If you're going to write something distro-specific, at least write it for the most popular one.

      Obligatory disclaimer: The last version of RedHat that I used was RedHat 6.0. When 7.0 came out, I switched to Slackware. I now use Zenwalk (slack-based, formerly MiniSlack, http://www.zenwalk.org/), having switched at Zenwalk 2.4. I have tried other distros, including Ubuntu, and still prefer Slackware-based distributions, and I find that the Zenwalk community and package management tools are the best of that breed.

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
    4. Re:Bad article by Anonymous Coward · · Score: 0

      I think it's best not to mention lilo, grub is it's successor and easier to use. As for syslinux that more something to boot cdroms, so understandably not in the article.

    5. Re:Bad article by WhiteSpade · · Score: 1

      I was rather hoping for an article where the author would actually parse the output of dmesg and explain, line for line, what everything meant. There's a lot of comments here which discuss how much this article sucks - and I tend to agree. However, I really am interested in learning more about the boot process and really what all that dmesg output means. Does anyone have a link to an article that Slashdot can deem "worthy?" I'd be quite interested in reading it. ---Alex
    6. Re:Bad article by i.r.id10t · · Score: 1

      And Ubuntu doesn't have an /etc/inittab either...

      --
      Don't blame me, I voted for Kodos
    7. Re:Bad article by ozmanjusri · · Score: 1
      Does anyone have a link to an article that Slashdot can deem "worthy?"

      This one's a bit elderly, but I found it handy for wrapping my head around Linux.

      --
      "I've got more toys than Teruhisa Kitahara."
    8. Re:Bad article by inode_buddha · · Score: 1

      You could always do it "old style" and dd the kernel image to the first disk sector.

      --
      C|N>K
  3. Re:Rob Malda says by andy666 · · Score: 1

    Yeah, but that is all about the desktop, even if you agree with him. This is a nerd oriented technical article.

  4. No Upstart? by dzelenka · · Score: 3, Informative

    How can you have an article about init without even mentioning upstart? Ubuntu has been using it since 6.10.

    --
    Bah!
    1. Re:No Upstart? by Colin+Smith · · Score: 1

      How can you have an article about init without even mentioning upstart? Ubuntu has been using it since 6.10. Because nobody can find any documentation on upstart?

      --
      Deleted
    2. Re:No Upstart? by Simon+(S2) · · Score: 3, Informative

      Because nobody can find any documentation on upstart?

      I think you didn't do your homework.
      --
      I just don't trust anything that bleeds for five days and doesn't die.
    3. Re:No Upstart? by dzelenka · · Score: 1

      I gave the parent the benefit of the doubt, and assumed he meant that the article's author couldn't find any upstart documentation to cut and paste in. You know, sarcasm about the originality of the article.

      This whole topic gave me the nudge to go back and read up on upstart. It really does have the potential to be either a colossal mess or a magical cure. I look forward to seeing how it plays out.

      --
      Bah!
    4. Re:No Upstart? by Simon+(S2) · · Score: 1

      I gave the parent the benefit of the doubt, and assumed he meant that the article's author couldn't find any upstart documentation to cut and paste in. You know, sarcasm about the originality of the article.

      Oh yes. Now that you say it maybe it is like that. Sorry Mr. Smith. I didn't mean to be mean.
      --
      I just don't trust anything that bleeds for five days and doesn't die.
  5. Pathetic by Anrego · · Score: 4, Informative

    That article was just pathetic.

    The concept to write an article about the boot process actually sounds cool, seeing as how there is quite a bit text that whips by on start up which many (even long time) Linux users don`t understand.

    This article however, was a really lame attempt to do so. It was very general, without even so much as a sample of text from dmesg. And what was there was very distro-specific. It just provided a quick over view of the major parts of the boot process, and didn`t even do that very well.

    Anyway, as someone said before, don`t even bother reading TFA..

    1. Re:Pathetic by dermoth666 · · Score: 1

      I fully agree with you. The article is filled with inaccuracies and misleading information. The writer clearly doesn't understand fully what's going on under the hood.

      To bad so many people will read this and end up with a biased understanding of the Linux boot process....

    2. Re:Pathetic by Cryophallion · · Score: 1

      RTFA?
      What?
      Am I supposed to do that?
      I have just been responding to what I misread in the summary.
      Someone should have told me when I joined, I never would have figured it out on my own... oh the wasted comments I have left. :^)

    3. Re:Pathetic by sound+vision · · Score: 0

      Why do some people use the accent mark (`) in place of the apostrophe (')?

    4. Re:Pathetic by mustafap · · Score: 1

      Because they aren't grammar Nazis, and they know we would understand, or just not care.

      --
      Open Source Drum Kit, LPLC deve board - mjhdesigns.com
    5. Re:Pathetic by zenkonami · · Score: 1

      It leaves me to wonder if there are any good Linux Wikis out there that explain things like the boot process clearly and simply, largely without all the technical language and recursive definitions. There's plenty of man pages for those who can parse them, but as far as getting more users to Linux, I'd think this would be quite helpful.

      It may not bring "the average user", but it may help the curious yet non-power user be a little less afraid of Linux on the desktop.

      For myself, I think I could surf such pages for hours =D

      --

      Do You Experiment?
    6. Re:Pathetic by dragonturtle69 · · Score: 1

      While I agree that the article is short on details, I would not characterize its content as pathetic. It is just an overview of the boot process for Redhat. It would be improved by adding links for more in depth information on runlevels and init.

      By it being posted on Slashdot, it may help some of the Windows users who think Linux is hard to at least try a dual boot. If nothing else, the fact that Windows can only boot in Safe Mode or Normal with limited customization, while Linux has different boot loaders, can be booted from several devices (Your OS and data directory on a USB stick can be a fun), run levels, and init scripts, all of which are configurable including graphics/fonts/amount of information displayed/shells, just might get a curious Windows geek to check it out.

      --
      "What luck for the rulers that men do not think." - Adolph Hitler
    7. Re:Pathetic by normuser · · Score: 1

      Maybee because they look exactly the same?

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
      XXX#######
    8. Re:Pathetic by WuphonsReach · · Score: 1

      It leaves me to wonder if there are any good Linux Wikis out there that explain things like the boot process clearly and simply, largely without all the technical language and recursive definitions. There's plenty of man pages for those who can parse them, but as far as getting more users to Linux, I'd think this would be quite helpful.

      Without looking, I would guess the Gentoo Wiki. Even when I'm looking for information on other distros, Google often turns up hits to Gentoo Wiki.

      (I also ran Gentoo for 2-3 years. It was a very good distro for learning the ropes because you do so much at the command line. Not as bare metal as Linux From Scratch, but definitely more so then a standard Ubuntu install.)

      --
      Wolde you bothe eate your cake, and have your cake?
  6. Windows refugees by Harmonious+Botch · · Score: 4, Interesting

    The article won't help, however... It is not nearly detailed enough for learning anything. For the recent immigrants from Windows, it is a great roadmap.
    1. Re:Windows refugees by NeverVotedBush · · Score: 4, Insightful

      And there are apparently quite a few Windows immigrants. More how-to and helping them get their Linux-legs is a good thing. And they will need all levels of articles too.

    2. Re:Windows refugees by Anonymous Coward · · Score: 0
      On my fuzzy screen:

      user@pIII:~$ uname -a
      Linux pIII 2.6.20.6 #1 Sun Apr 8 12:00:25 CEST 2007 i686 pentium-iii i386 GNU/Linux
      user@pIII:~$ uptime
      21:40:05 up 152 days, 1:42, 109 users, load average: 2.55, 2.58, 2.40
      user@pIII:~$


      There is not reason to reboot it and to enter to windows.
    3. Re:Windows refugees by NeverVotedBush · · Score: 1

      Just curious - with load averages in the 2.xx range, are you running something like BOINC that keeps it that busy?

      And 152 days of uptime is nice. Winows folks would love to have that kind of reliability ;-)

    4. Re:Windows refugees by fbjon · · Score: 1

      In that vein, wikipedia has an article on the Linux startup process.

      --
      True confidence comes not from realising you are as good as your peers, but that your peers are as bad as you are.
    5. Re:Windows refugees by VGPowerlord · · Score: 1

      In theory, Windows could run that long, but there are too many ifs that prevent it:
      1. If no drivers crash.
      2. If there are no security updates requiring a reboot.

      There are probably more, but those two alone prevent that long an uptime. ;) Heck #2 alone does!

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    6. Re:Windows refugees by Anonymous Coward · · Score: 1, Funny

      Ouch, ouch, it hurts...

      Wikipedia in the vein is not funny, my parrot's tapeworm died that way!

    7. Re:Windows refugees by Anonymous Coward · · Score: 0

      Immigrants? More like refugees.

      If you've ever used any version of Windows, you know what I'm talking about.

    8. Re:Windows refugees by fat_mike · · Score: 1

      Either you are the author, a friend of his, or an intern at NEWESTINTERNETBASEDCOMPUTERHARDWARESOFTWAREHATEMICROSOFTLOVELINUX.com

      That article was shit. If you think that was helpful then I guess the Joy of Sex was a real eye opener for you.

    9. Re:Windows refugees by mackyrae · · Score: 1

      Wouldn't they be Windows emigrants?

      --
      look! it's a bird, it's a plane, it's....a girl? yes, a girl browsing Slashdot on Linux
    10. Re:Windows refugees by ColdWetDog · · Score: 1

      For the recent immigrants from Windows, it is a great roadmap.

      We're refugees, not immigrants, you insensitive clod. We're gonna be requesting political asylum soon.

      --
      Faster! Faster! Faster would be better!
    11. Re:Windows refugees by Cprossu · · Score: 3, Informative

      As someone who currently has a 55 day uptime on his main XP box, I shall add a few others to the list

      3. If explorer.exe doesn't crash and not unallocate it's memory (which I suppose could be taken care of by a third party shell, but most of them will end up pulling explorer up for something anyway , and a decent amount of them are unstable when run for a very long time, a way around most explorer crashes has been for me to check the little known box that will load another explorer process for every window that is needed so that when one crashes it 'possibly' won't take the rest of them out)

      4. If general memory leaks don't take a substantial amount of your physical ram. (All I can say is I've personally had the most trouble with .net framework or vb based programs thieving memory and not returning it). (yay for firefox actually giving up the gobs of ram it takes once you close it after a week)

      5. If you don't pick up any viruses on the way (and your virus protection 1. requires no reboots during updates and 2. is programmed decently well)

      although a few things will plague any OS's stability,
      for an example,

      If your UPS/battery doesn't run out of juice during a given outage. (however I suppose you could circumvent this with proper usb drivers and hibernation, but there could be a technicality as then it might not count as continuous uptime)

      or

      If a piece of critical hardware fails

      Any OS can be stable (well, I take that back, except ME) just as long as you monitor it like crazy and keep everything up..

      Although I will admit that I am spoiled by my smoothwall and it's 280 something day uptime (the silly UPS's battery died less than a year ago leaving it unpowered in an outage), although even that's nothing compared to the old fridge VAX we had at the place I worked, which had a non-rebooting uptime of 5 1/2 years, good old VMS.

    12. Re:Windows refugees by Tim+C · · Score: 1

      Winows folks would love to have that kind of reliability ;-)

      Actually, this Windows user prefers not to waste all that electricity having the computer sat switched on doing nothing while he's asleep, watching TV, out with friends, etc...

    13. Re:Windows refugees by crhylove · · Score: 2, Insightful

      Here's what would help Windows immigrants:

      An easy way to record video and post to YouTube.
      An EASIER way to make mp3s out of a CD (out of the box).
      Distros defaulting to the obvious preferable applications: Thunderbird, VLC, etc.
      Some more decent games besides Urban Terror and Emulators.
      More and Better Hardware companies supporting Linux.
      Easy and Fast Videoconferencing via speex and h.264
      Not needing to configure Grub at all.
      Also (in Ubuntu), not having an infinite list of growing kernels to choose show up in Grub.
      More improvements to Gimp and Open Office so they can actually replace Photoshop and MS Office.
      Never, Ever getting Error 22 again on boot.

      I mean, there are REAL things that Windows refugees need, and I don't think a half-ass tutorial about grub is it.

      --
      I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
    14. Re:Windows refugees by Harmonious+Botch · · Score: 1

      Thanks!

  7. RTFA before writing it! by Anonymous Coward · · Score: 0

    I read the article before it was written, as the documentation of Gentoo installation.

    Except that TFA is Redhat specific, that is.

  8. It's Web 2.0 by SignupRequired · · Score: 5, Insightful

    Ever since somebody decided "Web 2.0" existed, there's been a big slew of these awful new "IT stuff" sites that look like they've been designed using a checklist of Web 2.0 mainstays and buzzwords. User ratings? Check. Submit news? Check. Blogs? Check. Annoying multipage articles? Check. Attention whoring abuse of social bookmarking sites at the end of every article? Check. More banner ads than content on any given page? Check. User comments? Check. Half of it is actually a decade old and was pioneered by Slashdot, but thanks to the magic of buzzwords, everything old is new.

    And with all of this stuff in place, they invariably fail to even attempt the final hurdle: creating decent content. Instead of picking one of the two available routes (create good content vs Slashdot-style aggregation), they seem to like to go halfway, with awkward "stories" like this half-boiled Red Hat GRUB HOWTO masquerading as "Breaking News".

    Sure, maybe these are probably all honest people trying to kick-start their journalism careers. But if so, what the hell are they doing throwing this crap around? Even Katz was more interesting than this trash.

    1. Re:It's Web 2.0 by tehcyder · · Score: 1

      Even Katz was more interesting than this trash.
      Yes, in the sense that chewing off your own genitalia while someone pours bleach into your ears is more interesting than watching paint dry.
      --
      To have a right to do a thing is not at all the same as to be right in doing it
  9. Gory details? by Anonymous Coward · · Score: 0

    The article is getting enough hate already, so I'm not gonna add to that. Instead I'm gonna say what I'd like to see in an article: a breakdown of what loading the kernel actually means. I'd like to know exactly what happens between the boot loader doing it's thing and init firing off the runlevel scripts.

  10. An Article about init by Simon+(S2) · · Score: 2, Informative

    As sad in previous posts this Article is about init, which is about to be obsoleted by upstart (at least in ubuntu and debian, but i think others will follow). Upstart can work as a drop-in replacement for init, and has done so in Ubuntu 6.10. Here is an old but nice Article about Linux Booting, that includes init and upstart.

    --
    I just don't trust anything that bleeds for five days and doesn't die.
    1. Re:An Article about init by JackieBrown · · Score: 2, Informative

      I still am not sure that upstart will be in Debian anytime soon.

      It just seems to sit in experimental. The fact that sysvinit stays marked as required and tries to re-install itself and remove upstart doesn't help.

      Grub2, on the otherhand, has been offered for the past couple months during installation.

  11. Ubuntu's fast resume patch for grub by schwaang · · Score: 3, Interesting
    By way of making lemonade, here's a post by an Intel engineer to ubuntu-kernel-devel about a proposed grub patch that would make resuming from hibernation much faster:

    Below is the work theory of our "grub fast resume" patch
    The normal swsusp2 resume process is:
    "grub" -> "kernel" -> "initrd" -> "resume from the hibernate"
    Our "grub fast resume patch" can work as below:
    "grub" -> "resume from hibernate"

    Our "grub fast resume" patch can resume the saved hibernation image from
    grub directly that will save much time to load and run kernel and
    initrd. The patch does not change any kernel code.


    [I use hibernate on Fedora all the time, so I'd love to see a patch like this go in to Fedora's grub. Thing is, the patch is apparently based on swsusp2, and I'm not sure Fedora's kernel uses the swsusp2 version of hibernation.]

    In a reply to the post, a debian guy points out that grub is legacy at this point, and that they are looking to move to grub2.
    1. Re:Ubuntu's fast resume patch for grub by pintpusher · · Score: 2, Interesting

      That's a pretty cool little bit. It only makes sense, if the entire system is imaged onto the harddrive, why not just pull up that whole image from the bootloader and run it from there. Obviously there's more to it than just that, but still its a concept that makes sense.

      I see potential problems though if you've got changing hardware. By loading the kernel, you can reprobe the hardware (haven't watched a resume in a while to see if it actually does, but at least the mechanism is there). If you just drag in the whole image and restart execution one potentially changed hardware, that's a problem. But then I don't know whether hibernate handles changing hardware very gracefully anyway. blah blah blah rambling.

      --
      man, I feel like mold.
    2. Re:Ubuntu's fast resume patch for grub by shaiay · · Score: 1

      excellent swsusp2 for fedora is available from http://mhensler.de/swsusp/ he has a yum repository and does not lag much behind the "official" fedora kernel updates

  12. What does Grub Offer that Lilo Doesn't by fast+turtle · · Score: 1
    I'm seriously asking this question as I've tried Grub on Via KM800 boards, No Splash screen available, Intel DQ965GF (new board with SATA only) couldn't finish booting.

    So what does grub offer? The Via K?800 problem has been unresolved over the last 5 years and there's no reason not to have fixed it by now. Hell if I was repurposing old windows machines to Linux, more then likely they'd have that damn chipset.

    On the new Intel chipset, as stated grub couldn't even finish booting. Wheres the kernel couldn't see the damn SATA drive (scsi mode idiots), thus making it absolutely useless, while Lilo has worked on every x86 based system I've installed it on and this makes me wonder, why should I use something as buggy and flawed as Grub for a stupid splash screen? It's Linux idiots, we don't reboot systems every stinking time we install/upgrade software (thankyou very much MS). Hell I haven't shut my system down fo 2 weeks since the last install (Gentoo from Stage1 - GCC-4.2.0) and I'm always testing things.

    So once again, Why use something that doesn't work well on common Via K8 chipsets and can't even finish booting on a brand new Intel 965 board with only SATA installed?

    --
    Mod me up/Mod me down: I wont frown as I've no crown
    1. Re:What does Grub Offer that Lilo Doesn't by fast+turtle · · Score: 1
      Hate replying to my own posts but got to clarify a few things:

      Grub couldn't complete booting on a system with either SATA or IDE drive installed and yet it could install itself into the mbr from a running kernel

      The VIA K8 chipset problem is a known issue with the splash images that's over 5 years old and still unsolved

      So the question once again What Does Grub offer over Lilo?

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    2. Re:What does Grub Offer that Lilo Doesn't by Anonymous Coward · · Score: 0

      Go on then, what errors did you get?

    3. Re:What does Grub Offer that Lilo Doesn't by Anonymous Coward · · Score: 0

      the ability to boot windows

    4. Re:What does Grub Offer that Lilo Doesn't by Anonymous Coward · · Score: 0

      LILO will boot Windows.

    5. Re:What does Grub Offer that Lilo Doesn't by DaleGlass · · Score: 1

      Grub has a console available right from the boot menu.

      That means that as long as grub works at all, you can load and boot any kernel from any disk with a FS grub can recognize. This is really great for the cases where for example there's a typo in the configuration and the kernel's name is wrong in the file, or it's been mistakenly deleted, but there's an old kernel on the disk not listed in the config file.

      LILO, on the other hand relies on a map file that tells it where on the disk the kernel is. That means it's unable to load anything it's not been configured for, and breaks if the kernel on the disk changes but the map file isn't updated.

      These days I always install grub if possible, as it means that if something goes wrong I don't have to look for a rescue CD.

    6. Re:What does Grub Offer that Lilo Doesn't by Anonymous Coward · · Score: 0

      The Via K?800 problem has been unresolved over the last 5 years

      For something that has been "unresolved" for 5 years, there sure isn't a lot out there about whatever problem you're having. This guy apparently made it boot far enough to figure out that the KM800's keyboard controller is buggy, and gives instructions on what to have grub pass to the kernel to make the kernel not panic on it. I found similar posts ("add xxx to menu.lst to fix yyy") for KM400 as well, so it seems that K??00 isn't a problem on its own, without more information, can't help you there.

      As for Intel, I'm using grub on a DQ965GF with just sata, and it's working just fine. And it looks to be working fine for a lot of other people too. No idea what problem you're having there either.

    7. Re:What does Grub Offer that Lilo Doesn't by Hackeron · · Score: 1

      I think historically, Grub's command line was convenient to fix a non booting system without using a livecd or floppy but as I understand there isn't much you can't do with Lilo these days.

      Anyone can answer this better? - I'm no bootloader expert :)

    8. Re:What does Grub Offer that Lilo Doesn't by VGPowerlord · · Score: 2, Interesting

      I'm sure I could go into more detail by doing a little research, but in short:
      GRUB is intended to be more generic than LILO and thus runs on more OSes and platforms. The developers probably got disgusted with dealing with LILO, SILO, PALO, boot0, etc... on different machines.

      --
      GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
    9. Re:What does Grub Offer that Lilo Doesn't by fast+turtle · · Score: 1
      In the Via K8 problems with grub, you simply can't get a usable splash image/menu using grub. That's been a problem on over 100 K8 based systems I've attempted to install grub onto from HP/Dell/Gateway and over the last 7 years when I started using linux regularly.

      As to grub failing to boot on my shiny new DQ965GF with only SATA, the error there was couldn't find bootable disk and yes I'm using AHCI mode only. No IDE emulation (it's emulation after all). Grub simply couldn't find either h/sd0,0 to boot from, which made it unusable.

      On the console being offered by grub, I consider that completely useless because I can boot into single mode using Lilo and busy box in the same amount of time as the grub console and once I've fixed what ever if foobarred on the system, finish bringing it up. Otherwise, it aint booting at all. Further more, grub refuses to compile on x86_64 systems in 64bit mode as it's not x86_64 compatible - WTF??

      Nice link but notice that almost all of the systems are using the standard Intel boot mode of IDE Emulation, whereas I'm using pure AHCI, while the 2nd one down couldn't get the system to boot reliably (suggestion was to disable acpi),Third one down is Ubunta 7.04 grub reinstall failed from Live-CD. Opps your effort has backfired as the first four (although the 5th does hold promise) search results all failed with grub. Seems you have to pass the option all-generic-ide to get grub to boot, which although workable is not acceptable to me because I don't have to pass any options to Lilo other then image=/boot/bzImage, root=/dev/sda3. Label=Crash read-only.

      Simply put, on a pure SATA system, grub isn't able to successfully mount /boot in order to boot the system without some kind of screwy work-around that's not well documented as yet. The Ubunta Forum post that listed the "all-generic-ide" option was posted in Late April, almost 6 months ago meaning they should have at least documented the work around on the grub site by now.

      Now the $64,000.00 question. Are you using AHCI/Advanced mode and if so, how bout sharing a copy of your grub conf to fturtle@gmail.com with grub in the subject line? If I'm able to use your config as the base and get it working, I can post an Update to the Gentoo Docs for the board so folks can take advantage of it. Otherwise, I'll have to call "BS" on your post.

      --
      Mod me up/Mod me down: I wont frown as I've no crown
    10. Re:What does Grub Offer that Lilo Doesn't by KillerBob · · Score: 2, Insightful

      Part right, part wrong.

      LILO copies a kernel image to its boot area. It doesn't matter if you change the kernel on the hard drive, because LILO's installed image won't change until you invoke the "lilo" command. I've actually seen LILO successfully boot a kernel and initrd (which panicked) after I had formatted a drive and removed all of the partitions, because I hadn't bothered to wipe the MBR.

      With GRUB, however, it's live. If you make a change to your menu.lst file, that change will take effect immediately. And while admittedly, I don't use GRUB, I don't think there's actually a test utility that will tell you whether your menu.lst is properly configured without rebooting. Correct me if I'm wrong, as I frequently am. The recovery console is useful, but as I'm often tinkering with things, I prefer to have a bootloader that's static, and won't change until I explicitly tell it to. There's also the "lilo -v -t" command to test when I make a change to /etc/lilo.conf.

      --
      If you believe everything you read, you'd better not read. - Japanese proverb
    11. Re:What does Grub Offer that Lilo Doesn't by Anonymous Coward · · Score: 0

      Damn. I must have imagined dual booting Linux and Windows during the mid 90s then.

      My memory gets worse all the time.

    12. Re:What does Grub Offer that Lilo Doesn't by DaleGlass · · Score: 3, Informative

      LILO copies a kernel image to its boot area. It doesn't matter if you change the kernel on the hard drive, because LILO's installed image won't change until you invoke the "lilo" command. I've actually seen LILO successfully boot a kernel and initrd (which panicked) after I had formatted a drive and removed all of the partitions, because I hadn't bothered to wipe the MBR.


      No, it doesn't. You can read the LILO technical documentation if you don't believe me.

      The fundamental thing about LILO is that unlike Grub, it's incapable of actually reading the filesystem the kernel is on. The way it works is that the boot sector contains the location of the map file, and the map file contains the list of sectors that make the kernel. There's no "boot area" as such. It's trivial to verify that the map file isn't the kernel, as it's tiny (78KB on one of my boxes)

      The reason LILO booted for you is simply because a format didn't overwrite the data areas of the disk. Since LILO doesn't read the FS itself, it doesn't matter to it that all the metadata is gone. So long the boot sector is there, the map's data is there (even without metadata indicating the filename, etc), and the kernel's data is there, it'll boot.

      LILO however will completely mess up if you are unlucky. Overwriting the kernel without calling "lilo" afterwards might work if it just happens to write over the same sectors and uses the same number of them. Or maybe the new kernel is written somewhere else entirely, in which case you'll boot the old kernel and it'll break later when something reuses the space taken by the old version.

      The recovery console is useful, but as I'm often tinkering with things, I prefer to have a bootloader that's static, and won't change until I explicitly tell it to. There's also the "lilo -v -t" command to test when I make a change to /etc/lilo.conf.


      The problem with LILO is that you can screw it up without touching LILO itself. For example, delete the active kernel. It'll probably work anyway, right until something reuses the space previously taken by the kernel. Then boom, doesn't work anymore. With grub it doesn't matter if you make a bad config file, or delete a needed kernel. So long there's a kernel on disk, grub can boot it.
    13. Re:What does Grub Offer that Lilo Doesn't by JackieBrown · · Score: 2, Informative

      GRUB, unlike LILO, is able to read filesystems and recognize kernel images too

      Lilo probably overcame this a while ago but there is also problem reading beyond 1024 cylinders

    14. Re:What does Grub Offer that Lilo Doesn't by swillden · · Score: 2, Informative

      LILO copies a kernel image to its boot area.

      No, it doesn't. When you run lilo to install a kernel, it finds out which set of physical disk blocks contain the kernel image and stores the address of those blocks in the boot area. At boot time, it loads from that address. Note that if your file system were in the habit of moving files around, it might break LILO.

      I've actually seen LILO successfully boot a kernel and initrd (which panicked) after I had formatted a drive and removed all of the partitions, because I hadn't bothered to wipe the MBR.

      It didn't matter that the partitions were removed because LILO doesn't know or care about partitions. It was able to load the kernel because the disk blocks containing the kernel hadn't been overwritten.

      I don't use GRUB, I don't think there's actually a test utility that will tell you whether your menu.lst is properly configured without rebooting.

      No, I don't think there is, but that's because it's not really necessary.

      GRUB lets you edit the configuration from the bootloader, so if you happen to have messed up your menu.lst, it's no problem. Try to boot, see that it can't load the kernel, pop back to GRUB, look at the configuration you're trying to boot, tweak the config, try to boot that. Repeat until the system boots. In a worst-case scenario, you can even use the GRUB command line to explore the system, find a bootable kernel and boot it even with *no* menu.lst. This is better than LILO, because it even accommodates situations where the system may have changed. Being able to test your LILO config does no good if the config has been invalidated because disks have been swapped around, or if you forgot to update LILO after installing a kernel and removing the old one.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    15. Re:What does Grub Offer that Lilo Doesn't by Blkdeath · · Score: 1

      Lilo probably overcame this a while ago but there is also problem reading beyond 1024 cylinders

      Welcome to 2000!

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    16. Re:What does Grub Offer that Lilo Doesn't by JackieBrown · · Score: 1

      Still two years after grub supported it

    17. Re:What does Grub Offer that Lilo Doesn't by Anonymous Coward · · Score: 0

      LILO copies a kernel image to its boot area. It doesn't matter if you change the kernel on the hard drive, because LILO's installed image won't change until you invoke the "lilo" command. I've actually seen LILO successfully boot a kernel and initrd (which panicked) after I had formatted a drive and removed all of the partitions, because I hadn't bothered to wipe the MBR.

      Chances are it booted the kernel from the erased partitions, since it does not copy the kernel anywhere, but does store a list of block numbers containing the kernel image.
      Removing the partitions and formating does not involve 0-ing the whole drive, so data can survive.

      I don't think there's actually a test utility that will tell you whether your menu.lst is properly configured without rebooting.

      Precisely, it's not so much of a problem with grub, provided that you can access the display & keyboard at boot: you get a chance to fix things without extra hardware (rescue cd, unpluging the drive and put it in another computer, whatever) to boot again.
    18. Re:What does Grub Offer that Lilo Doesn't by Blkdeath · · Score: 1

      Still two years after grub supported it

      Oh YEAH? Well LILO has a bigger ... feet!

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    19. Re:What does Grub Offer that Lilo Doesn't by JackieBrown · · Score: 1

      damn!

  13. what is needed is a list Linux documentation by Anonymous Coward · · Score: 0

    Is there a credible site with up to date links to the best Linux documentation?

    Most documentation states the obvious then stops just at the point of being useful!

  14. The problem with Linux... by Anonymous Coward · · Score: 0

    ...is the users.

    Get off your ass and write an Ubuntu-specific article, then. "Many more"? Please.

  15. Sad little article by FranTaylor · · Score: 1

    There are so many ways to boot linux, all different and interesting:

    - the standard way, from the boot sector of your hard drive
    - the live-cd way, from an eltorito image on a cd-rom or dvd-rom
    - the original way, from a floppy drive
    - some machines let you boot from a zip drive
    - from a usb key, which could be any of the above under the covers
    - over the network, using pxelinux
    - out of rom

    This article has no interesting content whatsoever.

  16. Re:Rob Malda says by GiMP · · Score: 1

    This is a nerd oriented technical article.


    Huh? This is old news, and hardly technical at all -- by my standards, anyway.

    Now, whitepapers, the ACM, IEEE, RFCs, etc... those are technical.
  17. Re:Rob Malda says by Anonymous Coward · · Score: 0, Insightful

    the year of linux is past. KDE Gnome fighting ruined it.

    Modded down only because you're an AC who happened to speak absolute fact in a First Post. Sure, the absolute truth was burdened by a Dadaist personal attack against TacoMan, or whatever, but still, the groupthink here is suppressing the truth.

    Information doesn't want to be free when peer pressure is in play. Slashdot denizens are stupid sheep, cowed by the threat of metamoderation.
  18. Linux users can boast long times between reboots by Tim+Ward · · Score: 2, Insightful

    Sigh. More climate change deniers.

    Look kids, it's time to grow out of willy-waving contests about how long you can keep it up, and turn the ****ing thing off when you're not using it.

  19. Re:Linux users can boast long times between reboot by Ant+P. · · Score: 2, Interesting

    That would be a GREAT idea, if only you showed us your secret way of resuming from cold boot within 0.5 seconds when the machine recieves a tcp syn packet on port 80.

  20. what a British geeza would say by cafelatte · · Score: 1

    It's gonna first run init innit?

  21. Re:Linux users can boast long times between reboot by Anonymous Coward · · Score: 0

    My willy is never off.

    It's a curse.

  22. Re-writing the boot-record by phorm · · Score: 1

    Well, for one thing I've found it's nice just to be able to update options, etc without having to re-write over my boot-record every single time. Grub writes to the boot-record once, and - provided that you don't change the location of the config file/partition/etc - you can then just update the menu.lst file on the config partition without needing to reinstall the bootloader into the MBR with every new kernel or change.

  23. Climate Changes? Ask me if I Care by fast+turtle · · Score: 2, Insightful
    I'm not willy-waving bragging about uptimes even though I leave my system on 24/7. It's because I'm running 2x Folding at home Clients.

    As to climate change, hell yes we're suffering climate changes but are the man-made or because we've entered the 50 year increased solar activity period of the 100 year cycle? The other question is who pays for the demanded changes and will they do any damn good? The damn research has gone about finding a solution the wrong way.

    Instead of looking at how to cut energy demands by

    getting rid of all parasitic electronic loads

    and you'd be surprised how fast those parasitic loads add up. The simple example is a 5watt load that's on 24/7. That consumes 1kw every 8d:6h, meaning just under 3kw in a month. Check how much is being used by the tv/stereo/surround sound, digital clocks, cordless phones, cable box, printers and such and you'll get an idea why the average household now uses more then 7.5kw per month.

    Now go and check all of your electronics and see if they're actually off instead of in standby before you bring up global warming again.

    --
    Mod me up/Mod me down: I wont frown as I've no crown
  24. What's the point of this article?? by jaxtherat · · Score: 1

    Seriously, why do people post such crap on slashdot?? what next, a review for "bash for Dummies"? "guide to pushing a power button"?

    --
    http://www.zombieapocalypse.tv/
  25. Re:Linux users can boast long times between reboot by dbIII · · Score: 2, Insightful

    Some of us use the things for stuff like serving web pages. In that case a couple of hundred days between power cycles or reboots is a pretty short time.

  26. do it from scratch by doti · · Score: 2, Informative

    A good way to know about the boot process is to install Linux From Scratch.

    I always got annoyed about things that run on my computer that I don't know what it is, and if removing it would break anything. LFS clarified for me many dark-spots about the boot process. I even ran the installed system for almost a year, but it got harder to keep up-to-date with package versions, and I came back to using a normal distro.

    --
    factor 966971: 966971
  27. Re:Rob Malda says by dbIII · · Score: 2, Insightful

    It's technical enough to divide the Moorlocks from the complete Eloi that call the beige box on their desk a "hard drive".

  28. Re:Linux users can boast long times between reboot by Anonymous Coward · · Score: 0

    Yeah, I'll tell that to the users of my clusters that since there was no activity, I turned it off.

    I need uptime, need it bad, and linux delivers it.

    The funniest joke ever played on the human race was that electricity causes climate change. Because carbon dioxide is BAD. LOL. One of the primary components of our AIR is DESTROYING THE PLANET!!! AHHHHH!!

    The planets fine. It doesn't care how much it rains in your town.

  29. Do it yourself by WarJolt · · Score: 1

    You want to understand the linux boot process better the best way is to build yourself your own mini linux boot disk.
    All you really need is busybox(gnu tools), the c library and linux kernel. It doesn't do much, but it will help you learn how it works.
    It's a lot more interesting than reading that article.

  30. Re:Redhat specific NO IT IS NOT by Anonymous Coward · · Score: 1, Informative

    Sure it mentions a few examples that are picked from RHEL but most of the stuff is very general. Never used RHEL and had no problems perfectly understanding the article.

  31. And guess who's behind it by Anonymous Coward · · Score: 0

    Migule de Icaza!
    a courtesy of Novell Inc,
    sponsored by Microsoft.

  32. Re:Rob Malda says by somersault · · Score: 1

    And the monitor is the 'computer', heh. Ah, the mind boggles..

    Isn't Eloi Aramaic for 'father'? o_0

    --
    which is totally what she said
  33. Re:Rob Malda says by trybywrench · · Score: 1

    mod parent + grandparent up

    --
    I came to the datacenter drunk with a fake ID, don't you want to be just like me?
  34. Re:Rob Malda says by dbIII · · Score: 1

    H.G.Wells - "The Time Machine" which is set as a high school english reading text in a few places. Many disfunctional businesses divide into groups like the Eloi and Moorlocks in the novel, sometimes even after HR is employing people purely on the way they look. When the techs and the "beautiful people" can no longer communicate and actively hate each other it becomes an apt description and the company is eating itself.

  35. Re:Rob Malda says by somersault · · Score: 1

    I did see the movie many years ago (talking of the old one, not the crappy new one), have a feeling I may have read the book too.. thanks for pointing that out though because I'd completely forgotten.

    --
    which is totally what she said
  36. Mackenzie Morgan naked and petrified!!! by Anonymous Coward · · Score: 0

    Dear Beautiful Mackenzie (an Actual Girl):

    I'd like to sneak up behind you and start fondling you violently and then as you struggle to try to escape I'll take a scientifically-proven magic petrification ray from my bag and zap you with it, and it would first disintegrate all your clothing, leaving you gloriously naked, then it would start the process of transforming your body into marble, inducing in you a massive magically-induced which would be captured eternally as your body is turned into solid stone from the feet up to the head gradually, freezing your final moan of ecstasy as you become a beautiful, cold lifeless statue, but with your mind still alive inside the statue, aware of everything that happens to you. I would put you in display in art museums so that everyone could admire your spectacular naked & petrified teen body, then I would put you on a pedestal in my apartment and admire you constantly, and climb up on the pedestal and make love to your stony form, getting my penis raw & red from the friction, and covering your beautiful hard marble skin with my spooge, my beloved naked-and-petrified queen.

    (NOTE: This is just a fantasy; I would not actually do this.)

    p.s. I like masturbating to your Blogspot picture3