From: Dylan Carlson <absinthe@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] livecd bug
Date: Sun, 8 Jun 2003 04:08:14 -0400 [thread overview]
Message-ID: <200306080408.14133.absinthe@gentoo.org> (raw)
In-Reply-To: <43014.194.85.81.130.1054836486.squirrel@mail.dgap.mipt.ru>
On Thu June 5 2003 2:08 pm, Andrew B. Panphiloff wrote:
> I installed gentoo-1.4rc4 with glibc-2.3.2, but when I tried to
> boot from livecd (1.4rc4) and make chroot to my system I get:
> Illegal instruction
> This error occure because of statically compiled bash on livecd.
> Can you fix it ?
Please file this on http://bugs.gentoo.org. This list is for discussion of
development-oriented topics only. This list is not for reporting bugs.
In the event you feel you must post this type of stuff to a mailing list,
try 'gentoo-user'. However if you truly want to get something fixed, it
needs to exist in Bugzilla first.
Cheers,
Dylan Carlson [absinthe@gentoo.org]
Developer, Java Lead -- Gentoo Linux
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-06-08 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 18:08 [gentoo-dev] livecd bug Andrew B. Panphiloff
2003-06-08 8:08 ` Dylan Carlson [this message]
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=200306080408.14133.absinthe@gentoo.org \
--to=absinthe@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