Re: Bug in Boot-Disk Package?
[EMAIL PROTECTED] (Goswin Brederlow) wrote on 21.06.97 in [EMAIL PROTECTED]: The script should eigther reboot after the disk holding root is partitioned or try to remount root r/w. Rebooting is a bit anoying when you only changed the type of another partition from DOS\0 to LNX\0, whereas remounting might get stuck if the partition holding root has changed name or place. So rebooting is probably the savest. It's not only getting stuck. It's that the kernel doesn't know what you have done to the partition table. You do something to the drive with the new partition table in mind, and the kernel interprets your actions based on the old partition table. It might lead to you creating a new file system where you think is a spare partition, but instead hitting your valuable data from which you have no backup, because the kernel counts partitions different from you. Going on without reboot is really dangerous. Only people who thoroughly understand the issues involved should try it. Much, much better just to reboot. On the other hand, repartitioning a drive with no mounted partitions is completely harmless; the kernel will just reread the partition table and go ahead. MfG Kai -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Bug in Boot-Disk Package?
I found a bug in the installation procedure on my Amiga, but the same will probably happen on all systems. When I try to partition the drive my root.bin is on during installation, it pops up a requester asking to unmount / before starting fdisk on it. After quitting fdisk it remounts /, but the installation routines complain about / being read-only and nothing works anymore. To reproduce this behavior on another system you need a spare partition at least the size of the root.bin (e.g. the swap partition). Dump the root.bin onto it and boot with it as root. Select the keyboard and then fdisk it (be carefull not to change anything that might erase youre data). Just quiting it again should do the trick. Before fdisk is started the installation routine will complain about the root mounted from that drive and unmount it. After fdisk it will remount it and you have the above bug. Can somebody second this on another system or is it just my Amiga? May the Source be with you. Mrvn. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bug in Boot-Disk Package?
Yes, it would do that. The problem is that un-mounting / leaves it mounted read-only, not unmounted. You can't unmount root. If it remounts it at all, it doesn't do it correctly, and re-partitioning the disk that root is running on is problematical, to say the least. On the PC installation floppy root would be a RAM disk at this point, and this problem would never come up. I wonder if your boot parameters are wrong, or if it is a 68k-specific issue. Thanks Bruce From: Goswin Brederlow [EMAIL PROTECTED] I found a bug in the installation procedure on my Amiga, but the same will probably happen on all systems. When I try to partition the drive my root.bin is on during installation, it pops up a requester asking to unmount / before starting fdisk on it. After quitting fdisk it remounts /, but the installation routines complain about / being read-only and nothing works anymore. To reproduce this behavior on another system you need a spare partition at least the size of the root.bin (e.g. the swap partition). Dump the root.bin onto it and boot with it as root. Select the keyboard and then fdisk it (be carefull not to change anything that might erase youre data). Just quiting it again should do the trick. Before fdisk is started the installation routine will complain about the root mounted from that drive and unmount it. After fdisk it will remount it and you have the above bug. Can somebody second this on another system or is it just my Amiga? May the Source be with you. Mrvn. -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bug in Boot-Disk Package?
OK, it's unmounted then, but it should remount the drive if its untouched or ask if it should remount it. I'm not repartitioning the drive, but I had to change the types of the partitions, cause I can't do it easily from AmigaOS (I dunno the hex for LNX\0). The partition holding root is unchanged so remounting it would be harmless. The reason why I did use a partition to hold root.bin was that I tried to install Debian with only 4 MB. With only 4 MB ram you don't have enough space the kernel and a ramdisk, so I used a spare partition for it. It works fine, except from the reboot I had to make to get root remounted again. Bruce Perens wrote: Yes, it would do that. The problem is that un-mounting / leaves it mounted read-only, not unmounted. You can't unmount root. If it remounts it at all, it doesn't do it correctly, and re-partitioning the disk that root is running on is problematical, to say the least. On the PC installation floppy root would be a RAM disk at this point, and this problem would never come up. I wonder if your boot parameters are wrong, or if it is a 68k-specific issue. Thanks Bruce From: Goswin Brederlow [EMAIL PROTECTED] I found a bug in the installation procedure on my Amiga, but the same will probably happen on all systems. When I try to partition the drive my root.bin is on during installation, it pops up a requester asking to unmount / before starting fdisk on it. After quitting fdisk it remounts /, but the installation routines complain about / being read-only and nothing works anymore. To reproduce this behavior on another system you need a spare partition at least the size of the root.bin (e.g. the swap partition). Dump the root.bin onto it and boot with it as root. Select the keyboard and then fdisk it (be carefull not to change anything that might erase youre data). Just quiting it again should do the trick. Before fdisk is started the installation routine will complain about the root mounted from that drive and unmount it. After fdisk it will remount it and you have the above bug. Can somebody second this on another system or is it just my Amiga? May the Source be with you. Mrvn. -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bug in Boot-Disk Package?
From: Goswin Brederlow [EMAIL PROTECTED] OK, it's unmounted then, but it should remount the drive if its untouched or ask if it should remount it. I'm not repartitioning the drive, but I had to change the types of the partitions I think it should not unmount the root, but it should complain before you partition a disk that the root is running on. I don't know how many people will hit this. Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bug in Boot-Disk Package?
[EMAIL PROTECTED] (Goswin Brederlow) wrote on 21.06.97 in [EMAIL PROTECTED]: OK, it's unmounted then, but it should remount the drive if its untouched or ask if it should remount it. I'm not repartitioning the drive, but I had to change the types of the partitions, cause I can't do it easily from AmigaOS (I dunno the hex for LNX\0). The partition holding root is unchanged so remounting it would be harmless. Of course, it can't know that. In general, the kernel cannot reread the partition table when it has mounted something from that drive, even read-only, so the only proper choice after changing the partition table is to reboot. You can re-mount the partition (mount -o remount,rw /), but the kernel will not know about any changes you made, which can be very dangerous. The boot disks should probably force a reboot at that point. The reason why I did use a partition to hold root.bin was that I tried to install Debian with only 4 MB. With only 4 MB ram you don't have enough space the kernel and a ramdisk, so I used a spare partition for it. It works fine, except from the reboot I had to make to get root remounted again. The low memory boot disk probably does the same thing on the x86. MfG Kai -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bug in Boot-Disk Package?
Bruce Perens wrote: From: Goswin Brederlow [EMAIL PROTECTED] OK, it's unmounted then, but it should remount the drive if its untouched or ask if it should remount it. I'm not repartitioning the drive, but I had to change the types of the partitions I think it should not unmount the root, but it should complain before you partition a disk that the root is running on. I don't know how many people will hit this. Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 It's the only choise if you have a low mem system. As Kai Henning pointed out: The boot disks should probably force a reboot at that point. The low memory boot disk probably does the same thing on the x86. The script complains that you have mounted filesystems on that drive when you try to partition it, which is perfectly valid. The script should eigther reboot after the disk holding root is partitioned or try to remount root r/w. Rebooting is a bit anoying when you only changed the type of another partition from DOS\0 to LNX\0, whereas remounting might get stuck if the partition holding root has changed name or place. So rebooting is probably the savest. May the source be with you. Mrvn -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Bug in Boot-Disk Package?
Kai Henningsen wrote: [EMAIL PROTECTED] (Goswin Brederlow) wrote on 21.06.97 in [EMAIL PROTECTED]: OK, it's unmounted then, but it should remount the drive if its untouched or ask if it should remount it. I'm not repartitioning the drive, but I had to change the types of the partitions, cause I can't do it easily from AmigaOS (I dunno the hex for LNX\0). The partition holding root is unchanged so remounting it would be harmless. Of course, it can't know that. In general, the kernel cannot reread the partition table when it has mounted something from that drive, even read-only, so the only proper choice after changing the partition table is to reboot. You can re-mount the partition (mount -o remount,rw /), but the kernel will not know about any changes you made, which can be very dangerous. You can't remount because the install script goes into an endless loop evaluating you're system, failing and poping up with the colour/monochrom menu. You can't even reboot. The only option is a keyboard reset, which thankfully makes a shutdown -r when Ctrl-Amiga-Amiga is pressed. (It just resets on CTRL-Alt-Del. Why?) The boot disks should probably force a reboot at that point. That's probably the best option. The low memory boot disk probably does the same thing on the x86. MfG Kai May the Source be with you. Mrvn -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
