Hello all,

We would like to cleanup asterisk packages in the feeds.
We will start by removing asterisk 1.2:
  - asterisk
  - asterisk-sounds (obsolete by asterisk14 sound packages)

Is there anyone still using asterisk 1.4 or 1.6?
  - asterisk14
  - asterisk14-chan-capi
  - asterisk16
  - asterisk16-addons
We would like to remove the above versions if not used anymore.

The officially maintained versions are asterisk 1.8 and asterisk 10:
  - asterisk-gui
  - asterisk14-core-sounds*
  - asterisk14-extra-sounds*
  - asterisk14-moh*
  - asterisk18
  - asterisk10


Regards,
Ovidiu Sas

Hi again guys.

Guess I didn't learn after the first time.
After screwing up my rcS file, I was able to correct it and regain access to ssh
and to my series 4 pogoplug again.
I then followed directions off of
http://www.nslu2-linux.org/wiki/Main/PlugComputers and found I was running
busybox 1.16.
According to this instructions, I needed to set up my series 4 like a pro
device.
I again edited my rcS file, putting the "mount /dev/sda1 /opt" and continued
with the config stuff.
On reboot, I didn't get anything except flashing green lights.
I figured, no biggie, was prepared to wire up to the jtag and try to recover. I
used a 485 converter box to talk to it and got the boot sequence showing up, but
no access. Since I had only held the wires on the points, I thought I would get
a better result soldering to it.
After soldering to the points, I booted up and no more flashing green light, and
no real communication showed up in my terminal. The Ethernet tx and rx lights
are barely glowing, and not sure what happened.
Nothing appears shorted out, and the two resistors on the jtag rx and tx are
still intact.
Any ideas?
If I cleared out or corrupted the NAND, can I set up a tftp to flash it back
somehow?
Hoping that someone has some ideas.
Thanks again,
Shannon

Putting in the mount command in the rcS does not break anything.  You could have
just placed the mount script at the end of rcS like the readme file where you
got your "mount_optext" script.  Did you verify the mount /dev/sda1 to /opt by
typing "mount" to verify the usb drive mounted like the directions mentioned?

Did you take out the invocation to the mount_optext that you had, if you didn't,
the flashing green light (only one in front) would have kept flashing since it
wouldn't load the mypogoplug.com service (db and hbmgr.sh) for another hour. 
That's what keeps the green light flashing.

You have a jtag?  Pretty drastic.  That was probably beyond the scope of that
archlinuxarm page.  Just a serial connection - ca-42 - usb to 3.3V ttl.  After
the boot sequence, it should show the prompt.  Did you hit enter/return to see
if you could get the prompt?  Did you take anti-static precautions?  Did you use
a low wattage iron?  The pads are near the power plug.  If you have a jtag and
soldering iron you should be experienced with this.  You can check with the
archlinuxarm guys or http://forum.doozan.com/ and see if anybody there has any
ideas, at least if they have a nand image.

--- In nslu2-general@yahoogroups.com, "al"  wrote:
>
> Hi again guys.
>
> Guess I didn't learn after the first time.
> After screwing up my rcS file, I was able to correct it and regain access to
ssh and to my series 4 pogoplug again.
> I then followed directions off of
http://www.nslu2-linux.org/wiki/Main/PlugComputers and found I was running
busybox 1.16.
> According to this instructions, I needed to set up my series 4 like a pro
device.
> I again edited my rcS file, putting the "mount /dev/sda1 /opt" and continued
with the config stuff.
> On reboot, I didn't get anything except flashing green lights.
> I figured, no biggie, was prepared to wire up to the jtag and try to recover.
I used a 485 converter box to talk to it and got the boot sequence showing up,
but no access. Since I had only held the wires on the points, I thought I would
get a better result soldering to it.
> After soldering to the points, I booted up and no more flashing green light,
and no real communication showed up in my terminal. The Ethernet tx and rx
lights are barely glowing, and not sure what happened.
> Nothing appears shorted out, and the two resistors on the jtag rx and tx are
still intact.
> Any ideas?
> If I cleared out or corrupted the NAND, can I set up a tftp to flash it back
somehow?
> Hoping that someone has some ideas.
> Thanks again,
> Shannon
>

I may have jumped the gun a little when I posted earlier. You're right on
several things.
I didn't have a jtag. It's been a few years since I've had to do some
programming like that. My experience with that is limited to saving old wrt54g
routers and old Xbox eeproms. I used the serial connection on the pogo board.
I also did not comment out the other mount command. I was working from my iPhone
with a ssh app that allowed me to use vi so after a little while of the tedious
process of trying to make sure the script was right, I may have overlooked that.
Hindsight shows now that I put myself right back into the same state I was to
begin with the other day with my series of posts.
I have to admit, I didn't use proper static precautions. I think I was getting
ahead o myself. I believe I just got ahead of myself there.

With the soldering, it wasn't that bad. The pads were more accessible than some
of the Xbox stuff I've worked on, so I wasn't too concerned. I maintained heat
awareness and didn't leave the iron there too long. I believe it's a 25 w iron,
I'm sure 15 might have been a better choice.

All in all, I think I may just set it up on the shelf if I cant find anything
right now. I finished school a few weeks ago, and I kinda just dove into a
project with about a weeks worth of research on it.

In response to your question regarding the prompt, I never got one. After the
boot info showed up, about 8 or 9 lines of CE/ repeated showed on the screen,
but wouldn't let me do anything. I did press buttons on the keyboard, but didn't
see anything show up.

I'll post I I find anything more and thanks for the tips for the two other
sites. I'll check them out.

Thanks again.

Shannon


--- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
>
> Putting in the mount command in the rcS does not break anything.  You could
have just placed the mount script at the end of rcS like the readme file where
you got your "mount_optext" script.  Did you verify the mount /dev/sda1 to /opt
by typing "mount" to verify the usb drive mounted like the directions mentioned?
>
> Did you take out the invocation to the mount_optext that you had, if you
didn't, the flashing green light (only one in front) would have kept flashing
since it wouldn't load the mypogoplug.com service (db and hbmgr.sh) for another
hour.  That's what keeps the green light flashing.
>
> You have a jtag?  Pretty drastic.  That was probably beyond the scope of that
archlinuxarm page.  Just a serial connection - ca-42 - usb to 3.3V ttl.  After
the boot sequence, it should show the prompt.  Did you hit enter/return to see
if you could get the prompt?  Did you take anti-static precautions?  Did you use
a low wattage iron?  The pads are near the power plug.  If you have a jtag and
soldering iron you should be experienced with this.  You can check with the
archlinuxarm guys or http://forum.doozan.com/ and see if anybody there has any
ideas, at least if they have a nand image.
>
> --- In nslu2-general@yahoogroups.com, "al"  wrote:
> >
> > Hi again guys.
> >
> > Guess I didn't learn after the first time.
> > After screwing up my rcS file, I was able to correct it and regain access to
ssh and to my series 4 pogoplug again.
> > I then followed directions off of
http://www.nslu2-linux.org/wiki/Main/PlugComputers and found I was running
busybox 1.16.
> > According to this instructions, I needed to set up my series 4 like a pro
device.
> > I again edited my rcS file, putting the "mount /dev/sda1 /opt" and continued
with the config stuff.
> > On reboot, I didn't get anything except flashing green lights.
> > I figured, no biggie, was prepared to wire up to the jtag and try to
recover. I used a 485 converter box to talk to it and got the boot sequence
showing up, but no access. Since I had only held the wires on the points, I
thought I would get a better result soldering to it.
> > After soldering to the points, I booted up and no more flashing green light,
and no real communication showed up in my terminal. The Ethernet tx and rx
lights are barely glowing, and not sure what happened.
> > Nothing appears shorted out, and the two resistors on the jtag rx and tx are
still intact.
> > Any ideas?
> > If I cleared out or corrupted the NAND, can I set up a tftp to flash it back
somehow?
> > Hoping that someone has some ideas.
> > Thanks again,
> > Shannon
> >
>

