Make sure there is no program running which still has the old ttyUSB device
still open.
-- Rod
-Original Message-
From: Mr Doug - dsc3...@yahoo.com
Date: Saturday, Jun 6, 2009 8:10 am
Subject: USB PORT assignment
To: debian-arm@lists.debian.org
I know I don't know enough about this so
fsck the disk on another system
depending on the size of the disk, you may be running out of ram in the fsck.
Any partition larger than 250Gb is dicey.
-- Rod
-Original Message-
From: Dave Potts d.j.po...@bcs.org.uk
Date: Sunday, Mar 29, 2009 8:10 am
Subject: NSLU2 Boot Stuck at
Martin Michlmayr wrote:
* Asier katxi...@gmx.net [2009-03-05 07:19]:
I've built kernel snapshots for armel based on 2.6.29-rc7. If you
2.6.29? Does it have fixed the DMABounce errors with nslu2 with 64 MB?
I don't think so, but Rod Whitby (CCed) should know for sure.
Whilst I saw some
Martin Michlmayr wrote:
* Asier katxi...@gmx.net [2009-01-19 07:31]:
Great! How can I backup ths nslu2 flash memory?
# cat /dev/mtd0 RedBoot
...
Yes
Actually, if you want to be able to reflash the image, or unpack it with
slugimage (so that you can repack it with a new Apex), then you
Asier wrote:
There's something I'm worring about. This morning I've made a backup of the
flash:
# cat /dev/mtdblock* nslu2-backup.bin
I have reflashed the nslu2 a few times with it without any problem. But if
I explode the backup with
# slugimage -u -i ../nslu2-backup.bin
and
Asier wrote:
I own a fantastic NSLU2 device and have installed Debian on it some months
working pretty well, but 32 MB of main memory isn't enough so I fatted it
with two 64MB modules, so it has 128 MB of main memory.
Note that at the moment, you'll only be able to use 64MB maximum without
Asier wrote:
You should be able to flash those directly into the appropriate mtd
partition (make sure it's not the RedBoot partition, or else you'll
permanently brick your device). However, it will need a 16 byte header
prepended - best to use slugimage to pack a new image and then flash the
Fernando Carolo wrote:
re-flashing a slug with upslug2 is safe, unless you mess with RedBoot
using --Complete-reprogram.
That option is not even enabled in any binary distribution of upslug2
that I'm aware of. You have to manually edit the source code and
recompile it yourself to enable that
Fernando Carolo wrote:
(Sorry, I sent my previous reply to Rod only, instead of sending it to the
list)
On Wed, Aug 13, 2008 at 6:56 PM, Rod Whitby [EMAIL PROTECTED] wrote:
Martin Michlmayr wrote:
I believe there's a tool that can change SysConf. Maybe this tool
could be included
Martin Michlmayr wrote:
I've built some kernel snapshots for armel based on 2.6.27-rc2.
I only briefly booted on some Orion machines, so consider these
completely untested. Try only if you have a serial console.
You can find the kernel packages at
Martin Michlmayr wrote:
* Xan [EMAIL PROTECTED] [2008-08-10 21:40]:
I have a nslu2. I installed debian-arm with installer in hardisk.
Now I have a problems and I run upslug2 unslung6.10-image. So now I
have Unslung on my slug. Surprisingly the network setting in
unslung are the same as I
Salvatore Iovene wrote:
Hello list,
yesterday morning I woke up, and realized my slug wasn't routing
anymore. It wasn't resolving my internal DNS or giving DHCP addresses.
I looked at it and noticed that the USB led was off: only the first 2
leds (from the top) were on.
I tried to turn it off
Martin Michlmayr wrote:
I've built some kernel snapshots for arm and armel based on
2.6.26-rc8. Please test them on your favourite ARM machine
and report success or failures to this list.
You can find the kernel packages at
arm: http://people.debian.org/~tbm/arm/kernel/r11700/
armel:
Holger Levsen wrote:
On Monday 23 June 2008 06:56, Rod Whitby wrote:
I'd like to start work on a Freecom FSG-3 kernel config in Debian, for
when upstream support finally gets merged in 2.6.27 ...
I guess adding those patches to the debian 2.6.26 kernel is no option?
That's certainly
Martin Michlmayr wrote:
I've built some kernel snapshots for arm and armel based on
2.6.26-rc7. Please test them on your favourite ARM machine
and report success or failures to this list.
You can find the kernel packages at
arm: http://people.debian.org/~tbm/arm/kernel/r11683/
armel:
Martin Michlmayr wrote:
* Martin Michlmayr [EMAIL PROTECTED] [2008-06-13 23:36]:
I've built some kernel snapshots for arm based on 2.6.26-rc6. Feel
free to test them on your favourite ARM machine and report success or
failures to this list. These kernels are for arm, not armel. I
haven't
Marc Singer wrote:
I know that I can detect an NSLU2 by looking at /proc/cpuinfo and
checking the Hardware: line for the NSLU2 moniker. I can also
detect whether or not APEX is installed on the system by calling
apex-env and checking for a release version, though this is a little
less reliable.
Martin Michlmayr wrote:
* Kevin Price [EMAIL PROTECTED] [2008-05-12 17:43]:
Kevin, since you have a serial console, are you interested in testing
the patches in #451882 and #421359?
Yes. My slug is now compiling apex-1.4.15 with the patch from #451882
(CONFIG_RAMDISK_SIZE=0x0050) I am
If you can get into upgrade mode (alternating red/green led), then it is
*extremely* unlikely that your slug is bricked.
Once it's in upgrade mode, the redboot telnet interface cli command parser is
not operable - that is normal.
Note that the SerComm upgrade protocol which upslug2 implements
Bob Cox wrote:
Giles Thomas [EMAIL PROTECTED] wrote:
There's nothing immediately obvious in the logfiles in /var/log; I've looked
at messages, syslog, kern.log and debug. Is there anywhere else I should be
looking for clues about why this is happening?
There may be a separate samba log
Giles Thomas wrote:
I've been playing with Debian on my NSLU2 for a few days now. With the
help of the wiki and the excellent install guide at
http://www.cyrius.com/debian/nslu2/install.html, I've got it up and
running, and I've set up a Samba share which I can see from my Windows
machine.
Giles Thomas wrote:
Rod - thanks for the suggestion. Unfortunately I don't think that's it
- the hard disk is externally powered. I've been using the disk and the
NSLU2 together for quite a while, with the unslung firmware, without
problems - so I think I can rule out interactions between
Holger Levsen wrote:
On Wednesday 19 March 2008 02:12, Rod Whitby wrote:
We'll need flash-kernel support and userland led management.
Ok, cool, that's not much :-)
The flash-kernel package already supports different devices, so that looks
quite straightforward.
Yep. The only problem
Tomasz Chmielewski wrote:
Holger Levsen schrieb:
Hi Rod, hi Tomasz,
Martin Michlmayr (and your work!) told me to contact you, to work on
getting debian-installer support for the Freecom FSG-3. Kudos and
thanks for your great work so far!
You're welcome.
I'm a Debian developer and have in
Rod Whitby wrote:
https://svn.nslu2-linux.org/svnroot/kernel/trunk/patches will always
have the latest version of my kernel patches for the fsg3.
Oops, make that:
http://svn.nslu2-linux.org/svnroot/kernel/trunk/patches
In particular,
http://svn.nslu2-linux.org/svnroot/kernel/trunk/patches
[EMAIL PROTECTED] wrote:
* Have a wiki up (but maybe you have one) so everybody (or some people)
can share ideas and the like about this todo list
http://qnap.nas-central.org/ exists if people want to use it.
See www.nas-central.org for other wikis (there's one for each manufacturer).
-- Rod
Jake McGraw wrote:
Anyway we could get the intel microcode rolled into this so I can help
test on the NSLU2?
My understanding is that the Intel microcode (even in the 2.4 version of
the license, which is less restrictive than earlier licenses) is still
not DFSG compliant, and therefore cannot
Jake McGraw wrote:
Aware of the issue, I wanted to know if we could get access to a
version of the latest Debian installer with the Intel microcode
(perhaps available at slug-firmware.net). This way we can test the
latest installer on the NSLU2, thereby avoiding the problems we had
with
Brendan Moran wrote:
I then flashed the new image onto my NSLU2 with upslug2. When I was done
that, I halted apex while it booted, and reset the environment variables
to the values that slugimage listed as it built the image.
You shouldn't have changed the environment variables at all. That
Gordon Farquharson wrote:
For the arm/ixp4xx Debian 2.6.24 kernel (used on the Linksys NSLU2), I
switched to Krzysztof Hasala's Ethernet driver.
The first paragraph contained the good news. The bad news is that
although Krzysztof's driver is works well, udev does not load the
driver
Sam Reed wrote:
Whenever the NSLU2 is set to a static IP of 192.168.1.77, and then
flashed it with the debian installer image, it is requesting an IP
addresses from DHCP erroneously. Ie it is not following the static ip
address (which is the Linksys default). Set to 192.168.1.78, and it uses
Cian Hannafin wrote:
And from what i've read, thumb drives only work in port 1 of an NSLU2,
That is not correct. That restriction only applies to the crippled
original vendor firmware.
SlugOS, Angstrom, OpenWRT and Debian on the NSLU2 have no restrictions
on what is plugged into the USB ports
Daniel Kahn Gillmor wrote:
I'm having difficulty flashing an image with my NSLU2.
When i try to send an image to it with upslug2, it works fine durin
gthe erasing step, but as soon as it tries to write data, it shows a
leading first character in the status line of *, which appears to
mean
Daniel Ascher wrote:
Is it still broken?
Doesn't even the Debian/NSLU2 Stable 4.0r0 on
http://www.slug-firmware.net/d-dls.php work?
No - it is a property of Debian/NSLU2 installations that they depend
upon a sane Debian repository, and there seems to be something at the
repository side which
Frank A. Kingswood wrote:
www.debonaras.org is down, and parked.
Who used to be running this domain?
Tom King (who manages the infrastructure for nslu2-linux.org) is the
domain registrant, is aware of the problem, and is working through the
problem with the registrar. www.debonaras.org will be
Joey Hess wrote:
I've prepared a build of d-i that uses the gnuab.org armel repository,
which currently holds the armel debs that the armel porters hope will
eventually get into Debian proper.
I made some minor modifications to d-i for this build, but it's
basically the same quality image
Riku Voipio wrote:
On Tue, Aug 07, 2007 at 04:06:54PM +0930, Rod Whitby wrote:
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
initramfs-tools: Depends: klibc-utils (= 1.4.19-2) but it is not going
to be installed
of the previous version (2007-02-27) of
this non-free NLSU2 image.
- -- Rod Whitby
- -- NSLU2-Linux Project Lead
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.4 (MingW32)
iD8DBQFGt8jZ5DZEEWQDKUYRAka6AJ4pMd62Q3MswrtR80jgArIg13nq/gCdGlDA
LwqIIrMEkscXqXvnrm3OqJE=
=kvcc
-END PGP SIGNATURE
[EMAIL PROTECTED] wrote:
Last week I bought a NSLU2, and I installed Debian on it as described
in http://www.cyrius.com/debian/nslu2/.
Now I want to install a new kernel on my slug, and I have a couple of
questions. In the docs (http://www.cyrius.com/debian/nslu2/
upgrade.html) I read that
Marc Singer wrote:
On Sat, Jul 21, 2007 at 07:33:59PM -0400, Joey Hess wrote:
Marc Singer wrote:
I've been looking for clues as to why one of my slugs would hang on
calling hwclock --show. The initial symptom is that it fails when it
attempts to run the hwclock.sh script.
IIRC this can
Marc Singer wrote:
I'm curious if we want to allow APEX to automatically detect more
memory on startup. The code in APEX that reconfigures the memory
controller and then scans memory to determine the amount of memory
installed on the slug appears to be working properly in 64MiB and
128MiB
? Not
100Mbit?
We didn't name it the slug for nothing ... ;-)
See http://www.nslu2-linux.org/wiki/Info/Performance for what you should
expect.
If you can add Debian figures to that page that would be good too ...
-- Rod Whitby
-- NSLU2-Linux Project Lead
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Marcus Better wrote:
Riku Voipio riku.voipio at iki.fi writes:
Broken initramfs? Seems libgcc_s.so.1 does not end up in the initramfs on
arm with glibc 2.5.
Should I file a bug report somewhere? nslu2-utils?
Since the slug is now unbootable, I tried to modify and rebuild the initramfs
be a better place to consolidate all the armel information.
-- Rod Whitby
-- NSLU2-Linux Project Lead
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Is there a free software ethernet
driver in works, and if so what is its status?
There is actually two (but the author of the first one which is
currently in the Debian kernel suggests using the second, and the second
one is much more likely to go upstream), but they
repository for which you can find the Trac
interface at:
http://trac.nslu2-linux.org/kernel/
-- Rod Whitby
-- NSLU2-Linux Project Lead
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Gordon Farquharson wrote:
I don't, but Phil Endecott wrote some instruction for building Apex
[1]. You'll have to figure out how to pad the mtdblock with 0xffs
though (I'm not sure if the latest slugimage does this - Rod Whitby
would probably know).
Slugimage *always* pads with 0xffs. It's
processor.
-- Rod Whitby
-- NSLU2-Linux Project Lead
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
be to work out how to add a small recovery
filesystem to the debian installer, to which the boot process falls back
to if it cannot load the rootfs from the hard disk.
Kind regards to every one in this great project :)
-- Rod Whitby
-- NSLU2-Linux Project Lead
--
To UNSUBSCRIBE, email to [EMAIL
anything else in #nslu2-linux on irc.freenode.net or
#debian-arm on irc.debian.org
-- Rod Whitby
-- NSLU2-Linux Project Lead
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Jeff Breidenbach wrote:
I can verify that there are still issues with the RC2 Installer if you
do not preformat the Flash drive beforehand.
Would it be helpful for me to put an nslu2 disk image online? That
way people could pre-burn their USB flash drive from a desktop
computer and skip a
Peter Naulls wrote:
While we're on the subject, I've managed to make the very latest
drivers from Intel (2.3 access library + 1.6 driver) work with a Debian
EABI system (little endian of course) with kernel 2.6.20-rc4.
...
If anyone wants to put it together sensibly, then get in touch. Or
Peter Naulls wrote:
On 3/28/07, Rod Whitby [EMAIL PROTECTED] wrote:
Rod Whitby wrote:
Peter Naulls wrote:
While we're on the subject, I've managed to make the very latest
drivers from Intel (2.3 access library + 1.6 driver) work with a
Debian
EABI system (little endian of course
Jeremy Brown wrote:
Just finished installing unslung, i decided not to go with sid unstable
alpha at least till i get used to this then i might move to SlugOS and
install go that route..
I typed cat cpuinfo to call BogoMips and i get this
# cat cpuinfo
Processor :
Joey Hess wrote:
It's a working installer, but it is --
* not official Debian
* not stable
* not appropriate for production use
For example, there is no guarantee that there will be an upgrade path
from the current armel system to the one that eventually (hopefully)
lands in Debian.
and redeployed for other purposes (e.g. for testing
Debian armel on nslu2 ...)
-- Rod Whitby
-- NSLU2-Linux Project Lead
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Laz wrote:
On Thursday 15 February 2007 05:10, Joey Hess wrote:
Rod Whitby wrote:
Looks like you're not loading the microcode.
FWIW, it's in /lib/firmware on an installed nslu2 system.
Aha! This is using the open source network driver (as far as I know!) and
didn't think it still had
Wouter Verhelst wrote:
It's obviously true that big endian architectures don't need to
byteswap, since they already have the data in network byte order in
their memory. Not having to do mangle your data before throwing it on
the network or after reading it from a socket clearly implies that
Laz wrote:
It looks like the kernel is booting fine, loading and modules it needs,
getting an IP address and then just stopping. Looking at the dmesg file, the
date is now two days in the past: I'd hope that wouldn't confuse it enough to
stop it booting!
Do you have the rtc - rtc0 symlink
Laz wrote:
I'll try to swap over the rootfs properly at some point. Is there any way
of telling the kernel what to use as the root partition? I'm used to
being able to set it with grub!
At the moment, You'll need to solder on the four pins for a serial
console, and set the cmdline in Apex.
Laz wrote:
I've been testing Debian armel on a Linksys NSLU2 over the past couple of
days. I built a kernel with EABI support and this seems to work fine both
with the normal arm port and with the armel rootfs in a chroot environment.
I have now mounted the (USB) disk on another Debian box
Martin Michlmayr wrote:
* Marc Singer [EMAIL PROTECTED] [2007-01-30 20:08]:
a new application for writing the environment from user-mode.
Interesting. Unfortunately it doesn't seem to work for me. It can
read the environment but not set it:
...
apex-env dump only shows zeros:
foobar:~#
Martin Michlmayr wrote:
* Rod Whitby [EMAIL PROTECTED] [2007-02-05 07:21]:
Assuming this build of apex puts the environment in the same block as
apex itself, are the debian scripts padding that block with FFs or
zeros? If the latter, that would explain it.
Ah, thanks. I remember
Martin Michlmayr wrote:
* Rod Whitby [EMAIL PROTECTED] [2007-02-05 07:34]:
I'm happy with it going in either spot. I've left room for it after
the microcode in the FIS directory area - we would just update
slugimage to use that area.
... I think that the APEX block is the right place
Marc Singer wrote:
I would like to clarify the recovery path for a bad APEX reflash. If,
for some reason, they lose power while erasing and rewriting APEX,
they will have a system that won't boot. It may be useful to have a
feature of upslug that can write just the second-stage loader. This
I was always envisaging the debian installer having a recovery rootfs in the
flash, and being able to switch between booting to the flashfs (especially if
the disk was not attached) or booting to the disk. Perhaps that can be done by
passing a flag on the kernel command line from Apex to the
Marc Singer wrote:
At 2007-01-11 22:01, [EMAIL PROTECTED] said:
I just installed debian-etch to a slug so I can use it for
development. It has the peculiar habit of disconnecting my ssh
session when I do work, e.g. compiling, installing packages.
Another console that is just used to watch
Bruno Altobelli wrote:
Was anyone able to find a workaround?
I am experiencing the same problem. Reflashing with a
standard Linksys firmware works, but trying with
di-nslu2 results in a (it seems) half-booting slug,
with the red led and no beeps.
No SSH possible but it replies to pings, a
Andrew Kesterton wrote:
I seem to be having the same problem, I can flash my nslu2 (both with
the Sercomm utility and upslug2) however when it boots I've never been
able to ssh in - I can succesfully ping my slug but nothing else, just
have the red LED and no beeps.
I downloaded the
for consumer ARM devices running custom
firmware!
-- Rod Whitby
-- NSLU2-Linux Project Lead
(see http://www.nslu2-linux.org/presentation.pdf for more info)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Martin Michlmayr wrote:
* Marc Singer [EMAIL PROTECTED] [2006-09-08 18:48]:
I'm not sure I understand the nature of the hurdle. AFAIK, there is
no technical hurdle to using the scripts as they were last proffered.
To be more clear, the slugimage script and APEX as we last tested were
Marc Singer wrote:
On Sat, Aug 19, 2006 at 10:28:12PM -0700, Marc Singer wrote:
On Sun, Aug 20, 2006 at 06:48:59AM +0930, Rod Whitby wrote:
Hmm - that makes me wonder how a Linux userland tool will update skip
regions in the FIS dir - I'm not sure that the FIS dir area is writeable
from
Marc Singer wrote:
On Sat, Aug 19, 2006 at 01:40:00PM +0930, Rod Whitby wrote:
A kernel that is less than 1MB still has a valid SerComm header (and
needs to do so for RedBoot-only slugs). I don't want different
partition formats depending on which first- or second-stage bootloader
you happen
Marc Singer wrote:
Note that APEX doesn't care about the order of the skips. It sorts
them by offset.
Also, having slugimage sort them in order before writing them out, and
apex sorting them before using them, can be our own small tribute to Jon
Postel (see the Robustness Principle from
that you can change the cmd line passed
to the kernel by RedBoot if you have a serial console but I'm not
entirely sure. I'm CCing Rod Whitby who probably knows.
You cannot change the cmdline in the NSLU2 RedBoot. You need to use
APEX (either as a first or second-stage bootloader) to be able to do
Marc Singer wrote:
The latest test.bin fails to boot.
+Ethernet eth0: MAC address 00:0f:66:7b:f7:b0
IP: 192.168.0.1/255.255.255.0, Gateway: 192.168.0.1
Default server: 0.0.0.0, DNS server IP: 0.0.0.0
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Red Hat certified release, version
Marc Singer wrote:
On Mon, Aug 14, 2006 at 12:25:43AM +0200, Martin Michlmayr wrote:
* Marc Singer [EMAIL PROTECTED] [2006-08-13 12:44]:
All good. I flashed the image the way I flash any upgrade. Since
it booted, I believe it's all good.
So, I can confirm that it also works for me. I've
Marc Singer wrote:
On Mon, Aug 14, 2006 at 09:02:33AM +0930, Rod Whitby wrote:
Marc Singer wrote:
On Mon, Aug 14, 2006 at 12:25:43AM +0200, Martin Michlmayr wrote:
* Marc Singer [EMAIL PROTECTED] [2006-08-13 12:44]:
All good. I flashed the image the way I flash any upgrade. Since
it booted
Marc Singer wrote:
On Sat, Aug 05, 2006 at 12:44:53AM +0200, Martin Michlmayr wrote:
copy kernel code from flash to RAM
copy ramdisk file from flash to RAM
$T0a0f:00020650;0d:0003ddc0;#a4
However, it works after changing the size to 8 blocks.
Given that the loader/APEX partition has to be
Marc Singer wrote:
I released apex-1.3.30.
Have you tried compiling apex with GCC 4.1.1 (i.e. Debian Etch default
version)?
I tried tonight, and the resulting apex.bin fails to boot (just prints
strings like $T0a0f:0120;0d:01ff2fec;#09
over and over in response to keyboard input.
Just
...
-- Rod Whitby
-- NSLU2-Linux Project Lead
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The existing utilities that access the FIS directory from userspace for upgrade
and configuration save and restore purposes currently rely (for the nslu2) on
the existence of kernel, SysConf and Flashdisk flash partitions, but the
utilities have been written to enable those names to be easily
Don't get me wrong - I also think it's great to have an alternative to RedBoot
as a first-stage bootloader, and will install APEX as a RedBoot replacement on
one or more of my slugs as soon as it has network access.
But I will never recommend such a thing to the tens of thousands of users of
Marc,
Do we want to leave a little more room for future versions of APEX which have
more functionality (i.e. Networking support and usb mass storage support, even
NFS rootfs support ...) that might take more than the space you currently have
allocated? Is the start location and size of the
We also need to preserve the last block (128KiB), which holds the FIS
directory, a 100+KiB unused area (we were considering using that to store the
NPE microcode if we couldn't use the copy already in RedBoot, but we could also
use that for the APEX configuration area if it is able to be in the
Off-topic for this list, but we will need both big-endian and little-endian
support if we are going to also consider using the two-stage loader in SlugOS
(OpenSlug, etc).
-- Rod
-Original Message-
From: Martin Michlmayr [EMAIL PROTECTED]
arm, not armeb (or, rather, both, but there's no
really think your concerns are unwarranted :-)
-- Rod Whitby
-- NSLU2-Linux Project Lead
-Original Message-
From: Kevin Price [EMAIL PROTECTED]
Date: Sunday, Jul 16, 2006 10:42 am
Subject: Re: APEX and Debian
Thanks a lot for nslu2-utils. I think that most users prefer not to flash
As far as we know, that's only happened once in the two year development period
of the nslu2-linux project (it was a bug I introduced in a very early version
of the slugimage tool).
-- Rod Whitby
-- NSLU2-Linux Project Lead
-Original Message-
From: Riku Voipio [EMAIL PROTECTED]
Date
for vendor binary
compatibility).
-- Rod Whitby
-- NSLU2-Linux Project Lead
-Original Message-
From: Marc Singer [EMAIL PROTECTED]
Date: Monday, Jul 17, 2006 3:28 am
Subject: Re: APEX and Debian
I don't believe there is a bonafide risk of over-erasing the NOR flash. And
with an initramfs enabled
Now that the (unofficial) project to produce an armeb port has been
announced on debian-devel [1], the group of people working on the
port[2] are looking for somewhere to discuss development. We could
easily set up our own mailing lists at debonaras.org or
nslu2-linux.org (the first, but not
90 matches
Mail list logo
