5 ms·
It's interesting to me to see this project be both so innovative in security domains, yet so backwards in usability. I was trying to install openbsd on a new r
by azinman2 9y ago
It's interesting to me to see this project be both so innovative in security domains, yet so backwards in usability.
I was trying to install openbsd on a new router this week, and I had a hell of a time trying to repartition the disk such that it didn't pre-allocate partitions for X11 (which I had no use for). I could delete partitions but then I got empty spaces and seemingly no good way to resize via the primitive CLI. I googled around and found this thread [1], where someone suggested a GUI installer to help novice users install it, which got this reply:
"Uh no. The OpenBSD installation routine is perfect as is. I would not want to see a GUI installer on my favourite BSD."
Really, perfect? Could not be possibly improved? And because you don't want a GUI, no one should have one? All the rest of the replies were similar to boot.
I went back to Linux as I can only imagine what the rest of running it is like. Sometimes old stubborn cranks can really get in the way of progress.
[1] http://daemonforums.org/showthread.php?t=8580 http://daemonforums.org/showthread.php?t=8580
- ams6110 9y agoOpenBSD "partitioning" is actually a disklabel, and the TUI for it is not bad. I almost always tweak the default partitions a bit when I install, because I like a larger /usr. You maybe missed option R: R [part] Resize a partition in an automatically allocated label, compacting unused space between partitions with a higher offset. The last partition will be shrunk if necessary. Works only for automatically allocated labels with no spoofed partitions. In OpenBSD, for any question first consult the man pages before "googling around". Their man pages are really good.
- protomyth 9y agoDisk setup https://www.openbsd.org/faq/faq14.html https://www.openbsd.org/faq/faq14.html With the actual installation instructions https://www.openbsd.org/faq/faq4.html https://www.openbsd.org/faq/faq4.html And how it does the auto https://man.openbsd.org/disklabel#AUTOMATIC_DISK_ALLOCATION https://man.openbsd.org/disklabel#AUTOMATIC_DISK_ALLOCATION
- milcron 9y agoI am a newer OpenBSD user, so I encounter roadblocks/papercuts quite frequently. What I like about the OS is that the problems are all easy in retrospect. I never struggle with the same issue twice. For instance, the first time I booted OpenBSD, I was met with the following prompt: boot> What am I supposed to do here? Does it require some weird incantation in order to load the kernel? It turns out you just have to hit enter. The OpenBSD install script really is quite simple. I'm not sure I would call it easy (simple ain't easy), but it's certainly straightforward and setup is usually just hitting enter a bunch of times. You only encountered trouble because you tried to fiddle with it and got frustrated. Another huge benefit of OpenBSD compared to Linux is the incredible quality of documentation. Missing or outdated docs are considered a serious bug. To address your issue, let's look at the docs: https://man.openbsd.org/disklabel#AUTOMATIC_DISK_ALLOCATION https://man.openbsd.org/disklabel#AUTOMATIC_DISK_ALLOCATION It looks as though if the installation target is smaller than 8GB, it won't create a separate partition for X11. That's useful to know. Additionally, you can specify your own partition template using the -T option. It might be cool to see a graphical project like GhostBSD built on top of OpenBSD, but I have to agree with the curmudgeons that the text-based installer is pretty fantastic as-is.
- jancsika 9y ago> boot> > What am I supposed to do here? Does it require some weird incantation in order to load the kernel? It turns out you just have to hit enter. > [...] > Another huge benefit of OpenBSD compared to Linux is the incredible quality of documentation. Where is the documentation that explains a) why you have to click <Enter> to continue the boot process and, b) the reason why this isn't self-documenting at the "boot>" prompt?
- ams6110 9y agoThe man page for boot(8) explains it. You don't have to hit enter at the boot> prompt. It pauses for a few seconds to allow you a chance to enter boot commands; you can hit enter to boot immediately, or it will proceed with a default boot after a few seconds if you do nothing.
- tedunangst 9y agoRandos on some forum don't speak for the project.
- IshKebab 9y agoThey speak for the attitudes of its community though.
- bigato 9y agoHow would a GUI install help you with your router install? I mean, it's not impossible to create one, but given that routers usually don't have video outputs, this is a very specific requirement. You won't even install X11 anyway. I'm not aware of any general-purpose OSes that have a GUI for router installs. Also, maybe you want to review the "GUI is easier than TUI" premise. Clicking per se is not inherently easier than hitting ENTER. And while I'm aware that I'm biased in that regard since OpenBSD is my favourite Unix, I'm honestly not aware of any other OS that's easier to install, GUI or not. You really have to read, understand answer those questions, there's no way around it. At this point, the difference between typing yes/no and ENTER vs clicking is minimal, usability-wise. On the other hand, the additional complexity brought by a GUI is a big burden on developers. I remember this same discussion years ago on Debian land, when they didn't have a GUI install. Like an email from a random guy stating that if Debian would only fix their install and have a GUI, they would conquer the world. At a certain point, they finally built a GUI install, that was exactly the same questions asked in a GUI that even resembled the TUI. Biggest difference was, you could use your mouse. And eventually have some trouble because the installer wouldn't recognize your video card. In which case you could always fallback to the TUI install, but the question is: were there any usability gains at all by switching to a GUI? My point being, you can improve usability regardless of GUI or TUI. In OpenBSD, if you are installing several similar machines with the same setup you can also do unattended installs (https://man.openbsd.org/autoinstall https://man.openbsd.org/autoinstall), and that would really make the install easier and simpler. I don't think you were referring to this anyway; but other than that, and putting the fallacious GUI vs TUI aside, I'm not sure how else you could make OpenBSD install much easier. I would be really curious to listen if someone have some specific ideas , and I'm pretty sure OpenBSD devs would also be interested.
- Gracana 9y ago> Sometimes old stubborn cranks can really get in the way of progress. I didn't see anyone getting in the way of progress. Someone said "I think the developers should make X for me," and other people replied "no they shouldn't." They could have said "yes, they should" and still nothing of substance would be done.