hi all, sorry if this is a noob question but i've been trying to flash openwrt
to a NSLU2 for the last couple of days and it's starting to feel like i'm
bashing my head on a wall ;)

i think i managed to flash the openwrt firmware correctly (i'm using 10.3.1)
with upslug2 but i can't connect to the device:

i tried both connecting the NSLU2 to a switch and directly to my computer.
when i try to telnet (or ping) the device on 192.168.1.1 or 192.168.1.77 it
doesn't respond and when i connect it to the switch it doesn't show up on the
DHCP table.
when i boot the NSLU2 it flashes all the leds and then shows only the ethernet
led.

any help would be REALLY appreciated!
Thanks in advance!
Marcello

Hi all, back with a new challenge (for me at least). Have been running a number
of programs without any real problems, Transmission, Samba2, Vsftpd. But now and
then when i need to use the original Pogoplug software that came on my plug it
takes forever to respond (if at all).  I came to the conclusion (after finding
it more responsive after a reboot) that its probably struggling with memory
loss. Can anyone tell me if there is a work around, virtual memory or something
like to help out. Thanks in advance for any help offered.

The things you mentioned below for your version of OpenWRT actually sound
correct.  Make sure you have read
http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the section
Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03) and
http://wiki.openwrt.org/toh/linksys/nslu2 .  The default installation of 10.03
(unless things have changed in a year, ok,maybe 2) is a static ip setup on
192.168.1.1.  It will not show up on your dhcp table because it is static.  You
have to make sure you are on the same subnet as your slug. So make the ip
address of you computer something like 192.168.1.254 temporarily until you
change the slug network setup.  The LED setup that you see,10.03 has most of the
lights turned off (except for Ethernet), is the default and you have to program
what you want those LEDs to do.  See the bottom of the above pages.  You can
setup the stuff with Luci or the setup files.

--- In nslu2-general@yahoogroups.com, "Marcello"  wrote:
>
> hi all, sorry if this is a noob question but i've been trying to flash openwrt
to a NSLU2 for the last couple of days and it's starting to feel like i'm
bashing my head on a wall ;)
>
> i think i managed to flash the openwrt firmware correctly (i'm using 10.3.1)
with upslug2 but i can't connect to the device:
>
> i tried both connecting the NSLU2 to a switch and directly to my computer.
> when i try to telnet (or ping) the device on 192.168.1.1 or 192.168.1.77 it
doesn't respond and when i connect it to the switch it doesn't show up on the
DHCP table.
> when i boot the NSLU2 it flashes all the leds and then shows only the ethernet
led.
>
> any help would be REALLY appreciated!
> Thanks in advance!
> Marcello
>

Depends on your type of Pogoplug.  The V1 and V2s had a fair amount of memory
and shouldn't be hurting.  The mypogoplug.com service itself may be having
problems after being idle for a while (you can kill and restart the service
"/etc/init.d/hbmgr.sh restart").  First, check "ps", check memory use with
"free", then check "top" (ipkg install procps if you don't have it, or atop, or
htop).  Finally read
http://www.nslu2-linux.org/wiki/SlugOS/InstallandTurnupABasicSlugOSSystem .  I
know it is for a SlugOS NSLU2 system, but mwester did a nice writeup of "Adding
a swapfile" and an arm/linux is an arm/linux ...., although you probably don't
need one (DONT do this in your nand space if you decide to implement one, only
should be done on external drive).  This will probably not speed up anything and
may cause things to run slower.  Again do this at your own risk.

--- In nslu2-general@yahoogroups.com, "stigslims"  wrote:
>
> Hi all, back with a new challenge (for me at least). Have been running a
number of programs without any real problems, Transmission, Samba2, Vsftpd. But
now and then when i need to use the original Pogoplug software that came on my
plug it takes forever to respond (if at all).  I came to the conclusion (after
finding it more responsive after a reboot) that its probably struggling with
memory loss. Can anyone tell me if there is a work around, virtual memory or
something like to help out. Thanks in advance for any help offered.
>

Judging by the cautious warning and the small gain from effort involved, i think
its easier to deal with it shortcomings as they arise rather than potentially
cause more harm than good
(after all i am what would be described as a novice). Thanks for the help none
the less, but rest assured i will be back at some point on a search for info.

-- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
>
>
>
> Depends on your type of Pogoplug.  The V1 and V2s had a fair amount of memory
and shouldn't be hurting.  The mypogoplug.com service itself may be having
problems after being idle for a while (you can kill and restart the service
"/etc/init.d/hbmgr.sh restart").  First, check "ps", check memory use with
"free", then check "top" (ipkg install procps if you don't have it, or atop, or
htop).  Finally read
http://www.nslu2-linux.org/wiki/SlugOS/InstallandTurnupABasicSlugOSSystem .  I
know it is for a SlugOS NSLU2 system, but mwester did a nice writeup of "Adding
a swapfile" and an arm/linux is an arm/linux ...., although you probably don't
need one (DONT do this in your nand space if you decide to implement one, only
should be done on external drive).  This will probably not speed up anything and
may cause things to run slower.  Again do this at your own risk.
>
> --- In nslu2-general@yahoogroups.com, "stigslims"  wrote:
> >
> > Hi all, back with a new challenge (for me at least). Have been running a
number of programs without any real problems, Transmission, Samba2, Vsftpd. But
now and then when i need to use the original Pogoplug software that came on my
plug it takes forever to respond (if at all).  I came to the conclusion (after
finding it more responsive after a reboot) that its probably struggling with
memory loss. Can anyone tell me if there is a work around, virtual memory or
something like to help out. Thanks in advance for any help offered.
> >
>

Hello,
Can someone help me out?  I am trying to build the latest kernel (3.7.2) on my
NSLU2 that is on Debian.  The reason is so I can enable and build the EM28xx USB
video capture modules.The build starts out but winds up with file not found
errors looking up the file(s) in Google result with a bunch of people saying I
need toolchain...  Do I really need the toolchain when building for the same
processor?arm-linux-gnueabi-objdump
Ah I see Debian issues go to a new list now.   Sorry for the spam.
I'm willing to donate if someone does it for me.  I've wasted days on this
reading many outdated howto's and helpguides.
Using build command - foobar:/usr/src/linux-3.7.2# fakeroot make-kpkg --initrd
--revision=1.custom.1.0 kernel_image kernel_headers
build buiild
/bin/sh: arm-linux-gnueabi-objdump: not found  CHK    
include/generated/compile.h  UPD     include/generated/compile.h  CC     
init/version.o/bin/sh: arm-linux-gnueabi-objdump: not found  CC     
init/do_mounts.o/bin/sh: arm-linux-gnueabi-objdump: not found  CC     
init/do_mounts_initrd.o/bin/sh: arm-linux-gnueabi-objdump: not found  LD     
init/mounts.o/bin/sh: arm-linux-gnueabi-ld: not foundmake[2]: ***
[init/mounts.o] Error 127make[1]: *** [init] Error 2make[1]: Leaving directory
`/usr/src/linux-3.7.2'make: *** [debian/stamp/build/kernel] Error
2foobar:/usr/src/linux-3.7.2#
Thanks!


[Non-text portions of this message have been removed]

Yeah, you will still need a tool chain to build anything. This is in Linux
in general, can't build without some basic things. ;)
On Jan 17, 2013 9:04 PM, "Dane Ruyle" <dane_ruyle@...> wrote:

> **
>
>
>
>
> Hello,
> Can someone help me out? I am trying to build the latest kernel (3.7.2) on
> my NSLU2 that is on Debian. The reason is so I can enable and build the
> EM28xx USB video capture modules.The build starts out but winds up with
> file not found errors looking up the file(s) in Google result with a bunch
> of people saying I need toolchain... Do I really need the toolchain when
> building for the same processor?arm-linux-gnueabi-objdump
> Ah I see Debian issues go to a new list now. Sorry for the spam.
> I'm willing to donate if someone does it for me. I've wasted days on this
> reading many outdated howto's and helpguides.
> Using build command - foobar:/usr/src/linux-3.7.2# fakeroot make-kpkg
> --initrd --revision=1.custom.1.0 kernel_image kernel_headers
> build buiild
> /bin/sh: arm-linux-gnueabi-objdump: not found CHK
> include/generated/compile.h UPD include/generated/compile.h CC
> init/version.o/bin/sh: arm-linux-gnueabi-objdump: not found CC
> init/do_mounts.o/bin/sh: arm-linux-gnueabi-objdump: not found CC
> init/do_mounts_initrd.o/bin/sh: arm-linux-gnueabi-objdump: not found LD
> init/mounts.o/bin/sh: arm-linux-gnueabi-ld: not foundmake[2]: ***
> [init/mounts.o] Error 127make[1]: *** [init] Error 2make[1]: Leaving
> directory `/usr/src/linux-3.7.2'make: *** [debian/stamp/build/kernel] Error
> 2foobar:/usr/src/linux-3.7.2#
> Thanks!
>
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]

