From: Jesse Pollard <pollard@admin.navo.hpc.mil>
To: Russell Coker <russell@coker.com.au>,
"Stephen D. Smalley" <sds@epoch.ncsc.mil>,
selinux@tycho.nsa.gov
Subject: Re: expect
Date: Mon, 2 Dec 2002 08:09:20 -0600 [thread overview]
Message-ID: <200212020809.20563.pollard@admin.navo.hpc.mil> (raw)
In-Reply-To: <200212011308.58878.russell@coker.com.au>
On Sunday 01 December 2002 06:08 am, Russell Coker wrote:
> On Fri, 29 Nov 2002 21:02, Stephen D. Smalley wrote:
> > > Due to what I believe to be bugs in expect, the new open_init_pty
> > > program will not work correctly with old versions of expect. Version
> > > 5.38.0 works fine, version 5.32.2 is broken. I don't know when the bug
> > > was fixed exactly.
> >
> > I've backed out the open_init_pty changes to our internal copy of
> > run_init. I'd rather not have the base run_init functionality dependent
> > on a particular version of expect, and I'm not even sure that it is
> > wise to depend on having expect installed at all.
>
> I will not do the same for my Debian packages.
>
> I can see the benefit in having two options available for users in this
> case, as some smaller devices such as PDAs may not have space for expect.
> But Debian is a heavy distribution primarily designed for workstations and
> servers. Debian works well on laptops too but is not designed to scale
> down any further than that. So I think that there is no reason not to
> depend on expect.
>
> I have made my Debian packages depend on the appropriate version of expect
> so you can just install the packages and be sure that the right things are
> automatically installed.
IMHO not the best solution, since the existance of "expect" depends entirely
on local policy. At our site, it is not to be installed without a LOT of
justification first, and only with policy wavers on an individual basis.
Making it mandatory for the system to function would mean that the Debian
distribution will not be permitted. This isn't a major problem for us, at
least, since we have standardized on RH.
--
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2002-12-02 14:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 20:02 expect Stephen D. Smalley
2002-12-01 12:08 ` expect Russell Coker
2002-12-02 14:09 ` Jesse Pollard [this message]
2002-12-02 14:58 ` expect Russell Coker
2002-12-02 17:34 ` expect Tom
2002-12-02 19:40 ` expect Russell Coker
2002-12-02 22:00 ` expect Tom
2002-12-03 11:46 ` expect Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2002-11-29 15:43 expect Russell Coker
2002-10-27 19:44 expect Russell Coker
2002-10-26 20:52 expect Russell Coker
2002-10-26 21:32 ` expect Chris Albert
2002-10-26 22:07 ` expect Russell Coker
[not found] ` <3DBB2043.2010709@sympatico.ca>
2002-10-26 23:26 ` expect Russell Coker
1999-03-12 12:15 Expect Dean Takemori
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=200212020809.20563.pollard@admin.navo.hpc.mil \
--to=pollard@admin.navo.hpc.mil \
--cc=russell@coker.com.au \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
/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.