Hi,
I used Debian for a little bit more than a year and now i installed fedora and i am really happy with this distribution. I have a few fedora specific questions.


Why i can't boot from a stock kernel with root=LABEL=/ in grub.conf and fstab. I get a kernel panic, where the kernel cant mount "/".

In Debian there is the config called /etc/modules. There are modules defined which are loaded at boot time. How is this handled in fedora?

What does modules.conf modprobe.conf and modprobe.conf.dist do anyway in Fedora?

For what is the boot parameter rhgb?

Why are the paths /sbin and /usr/sbin not exported in a x-terminal?


Thank you in advance!
Baltasar

I wish I could answer you about the root=LABEL=/ thing. I had immense troubles with grub and those lines, trying to do a custom kernel with Fedora.
As far as I could tell, (hint, I didn't put much time into it.. Just went back to Slack where things just always work they way they're supposed to) it read the root label from fstab (somehow, without mounting root first? Confusing to me.)

Not sure about module autoloading, although I'd suspect it's within /etc/init.d/init.modules or somesuch within. Red Hat's boot scripts make me dizzy.

rhgb boot parameter is for the "Red Hat Graphical Boot) It's that pretty splash screen you get that shows either a progress bar, or details of the boot process.

And as far as paths getting exported, you'll want to look at whether you've got a .bashrc or .bash_profile in your home folder. Do you mean when you do an "su" you don't get /sbin or /usr/sbin in your path? When you use "su" in Fedora, you are simply getting root priveleges -- not another login shell with root's settings. You're retaining the environment variables of your user's login, and hence the same path as your user.
Use "su -" to create a root login shell which will incluide */sbin in the path variable.

Bash, by default, doesn't export environment variables to child shells/scripts. (Something not entirely related, but good to keep in mind when workin within xterms and Xwindows. Won't necessarily have all the same variables as your text console.)

Hope some of this helps, as it's late and I've been working all day.
I'm also no Red Hat or Fedora expert. Just fiddled around with it for a while after I'd heard some good reviews.

--Shade

first thank you for your answer.
you were wright as you wrote that I meant the "su" stuff. i thought it is for security reason or something
the root=LABEL=/ thing makes me crazy. i think it has to do with the initrd ramdisk and/or devlabel imho.
i have most modules compiled in the kernel, so i actually do not need a ramdisk( or should i use a ramdisk? - let me know ) i can boot the kernel when i change root=LABEL=/ in the fstab to /dev/hdx. but i would really want to know what is a) the advantage of a label and b) how can i set up a custom kernel which will boot with this option.
and what i also need to know is where the config for the module autoloading is?
i hope some experts can help me

regards
Baltasar

thanks.
i hope this helps too