Hi,
Has anyone tried building the (latest) 3.2.7 kernel for the NSLU2?
Maybe I am doing something wrong.  The build starts but eventually errors out
with file not found errors.  It looks like I need a toolchain.  Is this really
necessary if I am building for the same processor?

What is the latest version people have built?

I am looking to enable EM28xx video capture device.

thanks!

Any suggestions on where or how to build the toolchain? I see three options on
the website and went with crosstool but haven't gotten past the homepage.

To: nslu2-general@yahoogroups.com
From: htwiz2002@...
Date: Thu, 17 Jan 2013 21:11:16 -0700
Subject: Re: [nslu2-general] RE: Help building Debian Kernel


























       Yeah, you will still need a tool chain to build anything. This is in Linux

in general, can't build without some basic things. ;)

On Jan 17, 2013 9:04 PM, "Dane Ruyle" dane_ruyle@...> wrote:



> **

>

>

>

>

> Hello,

> Can someone help me out? I am trying to build the latest kernel (3.7.2) on

> my NSLU2 that is on Debian. The reason is so I can enable and build the

> EM28xx USB video capture modules.The build starts out but winds up with

> file not found errors looking up the file(s) in Google result with a bunch

> of people saying I need toolchain... Do I really need the toolchain when

> building for the same processor?arm-linux-gnueabi-objdump

> Ah I see Debian issues go to a new list now. Sorry for the spam.

> I'm willing to donate if someone does it for me. I've wasted days on this

> reading many outdated howto's and helpguides.

> Using build command - foobar:/usr/src/linux-3.7.2# fakeroot make-kpkg

> --initrd --revision=1.custom.1.0 kernel_image kernel_headers

> build buiild

> /bin/sh: arm-linux-gnueabi-objdump: not found CHK

> include/generated/compile.h UPD include/generated/compile.h CC

> init/version.o/bin/sh: arm-linux-gnueabi-objdump: not found CC

> init/do_mounts.o/bin/sh: arm-linux-gnueabi-objdump: not found CC

> init/do_mounts_initrd.o/bin/sh: arm-linux-gnueabi-objdump: not found LD

> init/mounts.o/bin/sh: arm-linux-gnueabi-ld: not foundmake[2]: ***

> [init/mounts.o] Error 127make[1]: *** [init] Error 2make[1]: Leaving

