From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Andreas Deresch <aderesch@fs.tum.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] vmlinux header for savecrash.
Date: Thu, 24 Jan 2002 23:30:54 -0700 [thread overview]
Message-ID: <20020125063054.C4281482A@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Andreas Deresch <aderesch@fs.tum.de> of "Wed, 23 Jan 2002 11:23:26 +0100." <Pine.NEB.4.33.0201231118490.942-100000@ganymed.fachschaften.tu-muenchen.de>
Andreas Deresch wrote:
> > Isn't /vmlinux a symlink to /boot/vmlinux?
> > ie the file palo loaded is whatever the symlink points to.
> Can you guarantee, that everybody will have this link?
Of course not. I'm refering to a default installation.
I delete that link and replace /etc/palo.conf with my own.
But I'm hardly a "regular" user.
> (I for example don't right now - I always thought, this is just for
> historical reasons)
> > BTW, I explicitly specify /boot/vmlinux in my palo.conf files
> > and see 3/boot/vmlinux in my palo command line.
> Which means, /boot is not a separate partition as some people like to keep
> it. So you can't count on that either.
Right. I like to have lots of room for kernels. :^)
And if one wanted to have / as an ext3, it would make
sense to have /boot as an ext2 for loading kernels and then
the / could be the rest of the disk (ignoring the 2GB
IODC limitation).
grant
next prev parent reply other threads:[~2002-01-25 6:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 2:58 [parisc-linux] installation problems on an A500 Matthias Klose
2002-01-07 3:46 ` Grant Grundler
2002-01-07 5:28 ` Matthias Klose
2002-01-22 19:59 ` [parisc-linux] vmlinux header for savecrash Paul Bame
2002-01-23 2:13 ` Grant Grundler
2002-01-23 10:23 ` Andreas Deresch
2002-01-25 6:30 ` Grant Grundler [this message]
2002-01-23 8:57 ` Enrik Berkhan
2002-01-23 9:29 ` phi 4369
-- strict thread matches above, loose matches on Subject: below --
2002-01-21 17:45 Bruno Vidal
2002-01-21 20:25 ` Grant Grundler
2002-01-22 9:20 ` Bruno Vidal
2002-01-22 9:55 ` Enrik Berkhan
2002-01-22 12:25 ` Bruno Vidal
2002-01-22 15:11 ` Enrik Berkhan
2002-01-22 15:13 ` Matthew Wilcox
2002-01-22 12:05 ` James P. Kinney III
2002-01-22 17:45 ` Grant Grundler
2002-01-22 17:53 ` Randolph Chung
2002-01-22 17:59 ` Bruno Vidal
2002-01-22 17:55 ` Bruno Vidal
2002-01-22 18:11 ` Randolph Chung
2002-01-22 18:34 ` Grant Grundler
2002-01-22 0:43 ` James P. Kinney III
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020125063054.C4281482A@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=aderesch@fs.tum.de \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox