On Sat, 15 Apr 2000, you wrote:
> Andrew George wrote:
>
> >
>
> [snipped]
>
> May have already been answered, but in case it hasn't ...
>
> > >
> > Heres a related question
> > The following is part of my partition table
> > Device Mount Point Distribution
> > /hdb5 /bo
Andrew George wrote:
>
[snipped]
May have already been answered, but in case it hasn't ...
> >
> Heres a related question
> The following is part of my partition table
> Device Mount Point Distribution
> /hdb5 /boot Debian
> /hdb6 / Debi
Mike Corbeil wrote:
> However, in following the general guideline, I make /boot a separate filesystem or
> partition, and do this regardless of the filesystem being above or below the 1024
> limit. The reason for this generalized approach is merely to make sure that there's
> more flexibility for
> You're perfectly right: lilo only needs to find the kernel image,
> and you could often, in theory, put that anywhere as long as you
> specify it correctly in lilo.conf
>
> However, the /boot directory is part of the File System Standard (FSS)
> in linux, and this standard has been elaborated
Jean-Louis Debert wrote:
> Mike Corbeil wrote:
> > 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
> > config
On 14/04/00 0:06, Alan Shoemaker [EMAIL PROTECTED] is reported to have said:
>Kirkyour designations of boot1, boot2etc. Do partitions
>exist with those namesnot!? Ok, do me a favor. You say
>Caldera is running, so go into a console in Caldera and type
>fdisk /dev/hda then do a p
Mike Corbeil wrote:
> 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 ker
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 th
Alan Shoemaker wrote:
> Kirkyour designations of boot1, boot2etc. Do partitions
> exist with those namesnot!? Ok, do me a favor. You say
> Caldera is running, so go into a console in Caldera and type
> fdisk /dev/hda then do a p command and capture the results and
> post them. Ok?
Kirkyour designations of boot1, boot2etc. Do partitions
exist with those namesnot!? Ok, do me a favor. You say
Caldera is running, so go into a console in Caldera and type
fdisk /dev/hda then do a p command and capture the results and
post them. Ok?
Alan
Kirk McElhearn wrote:
>
> Caldera was the only one I could fully install. It started up, but
> there was no option during the install to create a boot disk ...
Hmmm... that sounds suspiciously like a bug. They really didn't give you
the option to create a boot floppy?
> Then I tried Corel Linux. This was an instant
11 matches
Mail list logo