> directory `/usr/src/linux-3.7.2'make: *** [debian/stamp/build/kernel] Error

> 2foobar:/usr/src/linux-3.7.2#

> Thanks!

>

>

> [Non-text portions of this message have been removed]

>

>

>



[Non-text portions of this message have been removed]


















[Non-text portions of this message have been removed]

Hi

I am having trouble starting NFS server on my Pogoplug. I get the following
error messages when I enter /opt/etc/init.d/S56nfsd:

/opt/sbin/rpc.nfsd: error while loading shared libraries: libnsl.so.1: cannot
open shared object file: No such file or directory
/opt/sbin/rpc.mountd: error while loading shared libraries: libnsl.so.1: cannot
open shared object file: No such file or directory

I have installed the package nfs-server. The file libnsl.so.1 is located in
/opt/lib:

-rwxrwxrwx    1 root     root         98394 Feb 14  2012 libnsl-2.5.so
lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so.1 ->
libnsl-2.5.so
lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so ->
libnsl-2.5.so

Root's PATH is as follows:
PATH=/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/lib:/usr/local/lib

Do I need to set LD_LIBRARY_PATH for this to work?

Any help much appreciated. By the way I am not an expert in Linux but I am
familiar with some of the basics.

Thanks
Dara

Yes, you need it.  Also make sure you run portmap.  See
http://openpogo.tumblr.com/ .  It shows you what you need to know.

--- In nslu2-general@yahoogroups.com, "dara_mullally"  wrote:
>
> Hi
>
> I am having trouble starting NFS server on my Pogoplug. I get the following
error messages when I enter /opt/etc/init.d/S56nfsd:
>
> /opt/sbin/rpc.nfsd: error while loading shared libraries: libnsl.so.1: cannot
open shared object file: No such file or directory
> /opt/sbin/rpc.mountd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
>
> I have installed the package nfs-server. The file libnsl.so.1 is located in
/opt/lib:
>
> -rwxrwxrwx    1 root     root         98394 Feb 14  2012 libnsl-2.5.so
> lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so.1 ->
libnsl-2.5.so
> lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so ->
libnsl-2.5.so
>
> Root's PATH is as follows:
PATH=/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/lib:/usr/local/lib
>
> Do I need to set LD_LIBRARY_PATH for this to work?
>
> Any help much appreciated. By the way I am not an expert in Linux but I am
familiar with some of the basics.
>
> Thanks
> Dara
>

Thanks, I will give that a go. I thought I read somewhere that ld_library_path
was not needed for optware.

--- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
>
> Yes, you need it.  Also make sure you run portmap.  See
http://openpogo.tumblr.com/ .  It shows you what you need to know.
>
> --- In nslu2-general@yahoogroups.com, "dara_mullally"  wrote:
> >
> > Hi
> >
> > I am having trouble starting NFS server on my Pogoplug. I get the following
error messages when I enter /opt/etc/init.d/S56nfsd:
> >
> > /opt/sbin/rpc.nfsd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
> > /opt/sbin/rpc.mountd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
> >
> > I have installed the package nfs-server. The file libnsl.so.1 is located in
/opt/lib:
> >
> > -rwxrwxrwx    1 root     root         98394 Feb 14  2012 libnsl-2.5.so
> > lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so.1 ->
libnsl-2.5.so
> > lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so ->
libnsl-2.5.so
> >
> > Root's PATH is as follows:
PATH=/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/lib:/usr/local/lib
> >
> > Do I need to set LD_LIBRARY_PATH for this to work?
> >
> > Any help much appreciated. By the way I am not an expert in Linux but I am
familiar with some of the basics.
> >
> > Thanks
> > Dara
> >
>

Depends on how the package was built.  If it takes into account /opt/lib.  You
can always put a symbolic link in /usr/lib to the one in /opt/lib.

--- In nslu2-general@yahoogroups.com, "dara_mullally"  wrote:
>
>
> Thanks, I will give that a go. I thought I read somewhere that ld_library_path
was not needed for optware.
>
> --- In nslu2-general@yahoogroups.com, "oddballhero"  wrote:
> >
> > Yes, you need it.  Also make sure you run portmap.  See
http://openpogo.tumblr.com/ .  It shows you what you need to know.
> >
> > --- In nslu2-general@yahoogroups.com, "dara_mullally"  wrote:
> > >
> > > Hi
> > >
> > > I am having trouble starting NFS server on my Pogoplug. I get the
following error messages when I enter /opt/etc/init.d/S56nfsd:
> > >
> > > /opt/sbin/rpc.nfsd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
> > > /opt/sbin/rpc.mountd: error while loading shared libraries: libnsl.so.1:
cannot open shared object file: No such file or directory
> > >
> > > I have installed the package nfs-server. The file libnsl.so.1 is located
in /opt/lib:
> > >
> > > -rwxrwxrwx    1 root     root         98394 Feb 14  2012 libnsl-2.5.so
> > > lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so.1 ->
libnsl-2.5.so
> > > lrwxrwxrwx    1 root     root            13 Jan 18 19:08 libnsl.so ->
libnsl-2.5.so
> > >
> > > Root's PATH is as follows:
PATH=/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/opt/lib:/usr/local/lib
> > >
> > > Do I need to set LD_LIBRARY_PATH for this to work?
> > >
> > > Any help much appreciated. By the way I am not an expert in Linux but I am
familiar with some of the basics.
> > >
> > > Thanks
> > > Dara
> > >
> >
>

i tried everything that came to my mind about the ip configuration (with
switch, connecting directly to the NSLU2, with dhcp and without), i tried
pinging 192.168.1.255 and doing arp -a, i downloaded a couple of ip
scanners but both weren't able to find the NSLU2 online.

the device correctly shows up when started in recovery mode but disappears
after the firmware flash...


On Tue, Jan 15, 2013 at 12:55 PM, echo mirage <echomrg@...> wrote:

> I already checked the pages you linked (i knew about the dark leds) but,
> unfortunately, most of the help is about post-flash configurations. the
> only real doubt i have is that i'm using a debian inside a virtualbox on a
> mac to connect and maybe that messed up with my network configuration (but
> upslug worked nicely), i'll double check that before trying to build my own
> image for openwrt with a different default IP.
>
> Thanks for the help!
>
>
> On Tue, Jan 15, 2013 at 12:40 PM, oddballhero <oddballhero@...>wrote:
>
>> The things you mentioned below for your version of OpenWRT actually sound
>> correct.  Make sure you have read
>> http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the section
>> Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03)
>> and http://wiki.openwrt.org/toh/linksys/nslu2 .  The default
>> installation of 10.03 (unless things have changed in a year, ok,maybe 2) is
>> a static ip setup on 192.168.1.1.  It will not show up on your dhcp table
>> because it is static.  You have to make sure you are on the same subnet as
>> your slug. So make the ip address of you computer something like
>> 192.168.1.254 temporarily until you change the slug network setup.  The LED
>> setup that you see,10.03 has most of the lights turned off (except for
>> Ethernet), is the default and you have to program what you want those LEDs
>> to do.  See the bottom of the above pages.  You can setup the stuff with
>> Luci or the setup files.
>>
>> --- In nslu2-general@yahoogroups.com, "Marcello"  wrote:
>> >
>> > hi all, sorry if this is a noob question but i've been trying to flash
>> openwrt to a NSLU2 for the last couple of days and it's starting to feel
>> like i'm bashing my head on a wall ;)
>> >
>> > i think i managed to flash the openwrt firmware correctly (i'm using
>> 10.3.1) with upslug2 but i can't connect to the device:
>> >
>> > i tried both connecting the NSLU2 to a switch and directly to my
>> computer.
>> > when i try to telnet (or ping) the device on 192.168.1.1 or
>> 192.168.1.77 it doesn't respond and when i connect it to the switch it
>> doesn't show up on the DHCP table.
>> > when i boot the NSLU2 it flashes all the leds and then shows only the
>> ethernet led.
>> >
>> > any help would be REALLY appreciated!
>> > Thanks in advance!
>> > Marcello
>> >
>>
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>
>
> --
> Cordiali saluti e ossequi
> - Marcello -
> _______________________________________________________________________
>
>            Numquam ponenda est pluralitas sine necessitate
> _______________________________________________________________________
>



--
Cordiali saluti e ossequi
- Marcello -
_______________________________________________________________________

            Numquam ponenda est pluralitas sine necessitate
_______________________________________________________________________


[Non-text portions of this message have been removed]

Connect the NSLU to a computer that has a static IP configured (do not
connect the NSLU to your network, use a direct ethernet cable between
your PC/laptop and NSLU).
Run ethereal on the specific interface and boot up the NSLU.
Inspect all IP packets and try to figure out the IP of the NSLU.

Regards,
Ovidiu Sas

On Sat, Jan 19, 2013 at 5:30 AM, echo mirage <echomrg@...> wrote:
>
>
>
> i tried everything that came to my mind about the ip configuration (with
> switch, connecting directly to the NSLU2, with dhcp and without), i tried
> pinging 192.168.1.255 and doing arp -a, i downloaded a couple of ip
> scanners but both weren't able to find the NSLU2 online.
>
> the device correctly shows up when started in recovery mode but disappears
> after the firmware flash...
>
> On Tue, Jan 15, 2013 at 12:55 PM, echo mirage echomrg@...> wrote:
>
> > I already checked the pages you linked (i knew about the dark leds) but,
> > unfortunately, most of the help is about post-flash configurations. the
> > only real doubt i have is that i'm using a debian inside a virtualbox on a
> > mac to connect and maybe that messed up with my network configuration (but
> > upslug worked nicely), i'll double check that before trying to build my own
> > image for openwrt with a different default IP.
> >
> > Thanks for the help!
> >
> >
> > On Tue, Jan 15, 2013 at 12:40 PM, oddballhero oddballhero@...>wrote:
>
>
> >
> >> The things you mentioned below for your version of OpenWRT actually sound
> >> correct. Make sure you have read
> >> http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the section
> >> Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03)
> >> and http://wiki.openwrt.org/toh/linksys/nslu2 . The default
> >> installation of 10.03 (unless things have changed in a year, ok,maybe 2) is
> >> a static ip setup on 192.168.1.1. It will not show up on your dhcp table
> >> because it is static. You have to make sure you are on the same subnet as
> >> your slug. So make the ip address of you computer something like
> >> 192.168.1.254 temporarily until you change the slug network setup. The LED
> >> setup that you see,10.03 has most of the lights turned off (except for
> >> Ethernet), is the default and you have to program what you want those LEDs
> >> to do. See the bottom of the above pages. You can setup the stuff with
> >> Luci or the setup files.
> >>
> >> --- In nslu2-general@yahoogroups.com, "Marcello" wrote:
> >> >
> >> > hi all, sorry if this is a noob question but i've been trying to flash
> >> openwrt to a NSLU2 for the last couple of days and it's starting to feel
> >> like i'm bashing my head on a wall ;)
> >> >
> >> > i think i managed to flash the openwrt firmware correctly (i'm using
> >> 10.3.1) with upslug2 but i can't connect to the device:
> >> >
> >> > i tried both connecting the NSLU2 to a switch and directly to my
> >> computer.
> >> > when i try to telnet (or ping) the device on 192.168.1.1 or
> >> 192.168.1.77 it doesn't respond and when i connect it to the switch it
> >> doesn't show up on the DHCP table.
> >> > when i boot the NSLU2 it flashes all the leds and then shows only the
> >> ethernet led.
> >> >
> >> > any help would be REALLY appreciated!
> >> > Thanks in advance!
> >> > Marcello

Indeed, a google search may help, check out these finds:

http://lists.debian.org/debian-arm/2006/11/msg00045.html
http://old.nabble.com/Cross-compile-toolchain-td30091841.html
http://www.nslu2-linux.org/wiki/Development/MasterMakefile

I'm actually not on Debian myself, but hopefully that should help you
along. ;)


On Fri, Jan 18, 2013 at 2:30 AM, Dane Ruyle <dane_ruyle@...> wrote:

> **
>
>
>
> Any suggestions on where or how to build the toolchain? I see three
> options on the website and went with crosstool but haven't gotten past the
> homepage.
>
> To: nslu2-general@yahoogroups.com
> From: htwiz2002@...
> Date: Thu, 17 Jan 2013 21:11:16 -0700
> Subject: Re: [nslu2-general] RE: Help building Debian Kernel
>
>
> Yeah, you will still need a tool chain to build anything. This is in Linux
>
> in general, can't build without some basic things. ;)
>
> On Jan 17, 2013 9:04 PM, "Dane Ruyle" dane_ruyle@...> wrote:
>
> > **
>
>
> >
>
> >
>
> >
>
> >
>
> > Hello,
>
> > Can someone help me out? I am trying to build the latest kernel (3.7.2)
> on
>
> > my NSLU2 that is on Debian. The reason is so I can enable and build the
>
> > EM28xx USB video capture modules.The build starts out but winds up with
>
> > file not found errors looking up the file(s) in Google result with a
> bunch
>
> > of people saying I need toolchain... Do I really need the toolchain when
>
> > building for the same processor?arm-linux-gnueabi-objdump
>
> > Ah I see Debian issues go to a new list now. Sorry for the spam.
>
> > I'm willing to donate if someone does it for me. I've wasted days on this
>
> > reading many outdated howto's and helpguides.
>
> > Using build command - foobar:/usr/src/linux-3.7.2# fakeroot make-kpkg
>
> > --initrd --revision=1.custom.1.0 kernel_image kernel_headers
>
> > build buiild
>
> > /bin/sh: arm-linux-gnueabi-objdump: not found CHK
>
> > include/generated/compile.h UPD include/generated/compile.h CC
>
> > init/version.o/bin/sh: arm-linux-gnueabi-objdump: not found CC
>
> > init/do_mounts.o/bin/sh: arm-linux-gnueabi-objdump: not found CC
>
> > init/do_mounts_initrd.o/bin/sh: arm-linux-gnueabi-objdump: not found LD
>
> > init/mounts.o/bin/sh: arm-linux-gnueabi-ld: not foundmake[2]: ***
>
> > [init/mounts.o] Error 127make[1]: *** [init] Error 2make[1]: Leaving
>
> > directory `/usr/src/linux-3.7.2'make: *** [debian/stamp/build/kernel]
> Error
>
> > 2foobar:/usr/src/linux-3.7.2#
>
> > Thanks!
>
> >
>
> >
>
> > [Non-text portions of this message have been removed]
>
> >
>
> >
>
> >
>
> [Non-text portions of this message have been removed]
>
>
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]

