Re: New disklable doesn't keep old partitions if requested
On Mon, 6 Jul 2009 14:40:32 +0200 Tor Houghton t...@bogus.net wrote: On Mon, Jul 06, 2009 at 04:15:51AM +, Miod Vallat wrote: This whole thread is actually one more proof that nobody ever reads the installation notes (INSTALL.*). Miod Oooh, you've just identified a space-saving measure! *ducks* It also proves I'm stupid enough to read to the end only to know if anything useful was said b4 I nuke this drivel. Dhu
Re: New disklable doesn't keep old partitions if requested
On Mon, Jul 06, 2009 at 04:15:51AM +, Miod Vallat wrote: This whole thread is actually one more proof that nobody ever reads the installation notes (INSTALL.*). Miod Oooh, you've just identified a space-saving measure! *ducks*
New disklable doesn't keep old partitions if requested
Hi, I try to keep the actual partition of the disk as it was before and do a fresh install, but the snapshots looks like simply do not allow this now. You can select Custom label and it will show the previous label, but then when you write it, obviously no changes are present, but when you Quit it, it comes back to the same question and looks like you can't move on from there. Good if you want to use the auto label, but if you want to keep the old one, then what really should be the step then? Here is an example: No label changes. '/' must be configured! The auto-allocated layout for wd0 is: #size offset fstype [fsize bsize cpg] a: 1.0G0 4.2BSD 2048 163841 # / b: 1.3G 2097648swap c:74.5G0 unused d: 4.0G 4719456 4.2BSD 2048 163841 # /tmp e: 6.0G 13109040 4.2BSD 2048 163841 # /var f: 1.9G 25692912 4.2BSD 2048 163841 # /usr g: 1.0G 29778336 4.2BSD 2048 163841 # /usr/X11R6 h: 5.4G 31875984 4.2BSD 2048 163841 # /usr/local i: 2.0G 43210944 4.2BSD 2048 163841 # /usr/src j: 2.0G 47406240 4.2BSD 2048 163841 # /usr/obj k:49.9G 51601536 4.2BSD 2048 163841 # /home Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] C You will now create a Sun-style disklabel on the disk. The disklabel defines how OpenBSD splits up the disk into OpenBSD partitions in which filesystems and swap space are created. You must provide each filesystem's mountpoint in this program. This platform requires that partition offsets/sizes be on cylinder boundaries. Partition offsets/sizes will be rounded to the nearest cylinder automatically. Label editor (enter '?' for help at any prompt) p OpenBSD area: 0-156301488; size: 156301488; free: 0 #size offset fstype [fsize bsize cpg] a: 10493280 4.2BSD 2048 163841 b: 8389584 1049328swap c:1563014880 unused d: 2097648 9438912 4.2BSD 2048 163841 e: 20972448 11536560 4.2BSD 2048 163841 f: 2097648 32509008 4.2BSD 2048 163841 g: 10486224 34606656 4.2BSD 2048 163841 h: 2097648 45092880 4.2BSD 2048 163841 i:109110960 47190528 4.2BSD 2048 163841 w q No label changes. '/' must be configured! The auto-allocated layout for wd0 is: #size offset fstype [fsize bsize cpg] a: 1.0G0 4.2BSD 2048 163841 # / b: 1.3G 2097648swap c:74.5G0 unused d: 4.0G 4719456 4.2BSD 2048 163841 # /tmp e: 6.0G 13109040 4.2BSD 2048 163841 # /var f: 1.9G 25692912 4.2BSD 2048 163841 # /usr g: 1.0G 29778336 4.2BSD 2048 163841 # /usr/X11R6 h: 5.4G 31875984 4.2BSD 2048 163841 # /usr/local i: 2.0G 43210944 4.2BSD 2048 163841 # /usr/src j: 2.0G 47406240 4.2BSD 2048 163841 # /usr/obj k:49.9G 51601536 4.2BSD 2048 163841 # /home Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] E This platform requires that partition offsets/sizes be on cylinder boundaries. Partition offsets/sizes will be rounded to the nearest cylinder automatically. Label editor (enter '?' for help at any prompt)
Re: New disklable doesn't keep old partitions if requested
I try to keep the actual partition of the disk as it was before and do a fresh install, but the snapshots looks like simply do not allow this now. You can select Custom label and it will show the previous label, but then when you write it, obviously no changes are present, but when you Quit it, it comes back to the same question and looks like you can't move on from there. Good if you want to use the auto label, but if you want to keep the old one, then what really should be the step then? Here is an example: No label changes. '/' must be configured! The auto-allocated layout for wd0 is: #size offset fstype [fsize bsize cpg] a: 1.0G0 4.2BSD 2048 163841 # / b: 1.3G 2097648swap c:74.5G0 unused d: 4.0G 4719456 4.2BSD 2048 163841 # /tmp e: 6.0G 13109040 4.2BSD 2048 163841 # /var f: 1.9G 25692912 4.2BSD 2048 163841 # /usr g: 1.0G 29778336 4.2BSD 2048 163841 # /usr/X11R6 h: 5.4G 31875984 4.2BSD 2048 163841 # /usr/local i: 2.0G 43210944 4.2BSD 2048 163841 # /usr/src j: 2.0G 47406240 4.2BSD 2048 163841 # /usr/obj k:49.9G 51601536 4.2BSD 2048 163841 # /home Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] C You will now create a Sun-style disklabel on the disk. The disklabel defines how OpenBSD splits up the disk into OpenBSD partitions in which filesystems and swap space are created. You must provide each filesystem's mountpoint in this program. This platform requires that partition offsets/sizes be on cylinder boundaries. Partition offsets/sizes will be rounded to the nearest cylinder automatically. Label editor (enter '?' for help at any prompt) p OpenBSD area: 0-156301488; size: 156301488; free: 0 #size offset fstype [fsize bsize cpg] a: 10493280 4.2BSD 2048 163841 b: 8389584 1049328swap c:1563014880 unused d: 2097648 9438912 4.2BSD 2048 163841 e: 20972448 11536560 4.2BSD 2048 163841 f: 2097648 32509008 4.2BSD 2048 163841 g: 10486224 34606656 4.2BSD 2048 163841 h: 2097648 45092880 4.2BSD 2048 163841 i:109110960 47190528 4.2BSD 2048 163841 w q No label changes. Wait. Don't you see what is wrong above? Let me guess. The last time you used this disk, partition d was your /home partition, right, and i is /var? We don't know what partition to mount where. You failed to fill in the information, using at least the 'm' command, and then when you quit disklabel it correctly says: '/' must be configured! Read what it says. The nice install script then nicely goes back to trying to see if you will learn to read next time. The auto-allocated layout for wd0 is: #size offset fstype [fsize bsize cpg] a: 1.0G0 4.2BSD 2048 163841 # / b: 1.3G 2097648swap c:74.5G0 unused d: 4.0G 4719456 4.2BSD 2048 163841 # /tmp e: 6.0G 13109040 4.2BSD 2048 163841 # /var f: 1.9G 25692912 4.2BSD 2048 163841 # /usr g: 1.0G 29778336 4.2BSD 2048 163841 # /usr/X11R6 h: 5.4G 31875984 4.2BSD 2048 163841 # /usr/local i: 2.0G 43210944 4.2BSD 2048 163841 # /usr/src j: 2.0G 47406240 4.2BSD 2048 163841 # /usr/obj k:49.9G 51601536 4.2BSD 2048 163841 # /home Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? [a] E This platform requires that partition offsets/sizes be on cylinder boundaries. Partition offsets/sizes will be rounded to the nearest cylinder automatically. Label editor (enter '?' for help at any prompt)
Re: New disklable doesn't keep old partitions if requested
No label changes. Wait. Don't you see what is wrong above? Let me guess. The last time you used this disk, partition d was your /home partition, right, and i is /var? Nope. Here is the standard setup on a truck load of servers. All use the same partition table, unless there is a very special need. I try to keep them all similar as much as possible and I do all fresh install every 6 months (not upgrade) using the sitexx.tgz files. It's more work to keep the sitexx.tgz files in sync, but at the same time, it provide for quick install and always run clean fresh install, plus should one server blow up, putting one back in service is just less the 10 minutes away max. And it force anyone to keep documentation of the setup, or changes of it by needing to keep sitexx.tgz in order. Here is an example here for fstab: # cat /etc/fstab /dev/wd0a / ffs rw 1 1 /dev/wd0i /data ffs rw,nodev,nosuid 1 2 /dev/wd0h /home ffs rw,nodev,nosuid 1 2 /dev/wd0d /tmp ffs rw,nodev,nosuid 1 2 /dev/wd0g /usr ffs rw,nodev 1 2 /dev/wd0e /var ffs rw,nodev,nosuid 1 2 /dev/wd0f /var/log ffs rw,nodev,nosuid 1 2 We don't know what partition to mount where. That I totally agree, but when I do the custom, and make no changes to the partition table, then why does it come back asking me to redo it instead of keep going and then I can re-enter the old mount name in the old partitions as it used to be? Same results with edit auto label as well. I can pass this pass deleting all and recreating all, but before (4.5 and before) I could keep the same label, and yes I needed to enter the mount point in label, witch was fine and I have no issue with that or doing it. You failed to fill in the information, using at least the 'm' command, and then when you quit disklabel it correctly says: Theo, I failed to follow you here. Sorry if that's obvious, but I fail to see it. The man page does say the m command is to modify parameters for an existing partition. I am not creating a new one, but just want to use the old one and I have no problem if I need to re inter the mount point obviously as it needed to be done as well before. But it doesn't allow me to do so IF I do not make changes to the partition table. It does force me to do m for each partition, not changing any data other then entering the mount point. Before, I could pass this and just enter the mount point and keep going. So, I have redone it to test it and yes, I can use the m for each partitions and not modify any data for the partition size and all and just provide the mount point then when I write it and quit, it does continue the process as before. But this wasn't required before. So, if one wants to keep the same partition then before, what would be the best way then? I thought that it would be logical to do the custom selection, not making any changes to the partition table as before and then when save, just needed to type the mount point and move on. But I can't do that now without needed to use the m for each partition, not making any changes to the partition size, offset and all and then provide the mount point. '/' must be configured! Read what it says. The nice install script then nicely goes back to trying to see if you will learn to read next time. I am sure not saying it's not nice. It is very nice and I like the new way for sure. I just never used to have the need to do this before. It previous version allow me to provide the name after no changes where done in the partition and the system didn't know what the partition were instead of going back to it asking to redo it all. That part of the previous install made more sense to me, but I sure can do it the new way. Instead of using the same partition table and then have to enter the mount point for each one, now it needs to use m for each partition, keep the setting the same for the size, offset and all and only enter the mount point now. It does add way more steps in that situation yes. Is that a big deal, no, just wonder why or if there was a way to skip that to be like in previous version? Wouldn't it make more sense if a custom setup is selected and no changes are done to the partition label, then to be assume the partition itself wanted to be kept intact and then only the mount label needed to be provided as before? The short of it is if you make no changes to the partition table, yes the system do not know what mount point you want, then why not only asked for the mount point then when getting out of the custom disklable part? That's how it was before. Is there really a need not to allow this? I really have no problem either way, but just wonder why or if there was a way to skip it. That was the essence of my question. Best, Daniel
Re: New disklable doesn't keep old partitions if requested
Let me guess. The last time you used this disk, partition d was your /home partition, right, and i is /var? Nope. Here is the standard setup on a truck load of servers. All use the same partition table, unless there is a very special need. How would we know that? You are doing an *INSTALL* We know nothing about your practices. [paragraphs of extra text deleted] That I totally agree, but when I do the custom, and make no changes to the partition table, then why does it come back asking me to redo it instead of keep going and then I can re-enter the old mount name in the old partitions as it used to be? Partition tables do not contain mount point information. Same results with edit auto label as well. I can pass this pass deleting all and recreating all, but before (4.5 and before) I could keep the same label, and yes I needed to enter the mount point in label, witch was fine and I have no issue with that or doing it. Labels do not contain mount point information. [paragraphs of moaning and complaining deleted] That's how it was before. Is there really a need not to allow this? You need to learn how to listen.
Re: New disklable doesn't keep old partitions if requested
You need to learn how to listen. That's fair Theo. But to make it short. Before when at the disklabel part of the install, one could just type 'q' and it was then asked for the mount point of that actual unchanged partition as before and skip the 'm' steps if you want. Now you can't just type 'q' and do this, but needs to do 'm' for each partitions and keep the same size, offset, etc the same and provide then the mount point, then save, quit and keep going. If there is a way to skip these additional steps using 'm' on disk unchanged partition between install and just need to type 'q' as before and provide the needed mount points obviously, I would like to know how now? Doesn't appear to be possible anymore. Am I wrong? Best, Daniel
Re: New disklable doesn't keep old partitions if requested
You need to learn how to listen. That's fair Theo. But to make it short. Before when at the disklabel part of the install, one could just type 'q' and it was then asked for the mount point of that actual unchanged partition as before and skip the 'm' steps if you want. You still are being asked. Do you see mountpoints on the listing with your partitions? No you don't. So why don't you set them up? I think it is because you prefer writing essays. Am I wrong? Yes you are wrong, and damn infuriating too.
Re: New disklable doesn't keep old partitions if requested
Daniel, As made quite clear in Theo's post, a disklabel does not contain any information about mount points. All of the partitions you created in 4.5 exist, but the installer does not know where to mount them, or even if you want to. In 4.6 selecting (C)ustom layout will show you what's actually on-disk, if anything is. In your email, you simply type 'w' and 'q' without setting any mount points. This will obviously fail. You *NEED* to use 'm' to define mount points, this information will be passed to the installer and won't be retained on-disk. The act of not doing this will loop the installation, you will no longer be prompted to confirm mount points. Hopefully you are now aware of the required steps, a native English speaker would have noticed the sarcasm in Theo's message. Take care. -Brynet
Re: New disklable doesn't keep old partitions if requested
You *NEED* to use 'm' to define mount points, this information will be passed to the installer and won't be retained on-disk. Or 'n' There is a reason why the installer disklabel and fdisk commands both have a 'M' command in them, to show the manual page. Hopefully you are now aware of the required steps, a native English speaker would have noticed the sarcasm in Theo's message. I am not being sarcastic. I truly am sick of having my time wasted.
Re: New disklable doesn't keep old partitions if requested
Theo de Raadt wrote: Or 'n' Thank you. There is a reason why the installer disklabel and fdisk commands both have a 'M' command in them, to show the manual page. I agree, that is a handy shortcut. :-) I am not being sarcastic. B I truly am sick of having my time wasted. Many people get frustrated when things change, but they did have the opportunity to test and influence the changes.. instead they wait until the last moment and send frustrated messages to the lists. I'm sure many here respect the time and effort you dedicate to the project and to these lists, hopefully you won't be driven away by it all. How were your Canada Day celebrations? -Brynet
Re: New disklable doesn't keep old partitions if requested
Sat, Sep 05, 2009 at 10:13:05PM -0400, Daniel Ouellet may have written: You need to learn how to listen. That's fair Theo. But to make it short. Before when at the disklabel part of the install, one could just type 'q' and it was then asked for the mount point of that actual unchanged partition as before and skip the 'm' steps if you want. Now you can't just type 'q' and do this, but needs to do 'm' for each partitions and keep the same size, offset, etc the same and provide then the mount point, then save, quit and keep going. If there is a way to skip these additional steps using 'm' on disk unchanged partition between install and just need to type 'q' as before and provide the needed mount points obviously, I would like to know how now? Doesn't appear to be possible anymore. Am I wrong? Best, Daniel Use 'n' instead of 'm' to provide the needed mount points. With the old installer, while in the disk label editor, you could name your mount points while creating (command 'a') or modifying (command 'm') your partitions, or you could just name the mount points for existing partitions without otherwise those partitions (command 'n'). After you finished the disk label editor, the old installer would then prompt you to name your mount points. If you'd already named them in the disk label editor, this was redundant. The new installer removes the redundancy and requires that you name your mount points in the editor. When you choose C for a custom layout, the installer shows you this: -- You will now create an OpenBSD disklabel inside the OpenBSD MBR partition. The disklabel defines how OpenBSD splits up the MBR partition into OpenBSD partitions in which filesystems and swap space are created. You must provide each filesystem's mountpoint in this program. -- Note the last sentence. Matt. -- ... let us keep in mind the basic governing philosophy of The Brotherhood, as handsomely summarized in these words: we believe in healthy, hearty laughter -- at the expense of the whole human race, if needs be. Needs be. -- H. Allen Smith, Rude Jokes
Re: New disklable doesn't keep old partitions if requested
Hi Daniel, It appears as if you're still confused. Specifiy the mount points within disklabel using 'm' or 'n' has been standard proceedure for some time. Some users skipped this and waited for the confirmation prompts after quiting disklabel. This was deemed redundant, users can already specify the mount points from within disklabel. You cannot do that anymore, using 'n' as Theo suggessted might save you some time. HTH. -Brynet
Re: New disklable doesn't keep old partitions if requested
Hi Matthew Use 'n' instead of 'm' to provide the needed mount points. That address my question. An obvious over site on my part! I never used it until today as far back as version 2.8. With the old installer, while in the disk label editor, you could name your mount points while creating (command 'a') or modifying (command 'm') your partitions, or you could just name the mount points for existing partitions without otherwise those partitions (command 'n'). I see that now. After you finished the disk label editor, the old installer would then prompt you to name your mount points. If you'd already named them in the disk label editor, this was redundant. The new installer removes the redundancy and requires that you name your mount points in the editor. That's where my confusion came from. I wrongly assume that you create the partitions and then named them after the fact. I was obviously wrong and made the wrong assumptions here. When you choose C for a custom layout, the installer shows you this: -- You will now create an OpenBSD disklabel inside the OpenBSD MBR partition. The disklabel defines how OpenBSD splits up the MBR partition into OpenBSD partitions in which filesystems and swap space are created. You must provide each filesystem's mountpoint in this program. -- Note the last sentence. I saw that one and obviously read it, but didn't sync in for me. Based on previous years, I assume that, yes you need to partition your disk and then obviously will also need to provide the mount point when you are done. Before, you could provide them after the fact like you explain and obviously was a miss understanding of the process on my part that you clarify for me. Sorry for the noise. And Theo, I am truly sorry you got upset on this question from me here. I obviously failed to understand it properly and that's why I asked the question. My apology for your increase in temper cause by my question, but I just obviously didn't get it right and this clear it up for me. I was obviously wrongly looking for the installer asking me for the mount point as before, witch I see now was wrong to assume on my part. Thanks for your time and clarification on my miss understanding. One need to be ready to get a beat up to get clarifications, but that's fine. And Theo, I NEVER intended to make you waste time here. It was an honest miss understanding on my part obviously. Best regards, Daniel
Re: New disklable doesn't keep old partitions if requested
This whole thread is actually one more proof that nobody ever reads the installation notes (INSTALL.*). Miod
