Does someone have an example mkisofs command with arguments to create a CD from the files on the CentOS CD?
Since we are building servers, all the data is on CentOS4 CD1. I plan to modify it to include a kickstart file and remove some of the things on there that I don't need.
I use something like this on the Cobalt Networks servers, need mods to work on CentOS. (following on one line)
mkisofs -P Name -b boot/elterito.img -c boot/boot.catalog -R -I -L -o path-to-iso/name.iso .
Now I am sure the boot references need to change.
TIA for help ;) Gerald
Gerald Waugh wrote:
Does someone have an example mkisofs command with arguments to create a CD from the files on the CentOS CD?
Check "Creating CentOS DVD from scratch" thread from few days ago. It has complete command line. You'd also might want to "lie" a bit to Anaconda, and say in .discinfo file that media contains all four CDs.
On Tue, 2005-04-12 at 09:03 -0500, Aleksandar Milivojevic wrote:
Gerald Waugh wrote:
Does someone have an example mkisofs command with arguments to create a CD from the files on the CentOS CD?
Check "Creating CentOS DVD from scratch" thread from few days ago. It has complete command line. You'd also might want to "lie" a bit to Anaconda, and say in .discinfo file that media contains all four CDs.
I made a CD with the ks.cfg included, but I get.... "isolinux: image checksum error, sorry... Boot failed: press a key to retry..."
Any clue why this might happen?
Gerald
On Tue, 2005-04-12 at 16:19 -0400, Gerald Waugh wrote:
On Tue, 2005-04-12 at 09:03 -0500, Aleksandar Milivojevic wrote:
Gerald Waugh wrote:
Does someone have an example mkisofs command with arguments to create a CD from the files on the CentOS CD?
Check "Creating CentOS DVD from scratch" thread from few days ago. It has complete command line. You'd also might want to "lie" a bit to Anaconda, and say in .discinfo file that media contains all four CDs.
I made a CD with the ks.cfg included, but I get.... "isolinux: image checksum error, sorry... Boot failed: press a key to retry..."
OK, my error, ran a bad mkisofs command line. Now I have ks.cfg on the top level of the CD, and the CD boots...
So testing continues.... I am not sure if I have to enter a command at the boot prompt or should this thing just run.
Please excuse all the dumb questions,.
Gerald
Gerald Waugh wrote:
So testing continues.... I am not sure if I have to enter a command at the boot prompt or should this thing just run.
No, it is not going to run all by itself. If you wan't it to run all by itself, you'd need to change couple more things. Check this article from Linux Journal for some ideas:
http://www.linuxjournal.com/article/6473
The article is rather old, and describes things for RH8. You may want to check newer kickstart/anaconda documentation too...
On Wed, 2005-04-13 at 08:28 -0500, Aleksandar Milivojevic wrote:
Gerald Waugh wrote:
So testing continues.... I am not sure if I have to enter a command at the boot prompt or should this thing just run.
No, it is not going to run all by itself. If you wan't it to run all by itself, you'd need to change couple more things. Check this article from Linux Journal for some ideas:
http://www.linuxjournal.com/article/6473
The article is rather old, and describes things for RH8. You may want to check newer kickstart/anaconda documentation too...
I have it running, "linux ks=cdrom" from an IDE cdrom, but need to get it running on a USB cdrom, as the servers do not normally have IDE cdrom.
I have searched for a method to get it to load the "USB Mass Storage Driver for Linux" during the install. I know it's on the cdrom, just have trouble locating it. Also I believe I have to enter something like linux ks=cdrom dd=<usb-mass-storage-driver>
Gerald
On Wed, 2005-04-13 at 09:54 -0400, Gerald Waugh wrote:
I have it running, "linux ks=cdrom" from an IDE cdrom, but need to get it running on a USB cdrom, as the servers do not normally have IDE cdrom.
I have searched for a method to get it to load the "USB Mass Storage Driver for Linux" during the install. I know it's on the cdrom, just have trouble locating it. Also I believe I have to enter something like linux ks=cdrom dd=<usb-mass-storage-driver>
I guess it's in the kernel. So need to edit isolinux.cfg and add to the last line "append - " (something) maybe "usb-scsi" ???
Gerald
Gerald Waugh wrote:
I have it running, "linux ks=cdrom" from an IDE cdrom, but need to get it running on a USB cdrom, as the servers do not normally have IDE cdrom.
Oh, I thought what you wanted was to have kickstart be default, without you having to type "ks=cdrom" or anything...
I have searched for a method to get it to load the "USB Mass Storage Driver for Linux" during the install. I know it's on the cdrom, just have trouble locating it. Also I believe I have to enter something like linux ks=cdrom dd=<usb-mass-storage-driver>
When booting form USB sticks, I was simply using "linux ks=hd:sdN:/ks.cfg" or something similar (with N being whatever was assigned by kernel to the stick, usually "0" if there were no SCSI/SATA devices in the system)... I believe that Anaconda is supposed to load USB device drivers before attempting to access kickstart file. You might check this link for various options on telling Anaconda where the kickstart file is:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/s...
On Wed, 2005-04-13 at 11:38 -0500, Aleksandar Milivojevic wrote:
When booting form USB sticks, I was simply using "linux ks=hd:sdN:/ks.cfg" or something similar (with N being whatever was assigned by kernel to the stick, usually "0" if there were no SCSI/SATA devices in the system)... I believe that Anaconda is supposed to load USB device drivers before attempting to access kickstart file. You might check this link for various options on telling Anaconda where the kickstart file is:
Thanks for your help (Patience) Well, it is weird, the server boots up off the usb cdrom but somehow just before anaconda loads the drive is disconnected. Now there is a little delay at "anaconda loading" if I pull the usb cdrom plug and reinsert it during that interval anaconda loads a usb driver and my ks.cfg runs.
The same thing happens in a text install when I select "Load from cdrom" it ask for a driver, I select usb-storage, and it can't find the usb cdrom, again if I pull the plug and reinsert it, it will find it. Maybe the usb cdrom I am using (TDK).
I still have that issue with the RAID1 (md0) not booting though. I read your article about that issue, tried it but could not get it to work, and you recommended using lilo, but there is no option to use lilo in the install.
Gerald
On Wed, 2005-04-13 at 23:34 -0400, Gerald Waugh wrote:
On Wed, 2005-04-13 at 11:38 -0500, Aleksandar Milivojevic wrote:
When booting form USB sticks, I was simply using "linux ks=hd:sdN:/ks.cfg" or something similar (with N being whatever was assigned by kernel to the stick, usually "0" if there were no SCSI/SATA devices in the system)... I believe that Anaconda is supposed to load USB device drivers before attempting to access kickstart file. You might check this link for various options on telling Anaconda where the kickstart file is:
Thanks for your help (Patience) Well, it is weird, the server boots up off the usb cdrom but somehow just before anaconda loads the drive is disconnected. Now there is a little delay at "anaconda loading" if I pull the usb cdrom plug and reinsert it during that interval anaconda loads a usb driver and my ks.cfg runs.
The same thing happens in a text install when I select "Load from cdrom" it ask for a driver, I select usb-storage, and it can't find the usb cdrom, again if I pull the plug and reinsert it, it will find it. Maybe the usb cdrom I am using (TDK).
I still have that issue with the RAID1 (md0) not booting though. I read your article about that issue, tried it but could not get it to work, and you recommended using lilo, but there is no option to use lilo in the install.
Oops! We also use Turbo Linux Appliance Server OS on these servers, their CD works and I did find "lilo --location mbr" in their ks.cfg so I guess that answers my question about lilo.... maybe ;)
Gerald
Gerald Waugh wrote:
Oops! We also use Turbo Linux Appliance Server OS on these servers, their CD works and I did find "lilo --location mbr" in their ks.cfg so I guess that answers my question about lilo.... maybe ;)
Not exactly... On newer Red Hats (Fedora Core, Enterprise), the option to use in ks.cfg is "bootloader --location=mbr --useLilo".
Hello Gerald,
I've thought about that approach, but found it easier to use the stock CD1 and simply put the rest of the CD's on an http server within the network. Basically, the CDROM is only a boot disk. The command to get the kickstart file is linux ks=http://192.168.0.99/anaconda.cfg
On Tue, 2005-04-12 at 07:51 -0700, Mickael Maddison wrote:
I've thought about that approach, but found it easier to use the stock CD1 and simply put the rest of the CD's on an http server within the network. Basically, the CDROM is only a boot disk. The command to get the kickstart file is linux ks=http://192.168.0.99/anaconda.cfg
That sounds like a reasonable approach. What does anaconda.cfg look like is that the actual ks file? Although all the files we need are on CD1.
Gerald
Hello Gerald,
Mine usually look something like this: # kickstart.cfg install url --url http://192.168.0.99/CentOS lang en_US.UTF-8 langsupport --default en_US.UTF-8 en_US.UTF-8 keyboard us #mouse generic3usb --device input/mice mouse none skipx network --device=eth0 --bootproto=static --ip=192.168.1.182 --hostname foo.com --netmask=255.255.255.0 --gateway=192.168.0.1 --nameserver=192.168.1.2 rootpw --iscrypted $1$24SzvzTC$0hasdfhw923n3tST235$. firewall --medium --port smtp:tcp --port http:tcp --port ftp:tcp --port ssh:tcp --port 110:tcp authconfig --enableshadow --enablemd5 timezone America/Vancouver zerombr yes bootloader --location=mbr
# The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --all --initlabel part /boot --fstype ext2 --size=250 --ondisk=hda --asprimary part /var --fstype ext2 --size=20000 --ondisk=hdc --asprimary part /usr --fstype ext3 --size=10000 --ondisk=hda part / --fstype ext3 --size=20000 --ondisk=hda part /tmp --fstype ext2 --size=1024 --ondisk=hda part /downloads --fstype ext3 --size=11112 part /d3 --fstype ext2 --size=10000 --grow --ondisk=hda part /d4 --fstype ext2 --size=10000 --grow --ondisk=hdc part /bk4 --fstype ext3 --size=10000 --grow --ondisk=hda part /bk3 --fstype ext3 --size=10000 --grow --ondisk=hdc part swap --size=1024 --ondisk=hdc part swap --size=1024 --ondisk=hda
#SATA DRIVES part /d1 --fstype ext2 --size=25000 --grow --ondisk=sda --asprimary part /d2 --fstype ext2 --size=25000 --grow --ondisk=sdb --asprimary part /bk2 --fstype ext3 --size=25000 --grow --ondisk=sda part /bk1 --fstype ext3 --size=25000 --grow --ondisk=sdb
%packages @ compat-arch-support -psgml -kernel-pcmcia-cs -emacs-leim kernel-smp -Canna-libs kernel -Canna grub -nedit -emacs -Wnn6-SDK-devel -emacs-el -Wnn6-SDK -FreeWnn-common -FreeWnn -emacspeak -gpm -portmap -nfs-utils -cups -xinetd gcc-c++ gcc-java gcc-g77 gcc-objc libjpeg libjpeg-devel gd-devel gd libpng libpng-devel ncurses-devel libgcj libgcj-devel libf2c libstdc++-devel flex m4 curl freetype freetype-devel
%post
Mickael Maddison wrote:
Hello Gerald,
I've thought about that approach, but found it easier to use the stock CD1 and simply put the rest of the CD's on an http server within the network. Basically, the CDROM is only a boot disk. The command to get the kickstart file is linux ks=http://192.168.0.99/anaconda.cfg
What I usually do is place ks.cfg on a floppy or USB stick and then do "linux ks=floppy". That way I can use standard installation CD, and Anaconda does not prompt me for network parameters (they are part of ks.cfg). Another solution would be to completely boot from the network.
BTW, it would be nice feature if distribution contained separate rescue and boot CD images in iso directory. Like those in Fedora Core 3. That way folks that install directly from mirrors would need to download only ~80 meg (rescue CD) if they want to be able to boot into rescue mode when something goes wrong, instead of having to download ~650 megs (the first CD). Boot CD is already present for those that know where to find it (in unpacked files under "os" tree), but something tells me you can't boot into rescue mode with it.
On Tue, 2005-04-12 at 11:04 -0500, Aleksandar Milivojevic wrote:
Mickael Maddison wrote:
Hello Gerald,
I've thought about that approach, but found it easier to use the stock CD1 and simply put the rest of the CD's on an http server within the network. Basically, the CDROM is only a boot disk. The command to get the kickstart file is linux ks=http://192.168.0.99/anaconda.cfg
What I usually do is place ks.cfg on a floppy or USB stick and then do "linux ks=floppy". That way I can use standard installation CD, and Anaconda does not prompt me for network parameters (they are part of ks.cfg). Another solution would be to completely boot from the network.
BTW, it would be nice feature if distribution contained separate rescue and boot CD images in iso directory. Like those in Fedora Core 3. That way folks that install directly from mirrors would need to download only ~80 meg (rescue CD) if they want to be able to boot into rescue mode when something goes wrong, instead of having to download ~650 megs (the first CD). Boot CD is already present for those that know where to find it (in unpacked files under "os" tree), but something tells me you can't boot into rescue mode with it.
There is a boot.iso that is the CentOS distribution it is in the images directory. See, for example, boot.iso in
http://centos.cs.ucr.edu/centos/centos/4.0/os/i386/images/
Sean
Sean O'Connell wrote:
On Tue, 2005-04-12 at 11:04 -0500, Aleksandar Milivojevic wrote:
Boot CD is already present for those that know where to find it (in unpacked files under "os" tree), but something tells me you can't boot into rescue mode with it.
There is a boot.iso that is the CentOS distribution it is in the images directory. See, for example, boot.iso in
Yes, I know there is. See the part just above your reply. I even wrote where to look for it ;-)
I was only suggesting making a copy/symlink to it from iso directory, and creating a separate rescue CD image, like the one that exists in Fedora Core 3 (~75 MB).
On Tue, 2005-04-12 at 11:47 -0500, Aleksandar Milivojevic wrote:
Sean O'Connell wrote:
On Tue, 2005-04-12 at 11:04 -0500, Aleksandar Milivojevic wrote:
Boot CD is already present for those that know where to find it (in unpacked files under "os" tree), but something tells me you can't boot into rescue mode with it.
There is a boot.iso that is the CentOS distribution it is in the images directory. See, for example, boot.iso in
Yes, I know there is. See the part just above your reply. I even wrote where to look for it ;-)
I was only suggesting making a copy/symlink to it from iso directory, and creating a separate rescue CD image, like the one that exists in Fedora Core 3 (~75 MB).
Yes. I saw it about 1/2 second after I hit send :) I suppose I am not awake yet. Also, I figured there was no point in spamming the list with an apology (unless you responded).
Sean
-
Aleksandar Milivojevic -
Gerald Waugh -
Mickael Maddison -
Sean O'Connell