try192.168.1.77?192.168.1.1?
192.168.1.255 is broadcast  dont use that

To: nslu2-general@yahoogroups.com
From: osas@...
Date: Sat, 19 Jan 2013 11:21:46 -0500
Subject: Re: [nslu2-general] Re: [noob] Problems installing openwrt


























       Connect the NSLU to a computer that has a static IP configured (do not

connect the NSLU to your network, use a direct ethernet cable between

your PC/laptop and NSLU).

Run ethereal on the specific interface and boot up the NSLU.

Inspect all IP packets and try to figure out the IP of the NSLU.



Regards,

Ovidiu Sas



On Sat, Jan 19, 2013 at 5:30 AM, echo mirage echomrg@...> wrote:

>

>

>

> i tried everything that came to my mind about the ip configuration (with

> switch, connecting directly to the NSLU2, with dhcp and without), i tried

> pinging 192.168.1.255 and doing arp -a, i downloaded a couple of ip

> scanners but both weren't able to find the NSLU2 online.

>

> the device correctly shows up when started in recovery mode but disappears

> after the firmware flash...

>

> On Tue, Jan 15, 2013 at 12:55 PM, echo mirage echomrg@...> wrote:

>

> > I already checked the pages you linked (i knew about the dark leds) but,

> > unfortunately, most of the help is about post-flash configurations. the

