From: Douglas Russell <puggy@bobspants.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] install CD bloat
Date: Thu, 21 Aug 2003 10:54:20 +0100 [thread overview]
Message-ID: <200308211054.27513.puggy@bobspants.com> (raw)
In-Reply-To: <1061458448.415.115.camel@vertigo>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think there are two camps trying to put forward points here and I'm
reasonably convinced that the camp arguing strongly for a vim are the camp
which also plan to us their livecds for rescue and popping in all over the
place to get a useful basic linux system. I can quite understand that in this
case having a powerful editor would be extremely useful. However, considering
purely the case of the installation, and download size I'm sure the
experienced users who are more likely to be using vi would be able to manage
editing a single file with nano.
I must say I really liked the idea from earlier on which would allow you to
easily add things to your livecd easily to make your own custom livecd, then
you can make it as huge as you want, with vim, emacs or whatever, creating
your perfect livecd.
Puggy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/RJbRXYnvgFdTojMRAl8TAJ9w3brdOi3s06q3H3ewe4JznHK0igCeN6au
4Bqv42YSEFkdF+cYz5ikQmA=
=YyHu
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-08-21 9:56 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 19:42 [gentoo-dev] install CD bloat Kurt Lieber
2003-08-18 21:17 ` Dhruba Bandopadhyay
2003-08-18 23:03 ` Stuart Herbert
2003-08-19 0:06 ` Bob Johnson
2003-08-19 1:33 ` Luke-Jr
2003-08-19 6:47 ` Sven Vermeulen
2003-08-19 6:54 ` Jon Portnoy
2003-08-19 6:59 ` Sven Vermeulen
2003-08-19 7:10 ` Jon Portnoy
2003-08-21 5:00 ` Stewart Honsberger
2003-08-21 6:16 ` C. Brewer
2003-08-20 1:10 ` Luke-Jr
2003-08-20 7:31 ` Sven Vermeulen
2003-08-20 13:09 ` Chris Gianelloni
2003-08-20 12:39 ` Chris Gianelloni
2003-08-20 13:18 ` Michael Cummings
2003-08-20 13:18 ` Douglas Russell
2003-08-20 14:05 ` Tobias Sager
2003-08-20 15:27 ` Aron Griffis
2003-08-20 15:56 ` Svyatogor
2003-08-20 15:51 ` Chris Gianelloni
2003-08-20 16:27 ` matt c
2003-08-20 17:09 ` Douglas Russell
2003-08-20 18:36 ` Paul de Vrieze
2003-08-20 22:51 ` Stuart Herbert
2003-08-20 16:31 ` Eric Olinger
2003-08-20 17:05 ` Matt Rickard
2003-08-21 5:13 ` Stewart Honsberger
2003-08-21 5:42 ` Jon Portnoy
2003-08-21 5:59 ` Stewart Honsberger
2003-08-21 6:08 ` Jon Portnoy
2003-08-21 6:25 ` Stewart Honsberger
2003-08-21 6:51 ` Ralph F. De Witt
[not found] ` <3F4464DC.1010904@snerk.org>
2003-08-21 6:30 ` Jon Portnoy
2003-08-21 16:58 ` [gentoo-dev] OT: Re: Nano. WAS: " Stroller
2003-08-21 17:41 ` Mike Frysinger
2003-08-21 9:34 ` [gentoo-dev] " Chris Gianelloni
2003-08-21 9:54 ` Douglas Russell [this message]
2003-08-21 17:55 ` Jon Portnoy
2003-08-21 9:52 ` Toby Dickenson
2003-08-20 18:43 ` Paul de Vrieze
2003-08-20 22:42 ` Stuart Herbert
2003-08-20 23:34 ` Tavis Ormandy
2003-08-21 1:16 ` Chris Gianelloni
2003-08-21 2:06 ` Luke-Jr
2003-08-21 10:29 ` Paul de Vrieze
2003-08-23 14:43 ` Stuart Herbert
2003-08-20 15:22 ` Aron Griffis
2003-08-20 12:43 ` Kurt Lieber
2003-08-20 14:09 ` Luke-Jr
2003-08-20 18:40 ` Paul de Vrieze
2003-08-20 20:01 ` Daniel Armyr
2003-08-20 23:05 ` William Kenworthy
2003-08-19 11:21 ` Chris Gianelloni
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=200308211054.27513.puggy@bobspants.com \
--to=puggy@bobspants.com \
--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