From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <003f01c12746$e02faf60$3a8314d1@nwlink.com> Reply-To: "Conan Callen" From: "Conan Callen" To: "John Scroggins" Cc: References: <3B7C7C69.E7B84C68@earthlink.net> Subject: Re: Partial TOC for Comment] Date: Fri, 17 Aug 2001 11:03:10 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003C_01C1270C.33C16E10" Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov This is a multi-part message in MIME format. ------=_NextPart_000_003C_01C1270C.33C16E10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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?=20 Transactions on Software Engineering (Dec 1998, V24, N12) This is a = special issue on the topic of using scenarios to determine requirements. Conan ------=_NextPart_000_003C_01C1270C.33C16E10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable SELinux Administrators Guide
More on supported scenarios = -
 
As an example of the "Supported = Scenario" idea is=20 this:
 
The Redhat 7.1 Linux installer gives = you the=20 following choices:
Workstation
Server
Laptop
Custom System
 
It also allows you to choose your = firewall=20 settings.
Of coursed, depending upon what you = select, the=20 installer will place different components onto your system. A list of = supported=20 scenarios would also helps to limit the scope of customer support. When=20 contacting redhat for support, I would imagine that the first thing they = ask you=20 is which sku you selected.
 
These represent what most people will = be interested=20 in over the next year or so. Supporting just this set would help to = limit the=20 scope of SELinux, and the amount of work that the dev's need to do. I = dont know=20 if there is an installer for SELinux (just finished the redhat install = at last=20 night) but if would be convienent if there was an install had = a selection=20 menu like the above list. Has anyone considered wraping selinux into an = rpm=20 package? 
 
Transactions on Software = Engineering (Dec=20 1998, V24, N12) This is a special issue on the topic of using scenarios = to=20 determine requirements.
 
Conan
------=_NextPart_000_003C_01C1270C.33C16E10-- -- You have received this message because you are subscribed to the selinux 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.