> > only real doubt i have is that i'm using a debian inside a virtualbox on a

> > mac to connect and maybe that messed up with my network configuration (but

> > upslug worked nicely), i'll double check that before trying to build my own

> > image for openwrt with a different default IP.

> >

> > Thanks for the help!

> >

> >

> > On Tue, Jan 15, 2013 at 12:40 PM, oddballhero oddballhero@...>wrote:

>

>

> >

> >> The things you mentioned below for your version of OpenWRT actually sound

> >> correct. Make sure you have read

> >> http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the section

> >> Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire 10.03)

> >> and http://wiki.openwrt.org/toh/linksys/nslu2 . The default

> >> installation of 10.03 (unless things have changed in a year, ok,maybe 2) is

> >> a static ip setup on 192.168.1.1. It will not show up on your dhcp table

> >> because it is static. You have to make sure you are on the same subnet as

> >> your slug. So make the ip address of you computer something like

> >> 192.168.1.254 temporarily until you change the slug network setup. The LED

> >> setup that you see,10.03 has most of the lights turned off (except for

> >> Ethernet), is the default and you have to program what you want those LEDs

> >> to do. See the bottom of the above pages. You can setup the stuff with

> >> Luci or the setup files.

> >>

> >> --- In nslu2-general@yahoogroups.com, "Marcello" wrote:

> >> >

> >> > hi all, sorry if this is a noob question but i've been trying to flash

> >> openwrt to a NSLU2 for the last couple of days and it's starting to feel

> >> like i'm bashing my head on a wall ;)

> >> >

> >> > i think i managed to flash the openwrt firmware correctly (i'm using

> >> 10.3.1) with upslug2 but i can't connect to the device:

> >> >

> >> > i tried both connecting the NSLU2 to a switch and directly to my

> >> computer.

> >> > when i try to telnet (or ping) the device on 192.168.1.1 or

> >> 192.168.1.77 it doesn't respond and when i connect it to the switch it

> >> doesn't show up on the DHCP table.

> >> > when i boot the NSLU2 it flashes all the leds and then shows only the

> >> ethernet led.

> >> >

> >> > any help would be REALLY appreciated!

> >> > Thanks in advance!

> >> > Marcello
















[Non-text portions of this message have been removed]

i know 255 is for broadcast, i was trying to find out the occupied IPs on
my network.
192.168.1.1/77 doesn't answer, that's my problem ;)


On Sat, Jan 19, 2013 at 5:23 PM, Dane Ruyle <dane_ruyle@...> wrote:

>
> try192.168.1.77?192.168.1.1?
> 192.168.1.255 is broadcast  dont use that
>
> To: nslu2-general@yahoogroups.com
> From: osas@...
> Date: Sat, 19 Jan 2013 11:21:46 -0500
> Subject: Re: [nslu2-general] Re: [noob] Problems installing openwrt
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>       Connect the NSLU to a computer that has a static IP configured (do
> not
>
> connect the NSLU to your network, use a direct ethernet cable between
>
> your PC/laptop and NSLU).
>
> Run ethereal on the specific interface and boot up the NSLU.
>
> Inspect all IP packets and try to figure out the IP of the NSLU.
>
>
>
> Regards,
>
> Ovidiu Sas
>
>
>
> On Sat, Jan 19, 2013 at 5:30 AM, echo mirage echomrg@...> wrote:
>
> >
>
> >
>
> >
>
> > i tried everything that came to my mind about the ip configuration (with
>
> > switch, connecting directly to the NSLU2, with dhcp and without), i tried
>
> > pinging 192.168.1.255 and doing arp -a, i downloaded a couple of ip
>
> > scanners but both weren't able to find the NSLU2 online.
>
> >
>
> > the device correctly shows up when started in recovery mode but
> disappears
>
> > after the firmware flash...
>
> >
>
> > On Tue, Jan 15, 2013 at 12:55 PM, echo mirage echomrg@...> wrote:
>
> >
>
> > > I already checked the pages you linked (i knew about the dark leds)
> but,
>
> > > unfortunately, most of the help is about post-flash configurations. the
>
> > > only real doubt i have is that i'm using a debian inside a virtualbox
> on a
>
> > > mac to connect and maybe that messed up with my network configuration
> (but
>
> > > upslug worked nicely), i'll double check that before trying to build
> my own
>
> > > image for openwrt with a different default IP.
>
> > >
>
> > > Thanks for the help!
>
> > >
>
> > >
>
> > > On Tue, Jan 15, 2013 at 12:40 PM, oddballhero oddballhero@...
> >wrote:
>
> >
>
> >
>
> > >
>
> > >> The things you mentioned below for your version of OpenWRT actually
> sound
>
> > >> correct. Make sure you have read
>
> > >> http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the
> section
>
> > >> Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire
> 10.03)
>
> > >> and http://wiki.openwrt.org/toh/linksys/nslu2 . The default
>
> > >> installation of 10.03 (unless things have changed in a year, ok,maybe
> 2) is
>
> > >> a static ip setup on 192.168.1.1. It will not show up on your dhcp
> table
>
> > >> because it is static. You have to make sure you are on the same
> subnet as
>
> > >> your slug. So make the ip address of you computer something like
>
> > >> 192.168.1.254 temporarily until you change the slug network setup.
> The LED
>
> > >> setup that you see,10.03 has most of the lights turned off (except for
>
> > >> Ethernet), is the default and you have to program what you want those
> LEDs
>
> > >> to do. See the bottom of the above pages. You can setup the stuff with
>
> > >> Luci or the setup files.
>
> > >>
>
> > >> --- In nslu2-general@yahoogroups.com, "Marcello" wrote:
>
> > >> >
>
> > >> > hi all, sorry if this is a noob question but i've been trying to
> flash
>
> > >> openwrt to a NSLU2 for the last couple of days and it's starting to
> feel
>
> > >> like i'm bashing my head on a wall ;)
>
> > >> >
>
> > >> > i think i managed to flash the openwrt firmware correctly (i'm using
>
> > >> 10.3.1) with upslug2 but i can't connect to the device:
>
> > >> >
>
> > >> > i tried both connecting the NSLU2 to a switch and directly to my
>
> > >> computer.
>
> > >> > when i try to telnet (or ping) the device on 192.168.1.1 or
>
> > >> 192.168.1.77 it doesn't respond and when i connect it to the switch it
>
> > >> doesn't show up on the DHCP table.
>
> > >> > when i boot the NSLU2 it flashes all the leds and then shows only
> the
>
> > >> ethernet led.
>
> > >> >
>
> > >> > any help would be REALLY appreciated!
>
> > >> > Thanks in advance!
>
> > >> > Marcello
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


