Rar. I've finally got the Netgear happier. I grabbed an OpenWRT 2.4.30 kernel and hacked that into my OpenEmbedded image. That stopped the init panic messages. I've also done some work on faking up a /etc based on the values from nvram - this should hopefully mean I have persistent data over reboots as well as meaning you can upgrade from a stock Netgear DG834G image and keep your settings. I think I'm going to have to write a very basic bit of C to crypt the password though, as there doesn't seem to be any existing tiny utility in OE that'll do so.
Anyway. This post is done from my desktop sshed to the Netgear which is connected to the ADSL and doing IPv6, and I'm then sshed from there to the via IPv6 (I could have setup the routing so I just sshed directly from my desktop through the Netgear, but this was quicker). Yay! That proves the ethernet, ADSL and IPv6 works. Haven't tried the wireless yet.
I think I'm at the stage where I need to pull the OpenWRT kernel into the OE framework so I can build it all easily, and then I'll commit it and be able to provide an image in case anyone else is actually interested in this warbling. :)
I finally found some time to devote to hacking on the DG834G. Given that
it seems the bootloader checksums almost the entire flash on each boot a
writeable flash file system doesn't seem to be an easy option. This
rules out vanilla OpenWRT unfortunately, which is a shame given the
AR7Port. However as I'm familiar with
OpenEmbedded (which seems to be non
working at present, but is behind OpenZaurus which I run on my C3000) I
decided to have a look at getting that going. So now I have an image
that boots, creates a ramfs for
/, pivotroots the flash round to
/media/realroot, creates a bunch of symlinks and should give me a basic
filesystem to play with.
Except it's not very happy, producing
INIT: PANIC: segmentation violation! sleeping for 30 seconds.
messages. Booting to just /bin/sh works fine, but various things won't
run. I'm currently blaming this on the fact I haven't changed the
default Netgear kernel from 2.4.17, so the next course of action is
probably to use an OpenWRT based kernel and see how that goes.
ping is a very useful command. It lets me see if a host is up. If you block
ICMP ECHO/REPLY then I instead have to play the "Guess what service might be
listening" game. Or I assume your machine is down and might worry (because I
care). So please don't do it. I really don't see what you're trying to gain; it
strikes me as firewalling without actually thinking about it. Are you by chance
ignoring things like destination unreachable as well? And breaking PMTU
discovery? Well done you.
From an ubuntu-announce mail just received:
A slim default installation, occupying just 400 megabytes
Now I'm not picking on Ubuntu in particular here, but the word just really does seem to indicate that Tom Womack's proclamation that "Disk space is cheap" just continues to get truer and truer. My first well used Linux install was on a 40MB disk and I'm prepared to bet there are plenty of people who started with less. Even these days people like OpenWRT are producing distros that fit in 8MB of flash. I think it's a sad reflection that 400MB is considered a small footprint for a mainstream distro.
subscribe via RSS