- Thread Starter
- #26
Resolving issues with FreeBSD-RC is rather simple compared to Systemd-bloat.
Probing for USB devices is however faster in Linux then FreeBSD.
I still complain about systemd at $JOB and have been told learn to like it.Some make money by selling "systemd-services". Because,well it's complicated.
I had an issue one time related to USB stick mounting and having an entry in fstab. System stopped booting, some stupid windows-like error code number on the console that had to go to another system and google grep "wtf does this mean" to find out "use this tool to look at binary logs and find out" "oh, usb, fstab entry"The real problem with systemd is it's opaque.
BTW, IMO the Solaris SMF was the correct way to solve the problem
I never complained, neither did any other Solaris or any other UNIX admin complain.
BTW, IMO the Solaris SMF was the correct way to solve the problem.
This is no wonder, because Redhat was Poettering's employer when heEven though systemd is technically not the best solution, a lot of,many,linux distro's have systemd as default.
Some big players like redhat are pushing it
Don't twist my words.But you wrote:
You are speaking about solving a Problem that is not a Problem. And why to form FreeBSD as the ones that
complain and should use Linux, because that is their reference point? Desktop freaks should use Linux,
Ubuntu, not FreeBSD.
I installed once Illumos, and got crazy with SMF. Also with the rc system of Linux. And also the one of FreeBSD
is too complicated for my taste. At best is the one of OpenBSD.
I think SMF is for people managing a lot of computers. For people with one or two servers, for people
using it as desktop, for embedded devices is not an advantage, it makes him life unnecessarily complicated.
Pottering now works for M$.This is no wonder, because Redhat was Poettering's employer when hegiftedcursed the Linux world with systemd.
I mean with commercial driven unices it's a common topic that all have replaced SYSV Init. Ubuntu had upstart, Apple has launchd, Solaris SMF. All are trying to solve more or less the same problem(s).
Like jails, Zones are a kernel isolation and partitioning technology. The term Solaris Containers are the userland definitions that structure zones in userland in order to present the Solaris "jail" (zone) to the end-user. Think of zones as a kernel thing and containers the environment.Imagine UCL formatted SMF manifests. I believe Zones uses SMF natively too. That would effectively kill the need for all this configuration management goo in the ports tree (yes, that includes you too, docker), and streamline service scripting in base.
It's more like SYSV rc on steroids. Rather than the order be determined by Snn* and Knn*, the order is determined by metadata in each script itself. It's sorta like both.Doesn't /etc/rc.d/* does the same thing as SMF manifests ? Just with sh-scripting & without XML-formating.
I know, when this became known I wrote an own thread about it here.Pottering now works for M$.
![]()
Lennart Poettering, the Systemd Creator, Goes to Work at Microsoft
Lennart Poettering, the creator of crucial Linux components such as systemd and PulseAudio, has left Red Hat to pursue careers at Microsoft.linuxiac.com
FreeBSD VNET jails are the FreeBSD equivalent to Zones. While Solaris Zones are created and managed using Container definitions, FreeBSD jails are managed through the jail(2) system call. The jail(8) command uses the jail(2) system call to create, manage, and destroy jails just as Solaris Containers manage Zones. One could, for example write one's own replacement for jail(8) command which might for example using a GUI or ncurses interface, calling the jail(2) system call directly.
Also, what do you mean by "finished Zones?"