Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
What should we do about systemd?
Re: What should we do about systemd?
I'm just gonna go retro Debian, stick with Wheezy or Wheezy-based, that's good for a couple more years.
Plenty of time to learn Slackware and just, in general, to wait and see. A lot can happen in the next two or three years.
I'm hopeful there will still be Linux solutions. Maybe even Debian ones.
Plenty of time to learn Slackware and just, in general, to wait and see. A lot can happen in the next two or three years.
I'm hopeful there will still be Linux solutions. Maybe even Debian ones.
Last edited by fleabus on 2014-11-25 01:26, edited 2 times in total.
Lenovo Legion 5-15IMH05 32GB Ram, 2TB Samsung 970 EVO Plus NVMe SSD
Re: What should we do about systemd?
I'm starting to agree, installed Mint 17 Xfce on my old machine, the only positive thing is it has DVDStyler, other than that, I can feel the virusd bugs, it's heavily infested, gkrellm seems 'jailed' like on a BSD system, the only sensor values accessible to tweak (offsets) are the HDD temps, everything else is locked, this isn't a huge issue but even on my new machine in Wheezy, grkrellm works perfectly and all values are accessible. Even simple things in Mint like adding icons or wallpaper to the appropriate directories is a chore now, it feels like excessive permissions lock-down.fleabus wrote:I'm just gonna go retro Debian, stick with Wheezy or Wheezy-based, that's good for a couple more years.
Plenty of time to learn Slackware and just, in general, to wait and see. A lot can happen in the next two or three years.
I'm hopeful there will still be Linux solutions. Maybe even Debian ones.
Edit: I transcoded the same video file with Bombono (available in dmo) on my new machine in Wheezy, it did a better job than DVDStyler in Mint 17 (with virusd) on my old machine (hardware is of no consequence here, they are both very capable machines), I may wipe the fresh install of Mint off my old machine and install Wheezy on it too, I disabled the splash in Mint and 'un-hid' Grub (everybody is really Window-izing things these days, grrr), you should see the Poett-hat-ware virus scrolling by, 'strangling' everything, it's disgusting.
Edit 2: Judging by the way things are going/looking, I'll be forced back to KDE on PC-BSD, I know they offer Xfce, which I tried, it's OK but a little buggy, I've always found most distros' default DE is the best supported and implemented. It really burns my @$$ that I may have to give up my fakeraid on both my old and new machines, I hate being forced in to a corner, grrrrrr.
Last edited by Linadian on 2014-11-05 22:03, edited 3 times in total.
Linux Registered User 533946
-
- Posts: 459
- Joined: 2013-06-16 00:10
Re: What should we do about systemd?
This is basically my path, with a slight bias towards *BSD. On the topic of Slackware, assuming parasited roots itself deeply enough into the kernel, would it even make sense to switch to a Linux-based distro? (This has been a widely-discussed topic as of late, but I know very little about how slackware differs from, say, Debian.)fleabus wrote:I'm just gonna go retro Debian, stick with Wheezy or Wheezy-based, that's good for a couple more years.
Plenty of time to learn Slackware...
the crunkbong project: scripts, operating system, the list goes on...bester69 wrote:There is nothing to install in linux, from time to time i go to google searching for something fresh to install in linux, but, there is nothing
- oswaldkelso
- df -h | grep > 20TiB
- Posts: 1497
- Joined: 2005-07-26 23:20
- Location: UK
- Has thanked: 1 time
- Been thanked: 60 times
Re: What should we do about systemd?
Free Software Matters
Ash init durbatulûk, ash init gimbatul,
Ash init thrakatulûk agh burzum-ishi krimpatul.
My oldest used PC: 1999 imac 333Mhz 256MB PPC abandoned by Debian
Ash init durbatulûk, ash init gimbatul,
Ash init thrakatulûk agh burzum-ishi krimpatul.
My oldest used PC: 1999 imac 333Mhz 256MB PPC abandoned by Debian
- keithpeter
- Posts: 502
- Joined: 2009-06-14 08:06
- Location: 5230n 0155w
Re: What should we do about systemd?
Slackware 14.1 default install comes in at around 8Gb including KDE/XFCE and a few other thinner window managers. The large default install is one way round the lack of dependency resolution when using the 'provided' package managers. You compile 'slackbuilds' to add other programs, not difficult but can take a bit of time on older hardware. The slackers are a pragmatic bunch not given to drama. If it becomes impossible to provide a decent desktop without systemd, they will include it. But just enough of it to make KDE workn_hologram wrote:This is basically my path, with a slight bias towards *BSD. On the topic of Slackware, assuming parasited roots itself deeply enough into the kernel, would it even make sense to switch to a Linux-based distro? (This has been a widely-discussed topic as of late, but I know very little about how slackware differs from, say, Debian.)fleabus wrote:I'm just gonna go retro Debian, stick with Wheezy or Wheezy-based, that's good for a couple more years.
Plenty of time to learn Slackware...
OpenBSD is an 'interesting' experience - similar to Linux but different in many details. I'm writing this on an OpenBSD 5.6 install on the test laptop with XFCE4 running with ConsoleKit, dbus, the hotplug daemon and 'toad', a little daemon that handles auto-mounting usb sticks and CDs. I'm puggling round the man pages trying to work out why the USB CD-ROM isn't auto-mounting. You get the picture.
Re: What should we do about systemd?
So where will that leave KDE loving PC-BSD?! So Poett-hat-ware will force the KDE folks to write KDE around virusd? The BSDs won't be happy if this ugly scenario plays out, unless KDE release two versions, virusd friendly and a non-virusd version. This is getting bloody ridiculous.keithpeter wrote:If it becomes impossible to provide a decent desktop without systemd, they will include it. But just enough of it to make KDE work
Linux Registered User 533946
Re: What should we do about systemd?
@keithpeter: as you are already testing OpenBSD you could also test FreeBSD. It's binary packages make life a lot more easy than OpenBSD. And if I understood correctly, there is KDE4 for FreeBSD.
Re: What should we do about systemd?
+1 to keithpeter here... I haven't yet screwed up the courage to try the BSDs, although I'm giving them a hard look. For me, going with Slackware has to do with my hope that after all this shakes out in the next couple of years there'll still be Linux solutions. After starting out with Slackware I moved on to Salix, which has as its major advantage its placement as "Slackware for lazy Slackers" to which I would add lazy Debian refugees, amongst which you may count me... In addition to dependency resolution with slapt-get, gslapt, and sourcery, it now has a nifty little command "spi", short for Salix Package Installer.n_hologram wrote:....would it even make sense to switch to a Linux-based distro? (This has been a widely-discussed topic as of late, but I know very little about how slackware differs from, say, Debian.)keithpeter wrote:You compile 'slackbuilds' to add other programs, not difficult but can take a bit of time on older hardware. The slackers are a pragmatic bunch not given to drama. If it becomes impossible to provide a decent desktop without systemd, they will include it. But just enough of it to make KDE work
http://guide.salixos.org/321SalixPackag ... html#4_2_1
It was written by the distro maintainer, George Vlahavas, and checks for both available binaries and available slackbuilds. For me, Salix has proved to be kind of addictive.
I also have hope that KDE might choose to remain somewhat above this stuff, since they supply builds for many different systems and architectures. I'm betting that keeping it going sans sysd won't be too much of a problem for the Slackers. I'll try to dig up links, I was reading some hopeful posts by KDE devs... I've been reading so much on this stuff lately that I haven't had time for much else.. I also have hopes that Xfce may find a way.
My hopes may prove to be irrational, but they'll do for the next couple of years. I'm in search, meanwhile, of a good used crystal ball, if anyone happens to stumble over one on their way to the latrine...
Lenovo Legion 5-15IMH05 32GB Ram, 2TB Samsung 970 EVO Plus NVMe SSD
Re: What should we do about systemd?
[removed by::fleabus]
Last edited by fleabus on 2014-11-25 01:12, edited 1 time in total.
Lenovo Legion 5-15IMH05 32GB Ram, 2TB Samsung 970 EVO Plus NVMe SSD
- keithpeter
- Posts: 502
- Joined: 2009-06-14 08:06
- Location: 5230n 0155w
Re: What should we do about systemd?
Salix is lovely, and I went Salix -> Slackware on the 'typing box' (the old Dell E5420 laptop that just works when I need to produce *stuff*, thanks to oswaldkelso for mini review, I got a cheap sample off ebay for 15 brown ones).fleabus wrote:After starting out with Slackware I moved on to Salix, which has as its major advantage its placement as "Slackware for lazy Slackers" to which I would add lazy Debian refugees, amongst which you may count me... In addition to dependency resolution with slapt-get, gslapt, and sourcery, it now has a nifty little command "spi", short for Salix Package Installer.
If 2020 is your kind of horizon, have a look at Stella Linux 6. A 'remix' of CentOS 6 by NuX, you get a live hybrid iso that has all the codecs/flash/ms fonts installed and ready to go and support for many wifi cards (CentOS, Epel, ElReopo and NuX desktop repositories) along with Gnome 2.30. I keep a live version on a USB stick for emergencies.
Re: What should we do about systemd?
Thank you Keith, I didn't even know it existed. I've zero experience with rpm, besides some messing about with Mandrake 7 back in '00. I never got anywhere with it. This does look interesting, I'll have to get the live version and add it to the todo list....keithpeter wrote:If 2020 is your kind of horizon, have a look at Stella Linux 6. A 'remix' of CentOS 6 by NuX, you get a live hybrid iso that has all the codecs/flash/ms fonts installed and ready to go and support for many wifi cards (CentOS, Epel, ElReopo and NuX desktop repositories) along with Gnome 2.30. I keep a live version on a USB stick for emergencies.
Lenovo Legion 5-15IMH05 32GB Ram, 2TB Samsung 970 EVO Plus NVMe SSD
Re: What should we do about systemd?
Yes, I thank you too Keith, gunna check out Stella (DistroWatch's Stella 6 package list), looks and sounds interesting, I don't care if it's 'retro-ware' (Debian Wheezy is not exactly cutting edge either, lol), as long as it works and it's supported, and it's still virusd free...until at least 2020, I hope. At least now I have my old machine to test distros, I'm sniffing around FreeBSD too, I didn't know they had binaries, PC-BSD without all the branding.keithpeter wrote:Salix is lovely, and I went Salix -> Slackware on the 'typing box' (the old Dell E5420 laptop that just works when I need to produce *stuff*, thanks to oswaldkelso for mini review, I got a cheap sample off ebay for 15 brown ones).fleabus wrote:After starting out with Slackware I moved on to Salix, which has as its major advantage its placement as "Slackware for lazy Slackers" to which I would add lazy Debian refugees, amongst which you may count me... In addition to dependency resolution with slapt-get, gslapt, and sourcery, it now has a nifty little command "spi", short for Salix Package Installer.
If 2020 is your kind of horizon, have a look at Stella Linux 6. A 'remix' of CentOS 6 by NuX, you get a live hybrid iso that has all the codecs/flash/ms fonts installed and ready to go and support for many wifi cards (CentOS, Epel, ElReopo and NuX desktop repositories) along with Gnome 2.30. I keep a live version on a USB stick for emergencies.
Just a heads up for those going to download Stella, I hope you have some patience, the London (England) server to Canada was about 400KB/s download speed on average. Poke around the download server for 6.6, the DistroWatch Stella page says 6.5, that's old info.
Edit: Test live run of Stella 6.6 on my old machine (Q9550, 8GB DDR2, 4 HDD ICH10R Raid 0, Nvidia, etc), check out the pic, see for yourself (fakeraid was auto detected, that means an install to it), a clean well rounded distro, tons of functionality and settings, very stable. I regret poo-pooing old Gnome 2.x in the past, it acutally feels like Xfce on steroids, you have to get used to where things are but that's no big deal.
Click on the pic after it loads to go full size...
Linux Registered User 533946
- keithpeter
- Posts: 502
- Joined: 2009-06-14 08:06
- Location: 5230n 0155w
Re: What should we do about systemd?
Some of us dream of speeds like thatLinadian wrote: Just a heads up for those going to download Stella, I hope you have some patience, the London (England) server to Canada was about 400KB/s download speed on average.
http://gnewsense.org/
Fully free deblobbed kernel, no proprietary drivers for wifi or nvidia &c. The 'Parkes' release is based on Debian Squeeze so familiar territory for most of us. Sam Geeraerts pops out updates, but applications *not* backported (Iceweasel 3.5, OpenOffice 3.x &c). The forthcoming Ucclia release will be Wheezy based.
- keithpeter
- Posts: 502
- Joined: 2009-06-14 08:06
- Location: 5230n 0155w
Re:
Well, the poll shows that yours is the majority opinion! Based on the Sid installation on my test laptop, Jessie's Gnome desktop will be a lot of fun. Enjoy.yzT wrote:I really don't understand what's the problem.
Try changing the sentence above toyzT wrote:If all major distros, Debian included, are either using or planning to use systemd, it can't be as bad as you say.
and see how it feelsnobody actually said this wrote:If all major [companies], [my company] included, are either using or planning to use [Windows], it can't be as bad as you say.
Seriously: we'll find out in a year or five. I'm sure Red Hat will *make* it work (same way that Microsoft have been *making* Windows work year after year with layer upon layer of code).
- Hallvor
- Global Moderator
- Posts: 2042
- Joined: 2009-04-16 18:35
- Location: Kristiansand, Norway
- Has thanked: 151 times
- Been thanked: 212 times
Re:
You don't understand the problem with people restricting other people's freedom of choice, and then calls them a**holes if they object?yzT wrote:I really don't understand what's the problem.
http://www.linux-magazine.com/Online/Ne ... bout-Rants
This is nothing more than appeal to popularityIf all major distros, Debian included, are either using or planning to use systemd, it can't be as bad as you say.
http://www.logicalfallacies.info/releva ... opularity/
[HowTo] Install and configure Debian bookworm
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
Debian 12 | KDE Plasma | ThinkPad T440s | 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz | 12 GiB RAM | Mesa Intel® HD Graphics 4400 | 1 TB SSD
-
- Posts: 183
- Joined: 2014-10-27 21:28
Re:
In that case stay silent.yzT wrote:I really don't understand what's the problem.
The rest you posted was already commented. Not sure if it is worth a comment at all. If someone doesn't realize that he can ignore gnome, or even the GUI altogether, in case he doesn't like it, then further discussion doesn't seem to offer any gain. Hence my advice: Stay silent.
Give me convenience or give me death.
Re:
Then you either don't understand FOSS or have no clue how to read or use a search engine.yzT wrote:I really don't understand what's the problem.
Poettering is a PAID employee of Redhat, a corporation who's interest is to make money off of Linux, and it seems, control the rest of Linux world with their code. Poettering has tried to bully, guilt or shame Linus Torvalds in to injecting buggy code in to the Linux kernel to make virusd work and 'standardize' virusd. That's not the way the Linux world works, you get the vanilla kernel, you build around it, if you can't, that's YOUR problem. If Redhat and Poettering want a proprietary kernel, then let them build their own, not FORCE it on to the rest of us. Do some reading, get enlightened, there are aspects of virusd that don't sit well with a lot of people, like it wants to CONTROL almost everything on your system, the logs are opaque in binary form, it's not easily tweakable, etc, etc, etc. This is not in line with the GNU philosophy, if I want secretive blobs on my machine, I'd go back to Windows, this blob (virusd) also has the potentional to become an NSA backdoor spyware (it controls your networking, hmmm), this is not a tinfoil hat rant, corporations have been approached by the NSA and are cooperating with them. Get a clue or go back to Windows.
Edited for grammar and spelling.
Linux Registered User 533946
- keithpeter
- Posts: 502
- Joined: 2009-06-14 08:06
- Location: 5230n 0155w
Re: Re:
I'm all for people getting paid, and all for making money of both Linux and GNU and other GPLed code. More power to them, for they are implementing Richard Stallman's vision and refuting Bill Gates and (more recently) Jaron Lanier's position. And, as edbarx always likes to point out, we have the source codeLinadian wrote:Poettering is a PAID employee of Redhat, a corporation who's interest is to make money off of Linux...
Linadian wrote:[...]and it seems, control the rest of Linux world with their code.
Nope, I genuinely think Lennart is just trying to deliver stuff that works for Red Hat and others. I suspect that it is the lack of other companies contributing that has lead to the huge tidal field that the systemd group are exerting.
We might not like systemd and the wider system (e.g. kdbus) but it is *not* proprietary. Lennart and his chums are 100% transparent and posting their code, unlike, say, nvidia. Their code is all GPLed. Can we try to keep the technical structure argument separate from the licence argument please? Otherwise the systemd people can claim FUD. See my earlier posts about how the the narrative is being constructed.Linadian wrote:If Redhat and Poettering want a proprietary kernel, then let them build their own, not FORCE it on to the rest of us.
-
- Posts: 183
- Joined: 2014-10-27 21:28
Re: What should we do about systemd?
On a side note:
"but it is open source"
is getting old.
It has become clear, long before systemd, that being open-source isn't enough (Ubuntu-Amazon, anyone? As one example).
Others have explained that in better words than i ever could.
Not sure why you call L. Poettering Lennart. Do you know him personally?
People tell FUD all the time anyway, no matter what the opponents say (not that i would be too happy with most comments about systemd, but that fear, we won't be taken serious, is not necessary. We are not taken serious, this way or the other. Example: I can't see how being a company is a bad thing per se --- One in NSA-land is another thing, of course ).
"but it is open source"
is getting old.
It has become clear, long before systemd, that being open-source isn't enough (Ubuntu-Amazon, anyone? As one example).
Others have explained that in better words than i ever could.
Not sure why you call L. Poettering Lennart. Do you know him personally?
People tell FUD all the time anyway, no matter what the opponents say (not that i would be too happy with most comments about systemd, but that fear, we won't be taken serious, is not necessary. We are not taken serious, this way or the other. Example: I can't see how being a company is a bad thing per se --- One in NSA-land is another thing, of course ).
Give me convenience or give me death.