From: Andre Noll <maan@systemlinux.org>
To: Nix <nix@esperi.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: A random initramfs script
Date: Fri, 17 Mar 2006 04:35:40 +0100 [thread overview]
Message-ID: <20060317033540.GE14051@skl-net.de> (raw)
In-Reply-To: <87r751q4wi.fsf@hades.wkstn.nix>
On 00:41, Nix wrote:
> > So I downloaded iproute2-2.4.7-now-ss020116-try.tar.gz, but there
> > seems to be a problem with errno.h:
>
> Holy meatballs that's ancient.
It is the most recent version on the ftp server mentioned in the HOWTO.
> Try <http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.15-060110.tar.gz>
> for a rather newer and more capable copy. :)
Much better. Thanks. This version works fine for me, just like busybox
ip does.
> Yes, the initial population of /dev is done by firing messages at udevd
> *from a shell script*. It's gone all the way from devfs's kernel-space
> hardwiring to something sufficiently extensible that a shell script can
> do all the neessary stuff to populate /dev :)
Yeah, Linux rulez :)
> [uClibc]
>
> Alternatively, just suck down GCC from, say, svn://gcc.gnu.org/svn/gcc/tags/gcc_3_4_5_release,
> or ftp.gnu.org, or somewhere, and point buildroot at that.
Yep, there's a 'dl' directory which contains all downloads. One can
download the tarballs from anywhere else to that directory. Seems to
work now.
Thanks
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
next prev parent reply other threads:[~2006-03-17 3:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 21:37 A random initramfs script Nix
2006-03-15 0:25 ` Andre Noll
2006-03-15 8:29 ` Nix
2006-03-15 18:57 ` Andre Noll
[not found] ` <87hd5zs9zm.fsf@hades.wkstn.nix>
2006-03-16 0:23 ` Andre Noll
[not found] ` <87zmjqq14r.fsf@hades.wkstn.nix>
2006-03-16 23:46 ` Andre Noll
2006-03-17 0:41 ` Nix
2006-03-17 3:35 ` Andre Noll [this message]
2006-03-17 14:58 ` Nix
2006-03-16 4:23 ` Neil Brown
2006-03-16 7:39 ` Nix
2006-03-17 1:22 ` Andre Noll
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=20060317033540.GE14051@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-raid@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).