Re: [ARMedslack] IPv6 Default behaviour

[Geoff Walton]

Microsoft does do this with Windows, if you don't disable ipv6.  Its part
of the spec.


On Thu, Jun 27, 2013 at 6:08 AM, Ottavio Caruso <
ottavio2006-usenet2...@yahoo.com> wrote:

> On 27 June 2013 01:34,   wrote:
> > Has anyone got any idea about how to trun of the default behaviour of
> having
> > every interface automatically assigned an IPv6 address when it comes up?
>
> Never tried it myself but have you tried adding "ipv6.disable=1" as
> kernel command line parameter?
>
>
>
>
> --
> Ottavio
> ___
> ARMedslack mailing list
> ARMedslack@lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: [ARMedslack] GuruPlug Wireless?

[Geoff Walton]

I had to 'borrow' to firmware files from the debian install that ships on
the device in order to get AP mode to work.  I never attempted to get it to
run as a client.  You can download the file system image from
plugcomputer.org and exact them.  I have good luck in general with the
2.6.33.5-kirkwood kernel from the 13.1 ArmedSlack distribution, after
struggling with the wireless on the later kernels; even though I am using
most of the other packages for a snapshot of current shortly before the
release of 13.37 and a few later application layer ones with security
updates.

I can send the firmware images if you need and get them out the Debian
image (not entirely sure of the license); but I would try the
2.6.33.5-kirkwood kernel image from 13.1 to get your wireless going.

It seems like a number of people had wireless

On Mon, Feb 20, 2012 at 1:49 PM, David Madden wrote:

> Hi, I've been working on customizing a GuruPlug to do some specific tasks
> on my home network.  I've tried installing Slackware & Debian (both
> successful) but I haven't been able to build a functional kernel or get
> wireless running.  So, I wonder:
>
> * How much of a hassle is it to get from a vanilla kernel tree to a
> bootable uImage?  (I've gotten clean compiles using the config from
> /boot/config-whatever, but it hangs on boot after "Uncompressing Linux...
> done, booting the kernel.")
>
> * Are the Marvell wireless drivers & tools integrated into the kernel /
> distro, or is it still an "add external software" project?
>
> (I'm fiddling with this in the first place, rather than going with a full
> Slackware or Debian install, because I'd like to put together a minimal
> system that fits in the 512MB NAND Flash, so my USB disk can be all data.)
>
> Thanks!
> __**_
> ARMedslack mailing list
> ARMedslack@lists.armedslack.**org 
> http://lists.armedslack.org/**mailman/listinfo/armedslack
>
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

[ARMedslack] Open Pandora

[Geoff Walton]

Has anyone tried to do armedslack on the Open Pandora handheld?

It looks like a pretty fun toy but I would want Slackware on it. 
http://www.openpandora.org/




smime.p7s
Description: S/MIME Cryptographic Signature
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: [ARMedslack] dockstar /etc/mtab inconsistent with /proc/mounts on current

[Geoff Walton]

Unless you have done something like got /etc on a different volume than /
which creates its own problems then you obviously can't write to / etc.  I
have done slackware86 on nfs before with a readonly rootfs and I did have
the same problem.  I soved it by creating a link just the same way you did.
I don't think there are any issues with it.  I am surpriesed you did not
encounter this on the x86 distribution, but I was working with Slackware
11.0 at the so maybe something has changed.

On Mon, Mar 28, 2011 at 1:06 PM, Davide  wrote:

>   Hi.
> While fiddling with rc.S to have / in RO I noticed that /etc/mtab is
> inconsistent with the content of /proc/mounts.
> I replaced /etc/mtab with a link to /proc/mounts and things seem to be ok
> again ... not 100% sure that it's ok to leave it this way.
> Anyone else spotted the same thing ?
> I can report that this does not happen on my x86 slackware current.
>
> Regards
> David
>
> ___
> ARMedslack mailing list
> ARMedslack@lists.armedslack.org
> http://lists.armedslack.org/mailman/listinfo/armedslack
>
>
___
ARMedslack mailing list
ARMedslack@lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack