From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Guidance on conflicts between GNU GRUB and proprietary software
Date: Tue, 28 Sep 2010 16:07:00 -0400 [thread overview]
Message-ID: <20100928200700.GV8579@caffeine.csclub.uwaterloo.ca> (raw)
In-Reply-To: <4CA2455D.2070105@gmail.com>
On Tue, Sep 28, 2010 at 09:43:25PM +0200, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> GPT has new types.
GPT has an msdos partition type for itself for use in hybrid setups.
I know GPT partition tables have new types, but GPT itself has a type
reserved in the old dos partition table.
> in msdos there are only 255 possible types. Some are known to be used by
> well known software but during 10 years of no central body for this and
> everybody willing a type just taking one in self-service I think every
> single type is used by either widely known or mostly unknown software.
> And destroying someone's hobby OS would be a bad thing.
And not having a reliable grub on actual used OSs isn't a bad thing?
Someone's hobby OS could change if it was an issue.
> GRUB has a design principle of being cross-platform installable.
> Moreover the same disk can contain multiple grub installation. I
> personally regularly move the disk between yeeloong and amd64 laptop,
> well it has only one GRUB since on yeeloong my GRUB is in flash but it
> could easily have one on disk too.
If two architectures expect sector 0 to contain boot code, then that
can't work. I certainly would not consider that a worthy design goal
compared to lots of other things.
--
Len Sorensen
next prev parent reply other threads:[~2010-09-28 20:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 22:19 Guidance on conflicts between GNU GRUB and proprietary software Colin Watson
2010-09-24 0:27 ` Lennart Sorensen
2010-09-24 14:09 ` Richard Stallman
2010-09-28 4:44 ` richardvoigt
2010-09-28 4:55 ` Bogdan
2010-09-28 8:04 ` Colin Watson
2010-09-28 9:10 ` Bogdan
2010-09-28 9:41 ` Colin Watson
2010-09-28 9:51 ` Bogdan
2010-09-28 10:25 ` Colin Watson
2010-09-28 10:40 ` Bogdan
2010-09-28 11:49 ` Colin Watson
2010-09-28 14:50 ` Lennart Sorensen
2010-09-28 15:05 ` Bogdan
2010-09-28 18:18 ` Grub2 Install Image Dee Sharpe
2010-09-28 21:45 ` Dmitry Ilyin
2010-09-28 15:40 ` Guidance on conflicts between GNU GRUB and proprietary software Phillip Susi
2010-09-28 16:18 ` Colin Watson
2010-09-28 17:52 ` Phillip Susi
2010-09-28 19:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 19:15 ` Lennart Sorensen
2010-09-28 19:43 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 20:07 ` Lennart Sorensen [this message]
2010-09-28 20:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 21:15 ` Lennart Sorensen
2010-09-28 21:34 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 19:22 ` Phillip Susi
2010-09-28 21:46 ` Grégoire Sutre
2010-09-28 22:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-29 10:00 ` Grégoire Sutre
2010-09-28 19:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-28 14:57 ` Lennart Sorensen
2010-09-28 9:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-09-24 10:57 ` Brendan Trotter
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=20100928200700.GV8579@caffeine.csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--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 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).