probably a dumb question, but ...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  ... i was poking around inside the boot floppy, and reading the
syslinux docs, and i just want to make sure i understand the layout
of the syslinux.cfg file to continue learning about kickstart (and
to better understand forrest taylor's missive on fixing the loader,
etc).

  the salient part of the syslinux.cfg file:

...
default linux
...
label linux
  kernel vmlinuz
  append initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788
...
label ks
  kernel vmlinuz
  append ks initrd=initrd.img lang= devfs=nomount ramdisk_size=7168
...


according to the docs, if you type the name of a label, the info for
that label is used to determine which kernel to boot and which options
get passed to the kernel.  fair enough.

note that, in the standard boot.img floppy image that comes with 
red hat 7.2, there is a "linux" label *and* a "ks" label.  i've
always thought that, to do a net-based kickstart install, i had
to type:

  boot: linux ks

but from the above, it looks as if i could just type:

  boot: ks

since that will invoke the other label line.  the only effective
difference is that one way of doing it will add a "vga=788" option, and
the other won't.  am i reading this correctly?  granted, it's not
a big deal, i'm just curious.  and, of course, if i got ambitious,
i could add extra stanzas to that file and cut myself a custom boot
floppy.

rday

p.s.  as i see it, if i wanted to do any variation of a kickstart
install that required me to type "linux ks=<something>", there is
no alternative for *that*.  but "linux ks" can, as it appears,
be abbreviated just as "ks" at the boot prompt, right?





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux