From: Goffredo Baroncelli <kreijack@libero.it>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kreijack@inwind.it, cwillu <cwillu@cwillu.com>,
helmut@hullen.de, linux-btrfs@vger.kernel.org
Subject: Re: R: Re: Subvolumes and /proc/self/mountinfo
Date: Thu, 21 Jun 2012 07:47:34 +0200 [thread overview]
Message-ID: <4FE2B576.3030301@libero.it> (raw)
In-Reply-To: <4FE2455E.2090007@zytor.com>
On 06/20/2012 11:49 PM, H. Peter Anvin wrote:
> On 06/20/2012 11:06 AM, Goffredo Baroncelli wrote:
>>
>> Am not saying that we *should* move the kernel away from /boot. I am
>> only saying that having the kernel near /lib/modules *has* some advantages.
>>
>> Few year ago there are some gains to have a separate /boot (ah, the time
>> when the bios were unable to address the bigger disk), where there are
>> the minimum things to bootstrap the system.
>>
>
> There still is (in fact this exact problem has made a comeback, as there
> are plenty of BIOSes which have bugs above the 2 TB mark); however,
> there are also issues with RAID (firmware often cannot address all the
> devices in the system -- and no, that isn't ancient history, I have a
> system exactly like that that I bought last year), remote boot media
> (your / might be on an iSCSI device, or even a network filesystem!) and
> all kinds of situations like that.
>
> The bottom line is that /boot is what the bootloader needs to be able to
> address, whereas / can wait until the kernel has device drivers. That
> is a *HUGE* difference
This leads to have a separately /boot filesystem. In this case I agree
with you: make sense that the kernel is near the bootloader files.
But if /boot has to be in a separate filesystem, which is the point to
support btrfs at all ? Does make sense to support only a subset of btrfs
features ?
>
>> Now we have the possibility to move the kernel near the modules, and
>> this could lead some interesting possibility: think about different
>> linux installations, with an own kernel version and an own modules
>> version; what are the reasons to put together under /boot different
>> kernel which potential conflicting names ? de facto standard ?
>> historical reasons ? Nothing wrong here; but also the idea to moving the
>> kernel under /lib/modules is not so wrong.
>
> No, it is completely, totally and very very seriously wrong.
When a bootloader (and the bioses) will be able to address the whole
diskS, this will change.. Not now
>
> -hpa
>
next prev parent reply other threads:[~2012-06-21 5:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 12:02 R: Re: Subvolumes and /proc/self/mountinfo Goffredo Baroncelli <kreijack@libero.it>
2012-06-20 15:37 ` H. Peter Anvin
2012-06-20 16:34 ` Goffredo Baroncelli
2012-06-20 17:41 ` H. Peter Anvin
2012-06-20 18:06 ` Goffredo Baroncelli
2012-06-20 19:15 ` Helmut Hullen
2012-06-20 20:22 ` Goffredo Baroncelli
2012-06-20 21:49 ` H. Peter Anvin
2012-06-21 5:47 ` Goffredo Baroncelli [this message]
2012-06-21 11:46 ` Martin Steigerwald
2012-06-21 17:05 ` Goffredo Baroncelli
2012-06-21 13:38 ` H. Peter Anvin
2012-06-21 17:05 ` Goffredo Baroncelli
2012-06-21 17:11 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2012-06-20 12:10 Goffredo Baroncelli <kreijack@libero.it>
2012-06-20 11:51 Goffredo Baroncelli <kreijack@libero.it>
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=4FE2B576.3030301@libero.it \
--to=kreijack@libero.it \
--cc=cwillu@cwillu.com \
--cc=helmut@hullen.de \
--cc=hpa@zytor.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).