Re: [Cooker] AutoInstall via NFS
On Monday 16 April 2001 12:11, you wrote: David Eastcott [EMAIL PROTECTED] writes: On Monday 16 April 2001 09:15, you wrote: David Eastcott [EMAIL PROTECTED] writes: [...] Both seem to work for me. Are you sure of yourself? Could you recheck putting back the original params and checking where come the errors from? Checked my notes and the errors that was being reported was 'unable to find auto install file'. I attempted about 4 different installs before finally coming up with the changes to syslinux.cfg. So just to be sure, I spent all evening doing installs using the cooker file sets from Apr 13, then 14 (the one I thought was bad) and 15th. From each file set, I created a 2 boot disks using the network.img file. One disk contained the original syslinux.cfg and auto_inst.cfg files from the 14th, the other contained my modified syslinux.cfg Friday the 13th file set worked for both installs, Sat. 14th work for both installs, Sun 15th worked for both installs, Then I thought well may its only the generated auto install disk that was causing me the problems snice that was what I had been using on Saturday s, Using the 13th's file set, did a minimal manual install and generated an auto install disk, then used it to re-install, that worked. Repeated with the 14th's, and it worked. However, I did have a lot of trouble getting the system to boot from the floppy disk. Repeated with the 15th's and it work too. Seems I can't repeat the problem that I reported on Sat. Other than my floppy disk drive being possibly intermitent, I can't explain what happened Sat. Best regards Dave
Re: [Cooker] AutoInstall via NFS
David Eastcott [EMAIL PROTECTED] writes:
[...]
it was:
label linux
kernel vmlinuz
append kickstart=floppy
automatic=method:nfs,server:linux1,directory:/Cooker/cooker,
network:static,ip:192.168.5.202,netmask:255.255.255.0,
gateway:192.168.5.253,dns:192.168.5.253,
ramdisk_size=32000 initrd=network.rdz vga=788
Note comma after dns ip. I don't know if this was real problem or not? I
can't remember if I tried with out it or not.
it doesn't seem to be a pb, gc you confirm?
[...]
for 'mkbootdisk' you might want to force this to undef, especially for
those of us that use a floppy to kickstart things. Imagine my surprise
when the carefully crafted autoinstall disk suddenly becomes a boot disk?
what was it set to?
'mkbootdisk' = 'fd0',
ok, i switch it to off by default
[...]
When I do an autoinstall I do not want the installer to format hdc at all.
The question is: given the above declartions and this one, will it only
format hda?
'partitioning' = {
'clearall' = 1,
try
'clear' = [ 'hda' ],
i think i've added it after 7.2, and it's not documented :-/
(by the way, contributors to auto_inst doc are welcome :)
thanks, cu Pixel.
Re: [Cooker] AutoInstall via NFS
Pixel [EMAIL PROTECTED] writes: [...] append kickstart=floppy automatic=method:nfs,server:linux1,directory:/Cooker/cooker, network:static,ip:192.168.5.202,netmask:255.255.255.0, gateway:192.168.5.253,dns:192.168.5.253, ramdisk_size=32000 initrd=network.rdz vga=788 Note comma after dns ip. I don't know if this was real problem or not? I can't remember if I tried with out it or not. it doesn't seem to be a pb, gc you confirm? confirmed. trailing comma is supported and works. -- Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/
Re: [Cooker] AutoInstall via NFS
Thanks for the info. On Monday 16 April 2001 04:06, you wrote: David Eastcott [EMAIL PROTECTED] writes: [...] (by the way, contributors to auto_inst doc are welcome :) thanks, cu Pixel. Thanks for the invite. I currently have a 15-20 page text file containing explaination of various options, but it is for 7.1/7.2. I would like to update it to 8.0 first. What is best way to submit: to cooker list or you direct? (reason is because my perl is weak and it is incomplete) regards Dave
Re: [Cooker] AutoInstall via NFS
David Eastcott [EMAIL PROTECTED] writes: [...] Thanks for the invite. I currently have a 15-20 page text file containing explaination of various options, but it is for 7.1/7.2. I would like to update it to 8.0 first. What is best way to submit: to cooker list or you direct? (reason is because my perl is weak and it is incomplete) try me directly.
[Cooker] AutoInstall via NFS
Hi, Once I got things set right, works nice... Sure saves me a lot of time re-installing the same things for testing or experimenting. The syslinux.cfg that is generated during the install does not work for me. I had to change it to the following to get it work (append text is all on one line): label linux kernel vmlinuz append ramdisk_size=32000 initrd=network.rdz vga=788 kickstart=floppy automatic=method:nfs,server:linux1,directory:/Cooker/cooker, network:static,ip:192.168.5.202,netmask:255.255.255.0, gateway:192.168.5.253,dns:192.168.5.253 Couple observations: for 'superuser' the 'name' should be set to 'root', the 'pw' should be set to the md5 value generated during install (it was in 7.1 and 7.2). Probably goes for users too, but did not add a user at install time to confirm. I re-ran the autoinstall with a value from /etc/shadow for the 'pw' and the install ignored it. Until I actually used passwd as root to change, root access was available to anyone with any password. for 'mkbootdisk' you might want to force this to undef, especially for those of us that use a floppy to kickstart things. Imagine my surprise when the carefully crafted autoinstall disk suddenly becomes a boot disk? Couple questions: In the 'partitions', should the field 'hd' = 'hda' be present when you have multiple disks? Will the installer format disks other than the ones identified in 'partitions'? Can the 'configureServices' be controlled from the auto_inst.cfg file? In the expert install, I get to choose which is started, can I do it with this file too? best regards Dave
Re: [Cooker] AutoInstall via NFS
David Eastcott [EMAIL PROTECTED] writes: [...] The syslinux.cfg that is generated during the install does not work for me. I had to change it to the following to get it work (append text is all on one line): can you tell what you changed? [...] for 'superuser' the 'name' should be set to 'root', the 'pw' should be set to the md5 value generated during install (it was in 7.1 and 7.2). Probably goes for users too, but did not add a user at install time to confirm. i'll try. [...] for 'mkbootdisk' you might want to force this to undef, especially for those of us that use a floppy to kickstart things. Imagine my surprise when the carefully crafted autoinstall disk suddenly becomes a boot disk? what was it set to? [...] In the 'partitions', should the field 'hd' = 'hda' be present when you have multiple disks? Will the installer format disks other than the ones identified in 'partitions'? i don't quite understand the question. What do you have in 'partitions'? Can the 'configureServices' be controlled from the auto_inst.cfg file? In the expert install, I get to choose which is started, can I do it with this file too? you can. "services" is a list of services that will be run. You can't remove some though, only give the list of all that you want. i use: services = [ qw(syslog xfs network portmap mandrake_firstime) ], cu Pixel.
Re: [Cooker] AutoInstall via NFS
Pixel [EMAIL PROTECTED] writes: for 'superuser' the 'name' should be set to 'root', the 'pw' should be set to the md5 value generated during install (it was in 7.1 and 7.2). Probably goes for users too, but did not add a user at install time to confirm. i'll try. ok, reproduced and fixed. 'pw' is now working again thanks, Pixel.
Re: [Cooker] AutoInstall via NFS
Pixel, This AutoInstall is s nice. Thanks Dave On Sunday 15 April 2001 10:56, you wrote: Pixel [EMAIL PROTECTED] writes: for 'superuser' the 'name' should be set to 'root', the 'pw' should be set to the md5 value generated during install (it was in 7.1 and 7.2). Probably goes for users too, but did not add a user at install time to confirm. i'll try. ok, reproduced and fixed. 'pw' is now working again thanks, Pixel.
Re: [Cooker] AutoInstall via NFS
On Sunday 15 April 2001 10:43, you wrote:
David Eastcott [EMAIL PROTECTED] writes:
[...]
The syslinux.cfg that is generated during the install does not work for
me. I had to change it to the following to get it work (append text is
all on one line):
can you tell what you changed?
it was:
label linux
kernel vmlinuz
append kickstart=floppy
automatic=method:nfs,server:linux1,directory:/Cooker/cooker,
network:static,ip:192.168.5.202,netmask:255.255.255.0,
gateway:192.168.5.253,dns:192.168.5.253,
ramdisk_size=32000 initrd=network.rdz vga=788
Note comma after dns ip. I don't know if this was real problem or not? I
can't remember if I tried with out it or not.
[...]
for 'mkbootdisk' you might want to force this to undef, especially for
those of us that use a floppy to kickstart things. Imagine my surprise
when the carefully crafted autoinstall disk suddenly becomes a boot disk?
what was it set to?
'mkbootdisk' = 'fd0',
[...]
In the 'partitions', should the field 'hd' = 'hda' be present when you
have multiple disks? Will the installer format disks other than the
ones identified in 'partitions'?
i don't quite understand the question. What do you have in 'partitions'?
I have two disks, hda and hdc. The first disk is partitioned as follows:
'partitions' = [
{
'mntpoint' = '/boot',
'size' = 80292,
'type' = 387
},
{
'mntpoint' = 'swap',
'size' = 497952,
'type' = 130
},
{
'mntpoint' = '/',
'size' = 15502662,
'type' = 387
}
],
and is used to hold all normal files. The second (hdc) is an archive disk
which gets mounted in the root directory (/mass) as follows:
'manualFstab' = [
{
'device' = '/dev/hdc1',
'mntpoint' = '/mass',
'options' = 'default',
'type' = 'reiserfs'
}
],
When I do an autoinstall I do not want the installer to format hdc at all.
The question is: given the above declartions and this one, will it only
format hda?
'partitioning' = {
'clearall' = 1,
'eraseBadPartitions' = 0,
'auto_allocate' = 1
},
regards
Dave
