From: Christian Loitsch <gentoo-dev@loitsch.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] ideas/bugs
Date: Fri, 1 Mar 2002 18:39:16 +0000 [thread overview]
Message-ID: <20020301183916.A13540@matrix.netsoc.tcd.ie> (raw)
hi,
I just finished compiling the base system on an MMX-130 Mhz with 48MB of
Ram. (slow but doable). Note that 48MB were nearly always enough for
the compilation! (ok glibc would have liked more ;).
I made some observations, and would like to know, which of them are
considered as bugs. (so that I can enter them in bugzilla)
* why is there an mta-mysql USE flag, and no mta-postgres?
* why do you call the postgresql-flag postgres? After all its name is
postgresql (you don't call mysql mys)
* why are the permissions of /etc/make.conf so strict (only 600 on my
machine) (i hope it wasn't me who changed them ;)
* as I am behind a firewall, which asks for username and password, I
could not use wget. The only program, which is (afaik!) capable of
even "tunneling" through an ftp-proxy is lftp.
I downloaded a static version (and modified the lftp-get script, so
that it accepted a Path-option) and it worked really well.
But it took me quite some time to realize that bootstrap doesn't use
FETCHCOMMAND. You could at least mention it somewhere.
I also really think that lftp is more appropriate than wget.
* fortunately I have access to a machine outside the firewall and was
therefore able to make the rsync there and then download it via ftp,
would be really nice, to do this directly.
* why does the installation of grub won't work if /boot is not a
partition on its own? (had no cdrom and "installed" the iso-image
temporarely on the boot-partition)
* my installed system works "worse" than the iso-image.
the installation-manual does not explain how to set up the right
keyboard and "make menuconfig" shows funny chars instead of the lines.
(afaik this is only an Env. variable, but which one)
* depscan is maybe not called with the right params in the boot-scripts:
depscan: Usage depscan ....
* why do you ask users in you manual to execute depmod, if it is in 1 of
your boot-scripts?
* I guess the best way to avoid "broken" Gentoos because of forgetting
the -w option with nano, would be to make an alias right at the
beginning. (like nanow)
* i think that you should also treat pcmcia a little bit in your
install-manual.
* because of wrong parameters the pcmcia-boot-script failed. But there
was no message. like [ FAIL ]
* I have not yet verified the next point:
I have a pcmcia-network-card, but because of a race condition (will
make a bug-report), I had to remove the net.eth0 script (rc-update del
net.eth0), and call it manually.
Surprisingly when I halt the system there is still a message:
?? Bringing down eth0 ?? which of course fails, because I brought
it down already manually.
Please note that I do _not_ consider everything I mentioned as bug!
christian
ps: Gentoo really rocks!
next reply other threads:[~2002-03-01 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 18:39 Christian Loitsch [this message]
2002-03-01 23:02 ` [gentoo-dev] ideas/bugs Martin Schlemmer
2002-03-04 13:34 ` [gentoo-dev] ideas/bugs Christian Loitsch
2002-03-04 15:49 ` Martin Schlemmer
2002-03-05 4:05 ` Chad M. Huneycutt
2002-03-05 12:15 ` Christian Loitsch
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=20020301183916.A13540@matrix.netsoc.tcd.ie \
--to=gentoo-dev@loitsch.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