i haven't installed openbsd in a long time.
what's up with this automatic disklabel business? disappointing.
what's up with this automatic disklabel business? disappointing.
it creates so many partitions. I stick to what they used to have in the install faq: a for root, b for swap, d for tmp, e for var, g for usr, and h for home.
Oh man, what have they done to it?
when i was dropped into the disklabel interactive editor, i was transported back to my basement in 2003.
i knew what to do.
p
d a
c a
oops
a a
a b
a d
a e
a f
p
w
q
i know this installer .. BECAUSE IVE USED IT THIRTY TIMES
i knew what to do.
p
d a
c a
oops
a a
a b
a d
a e
a f
p
w
q
i know this installer .. BECAUSE IVE USED IT THIRTY TIMES
You can *choose* to automatically assign labels, and when it does, you can *choose* to modify them afterwards.
I find that the automatic disklabeling works fairly reasonable in most cases.
Why do the work yourself if the computer can do it for you? Isn't that the whole point of computers?
I find that the automatic disklabeling works fairly reasonable in most cases.
Why do the work yourself if the computer can do it for you? Isn't that the whole point of computers?
nice post lr!!!
I remember getting that disklabel editor the first time I installed openbsd like nine years ago. I still have the printout of the relevant part of the install faq and I still use it for reference if I forget any of the standard/traditional mount points/partitions!
the new automatic labels seem a bit ridiculous. it creates like twelve partitions for a bunch of stuff like /usr/X11R6. maybe they're sized perfectly or something, but I've never tried it.
also, 'p m' etc. are crucial.
the new automatic labels seem a bit ridiculous. it creates like twelve partitions for a bunch of stuff like /usr/X11R6. maybe they're sized perfectly or something, but I've never tried it.
also, 'p m' etc. are crucial.
speaking of openbsd, I have a pf firewall again.
asemi I am envious. for real.
I can't figure out why mp3s are skipping when played from an nfs share :(. this is happening over wifi and ethernet. and a tcpdump of nfs traffic doesn't show anything out of the ordinary when a song skips.
Cache issue?
> You can *choose* to automatically assign labels, and when it does, you can *choose* to modify them afterwards.
aren't the offsets all messed up then?
aren't the offsets all messed up then?
Doesn't that get calculated automagiclly for you? On FreeBSD I just use * and presto!
/
swap
DONE. :3
swap
DONE. :3
Not much point in creating lots of partitions unless it's a server where it's important to set mount flags like noexec, nodev, etc.
It helps fragmentation, prevents file corruption, makes backups easier, running newfs on /obj/ is *way* faster then rm -rf /obj/
I agree wrt fragmentation, but why does it prevent file corruption or make backups easier?
If you system crashes there is a much larger chance that something like /var/ is corrupted then / (/var == lots of writes, / == almost no writes).
And IF /var/ becomes VERY corrupted (rare, but may occur in freak crashes, broken hard drives, weird software bugs, or a combination of those) it will isolate the corruption to that one FS.
It makes backups easier because you can get away dumping / and /usr only at upgrades, and stuff like /home/ or /var/ much more often ... This of course depends on your backup solution, but I like filesystem dumps.
And IF /var/ becomes VERY corrupted (rare, but may occur in freak crashes, broken hard drives, weird software bugs, or a combination of those) it will isolate the corruption to that one FS.
It makes backups easier because you can get away dumping / and /usr only at upgrades, and stuff like /home/ or /var/ much more often ... This of course depends on your backup solution, but I like filesystem dumps.
It doesn't prevent file corruption then, it just limits possible consequences of it :)
It prevents the *spread* of file corruption.
These are very rare conditions though.
These are very rare conditions though.
I think it actually helps with *file system* corruption, not *file* corruption, i.e. if the file system is corrupted it doesn't affect everything (and fsck will be faster). If just a file gets corrupted I don't see how that can affect other files or the file system itself. You just lose whatever data got corrupted.