When you install Crux, yes, it's fully binary. But all subsequent updating is from source code (except for a few huge packages like FF and LO).
Quote:
|
Quote:
Actually CRUX is not similar to Slackware. It does the things much better. It is lean. It has a better packaging system. Its ports system is more flexible than SBo. It is developed on git. And it survived the retirement of its BDFL. P.S. Sorry for the OT. Cheers |
Quote:
2. If that fails, try the same thing with systemd.unit=emergency.target. 3. If that fails too, boot an emergency system, mount the partitions and chroot into your installed system. Last time I had some trouble (bad LDAPS configuration on 389 Directory Server), systemd.unit=rescue target did the trick, and I could figure out what was wrong. Systemd is just a different kind of tool in your toolbox. That's it. |
Quote:
|
Quote:
systemd development: https://www.youtube.com/watch?v=LCN4rDnm6Ws |
Quote:
|
Quote:
I do not remember precisely every detail, but certainly I used a tool named "pkg-get" to update my installation from loops like this one: http://ftp.morpheus.net/pub/linux/crux/loop/ Well, was nothing fancy in my setup. Just XFCE and Firefox as additions. |
Quote:
https://github.com/Dlackware/systemd |
Quote:
If for some reason systemd makes its way into CRUX, it will be the same way PAM did it. The port will appear in a private repository. Then eventually it will make its way into contrib an then into opt. And finally maybe it will land into core. There will be no drama. In the meantime if I want a systemd enabled CRUX I will make my own port and will modify a few core/opt/xorg ports and give them higher priority. That's it. Dlackware only touches the surface of what is needed to implement systemd into Slackware. Cheers |
Quote:
Or is this a general complaint about how one would go about getting SystemD into the main tree; that is a complaint that it is not done in a more democratic manner; and that you favor a more democratic method of getting software moved into the "core"? |
Quote:
https://crux.nu/pipermail/crux-devel...ly/004039.html (Dead link) https://lists.crux.nu/pipermail/crux...ly/thread.html http://gabordemooij.com/index.php?p=...e_from_systemd Also how would it be easier to start over from scratch and port systemd to crux than it would be to complete dlackware? What is missing from dlackware? From its own documentation it seems to be at least enough to build gnome3. |
Quote:
That was a good analogy and one in various forms has been used for a long time for many scenarios. Yes, it is like heroin, tyrants, or any situation where a person has adjusted and has grown comfortable with that which harms them, and I say this from observing hard drug addicts for years. That is the analogy the person is making, That people do not see a problem with systemd, say it works fine for me, because it provides my basic needs, but that is not the issue. You have a habit of demeaning people' s experiences as ranting and other nonsense when you do not like what they say. You are actually are being more intolerant than the ones against systemd and just be honest and say you do not want to hear anything bad about system, FUD or truth, and will shout them down. |
Quote:
Devuan is done by a multi-million dollar non-profit that also provides other services. I donated to them a few times over 15 years ago when I was on dial-up and running a webserver on the desktop (dyndns). So there is people paying. |
Quote:
I have come across this on Debian (SteamOS) with an external hard drive. Something similar too on Crux on the same external. I think it is my external does not have a fully standard compliant controller or missing something but irrelevant. The offset is an error in looking for the filesystem, the fs may be fine but it expect to look for / at a location (offset) and cannot find and since it cannot find / the kernel says good-bye and systemd says me too. In short what the controller or hd or fs is reporting where the / starts is wrong. Has he installed a Linux on this machine before? Does he have a BIOS or UEFI? If it is a few years old it may be better to boot in legacy mode. This is another real world experience with systemd and is bringing back old crap that had been fixed years ago. I used to refurbish surplus government computers ( when still modem dip switches ) and some BIOSes would do the same kind of thing. Except they would drop seeing the IDE controller. This is not the case, but it an old problem that was solved for many years that has reappeared and I seem to remember this case JakeJake ran into before with systemd not finding a / that an fschk or chroot mount has no problem seeing. |
Quote:
I fail to see how it is "cyber-luddite" in comparison too Slackware. I' am guessing but I would bet that most long term Slackware users can do the install and maintenance of CRUX as easy as they do in Slackware. Only two skills one has to transfer from using Slackware too CRUX - changing how to start daemons which is exactly like FreeBSD a couple of minutes to figure out, and ports which is almost exactly like FreeBSD so a couple of more minutes, and a few minor details anybody comfortable with Slackware will have no problems learning and applying in a few minutes. Slackware installs on my external ssd, CRUX doesn' t. Therefore Slackware would be a smarter system and smart people use smart systems. I say that light hearted btw for some humour. |
All times are GMT -5. The time now is 02:10 PM. |