* [Johan Breeven]
Second one flashed the installer, logged in as installer
through SSH. As soon as I plug in an USB stick (I tried several, formatted
NTFS and EXT3) in port 1 or port 2, the NSLU stops reacting to keypresses,
So you boot the installer, connect with SSH, and only then connect
* [heffa niceday]
It works with or without .local.
Just to clarify. The above is true for Mac OS X.
Should be true for GNU/Linux, too, if you put search local in
/etc/resolv.conf. I'm pretty far off topic for this list and more
towards debian-users by now, though :)
Øystein
--
Nobody
* [heffa niceday]
And when trying to connect via SSH:
ssh: Could not resolve hostname HOSTNAME.local: nodename nor servname
provided, or not known
Try installing avahi-daemon, avahi-utils, and libnss-mdns. First
package should let other hosts discover the slug, third one should let
the slug
* [Martin Michlmayr]
They relaxed their policies a bit, which is why we have the microcode
in non-free now. I don't have any IXP contacts at Intel, so I cannot
ask whether they could completely open source it.
Does redistributable microcode mean we might see official nslu2 install
images
* [Charles de Miramon]
I'm trying to transform a nslu2 in a debian/rsync backup of my workstation.
Hi,
(Not directly an answer to your question or even relevant to this list,
but seems very close to what you want).
I tried using rsync to backup my home directory, too, but quickly gave
it up
* [Martin Michlmayr]
debian-installer is still based on 2.6.22, but maybe it's 2.6.24
because you're using armel.
The installer ran on 2.6.22, but it installed 2.6.24.
Looks like 2.6.24-3 is out on the mirrors now, so the ethernet module
will probably Just Work in the future. :)
Øystein
--
* [Rod Whitby]
See the last two sections on this page:
http://www.nslu2-linux.org/wiki/Debian/BuildImage
for how to do this.
Using a slightly modified version of the script on this page and the
2008-02-09 build of the armel installer[1], I was able to successfully
install Debian Unstable
Hi,
I recently got a new slug for playing with armel.
For installing, I first tried the experimental unstable unsupported
alpha release from slug-firmware.net, but it seems the sid tree has
changed a bit too much since this was created (in july, I think), so it
didn't work for me. Next, I
* [Adam C Powell IV]
Greetings,
mpich has not been building on ARM for the past month or so, stopping at
the C++ static-shared lib linking moment:
[...]
Any ideas on what might be different on ARM such that this is failing?
Broken autobuilder chroot?
I tried (roughly) the following
* [Adam C Powell IV]
Sounds like a problem autobuilder. But then, there are multiple ARM
autobuilders, right? What's the probability that three separate builds
would fail within the last month under these conditions? Are all of the
autobuilders deficient, or did mpich happen to hit the
* [Aurelien Jarno]
It does build correctly on a machine with more RAM (512 MB), so the
problem is very probably due to limited RAM and swap on the build
daemon.
You should ask to requeue quantlib on another build daemon.
I notice this problem seems to crop up a lot. Could the situation
* [David Fokkema]
of user time whereas on my NSLU2 (ARM 266 Mhz) it uses 23.57 s of user
time. That is to be expected, of course. Oh, I forgot, it also uses
8m29.430 s of system time. Adding up to a real time of 9m! Why is that?
Isn't resizing pictures most likely a floating point heavy
12 matches
Mail list logo
