From: Tim Waugh <twaugh@redhat.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Linux Kernel Maillist <linux-kernel@vger.kernel.org>
Subject: Re: Is printing broke on sparc ?
Date: Wed, 18 Apr 2001 09:20:58 +0100 [thread overview]
Message-ID: <20010418092058.H350@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0104171707310.22166-100000@filesrv1.baby-dragons.com> <Pine.LNX.4.32.0104171720370.22166-100000@filesrv1.baby-dragons.com>
In-Reply-To: <Pine.LNX.4.32.0104171720370.22166-100000@filesrv1.baby-dragons.com>; from babydr@baby-dragons.com on Tue, Apr 17, 2001 at 05:28:13PM -0700
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
On Tue, Apr 17, 2001 at 05:28:13PM -0700, Mr. James W. Laferriere wrote:
> Ok , There isn't a sysctl available to do that . I am also a
> little worried about the 'none' in ths below .
>
> root@udragon:~# sysctl -A | grep -i parp
> dev.parport.parport0.devices.active = none
Don't be: unless the printer driver is actually using the port at the
instant that you look at the sysctl, it'll say none. It's normal.
If you are printing at the time you look, keep checking sysctl and you
will see 'lp' there sometimes.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-04-18 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 0:54 Is printing broke on sparc ? Mr. James W. Laferriere
2001-04-17 12:42 ` Tim Waugh
2001-04-18 0:10 ` Mr. James W. Laferriere
2001-04-18 0:28 ` Mr. James W. Laferriere
2001-04-18 8:20 ` Tim Waugh [this message]
2001-05-16 0:14 ` Mr. James W. Laferriere
2001-05-16 0:27 ` kernel2.2.x to kernel2.4.x jalaja devi
2001-05-16 20:40 ` Alan Cox
2001-05-17 18:20 ` jalaja devi
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 12:37 Is printing broke on sparc ? Jesse Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010418092058.H350@redhat.com \
--to=twaugh@redhat.com \
--cc=babydr@baby-dragons.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox