I'm testing my latest -current build (from 9.99.64, sources about a week
old now), on an amd64 Xen domU.
I'm having trouble getting the "new" sysinst, when using extended
partitioning, to set the "newfs" flag (and the "-o log" flag).
I can set it, but it never sticks and never happens, which means nothing
gets mounted.
Here's the partitions screen once I've set things as I want them:
This is the extended partition manager. All disks, partitions, etc. are
listed below. To use RAID, LVM, or CGD: 1) Create partitions with the
appropriate type; 2) Create RAID/LVM VG/CGD using these partitions; 3) Save
changes; 4) Create partitions for RAID/CGD or Logical Volumes for LVM.
a: xbd0 (6.0G) USED
b: xbd0a on / (FFSv2) (unused) 6144M
c: xbd1 (4.0G) USED
d: xbd1b (swap) 4096M
e: xbd2 (2.0G) USED
f: xbd2a on /var (FFSv2) (unused) 2048M
g: xbd3 (20G) USED
h: xbd3a on /usr/pkg (FFSv2) (unused) 20G
i: Create cryptographic volume (CGD)
j: Create virtual disk image (VND)
k: Create volume group (LVM VG)
l: Create software RAID
m: Update device list
n: Save changes
>x: Finish partitioning
Note how each actual partition still says "unused"!
Note I'm using LVM volumes as whole filesystem partitions, so I just
want to make one big filesystem on each (except for swap, of course --
it just needs to have the right "type" field value).
Here's an example of editing the partitions for xbd0:
This is the extended partition manager. All disks, partitions, etc. are
listed below. ┌────────────────────────────────────────────────────────────┐
appropriate ty│ The current values for this partition are │
changes; 4) Cr│ displayed below. │
│ │
a: xbd0 (6.0G)│ Select the field you wish to change: │
>b: xbd0a on│ │
c: xbd1 (4.0G)│>a: type : FFSv2 │
d: xbd1b (s│ b: start : 0 MB │
e: xbd2 (2.0G)│ c: size : 6144 MB │
f: xbd2a on│ d: end : 6144 MB │
g: xbd3 (20G) │ e: install : Yes │
h: xbd3a on│ f: newfs : No │
i: Create cryp│ g: mount : Yes │
j: Create virt│ h: mount options : │
k: Create volu│ i: mount point : / │
l: Create soft│ j: Change input units (sectors/cylinders/MB/GB) │
m: Update devi│ k: Restore original values │
n: Save change│ l: Delete partition │
x: Finish part│ m: Cancel │
│ x: OK │
└────────────────────────────────────────────────────────────┘
No matter how many times I try to turn on the "newfs" flag or set mount
options, nothing sticks and it always looks as above again if I exit the
partition editor and then go back.
When I select the whole disk (e.g. the "a:" choice above) I never see
the 'N' flag set:
We now have your disklabel partitions for xbd0 below. This is your last
chance to change them.
Flags: (I)nstall, (N)ewfs. Total size: 6144M, free: 0B
Start (MB) End (MB) Size (MB) FS type Flag Filesystem
------------ ------------ ------------ -------- ---- ----------------
a: 0 6143 6144 FFSv2 I /
b: 0 6143 6144 Whole disk
------------ ------------ ------------ -------- ---- ----------------
d: Change input units (sectors/cylinders/MB/GB)
e: Edit name of the disk
f: Clone external partition(s)
g: Cancel
>x: Partition sizes ok
I can set the 'N' flag by editing the partition, but it just disappears
again next time I go back to the partition.
Obviously once the extraction starts it immediately fails because
there's nothing mounted on /targetroot (and the root filesystem is
read-only).
I'm not even sure why it didn't decide these volumes were new and empty
and in need of newfs in the first place, since they are -- they had no
labels at all to begin with.
What magic am I missing, or is this a bug?
It would be nice if there were some way to see the internal
partitioning configuration in sysinst (i.e. what it "saves" when one
chooses "Save changes").
It would also be really handy to have an option in the utility menu that
will actually "run" all the partitioning, including newfs, etc., and do
all the mounts so that one can then go into a shell and see all the
mounted filesystems on /targetroot to see if they're OK (and to edit the
installed system after extraction and config as well).
(Also, as an aside, this extended partitioning tool, while wonderfully
flexible, is a bit obtuse and complex to use -- one thing that tripped
me up initially was getting confused between the menu choice letters and
the partition label letters that I was hoping/expecting to see, though
once I actually noticed the "b" on "xbd1b" for the swap partition I
realised it was doing the right thing. It would also be nice if a
default partitioning scheme could be chosen for all disks. It takes an
awful lot of fiddley keystrokes to get to what I show above, and that's
without even having to change the sizes or anything fancy.)
(Totally unrelated to partitioning, it would be nice if the "get release
sets" action happened _before_ first asking what sets to install and
then that the default selected sets would never include ones that are
not available (though selecting an unavailable one could still work and
ask you separately where to get it from instead) and a "full
installation" would just try to install all of the sets that were found
to be available from the chosen source.)
--
Greg A. Woods <gwoods%acm.org@localhost>
Kelowna, BC +1 250 762-7675 RoboHack <woods%robohack.ca@localhost>
Planix, Inc. <woods%planix.com@localhost> Avoncote Farms <woods%avoncote.ca@localhost>
Attachment:
pgpQyish7Pvyt.pgp
Description: OpenPGP Digital Signature