A third option (I just thought of it): is to use mfsbsd.
Then you don't need to have the power of FreeBSD. Any generic GUI operating system is sufficient. Matter-of-fact, if you use a cloud-hosted office suite (both Microsoft and Google have excellent versions, the latter is free), then a ChromeBook is appropriate technology.If 99% of your desktop usage involves an office suite and a browser, ...
Then you don't need to have the power of FreeBSD. Any generic GUI operating system is sufficient.
From a user viewpoint, you can indeed simply say "no". That doesn't worry me.
I am using plasma6-plasma on 14.3 latest on one machine. The kde control panel has a tick box for automount USB devices that does indeed automount USB devices.Will the KDE which is installed optionally by the installer be different (better?) from what is currently avaiable in ports/packages?
I mean: Will it, e.g., be better integrated into the system? For example: Can I click on an USB-stick icon and it will mount and open it in a File Browser. (Edit: this does not work out of the box, e.g., in XFCE, which is what I am currently using). Something like that.
If that KDE becomes a polished, true official "FreeBSD Desktop", I would probably use it.
Speak for yourself, thank you.Then you don't need to have the power of FreeBSD.
Exactly. I feel that this is what's most disturbing for a lot of folks here.What worries you is that making FreeBSD more accessible to users ruins your false sense of superiority.
13 pagesAlain De Vos that holds for most desktops or window managers.
I remember there was a big fuss when PCBSD first came out, basically the same arguments, then Dru Lavigne took its (PCBSD's) side and most complaints stopped. (Even though I'm adding to it) I don't see how this thread has gone on for 12 pages. Maybe too many of us are bored.![]()
What is disliked about PkgBase will only manifest itself after a couple of years after its too late (when people start ricing the package list of what constitutes base). This was clarified earlier on in this thread.To people opposed to pkgbase: why don't you folks play with it, find out what you like, dislike or have questions about and provide some on-point feedback? That will be far more useful than complaining about it here.
What if I told you that these things are potentially related? Less technical users *like* monstrosities. Making FreeBSD accessible may well consist of us now having to deal with this cruft more and more in forums, mailing lists and in the software itself.What worries you is that making FreeBSD more accessible to users ruins your false sense of superiority.
[...]
Also. Leave the GTK/GNOME monstrosity to IBM/Red Hat.
I useI am using plasma6-plasma on 14.3 latest on one machine. The kde control panel has a tick box for automount USB devices that does indeed automount USB devices.
/Sysutils/Automount
A real puristI don't like automount, i like to mount manually.
QEDWhat if I told you that these things are potentially related? Less technical users *like* monstrosities. Making FreeBSD accessible may well consist of us now having to deal with this cruft more and more in forums, mailing lists and in the software itself.
What if I told you that these things are potentially related? Less technical users *like* monstrosities. Making FreeBSD accessible may well consist of us now having to deal with this cruft more and more in forums, mailing lists and in the software itself.
Might be better to apply our engineering experience and set the bounds of the scope to exclude it, at this point no?
I don't have a problem with this. Without the Berkeley folks & Bill Jolitz making BSD sources accessible to all, we'd have no open source *BSD. If opening up access was good then, it is good now. Reducing friction and making things easier for newbies doesn't mean the hordes will descend and destroy FreeBSD. As the userbase grows, you will have smaller percentage of people and at the same time a larger number of people writing software or otherwise helping FreeBSD. That is a good thing. Without the system evolving to accommodate the needs of new users, it will eventually wither away and die.What if I told you that these things are potentially related? Less technical users *like* monstrosities. Making FreeBSD accessible may well consist of us now having to deal with this cruft more and more in forums, mailing lists and in the software itself.
Yep, and I do like the automount feature.I don't like automount, i like to mount manually.
You can always use the umount(8) to un-mount anything that's been auto-mounted. Oh, and KDE actually offers you buttons to mount/unmount the USB sticks. And, that doesn't stop you from using dd(1) or gpart(8) on command-line afterwards... Just less typing and trying to remember the correct flags. The option is definitely there, and there's no lock-in to use a specific method.The reason i don't use automount is if i want to use dd or use gpart on the mounted partition.
[OT]In my case automount works but I cannot unmount anything automounted - this happens on every DE I tried (the last three are GNOME-Cinnamon-KDE)[/OT]and KDE actually offers you buttons to mount/unmount the USB sticks.
In which case, I'd check to see if something is trying to access the auto-mounted USB stick - if Dolphin has an open folder there, or if VLC is running. Paying attention to that helped me solve the un-mounting issues I had.[OT]In my case automount works but I cannot unmount anything automounted - this happens on every DE I tried (the last three are GNOME-Cinnamon-KDE)[/OT]
I don't believe it's the case. USB devices are handled by automount in my case and I suspect DEs are not allowed to unmount if they were not the ones which actually mounted the devices (to be clear, kde control panel tick box is not checked here).In which case, I'd check to see if something is trying to access the auto-mounted USB stick - if Dolphin has an open folder there, or if VLC is running. Paying attention to that helped me solve the un-mounting issues I had.
They certainly didn't open it up to non-technical users. It was not an easy process to get started back then.I don't have a problem with this. Without the Berkeley folks & Bill Jolitz making BSD sources accessible to all, we'd have no open source *BSD. If opening up access was good then, it is good now.
It will be way too late by then. Its like road speed limits; decreasing them is easy, but putting them back up when its determined they have no effect is very hard. No-one dares sign the dotted line to do so. If PkgBase does end up becoming an inconsistent mess, you think this will be reverted? No, we will simply lose the concept of "base" and FreeBSD will just become more aligned with the issues with Linux as the traditional BSD guys (i.e many of the developers) move to one of the other projects.
To be fair, I wasn't really referring to KDE being provided by the installer as a problem. I was around in the old FreeBSD 6.x days after all. Though I am disappointed after almost a decade, KDE isn't actually in a better state to new users... (Wifi, accounts, disk management tools are either non-existant or (dangerously) broken). Frankly, it makes FreeBSD look crap because its a perpetual MVP of a working desktop.No. Youre grasping at straws right now. The difference between the opt-in addition to the installer and DIY, is what I already stated. It removes the barrier to entry to having a working desktop. Thats the whole point.
Problem solved.Admittedly I moved to OpenBSD when pkg-ng came about.