public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "C. Brewer" <cbrewer@stealthaccess.net>
To: azarah@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Runlevels
Date: Wed, 26 Mar 2003 09:52:17 -0800	[thread overview]
Message-ID: <20030326095217.2bc41b3c.cbrewer@stealthaccess.net> (raw)

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

Well I wasn't really asking for the wheel reinvented, more of a move from bias-ply to steel belted radials. Starting in single mode and executing /sbin/rc default brings up local and metalog, skipped postfix and cron, and left me with only one vc and never did make it to the startDM script. What I was trying to say is that instead of using numbered init runlevels, the package I referred to allows such as "telinit default" "telinit nonetwork" and will execute them as such. Also the need(8) seems to take care of a lot of stuff through code that you currently use bash scripts for, and allows you to rollback to any point in a runlevel. It comes with a nice userspace demo that you can check out without altering your current init setup. I just figured that if its simplicity and flexibility wowed even me, that perhaps it wouldn't be lost on anyone truly in the know. I know the standard answer of develop it myself and submit it, but I'm not a developer, so my next resort is to appeal
  to those that are:)

On an unrelated note, there must be a better way to report smaller bugs.. I mean do you really want to see a bugzilla report such as "Added ampersand to /sbin/rc to supress devfsd version output on boot"? 

Thanks for your time:)
-- 
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.



[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2003-03-26 17:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030326095217.2bc41b3c.cbrewer@stealthaccess.net \
    --to=cbrewer@stealthaccess.net \
    --cc=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.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