On Sunday 19 March 2006 10:01, Grant Grundler wrote: > Sorry - didn't have a chance to check that. > Is the log automatically preserved? Saved in /var/log/installer/... on the installed system. > > Yes, if you did not set up /boot in the PALO partition during the > > install, that is very likely as the kernel is installed after the > > rest of the base system. We could probably add a check for the max > > physical position of the partition that has /boot in palo-installer > > (in a finish.d hook for partman). > > > > Care to file a bugreport about that? > > TBH, I don't considered it a bug unless it happens with > a default install. Well, partitioning manually is an option in a default install. Automatic partitioning is just for convenience. In a lot of cases users will want a different partition layout and thus need manual partitioning. > It would be nice if the default install were smart enough to > use sda1 as /boot _always_. > That would completely avoid the issue of needing a check. I think the reason in that partman is not really smart enough at the moment to format a partition type other than 83 as ext2. I'm not really sure of the details, but it will need some partman rewriting. I agree it would make partitioning more logical. > > Device Boot Start End Blocks Id System > > /dev/sda1 1 4 32098+ 83 Linux > > /dev/sda2 5 20 128520 83 Linux > > /dev/sda3 21 1106 8723295 5 Extended > > /dev/sda5 * 21 338 2554303+ 83 Linux > > /dev/sda6 339 369 248976 82 Linux swap > > /dev/sda7 370 1106 5919921 83 Linux > > This works?!! > Shouldn't sda1 be the palo partition? (Id == f0) > I would expect palo command to complain that it can't find the palo > partition. Yeah, there is something weird there. I have 3 disks in my system and when I install to a second disk, the type of the PALO partition on the first disk will be changed; I have needed to change it back once. It does boot fine ATM, but there is definitely a bug there.
Attachment:
pgptJIBMZvTOj.pgp
Description: PGP signature