From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: mkfs command in grub
Date: Sat, 11 Mar 2006 21:46:10 +0100 [thread overview]
Message-ID: <87hd64u2ul.fsf@xs4all.nl> (raw)
In-Reply-To: <200603112028.59600.okuji@enbug.org> (Yoshinori K. Okuji's message of "Sat, 11 Mar 2006 20:28:59 +0000")
"Yoshinori K. Okuji" <okuji@enbug.org> writes:
>> The main reason for this feature request was that swap space can be
>> shared between windows and GNU/Linux this way. So you can make a fat
>> filesystem when booting windows and a swap filesystem when booting
>> GNU/Linux. Although this is not something really important for us, I
>> do see the use of such feature.
>
> So? Why does a boot loader have to deal with that? Is a swap partition
> creation critical for booting? Why don't you just make a swap partition in
> the boot process of each operation system and activate it? I really don't see
> this as a task for a boot loader.
Heh, now I am defending a feature I don't really want, need or care
about myself. It's just that the idea is not that bad, not that I
want it or so.
The problem of the person who proposed this, is that he can not change
some of his operating systems. Which of course is a problem of
non-free software.
--
Marco
next prev parent reply other threads:[~2006-03-11 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 19:14 mkfs command in grub technologypages
2006-03-10 21:44 ` Marco Gerards
2006-03-11 9:10 ` Vesa Jääskeläinen
2006-03-11 11:08 ` Yoshinori K. Okuji
2006-03-11 14:37 ` Marco Gerards
2006-03-11 20:28 ` Yoshinori K. Okuji
2006-03-11 20:46 ` Marco Gerards [this message]
2006-03-12 0:03 ` Tomáš Ebenlendr
2006-03-12 22:28 ` Yoshinori K. Okuji
-- strict thread matches above, loose matches on Subject: below --
2006-03-13 13:54 technologypages
2006-03-28 16:04 ` Marco Gerards
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=87hd64u2ul.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.