Learn how to use it. It's not like you knew how to maintain the traditional bootscripts before you learned how they worked...
Originally Posted by RollMeAway
Good thing he didn't begin his computing with CP/M. He would still be using it because the boot system of MS-DOS was a bit different.
+1 ...and very well said. I had also been following the threads on the list and was a little surprised by some of the comments.
Originally Posted by TheCycoONE
I wasn't sure if i was going to like systemd, at first. but after switching over and familiarizing myself with it - i quite like it. My system boots faster (small benefit, no big deal) but the service files are easy to work with and fairly straight-forward.
I think it is a good move for Archlinux to switch now rather than somewhere down the line. I haven't switched my other Arch machine yet, but i think i will do that sometime over the next few days.
NO option but to install systemd? You must be mistaken.
Originally Posted by RollMeAway
Switching to systemd is the topic of this article.
I never used slackware but I have heard it doesn't have dependency resolution with the packages? I'm sure there are tools that provide that functionality but, really that sounds like a pain.
Originally Posted by AJSB
I use slapt-get utility and it works OK....besides that i also use my brain
Originally Posted by n3wu53r
It was much worse some years ago...
With time i kinda wrote my own handbook, it's a breeze to install and configure now any new Slackware release....can't wait for Slackware 14
There was a phrase "If you learn UBUNTU, you learn UBUNTU, if you learn FEDORA , you learn FEDORA but if you learn Slackware, you learn LINUX" ...so, true...the instalation process is something more intimidating than UBUNTU or Windows where you are carried by hand....i still remember my 1st time that installed it
I said to myself " Oh s**t, oh S**T !!! I must be nuts to try to install this alone !!!" after tested UBUNTU, Fedora, Mandriva , PCLinuxOS, XUBUNTU, KUBUNTU, Debian, etc, etc.
But ended up OK, and no matter i continue to test other distros , i end up coming back to Slackware...
FYI, I think the terms you're looking for are "de facto" and "de jure."
Originally Posted by ShadowBane
I am pretty sure you have your wires crossed on the rt daemon thing since I have been around on the LAD and LAU mailing lists while this has been happening. My understanding goes like this - the method for RT that jack currently uses introduces security issues such that distros such as debian don't want to turn it on by default... The current compromise is that debian based distros at least give you the option to turn it on when you install jack. What Lennart proposed (and implemented) was an alternative method of getting realtime privileges that offered extra security against some forms of attack. He wrote to the linux audio crowd to inform them that an alternative way of getting realtime privileges was available. The jack crowd understandably had previously been told that they way that they were doing things was acceptable and to my knowledge has stuck to the way that they are doing things. I don't think a daemon (other than pulse or jack) is involved in this process at all. -
Originally Posted by energyman
Mostly I just didn't want to spell check those.. :P
Originally Posted by adler187
Also, "de facto" presents itself in english as "the standard" and "de jure" presents itself in english as "a stanard"