From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Vanilla behaviour in Gentoo Linux (long email)
Date: Mon, 3 Nov 2003 12:55:15 -0500 [thread overview]
Message-ID: <200311031255.23334.vapier@gentoo.org> (raw)
In-Reply-To: <87k76hzboq.fsf@killr.ath.cx>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1397 bytes --]
On Monday 03 November 2003 10:58, Matthew Kennedy wrote:
> > developer preference deviating from vanilla behaviour? There have
> > been bugs filed about the removal of graphical /etc/issue which was
> > later removed. Why not give the user the choice and put control in
> > his or her hands? Customisation is a preference. My requests:
>
> I'm just glad the gory ASCII art one is gone :-D
/etc/issue.logo :p
but anyways ... asking for a blank /etc/issue is wrong imo ... every distro
has an issue, Gentoo gets one ... it's a basic file that every distro should
have by default ...
if you dont like it, make it a 0 byte file ... next time you update baselayout
it'll ask if you want to update /etc/issue, you just say no :p
> > On completion of merging the portage ebuild sleeps for ~15 seconds,
> > the baselayout ebuild for ~10 seconds and even dev-sources sleeps for
> > ~5 seconds whilst all these packages display messages. In my opinion,
> > this is downright pointless. On a source distribution like this one
>
> I agree with this. Delays and beeps are pointless. I'm probably
> asleep in bed when these important messages, complete with delays and
> beeps fly up the screen.
i dont like the sleep/beeps either and there is a bug open about einfo
logging ... go make some noise on it because it seems it's gone neglected by
the portage team
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2003-11-03 17:54 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 1:29 [gentoo-dev] Vanilla behaviour in Gentoo Linux (long email) Dhruba Bandopadhyay
2003-11-03 2:01 ` Brad House
2003-11-04 23:06 ` Steven Elling
2003-11-04 23:54 ` William Kenworthy
2003-11-07 23:24 ` Steven Elling
2003-11-08 0:09 ` Spider
2003-11-05 1:00 ` Terje Kvernes
2003-11-05 9:24 ` Paul de Vrieze
2003-11-05 11:46 ` Terje Kvernes
2003-11-06 15:47 ` Anthony de Boer
2003-11-06 17:01 ` Marius Mauch
2003-11-07 23:29 ` Steven Elling
2003-11-07 23:55 ` Eldad Zack
2003-11-03 2:16 ` Jon Portnoy
2003-11-03 8:49 ` Toby Dickenson
2003-11-03 16:36 ` Markus Nigbur
2003-11-03 17:02 ` Philippe Coulonges
2003-11-03 17:17 ` Caleb Tennis
2003-11-05 0:43 ` Anthony de Boer
2003-11-05 1:11 ` Camille Huot
2003-11-03 2:19 ` Chris Smith
2003-11-03 3:33 ` C. Brewer
2003-11-03 3:45 ` Jon Portnoy
2003-11-03 6:31 ` C. Brewer
2003-11-03 6:40 ` Jon Portnoy
2003-11-03 7:03 ` C. Brewer
2003-11-03 5:55 ` [gentoo-dev] " Björn Lindström
2003-11-03 6:33 ` Spider
2003-11-03 11:15 ` purslow
2003-11-03 8:44 ` [gentoo-dev] " Donnie Berkholz
2003-11-03 9:37 ` Paul de Vrieze
2003-11-03 10:11 ` Antonio Dolcetta
2003-11-03 9:39 ` Robin H. Johnson
2003-11-03 15:36 ` Matthew Kennedy
2003-11-03 15:58 ` Matthew Kennedy
2003-11-03 17:55 ` Mike Frysinger [this message]
2003-11-03 21:01 ` Martin Schlemmer
2003-11-03 18:40 ` Donnie Berkholz
2003-11-03 18:47 ` Mike Frysinger
2003-11-04 5:49 ` Donnie Berkholz
2003-11-04 19:04 ` Marius Mauch
2003-11-03 16:25 ` Luca Barbato
2003-11-04 6:31 ` Jesper Fruergaard Andersen
2003-11-04 7:08 ` Troy Dack
2003-11-04 10:03 ` Paul de Vrieze
2003-11-04 11:49 ` Christian Birchinger
2003-11-05 10:48 ` Thomas de Grenier de Latour
2003-11-05 12:03 ` Christian Birchinger
2003-11-04 17:18 ` Martin Schlemmer
2003-11-04 10:08 ` Thomas de Grenier de Latour
2003-11-04 17:15 ` Martin Schlemmer
2003-11-04 7:34 ` Troy Dack
2003-11-04 8:04 ` C. Brewer
2003-11-04 10:08 ` Paul de Vrieze
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=200311031255.23334.vapier@gentoo.org \
--to=vapier@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