Package: partman
Severity: wishlist
mipsel/cobalt and arm/netwinder need an ext2 -r 0 -O none boot
partition (so you can either have a separate boot partition as ext2 r0
and a root with ext3, or the root containing boot has to be ext2 r0).
In the case of mipsel/cobalt, the following restrictions apply:
- the boot partition _must_ be the 1st (primary) partition
- the root partition must be a primary partition (not a logical one)
- the boot partition (if separate from root) should be about
5 (min) to 25 (max) MB.
In the case of arm/netwinder:
- the boot partition can be anywhere.
- it should be about 10-25 MB.
partconf-auto also need special recieps for this. Thanks.
----- Forwarded message from Martin Michlmayr <[EMAIL PROTECTED]> -----
From: Martin Michlmayr <[EMAIL PROTECTED]>
Subject: Question about custom boot partitions
Date: Mon, 12 Apr 2004 17:02:45 +0100
To: [EMAIL PROTECTED]
Cc: Anton Zinoviev <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.5.1+cvs20040105i
There are at least 2 sub-architectures which need a special ext2
partition to boot. That is, not just an ext2 file system, but an ext2
file system of revision 0 with no extensions (mkfs.ext2 -r 0 -O none).
Now I wonder how to implement this in partman. As I see it, there are
3 options:
1. Change the ext2 type to always be revision 0, and then write some
finish.d scripts which check that boot (or root if there's no
separate boot) is of ext2.
2. In addition to having a ext2 type, also have a "traditional ext2"
type or so, and create finish.d scripts.
3. Followg partman-palo or -newworld and create, say, a "Cobalt boot
partition" (for Cobalt machines). The problem is that 2
different sub-arches need ext2 -r 0 as boot (MIPS Cobalt, and ARM
Netwinder), so we'd have 2 virtually identical packages. (There
would be some differences, though. Cobalt requires the boot
partition to be the _first_ partition while Netwinder doesn't care.)
What's the best approach?
--
Martin Michlmayr
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----- End forwarded message -----
----- Forwarded message from Anton Zinoviev <[EMAIL PROTECTED]> -----
From: Anton Zinoviev <[EMAIL PROTECTED]>
Subject: Re: Question about custom boot partitions
Date: Fri, 16 Apr 2004 12:18:44 +0300
To: [EMAIL PROTECTED]
User-Agent: Mutt/1.3.28i
On 15.IV.2004 at 23:21 (+0100) Martin Michlmayr wrote:
> * tbm <[EMAIL PROTECTED]> [2004-04-12 17:02]:
> > There are at least 2 sub-architectures which need a special ext2
> > partition to boot. That is, not just an ext2 file system, but an ext2
> > file system of revision 0 with no extensions (mkfs.ext2 -r 0 -O none).
> > Now I wonder how to implement this in partman. As I see it, there are
> > 3 options:
I think the best for the users is the following:
1. partman warns the user if /boot is not on ext2 file system
2. partman automatically uses mkfs.ext2 -r 0 -O none for the bootable
partition and the default for the other partitions.
Regarding the implementation, if you want to do something for beta4 (I
won't be able) do it the easiest for you way. If you don't plan this
for beta4, then I will implement it.
Anton Zinoviev
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----- End forwarded message -----
--
Martin Michlmayr
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