--
Cordiali saluti e ossequi
- Marcello -
_______________________________________________________________________

            Numquam ponenda est pluralitas sine necessitate
_______________________________________________________________________


[Non-text portions of this message have been removed]

sounds like good advice, i'll try that out!


On Sat, Jan 19, 2013 at 5:21 PM, Ovidiu Sas <osas@...> wrote:

> Connect the NSLU to a computer that has a static IP configured (do not
> connect the NSLU to your network, use a direct ethernet cable between
> your PC/laptop and NSLU).
> Run ethereal on the specific interface and boot up the NSLU.
> Inspect all IP packets and try to figure out the IP of the NSLU.
>
> Regards,
> Ovidiu Sas
>
> On Sat, Jan 19, 2013 at 5:30 AM, echo mirage <echomrg@...> wrote:
> >
> >
> >
> > i tried everything that came to my mind about the ip configuration (with
> > switch, connecting directly to the NSLU2, with dhcp and without), i tried
> > pinging 192.168.1.255 and doing arp -a, i downloaded a couple of ip
> > scanners but both weren't able to find the NSLU2 online.
> >
> > the device correctly shows up when started in recovery mode but
> disappears
> > after the firmware flash...
> >
> > On Tue, Jan 15, 2013 at 12:55 PM, echo mirage echomrg@...> wrote:
> >
> > > I already checked the pages you linked (i knew about the dark leds)
> but,
> > > unfortunately, most of the help is about post-flash configurations. the
> > > only real doubt i have is that i'm using a debian inside a virtualbox
> on a
> > > mac to connect and maybe that messed up with my network configuration
> (but
> > > upslug worked nicely), i'll double check that before trying to build
> my own
> > > image for openwrt with a different default IP.
> > >
> > > Thanks for the help!
> > >
> > >
> > > On Tue, Jan 15, 2013 at 12:40 PM, oddballhero oddballhero@...
> >wrote:
> >
> >
> > >
> > >> The things you mentioned below for your version of OpenWRT actually
> sound
> > >> correct. Make sure you have read
> > >> http://www.nslu2-linux.org/wiki/OpenWrt/HomePage (especially the
> section
> > >> Configuring DHCP and USB ports in OpenWRT Kamikaze 8.09 and Backfire
> 10.03)
> > >> and http://wiki.openwrt.org/toh/linksys/nslu2 . The default
> > >> installation of 10.03 (unless things have changed in a year, ok,maybe
> 2) is
> > >> a static ip setup on 192.168.1.1. It will not show up on your dhcp
> table
> > >> because it is static. You have to make sure you are on the same
> subnet as
> > >> your slug. So make the ip address of you computer something like
> > >> 192.168.1.254 temporarily until you change the slug network setup.
> The LED
> > >> setup that you see,10.03 has most of the lights turned off (except for
> > >> Ethernet), is the default and you have to program what you want those
> LEDs
> > >> to do. See the bottom of the above pages. You can setup the stuff with
> > >> Luci or the setup files.
> > >>
> > >> --- In nslu2-general@yahoogroups.com, "Marcello" wrote:
> > >> >
> > >> > hi all, sorry if this is a noob question but i've been trying to
> flash
> > >> openwrt to a NSLU2 for the last couple of days and it's starting to
> feel
> > >> like i'm bashing my head on a wall ;)
> > >> >
> > >> > i think i managed to flash the openwrt firmware correctly (i'm using
> > >> 10.3.1) with upslug2 but i can't connect to the device:
> > >> >
> > >> > i tried both connecting the NSLU2 to a switch and directly to my
> > >> computer.
> > >> > when i try to telnet (or ping) the device on 192.168.1.1 or
> > >> 192.168.1.77 it doesn't respond and when i connect it to the switch it
> > >> doesn't show up on the DHCP table.
> > >> > when i boot the NSLU2 it flashes all the leds and then shows only
> the
> > >> ethernet led.
> > >> >
> > >> > any help would be REALLY appreciated!
> > >> > Thanks in advance!
> > >> > Marcello
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


--
Cordiali saluti e ossequi
- Marcello -
_______________________________________________________________________

            Numquam ponenda est pluralitas sine necessitate
_______________________________________________________________________


[Non-text portions of this message have been removed]

Lat call for asterisk14 (1.4) and asterisk16 (1.6).
Please upgrade to asterisk18 (1.8) or asterisk10 (10).

Regards,
Ovidiu Sas

On Thu, Jan 10, 2013 at 8:53 AM, Ovidiu Sas <osas@...> wrote:
> Hello all,
>
> We would like to cleanup asterisk packages in the feeds.
> We will start by removing asterisk 1.2:
>  - asterisk
>  - asterisk-sounds (obsolete by asterisk14 sound packages)
>
> Is there anyone still using asterisk 1.4 or 1.6?
>  - asterisk14
>  - asterisk14-chan-capi
>  - asterisk16
>  - asterisk16-addons
> We would like to remove the above versions if not used anymore.
>
> The officially maintained versions are asterisk 1.8 and asterisk 10:
>  - asterisk-gui
>  - asterisk14-core-sounds*
>  - asterisk14-extra-sounds*
>  - asterisk14-moh*
>  - asterisk18
>  - asterisk10
>
>
> Regards,
> Ovidiu Sas

