All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Conan Callen" <ccallen@windowpane.com>
To: "John Scroggins" <dataefx@earthlink.net>
Cc: <SELinux@tycho.nsa.gov>
Subject: Re: Partial TOC for Comment]
Date: Fri, 17 Aug 2001 11:03:10 -0700	[thread overview]
Message-ID: <003f01c12746$e02faf60$3a8314d1@nwlink.com> (raw)
In-Reply-To: 3B7C7C69.E7B84C68@earthlink.net

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

SELinux Administrators GuideMore on supported scenarios -

As an example of the "Supported Scenario" idea is this:

The Redhat 7.1 Linux installer gives you the following choices:
Workstation
Server
Laptop
Custom System

It also allows you to choose your firewall settings.
Of coursed, depending upon what you select, the installer will place different components onto your system. A list of supported scenarios would also helps to limit the scope of customer support. When contacting redhat for support, I would imagine that the first thing they ask you is which sku you selected.

These represent what most people will be interested in over the next year or so. Supporting just this set would help to limit the scope of SELinux, and the amount of work that the dev's need to do. I dont know if there is an installer for SELinux (just finished the redhat install at last night) but if would be convienent if there was an install had a selection menu like the above list. Has anyone considered wraping selinux into an rpm package? 

Transactions on Software Engineering (Dec 1998, V24, N12) This is a special issue on the topic of using scenarios to determine requirements.

Conan

[-- Attachment #2: Type: text/html, Size: 2289 bytes --]

  parent reply	other threads:[~2001-08-17 18:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  2:07 [Fwd: Partial TOC for Comment] John Scroggins
2001-08-16 23:12 ` Dale Amon
     [not found]   ` <3B7D591A.EA28B00C@earthlink.net>
2001-08-17 11:23     ` Dale Amon
2001-08-18 11:43       ` LeRoy Cressy
     [not found]         ` <20010818084601.A7060@vnl.com>
     [not found]           ` <3B7FD0EE.398E6F02@telocity.com>
2001-08-19  4:58             ` Dale Amon
2001-08-17 17:20   ` Benjamin D. Thomas
2001-08-17 19:00     ` John Scroggins
2001-08-17 17:37   ` Conan Callen
2001-08-17 20:05     ` John Scroggins
2001-08-16 23:18 ` Dale Amon
2001-08-17 18:03 ` Conan Callen [this message]
2001-08-17 19:51   ` John Scroggins
2001-08-17 20:09     ` Conan Callen
2001-08-17 11:42       ` Dale Amon
2001-08-17 22:21       ` John Scroggins
  -- strict thread matches above, loose matches on Subject: below --
2001-08-18 13:01 Westerman, Mark

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='003f01c12746$e02faf60$3a8314d1@nwlink.com' \
    --to=ccallen@windowpane.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dataefx@earthlink.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.