From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: /boot or not /boot (was Re: [gentoo-user] can't stop the panic on eeepc)
Date: Sat, 09 May 2009 18:58:16 -0500 [thread overview]
Message-ID: <4A061898.70405@gmail.com> (raw)
In-Reply-To: <20090510003417.4bea3925@zaphod.digimed.co.uk>
Neil Bothwick wrote:
> On Sat, 09 May 2009 08:15:09 -0500, Dale wrote:
>
>
>> I was talking about with just a plain file system. I read in a install
>> guide somewhere when I was installing ages ago that having /boot on a
>> separate partition, and not always mounted, was a good security
>> practice. That way no one could alter the kernel since it was not
>> mounted.
>>
>
> That's a bit of a red herring IMO. If anyone can alter your kernel they
> can mount the filesystem. The argument about protecting the kernel from
> corruption is similarly spurious, since you always have a spare copy
> in /usr/src/linux anyway. The main reason for doing this was because some
> BIOSes could work past cylinder 1024 of a drive, so you needed to ensure
> the kernel was on a filesystem fully within that area.
>
> If it were a security issue, then the Gentoo handbook would have
> recommended this practice for all architectures, not just x86-based ones.
>
>
>
That was my thoughts as well. You have to be root to get to the kernel
and alter/copy it and if you are root, you can mount it anyway. No real
point.
I do get the old BIOSes tho. That was a issue for a good while.
Dale
:-) :-)
next prev parent reply other threads:[~2009-05-09 23:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 19:51 [gentoo-user] can't stop the panic on eeepc maxim wexler
2009-05-06 20:15 ` Daniel da Veiga
2009-05-06 20:41 ` Masood Ahmed
2009-05-07 16:37 ` Dirk Heinrichs
2009-05-07 16:48 ` Saphirus Sage
2009-05-07 16:52 ` Dirk Heinrichs
2009-05-07 19:37 ` Alan McKinnon
2009-05-07 20:46 ` Dirk Heinrichs
2009-05-07 20:53 ` Alan McKinnon
2009-05-07 21:00 ` Volker Armin Hemmann
2009-05-07 21:16 ` Alan McKinnon
2009-05-07 21:34 ` Neil Bothwick
2009-05-07 21:42 ` Alan McKinnon
2009-05-08 17:04 ` Dirk Heinrichs
2009-05-08 17:17 ` Daniel da Veiga
2009-05-08 20:58 ` Dirk Heinrichs
2009-05-08 21:12 ` Neil Bothwick
2009-05-08 21:23 ` Dirk Heinrichs
2009-05-09 10:20 ` Stroller
2009-05-09 12:41 ` /boot or not /boot (was Re: [gentoo-user] can't stop the panic on eeepc) Dirk Heinrichs
2009-05-09 12:46 ` Dale
2009-05-09 12:54 ` Dirk Heinrichs
2009-05-09 13:15 ` Dale
2009-05-09 23:34 ` Neil Bothwick
2009-05-09 23:58 ` Dale [this message]
2009-05-10 6:48 ` Francesco Talamona
2009-05-10 7:50 ` Dale
2009-05-09 13:13 ` Stroller
2009-05-09 13:23 ` [gentoo-user] Re: /boot or not /boot Dirk Heinrichs
2009-05-09 15:23 ` /boot or not /boot (was Re: [gentoo-user] can't stop the panic on eeepc) Alan McKinnon
2009-05-10 12:24 ` Stroller
2009-05-11 17:09 ` [gentoo-user] Re: /boot or not /boot Dirk Heinrichs
2009-05-07 16:35 ` [gentoo-user] can't stop the panic on eeepc Dirk Heinrichs
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=4A061898.70405@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.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