Actually, I guess that the boot directory doesn't need to be named /boot, as long as the correct path is specified in the boot configuration. This may be incorrect; however, the reason I say this is because linuxconf lilo boot configuration requires the name of the kernel image file as well as the directory path, at least when linuxconf isn't run in or from the /boot directory, or the directory the kernel image(s) are located in. Otherwise, if /boot is strictly required, then I don't know why linuxconf would require for the directory to be specified. Is there are slight inconsistency or discrepancy in this sense, or is there a valid technical reason I'm not aware of? Anyone know? mike
- [expert] Follow-up - Multiple Linux systems on one hard... Kirk McElhearn
- Re: [expert] Follow-up - Multiple Linux systems on... Matt Stegman
- Re: [expert] Follow-up - Multiple Linux systems on... Alan Shoemaker
- [expert] Sound Problms witn 7.0_2 Eosnet Team
- Re: [expert] Sound Problms witn 7.0_2 Jonathan Oppenheim
- Re: [expert] Sound Problms witn 7.0_2 Larry Sword
- Re: [expert] Sound Problms witn 7.0_2 Eosnet
- Re: [expert] Sound Problms witn 7... Larry Sword
- Re: [expert] Follow-up - Multiple Linux system... Mike Corbeil
- Re: [expert] Follow-up - Multiple Linux system... Mike Corbeil
- Re: [expert] Follow-up - Multiple Linux sy... Jean-Louis Debert
- Re: [expert] Follow-up - Multiple Linu... Mike Corbeil
- Re: [expert] Follow-up - Multiple... Jean-Louis Debert
- Re: [expert] Follow-up - Multiple Linu... Andrew George
- Re: [expert] Follow-up - Multiple... Mike Corbeil
- Re: [expert] Follow-up - Mult... Andrew George
- [expert] How to make hd.img installation see s... Mike Corbeil
- Re: [expert] Follow-up - Multiple Linux systems on... Kirk McElhearn
