From: Tim Wright <timw@splhi.com>
To: Miles Lane <miles@megapathdsl.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Will the IBM OMNI printer driver be making its way into the kernel tree?
Date: Tue, 13 Feb 2001 14:05:12 -0800 [thread overview]
Message-ID: <20010213140512.A8339@kochanski.internal.splhi.com> (raw)
In-Reply-To: <auto-000013960967@megapathdsl.net>
In-Reply-To: <auto-000013960967@megapathdsl.net>; from miles@megapathdsl.net on Tue, Feb 13, 2001 at 01:42:27PM -0800
Maybe I'm missing your point, but why would it go into the kernel tree ?
This is all stuff that gets done in userland under Linux.
The Omni drivers plugin with Ghostscript and generate output appropriate to
the printer. There's no kernel relevance here.
Tim
On Tue, Feb 13, 2001 at 01:42:27PM -0800, Miles Lane wrote:
> http://oss.software.ibm.com/developer/opensource/linux/projects/omni/
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/
--
Tim Wright - timw@splhi.com or timw@aracnet.com or twright@us.ibm.com
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI
next prev parent reply other threads:[~2001-02-13 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 21:42 Will the IBM OMNI printer driver be making its way into the kernel tree? Miles Lane
2001-02-13 21:53 ` Bill Nottingham
2001-02-13 22:05 ` Tim Wright [this message]
2001-02-13 22:18 ` Miles Lane
2001-02-13 22:34 ` Timur Tabi
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=20010213140512.A8339@kochanski.internal.splhi.com \
--to=timw@splhi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@megapathdsl.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.