debian-policy@lists.debian.org
Bcc: [EMAIL PROTECTED]
Subject: Re: Multi-level symlinks for default kernel
Reply-To:
In-Reply-To: <[EMAIL PROTECTED]>
On Fri, Jul 25, 2003 at 01:17:27AM -0500, Manoj Srivastava wrote:
> Hi,
> On Tue, 22 Jul 2003 16:29:59 -0700, Mike Fedyk <[EMAIL P
Hi,
On Tue, 22 Jul 2003 16:29:59 -0700, Mike Fedyk <[EMAIL PROTECTED]> said:
> Hi, I am wondering if anyone else is having the same problems I am
> with debian keeping the vmlinuz symlink in /.
> I have several systems where /boot is the only filesystem accessable
> by the boot loader because of
On Tue, Jul 22, 2003 at 07:48:33PM -0400, Morgon Kanter wrote:
> > I am wondering if anyone else is having the same problems I am with debian
> > keeping the vmlinuz symlink in /.
> >
> > I have several systems where /boot is the only filesystem accessable by the
> > boot loader because of softwar
On Tue, Jul 22, 2003 at 07:48:33PM -0400, Morgon Kanter wrote:
> > I am wondering if anyone else is having the same problems I am with debian
> > keeping the vmlinuz symlink in /.
> >
> > I have several systems where /boot is the only filesystem accessable by the
> > boot loader because of softwar
> I am wondering if anyone else is having the same problems I am with debian
> keeping the vmlinuz symlink in /.
>
> I have several systems where /boot is the only filesystem accessable by the
> boot loader because of software raid, or possibly lvm (haven't done this
> yet, but thinking about it).
Hi,
I am wondering if anyone else is having the same problems I am with debian
keeping the vmlinuz symlink in /.
I have several systems where /boot is the only filesystem accessable by the
boot loader because of software raid, or possibly lvm (haven't done this
yet, but thinking about it).
I reg
6 matches
Mail list logo
