From: technologypages@yahoo.com
To: grub-devel@gnu.org
Subject: Re: mkfs command in grub
Date: Mon, 13 Mar 2006 15:54:07 +0200 [thread overview]
Message-ID: <4415797F.7000808@yahoo.com> (raw)
Tomáš, unfortunately your solution to the swap sharing problem is
suboptimal -- swapping through filesystem code to a file in a VFAT
filesystem will quite likely be a order of magnitude slower than raw
partition access. It's OK if you are a casual Linux user, but not
acceptable if you are a casual Windows user like me :).
Okuji, it's a matter of theoretical purism vs pragmatical problem
solving. As Marco already said, we can't change the behaviour of
non-free software. Hence we need to manipulate the swap partition before
booting Windows in this particular (and very common) use-case. Preparing
the swap partition for Windows is possible from a Linux shutdown script,
but this solution is fragile (one can imagine plenty of cases when the
script will not be run), and is not really Linux's responsibility
(preparing a partition for another OS). Which brings us back to the fact
that in this particular case it is the bootloader's responsibility. I
agree that this functionality should not be part of the core, but as
GRUB 2 is supposedly modular (haven't seen the code though), it should
be available as a module.
Could someone who knows the code please envisage what should be done in
order to implement the mkfs module?
next reply other threads:[~2006-03-13 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 13:54 technologypages [this message]
2006-03-28 16:04 ` mkfs command in grub Marco Gerards
-- strict thread matches above, loose matches on Subject: below --
2006-03-09 19:14 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
2006-03-12 0:03 ` Tomáš Ebenlendr
2006-03-12 22:28 ` Yoshinori K. Okuji
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=4415797F.7000808@yahoo.com \
--to=technologypages@yahoo.com \
--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.