[Techtalk] Two quick questions: linking /dev/parport0 andnolsmod, modprobe, etc.

housekm at fastmail.fm housekm at fastmail.fm
Sun May 16 21:25:57 EST 2004


> 2> error.log 

-That's- exactly what I was thinking of - just too panicked to separate
it from the context I've usually seen it in: 2>/dev/null.  I'll post this
sort of thing on the newchix list, where it belongs, from now on, but did
want to say thanks for the very helpful reply.

Oh, and the flame thing was part of the general discouragement this
brought on - I'm on another non-Linux computer list that periodically
gets very touchy, but should have known that this was not that. 

Kathleen

Ah, that 
On Sat, 15 May 2004 18:45:49 -0700, "Anthony Gorecki"
<anthony at futurepoint.com> said:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On May 15, 2004 5:38 pm, housekm at fastmail.fm wrote:
> > Anthony, in trying to come up with the exact error message and being too
> > lazy and emabarassed to ask or look up how to pipe to /dev/null (I know,
> 
> Error messages are normally printed to stderr or piped to a system
> logging 
> daemon, which would make attempting to pipe the output to the null device 
> seem somewhat counter-productive. As the messages would have been written
> to 
> a file or output to the console by default, the null device would instead 
> destroy them, accomplishing the opposite of what you intended.
> 
> For reference, you can pipe the information from one program to another
> using:
> 	program_one | program_two
> 
> With multiple requirements, you can also construct more advanced command 
> structures by piping information to several programs in series:
> 	program_one -args | program_two -args "param" | program_three 2> error.log
> 
> Although I can't see how that level of system instability would be
> possible 
> under the circumstances, your next option would be to instruct your boot 
> loader to boot using runlevel 1, which may be able to bypass some of the 
> startup errors and allow you to repair the configuration and software.
> You'll 
> need to google your specific boot loader on that procedure, as they vary 
> depending on which piece of software you're using.
> 
> > (hoping no one takes this *at all* as an effort to blame Anthony, I hate
> > life too much at the moment to deal with stupid flames)
> 
> It wouldn't have been the first time, having been doing development,
> system 
> administration and customer support for several years, although I don't 
> believe I can be blamed in this case. Please let me know if you have any 
> questions which I can help you with, and good luck!
> 
> 
> - -- 
> Best Regards,
> Anthony Gorecki
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.3.4 (GNU/Linux)
> 
> iD8DBQFApsfN1YBSMGhoIMkRAj+JAJ0QgU5jjEf6vOkrUDZQpFR4Z/Dp8QCcCki3
> p92wOrMRLd3lx2IvoGFXhqg=
> =63n8
> -----END PGP SIGNATURE-----
> _______________________________________________
> Techtalk mailing list
> Techtalk at linuxchix.org
> http://mailman.linuxchix.org/mailman/listinfo/techtalk

-- 
http://www.fastmail.fm - The professional email service


More information about the Techtalk mailing list