4 ms·

Consistency, I have been using linux for 20+ years but if its not redhat or debian based I couldn't tell you how to start or stop services etc as its always dif

Consistency, I have been using linux for 20+ years but if its not redhat or debian based I couldn't tell you how to start or stop services etc as its always different from the unix standard and every other linux. FreeBSD is unix it doesn't try to be that and something else at the same time.

nix23 4y ago
>but if its not redhat or debian based I couldn't tell you how to start or stop services The same way as in freebsd "service blabla start" it's a compatibility hook.
- dangerface 4y ago
  on fedora its systemctl instead of service because they are all systemd up, other distros might use something other than systemd and a compatibility hook is entirely dependant on the distro deciding it cares about backwards compatibility which isn't the case for fedora or debian at least in comparison to freebsd you can still build work the old school way.
  - cesarb 4y ago
    > on fedora its systemctl instead of service because they are all systemd up Fedora (and its derivatives like RHEL/CentOS/etc) still has the "service" command, it forwards to the corresponding systemctl command. The same for Debian (the comments in Debian's "service" command even mention it's a modified version of the RHEL/Fedora one).
anthk 4y ago
This, this. On Debian I had to run rcconf since Debian Sarge. On OpenBSD there's rcctl and /etc/rc.conf.local. MUCH saner. If I had internet at home before 2010, a lot of things would be far easier. My fist Linux was from 2003-4, Debian Woody. Why I learned was until 2007-8 mainly the bunch of tools from Debconf (the installer, update-alternatives, apt, dpkg-reconfigure, make-kpkg (to compile a newer kernel), debhelper and so on), not the Unix way to do things. In 2006-2009 I knew how to compile Mplayer from source (tgz) and a bunch of other tools (Cedega from CVS) with apt-get build-dep to fetch the deps and a bit more, that's it. From 2009-2010, I've got a brief match with Slackware and Arch, and from that, OpenBSD. OpenBSD was dumb simple in design, seriously. With Linux you had to do voodoo with Artsd/ESD disabling them and then more fuckery with UCM files and DMIX. OSS under BSD's (I liked FreesBIE, a lovely live CD with FreeBSD and XFCE) just worked. And it ran faster than Linux. Also, the Bash guides from the Howto's were utterly difficult, much more than the Ksh ones from Orelly (learning Perl for scripting was far easier, trust me).

nix23 4y ago

>but if its not redhat or debian based I couldn't tell you how to start or stop services The same way as in freebsd "service blabla start" it's a compatibility hook.

dangerface 4y ago
on fedora its systemctl instead of service because they are all systemd up, other distros might use something other than systemd and a compatibility hook is entirely dependant on the distro deciding it cares about backwards compatibility which isn't the case for fedora or debian at least in comparison to freebsd you can still build work the old school way.
- cesarb 4y ago
  > on fedora its systemctl instead of service because they are all systemd up Fedora (and its derivatives like RHEL/CentOS/etc) still has the "service" command, it forwards to the corresponding systemctl command. The same for Debian (the comments in Debian's "service" command even mention it's a modified version of the RHEL/Fedora one).

anthk 4y ago

This, this. On Debian I had to run rcconf since Debian Sarge. On OpenBSD there's rcctl and /etc/rc.conf.local. MUCH saner. If I had internet at home before 2010, a lot of things would be far easier. My fist Linux was from 2003-4, Debian Woody. Why I learned was until 2007-8 mainly the bunch of tools from Debconf (the installer, update-alternatives, apt, dpkg-reconfigure, make-kpkg (to compile a newer kernel), debhelper and so on), not the Unix way to do things. In 2006-2009 I knew how to compile Mplayer from source (tgz) and a bunch of other tools (Cedega from CVS) with apt-get build-dep to fetch the deps and a bit more, that's it. From 2009-2010, I've got a brief match with Slackware and Arch, and from that, OpenBSD. OpenBSD was dumb simple in design, seriously. With Linux you had to do voodoo with Artsd/ESD disabling them and then more fuckery with UCM files and DMIX. OSS under BSD's (I liked FreesBIE, a lovely live CD with FreeBSD and XFCE) just worked. And it ran faster than Linux. Also, the Bash guides from the Howto's were utterly difficult, much more than the Ksh ones from Orelly (learning Perl for scripting was far easier, trust me).