From: Timur Tabi <ttabi@interactivesi.com>
To: 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 16:34:16 -0600 [thread overview]
Message-ID: <4xDLsB.A.zkH.oZbi6@dinero.interactivesi.com> (raw)
In-Reply-To: <auto-000013965666@megapathdsl.net>
In-Reply-To: <auto-000013960967@megapathdsl.net> <20010213140512.A8339@kochanski.internal.splhi.com> <20010213140512.A8339@kochanski.internal.splhi.com>
** Reply to message from Miles Lane <miles@megapathdsl.net> on 13 Feb 2001
14:18:43 -0800
> The reason I asked about inclusion is that printing is one of the areas
> that Linux seems to struggle in terms of usability and I thought perhaps
> it would make sense to modular print drivers in the kernel tree.
No, improving printing support is something that the distribution vendors are
supposed to provide.
I think you're under the assumption that this support were to be placed in the
kernel, it would then become ubiquitous. That may be true, but it's irrelevant.
Instead, what is needed is a sort of "standard" that indicates what every Linux
distribution should have in addition to the kernel. And that's something that's
being addressed by organization such as the Linux Standard Base
(http://www.linuxbase.org/). You should ask them about it.
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
When replying to a mailing-list message, please direct the reply to the mailing list only. Don't send another copy to me.
next prev parent reply other threads:[~2001-02-13 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 21:42 Miles Lane
2001-02-13 21:53 ` Bill Nottingham
2001-02-13 22:05 ` Tim Wright
2001-02-13 22:34 ` Timur Tabi [this message]
2001-02-13 22:18 ` Miles Lane
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=4xDLsB.A.zkH.oZbi6@dinero.interactivesi.com \
--to=ttabi@interactivesi.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
all inboxes | Powered by JetHome®