From: Hal MacArgle <haltec@kvinet.com>
To: "heisspf@skyinet.net" <heisspf@skyinet.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Printing with Kernel 2.6.14.4
Date: Sun, 26 Mar 2006 13:55:31 -0500 [thread overview]
Message-ID: <20060326185531.GA1485@lnx2.kvinet.com> (raw)
In-Reply-To: <380-22006362515858506@M2W055.mail2web.com>
On 03-24, heisspf@skyinet.net wrote:
> Thanks Ray,
>
> >>Doesn't 'cat filename.txt > /dev/lp0' work
> >
> >
> > no since /dev/lp0 is not an executable file.
> >
>
> Ok my mistake. It does work under su, however, not as sudo which I had
> tried only.
>
> > as I have a hazy recollection that some versions of Slackware associated
> > lp1, not lp0, with the first parallel port.
>
> It is lp0.
>
> The reason I can't print not being connected with kernel 2.6.14 is, the way
> I see it, that there is no provision for a parallel port on "local printer"
> set-up, but only for "network printer".
>
> May be I should try to fumble around the source, /usr/src/linux.
>
> Regards
>
> Peter
Greetings: You got my curiosity in gear: I installed
Slackware 10.2, (test26) and it's module library, full install except KDE,
Tex or Games and hooked a Panasonic KX-P2123, Epson mode, printer;
and booted...
After logging in as root; lsmod reported that parport_pc and
parport were both installed automatically..
Noting there was one txt file already in root I invoked 'cat
loadlin16c.txt > /dev/lp0' and it printed perfectly.. I created
another txt file of all 60 lines and tried it too; AOK...
Since default Slack 10.2/26test is 2.6.13; something may have
happened when you bumped up from that?? I don't remember; maybe
you're not using Slackware10.2 here?? As an aside; I've been trying
to install SuSE 10.0 on the same machine, off and on for a week, to
no avail.. Forget which 2.6 patch it defaults to...
At least I know Slack still works as expected.. I didn't go
any further than that...
--
Hal - in Terra Alta, WV/US - Slackware GNU/Linux 10.1 (2.4.29)
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2006-03-26 18:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 1:58 Printing with Kernel 2.6.14.4 heisspf
2006-03-26 18:55 ` Hal MacArgle [this message]
2006-03-28 2:59 ` Peter
2006-03-28 5:20 ` Ray Olszewski
2006-03-28 8:09 ` Peter
[not found] ` <200603280742.21986.david@fierbaugh.org>
2006-03-29 3:55 ` Peter
2006-04-04 3:28 ` Problems with Scanner class in Blackdown JDK Mac
2006-04-05 6:26 ` Yawar Amin
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 2:04 Printing with Kernel 2.6.14.4 Peter
2006-03-24 6:44 heisspf
2006-03-24 14:55 ` Ray Olszewski
2006-03-21 2:40 Peter
2006-03-21 13:44 ` Hal MacArgle
2006-03-23 8:42 ` Peter
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=20060326185531.GA1485@lnx2.kvinet.com \
--to=haltec@kvinet.com \
--cc=heisspf@skyinet.net \
--cc=linux-newbie@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