The package has been rebuilt and the latest version is 0.9.7m-6. Please do "ipkg update" and retry.
-Brian
--- In nslu2-linux@yahoogroups.com, "floh0033" <mario.althammer@...> wrote:
>
>
>
> --- In nslu2-linux@yahoogroups.com, "Brian" <b88zhou@> wrote:
> >
> > Should be fixed now.
> >
> > -Brian
> >
>
> Thanks for your response
>
> Still the same problem this time...
>
> Installing openssl (0.9.7m-5) to root...
> Downloading http://ipkg.nslu2-linux.org/feeds/optware/nslu2/cross/stable/openssl_0.9.7m-5_armeb.ipk
> wget: server returned error 404: HTTP/1.1 404 Not Found
> Nothing to be done
>
Monday, April 30, 2012
[nslu2-linux] Re: apache - openssl installation
[nslu2-linux] Re: apache - openssl installation
--- In nslu2-linux@yahoogroups.com, "Brian" <b88zhou@...> wrote:
>
> Should be fixed now.
>
> -Brian
>
Thanks for your response
Still the same problem this time...
Installing openssl (0.9.7m-5) to root...
Downloading http://ipkg.nslu2-linux.org/feeds/optware/nslu2/cross/stable/openssl_0.9.7m-5_armeb.ipk
wget: server returned error 404: HTTP/1.1 404 Not Found
Nothing to be done
[nslu2-linux] ipkg update reports "file too short"
Hi all,
I have a GoFlex Home, which is based upon the OpenStora system, which uses ipkg
for package management:
http://www.openstora.com/wiki/index.php?title=Getting_Started#Preparing_to_insta\
ll_software_and_checking_free_space
So I followed the instructions for moving /opt (I moved it to /mnt/eSata/opt)
and have been installing packages.
I cancelled an install process of ipkg and now it reports:
bash-3.2# /opt/bin/ipkg update
/opt/bin/ipkg: error while loading shared libraries: /opt/lib/libipkg.so.0: file
too short
The only way to get around this seems to be a reinstall of ipkg. That's
annoying...
Help?
- Phil
PS here is the results of running 'df':
bash-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 212M 196M 16M 93% /
ubi0:rootfs 212M 196M 16M 93% /
none 62M 32K 62M 1% /dev
nodev 62M 36M 26M 59% /var/log
nodev 62M 480K 61M 1% /mnt/tmpfs
nodev 62M 24K 62M 1% /var/lib/php/session
nodev 62M 480K 61M 1% /tmp
nodev 62M 480K 61M 1% /var/run
nodev 62M 480K 61M 1% /var/cache
nodev 62M 480K 61M 1% /var/lib/axentra_sync
nodev 62M 480K 61M 1% /var/lib/oe-admin/minions
nodev 62M 480K 61M 1% /var/lib/oe-admin/actions
nodev 62M 480K 61M 1% /var/lib/oe-update-checker
nodev 62M 480K 61M 1% /etc/blkid
nodev 62M 480K 61M 1% /var/lib/dbus
nodev 62M 480K 61M 1% /var/lib/dhclient
nodev 62M 480K 61M 1% /var/lock
nodev 62M 480K 61M 1% /var/spool
nodev 62M 480K 61M 1% /var/lib/avahi-autoipd
nodev 62M 480K 61M 1% /etc/dhclient-eth0.conf
nodev 62M 480K 61M 1% /etc/printcap
nodev 62M 480K 61M 1% /etc/resolv.conf
nodev 1.9T 413G 1.5T 23% /var/cache/mt-daapd
ubi0:rootfs 212M 196M 16M 93% /tmp/eaccelerator
ubi0:rootfs 212M 196M 16M 93% /tmp/templates_c
nodev 62M 480K 61M 1% /home/0external
/dev/sda1 1.9T 413G 1.5T 23% /mnt/eSata
/dev/sda1 1.9T 413G 1.5T 23% /home/0common
/dev/sda1 1.9T 413G 1.5T 23% /tmp/atalk
/dev/sda1 1.9T 413G 1.5T 23% /tmp/albumcache
/dev/sda1 1.9T 413G 1.5T 23% /tmp/0db
/dev/sda1 1.9T 413G 1.5T 23% /var/cache/mt-daapd
/dev/sda1 1.9T 413G 1.5T 23% /tmp/apache_tmp
/dev/sda1 1.9T 413G 1.5T 23% /tmp/minidlna
/dev/sda1 1.9T 413G 1.5T 23% /home/0db/id3_cache
/dev/sda1 1.9T 413G 1.5T 23% /home/0backups
nodev 62M 480K 61M 1% /home/<user id 1>/External Storage
nodev 62M 480K 61M 1% /home/<user id 2>/External Storage
/dev/sda1 1.9T 413G 1.5T 23% /home/<user id 1>/GoFlex Home Personal
/dev/sda1 1.9T 413G 1.5T 23% /home/<user id 1>/GoFlex Home Backup
/dev/sda1 1.9T 413G 1.5T 23% /home/<user id 1>/GoFlex Home Public
/dev/sda1 1.9T 413G 1.5T 23% /home/<user id 2>/GoFlex Home Personal
/dev/sda1 1.9T 413G 1.5T 23% /home/<user id 2>/GoFlex Home Backup
/dev/sda1 1.9T 413G 1.5T 23% /home/<user id 2>/GoFlex Home Public
[nslu2-linux] Re: apache - openssl installation
Should be fixed now.
-Brian
--- In nslu2-linux@yahoogroups.com, "floh0033" <mario.althammer@...> wrote:
>
> an error occures during the apache installation on my slug (unslung 6.8)
> apache needs openssl for the install, but the link will be no more present
>
> please could you help me ?
>
Sunday, April 29, 2012
[nslu2-linux] apache - openssl installation
an error occures during the apache installation on my slug (unslung 6.8)
apache needs openssl for the install, but the link will be no more present
please could you help me ?
Friday, April 27, 2012
[nslu2-linux] Re: unslung and UTF-8 character encoding
Made a cross compile machine and built it myself
http://dl.dropbox.com/u/60363804/nls_utf8.o
copy to lib\modules\2.4.22-xfs\kernel\fs\nls
and insmod nls_utf8
Setup Putty or whatever you use to UTF-8 and select a font with greek
characters.
Thursday, April 19, 2012
[nslu2-linux] Re: unslung and UTF-8 character encoding
I would really also like this.
I guess we need someone to compile the module
kernel-module-nls-utf
for unslung 2.4.22.l2.3r63-r21
for us to able to read greek characters from cli.
Thanks
Tuesday, April 17, 2012
[nslu2-linux] Re: unslung and UTF-8 character encoding
Hi Vassili,
thanks for your tip.But I am not talking about samba. I am trying to synch my source codes from my office to my unslung machine at home.
unslung svn <---- > office sources svn.
Only the "default" english characters are shown and the svn proccess hangs with the greek file names.
Thanks anyway.
--- In nslu2-linux@yahoogroups.com, "Iraklis" <iraklis031@...> wrote:
>
> I am trying to use svn and handle Greek characters within files and folders. The only way to do it i must install utf-8 locale to my unslung V2.3R63-uNSLUng-6.10-beta. "locale" is missing and I am really stuck here. any Ideas ???
>
> Regards
> Iraklis
>
Re: [nslu2-linux] unslung and UTF-8 character encoding
Γεια σου Irakli,
I had similar problems in the past with the Greek filenames. I solved them by adding the following lines to the user_smb.conf file.
/etc/samba/user_smb.conf
unix charset = UTF8
dos charset = UTF8
display charset = UTF8
hth
vassilis
On 17/04/2012 02:51 μμ, Iraklis wrote:
I am trying to use svn and handle Greek characters within files and folders. The only way to do it i must install utf-8 locale to my unslung V2.3R63-uNSLUng-6.10-beta. "locale" is missing and I am really stuck here. any Ideas ???
Regards
Iraklis
[LINUX_Newbies] Re: Changing PATH environment after manual TexLive 2011 installation on Debian
--- In LINUX_Newbies@yahoogroups.com, "Pascal" <pascal.hasko@...> wrote:
>
> I'd like to disagree with you. I do think that it is a Debian issue also, not only Tex's fault. TexLive packages provided by Debian are missing certain stuff and in this case I need that. Otherwise I don't have a problem with Debian's tex. Even the version 2011 from Debian unstable is not complete. I'd say I could tinker around with Debian's package management as much as I want, if it is not in the repositories what I want I won't get it that way. That's why I had to install TexLive 2011 manually.
>
> Pascal
>
"if it is not in the repositories what I want I won't get it that way."
Then you make it yourself. This is GNU/Linux.
http://tldp.org/HOWTO/html_single/Debian-Binary-Package-Building-HOWTO/
With FOSS the only limits are the ones that you arbitrarily place upon yourself.
[nslu2-linux] unslung and UTF-8 character encoding
I am trying to use svn and handle Greek characters within files and folders. The only way to do it i must install utf-8 locale to my unslung V2.3R63-uNSLUng-6.10-beta. "locale" is missing and I am really stuck here. any Ideas ???
Regards
Iraklis
Monday, April 16, 2012
[LINUX_Newbies] Re: Changing PATH environment after manual TexLive 2011 installation on Debian
--- In LINUX_Newbies@yahoogroups.com, "Paul" <pfrederick1@...> wrote:
>
>
>
> --- In LINUX_Newbies@yahoogroups.com, "Pascal" <pascal.hasko@> wrote:
> >
> > Yes I have. Indeed I updated my TexLive to the Debian unstable version, but still crucial packages are missing. It also lacks TexLive package manager "tlmgr" for updating which is the recommended way instead of using apt-get or aptitude. As my favorite tex editor 'Kile' would be removed by uninstalling the official TexLive, I'd prefer to have both installations and have Debian ignore its own packages.
> >
>
> It sounds to me like you'd be happier with another distribution. Now might possibly be a good time to either switch, or learn how to better control Debian's package management system. There are other alternatives you have yet to explore.
>
> http://www.debianhelp.co.uk/debianproblem.htm
>
> Some of this, sections 8-12, read correctly, applies to you as well:
> http://wooledge.org/~greg/sidfaq.html
>
> I'm not going to tell you what you should do regarding your TeX dilemma, or even suggest it, but I do recommend you completely familiarize yourself with all pertinent information before you go ignoring everything, and carving out your own path.
>
> The more you know, the more you Debianize.
>
> P.S. Debian isn't your problem, TeX is.
>
Finally, I got the issue fixed. I created a .bash_profile in my HOME-directory with the necessary lines for modifying the PATH environment and had it sourced by /etc/profile. Now everything works fine, for the time being.
I'd like to disagree with you. I do think that it is a Debian issue also, not only Tex's fault. TexLive packages provided by Debian are missing certain stuff and in this case I need that. Otherwise I don't have a problem with Debian's tex. Even the version 2011 from Debian unstable is not complete. I'd say I could tinker around with Debian's package management as much as I want, if it is not in the repositories what I want I won't get it that way. That's why I had to install TexLive 2011 manually.
Pascal
Sunday, April 15, 2012
[LINUX_Newbies] Re: Changing PATH environment after manual TexLive 2011 installation on Debian
--- In LINUX_Newbies@yahoogroups.com, "Pascal" <pascal.hasko@...> wrote:
>
> Yes I have. Indeed I updated my TexLive to the Debian unstable version, but still crucial packages are missing. It also lacks TexLive package manager "tlmgr" for updating which is the recommended way instead of using apt-get or aptitude. As my favorite tex editor 'Kile' would be removed by uninstalling the official TexLive, I'd prefer to have both installations and have Debian ignore its own packages.
>
It sounds to me like you'd be happier with another distribution. Now might possibly be a good time to either switch, or learn how to better control Debian's package management system. There are other alternatives you have yet to explore.
http://www.debianhelp.co.uk/debianproblem.htm
Some of this, sections 8-12, read correctly, applies to you as well:
http://wooledge.org/~greg/sidfaq.html
I'm not going to tell you what you should do regarding your TeX dilemma, or even suggest it, but I do recommend you completely familiarize yourself with all pertinent information before you go ignoring everything, and carving out your own path.
The more you know, the more you Debianize.
P.S. Debian isn't your problem, TeX is.
[LINUX_Newbies] Re: Changing PATH environment after manual TexLive 2011 installation on Debian
--- In LINUX_Newbies@yahoogroups.com, "Paul" <pfrederick1@...> wrote:
>
>
>
> --- In LINUX_Newbies@yahoogroups.com, "Pascal" <pascal.hasko@> wrote:
> >
> > Hi all,
> >
> > I need help with setting up my PATH environments on Debian Testing (Wheezy) after I manually installed TexLive 2011. In Debian's repositories (Testing) there is only TexLive 2009 available and I need an up-to-date moderncv.cls class file for writing a specific document. So I decided to upgrade TexLive to the unstable version (TexLive 2011). Unfortunately the moderncv.cls file is also missing there. On the German Tex mailinglist I was adviced to manually install TexLive 2011, which has the files I need. Debian's TexLive package is rather incomplete. They generally advice to install TexLive by hand on Linux system and not rely on package-management in this regard.
> >
> > Removing the Debian TexLive is not really an option as my favorite LaTeX-Editor 'Kile' depends on it.
> >
> > The installation finished (Tested via command line, it works there!) the installer told me to change my PATH environment settings accordingly:
> >
> > Add /usr/local/texlive/2010/texmf/doc/man to MANPATH, if not dynamically determined.
> >
> > Add /usr/local/texlive/2010/texmf/doc/info to INFOPATH.
> >
> > Most importantly, add /usr/local/texlive/2010/bin/x86_64-linux to your PATH for current and future
> > sessions.
> >
> > Now I'm somewhat confused as to where to put these lines. I am the only user on my home PC (If you do not count Root as a user in his own right), so the settings do not necessarily have to be system-wide. Some websites told me to put
> > 'PATH=PATH$:/usr/local/texlive/2011/bin/i386-linux'
> >
> > in /etc/profile
> >
> > Others to put it into my own .profile. Still others said it should be either in /bash.bashrc or
> > ~/.bashrc
> >
> > I got a little confused here.
> >
> > Ubuntu's German wiki advises against all the proposed solutions, and wants me to add these lines to /etc/environment. This file does not exist yet on my Debian system and I have not found any information so far, whether one should create such a file first. Although as to what I have read /etc/environment, at least on Ubuntu, should exist and have already some lines relating PATH variables in it.
> >
> >
> > My GUI LaTeX editors still use Debian's own TexLive packages, not the manually installed ones and do not let me write the document as the aforementioned file is missing. I logged out after each change, and as that did not help I did a full reboot.
> >
> > Could you give some advice where to set the PATH environment? This should also be set for GUI programs.
> >
> > For the time being I would like to avoid the rough&dirty workaround of symlinking the default TexLive folders with the ones I have installed by hand.
> >
> > Thanks a lot for your help,
> >
> > Pascal
> >
>
> Have you looked in Debian unstable for texlive 2011?
>
> http://packages.debian.org/sid/texlive
>
> Package: texlive (2011.20120410-1)
Yes I have. Indeed I updated my TexLive to the Debian unstable version, but still crucial packages are missing. It also lacks TexLive package manager "tlmgr" for updating which is the recommended way instead of using apt-get or aptitude. As my favorite tex editor 'Kile' would be removed by uninstalling the official TexLive, I'd prefer to have both installations and have Debian ignore its own packages.
Re: [nslu2-linux] Looking for replacement AC adaptor
Mind that some power supplies have a max current and a minimal current.
If the max current is significantly larger that the one of the official power supply (which now I don't recall) you have more chances that the NSLU2 without or even with load (HD)
won't draw enough power to keep the replacement power supply active.
It happened to me: I had to disable the low-power mode of my USB HD (as I was too lazy to solder a resistor on the supply cable).
Ettore
If the nominal max current is much larger than the one actually
Just to clarify, you don't need to match the max current; the max
current of the power supply just needs to be at least as large (as the
max current of the NSLU2 or the original power supply).
When replacing power supplies, check that:
- the plug matches,
- the polarity matches (whether the center is + or -, this is usually
indicated in symbol form),
- the output voltage is identical,
- the output current rating of the power supply is larger than the
current rating of the load (in this case, the NSLU2),
- and that the power supply is compatible with your wall power (if
you're buying the power supply domestically, this last point is
probably true).
Best regards,
-Jimmy> > **
On Wed, 28 Mar 2012 12:20:28 -0700
Ralph Finch <ralphmariafinch@gmail.com> wrote:
> Or...get a brand x power supply with the same output voltage and max
> current. If the plug is not the same, no problem, cut the wires of the
> replacement and defunct PSU, and wire the old plug to the new PSU.
> Solder, crimps, whatever, separate with heat shrink tubing (best) or
> electrical tape, etc.
>
> On Wed, Mar 28, 2012 at 5:09 AM, dystopianrebel
> <dystopianrebel@yahoo.com>wrote:
>
> >
> >
> > The AC adaptor for one of my Slugs has failed. By swapping
> > adaptors, I know that the Slug itself is still good.
> >
> > If you have a spare that you will not be using or want to sell,
> > please contact me.
> >
[LINUX_Newbies] Re: Changing PATH environment after manual TexLive 2011 installation on Debian
--- In LINUX_Newbies@yahoogroups.com, "Pascal" <pascal.hasko@...> wrote:
>
> Hi all,
>
> I need help with setting up my PATH environments on Debian Testing (Wheezy) after I manually installed TexLive 2011. In Debian's repositories (Testing) there is only TexLive 2009 available and I need an up-to-date moderncv.cls class file for writing a specific document. So I decided to upgrade TexLive to the unstable version (TexLive 2011). Unfortunately the moderncv.cls file is also missing there. On the German Tex mailinglist I was adviced to manually install TexLive 2011, which has the files I need. Debian's TexLive package is rather incomplete. They generally advice to install TexLive by hand on Linux system and not rely on package-management in this regard.
>
> Removing the Debian TexLive is not really an option as my favorite LaTeX-Editor 'Kile' depends on it.
>
> The installation finished (Tested via command line, it works there!) the installer told me to change my PATH environment settings accordingly:
>
> Add /usr/local/texlive/2010/texmf/doc/man to MANPATH, if not dynamically determined.
>
> Add /usr/local/texlive/2010/texmf/doc/info to INFOPATH.
>
> Most importantly, add /usr/local/texlive/2010/bin/x86_64-linux to your PATH for current and future
> sessions.
>
> Now I'm somewhat confused as to where to put these lines. I am the only user on my home PC (If you do not count Root as a user in his own right), so the settings do not necessarily have to be system-wide. Some websites told me to put
> 'PATH=PATH$:/usr/local/texlive/2011/bin/i386-linux'
>
> in /etc/profile
>
> Others to put it into my own .profile. Still others said it should be either in /bash.bashrc or
> ~/.bashrc
>
> I got a little confused here.
>
> Ubuntu's German wiki advises against all the proposed solutions, and wants me to add these lines to /etc/environment. This file does not exist yet on my Debian system and I have not found any information so far, whether one should create such a file first. Although as to what I have read /etc/environment, at least on Ubuntu, should exist and have already some lines relating PATH variables in it.
>
>
> My GUI LaTeX editors still use Debian's own TexLive packages, not the manually installed ones and do not let me write the document as the aforementioned file is missing. I logged out after each change, and as that did not help I did a full reboot.
>
> Could you give some advice where to set the PATH environment? This should also be set for GUI programs.
>
> For the time being I would like to avoid the rough&dirty workaround of symlinking the default TexLive folders with the ones I have installed by hand.
>
> Thanks a lot for your help,
>
> Pascal
>
Have you looked in Debian unstable for texlive 2011?
http://packages.debian.org/sid/texlive
Package: texlive (2011.20120410-1)
Installing it might be your cleanest solution.
Sometimes it isn't the answers but the questions that matter.