Re: Google Chrome can share but Chromium cannot share screen
On Sun, 2022-09-11 at 10:26 +0200, Corentin Bardet wrote: > Hi, > > Le 2022-09-11 07:39, Pankaj Jangid a écrit : > > For a few work related meetings, I have to use Google Meet. But the > > screensharing doesn't work in the Chromium installed from stable APT > > repository. Clicking on the share-screen icon and then selecting any of > > the three options - Tab, Windows, Entire Screen - shows this error > > message, > > > > "Your browser can't share your screen" > > > > But if I install and use Google Chrome, then the screen sharing works > > in > > Google Meet. > > That doesn't surprise me much. > > Google removed the majority of its APIs from Chromium : > [here]( > https://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrom > e) > and > [here](https://www.omgubuntu.co.uk/2021/01/chromium-sync-google-api-removed) > > Maybe screen sharing was a Google thing. Especially screen sharing to > Google Meet. > > I think you have no other option than using Google Chrome for your > meetings. O r u s e J i t s i ! SteveT
Re: Avoiding SystemD isn't hard
On Tue, 21 Oct 2014 19:09:39 -0400 Miles Fidelman mfidel...@meetinghouse.net wrote: Brian wrote: On Tue 21 Oct 2014 at 15:01:18 -0400, Steve Litt wrote: On Tue, 21 Oct 2014 17:19:08 +0200 Liam Proven lpro...@gmail.com wrote: A blog post explaining why it isn't mandatory, the utter futility of the fork and more besides, clearly and simply. http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html What I really like about the blog is that, almost from the beginning, the author lets us know his agenda with words like trolls. And, just to make his point with his non-cognizant readers, he quotes Gregory Smith as just another anti-systemd-troll, instead of as a guy all of the anti-systemd people have repudiated and disavowed all alliance with. Have all the anti-systemd people repudiated Gregory? Here is one who embraces him as part of the fold: https://lists.debian.org/debian-user/2014/10/msg00287.html Gregory, please don't do this. It hurts the credibility of the entire group who agrees with you 100% on the issues. There are enough *facts* about systemd, Poettering, Sievers and Redhat to logically and completely make your point. The group agrees with you 100% . Does that look like repudiation and disavowed all alliance with? It seems more like trying to get someone to toe the Party line. Just for the record, just because someone is a little over-the-top in his language, doesn't make him wrong. Miles Fidelman I guess that's what I get for /dev/null'ing Brian long before the systemd thing ever started (my .procmailrc notes say Rude boy Brian who thinks he's funny). Anyway, as Brian knows full well if he researched my ancient advice to Gregory, about two days later I publically repudiated Gregory. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141022020034.56cd4...@mydesq2.domain.cxm
Re: If Not Systemd, then What?
On Tue, 21 Oct 2014 18:41:21 -0700 Patrick Bartek nemomm...@gmail.com wrote: On Mon, 20 Oct 2014, Steve Litt wrote: On Mon, 20 Oct 2014 12:45:11 -0700 Patrick Bartek nemomm...@gmail.com wrote: After much vitriolic gnashing of teeth from those opposed to systemd, I wonder... What is a better alternative? * Nosh * Runit * Upstart * S6 * Probably more I don't know about. OpenRC, God, and another one -- I can't recall the name -- come to mind. Been studying them all. Runit as a partial or full drop-in replacement for sysvinit seems promising. And it can't be sysvinit. Yes. Syvinit still works, but it is after all 20 years old. It's been patched and bolted onto and jury-rigged Nobody's arguing for sysvinit as a long term solution, for the exact reasons you post above. Those of us who appeared to favor sysvinit were saying let's wait until we have something good. We also pointed out the false choice of prematurely narrowing it to systemd, Upstart or sysvinit. This I realize, but for some something good is never ever good enough to replace the old, the familiar, the comfortable. I spoze. But there's little good about systemd, and a whole lot of bad. Like I listed near the beginning of this thread, there are plenty of something goods that I'd gladly replace sysvinit with. But systemd is a catastrophe if you want a computer controlled by you and not Red Hat. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141022020458.55d17...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Tue, 21 Oct 2014 08:25:31 +0200 Ludovic Meyer ludo.v.me...@gmail.com wrote: On Mon, Oct 20, 2014 at 04:49:48PM -0400, Ric Moore wrote: On 10/20/2014 02:35 PM, Andrei POPESCU wrote: If you mean you are actually DOSing Debian's support channels just to make you're point that's likely to get you banned instead, besides not achieving anything. ~OR!~ List archives get refreshed every 20 minutes. is a more likely reason for the list to go down just for a bit, especially with the higher than normal activity. I doubt any of the 4chan types to give a whit, one way or the other, as we're not exactly clubbing baby seals here. Maybe there is a GNU/Low Orbit Ion Cannon?? That would be more likely. chuckles :) Ric You must have missed the memo : http://www.vitavonni.de/blog/201410/2014101801-beware-of-trolls---do-not-feed.html The subject of the preceding article link hasn't posted in several days. I know that because, no matter what name he uses, his posts are immediately recognizeable. So what's the purpose of your putting this link in your email? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021025038.4a3b5...@mydesq2.domain.cxm
Re: LSB headers and other junk, how do you hack a quick init script in debian these days?
On Tue, 21 Oct 2014 08:41:19 +0200 Michael Ole Olsen g...@gmx.net wrote: Who needs to document their own pc they hack on daily? suddenly I couldnt just place a script in rc2.d folder anymore, needed to symlink needed to add an lsb header too it seems maybe I'm overlooking something I prefer to hack on my own without using debian tools, update-rc.d i.e. would be nice to be able to place a script in rc2.d folder again, even though it isn't a symlink it seems that 'feature' has been removed in the new debians I wouldn't do it at work/anywhere where documentation is important though but why force people to document / use the right tools? I prefer an OS that is easy to hack around debian init scripts is something that frustrates me often, because I can't just hack them easily need to symlink in different folders or use the debian tool got no experience with sysV or whatever it uses, only bash programming which I am fairly good with so it frustrates me that hacking initscripts should be so annoying at times :P it used to work good back in the days, I could just add an S99mio and that would get executed after booting not anymore, now it needs to be symlinked and all it seems there used to be an /etc file one could edit to make boot scripts anyone remember which one? rc.local or such I think, but not sure anymore, debian has changed a bit lately it seems How do you hack a quick init script these days?:) If it's something that can be done at the end of the boot, I'd recommend daemontools. Unlike both systemd and sysvinit, your daemons are under perfect control, and controlling them is zombie-simple. If you want, I can even tell you how to control which order daemontools starts its stuff up in, although that would be a kludge and it would start looking a little like sysvinit scripts. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021025354.27d83...@mydesq2.domain.cxm
Re: If Not Systemd, then What?
On Tue, 21 Oct 2014 08:12:17 +0200 Ludovic Meyer ludo.v.me...@gmail.com wrote: On Mon, Oct 20, 2014 at 09:34:48PM -0400, Steve Litt wrote: On Mon, 20 Oct 2014 12:45:11 -0700 Patrick Bartek nemomm...@gmail.com wrote: After much vitriolic gnashing of teeth from those opposed to systemd, I wonder... What is a better alternative? * Nosh So this one is fun, it is just a direct copy of the systemd service format. Guess the proof that's at least a feature that people do want, dropping shell. I think you meant a direct copy of daemontools, didn't you? http://homepage.ntlworld.com/jonathan.deboynepollard/Softwares/nosh.html It's not a direct copy, it's an enhanced superset of daemontools, kind of. Daemontools preceded systemd by several years, and I sincerely doubt daemontools and systemd have anything in common. And of course, not only the format is copied, it took the set of systemd services and copied them like this. I am sure ftp-masters wouldn't accept a GPL violation ( as the .service file are likely not un the BSD ). Daemontools wasn't GPL'ed, it was Public Domained, so anyone can do absolutely anything with it. * Runit was non free for a long time, not sure if developped anymore, especially since last post on one of the ml date back to June 2013. Funtoo is using it, and I seriously doubt they'd be using something not developed anymore. * Upstart no longer developped, and suffer from several bugs, go read the tech-ctte debate. I read it, and if Upstart problems were the most distressing thing in that debate, I'd be a happy man. If Upstart is no longer under development, the reason would be that the Debian CTTE decided on systemd, so Cannonical reluctantly followed suit. * S6 likely the same as runit when it come to be alive. * Probably more I don't know about. You could add openrc, the only serious contender. Thanks. I hereby add openrc, assuming it's ready now. And it can't be sysvinit. Yes. Syvinit still works, but it is after all 20 years old. It's been patched and bolted onto and jury-rigged Nobody's arguing for sysvinit as a long term solution, for the exact reasons you post above. Those of us who appeared to favor sysvinit were saying let's wait until we have something good. We also pointed out the false choice of prematurely narrowing it to systemd, Upstart or sysvinit. You mean let's do like we did since 20 years, wait, in case if something will happen. None of the alternatives you propose have been widely adopted by anyone except upstart. And that's mostly because no one cared about them up to the point to even propose them. The reason nobody paid attention to them yet is the alternative wasn't systemd until now. systemd is a mighty motivator, I'll say that for it. Now of course, the systemd cabal will argue that we can't wait any longer. My question to them is, why was sysvinit not a dire emergency until Red Hat's systemd juggernaut came along, and then all of a sudden we just couldn't wait? You mean that after waiting several years, the solution is to wait again, because no one cared before, That is *exactly* what I mean. Don't move to a worse position, and if this had really been life or death, systemd would have been gone a few years ago. and when 1 group came and changed, the solution is to refuse and go back doing nothing ? Now that, I didn't say. Go back and read the quoted text. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021024646.04540...@mydesq2.domain.cxm
Re: If Not Systemd, then What?
On Tue, 21 Oct 2014 09:11:32 +0100 Jonathan Dowland j...@debian.org wrote: Hi, Please do not top-post. On Tue, Oct 21, 2014 at 05:27:34AM -0200, Martinx - ジェームズ wrote: If uselessd provides ONLY a new init, based on CGroups and lots of cool ideas from systemd itself, then, it worth trying it! Just for fun... I think it's an interesting project and I might contribute towards the packaging, so long as it's a team effort, but currently nobody has taken ownership of the 'request for package' bug, so there is almost no chance of uselessd being a part of jessie. (it would have to be packaged, uploaded and pass NEW in under 2 weeks.) Hey Jonathan, First, if you do contribute to uselessd, thank you very much. I want to make sure I'm reading your paragraph correctly: The Debian uselessd package cannot be finished in time to make it into Jessie, so there will be no uselessd package in Jessie. Is that correct? Let's say that, in six months from now, Debian's uselessd package is ready for prime time. Would there be any reason some enterprising person couldn't simply copy it to another repository (hopefully a trusted one), so that people could add that repository and thus install uselessd on Jessie? Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021140253.264d0...@mydesq2.domain.cxm
Re: Refracta systemd-free progress
On Tue, 21 Oct 2014 09:16:50 +0100 Jonathan Dowland j...@debian.org wrote: On Mon, Oct 20, 2014 at 07:39:06PM -0500, goli...@riseup.net wrote: Check out the outstanding progress that fsmithred and dzz are making with a systemd-free Refracta: This is off-topic for the Debian User mailing list. Please stick to on-topic discussions. https://www.debian.org/MailingLists/#codeofconduct This is true, golinux. It violates the very first element of the rules, because it doesn't foster development and use of Debian. So, if I were you, I'd rephrase it thusly... === Check out the outstanding progress that fsmithred and dzz are making with a systemd-free Refracta. I think that similar construction can greatly benefit Debian: === SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021140726.51d8d...@mydesq2.domain.cxm
Re: If Not Systemd, then What?
On Tue, 21 Oct 2014 10:18:49 +0200 Raffaele Morelli raffaele.more...@gmail.com wrote: Here are some interesting things one should be aware of before http://0pointer.de/blog/projects/the-biggest-myths.html We've all read that. My favorite Poettering manifesto is the one where he talks of systemd subsuming packaging systems: http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html Read enough about but still haven't read something really valuable against systemd from eg. Torvalds, Eric Steven Raymond, etc... (if you do, post the link) Isn't this quote from ESR enough against systemd? http://en.wikipedia.org/wiki/Systemd#Reception very prone to mission creep and bloat and likely to turn into a nasty hairball over the longer term. As far as Torvalds, would this qualify as something really valuable against systemd? http://www.phoronix.com/scan.php?page=news_itempx=MTY1MzA Key, I'm f*cking tired of the fact that you don't fix problems in the code *you* write, so that the kernel then has to work around the problems you cause. I believe the main issue with systemd and the community mainly the badass-ness Badass is a complement. Poettering is just an ass. But if I used ass-ness as a filter on software I use, I wouldn't use anything RMS created, because he can be an ass, and I wouldn't use anything from the Linux kernel, because Linus can be an ass. Ass-authored software is used every day, by all of us. The thing is, asses like Linus and RMS don't have a roadmap to the destruction of the software ecosystem that created them (any more). of the guys in this init system war or whatever you prefer to address at. Using systemd since 2014-08-09 with no issues. Good for you. Let's see if you have no issues 2016-08-09, if Red Hat wins its war against Linux. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021143639.64ed9...@mydesq2.domain.cxm
Re: Avoiding SystemD isn't hard
On Tue, 21 Oct 2014 17:19:08 +0200 Liam Proven lpro...@gmail.com wrote: A blog post explaining why it isn't mandatory, the utter futility of the fork and more besides, clearly and simply. http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html What I really like about the blog is that, almost from the beginning, the author lets us know his agenda with words like trolls. And, just to make his point with his non-cognizant readers, he quotes Gregory Smith as just another anti-systemd-troll, instead of as a guy all of the anti-systemd people have repudiated and disavowed all alliance with. But putting the author's agenda aside for a moment, he pins his Avoiding systemd isn't difficult mantra on pinning. Umm, what happens three years from now if Ian Jackson's GR votes against choice? Oops! And once again, I thank Ian Jackson for doing the right thing, in spite of the difficulties it created for him, personally. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021150118.47e33...@mydesq2.domain.cxm
What actual program does the kernel run at boot in the default Jessie?
Hi all, In the past, I've been taught that the very last thing the kernel does during boot is run whatever program is called /sbin/init. And therefore, I can replace /sbin/init with the PID1 of my choice, always assuming I can connect the myriad of dots. In default new-installed Jessie, does the kernel still hand off to the program called /sbin/init during boot, or does it do something else? Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021151758.18662...@mydesq2.domain.cxm
Re: Good news on claws-mail
On Tue, 21 Oct 2014 00:58:27 +0200 lee l...@yagibdah.de wrote: berenger.mo...@neutralite.org writes: But my opinion is that, it's the accumulation of tools using different slow languages, which will kill the computer's resources (shell, python2, python3, php, perl, basic, whatever). Perl isn't exactly slow, considering what it does. In any case, pick the right tool for the job --- and I'm finding perl really amazing in some regards. For an interpreter (you know what I mean), when I used Perl it was fast as hell. You'd need to go to Lua or Luajit to get a faster interpreter. One of the first things I do when writing software is figure what the bottleneck is. If the bottleneck is the user's molassas slow 140 word per minute typing, I'll use an interpreter every time so I'm not the guy doing allocation and garbage collection and bounds checking. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021173704.2b55e...@mydesq2.domain.cxm
Re: msg from tornow....
On Tue, 21 Oct 2014 10:14:00 +1100 Andrew McGlashan andrew.mcglas...@affinityvision.com.au wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Thanks for the cc in this case, your message never made it to the list, it was /probably/ silently dropped changing the subject line to see if it helps *this* message to get through ;-) for the list *benefit* ... said email follows... On 21/10/2014 8:06 AM, tor...@riseup.net wrote: Do I want systemd ? - definitely and absolutely NO. Is there any point arguing here in debian-user ? - definitely NOT. My view is that systemd is a forgone conclusion and no-one whom has decided that it should be will be convinced otherwise. I cannot agree that systemd is better over sysvinit and I don't expect that to ever change. There is NOTHING wrong with sysvinit, there is something wrong with blaming sysvinit for other startup issues that had/have been done incorrectly. Same thoughts here. I made my choice and changed the distribution, after running Debian for 6 years. If needed, Poettering's ideas make it sound like that, i will even change the OS (obvious choice: BSD). I didn't make that choice lighthearted. Debian meant something to me. So Andrew, what did you move to? If I were just running a server, I'd have been using BSD years ago. But running a desktop, being able to run the programs I want to run is a real issue. Where did you go, and are you doing desktop/workstation, or server? Not arguing here, cause it won't bring a change, doesn't mean one doesn't care and won't make the according choice. And calling people who are worried about systemd trolls (and/or haters), worried because they *do* care about Debian, sure won't convince them to stay. LOL, they *want* us gone. They're feeling the juice right now, and haven't yet considered the frequent consequences of my way or the highway. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021174044.07a90...@mydesq2.domain.cxm
Re: What actual program does the kernel run at boot in the default Jessie?
On Tue, 21 Oct 2014 23:11:46 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Ma, 21 oct 14, 15:17:58, Steve Litt wrote: In default new-installed Jessie, does the kernel still hand off to the program called /sbin/init during boot, or does it do something else? Yes it does, unless you override it on the command line with an init= parameter. Good. That makes for easy experimentation. Thanks! SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021174325.0e1a6...@mydesq2.domain.cxm
Re: Avoiding SystemD isn't hard
On Tue, 21 Oct 2014 23:17:56 +0200 tor...@riseup.net tor...@riseup.net wrote: If one doesn't want systemd/libsystemd0, then Debian is not a good choice (having to tinker all the time one can just as well run one of the KISS distros). imho, of course. Debian *was* a KISS distro. That's why a lot of us migrated to it. Wheezy *is* a KISS distro. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021175049.2a071...@mydesq2.domain.cxm
Does Debian still have a systemd-must-die metapackage?
Does Debian still have a systemd-must-die metapackage, and does it still work in Jessie? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021184153.69f16...@mydesq2.domain.cxm
Re: Good news on claws-mail
On Mon, 20 Oct 2014 03:37:56 +0200 berenger.mo...@neutralite.org wrote: And, finally, I consider myself as a DE user. My DE is built by myself around a terminal-emulator, a tiling window manager, Which one? I use Openbox, which of course isn't tiling. and several applications, Such as? My main apps are: * Sigil * Bluefish * Iceweasel (I use xxxterm on Ubuntu) * Vim * VimOutliner * LyX * Gnumeric * LibreOffice Impress * The various programming languages * UMENU * dmenu but it's still a DE. A light one, an efficient one, a personal one, but it's my DE. :D An afficienado would argue with you that it's a DE only if the apps can all interact. Me, I'd prefer all my apps mind their own business, but hey, that's just me. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141020112909.10c00...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Mon, 20 Oct 2014 17:15:47 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Sb, 18 oct 14, 10:20:25, Joel Rees wrote: Does this help explain why what appears to some as mere turf battles and childish name-calling, etc., is a bit more than playground antics? Not to me. All these discussions could very well happen on the -offtopic list. Sure it can. Every single status-quo supporter in history has told protestors the same thing: If you want to ride on the front of the bus, petition the county, but don't do boycotts and civil disobediance. Yes, if we all wanted to have a polite discussion amongst ourselves, reaching nobody but those wanting to discuss cars, Obama, Ebola, and the Mideast, we certainly could go on the offtopic list. But we want to: A) Reach real people involved in the situation B) Build a community Frankly, telling us we can do it on the offtopic list is an insult to our intelligence. You know it, and we know it. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141020135237.39350...@mydesq2.domain.cxm
Re: Remember when men were men and wrote their own init scripts? =)
On Mon, 20 Oct 2014 15:34:43 -0200 Martinx - ジェームズ thiagocmarti...@gmail.com wrote: But please, guys, DO NOT LOSE *DEBIAN COMPILATION*!! I mean, when I read that infamous guy, Poettering, talking about things like this: http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html It creeps the hell outta me! [snip] So, is systemd even trying to replace dpkg+apt too? Come guys... For real?! [snip] Honestly, I don't fear systemd itself, or binary logs... I fear things like this: Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd: http://www.phoronix.com/scan.php?page=news_itempx=MTY1MzA Linux systemd dev says open source is 'SICK', kernel community 'awful': http://www.theregister.co.uk/2014/10/06/poettering_says_linux_kernel_community_is_hostil/ Thiago, Sadly, you ask the exact right question. Do we want Debian (and Linux) ruled by a megalomaniac who hates Linux, is determined to make it into something un-Linux, and wants all distros to be the same (copies of his employer's distro, no doubt). Systemd's architecture, which I personally find unwise, is nevertheless something that, from a technical standpoint, *could* be disentangled at a later date if it turns out to be as problematic as I think it will be. The real problem, which you put your finger square on, is that the architecture is simply a tool of monopolization. And, in fact, the megalomaniac is a proxy for his employer, Red Hat. Anybody who reads Poetterings writings, listens to his interviews, and doesn't come away with the idea that he wants to destroy what is currently Linux, and make sure it can never regenerate itself, isn't paying attention. Red Hat already had OpenSuSE, Fedora, CentOS, Mand* and all its descendants, and several others on its team already. Somehow, Arch and Sabayon fell for it too. If they conquer Debian, then Ubuntu and all the Debian and Ubuntu descendants fall, and Red Hat controls all of Linux. From there it's a simple matter to weld more and more onto their systemd (such as the packaging system), until regenerating the real Linux is no longer practical. Once they have a monopoly, they'll show much less regard for us than the CTTE ever did. Right now, this minute, Debian has the last clear chance to avoid the Poettering Vision, which is really the Red Hat strategy for Linux monopolization, which means destruction of the operating system we currently use. At this point, the technical issues are a minor thing. The big news is how humans are going to use those technical issues to replace our wonderful, almost POSIX OS with a Windows wannabe. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141020142250.56fb6...@mydesq2.domain.cxm
Re: If Not Systemd, then What?
On Mon, 20 Oct 2014 12:45:11 -0700 Patrick Bartek nemomm...@gmail.com wrote: After much vitriolic gnashing of teeth from those opposed to systemd, I wonder... What is a better alternative? * Nosh * Runit * Upstart * S6 * Probably more I don't know about. And it can't be sysvinit. Yes. Syvinit still works, but it is after all 20 years old. It's been patched and bolted onto and jury-rigged Nobody's arguing for sysvinit as a long term solution, for the exact reasons you post above. Those of us who appeared to favor sysvinit were saying let's wait until we have something good. We also pointed out the false choice of prematurely narrowing it to systemd, Upstart or sysvinit. Now of course, the systemd cabal will argue that we can't wait any longer. My question to them is, why was sysvinit not a dire emergency until Red Hat's systemd juggernaut came along, and then all of a sudden we just couldn't wait? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141020213448.6c545...@mydesq2.domain.cxm
Re: Refracta systemd-free progress
On Mon, 20 Oct 2014 23:33:23 -0400 Gary Dale garyd...@torfree.net wrote: On 20/10/14 08:39 PM, goli...@riseup.net wrote: Check out the outstanding progress that fsmithred and dzz are making with a systemd-free Refracta: http://refracta.freeforums.org/going-with-the-systemd-flow-or-not-t422-50.html#p4085 http://refracta.freeforums.org/going-with-the-systemd-flow-or-not-t422-60.html#p4086 Kudos to them!! Looking forward to giving this a spin before too long. If it makes you happy. Freedom of choice is one benefit of Linux. Personally, I like systemd and the fast boots it provides, plus the ease of administration. Gary, *Thank you* for actually saying something positive about systemd, rather than just telling us to shut up. I happen to believe that in the long run the entanglement isn't worth the benefits you mention, but that's just a difference of opinion between us, rather than the your opinion doesn't count type of thing. Jonathan de Boyne Pollard, what's your impression of the relative boot time of nosh vs systemd? Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141021010820.016e6...@mydesq2.domain.cxm
Re: Good news on claws-mail
On Sun, 19 Oct 2014 12:47:03 +0200 Peter Nieman gmane-a...@t-online.de wrote: By the way, I am a desktop user, using fvwm. But I don't want all my applications to look and feel the same, I don't want everything to interact with everything, and I want to control my computer instead of being controlled by my computer. Quoted For Truth!!! Steve Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141019101536.07455...@mydesq2.domain.cxm
Re: Good news on claws-mail
On Sun, 19 Oct 2014 14:20:25 +0200 lee l...@yagibdah.de wrote: Since you're re-inventing the wheel: // sxnotify.c // // This program is free software: you can redistribute it and/or // modify it under the terms of the GNU General Public License as // published by the Free Software Foundation, either version 3 of the // License, or (at your option) any later version. // // This program is distributed in the hope that it will be useful, but // WITHOUT ANY WARRANTY; without even the implied warranty of // MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU // General Public License for more details. // // You should have received a copy of the GNU General Public License // along with this program. If not, see // http://www.gnu.org/licenses/. // // Author: l...@yun.yagibdah.de, 2013-07-21 // // compile with something like: // gcc -lsx -lXpm -lXaw -lXt -lX11 -march=native -O2 -Wall -fomit-frame-pointer -finline-functions sxnotify.c -o sxnotify // #include stdio.h #include unistd.h #include stdlib.h #include libsx.h void xx(void *data) { exit(0); } int main(int argc, char *argv[]) { if(!OpenDisplay(argc, argv)) { puts(cannot open display); exit(1); } if(argc != 2) { puts(usage: sxnotify message); exit(1); } MakeLabel(argv[1]); ShowDisplay(); int foo; AddTimeOut(5000, xx, (void *)(foo)); MainLoop(); exit(0); } # aptitude install libsx-dev Very, very nice! Not an entanglement in sight. This is the first I've heard about libsx, but I'll be learning a lot more about it. So far I've found: * http://www.ee.usyd.edu.au/tutorials/ee_database/programming/libsx/libsx.html * http://www.nada.kth.se/~sungam/libsx/general.libsx.html * /usr/share/doc/libsx-dev/examples Unfortunately, a 5 minute Google search found no Python implementation of libsx. I don't need C for forms: The speed bottleneck is the typist anyway. But then again, I could have somebody define a form in some sort of data file, parse that and convert to a simple C program, call gcc to make it into an executable. Rapid Application Development, Army Surplus style, which of course makes me a pariah in the eyes of real programmers. Life's tough. Thanks so much for cluing me into this! SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141019110313.371f1...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Fri, 17 Oct 2014 23:06:53 -0700 Jimmy Johnson field.engin...@gmail.com wrote: On 10/17/2014 10:12 PM, Steve Litt wrote: On Fri, 17 Oct 2014 21:59:44 -0700 Jimmy Johnson field.engin...@gmail.com wrote: On 10/17/2014 08:44 PM, Ric Moore wrote: On 10/17/2014 10:22 PM, Jimmy Johnson wrote: What's the hurry, Squeeze is good until 2016, we have plenty of time to test other init-systems. You use KDE. Where you there when KDE3 became KDE4 and broke our hearts? What a flame fest that was. Yet, you use it now? Ah! Time must have finally smoothed the rough edges. Yet, KDE4 happened no matter what any of us had to say, and I was royally jerked about it. Gnome went through the very same cycle. So did Ubuntu with all of the lens (IMHO) junk. Every one of those projects were driven top-down. We users just got pulled along. Yes! I was at the KDE4 release at Google what fun..I also helped with Trinity, Linux is about diversity and Debian has always been the leader. Whoa guys, slow down on the generalizations. Don't assume everyone uses KDE4. Two years ago I kicked KDE, in its entirety, libraries and all, off all my computers. It's an entangled monolith and a danger to computing. The time might come when I need to do the same with Gnome. Don't assume that users just bend over and take this entangled junk. Debian KDE4 has been manageable, nothing but a bunch of meta-packages remove what you don't need and then use 'aptitude keep-all' to keep the app's and then 'upgrade-system' to cleanup the crud. Some of the best minds use KDE. ;) LOL, in that case, consider me one of the worst minds. With my special set of hotkeys, I've tweaked my Openbox to break the sound barrier. :-) SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018023627.471af...@mydesq2.domain.cxm
Re: alternative file systems
On Sat, 18 Oct 2014 12:06:17 +0400 Reco recovery...@gmail.com wrote: Hi. On Fri, 17 Oct 2014 18:24:16 -0400 Steve Litt sl...@troubleshooters.com wrote: On Fri, 17 Oct 2014 03:00:26 +0200 lee l...@yagibdah.de wrote: But when it eats files and is 10 years behind, why are people buying it? So how can we safely store large amounts of data? I thought Postgres was supposed to be powerful, stable, reliable, and great for lots of data. Storing all your data in Postgres is surely possible, but what about convenience of doing so? I mean, how easily the data (say, home videos or photo collection) can be put in and retreived. Reco I think comm got crossed. Somebody had asked why we use Oracle, someone else said that was a safe DBMS, and I said what about Postgres. I would never, never, NEVER store file data like home video or photos in a DBMS. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018091445.6bed5...@mydesq2.domain.cxm
Re: Good news on claws-mail
On Sat, 18 Oct 2014 17:16:04 +0100 berenger.mo...@neutralite.org wrote: Le 18.10.2014 16:29, Peter Nieman a écrit : As far as I am concerned, I don't have the time right now to learn the officially accepted procedures of filing bug reports in Debian Just run bugreport (or is it reportbug? I don't have a Debian currently, but I'm trying to fix that :p) . It'll ask you several questions the first time, like, do you want gtk based interface, what's your level of knowledge, etc. Then, the normal way it works: _ asking which package is buggy _ checking if there are some updates _ if yes, it asks if the user want to report anyway _ before letting you send a bug report, it will list the current list (which is sometimes pretty long, but not always) _ it asks you if your bug is already there _ if yes, it will ask you if you want to improve the bug report _ otherwise, it will ask you to write the report _ last step, it will ask if you want to be noticed when there are changes on the report Pretty simple imo. Nicely done. And no registration neeeded, which is really great! (seriously, registering on every damned bug tracker in the world is a pain. In debian, this problem is well fixed!) Very nice, berenger.morel. Thanks for the info. I just sent a bug I've been working around for several months. Let's see whether it actually got emailed to Debian. The process, the questions it asked, and the automatic collection of my computer's configuration made submitting the bug trivial. *Every* project should have one of these. Thanks so much for telling me about this. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018152900.554cf...@mydesq2.domain.cxm
Re: Good news on claws-mail
On Sat, 18 Oct 2014 19:19:26 +0200 Sven Hartge s...@svenhartge.de wrote: berenger.mo...@neutralite.org wrote: I guess that claws uses (lib)dbus to notify dbus-compliant softwares that there is a new mail. Also claws might get a signal from (for example) network-manager if there is a connection available to toggle its offline/online mode to avoid unnecessary tries to connect to the mailserver while offline. Or to change to polling rate if the device is on battery to conserve power. There are many reasons why a software might want to communicate things to other running applications and the standard way of doing so has become Dbus. Here's the official answer as to how Claws uses dbus: === On Fri, 17 Oct 2014 12:15:34 -0500 »Q« boxc...@gmx.net wrote: I don't use networkmanager and I don't use any local MTA. Does C-M use dbus for anything else? Avant Window Navigator support, and the experimental new address book, which is not packaged, and disabled by default. with regards Paul === Reading the preceding, it looks to me like it's used for some fairly arcane enhancements to the basics of Claws-Mail. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018153409.6bff9...@mydesq2.domain.cxm
Re: Good news on claws-mail
On Sat, 18 Oct 2014 17:30:27 +0100 berenger.mo...@neutralite.org wrote: Le 18.10.2014 16:14, Brian a écrit : Which once again raises the main question; what does systemd have to do with this? The original post gives an unexplained solution to a non-existent problem. Dbus is (a crap, but not only) a tool to allow applications to share informations with other applications (why should those apps to do so, is often a mistery for me. Hi berenger.morel, I think you and I have the same basic beliefs about software. Enabling applications to permiscuously talk to each other, to broadcast their business to everybody else and to listen to (and presumably take action depending upon) everybody else's broadcasts, greatly reduces repairability of the system. I'm a huge believer in modularity, and one of my definitions of modularity is that module A knows the business of module B **only** to the extent it needs to know B's business in order to function. In most cases, the need is zero. POSIX gives two modules many, many ways to communicate: Files, piping, fifos, sockets, heck, I've probably missed five or ten. If both modules know they'll need to communicate, it's a snap. If one knows, it can be built with a fifo interface, like mplayer. Or a socket interface. Especially why should them have to do that in XML...). I guess that's so they can pass huge, arbitrary data in dbus. My thought when contemplating that is what could *possibly* go wrong? [clip] Now, how softwares did before was maybe a nightmare. Doing the wheel everytime, in different fashion, etc. Later today I'm writing a whole page on reinventing the wheel. Unless the wheel you need is very similar to the wheel already invented, reinventing is simpler, and produces a much smaller and robust design, than trying to strongarm somebody else's wheel into your needs. The other reliable technique I know is through window managers, by setting a flag (I do not know how it's named, I only know about this technique because some softwares uses it... like, for example, claws.) which, depending on the WM, will result in a visual and or audio hint. Those visual and audio hints are one of the few things that most programs might need to write to. They need a predefined standard to write to, and I guess dbus is the standard being used. If I were in charge of standards, I might have used something simpler (like a fifo with a very simple data definition) exclusively for notifications (the official visual and audio hints), but hey, that's just me. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018161009.4652b...@mydesq2.domain.cxm
Re: Openbox systemd-free
On Sat, 18 Oct 2014 20:20:29 +0100 Keith Peter ping.ke...@gmail.com wrote: Hello On my Jessie laptop with sysvinit, X and IceWM updated to today installing wicd with --no-install-recommends brings dbus, wpasupplicant and wireless-tools with it. So I just use wpasupplicant in roaming mode with wpa-gtk as I need basically wifi in four locations. Not bothering with wicd itself. Cheers Nice! This was exactly the kind of stuff I've been looking for. I'll probably ask you more about it later. One look at /etc/wpa_supplicant/functions.sh tells me that wpa_supplicant is a daemon that's begging to be managed by daemontools instead of the unfathomable shellscripts it's now managed by. I spoze one could also make a point for managing it with systemd, but I can't afford the price of that ticket. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018162512.7c123...@mydesq2.domain.cxm
Re: All roads to suspend/hibernate lead through systemd?
On Sat, 18 Oct 2014 19:53:38 -0700 (PDT) Rusi Mody rustompm...@gmail.com wrote: On Saturday, October 18, 2014 11:40:01 PM UTC+5:30, Nate Bargmann wrote: No, this is not a troll (seems like that is necessary to state up front). I have been experimenting with dropping systemd from my laptop running Sid but find that even with xfce4-power-manager suspend nor hibernate are available any more unless I install the policykit-1 package recommended by the upower package which depends on libpam-systemd which, even if I install systemd-shim, also installs the systemd package as a dependency, even though it won't run as PID 1. Just a heads up. xfce on jessie with systemd A couple of weeks ago in trying to get round some dependency issues I needed to install policykit that did: libpolkit-agent-1-0 (0.105-6.1) libpolkit-backend-1-0 (0.105-6.1) policykit-1 (0.105-6.1) After that direct poweroff from the xfce panel has stopped working ie whether I choose logout or shutdown, it only logs out, ie closes startx and puts me back in console shell. [Oh and BTW about 6 months or so back gdm stopped working and Ive switched to startx ] There's a certain irony. First, IMHO startx is better than booting directly to GUI. Secondly, now that stopping X gets you to the command prompt, you can type whatever shutdown/reboot/poweroff command you want. Unless those were messed up too. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141019002453.34efc...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Fri, 17 Oct 2014 07:54:06 -0700 (PDT) Rusi Mody rustompm...@gmail.com wrote: On Friday, October 17, 2014 8:00:02 PM UTC+5:30, Rob Owens wrote: - Original Message - Now let's see what happens with this! https://lists.debian.org/debian-vote/2014/10/msg1.html Very interesting discussion there. Thanks for posting. -Rob Thank you Ian Jackson and all seconders for this. Particularly Ian for having done this and become the 'bad-guy' for a good cause. Yes!!! Thank you Ian, and the seconders, and everyone who is speaking up for (what I call) sanity. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017122127.3eb3c...@mydesq2.domain.cxm
Re: how to shutdown in less than 8 minutes
On Fri, 17 Oct 2014 09:56:28 +0200 (CEST) Pierre Frenkiel pierre.frenk...@gmail.com wrote: On Fri, 17 Oct 2014, Michael Biebl wrote: The samba package does not properly clean up it's config files on upgrades. See the RC bug that's filed against samba. Run update-rc.d samba remove to fix that. hi Michael, I saw the thread concerning the bug report against samba, but only saw a proposed fix about the LSB headers(which didn't work), and not this one. Actually, you need both: update-rc.d samba and update-rc.d samba-ad-dc remove Then, the shutdown lasts a few seconds Thanks a lot for this valuable information. Question: the daemons nmbd and smbd are still launched by systemd at boot. although all the links in /etc/rcxx have been removed. How is it done? This behavior is apparently consistent with a known Samba defect, but are you all sure that the delay *does* happen during the shutdown of Samba? If it turns out not to be Samba, you've just needlessly chased your tail for hours or days. Personally, I'd find out where all the time is going before troubleshooting Samba or any other package. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017122338.5fef5...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Fri, 17 Oct 2014 12:38:12 -0400 Tanstaafl tansta...@libertytrek.org wrote: On 10/17/2014 12:21 PM, Steve Litt sl...@troubleshooters.com wrote: On Fri, 17 Oct 2014 07:54:06 -0700 (PDT) Rusi Mody rustompm...@gmail.com wrote: On Friday, October 17, 2014 8:00:02 PM UTC+5:30, Rob Owens wrote: - Original Message - Now let's see what happens with this! https://lists.debian.org/debian-vote/2014/10/msg1.html Very interesting discussion there. Thanks for posting. Thank you Ian, and the seconders, and everyone who is speaking up for (what I call) sanity. Still only 4 seconds though... Succeed or fail, I thank them immensely. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017125748.7d255...@mydesq2.domain.cxm
Good news on claws-mail
Hi all, For those of you using Claws-Mail, you can keep it systemd-free into the foreseeable future by disabling dbus, like this: ./configure --disable-dbus I've compiled Claws_Mail from source on Debian. It's fairly easy to do, it can exist in tandem with the existing Claws-Mail (obviously rename the executables), and it works. Bang, another 0d program! SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017131123.1ffdf...@mydesq2.domain.cxm
Re: A Systemd Second Chance (Sorta)
On Fri, 17 Oct 2014 09:56:16 -0700 Patrick Bartek nemomm...@gmail.com wrote: Systemd is a done deal, but this may thwart the potential dependency issues: http://lwn.net/Articles/616571/rss After reading this, I triple my thanks to Ian. What he did took a lot of guts, even though it was the right thing to do. Thank you Ian, win or lose. You do good work! SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017132206.086e5...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Fri, 17 Oct 2014 10:20:16 -0700 (PDT) Rusi Mody rustompm...@gmail.com wrote: Seconds continue Bernhard R. Link Dimitri John Ledkov Arnaud Fontaine Thorsten Glaser And once again loud cheers for Ian Jackson and the seconds Some like Charles Plessy are distressed that this may be de-motivating, delaying etc. Absolutely! By definition it's delaying, and I can't conceive of being a systemd-agnostic developer or packager and not being de-motivated by getting yanked this way and that. But ... This reminds me of the old saying: Marry in haste, repeat at leasure. This was all forseeable when the CTTE voted, given their decision logistics. It's too late to repeal the engagement, apparently it's even too late for an annulment, but at least there can be an agreement to see others during this loveless marriage. Systemd as the one-and-only will doubtlessly produce a huge splintering of Linux. Systemd as the preferred over other alternatives will probably calm things down. As for me, regardless of outcome, I'm going to continue finding and making entanglement-free software. In fact, I should have started doing this ten years ago, and in fact, I should have given much higher priority to freedom from gratuitous dependencies of all types. I always had a lousy feeling about network-manager: I should have created a simple, low dependence alternative years ago. I've always had a lousy feeling about dbus, and should have prioritized dbus-free software years ago. And from now on, when people laugh at my ugly, no-dependency, home grown solutions as kludges, I'll have exactly two words to say to them: *Thank you*. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017135904.5a653...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Fri, 17 Oct 2014 10:20:16 -0700 (PDT) Rusi Mody rustompm...@gmail.com wrote: Seconds continue Bernhard R. Link Dimitri John Ledkov Arnaud Fontaine Thorsten Glaser And once again loud cheers for Ian Jackson and the seconds Abso-Lutely! [snip] However the contentiousness of this case clearly overrides the need to hit deadlines I agree. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017140012.1b633...@mydesq2.domain.cxm
Re: alternative file systems
On Fri, 17 Oct 2014 03:00:26 +0200 lee l...@yagibdah.de wrote: But when it eats files and is 10 years behind, why are people buying it? So how can we safely store large amounts of data? I thought Postgres was supposed to be powerful, stable, reliable, and great for lots of data. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017182416.2a4db...@mydesq2.domain.cxm
Re: Conflict of interest in Debian
On Fri, 17 Oct 2014 08:06:11 -0400 Henning Follmann hfollm...@itcfollmann.com wrote: On Thu, Oct 16, 2014 at 02:08:47PM -0400, Rob Owens wrote: - Original Message - From: Marty mar...@ix.netcom.com It seems like free software employment and market share come with increasing risk to objectivity and technical quality. It's my main concern as a Debian user, as I consider recent trends. I hope that Debian members consider an amendment to restrict voting rights for members who have a financial interest in Debian or in any project used by Debian, to promote and protect the public interest. Conflicts of interest are not just financial. Even an unpaid developer should probably not be voting as a technical committee member on whether to make his project the Debian default. He could vote for his project because of the glory that comes with being the Debian default. Or maybe he truly believes it is the best. But he knows his project better than any of the alternatives. He is invested in it. He should be the expert petitioning the decision-makers, but he should not be one of the decision-makers. I really think this concept is obvious and was really surprised that Debian allowed a vote for default init system to occur in a technical committee whose members have vested interests in one init system or another. Avoiding perceived conflict of interest is just as important as avoiding actual conflict of interest, because it undermines confidence in the leadership. Most conflict-of-interest regulations that I know of (USA-based) reflect this. (But let's not start citing examples of government officials who have violated these principles -- we all know there are plenty). Anyway, regardless of how impartial the tech committee members are believed to be, the upstart guys and the systemd guys probably should not have participated in the vote for default init system. -Rob There was no conflict of interest. Every voter has some interests and the outcome of a vote determines the common interest. But there is no conflict of interest during a vote. You're a man after former Chicago Mayor Richard J Daley's heart! A conflict happens when somebody is entrusted by a group to guard a common good and he/she has her/himself interests in that good. Or, when his paycheck or bribe might cause him to vote a certain way. This thread is about the inability to accept a outcome of a democratic process. Now they claim to own the right debian way and to protect that some un-debian persons have to be stopped. I have seen that before... Keep telling yourself that. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017182937.53614...@mydesq2.domain.cxm
Re: how to shutdown in less than 8 minutes
On Fri, 17 Oct 2014 22:44:41 +0200 (CEST) Pierre Frenkiel pierre.frenk...@gmail.com wrote: On Fri, 17 Oct 2014, Steve Litt wrote: are you all sure that the delay *does* happen during the shutdown of Samba? If it turns out not to be Samba, you've just needlessly chased your tail for hours or days. I'm quite sure, because: 1/ there are a lot of bug reports against samba about this problem 2/ before removing the samba links, I had this message at shutdown with a countdown of 5 minutes A stop job is running for LSB: ensure samba daemons are started (nmbd and smbd) ( 3 min 2 s / 5 min ) 3/ after removal of the samba links, the shutdown takes a few seconds ... Bang, that's it, you proved it. Obviously, your next step is to do the corrective maintenance suggested for Samba. If that doesn't eliminate the symptom... My next step would be, just as a diagnostic test, run smb and nmb from a terminal, then shut them down again, and see if the problem occurs. If so, ***TEMPORARILY*** replace your smb.conf with the simplest possible smb.conf (maybe just printers) and see if the problem still occurs. If so, ask for help on the Samba list. But if the simplest possible smb.conf shuts down in a few seconds, then start adding stuff back until you find the Samba service that takes all the time, and examine that. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017183513.0a134...@mydesq2.domain.cxm
Re: how to shutdown in less than 8 minutes
On Fri, 17 Oct 2014 23:51:34 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: I meant /etc/init.d/nmbd /etc/init.d/smbd Kind regards, Andrei LOL, same here (in my advice on troubleshooting to Pierre)_. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017183625.7d03a...@mydesq2.domain.cxm
Re: how to boot in les than 8 minutes
On Fri, 17 Oct 2014 18:15:01 -0700 (MST) Buntunub mckis...@gmail.com wrote: Pierre Frenkiel wrote hi, it seems that tha last version of systemd in jessie (215-5+b1) has a big number of bugs, among which the very long time to shutdown, mainly for samba (5 minutes). Trying to kill samba manually before the shutdown did not solve the problem. If this is the future with Systemd, then all the more reason to ensure we maintain more seasoned init systems, which we know work without issues like this. Has Debian utterly forgotten its roots of stability and conservative approach to adopting experimental software in its stable releases? Hey, I hate systemd as much as the next guy, but the diagnosis implied by the OP's quoted text is nowhere near ready to declare systemd as the root cause. Contrarily, the fact that his shutting down manually reproduced his symptom makes it unlikely that any PID1, including systemd, is responsible. My suspicion at this point would be either a flaw in his smb.conf (which is easy to test by temporarily replacing it with a minimal) or Samba itself. It turned out he was starting two of them, one by systemd and one elsewhere. Umm, err, blush, I recently had the exact same problem with daemontools! SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017213414.05b7b...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Sat, 18 Oct 2014 10:20:25 +0900 Joel Rees joel.r...@gmail.com wrote: According to what I understand as an engineer, everything that systemd does beyond the minimum (in other words, beyond being the ultimate backstop for signals and dying orphaned processes) should be delegated. I would add that it should be delegated to an interchangeable part through a well-specified thin interface, without global variables like dbus. Or, if there *must* be a global variable, at least make it purposed only for interaction between init and program, and not used by my music player to announce song titles. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017213834.52d70...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Fri, 17 Oct 2014 18:52:32 -0700 Jimmy Johnson field.engin...@gmail.com wrote: On 10/17/2014 07:54 AM, Rusi Mody wrote: On Friday, October 17, 2014 8:00:02 PM UTC+5:30, Rob Owens wrote: - Original Message - Now let's see what happens with this! https://lists.debian.org/debian-vote/2014/10/msg1.html Very interesting discussion there. Thanks for posting. -Rob Thank you Ian Jackson and all seconders for this. Particularly Ian for having done this and become the 'bad-guy' for a good cause. Yes! I too think Ian for sticking up for Debian, I was following the posts and Ian's membership was indeed threatened..it's so insane and Ian is trying to save what is left of Debian..But this GR is not enough..I propose all of 'systemd' be removed as default, it's doing nothing but causing problems, VLC-headless is requiring the VLC-player is ridicules, readable text files(my logs) are now unreadable is not rational at all, The perfect is the enemy of the good. The GR is good enough for the time being. We're proceeding with a two prong plan: 1) The GR might cause init program choice. 2) Several of us are documenting, and creating, systemd-free software. I think at this point insisting on systemd being declared non-default might risk the success of #1. If they vote no on the GR, then I think that unless Red Hat succeeds in systemdizing X itself, we'll (meaning those of us who care) will replace systemd-contaminated software with init-agnostic software. And for sure, boycott all systemd-dependent software to the best of our ability. The GR is good thing because one of two things will become obvious in the coming years. Either: A. We were right all along, Linux is being destroyed, and because we've maintained init choice, we can dump systemd and the corporation that tried to destory Linux. B. They were right, the world goes on, and systemd is a nonissue. I think within three or four years we'll know which of the above is true. If it's A, we'll take Linux back from Red Hat, and with any luck cause the demise of Red Hat via competition of a superior OS. If it's B, we won't even let out a wimper if, in 2018, they finally declare systemd as the one true init. I just don't want to do anything that jeopardizes the chances of the GR voting for choice. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018010600.11828...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Fri, 17 Oct 2014 21:59:44 -0700 Jimmy Johnson field.engin...@gmail.com wrote: On 10/17/2014 08:44 PM, Ric Moore wrote: On 10/17/2014 10:22 PM, Jimmy Johnson wrote: What's the hurry, Squeeze is good until 2016, we have plenty of time to test other init-systems. You use KDE. Where you there when KDE3 became KDE4 and broke our hearts? What a flame fest that was. Yet, you use it now? Ah! Time must have finally smoothed the rough edges. Yet, KDE4 happened no matter what any of us had to say, and I was royally jerked about it. Gnome went through the very same cycle. So did Ubuntu with all of the lens (IMHO) junk. Every one of those projects were driven top-down. We users just got pulled along. Yes! I was at the KDE4 release at Google what fun..I also helped with Trinity, Linux is about diversity and Debian has always been the leader. Whoa guys, slow down on the generalizations. Don't assume everyone uses KDE4. Two years ago I kicked KDE, in its entirety, libraries and all, off all my computers. It's an entangled monolith and a danger to computing. The time might come when I need to do the same with Gnome. Don't assume that users just bend over and take this entangled junk. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018011211.71724...@mydesq2.domain.cxm
Re: GR proposed re: choice of init systems
On Sat, 18 Oct 2014 01:26:11 -0400 Doug dmcgarr...@optonline.net wrote: /Snip/ That's not the problem. A few people have recognized the problem(s). 1--Putting all your eggs (programs) in one basket. Making almost everything have a dependency on systemd. Registry, anyone? 2--Forcing the entire Linux community to use just one system, and every application to be modified so as to run on systemd. 3--Making all those applications incompatible with any other version of Unix. Never mind GNU's not Unix. This stuff we're running is essentially Unix. 4--Eliminating readable logs. I probably missed a few along the way. So let me add a couple: * Design with no regard to repairability. In fact, hostility toward repairability. * Lessening the use of interchangeable parts. * Giving design leadership to a guy who said Linux isn't a real operating system. But here's the thing, Doug. Even if it were nothing more than your first two points, it would be a travesty. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141018014611.61124...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Thu, 16 Oct 2014 00:54:02 +0100 Jonathan de Boyne Pollard j.deboynepollard-newsgro...@ntlworld.com wrote: wande...@fastmail.fm: I have a similar lack of awareness and/or understanding about all of the *kit packages / projects / tools / what-have-you, actually; I'm not positive I even know how many there are, much less all of their names. This should help: Put yourself in the position of someone writing a desktop system for Linux and the BSDs. You've reached the part where you're writing a control panel gadget for allowing system administrators (and [clip amazingly detailed and helpful summary of the helper daemons and apis] Thank you Jonathan. I have a much better understanding of the situation now. Interestingly, the stuff Jonathan described was part of my reason for migrating from Ubuntu to Debian. I've always felt unease at those GUI admin tools. And also, of course, Plymouth isn't required in Debian (unless you use Xfce, but then you can just disable Plymouth). Let me ask you one more question: Is there any way that I personally could make wicd independent of all of those helper daemons that are now welded to systemd, or would I have to drop all the way back to wpa-supplicant to get rid of the need for those daemons? Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016022331.3b692...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Thu, 16 Oct 2014 08:10:47 +0200 Ansgar Burchardt ans...@debian.org wrote: Steve Litt sl...@troubleshooters.com writes: OK, I'll be the first to admit that after Red Hat caused the demise of ConsoleKit (and probably lots more important software), I am free to take significant time out of my day job (that feeds my family) and rescue all sorts of software that Red Hat deliberately scuttled. Even though, apparently unlike 80% of today's kernel developers, nobody pays me to do it. You are free to do so in your free time. It would be a more constructive use than trying to annoy other people (who spend their free time on Linux) until they do so for you for free. So, reading between the lines, you find my saying don't break Linux annoying. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016023029.531bd...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Thu, 16 Oct 2014 07:33:38 +0100 Jonathan Dowland j...@debian.org wrote: On Thu, Oct 16, 2014 at 01:12:51AM -0400, Steve Litt wrote: OK, I'll be the first to admit that after Red Hat caused the demise of ConsoleKit (and probably lots more important software), I am free to take significant time out of my day job (that feeds my family) and rescue all sorts of software that Red Hat deliberately scuttled. You're being completely ludicrous, Steve. The extent of your sense of entitlement is breathtaking. I've asked for two software changes in my life: 1) Add character styles to LyX 2) Add real ePub export to LyX Every other need I had, I either wrote software for it, or worked around it. Several of the softwares I wrote for it I released as Free Software, one of which is in the Debian repositories right now. I'm not asking anyone to change Debian. I'm asking them *not* to change it. Leave well enough alone. It's not too late. Here you are on a list dedicated to an OS built almost entirely by volunteers and you're not prepared to roll your sleeves up, but you're more than happy to tell everyone how they should do it, and what they should do. You used the word ludicrous. I'll tell you what's ludicrous. Implying that if I don't roll up my sleeve and make alternatives for everything that systemd welded together, but instead say don't weld it, I'm entitled. It took a lot of people to do this damage to Linux, many of them paid handsomely for their damage: One guy, or even a few guys, aren't going to undo it. You state that Linux is built almost entirely by volunteers. Do you have a reference for that? If the whole OS is anything like the kernel, a heck of a lot of those volunteers get a paycheck for their volunteerism. http://spectrum.ieee.org/computing/software/whos-writing-linux Then there's this idea that if you're not writing C code, you're not doing anything for Linux. I'm actually going to write an entire article on that, but suffice it to say a lot of people have done a lot of different things to make Linux succeed, and a lot of those things weren't writing code. And very few of those things have anything to do with writing systemd related code. I'm not going to engage with you any more on this list. That's your choice. Believe me, I don't like it either, and if there were any reasonable low maintenance desktop Linux distros, I'd have simply migrated and wouldn't be on this list. I didn't yell on the Ubuntu list about Plymouth, I just moved. The problem is, this systemd thing is a concerted effort to change to all major distros to what Leonnart Poettering calls a real OS and I call fewer interchangeable parts. You can't escape it by switching major desktop distros. The one hope is to keep talking it up on the one major distro that might have the guts to defy Red Hat. Actually, I take it all back: I *do* have a sense of entitlement. I feel entitled to use a reasonable facimile of the same OS that, for thirteen years, I've used, written about, created software for, created user groups for, and recruited others to use. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016042029.72620...@mydesq2.domain.cxm
Re: Would discussion of improving sysv-init be on topic?
On Thu, 16 Oct 2014 21:52:58 +0900 Joel Rees joel.r...@gmail.com wrote: On Thu, Oct 16, 2014 at 9:33 PM, Nate Bargmann n...@n0nb.us wrote: * On 2014 15 Oct 19:39 -0500, Joel Rees wrote: systemd's problems would best be discussed at the systemd project. (Modulo the willingness of the devs over there to discuss them.) What I'm thinking is to talk about specific features to enable the sort of managing services that systemd seems to be aimed at, and how to implement them, where existing alternatives exist and how well they work, With enough discussion, we might be able to get enough mass to get a project started and get it (mostly) off-list. Perhaps you are not aware of the development project for sysvinit that already exists: http://savannah.nongnu.org/projects/sysvinit That would be a far better place to get involved. Would that be debian's sysv-init? With everything I've learned during the systemd fiasco, if I were to choose Debian's sysv-init, it would be nosh or something very much like it. And, as far as I know, it's ready to go, and our only involvement would be building replacements for formerly available software that was replaced by systemd-welded substitutes. After Jonathan de Boyne Pollard revealing post from yesterday (Wednesday, 10/15/2014), we could write some stupid-simple utilities to individually do all the stuff that logind does, probably using sudoers. Which means a big part of the task would be documentation, and I can do that. Of course, we'd need to write substitutes for the other 3 major welded and subsumed daemons, and some other stuff, but from what Jonathan said, logind is the challenging one. IMHO we should spend absolutely no time or energy making this stuff pretty, or even GUI if it presents challenges. If I'm guessing right about the situation, people who want pretty wouldn't have a problem with monolithic entanglement and vendor lock-in, just as long as they didn't have to pay money for their OS. As a matter of fact, regardless of what the DDs do, it just might be true that making either a systemd-free or systemd-neutered Debian might be mainly a documentation problem, and I'm pretty good at documentation. Who wants to join me? It's your chance to make Red-Hat *really* hate you. And make a lot of Debian users and other Linux people love you. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016112850.36018...@mydesq2.domain.cxm
Re: Would discussion of improving sysv-init be on topic?
On Thu, 16 Oct 2014 11:28:50 -0400 Steve Litt sl...@troubleshooters.com wrote: POINT OF CLARIFICATION: Nothing written below is nosh specific. It could be used with nosh, or upstart, or sysvinit, or any other PID1 that's *only* a PID1. So how about it, who wants to join me in neutering systemd on Debian and probably every other distro? With everything I've learned during the systemd fiasco, if I were to choose Debian's sysv-init, it would be nosh or something very much like it. And, as far as I know, it's ready to go, and our only involvement would be building replacements for formerly available software that was replaced by systemd-welded substitutes. After Jonathan de Boyne Pollard revealing post from yesterday (Wednesday, 10/15/2014), we could write some stupid-simple utilities to individually do all the stuff that logind does, probably using sudoers. Which means a big part of the task would be documentation, and I can do that. Of course, we'd need to write substitutes for the other 3 major welded and subsumed daemons, and some other stuff, but from what Jonathan said, logind is the challenging one. IMHO we should spend absolutely no time or energy making this stuff pretty, or even GUI if it presents challenges. If I'm guessing right about the situation, people who want pretty wouldn't have a problem with monolithic entanglement and vendor lock-in, just as long as they didn't have to pay money for their OS. As a matter of fact, regardless of what the DDs do, it just might be true that making either a systemd-free or systemd-neutered Debian might be mainly a documentation problem, and I'm pretty good at documentation. Who wants to join me? It's your chance to make Red-Hat *really* hate you. And make a lot of Debian users and other Linux people love you. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016113419.37ea8...@mydesq2.domain.cxm
Re: how to shtdown in less than 8 minutes
On Thu, 16 Oct 2014 20:07:42 +0200 (CEST) Pierre Frenkiel pierre.frenk...@gmail.com wrote: oops! sorry for the error in the subject: obviously, I meant shutdown and not boot I think better to re-submit with the correct subject hi, it seems that tha last version of systemd in jessie (215-5+b1) has a big number of bugs, among which the very long time to shutdown, mainly for samba (5 minutes). Trying to kill samba manually before the shutdown did not solve the problem. I then tried to downgrade to version 208-8, which is available according the output of apt-cache madison systemd systemd | 215-5+b1 | http://ftp.fr.debian.org/debian/ jessie/main i386 Packages systemd | 208-8 | http://ftp.fr.debian.org/debian/ jessie/main Sources systemd | 215-5 | http://ftp.fr.debian.org/debian/ jessie/main Sources but I get: apt-get install systemd=208-8 Reading package lists... Done Building dependency tree Reading state information... Done E: Version '208-8' for 'systemd' was not found What is wrong? Hi Pierre, I can't begin to answer the question what's wrong, but I have a pretty good idea of what I'd do in your position. I'd start moving as many as possible of my services to daemontools, because daemontools exercises exquisite control and logging over its services. It would even be pretty easy to write a shellscript to start them in the order you desire. Because by default daemontools logs are all sortably timestamped, it would be trivial to cat then datesort all daemontools lots to see who's hogging the shutdown time. This is more than a diagnostic test. Because daemontools is so good at what it does, I'd just leave your services governed by daemontools, even after you solve the problem. HTH, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016185345.52927...@mydesq2.domain.cxm
Openbox systemd-free
Hi all, The first task of my project is done. Openbox is systemd-free, and is intended to be systemd free. So that will form the GUI foundation. I'll come back in the next few days with some systemd-free panels that go well with Openbox, as well as a lock program. So far my research is telling me that wicd command line is systemd free (if anyone knows to the contrary, please let me know), so I'll probably put a small front end on wicd. I'll also try to find a systemd-free alternative to LibreOffice, and to Gnumeric (Gnumeric will be tough, it's actually a good program). By the way, could somebody do me a favor and, on an installed (not upgraded) Jessie do aptitude show gnumeric to see if it depends on any systemd stuff? I'm also starting to list functionalities provided by the welded on systemd tools so that I can provide them in an elemental way. Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141017010321.09818...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Wed, 15 Oct 2014 10:02:03 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Ma, 14 oct 14, 17:56:58, Steve Litt wrote: Because you don't want to inextricably drag a giant monolith into your Desktop Environment just to do a few things. If you compare systemd with a Desktop Environment I'm not quite sure who's the giant ;) Yeah, I wasn't clear. I meant giant relative to what needed to be done. In other words, you need to verify passwords, so you bring in the entirety of systemd to do it, instead of just writing the code yourself. I completely understand not reinventing the wheel, but if all you need is a spoke, you don't construct an interface to a whole wheel just to get your spoke. And how were they handling this task before systemd? It's not like Desktops, Window Managers and whatever things like lightdm are called didn't exist before systemd. ConsoleKit, unmaintained. Pre-cisely. I see Red Hat's fingerprints all over that unmaintained status. If not for Red Hat, somebody would have picked up ConsoleKit. After all, as shown in http://spectrum.ieee.org/computing/software/whos-writing-linux , there's plenty of money floating around to pay for free software development. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141015123026.5f396...@mydesq2.domain.cxm
Re: Conflict of interest in Debian
On Wed, 15 Oct 2014 08:11:10 +0100 Jonathan Dowland j...@debian.org wrote: On Wed, Oct 15, 2014 at 12:51:07AM -0400, Steve Litt wrote: Check out what single company has 30% of the gatekeepers. Surprise, surprise. Damned for their success. We want Linux to be successful, but woe betide any company that actually gets us there... Hi Jonathan, Parse the preceding sentence. We want *Linux* to be successful, but woe betied any *company* ... I want *Linux* to succeed, and it would be nice for that success to float the boats of the companies making Linux succeed, but not the companies trying to completely change the Linux that attracted most of us to it. We've actually been in this place before. Wonderful Linux company Caldera became SCO (oversimplification, but you know what I mean). Wonderful Linux company Corel changed their CEO, and promptly accepted money from Microsoft and dropped all their Windows software. No doubt, mid 1990's to mid 2000's, Red Hat got us there, and I thanked and celebrated them. What Red Hat is doing now is anti-Linux, as demonstrated by timestamps 1:35 and 2:20 in the following: https://www.youtube.com/watch?v=LdRmnSHHVw4 SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141015123909.55ec1...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Wed, 15 Oct 2014 09:08:26 +0100 Martin Read zen75...@zen.co.uk wrote: On 14/10/14 22:56, Steve Litt wrote: And how were they handling this task before systemd? They were using ConsoleKit, which was orphaned upstream some time after systemd-logind came along. I rest my case. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141015124258.53bd8...@mydesq2.domain.cxm
Re: Conflict of interest in Debian
On Wed, 15 Oct 2014 23:37:37 +0900 Joel Rees joel.r...@gmail.com wrote: 2014/10/15 1:47 Brian a...@cityscape.co.uk: Give me swearing in posts rather than innuendo and attempted character assassination of a group dedicated workers. Do you realize that a lot of your posts, jumping on anti-systemd topics, might appear, to casual examination, to be innuendo and/or character assassination? Yes. Let's get rid of the innuendo. It is my belief that Red Hat is foisting systemd on Linux for the purpose of making Linux harder to repair and manage, and have hired clever Rube Goldberg software creator Leonart Poettering to create something that works, but in the long term will be a house of cards only specialists (primarily Red Hat specialists, they hope) can work on. Well, that's certainly character assassination (and well deserved in my opinion), but I think I got rid of the innuendo :-) SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141015125352.037f4...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Wed, 15 Oct 2014 19:27:20 +0100 Jonathan Dowland j...@debian.org wrote: On Wed, Oct 15, 2014 at 12:42:58PM -0400, Steve Litt wrote: They were using ConsoleKit, which was orphaned upstream some time after systemd-logind came along. I rest my case. There's nothing at all (not even Red Hat) preventing anyone (even you!) from stepping up and taking over development of ConsoleKit. It's a considerably smaller proposition than taking over GNOME 2, a vastly more complex suite of software and libraries, and that actually did happen (http://mate-desktop.org). OK, I'll be the first to admit that after Red Hat caused the demise of ConsoleKit (and probably lots more important software), I am free to take significant time out of my day job (that feeds my family) and rescue all sorts of software that Red Hat deliberately scuttled. Even though, apparently unlike 80% of today's kernel developers, nobody pays me to do it. http://spectrum.ieee.org/computing/software/whos-writing-linux But that has nothing to do with my I rest my case statement. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016011251.530d0...@mydesq2.domain.cxm
Re: Conflict of interest in Debian
On Thu, 16 Oct 2014 06:06:00 +0900 Joel Rees joel.r...@gmail.com wrote: 2014/10/16 5:46 Ric Moore wayward4...@gmail.com: On 10/15/2014 12:39 PM, Steve Litt wrote: We've actually been in this place before. Wonderful Linux company Caldera became SCO (oversimplification, but you know what I mean). Wonderful Linux company Corel changed their CEO, and promptly accepted money from Microsoft and dropped all their Windows software. [...] If you knew Caldera, then you would know that it started with capitalization and focus by the retired CEO of Novell, Ray Noorda. Now that is my kinda guy, as he knew that Linux would grow to be more than a desktop hobby toy. And, he put his own money where his mouth was. He was not responsible for what happened after. I still have a copy of the Caldera install CD and it worked like a charm on an aging ThinkPad. But it was too pitiful to watch Netscape try to update itself. :) Ric Yes, Noorda was a good guy. I think Steve was talking about a later CEO. It was a bad time for Linux and a complicated situation. I just looked up Noorda, Caldera, SCO and WordPerfect on Wikipedia: http://en.wikipedia.org/wiki/SCO_Group I can't tell for sure, but it looks like Noorda was innocent of all betrayal. I'm pretty sure the Caldera/SCO badguy was a slimebag patent troll named Darl McBride. http://en.wikipedia.org/wiki/Darl_McBride About Corel, the other example I used... Corel had bought WordPerfect in 1996, and some time around Y2K came out with both Corel Linux, which was a pretty darn good desktop Linux for the time, and WordPerfect for Linux, which I paid for (and liked). Those times are long past, and I could find little on what happened with Corel, so I looked at my contemporaneous writing from that era: http://www.troubleshooters.com/tpromag/200010/200010.htm#_linuxlog Apparently, Corel CEO and board chair Michael Cowpland stepped down on 8/15/2000, and Derek Burney was appointed interrum president and CEO. On 10/2/2000, Corel and Microsoft announced a strategic alliance, involving Microsoft's infusion of $135 million for 24 million non-voting convertable shares. The short story, Microsoft bought Corel and Corel almost immediately stopped making any software for Linux. Both Caldera and Corel were co-opted by Microsoft and turned into Microsoft proxies in the battle against Free Software, but at least Corel didn't turn into patent troll. As I remember, the main non-Microsoft slimebags of the era were Darl McBride of Caldera/SCO, and Derek Burney of Corel. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141016015427.40554...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Tue, 14 Oct 2014 02:50:32 +0200 lee l...@yagibdah.de wrote: Joey Hess jo...@debian.org writes: So at this point, most of us are pretty tired of the subject. And just ignore it and the consequences because you're tired of thinking about it? Lee, he has a point. He sees nothing wrong with a Red Hat owned and controlled Linux, and is tired of hearing from those of us who do. The solution is trivial. If, as everyone claims, we're such a minority, he could filter us all out and never see our posts again. Problem solved. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014104059.26aad...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Tue, 14 Oct 2014 07:56:17 +0100 Jonathan Dowland j...@debian.org wrote: You are still writing as if you are going to be forced to run systemd, despite being repeatedly told that multiple init systems will be supported. I'm really struggling to continue to presume good faith on your part now. Hi Jonathan, The fact that Jessie now supports, for want of a better word, dual init, doesn't preclude this choice going away later. Given the email thread of the CTTE decision and the words of Poettering in the video, as well as *many* references in the CTTE decision that only one choice would be kept, I think the possibility of later removal of choice has moved from paranoid conspiracy theory to yeah, it might happen. For the same reasons, it looks to me like a continued systemd land-grab, resulting in Linux morphing from something anyone can work with into something requiring Red Hat special sauce, has also moved from paranoid conspiracy theory to yeah, it might happen. I think I said it a couple weeks ago: This systemd thing was once merely a technical disagreement, but it's transformed into a matter of trust. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014105347.21718...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Tue, 14 Oct 2014 11:25:23 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Lu, 13 oct 14, 18:30:41, Miles Fidelman wrote: Gee assuming that you don't run anything that has systemd dependencies and/or systemd-shim is actually maintained and kept up-to-date. Have you actually looked into what depends on systemd? PAM is enough for me, considering everything that uses PAM. They could have made their PAM plug compatible with the old PAM, but nooo. Because interchangability is not only not their goal, it gets in the way of their goal. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014105609.18076...@mydesq2.domain.cxm
Re: Conflict of interest in Debian
On Tue, 14 Oct 2014 08:05:06 -0400 Henning Follmann hfollm...@itcfollmann.com wrote: On Tue, Oct 14, 2014 at 07:56:40AM -0400, Marty wrote: It seems like free software employment and market share come with increasing risk to objectivity and technical quality. It's my main concern as a Debian user, as I consider recent trends. I hope that Debian members consider an amendment to restrict voting rights for members who have a financial interest in Debian or in any project used by Debian, to promote and protect the public interest. Why, what is the reason for that? Explain why they are less objective or anyone having no financial interest is more objective. You know darn well, Henning. In anything, not just Linux, not just Debian, not just systemd, when somebody has the responsibility of doing the best thing for the community or other entity, but they also have a financial stake in which way the thing goes, they have a huge incentive to vote in a way detrimental to the community or other entity. This is why bribery is a crime. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014110210.7696a...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Tue, 14 Oct 2014 11:33:56 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Ma, 14 oct 14, 10:40:34, Andrew McGlashan wrote: On 14/10/2014 9:50 AM, Joey Hess wrote: Sysvinit will continue to be supported on servers in Debian 8 (jessie) release of Debian. So you can continue to boot your production servers with sysvinit. Okay, for now, that is until more packages decide that they can't do without systemd. Debian testing (Jessie) will freeze on 5. November. That's about three weeks from now. No serious package maintainer is going to introduce major changes now. Andrei brings up an important point: We should enter phase two, where we: 1) Boycott (and be vocal about it) Gnome 2) Pressure all other upstreams into a no systemd dependencies pledge, and to the best of our abilities, boycott (and be vocal about it) those who don't comply. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014110645.725a1...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Tue, 14 Oct 2014 15:51:09 +0100 Jonathan Dowland j...@debian.org wrote: On Tue, Oct 14, 2014 at 10:40:59AM -0400, Steve Litt wrote: The solution is trivial. If, as everyone claims, we're such a minority, he could filter us all out and never see our posts again. Problem solved. Sadly not. If I were reading -user entirely for my own delectation, I'd have filtered many regulars long ago. Or simply stopped reading it, since I rarely ask questions anyway. But I, and I imagine many of my DD colleagues, are particularly interested in ensuring -user is a useful resource for our users, and by filtering out people, we don't get a clear picture of just how broken the list is. :-) I'd characterize it a little differently, and say you don't get a clear picture of how broken systemd is, but I understand what you're saying. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014110831.1fdd3...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Tue, 14 Oct 2014 16:37:30 +0100 Martin Read zen75...@zen.co.uk wrote: On 14/10/14 15:56, Steve Litt wrote: On Tue, 14 Oct 2014 11:25:23 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: Have you actually looked into what depends on systemd? PAM is enough for me, considering everything that uses PAM. They could have made their PAM plug compatible with the old PAM, but nooo. I find these statements confusing, and crave enlightenment. When I look up libpam-systemd on packages.d.o, I see the following sentence: This package contains the PAM module which registers user sessions in the systemd control group hierarchy. and the following dependencies: dep: libpam-runtime (= 1.0.1-6) Runtime support for the PAM library dep: libpam0g (= 0.99.7.1) Pluggable Authentication Modules library Now, I may be being dim here, but it looks to me like that means that libpam-systemd is, in fact, plug-compatible with PAM. So are you saying I could use sysvinit or nosh as my PID1, drop in libpam-systemd and no other systemd components, and have all PAM functionalities run properly? Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014114826.54c6e...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Tue, 14 Oct 2014 18:35:34 +0100 Martin Read zen75...@zen.co.uk wrote: On 14/10/14 16:48, Steve Litt wrote: So are you saying I could use sysvinit or nosh as my PID1, drop in libpam-systemd and no other systemd components, and have all PAM functionalities run properly? Thank you for the clarification. The short and vague answer is no; PAM modules that depend on external programs for correct operation don't run properly if those programs aren't present. (pam_systemd is not the only such module that is part of Debian.) For a longer and more accurate answer, I refer to the pam_systemd(8) man page: If the system was not booted up with systemd as init system, this module does nothing and immediately returns PAM_SUCCESS. It appears, then, that the answer is that your other PAM modules will not be prevented from running properly, while the pam_systemd module's behaviour will be reduced to a no-op returning PAM_SUCCESS, presumably meaning that it won't cause any PAM failures but that programs which expect it to have done something useful will probably not work correctly. Thanks for the clarification Martin, I therefore drop my PAM based objection, if and only if I see convincing evidence that Debian will always give and additional PID1 choice that is PID1 and nothing but PID1, and works with regular PAM, and regular PAM continues to be supported. Of course, then there's the matters of upstreams requiring systemd... SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014163104.67848...@mydesq2.domain.cxm
Re: debian-advocacy?
On Tue, 14 Oct 2014 15:17:27 -0500 Richard Owlett rowl...@cloud85.net wrote: Anders Wegge Keller wrote: On Mon, 13 Oct 2014 22:43:48 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: There's -offtopic (see my .sig), but apparently the anti-systemd crowd wants an audience :( Stop your condescending tone, CAREFUL, you insert foot-in-mouth past clavicle :-) Now wait a minute Richard. His tone *was* condescending, but of course, he was replying to somebody who dissed the list in an insulting way. ... and make your self useful Have you surveyed his other posts? He condescends a lot, and often gets snarky with me, and I deserve the snark only some of the time. And of course, the reply to *him* was snarky too. And I'm not being angel-nice right now. All that being said, as much as he's snarked at me in the past, yeah, I value his opinion, even when he's calling me wrong (in not the nicest possible way), which of course is why I haven't filtered him. by reading a book about change mangament. I don't know who you are or what your merits might be. I couldn't care less right now. You just need to stop. Right now! If your only contribution is to tell people off, ... If you could have been bothered to research his posts. He gives relevant publicly posted answers to questions. That's true. I have even publicly disagreed with him. I continue to value his input. Same with me. ... the whole project would be better off without you. *NO* Agreed. Andrei's OK. I know this impending systemd thing is bringing out the worst in me, and I think it's bringing out the worst in a lot of us. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014164230.07ee7...@mydesq2.domain.cxm
Re: debian-advocacy?
On Tue, 14 Oct 2014 18:11:31 +0200 Anders Wegge Keller we...@wegge.dk wrote: ... make your self useful by reading a book about change mangament. Without in any way endorsing or criticizing anything else that's happened in this thread, I'd like to ask what are some relatively simple change management books you'd recommend, especially in light of the fact that a lot of us want to change the PID1 software one way or another? I have a feeling such a book might make *me* more useful. Thanks, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014164517.48c4c...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Wed, 15 Oct 2014 00:15:40 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Ma, 14 oct 14, 16:31:04, Steve Litt wrote: Of course, then there's the matters of upstreams requiring systemd... As far as I understand none of the upstreams are actually requiring systemd itself (or more accurately systemd-logind), but the interfaces it is providing. I fail to see the distinction. And it also seems to make sense (why should every Desktop Environment implement it's own solution for this?). Because you don't want to inextricably drag a giant monolith into your Desktop Environment just to do a few things. And how were they handling this task before systemd? It's not like Desktops, Window Managers and whatever things like lightdm are called didn't exist before systemd. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141014175658.50d51...@mydesq2.domain.cxm
Re: Conflict of interest in Debian
On Tue, 14 Oct 2014 20:35:54 -0400 Marty mar...@ix.netcom.com wrote: http://spectrum.ieee.org/computing/software/whos-writing-linux Say hello to our new bosses? Check out what single company has 30% of the gatekeepers. Surprise, surprise. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141015005107.2e973...@mydesq2.domain.cxm
Re: implicit linkage
On Mon, 13 Oct 2014 08:18:57 +0100 Jonathan Dowland j...@debian.org wrote: On Sun, Oct 12, 2014 at 02:48:55PM -0400, Steve Litt wrote: On Sun, 12 Oct 2014 19:02:08 +0100 Martin Read zen75...@zen.co.uk wrote: On 12/10/14 18:13, John Hasler wrote: You have no problem with an 1800 line function? ... I have a problem with 1800 line functions in general; ... I have no problem with an 1800 line function. ... *What* 1800 line function? The commit URI that was shared was an 1894-line *file* with a large function definition starting at line 638 and ending at 1890. That's a 1252-line function. OK, %s/1800/1252/g I have a hunch the guy I replied to would have had as much of a problem with a 1252 line function as an 1800 line one. My Ruby friends disparage functions over 30 lines long. I view function lengths as an implementation detail and don't worry too much about them. The code looked reasonable to me. Not only that but you're looking at a commit dating from August last year. The function doesn't even exist any more in current systemd[1]. There are no functions of even a 100 lines length in that file now. [1] http://cgit.freedesktop.org/systemd/systemd/tree/src/core/dbus-manager.c I'm not that concerned about function lengths anyway. What I *DO* have a problem with is the guy's welding pam onto his new init, and welding other critical and former separate OS functionalities onto his toolset, preventing (either technically or by them being removed from the packages) former modules from being used. Which guy is that? The commit that the URI referenced was written by Lennart Poettering, so I guess you mean him; Yep. but that commit didn't touch the file that was being complained about. Maybe you mean one of the other 17 people who have contributed to that file? I wasn't talking about that commit, I was talking about what has been done, and what Poettering has stated his goal is. If I were to maintain his code, before reducing the 1800 line function, I'd do something about the function with 20 arguments, with each argument including a function call. I'd replace all of that with a struct pointer. I'd start with *reading the code* if I were you; something you guys clearly aren't doing. OK, nothing in that code was that important. I *did* notice a function with 20 arguments, and I, personally, would substitute a struct pointer for that. But, as I said before, my objection to systemd isn't coding style. But if you get past that you'll be pleased to discover that such clean ups and refactors are happening quite often. See e.g. df2d202e6ed4001a21c6512c244acad5d4706c87 (bus: let's simplify things by getting rid of unnecessary bus parameters). I'll leave you to guess the author of that one. I couldn't find that, but once again, I'm not saying anything about the coding style. As a matter of fact, the thrust of my post was basically that I'm not concerned about the referenced code's coding style, I'm concerned about the macro-architecture. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013141807.27141...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Mon, 13 Oct 2014 17:33:02 +0200 Didier 'OdyX' Raboud o...@debian.org wrote: I really don't buy the argument that the GR proposal was too quiet to be noticed by 6+ people. I mean: the proposition happened to be in the middle of the post-TC decision wave, on the mailing lists where it belonged. The people who cared about the whole default init for Debian question _were_ following and contributing to these various lists. I'm therefore claiming that the people who missed the GR proposal were not sufficiently interested (otherwise they would've been subscribed to either -vote or -project, where these proposals belong). I'm also thankful that the proposer limited his proposal to these lists (I'd have considered a spread of the call over -devel, -user or other lists an abuse). Le lundi, 13 octobre 2014, 16.15:02 Ian Jackson a écrit : If four other DDs send me and Matthew Vernon private email to say that they would support a GR on this subject, I will restart this conversation on -project. Doing this now despite the fact that the GR didn't reach its 6 seconds, 7 months ago, will lead to an incredibly bigger waste of time, just when we're about to freeze testing. The GR train passed… So what do you suggest instead? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013143754.7880d...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Mon, 13 Oct 2014 14:21:45 +0200 Thorsten Glaser t...@mirbsd.de wrote: On Mon, 13 Oct 2014, Miles Fidelman wrote: Those who are most impacted are sys admins of servers, and upstream developers I’m both, and I joined Debian to try to make an impact… - the two communities most impacted, but that seem to have no say in the matter. … but even then, am drowned by the masses. (I did not have the chance to Second the GR proposal because I was not even aware that there *was* one.) bye, //mirabilos mirabilos, Thank you for being one of the few who stood up and said hey guys, let's not rush to judgement here. No matter how things turn out, I'll always respect the stance you took, and how long you maintained that stance in spite of people opposing you. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013144052.51d0e...@mydesq2.domain.cxm
Re: debian-advocacy?
On Mon, 13 Oct 2014 19:45:03 +0200 Anders Wegge Keller we...@wegge.dk wrote: It seems that there's a lot of controversy about the SysV-replacement that should not be named. Most, if not all of the arguments for, as well as against seem to be of a philosophical, rather than stringent technichnical nature. As such, they are probably not suited for this list. The preceding sentence is not at all true. If Red Hat is using Debian as its proxy in monopolizing Linux, and morphing Linux into something completely different, this is the business of rank and file Debian users. So my question as a relative newcomer to the Debian ecosystem is if there is an -advocacy list, where the philosophical differences can be beaten into the ground, while keeping this list at a more factual level? You're not the first to propose such divide and conquer. Without a lot of stringent moderation, it's not going to work. If not, where do I propose the creation of such a list? It already exists: http://www.freelists.org/archive/modular-debian/ You can subscribe at http://www.freelists.org/list/modular-debian Posting there does not preclude expressing systemd displeasure here. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013145849.11cb9...@mydesq2.domain.cxm
Re: piece of mind (Re: Moderated posts?)
On Mon, 13 Oct 2014 20:13:23 +0200 Ansgar Burchardt ans...@debian.org wrote: As [1] shows the majority of Jessie users have migrated to systemd, probably as an effect of GNOME starting to depend on it (around May 2014) and the new init package (around June 2014). Everyone: Please, please, PLEASE read the preceding paragraph. Ansgar made my anti-systemd argument perfectly. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013150257.2da8b...@mydesq2.domain.cxm
Re: who is looking for a new distro as a result of systemd (particularly server-side users)
On Mon, 13 Oct 2014 17:24:29 + (UTC) Curt cu...@free.fr wrote: On 2014-10-13, Miles Fidelman mfidel...@meetinghouse.net wrote: I'm really curious to know how many others here have come to a similar conclusion, and what folks are looking at (in my case, SmartOS is looking better and better). Oh shit. If I were going to give up free software and go proprietary, I'd go Mac. Unfortunately, at this point I'm actually considering Mac as my final backstop. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013144912.64e44...@mydesq2.domain.cxm
Re: who is looking for a new distro as a result of systemd (particularly server-side users)
On Mon, 13 Oct 2014 14:02:16 -0400 Carl Fink c...@finknetwork.com wrote: Slackware springs to mind. Before this, I would have said that slackware sucks. From what I understand, they're proud that their package manager doesn't support dependencies. Sy wht? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013150100.33a3e...@mydesq2.domain.cxm
Re: debian-advocacy?
On Mon, 13 Oct 2014 23:18:01 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Ma, 14 oct 14, 06:53:12, Andrew McGlashan wrote: That list is basically irrelevant, no traffic at all, virtually. That only happens because people insist on posting off-topic stuff to -user instead of -offtopic. :s/off-topic/stuff that Andrei deems off-topic/ SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013190641.0fa09...@mydesq2.domain.cxm
Re: Way OT: Re. lines of code [was Re: implicit linkage]
On Tue, 14 Oct 2014 07:37:17 +0900 Joel Rees joel.r...@gmail.com wrote: The only way to fix that in systemd is for systemd to delegate the complicated stuff like managing dbus to child processes, so the processes that will occasionally stall won't impact the whole system as much. When/if that happens, we should see the hard dependencies between systemd and other stuff that has been absorbed by systemd disappear. The real problem is that Poettering and others over there have rather indicated an unwillingness to do that. Three words: Follow the money. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141013191401.07738...@mydesq2.domain.cxm
Re: implicit linkage
On Sun, 12 Oct 2014 03:05:59 +0200 lee l...@yagibdah.de wrote: Steve Litt sl...@troubleshooters.com writes: pingaddr=8.8.8.8 pingaddr=192.168.100.96 Why is this is defined multiple times? Mistake! The 8.8.8.8 isn't needed. That's a test of Internet connectivity, when what I wanted was to test LAN connectivity, which in my case is my firewall at 192.168.100.96. You can safely remove the 8.8.8.8. Obviously :-) Thanks for catching that. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141012125103.37e0c...@mydesq2.domain.cxm
Re: Bash usage: was implicit linkage
On Sun, 12 Oct 2014 09:33:43 +0100 Martin Read zen75...@zen.co.uk wrote: On 12/10/14 04:12, Peter Zoeller wrote: But the nice thing is shell scripting is simplistic easy to learn and understand. I refer the audience to David A. Wheeler's essay[1] on how to handle filenames correctly in shell scripts, and to the bug report that he filed against POSIX.1-2008[2] on the subject. From those, I take away the lesson that no, shell scripting is not simplistic, easy to learn, and easy to understand. It just *looks* simplistic, easy to learn, and easy to understand, in ways that make it a horribly effective footgun. [1] http://www.dwheeler.com/essays/filenames-in-shell.html Martin, Thanks so much for the preceding resource. It's worth its weight in gold, and I've bookmarked it for quick retrieval. This essay practically screams out for somebody to write a C program that takes an argument of an arbitrary string, finds all files in a directory, and returns a long string with those files separated by the arbitrary string. A shellscript can then use mktemp or some other facility to make that arbitrary string, pass it to the C program, and then use the temporary string as a sure fire field separator. The C program could also take an option as to whether or not should find hidden files, and it could prepend ./ onto all relative paths not already beginning with ./. I might do that tonight. Thanks for this great info. I wish I'd had it a decade ago. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141012134204.37901...@mydesq2.domain.cxm
Re: implicit linkage (was: Re: Effectively criticizing decisions you disagree with in Debian)
On Sun, 12 Oct 2014 19:06:11 +0900 Joel Rees joel.r...@gmail.com wrote: Hmm. Let's comment that for people newer to scripting than I am. On Sun, Oct 12, 2014 at 6:28 AM, Steve Litt sl...@troubleshooters.com wrote: ### RUN THE DAEMON ### exec envuidgid slitt envdir ./env setuidgid slitt \ /d/at/python/littcron/littcron.py \ /d/at/python/littcron/crontab man exec for clues to that, understand that littcron.py is Steve's special cron (right, Steve?), and that he is setting up a special environment for things and there's other stuff there that I can only guess at, not having the code to littcron, I think. So I'll punt here. Exec takes the current process, which in this case is the daemontools run script, and swaps exec's argument for the current process. So, if the current process is a shellscript PID 4321, after exec gnumeric, PID 4321 is now Gnumeric, not a shellscript. envdir, envuidgid and setuidgid are executables provided by daemontools. Let's talk about envdir. Although in daemontools you can export environment variables to sub programs, just like in any other shellscript, idiomatic daemontools usage specifies that instead of exporting within a shellscript, you have an environment directory in which each desired environment variable is associated with a file of the same name as the environment variable name, and the contents of the file is the value of the environment variable. So: envdir ./env The preceding means look in ./env, and all filenames are environment variable names, and the contents of each is the value of the respective filename. setuidgid and envuidgid are daemontools provided executables to accommodate running as an arbitrary user instead of root. Consider the command: setuidgid slitt The preceding runs the entire command defined by its arguments as user slitt instead of user root. In other words: setuidgid gnumuser gnumeric test.gnumeric The preceding runs gnumeric as user gnumuser. One gotcha: It runs it as user slitt with user slitt's major group, but it doesn't run it with auxilliary groups, for slitt, defined in /etc/group. So if the command depends on membership in those auxilliary groups, you have to do some fancy footwork. Here's another challenge: Now that you're running as a non-privileged user, you can't read the ./env directory. This is where envuidgid comes in: envuidgid slitt The preceding tells daemontools that user slitt can read the environment directory. And the way envuidgid command works, after making this notation it simply passes control to the command defined in its arguments, which include envdir (which finally defines the environment directory) and setuidgid, and last but not least, the actual program you're daemonizing. And speaking of the devil, /d/at/python/littcron/littcron.py /d/at/python/littcron/crontab The preceding is the cron substitute I wrote, whose one argument is the crontab file you're using. If I wanted, I could manually run it in the foreground and it would function just fine. But I wanted it automatic, and managed as a daemon. So daemontools runs it as user slitt, and puts its environment variables in the /service/littcrond/env directory. Environment vars are important here, because my cron program is called upon by its constituants to run GUI programs, so its $DISPLAY and $XAUTHORITY vars must be set right. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141012141133.03803...@mydesq2.domain.cxm
Re: implicit linkage
On Sun, 12 Oct 2014 15:33:48 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Sb, 11 oct 14, 17:41:28, Steve Litt wrote: On Sat, 11 Oct 2014 22:28:31 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: Really? How do you write an initscript that restarts your daemon automatically in case it fails for some reason? Also, imapfilter doesn't write a pidfile at all, so I'd need to make at least some modifications to the script. Does imapfilter run in the foreground, or does it have an option to run in the foreground? In my configuration it runs in the foreground. It can be configured to detach from the terminal, but anything more complicated than that I'd have to script myself. Because it can run in the foreground, it's a prime candidate for daemontools (or one of the daemontools-inspired programs like nosh, etc). One more thing: In my belief system and priorities, I personally feel more comfortable making /system and /command, using the djb installer, rather than installing the Debian daemontools package. If creating two new top level directories makes you uncomfortable, the Debian daemontools package creates the service and command directories in existing subdirectories. Last time I looked, the documentation for Debian's daemontools package wasn't as good as the documentation for raw djb daemontools, but that might have changed. So if you don't like brand new top level directories, ignore my suggestions of using djb's instructions exactly, and consider the Debian package. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141012142432.6f798...@mydesq2.domain.cxm
Re: Bash usage: was implicit linkage
On Sun, 12 Oct 2014 17:07:01 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Sb, 11 oct 14, 21:40:49, Steve Litt wrote: From my viewpoint, shellscripts were never intended to be big, huge programs. To me, they just glue together commands, and have a few rudimentary branching and looping constructs. Isn't that like buying IKEA furniture, Exactly! but when you get home you realise all those little plastic bags with screws and mounting pieces are missing? Not similar, becase either the parts are there, or they're creatable with a few very basic tools (much easier to create files than screws). I will say this: Any program that requires additional scripting just to get it running is insufficiently advanced. (you can quote me on that) I can't argue with the preceding, because it's a belief, no more or less valid than my (very contradictory) belief. The best I could do is create a run script making program that asks you a few questions and writes the script for you. Which, if it would bring more people into the daemontools fold, isn't a half bad idea. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141012143419.10361...@mydesq2.domain.cxm
Re: implicit linkage
On Sun, 12 Oct 2014 19:02:08 +0100 Martin Read zen75...@zen.co.uk wrote: On 12/10/14 18:13, John Hasler wrote: Martin Read writes: I'm not seeing a serious problem with that function. You have no problem with an 1800 line function? The thing that you are asking me if it is the case is not the thing I said. I have a problem with 1800 line functions in general; they're clearly undesirably long. I don't have a *serious* problem with 1800-line functions *in general*, though they're certainly on my list of things that should be refactored. Moving on to the specific case, I don't have a *serious* problem with that particular 1800-line function. It certainly merits refactoring (I can even see an obvious starting point for doing so), but it's not unreadable or hard to follow; it's just inconveniently long. But while we're on the topic of things I have a problem with, here's one: people choosing to interpret I'm not seeing a serious problem with that function as I have no problem with that function :) I have no problem with an 1800 line function. Personally, I wouldn't write one, and I'd hate to maintain one, but how many lines the guy puts in his function is no business of mine. What I *DO* have a problem with is the guy's welding pam onto his new init, and welding other critical and former separate OS functionalities onto his toolset, preventing (either technically or by them being removed from the packages) former modules from being used. From my perspective, a toolset is a set of tools you can use singly, in combination, and *in combination with other tools*. If I were to maintain his code, before reducing the 1800 line function, I'd do something about the function with 20 arguments, with each argument including a function call. I'd replace all of that with a struct pointer. But then again, as a user, his implementation is none of my business, whereas his overall architecture is *certainly* my business, especially if it constrains my abilities to maintain/modify my system. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141012144855.1d37f...@mydesq2.domain.cxm
Re: Bash usage: was implicit linkage
On Sun, 12 Oct 2014 11:16:54 -0700 Don Armstrong d...@debian.org wrote: On Sun, 12 Oct 2014, Steve Litt wrote: This essay practically screams out for somebody to write a C program that takes an argument of an arbitrary string, finds all files in a directory, and returns a long string with those files separated by the arbitrary string. You seem to be looking for find -print0; \0 is one of the few characters which is not valid to have in a file name. Let me think about that. I wasn't aware that \0 couldn't get into a filename. I was concerned about the following in /http://www.dwheeler.com/essays/filenames-in-shell.html : = Most shells cannot store byte 0 in a variable at all. You can’t even pass such null-separated lists back to the shell via command substitution; cat $(find . -print0) and similar “for” loops don’t work. Even the POSIX standard’s version of “read” can’t use \0 as the separator (POSIX’s read has the -r option, but not bash’s -d option). = It's not like it's that hard to do this properly in a policy compliant POSIX shell, either. Use IFS and reset it as appropriate, or properly quote things. I'll try these things, before writing my own return each filename program. Thanks. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141012150633.0dc9e...@mydesq2.domain.cxm
Re: How to do this ?
On Sat, 11 Oct 2014 13:38:05 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Vi, 10 oct 14, 19:51:50, Erwan David wrote: I want to have a system which boots, and starts a subset of daemons. Then afterward I ssh to it, do something which 1) mount an encrypted disk, 2) start other daemons (which depends on the encrypted disk). I know how to do this with policy-rc.d, how can I do this with systemd ? My first though on doing this with sysv-rc would have been runlevels, why do you even need policy-rc.d? LOL, when I read the original question, I didn't answer because I thought he was inisting on a policy-rc solution. If policy-rc.d weren't required, and if it were me, the solution would be totally obvious, because I'm a daemontools type of guy... I'd put all the services to be started secondarily under daemontools. I'd have a directory somewhere, with empty filenames corresponding to the services I want to bring up secondarily: /home/slitt/servicelist or whatever. Then I'd make these shellscripts: # #!/bin/sh # this is uppp.sh if bring_up_encrypted_filesystem.sh; then for f in /home/slitt/servicelist; do rm -f /service/$f/down svc -u /service/$f done else handle_encrypt_up_error.sh fi # # #!/bin/sh # this is downnn.sh for f in /home/slitt/servicelist; do touch /service/$f/down svc -d /service/$f done if bring_down_encrypted_filesystem.sh; then poweroff else handle_encrypt_down_error.sh fi # Obviously I haven't tech-edited these, and also obvious I left a lot of stuff for the encrypted disk as an exercise for the reader, but basically: To boot up, you boot up, ssh in, and run uppp.sh To shut down, you ssh in, run downnn.sh. If you sometimes need to reboot instead of powering off, you could remove the shutdown from downnn.sh and just do it manually while you're ssh'ed in. HTH, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011124548.15d40...@mydesq2.domain.cxm
Re: question about systemd
On Sat, 11 Oct 2014 13:53:20 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Vi, 10 oct 14, 06:57:18, PETER ZOELLER wrote: This is really ticking me off. We are becoming just like Microsoft that one size fits all. Linux has always been about choice and modularity and reconfigurability where a user or admin can choose that what suits him/her and the type of system they want. You want sysvinit you use Debian or Slackware, want Upstart go to Ubuntu, want systemd go to Fedora/Redhat. Where in all this is my choice to have my system boot via the means I or any user or admin considers to be the appropriate method to boot their system? What's wrong with you people? Have you lost sight of why Linus designed this system? Its about simplicity, modularity and reconfigurability. You might want to check your facts: Linus Torvalds only created the Linux kernel, which is notoriously monolithic[1]. [1] https://en.wikipedia.org/wiki/Tanenbaum%E2%80%93Torvalds_debate This is very true, but the kernel knows its boundaries, and doesn't try to conquor all sorts of other, non-related, subsystems. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011124915.4c8e3...@mydesq2.domain.cxm
Re: implicit linkage (was: Re: Effectively criticizing decisions you disagree with in Debian)
abandoned in favor of systemd. I have a theory on that. runit, s6, init-ng, etc never caught on because sysvinit was considered good enough, and it was easier for the average person to work around its rough edges rather than learn a new init system. Then Red Hat decided to subsume all of Linux with systemd, and to do so, they convinced everyone that the sysvinit they'd used for years was horrible, and *we must instantly* move on. Meanwhile, read https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708 . runit, s6, init-ng, etc, never stood a chance, because *all of a sudden*, after years of sysvinit being though manageable, it was considered the kiss of death, and we didn't have no damn time to explore runit, s6, init-ng, etc. Follow the money. I contend Red Hat's vilification of sysvinit was as much self serving disease mongering as drug maker Burroughs Wellcome's late 1970's stigmatization of herpes, just after they invented an anti-herpes drug: http://en.wikipedia.org/wiki/Herpes_simplex#Society_and_culture Similar tactics, exact same exact motivation. As far as I understand Linus Torvalds himself admits that a modular kernel design is better, yet he choose to make Linux monolithic. On the other hand Hurd is still not even in a releasable state. The difference is that the kernel doesn't reach out and try to take over subsystems that are obviously outside its normal sphere of influence. Could it be that a modular design for such complex tasks becomes too difficult to *do it right*? There's no doubt that for a small, self contained subsystem, it's often easier to write your own, perhaps less modularly than might be ideal, rather than grab all sorts of modules which kinda-sorta fit but you need to massively code to make them mesh. On the other hand, when something gets big, like as big as systemd is trying to be, a monolithic solution, or even a modular solution with wide and detailed interfaces, is a constant bug risk, and disables smart people from making things with building blocks. Is systemd going to change the GNU/Linux ecosystem? Definitely. Will this change be good or bad? Only time will tell, but I'm quite sure that even if the change will turn out to be bad it will *not* destroy GNU/Linux, but help it evolve in better ways. Not if Red Hat has their way, and it appears they're on their way to getting their way. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011134008.4724d...@mydesq2.domain.cxm
Re: question about systemd
On Sat, 11 Oct 2014 20:06:14 +0200 Slavko li...@slavino.sk wrote: Ahoj, Dňa Sat, 11 Oct 2014 18:41:12 +0100 Brian a...@cityscape.co.uk napísal: And to illustrate how much work Debian maintainers put in to respond to users' concerns: root@gnome-jessie:~# apt-get install sysvinit-core systemd-shim Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: cgmanager libcgmanager0 libnih-dbus1 libnih1 Suggested packages: pm-utils The following packages will be REMOVED: systemd-sysv The following NEW packages will be installed: cgmanager libcgmanager0 libnih-dbus1 libnih1 systemd-shim sysvinit-core 0 upgraded, 6 newly installed, 1 to remove and 0 not upgraded. Need to get 482 kB of archives. After this operation, 1,030 kB of additional disk space will be used. Do you want to continue? [Y/n] What more could a Debian user want? I don't know what other users want, but i tried it some days ago (when the latest version of the systemd comes into testing) and i want e.g. to be able to reboot, shutdown, suspend and hibernate the machine as regular user from my XFCE session. That is all, what i want and when i try it, i get message about insufficient permissions. From what I've heard on this list, Xfce has drunk the systemd koolaid. If that's true, screw em, they're not the only game in town. If nothing else, use Openbox with a no-brand panel, and that's kind of like Xfce. Oh, and make a few sudoers entries so you can reboot, shutdown, suspend and hibernate as a normal user. I ask here for help, but no one (i expect the response especially from these who tells, that this ML is for support not for discussion) give me the solution how to get the sufficient permissions back. I'd just work around their silly BS. sudoers plus shellscripts plus one of those multi-launchers to call those shellscripts should do that job. And maybe submit a bug report to Xfce telling them their new master killed features you use every day. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011161605.6254c...@mydesq2.domain.cxm
Re: implicit linkage (was: Re: Effectively criticizing decisions you disagree with in Debian)
On Sat, 11 Oct 2014 21:21:14 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: On Sb, 11 oct 14, 13:40:08, Steve Litt wrote: sysvinit is an idea whose time has gone. sysvinit is a poor way to showcase the Unix Way. First of all, the whole idea of runlevels is bizarre, and adds a lot of complexity to init scripts. If you compare a daemontools /service/myserviced/run to an init script, you'll see an order of magnetude simplification, without sacrificing the flexibility of a shellscript. Why should I write a script? I'm not a programmer. Why should I configure and maintain a firewall? I'm not an admin. One's being a programmer is such an arbitrary division. OK, you're not the first guy I'd call if I wanted a device driver coded, but I'd have complete confidence in you to write a short shellscript. And, being able to write a short shellscript (which I'm sure you can do), would make you a much more able Linux administrator and user. [snip] I *might* characterize the preceding as trying to reduce complexity for the dufus who can't even write a shellscript. However, the cost of this reduced complexity for the dufus is huge complexity within the program: complexity even smart people can't work around without some truly ridiculous kludges. I can write a (simple) shellscript, but I wouldn't dare write an initscript or even a daemontools runscript. Daemontools runscripts are incredibly simple shellscripts, that I'm sure you could write no sweat except in very wierd edge cases. Here's my run script for my home-grown cron substitute: == #!/bin/sh ### DON'T START littcrond UNTIL THE NETWORK'S UP ### pingaddr=8.8.8.8 pingaddr=192.168.100.96 echo littcrond checking network 12 while ! ping -q -c1 $pingaddr /dev/null; do sleep 1 echo littcrond REchecking network 12 done ### RUN THE DAEMON ### exec envuidgid slitt envdir ./env setuidgid slitt \ /d/at/python/littcron/littcron.py \ /d/at/python/littcron/crontab == The last three lines are really one line that wordwraps in email. If I hadn't checked for the network being up, this would have been a two line shellscript. I've known you (online) for several months, and although we sometimes disagree, I know you're pretty smart, so I'm positive you could have written this shellscript without breaking a sweat. I have a theory on that. runit, s6, init-ng, etc never caught on because sysvinit was considered good enough, and it was easier for the average person to work around its rough edges rather than learn a new init system. I recently needed something to run imapfilter and restart it in case it might exit, so I had a look at daemontools. I gave up quickly after I realised the amount of scaffolding required just to get daemontools itself running (additional top-level directories, are you kidding?). With systemd (v215) I had to write this unit file: [clip Andre's easy description of daemonizing imapfilter with systemd] Yes, there's significant scaffolding, mostly revolving around installing daemontools. Also, Andre didn't bring this up, but it's implicit in his objection: Most daemontools documentation is terse and assumes a whole lot of Unix-smarts on the part of the reader, with few examples. That's why I wrote this document: http://www.troubleshooters.com/linux/djbdns/daemontools_intro.htm Armed with the preceding document, a person can learn daemontools in a day, and use it for the rest of his life. If you can run imapfilter in the foreground, it's trivial to have daemontools daemonize it for you. And you'll know *exactly* how it's going to work. The other benefit of daemontools is it works, every single time. It never misfires, it never behaves in ways that are unspecified or against specification, it keeps working for years, and a simple (as root) backup walks it from distro to distro. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011172828.4a603...@mydesq2.domain.cxm
Re: implicit linkage (was: Re: Effectively criticizing decisions you disagree with in Debian)
On Sat, 11 Oct 2014 23:20:34 +0400 Reco recovery...@gmail.com wrote: Hi. On Sat, 11 Oct 2014 20:47:36 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: [huge snip] No, that was just for the I'm sole user of this system, why would I need this logind stuff? crowd. Thanks, I'm perfectly aware why I don't need logind - it does not solve any of the problems I need to solve. Same for it's predecessor, ConsoleKit. If I ever need a computer with the multiple X servers running simultaneously - I'll consider using logind. Am I missing something. If I needed multiple X servers, wouldn't I just CLI log into different users on Ctrl+Alt+F2 and Ctrl+Alt+F3, and run startx from each? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011173500.03936...@mydesq2.domain.cxm
Re: implicit linkage
On Sat, 11 Oct 2014 22:28:31 +0300 Andrei POPESCU andreimpope...@gmail.com wrote: Really? How do you write an initscript that restarts your daemon automatically in case it fails for some reason? Also, imapfilter doesn't write a pidfile at all, so I'd need to make at least some modifications to the script. Does imapfilter run in the foreground, or does it have an option to run in the foreground? SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011174128.4afe4...@mydesq2.domain.cxm
Re: question about systemd
On Sat, 11 Oct 2014 20:03:18 +0100 Martin Read zen75...@zen.co.uk wrote: On 11/10/14 19:00, Nate Bargmann wrote: This is the question I have, what are the stated boundaries of the systemd project? Have any boundaries/goals been stated in terms of when systemd will be feature complete? What is the stated compliance to POSIX (Google doesn't seem to provide me good results)? In respect of the first two questions: I am not aware of any such firm statements having been made. In respect of your third question: Contrary to the implicit expectation that seems to be attached to this question, POSIX.1-2008 appears to have very little to say about how any of the things systemd does are supposed to work. I think the source of most POSIX questions re systemd is the fact that Poettering has publically stated POSIX should be ignored under certain circumstances, and I mean a lot more circumstances than any Linux implementation currently ignores it. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011173951.50c60...@mydesq2.domain.cxm
In Poettering's own words: was question about systemd
On Sat, 11 Oct 2014 22:58:18 +0200 Peter Nieman gmane-a...@t-online.de wrote: Didn't Mr. Poettering make it sufficiently clear in numerous speeches that the ultimate goal of the systemd people was to create an entirely new OS? Just listen to the first two minutes of the first youtube video you get when searching for his name: http://www.youtube.com/watch?v=LdRmnSHHVw4 Breathtaking! At timestamp 0:51 he says that systemd is now more than just an init system, it's a set of building blocks to build an operating system. Nowhere does he say that if you accept any of those tools, you need to throw away several tools you've been using, or that if you use certain systemd tools, you need to install many of them. He glosses over the in for a penny, in for a pound nature of systemd. It's not a set of a-la-carte building blocks, it's a huge meal. At timestamp 1:35, he says that systemd feels more like a real operating system. Amazing: here I thought that I *had* been using a real operating system since I installed Linux in 1998. We should rejoice that, after almost a couple decades, Debian is now, finally, a *real* operating system! At 2:20, he states that we believed the operating system design isn't the right design to have. Then why the hell are they still calling what they're moving to Linux? And what, we've been using the wrong operating system all these years? At 2:45 he says that you tell systemd what the dependencies of things are, and systemd figures out at boot time what to do. Hey, couldn't that be done with a make file, with a whole less code and fanfare? LOL, make boot. 7:19 he says that Debian's in the process of deciding whether Debian should switch to it. And at 8:06 he said Cannonical really hates systemd. So when the CTTE chose systemd, that's the only thing that brought Ubuntu on board, and all resistance was gone. Nice! Thanks guys. It appears that because of that vote, the Linux of the future will be a totally different operating system, and I'll have *very* limited choices if I happen to like the real Linux, instead of the Red Hat fork. How anybody familiar with this interview could have included systemd as an option, let alone the default, is beyond my comprehension. Several months ago somebody referred to systemd as Embrace, Extend, Extinquish, and at the time I thought he was over the top. But that's basically exactly what Poettering says in this 9:31 interview. Everybody should view this video! SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011182053.1dab4...@mydesq2.domain.cxm
Bash usage: was implicit linkage
On Sat, 11 Oct 2014 19:05:19 -0400 Doug dmcgarr...@optonline.net wrote: On 10/11/2014 05:28 PM, Steve Litt wrote: On Sat, 11 Oct 2014 21:21:14 +0300 Daemontools runscripts are incredibly simple shellscripts, that I'm sure you could write no sweat except in very wierd edge cases. Here's my run script for my home-grown cron substitute: == #!/bin/sh ### DON'T START littcrond UNTIL THE NETWORK'S UP ### pingaddr=8.8.8.8 pingaddr=192.168.100.96 echo littcrond checking network 12 while ! ping -q -c1 $pingaddr /dev/null; do sleep 1 echo littcrond REchecking network 12 done ### RUN THE DAEMON ### exec envuidgid slitt envdir ./env setuidgid slitt \ /d/at/python/littcron/littcron.py \ /d/at/python/littcron/crontab == The last three lines are really one line that wordwraps in email. If I hadn't checked for the network being up, this would have been a two line shellscript. I've known you (online) for several months, and although we sometimes disagree, I know you're pretty smart, so I'm positive you could have written this shellscript without breaking a sweat. /snip/ I've been using Linux seriously for about five years, altho I diddled around with it a bit earlier. About the time I started seriously using it, I took a course in Linux at the local community college, of which perhaps a third was devoted to scripting. Quite some time earlier, I had taken a course in Pascal, which I did very well in, and I actually wrote some useful code in that language for my job as an engineer. Prior to that, I used and wrote a lot of stuff in BASIC. Getting back to my Linux class, I received a B+. I don't know how much code I could have actually written when class was over, since one needs to know a lot more about system commands. At any rate, it's been about five years, and I could not now write the script you use to illustrate this message, and I'm not really sure I can read it! BASH scripts are written in perfectly logical code, quite similar, in fact, to Pascal. The problem is that they don't have the advantage of normal language; they rely on all sorts of abbreviations instead of the English words that more popular programming languages like Pascal, C, Python, and BASIC use. It's been probably 25 years since I wrote anything in Pascal or BASIC, but with about 30 minutes of reference-book research, I think I could go back and do it now. I can't imagine that to be true with BASH scripting. Just call me dufus. --doug Hi Doug, You're absolutely right. From my viewpoint, shellscripts were never intended to be big, huge programs. To me, they just glue together commands, and have a few rudimentary branching and looping constructs. Their loops are incredibly slow, you'd *never* do an inner loop in Bash. To me, if something involves you doing your own logic rather than calling other executables to do it, then Python, C, or some other real language is the way to do it. So yes, sysvinit startup scripts are on the far edge of what Bash should be used for. I'd say most daemontools run scripts are under 20 lines of code, so you'll be able to re-figure them, in a few minutes, six months from now. Now that I've said that, you can accomplish some pretty incredible things by gluing a few commands together. I wrote the better half of a http log evaluation program using a shellscript gluing together grep, cut, and awk, and piped the remainder (which was a much smaller data set than what went in) to a Python program or something like that. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141011214049.0a4dd...@mydesq2.domain.cxm
Re: Proposal: An alternative to mailing lists which isn't a forum
On Thu, 09 Oct 2014 23:16:33 +0300 softwatt softw...@gmx.com wrote: I have been contemplating the merits of mailing lists and comparing them with those of forums, [snip] If you're really impatient and prefer examples, head to the usage example at the bottom of the mail and skip the rest. Advantages of mailing lists: - Integrated with your mailing client - Filters - Work offline - Builtin PGP support - several others I haven't mentioned, but most of them stem from #1 You missed the biggest 2 advantages of mailing lists: 1) The messages come to you, you don't need to remember to go out to two dozen forums to find your conversations. 2) You don't need to log in to post a reply. I'm on several forums. But invariably, as time goes on, I forget their existence. The day's just too busy to walk around the web visiting groups. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141010104108.79d01...@mydesq2.domain.cxm
Re: Proposal: An alternative to mailing lists which isn't a forum
On Fri, 10 Oct 2014 17:58:04 +0300 softwatt softw...@gmx.com wrote: On 10/10/2014 05:41 PM, Steve Litt wrote: You missed the biggest 2 advantages of mailing lists: You missed my point entirely. Those two advantages are reserved in my proposal. OK then... As long as it continues acting like a mailing list and doesn't do anything dumb, it's fine with me --- I won't see the difference. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141010105946.11647...@mydesq2.domain.cxm
Re: Proposal: An alternative to mailing lists which isn't a forum
On Fri, 10 Oct 2014 18:01:15 +0300 softwatt softw...@gmx.com wrote: On 10/10/2014 05:58 PM, softwatt wrote: On 10/10/2014 05:41 PM, Steve Litt wrote: You missed the biggest 2 advantages of mailing lists: You missed my point entirely. Those two advantages are reserved in my proposal. I apologize. You only added some advantages to mailing lists. For some resume I assumed you're talking about disadvantages in my proposal. You assumed right, because I assumed your proposal wouldn't let me read from my email client and reply from my email client. But since your proposal lets me read from my email client and write from my email client, with no special effort on my part, it's transparent to me. SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141010110128.19315...@mydesq2.domain.cxm