All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: selinux@tycho.nsa.gov
Subject: Re: expect
Date: Mon, 2 Dec 2002 23:00:47 +0100	[thread overview]
Message-ID: <20021202230046.A8632@lemuria.org> (raw)
In-Reply-To: <200212022040.26257.russell@coker.com.au>; from russell@coker.com.au on Mon, Dec 02, 2002 at 08:40:26PM +0100

On Mon, Dec 02, 2002 at 08:40:26PM +0100, Russell Coker wrote:
> > easier. It's not just that sometimes you have several daemons to
> > (re)start, it is during development that you easily restart a given
> > service a couple dozen times. I know I considered the password request
> > a nuisance after the 5th or so time.
> 
> Good point.  When doing development you tend to have a dozen x-terms open at 
> once anyway, so reserving one for starting and stopping daemons should be OK.
> 
> Although this is when having labelled X windows would be good.

Actually, most of my development work is done remotely, and so I guess
for many other people, so X isn't a factor on the server-side.


> > expect is no longer required (and a couple of the recent postings here have
> > shown just why that may be a good thing).
> 
> The only real problem we have with expect IMHO is the problem I discovered 
> where some daemons don't start because the parent exits too fast.  I expect 
> that I'll solve that soon though.

Actually, it's more a problem of "do I really want Tk on this machine,
just so that I can run SELinx?" - it is a considerably extension of the
dependencies. Maybe I'm too old-school, but I cringe everything I
select a simple packet and it wants to install two dozen libraries and
programming languages in dependencies.
Or maybe that attitude is not for the SELinux world anymore. With a
regular system, the less stuff you have on it the more secure you can
feel (less possibilities for problems). On an SELinux machine, though,
that isn't (or at least shouldn't) be true anymore.


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
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.

  reply	other threads:[~2002-12-02 22:03 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   ` expect Jesse Pollard
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           ` Tom [this message]
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=20021202230046.A8632@lemuria.org \
    --to=tom@lemuria.org \
    --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.