SoylentNews is people
SoylentNews
Eric Hameleers announces
[May 18,] on the final day of my short holiday (of sorts), I prepped and released version 1.0.0 of my liveslak project. It is stable and the bugs that were reported (plus some more) have been taken care of.
The "1.0.0" marker is not the end of its development, of course. It means that I consider the project production-ready. It will be used to create Live Editions of Slackware 14.2 (64bit and 32bit) when that is released. There's still some more ideas for liveslak that I want to implement and those will become available as 1.x releases.
For demonstration purposes, I have generated a new set of ISO images using liveslak version 1.0.0. There are ISO images for a full Slackware (64bit and 32bit versions), 64bit Plasma5 and MATE variants, and the 700MB small XFCE variant (also 64bit). They are based on Slackware-current dated "Thu May 12 01:50:21 UTC 2016".
[...] I will re-write [the original blog post] into a landing page for anyone who is interested in a Live Edition of Slackware. [...] All previous articles about the liveslak project aka Slackware Live Edition are accessible through this shortcut link, by the way [links to changelogs].
(Score: 1, Troll) by Anonymous Coward on Sunday May 22 2016, @07:47PM
I made similar progression. But my reasons were more technical. The packages were rotting. Some packages being 5 years old at this point with many security fixes being overlooked. For slack it was the package manager that needed some work done to it. People kept coming up with neat innovations for it then the slack group would get mad about it for some reason or another. Then try to re-invent what was done and then it would get stuck being worse than the improved way. Then the improved way would not work correctly anymore or rot because you were supposed to use the 'approved way'. It got very frustrating. Especially when recompiling a couple of key libraries made a noticeable difference in the speed of the system.
Bloatware is my biggest problem with most distros. They seem to want to install *everything* that is in any way open source. So the first thing you end up doing after every install is stripping tons of un-needed things out. Then if you accidentally strip out some dependency the whole system pretty much just ends and you sit there thinking 'what did I screw up this time'. My biggest peeve is openoffice. I have a windows computer with office on it. I do not need a knockoff copy, yet I end up with one all the time. So I end up picking a mini distro and its too far the other way and you spend hours digging around trying to find the right incantations to get a working X system with a GUI that is not completely broken and missing the most basic of utilities like resizing the screen.
(Score: 1, Informative) by Anonymous Coward on Sunday May 22 2016, @08:04PM
tl;dr
your post basically indicates that you're clueless; thanks for trying.
(Score: 0) by Anonymous Coward on Monday May 23 2016, @05:35AM
Interesting. Why do you feel that way? Because I think the way distros are made and rotting on the vine is a problem? Or do you care not for any sort of real security in your system?
(Score: 2) by MichaelDavidCrawford on Sunday May 22 2016, @08:36PM
It's an Open Source clone of the BeOS [haiku-os.org]. BSD-licensed. Pay no attention to the fact that it's not beta yet; the stuff that really matters is quite stable, it's just that they keep trying out new ways to tile windows.
I've been using it for years and have only rarely had trouble with it. You're more likely to crash a hard drive than lose a file due to a bug.
Yes I Have No Bananas. [gofundme.com]
(Score: 0) by Anonymous Coward on Sunday May 22 2016, @09:05PM
I've wondered a bit about that OS (but never got ambitious enough to actually try it).
Do you recall the size of your ISO?
How is the state of default apps|repos?
Ever have to compile an app from source?
Where did you get the source?
-- OriginalOwner_ [soylentnews.org]
(Score: 2) by MichaelDavidCrawford on Tuesday May 24 2016, @01:47AM
I've only compiled from source when I've been contributing to the development.
BeOS didn't have a real package manager; Haiku does.
The default apps are most of what you need, however I don't really like Pe, the "Programmer's Editor". I'd rather use vi, which does not come by default.
It has a posix layer so most *NIX apps will build out of the box. Some are included by default.
Haiku's source is at http://cgit.haiku-os.org/ [haiku-os.org]
There are nightly automated builds. Most of them are quite stable. Download the latest nightly, it will probably be OK for you.
It runs fine in a VM if you just want to try it out. It can run natively on lots of hardware, but I expect the need for more drivers is why it's not beta yet.
Yes I Have No Bananas. [gofundme.com]
(Score: 0) by Anonymous Coward on Tuesday May 24 2016, @09:14AM
has a posix layer so most *NIX apps will build out of the box
Cool.
the need for more drivers
When it comes to hardware, I've thought of Linux as one of The Big 3 for quite some time.
gregkh and the Linux Driver Project guys have Linux users quite spoiled.
Thanks for the info.
-- OriginalOwner_ [soylentnews.org]
(Score: 2) by MichaelDavidCrawford on Tuesday May 24 2016, @02:30PM
Linux drivers could be informative were they not such rats' nests.
Yes I Have No Bananas. [gofundme.com]
(Score: 0) by Anonymous Coward on Wednesday May 25 2016, @12:40AM
This guy wasn't an experienced device driver hacker as such but he tweaked what he had enough to get his new gadget going.
Adding an unsupported resolution [googleusercontent.com] (orig) [goodbyemicrosoft.net]
That one was clearly not -that- big a mess.
...and, of course, I'll take *something* over what the closed-source stuff offers any day.
-- OriginalOwner_ [soylentnews.org]
(Score: 2) by Azuma Hazuki on Sunday May 22 2016, @10:36PM
Arch is really very easy, and surprisingly stable for something that has a reputation for being bleeding-edge. I use it on my personal machine specifically because it's both easy and completely bloat-free (and because Gentoo on a mobile Core 2 Duo is made of pain). Try it.
That incantation, by the way, is "pacstrap /mnt xorg xorg-xinit xfce4 lightdm lightdm-gtk-greeter" during the install phase :)
I am "that girl" your mother warned you about...
(Score: 0) by Anonymous Coward on Monday May 23 2016, @03:42AM
For slack it was the package manager that needed some work done to it.
Cool story, bro'
Slackware does not have, nor has it ever had, a package manager. If you had actually ever used Slackware, you would know this.
So, you're a liar.
Bloatware is my biggest problem with most distros.
and
My biggest peeve is openoffice.
A full install of Slackware (which is recommended) will use about 8G of your precious hd. You are given choices as to which DE or WM you wish to run, as well as which services/daemons you wish to run. This is hardly "Bloatware"
Open/Libre office is not part of the Slackware installation.
Perhaps next time you post, perhaps you should just tell us that you once opened a can of creamed corn with a can opener. That might be the closest you'll ever come to actually telling the truth about anything.
(Score: 0) by Anonymous Coward on Monday May 23 2016, @04:42AM
Slackware has had a package manager for most of its life. What it lacks is dependency resolution.
(Score: 0) by Anonymous Coward on Monday May 23 2016, @06:03AM
8 gig? You see no problem with that? You see nothing wrong with 8 GIG of attack surface for an OS that should be 50-200 meg at most? Sure I can pick a-X and just sit right back while it installs all sorts of things I will never use and spins up services I dont need.
Slackware does not have, nor has it ever had, a package manager.
I can tell *YOU* have never used slackware in a serious way. I have been using it since the mid 90s. It has a *very* simplistic package/install manager. Basically tgz files with an extra catalog file. Thats it. The dependency manager stinks. The upgrade manager stinks. The only thing I like about it is that it is 'simple'. Its init system is 'ok' but very simplistic. It is nice if you want to do something fancy but that is rarely needed these days. The couple of times I have seen someone attempt to fix it the community flipped out on the poor soul who did it. It became clear in the early 2000s it was *never* going to be resolved.
On the flip side you have things like apt which seem to drag in the kitchen sink with the smallest app. No one sees a problem with that? I either get 'compile and hope it works' all the way to 'here is a half gig of libraries and an app'. Oh it 'works'. But why not do better?
Maybe upgrade has gotten better over the years. I however got tired of 'just reinstall the whole thing' to get an upgrade to work correctly with slack. I gave up around 2005.
Now dont get me wrong. Slack is amazing. But it has some serious issues. Many distros do. My biggest complaint is security patches being ignored on many of the distros. The only ones making a half an attempt at it are the rolling distros. Yet then you end up with bleeding edge 'wopsie sorry your system is fucked again' all the time.
Everyone keeps saying 'oh this year'. Linux's year was *YEARS* ago. Its called android. The desktop belongs to MS and Apple. It took a semi locked down distro from google for linux to succeed. It is why docker is killing it in the server market. Small distro with plugins of exactly what people want instead of heavy servers behind massive VM infrastructures. Yet no one seems to think an end user would like that too and just labels them 'troll'.
(Score: 2) by Reziac on Monday May 23 2016, @05:16AM
Normally I'd agree with you... ironically, last time I toured the current distros, the one I liked best was PClinuxOS-FullMonty, which installs everything including the kitchen sink, the bathtub, the toilet, and a sauna at your neighbor's house.
And there is no Alkibiades to come back and save us from ourselves.