Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]): > * 2) The partman problem > During the first process install you are prompted to make partitions on > your disk(s). The only problem (but it is a big one) is that it is > nowhere said that you should press the "F12" key to edit the fields you > can see. > > I wanted to make a 4 GB partition for Windows as hda1 (for an eventually > future install), then a /dev/hda2 (1GB) for Linux swap and /dev/hda3 (6 > GB) for OpenBSD and hda4 extented and full of hda5 to hda14 partitions > for my new Linux/Debian/Sarge OS. > > The problem is that you have to strike the "F12" to modify the fields of > partman, but it is not said anywhere. I found this out by striking all > the keys of the keyboard in a «aléatoire» way which is not a good idea > in a partition program ! > > (Sorry I don't know how to translate «aléatoire», it means I stroke > all keys on the keyboard and finally (finlandly ? (it's ajoke: have a > smile)) found out "F12" makes something).
randomly This is the very first time I ever hear about this F12 key doing something in partman. This is probably the reason which explains why it is not documented..:-) I have no partman with me currently but the usual way of editing partitions from the main partman screen is by moving on entries and hitting Enter..:-) > Always include in /etc/lilo.conf (or in grup machin/bidule (I don't know > anything about grub)) the boot options the user passed to boot on the > first CD. > > Please had an help-screen in partman so the user knows about this > f*****g "F12" key to edit the fields. > > The shell you provide with the first-part installation processe is too > minimal (and no /target at the horizon). It depends on the step you are in. /target is mounted after partman did its job. The shell is minimal because there are size constraints. Up to now, it has proven functional enough for doing what's needed (mostly strange stuff for strange situations...). The only suggestion that may be examined here is adding the boot options to the boot loader command line. But I'm pretty sure there are very good reasons for not doing so...for instance because most of the passed options are often meant to pass parameters to the install system and thus are only relevant for the install system.