If anybody actually needs the packages, they can download the ipk files
(http://ipkg.nslu2-linux.org/feeds/) for posterity's sake or build them
(http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware) for the fun of
it.

--- In nslu2-general@yahoogroups.com, Ovidiu Sas  wrote:
>
> Lat call for asterisk14 (1.4) and asterisk16 (1.6).
> Please upgrade to asterisk18 (1.8) or asterisk10 (10).
>
> Regards,
> Ovidiu Sas
>
> On Thu, Jan 10, 2013 at 8:53 AM, Ovidiu Sas  wrote:
> > Hello all,
> >
> > We would like to cleanup asterisk packages in the feeds.
> > We will start by removing asterisk 1.2:
> >  - asterisk
> >  - asterisk-sounds (obsolete by asterisk14 sound packages)
> >
> > Is there anyone still using asterisk 1.4 or 1.6?
> >  - asterisk14
> >  - asterisk14-chan-capi
> >  - asterisk16
> >  - asterisk16-addons
> > We would like to remove the above versions if not used anymore.
> >
> > The officially maintained versions are asterisk 1.8 and asterisk 10:
> >  - asterisk-gui
> >  - asterisk14-core-sounds*
> >  - asterisk14-extra-sounds*
> >  - asterisk14-moh*
> >  - asterisk18
> >  - asterisk10
> >
> >
> > Regards,
> > Ovidiu Sas
>

Thanks for the upkeep!


On Tue, Jan 22, 2013 at 12:15 AM, oddballhero <oddballhero@...> wrote:

> **
>
>
> If anybody actually needs the packages, they can download the ipk files (
> http://ipkg.nslu2-linux.org/feeds/) for posterity's sake or build them (
> http://www.nslu2-linux.org/wiki/Optware/AddAPackageToOptware) for the fun
> of it.
>
>
> --- In nslu2-general@yahoogroups.com, Ovidiu Sas wrote:
> >
> > Lat call for asterisk14 (1.4) and asterisk16 (1.6).
> > Please upgrade to asterisk18 (1.8) or asterisk10 (10).
> >
> > Regards,
> > Ovidiu Sas
> >
> > On Thu, Jan 10, 2013 at 8:53 AM, Ovidiu Sas wrote:
> > > Hello all,
> > >
> > > We would like to cleanup asterisk packages in the feeds.
> > > We will start by removing asterisk 1.2:
> > > - asterisk
> > > - asterisk-sounds (obsolete by asterisk14 sound packages)
> > >
> > > Is there anyone still using asterisk 1.4 or 1.6?
> > > - asterisk14
> > > - asterisk14-chan-capi
> > > - asterisk16
> > > - asterisk16-addons
> > > We would like to remove the above versions if not used anymore.
> > >
> > > The officially maintained versions are asterisk 1.8 and asterisk 10:
> > > - asterisk-gui
> > > - asterisk14-core-sounds*
> > > - asterisk14-extra-sounds*
> > > - asterisk14-moh*
> > > - asterisk18
> > > - asterisk10
> > >
> > >
> > > Regards,
> > > Ovidiu Sas
> >
>
>
>


[Non-text portions of this message have been removed]

Thanks to Crosstool, I managed to get kernel 3.7.2 built for the NSLU2.
Yeaaaaaaa

ok, so I have my *.deb packages.. (I made headers too)
I install them to the NSLU2..  reboot...
uname -a still shows older kernel version 2.6.32-5-ixp4xx

Doing some googling this morning I see there is a step that copies the kernel to
flash / USB, or whatever it is..   Apex in in there somewhere, too.

Anyway, I see the process happen.. That is, I can even run the command
flash-kernel...

Flashing kernel:  <short delay...> done.
Flashing initramfs: <long delay...> done.

Doesn't that mean it worked?

Why can't I do apt-get update,    apt-get upgrade and get 3.7.x kernel like all
the documentation says I can do?  Am I missing a source?

Thanks!!!!

Anyone out there willing to build a new debian kernel for the NSLU2 for
me?Having a hard time.Thanks


[Non-text portions of this message have been removed]

I followed this article but it didn't work
http://www.adrianandgenese.com/blogger/2010/07/15/how-to-set-a-static-ip-for-a-p\
ogoplug-and-make-it-persistent/

Does anyone else have a way to give a static ip address to pogoplug?

Did you reboot after making those modifications?  Where there any error messages
while you were performing the modifications?  Are you able to ssh back in to
your plug after making those modifications?

If you didn't reboot, then the modifications won't take place.
If there were error messages, then the instructions probably were not carried
out successfully.
If you can't ssh back into your plug after making the modification and rebooting
the plug, then you need to solve that problem first.

If everything is working fine and you have a static ip, then you don't need to
do anything.
If everything is working fine and you don't have a static ip, then continue.
What is described below is actually just a variation of that article you
followed, except that if no usb drive is seen, then it acts "stock" obtaining
the ip information with dhcp.  All this adds is a statement after mounting the
/opt drive to change to a static ip.
The is just the same as typing on the command line "ifconfig eth0
192.168.xxx.xxx" where 192.168.xxx.xxx is the static ip address you desire.  If
you are still connected by ssh after typing above statement, you can verify this
information by typing "ifconfig" which should show eth0 to have your desired
static ip.  If not, then the method below and that article you cited won't work.

Do this at your own risk!  No warranty implied.
Be careful, modifying you rcS can "brick/break" the plug!
If you don't feel comfortable doing this then don't.
If you don't know how to edit the file, then don't.
Make sure that you read everything below before doing anything and that you know
how to perform the modifications.  If not, don't.

You should also make a backup of your rcS.

A little trick is to leave the rcS as it is, so remove your modifications.  Let
"udhcpc" get most of the information and create the resolv.conf so that in case
parameters change with your network, you can recover.  Assuming you are using
Optware, create a file in "/opt/etc/init.d called S22static, with the contents
between the lines (you need to modify aaa.aaa with the pertinent information for
your static ip and bbb.bbb with the pertinent information for your local dns
server):
_________________________________
#!/bin/sh

/sbin/ifconfig eth0 192.168.aaa.aaa
echo "nameserver 192.168.bbb.bbb" >> /tmp/resolv.conf
## Uncomment the lines below to activate Google's public name servers.
#echo "nameserver 8.8.8.8" >> /tmp/resolv.conf
#echo "nameserver 8.8.4.4" >> /tmp/resolv.conf
__________________________________

You need to make this file executable with "chmod 755
/opt/etc/init.d/S22static".
You then add the line "/opt/etc/init.d/S22static" after you mount your /opt usb
drive.  This way, if you boot up without the usb drive, it can still get the
dhcp info like the stock setup, in case your network parameters change (change
subnet, replace router, etc.).

A problem you may have is that the instructions on that site you followed,
probably deleted the soft link from "/etc/resolv.conf" to "/tmp/resolv.conf". 
Verify with "ls -l /etc/resolve.conf".  It should look approximately like:
lrwxrwxrwx 1 root root 16 Dec 31  1999 /etc/resolv.conf -> /tmp/resolv.conf
The date and size does not matter.  If not, you have to recreate the link.

--- In nslu2-general@yahoogroups.com, "Jackie"  wrote:
>
> I followed this article but it didn't work
>
http://www.adrianandgenese.com/blogger/2010/07/15/how-to-set-a-static-ip-for-a-p\
ogoplug-and-make-it-persistent/
>
> Does anyone else have a way to give a static ip address to pogoplug?
>