Hi, I hope I won't be boring...
I would need some help about tomsrtbt-bootcd I'm trying to understand what Tom did... Le Jeudi 25 Septembre 2003 22:17, Tom Oehser a �crit : > I have never productionized the script that makes the CD, I think > some others have worked on that and maybe what they did can be > found in the wikiwiki or the mailing list archive, the canonical > script (that is, what I use) will need to be customized, but, for > the record, here it is: > > Before doing anything: - You boot tomsrtbt2.0.103 - Run "./unpack.s" from /bin - Customize... - And then the lines you send me to build iso image? Am I right? Probably not: I did it and get error writing /etc/mtab.tmp: No space left on device I've got it: I run it from a linux partition mounted in /rb and it is OK. Why "./unpack.s"? Many questions are coming... ... I apologize... What does this line mean? > . 1/settings.s Execute ./1/settings.s? And this one: > echo $NM-$VE.$PL I did it and get (I'm running Tomsrtbt2.0.103): -. Oho! From: /rb/tomsrtbt-2.0.103.unpacked/1# vi settings.s I see NM and VE variables not empty. Why don't I get anything? No VE variable on my floppy in settings.s but NM is "tomsrtbt". What is /rb? Is it the directory where you unpack...? > export topdir=/rb/$NM-$VE.$PL.ElTorito > mkdir $topdir When I do # mount I get: /dev/ram0 on / type minix (rw) none on /proc type proc (rw) /dev/ram3 on /tmp type minix (rw) I can understand the first line. But why the second one? > umount /dev/ram0 2>/dev/null > umount /mnt/ram0 2>/dev/null Maybe because you run many times this script without rebooting so you need to unmount /mnt/ram0,... (mounted a few lines after) Nothing about /dev/ram1 for me... > umount /dev/ram1 2>/dev/null > umount /mnt/ram1 2>/dev/null What do you mount in /fl? > umount /fl 2>/dev/null Nothing about /dev/ram2 for me... > umount /dev/ram2 2>/dev/null Now you are creating ramdrive... > dd if=/dev/zero of=/dev/ram0 bs=1k count=2880 2>/dev/null > dd if=/dev/zero of=/dev/ram1 bs=1k count=4096 2>/dev/null and "formating" it: > mkfs.minix /dev/ram0 2880 > /dev/null > mkfs.minix /dev/ram1 4096 > /dev/null OK for these lines: > mount /dev/ram0 /mnt/ram0 > mount /dev/ram1 /mnt/ram1 You start populating ramdives: > cp -af /rb/1/* /mnt/ram0 Does it mean that you rename tomsrtbt-2.0.103.unpacked to rb? > cp -af /rb/1/settings.s /mnt/ram1 > cp -af /rb/1/rc.custom.gz /mnt/ram1 > mkdir /mnt/ram0/dev > cp -af /rb/2/dev/ram* /mnt/ram0/dev > cp -af /rb/2/* /mnt/ram1 > cp -af /rb/license.html /mnt/ram1 > mv /mnt/ram1/etc/rc.S /mnt/ram1/etc/rc.S_ > cat > /mnt/ram1/etc/rc.S <<! > #!/bin/sh > PATH=/bin > BT=1 > mount -o remount / > mount -a > . /settings.s > update & > cp /rc.* /*.s /bin > gzip -d /bin/*.gz > . /bin/rc.custom > ! > chmod ugo+rx /mnt/ram1/etc/rc.S > umount /mnt/ram1 > dd if=/dev/ram1 bs=1k count=4096 | bzip2 -9 > /mnt/ram0/initrd.bz2 2>/dev/null > rm /mnt/ram0/map > lilo -r /mnt/ram0 -C - <<! > boot=/dev/ram0 > disk=/dev/ram0 > bios=0x00 > sectors=36 > heads=2 > cylinders=80 > install=/boot.b > message=/settings.s > backup=/dev/null > map=/map > timeout=150 > read-write > vga=ask > prompt > image=/bz2bzImage > root=/dev/ram0 > initrd=/initrd.bz2 > append="parport=0x378,7" > ! > #mkdir /mnt/ram0/add-ons > #cp -af /rb/add-ons/part1/* /mnt/ram0/add-ons > umount /mnt/ram0 > dd if=/dev/ram0 bs=1k count=2880 | bzip2 -9 > /var/httpd/htdocs/pair$topdir.288.img.bz2 I'll need to change M5 to where I mounted my partition: > cd /M5/rb Why is it /M5/rb? It was /rb a few lines before... I did a test (see other mail): I couldn't go up to root. root was /rb/tomsrtbt-2.0.103.unpacked for me during the test. cd / didn't change anything. > dd if=/dev/ram0 bs=1k count=2880 of=/M5/rb/tomsrtbt.288.img > mkisofs -b tomsrtbt.288.img -c boot.catalog -o tomsrtbt.iso 1 2 add* tomsrtbt.288.img > cp /M5/rb/tomsrtbt.iso /var/httpd/htdocs/pair/rb > cd /var/httpd/htdocs/pair/rb > chmod ugo+rx * Thank you very much. -- Stephane. > On Thu, 25 Sep 2003, Stephane Boireau wrote: > > > Date: Thu, 25 Sep 2003 16:00:52 +0200 > > From: Stephane Boireau <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: [tomsrtbt] Modify tomsrtbt-bootcd? > > > > Hi, > > > > If I want to change some things in tomsrtbt-bootcd, how can I proceed? > > > > - mount with -o loop option > > - copy to a directory > > - make changes > > - and then, what do I have to do to rebuid the image? > > > > Thank you very much. > > -- > > Stephane Boireau > > Personne ressource TICE du coll�ge Le Hameau � Bernay (27) > > > > -- Stephane Boireau Personne ressource TICE du coll�ge Le Hameau � Bernay (27)
