Re: systemd, again
Most people who are not OK with systemd have better things to than try to persuade debian-devel that the debian prject's transition to it is problematic, and at more than just the implementation level. See how much fun it is to belittle? See how good it feels? More important than numbers is content. The objections being raised seem diverse, dire and cogent, while the defenses seem to be mere vague reassurances expressed in tones just as dismissive as yours was just there. Peter Rooney On 06/09/14 07:00 AM, Matthias Urlichs wrote: > That doesn't change the fact that most people who are OK with systemd have, > to put it mildly, better things to do these days than to participate in yet > another "discussion" about how evil, overbearing, non-Unix-way-ish, buggy, > or being-driven-by-a-principal-author-who-is-a-*censored* systemd is. > -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/540b2b7a.2060...@shaw.ca
Re: PulseAudio
Having read both sets of docs (and not merely the two pages named), I have to assert that the question is not a troll. The end user docs explain to end users how to use PA when everything's going according to plan, and cover some common glitches. I have gained no additional understanding of the concepts behind PA, though I suppose that if I went through those pages again I might be able to pick out some specific terminology to search elsewhere for. PeteR On 17/07/13 01:24 AM, John Paul Adrian Glaubitz wrote: On 07/17/2013 09:26 AM, Marc Haber wrote: Where are the end-user docs that explain the concept? Was that a troll question? Just use your favorite search engine. > http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/ > http://freedesktop.org/software/pulseaudio/doxygen/ PA also has excellent support on their IRC channels. I have been able to solve any problem I had with it so far and in all cases it turned out to be a user error. Adrian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51e952da.4080...@shaw.ca
Re: Check whether fsck would run
There's an option for that: fsck -N -T (don't show Title at startup) On 13/12/14 07:27 AM, Scott Schaefer wrote: On 12/13/2014 08:56 AM, martin f krafft wrote: Holger had the idea to add to molly-guard a check that would require the sysadmin to manually ack a reboot if fsck would be expected to run. I like it. Instead of parsing df -t output, invoking tune2fs -l and doing a whole bunch of grep magic, I wonder if there's a smarter way to find out if fsck would do something if it were to run now. There is fsck -A -t ext2,ext3,ext4,… ... but I could not find out how to ask it the question I want answered, which is: "hey, fsck, if you were to run right now on -All filesystems of -type as listed, would you want to do a routine check?" Do you know? Cheers, Per man fsck ... *-N*Don't execute, just show what would be done. Which, unfortunately, always outputs one line: fsck from util-linux-ng 2.17.2 ... but then lists the fs-specific fscks that it would run .. [/sbin/fsck.xfs (1) -- /] fsck.xfs /dev/md0 [/sbin/fsck.ext3 (1) -- /boot] fsck.ext3 /dev/sda1 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/548d0d0c.8030...@shaw.ca
