Re: LSB init scripts and multiple lines of output
Adam Borowski wrote: The friend muttered something about Ubuntu being as flaky as Windows, then rebooted and started the installation anew... This is not an Ubuntu mailing list. It's pretty annoying to require all us d-i developers to get this far down in the mail before we realize that the problems you are describing are (probably) not d-i problems. -- see shy jo signature.asc Description: Digital signature
Re: LSB init scripts and multiple lines of output
martin f krafft wrote: also sprach martin f krafft [EMAIL PROTECTED] [2006.06.01.2122 +0200]: Starting RAID device md0 ... 3 drives, done Starting RAID device md1 ... 3 drives, done Starting RAID device md2 ... 2/3 drives, degraded Starting RAID device md3 ... 1/3 drives, failed Starting RAID device md4 ... 3 drives, done What do people think about that? Would combining the drives that went well make sense? Starting RAID devices... md0, md1, md4 done Starting RAID device md2 ... 2/3 drives, degraded Starting RAID device md3 ... 1/3 drives, failed The Starting RAID devices... could be put before the startup. I guess the gain I see is that on normal operation only one line is printed while providing more detailed and still legible information in case of a failure. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
On Fri, Jun 02, 2006 at 02:36:15AM -0400, Joey Hess wrote: Adam Borowski wrote: The friend muttered something about Ubuntu being as flaky as Windows, then rebooted and started the installation anew... This is not an Ubuntu mailing list. It's pretty annoying to require all us d-i developers to get this far down in the mail before we realize that the problems you are describing are (probably) not d-i problems. My sincere apologies. For my defense, I was ranting about why hiding error messages is unacceptable not about the installation is bad, but certainly mentioning just a certain brand new Debian-like distribution wasn't clear enough. And I still haven't completed the report I once promised on the behavior of d-i on low-end 486 with various amounts of memory... -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
also sprach Thomas Viehmann [EMAIL PROTECTED] [2006.06.02.0847 +0200]: Would combining the drives that went well make sense? Starting RAID devices... md0, md1, md4 done Starting RAID device md2 ... 2/3 drives, degraded Starting RAID device md3 ... 1/3 drives, failed Nice, but is it worth the trouble? Remember, I need to do all this with POSIX shell. Sure, it's not that hard, but... -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system ah, but a man's reach should exceed his grasp, or what's a heaven for? -- robert browning signature.asc Description: Digital signature (GPG/PGP)
LSB init scripts and multiple lines of output
Hi, I am faced with the problem on how to tackle multiline output from an init.d script, which I have just converted to LSB. Since the package is mdadm and RAID is kinda essential to those that have it configured, I'd rather not hide information but give the user the entire process. In my ideal world, this is what it would look like: Starting RAID devices ... /dev/md0 has been started with 3 drives. /dev/md1 has been started with 3 drives. /dev/md2 assembled from 2 drives - need all 3 to start it /dev/md3 assembled from 1 drive - not enough to start the array. /dev/md4 has been started with 3 drives. ... done assembling RAID devices: failed. I don't seem to be able to realise this with lsb-base, nor does it seem that they even provide for this. The alternative -- all in one line -- just seems rather uninviting: Starting RAID devices ... /dev/md0 has been started with 3 drives, /dev/md1 has been started with 3 drives, /dev/md2 assembled from 2 drives - need all 3 to start it, /dev/md3 assembled from 1 drive - not enough to start the array, /dev/md4 has been started with 3 drives. failed. Generally, I would not have a problem doing something like Starting RAID devices ... failed (see log for details). But the problem is quite simply that by the time the script runs, /var may not be there, and neither is /usr/bin/logger. So what to do? My current approach, which is to map short terms to the long errors is just too much of an obfuscating hack, and it runs more than 80 characters as well: Starting RAID devices ... md0 started, md1 started, md2 degraded+started, md3 degraded+failed, md4 started ... failed. Any suggestions? -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system drink canada dry! you might not succeed, but it *is* fun trying. signature.asc Description: Digital signature (GPG/PGP)
Re: LSB init scripts and multiple lines of output
On 6/1/06, martin f krafft [EMAIL PROTECTED] wrote: Hi, I am faced with the problem on how to tackle multiline output from an init.d script, which I have just converted to LSB. Since the package is mdadm and RAID is kinda essential to those that have it configured, I'd rather not hide information but give the user the entire process. In my ideal world, this is what it would look like: Starting RAID devices ... /dev/md0 has been started with 3 drives. /dev/md1 has been started with 3 drives. /dev/md2 assembled from 2 drives - need all 3 to start it /dev/md3 assembled from 1 drive - not enough to start the array. /dev/md4 has been started with 3 drives. ... done assembling RAID devices: failed. I don't seem to be able to realise this with lsb-base, nor does it seem that they even provide for this. The alternative -- all in one line -- just seems rather uninviting: Starting RAID devices ... /dev/md0 has been started with 3 drives, /dev/md1 has been started with 3 drives, /dev/md2 assembled from 2 drives - need all 3 to start it, /dev/md3 assembled from 1 drive - not enough to start the array, /dev/md4 has been started with 3 drives. failed. Generally, I would not have a problem doing something like Starting RAID devices ... failed (see log for details). But the problem is quite simply that by the time the script runs, /var may not be there, and neither is /usr/bin/logger. So what to do? My current approach, which is to map short terms to the long errors is just too much of an obfuscating hack, and it runs more than 80 characters as well: Starting RAID devices ... md0 started, md1 started, md2 degraded+started, md3 degraded+failed, md4 started ... failed. Any suggestions? Yes. Starting RAID devices ... md0 ok, md1 ok, md2 2/3, md3 failed, md4 ok ... failed I would go to check why just 2 out of 3 disks are ok in md2 and why md3 failed. The only missing information from the output above is if md3 failed with 0 or 1 disk ok. I really think that all that multpline lines are annoying and hard to debug, since it's not in RAID services but almost everywhere. If the service 'foo' isn't starting and you've no idea the reason, because there's too much stuff to read during the boot, it will be easier just look at 'md3 failed', and associate it with the mountpoint that hosts the files for that service. Unfortunately it seems that the common sense says otherwise, and people are just populating more and more the boot output as admin it isn't useful for me, really. regards, -- stratus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 martin f krafft wrote: I am faced with the problem on how to tackle multiline output from an init.d script, which I have just converted to LSB. Since the package is mdadm and RAID is kinda essential to those that have it configured, I'd rather not hide information but give the user the entire process. In my ideal world, this is what it would look like: Starting RAID devices ... /dev/md0 has been started with 3 drives. /dev/md1 has been started with 3 drives. /dev/md2 assembled from 2 drives - need all 3 to start it /dev/md3 assembled from 1 drive - not enough to start the array. /dev/md4 has been started with 3 drives. ... done assembling RAID devices: failed. I don't seem to be able to realise this with lsb-base, nor does it seem that they even provide for this. The alternative -- all in one [...] what about $ cat raid . /lib/lsb/init-functions log_action_msg Starting RAID devices ... log_action_msg /dev/md0 has been started with 3 drives. log_action_msg /dev/md1 has been started with 3 drives. log_action_msg /dev/md2 assembled from 2 drives - need all 3 to start it log_action_msg /dev/md3 assembled from 1 drive - not enough to start the array. log_action_msg /dev/md4 has been started with 3 drives. log_failure_msg ... done assembling RAID devices: failed. $ ./raid Starting RAID devices ... /dev/md0 has been started with 3 drives.. /dev/md1 has been started with 3 drives.. /dev/md2 assembled from 2 drives - need all 3 to start it. /dev/md3 assembled from 1 drive - not enough to start the array.. /dev/md4 has been started with 3 drives.. * ... done assembling RAID devices: failed. Best Regards, Andreas - -- Andreas Fester mailto:[EMAIL PROTECTED] WWW: http://www.littletux.net ICQ: 326674288 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEfyVLZ3bQVzeW+rsRAvD/AKCJza+5KPQOZ2wMVm/5upylsdcEjgCdFmT7 kfYIlW9IyE/Lcf4gZuWtzOU= =HR7O -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
also sprach Andreas Fester [EMAIL PROTECTED] [2006.06.01.1935 +0200]: log_action_msg Starting RAID devices ... log_action_msg is supposed to be used to log an atomic message, which is not the case the way we/you use it here. log_failure_msg ... done assembling RAID devices: failed. According to /usr/share/doc/lsb-base/README.Debian, this function does not comply with Debian policy. Whether I can actually use it or not isn't exactly clear from the README. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system i'd rather be riding a high speed tractor with a beer on my lap, and a six pack of girls next to me. signature.asc Description: Digital signature (GPG/PGP)
Re: LSB init scripts and multiple lines of output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 martin f krafft wrote: also sprach Andreas Fester [EMAIL PROTECTED] [2006.06.01.1935 +0200]: log_action_msg Starting RAID devices ... log_action_msg is supposed to be used to log an atomic message, which is not the case the way we/you use it here. why did I already expect that without having read the documentation? :-( module-init-tools also use the lsb functions, but they use a raw echo to print the module list, one module per line. Probably not the solution you are looking for ... Another possibility: log_begin_msg Starting RAID devices ... log_success_msg /dev/md0 has been started with 3 drives. log_success_msg /dev/md1 has been started with 3 drives. log_failure_msg /dev/md2 assembled from 2 drives - need all 3 to start it log_failure_msg /dev/md3 assembled from 1 drive - not enough to start the array. log_success_msg /dev/md4 has been started with 3 drives. log_failure_msg ... done assembling RAID devices: failed. but I did not have a look into the log_failure_msg and log_success_msg constraints. I think there are no other possibilities because all other functions internalls use echo -n, and adding the line feed manually might also not be what you want... Regards, Andreas - -- Andreas Fester mailto:[EMAIL PROTECTED] WWW: http://www.littletux.net ICQ: 326674288 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEfyxjZ3bQVzeW+rsRAt8qAJ4hIS/3TYtjC0UT/awzh3/TKDZPVwCggbMx Dl+KYP3c3nYpDH+Lwxfqxt0= =Bl++ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
On Thu, Jun 01, 2006 at 06:51:54PM +0200, martin f krafft wrote: In my ideal world, this is what it would look like: Starting RAID devices ... /dev/md0 has been started with 3 drives. /dev/md1 has been started with 3 drives. /dev/md2 assembled from 2 drives - need all 3 to start it /dev/md3 assembled from 1 drive - not enough to start the array. /dev/md4 has been started with 3 drives. ... done assembling RAID devices: failed. Have you considered: Starting RAID device md0 ... 3 drives, done Starting RAID device md1 ... 3 drives, done Starting RAID device md2 ... 2/3 drives, degraded Starting RAID device md3 ... 1/3 drives, failed Starting RAID device md4 ... 3 drives, done -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
also sprach Daniel Jacobowitz [EMAIL PROTECTED] [2006.06.01.2012 +0200]: Starting RAID device md0 ... 3 drives, done Starting RAID device md1 ... 3 drives, done Starting RAID device md2 ... 2/3 drives, degraded Starting RAID device md3 ... 1/3 drives, failed Starting RAID device md4 ... 3 drives, done What do people think about that? The only problem is that I start them all at once, then parse the output. So the above is not really true. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system when faced with a new problem, the wise algorithmist will first attempt to classify it as np-complete. this will avoid many tears and tantrums as algorithm after algorithm fails. -- g. niruta signature.asc Description: Digital signature (GPG/PGP)
Re: LSB init scripts and multiple lines of output
also sprach martin f krafft [EMAIL PROTECTED] [2006.06.01.2122 +0200]: Starting RAID device md0 ... 3 drives, done Starting RAID device md1 ... 3 drives, done Starting RAID device md2 ... 2/3 drives, degraded Starting RAID device md3 ... 1/3 drives, failed Starting RAID device md4 ... 3 drives, done What do people think about that? The only problem is that I start them all at once, then parse the output. So the above is not really true. not true means that I am not starting md1 after md0 has started successfully. Right now, the script does this: Stopping RAID devices... md6 busy; md5 busy; md3 busy; md2 busy; md0 busy; md1 busy; failed (6 busy, 1 stopped). Starting RAID devices... md0 running; md1 running; md2 running; md3 running; md4 started (3/3); md5 running; md6 running; done (6 running, 1 started, 0 failed). Which do people prefer? Btw: I cannot yet log which ones have been stopped, there's no easy way to find out with only POSIX and without /usr/bin/*. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system what do you mean, it's not packaged in debian? signature.asc Description: Digital signature (GPG/PGP)
Re: LSB init scripts and multiple lines of output
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 martin f krafft wrote: also sprach Daniel Jacobowitz [EMAIL PROTECTED] [2006.06.01.2012 +0200]: Starting RAID device md0 ... 3 drives, done Starting RAID device md1 ... 3 drives, done Starting RAID device md2 ... 2/3 drives, degraded Starting RAID device md3 ... 1/3 drives, failed Starting RAID device md4 ... 3 drives, done What do people think about that? The only problem is that I start them all at once, then parse the output. So the above is not really true. Starting them individually just seems better IMO, more atomic. For example, if starting md1 pukes really hard, the parent process still exists to start md[234]. - -- Ron Johnson, Jr. Jefferson LA USA Is common sense really valid? For example, it is common sense to white-power racists that whites are superior to blacks, and that those with brown skins are mud people. However, that common sense is obviously wrong. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEf0bpS9HxQb37XmcRAhoZAJ4ydDm3roD7c9iuFKach2pwMgab/gCgpvjc HaPS22BbDcMgUKlFaEkWDbw= =dIUY -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
also sprach Ron Johnson [EMAIL PROTECTED] [2006.06.01.2158 +0200]: Starting them individually just seems better IMO, more atomic. Mh, I would have to do config file parsing in the init.d script to figure out all available devices. mdadm already handles it; it starts all devices that haven't been started; short of a segfault, nothing can prevent it from starting md1 after md0 failed. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system everyone has a little secret he keeps, i like the fires when the city sleeps. -- mc 900 ft jesus signature.asc Description: Digital signature (GPG/PGP)
Re: LSB init scripts and multiple lines of output
also sprach martin f krafft [EMAIL PROTECTED] [2006.06.01.2150 +0200]: Stopping RAID devices... md6 busy; md5 busy; md3 busy; md2 busy; md0 busy; md1 busy; failed (6 busy, 1 stopped). Starting RAID devices... md0 running; md1 running; md2 running; md3 running; md4 started (3/3); md5 running; md6 running; done (6 running, 1 started, 0 failed). Which do people prefer? Btw: I cannot yet log which ones have been stopped, there's no easy way to find out with only POSIX and without /usr/bin/*. Here's the other version: piper:~# /etc/init.d/mdadm-raid restart [575] Stopping RAID array md6...failed (busy). Stopping RAID array md5...failed (busy). Stopping RAID array md0...failed (busy). Stopping RAID array md1...failed (busy). Stopping RAID arrays...done (3 array(s) stopped). Starting RAID array md0...done (already running). Starting RAID array md1...done (already running). Starting RAID array md2...failed (not enough devices). Starting RAID array md3...done (started, degraded [2/3]). Starting RAID array md4...done (started [3/3]). Starting RAID array md5...done (already running). Starting RAID array md6...done (already running). -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system everyone smiles as you drift past the flower that grows so incredibly high. -- the beatles signature.asc Description: Digital signature (GPG/PGP)
Re: LSB init scripts and multiple lines of output
On Thu, Jun 01, 2006 at 06:51:54PM +0200, martin f krafft wrote: In my ideal world, this is what it would look like: Starting RAID devices ... /dev/md0 has been started with 3 drives. /dev/md1 has been started with 3 drives. /dev/md2 assembled from 2 drives - need all 3 to start it /dev/md3 assembled from 1 drive - not enough to start the array. /dev/md4 has been started with 3 drives. ... done assembling RAID devices: failed. [...] Generally, I would not have a problem doing something like Starting RAID devices ... failed (see log for details). Really, PLEASE, don't! Hiding information is _never_ good. For any reason. Even if you expect the user to be non-technical. Let me go into a longer rant, only partially on the topic. I witnessed a smart but non-guru user install a certain brand new Debian-like distribution on her home box today. That person is a physicist doing medical research, with no sysadmin experience but familiar with quite a bunch of Unices. The machine was known to be good except for the disk, which in turn was checked on an identical box before. The trouble she faced consistent of a number of _random_ breakages with totally no usable error messages: * In about 1/3 tries, parted failed with whatever the error message was hidden by the installer's GUI. Tell me, how she was supposed to figure out what's wrong? (Skipping the fact that something as dangerous as parted should never be allowed to break in a common setup [1].) * At some point during the main installation phase (with nothing but a progressbar shown), the installer coughed up and barfed a window full of a Python backtrace right in the user's face, then died. I looked at the dialog, but couldn't figure out what went wrong, either. Perhaps taking a look at the logs (HIDDEN FROM THE USER) would be insightful, but the friend claimed that if the installation is supposed to be graphical, she's not going to let me do everything by hand [2]. Where's the goddamn meaningful error message? * Two times, a dialog simply popped up, saying: The installer has crashed. Just that. Without a single damn word about the cause, or even just a mention of what it was doing at the time. The friend muttered something about Ubuntu being as flaky as Windows, then rebooted and started the installation anew... * The GUI network setup tools simply ignore any failures. After choosing a SSID from a list (the list shows that the hardware and kernel-side stuff was working ok) then clicking Activate, the dialog simply shows nothing for ~20sec and then acts as if everything was in working order. What was wrong? Can you tell me from the provided information? Current vanilla text-mode Debian will give you a message after every action. With Ubuntu, you need to dig deeply to force the system to reveal what's going on. Finally, I had to leave; the friend hasn't succeed yet. [1]. A 50GB unformatted primary partition, the rest being on extended: two 50GB unformatted ones, 50+GB ext3 on /home, 1GB swap, 7GB ext3 on /. [2]. Get a reflex of going into mkfs/debootstrap mode at the smell of the first installer trouble and people will start spreading evil rumors about you :p --End of rant-- Now, let's go into your question: Starting RAID devices ... /dev/md0 has been started with 3 drives. /dev/md1 has been started with 3 drives. /dev/md2 assembled from 2 drives - need all 3 to start it /dev/md3 assembled from 1 drive - not enough to start the array. /dev/md4 has been started with 3 drives. ... done assembling RAID devices: failed. An user who has just the basic idea what RAID is will know what's going on instantly. When they'll call you, you will be able to help them right away. Starting RAID devices ... failed (see log for details). Now, you'll have to explain to the user how to get to the log. And what if the system is inoperative (with failed RAID, it almost certainly will be)? You can't be too verbose, but if you hide the most important parts, it will be a great disservice to the users. -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
Op do, 01-06-2006 te 22:29 +0200, schreef martin f krafft: also sprach martin f krafft [EMAIL PROTECTED] [2006.06.01.2150 +0200]: Stopping RAID devices... md6 busy; md5 busy; md3 busy; md2 busy; md0 busy; md1 busy; failed (6 busy, 1 stopped). Starting RAID devices... md0 running; md1 running; md2 running; md3 running; md4 started (3/3); md5 running; md6 running; done (6 running, 1 started, 0 failed). Which do people prefer? Btw: I cannot yet log which ones have been stopped, there's no easy way to find out with only POSIX and without /usr/bin/*. Here's the other version: piper:~# /etc/init.d/mdadm-raid restart [575] Stopping RAID array md6...failed (busy). Stopping RAID array md5...failed (busy). Stopping RAID array md0...failed (busy). Stopping RAID array md1...failed (busy). Stopping RAID arrays...done (3 array(s) stopped). Starting RAID array md0...done (already running). Starting RAID array md1...done (already running). Starting RAID array md2...failed (not enough devices). Starting RAID array md3...done (started, degraded [2/3]). Starting RAID array md4...done (started [3/3]). Starting RAID array md5...done (already running). Starting RAID array md6...done (already running). Seems ok to me. This way all boot messages look consistent. It would be nice if the log_action_end_msg would support warnings in addition to succes and failures, so the output would clearly distinguish a degraded array from a completely succesfully started array. Greetings Arjan signature.asc Description: Dit berichtdeel is digitaal ondertekend
Re: LSB init scripts and multiple lines of output
also sprach Arjan Oosting [EMAIL PROTECTED] [2006.06.01.2307 +0200]: It would be nice if the log_action_end_msg would support warnings in addition to succes and failures, so the output would clearly distinguish a degraded array from a completely succesfully started array. Consider filing a bug? It would be trivial, but the question is whether we want to extend the policy in that way. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system geld ist das brecheisen der macht. - friedrich nietzsche signature.asc Description: Digital signature (GPG/PGP)
Re: LSB init scripts and multiple lines of output
On Thu, Jun 01, 2006 at 06:51:31PM +0200, martin f krafft wrote: Any suggestions? Submit a feature request to LSB? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: LSB init scripts and multiple lines of output
also sprach Matthew R. Dempsky [EMAIL PROTECTED] [2006.06.02.0238 +0200]: Any suggestions? Submit a feature request to LSB? And wait 15 years? -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system microsoft: for when quality, reliability, and security just aren't that important! signature.asc Description: Digital signature (GPG/PGP)
Re: LSB init scripts and multiple lines of output
On Fri, Jun 02, 2006 at 02:44:54AM +0200, martin f krafft wrote: also sprach Matthew R. Dempsky [EMAIL PROTECTED] [2006.06.02.0238 +0200]: Any suggestions? Submit a feature request to LSB? And wait 15 years? Eh, that's only 2 or 3 debian releases from now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
