I have an LS-250GL and I am trying to set up access to it from the outside
world via the internet.  I dont mind whether it's ftp access or any other
type of access, as long as I can read/write to it.

My broadband has a dynamic IP address, but I have set up an account with
dyndns so that's not a problem.

I have tried two Virtual Server setups in my router, one using port 80 and
the other, port 21.  With the port 80 setup, when I go to my dyndns address
in Internet Explorer, I get to the admin system of the Linkstation where it
askes me to log in with my admin password.  This proves that I can reach the
Linkstation but obviousley I have no access to the information stored on it.
With the port 21 setup, if I ftp to the dyndns address from internet
explorer, I get to the root of the drive which shows 2 directories, 'Info' &
'Disk 1'.  I can open the info directory and view/download the files
contained within, but can't see or access the area of the drive where my
info is stored.

Sorry if this is all a bit basic for all the clever people who use this
forum, but I'm way out of my depth with this type of thing and don't know
what else to try.

I hope someone will be kind enough to give me some pointers on what I'm
doing wrong and what I should try next.

Many thanks


--
View this message in context:
http://www.nabble.com/LS-250GL-Internet-FTP-Server-Help-tf3154436.html#a8747028
Sent from the Buffalo LinkStation mailing list archive at Nabble.com.

> I must admit that getting a stock kernel up an running on the
> Linkstation was more troublesome than on the Kurobox, because I
> originally patched my firmware with freelink and you need it kept on
> rebooting with a v2.4 kernel (as expected and documented). But it
can be
> done, and I think it is a great leap forward!

i also agree that this was nice work.

we really should create a simple way of installing UBoot-images to all
linkstations...kuroguy summed up the way we outlined already here:
http://forum.linkstationwiki.net/index.php?action=vthread&forum=7&topic=1760&pag\
e=1#msg17689

when i have time i think i will look at that again....

LNI`s UBoot still is the best one...

On Sat, 27 Jan 2007, daveyip wrote:

> I have a Linkstation HS that I have installed u-boot on according to
>
> http://www.kurobox.com/mwiki/index.php/Kurobox_support_in_stock_2.6_kernels
>
> Over at the Kurobox wiki
>
> I have everything installed and a 2.6.20-rc5 kernel booting over nc
>
> But have run up against
>
> linkstation: disarming the AVR watchdog:
> VFS: Cannot open root device "sda1" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
>
> I have used the stock .config file for the linkstation out of the
> kernel that has IDE disabled and PATA enabled. My fstab looks like

Ok, I am not sure what a Linkstation HS exactly is. The stock kernel /
bootloader configuration has been tested so far on KuroBox HG and HD. Is
the LS HS hardware identical to kuro HG? Looks like there might be a
slight difference. Maybe you'll need a special device tree. To clarify
that, please post your complete dmesg captured with your nc. Would also be
good to see dmesg from a running kernel on such a system, as well as
output from lspci -vv, /proc/interrupts.

> # /etc/fstab: static file system information.
> #
> # <file system> <mount point>   <type>  <options>               <dump>
>  <pass>
> /dev/sda1       /               ext3    defaults,noatime,errors=remount-ro
> 0 0
> proc            /proc           proc    defaults
>   0 0
> none            /dev/pts        devpts  gid=5,mode=20
>   0 0
> /dev/sda2       swap            swap    defaults
>   0 0
> /dev/sda3       /datafiles      ext3    defaults,noatime
>   0 0

Correct, but you haven't got that far - your kernel cannot mount the root
as specified on the command line, i.e., your /etc/fstab has not been read
yet:-)

> My u-boot config for CONFIG_BOOTARGS looks like
>
> #define CONFIG_BOOTARGS         "root=/dev/sda1
> netconsole=6666@.../,@192.168.0.7/00:11:D8:1A:78:21"
>
> (Incidently, the instructions say to have rtc-rs5c372.probe=0,0x32 in
> there to, but I found that this causes no kernel messages to be
> displayed in nc)

This also hints at some differences in the hardware.

Thanks
Guennadi
---
Guennadi Liakhovetski

"root=/dev/sda1 netconsole=6666@.../,@5.6.7.8/ rtc-rs5c372.probe=0,0x32"

On Mon, 29 Jan 2007, David Yip wrote:

> I believe that under v2.6.19 the hwclock is working
>
> LinkStation:/sys/devices# hwclock
> Mon Jan 29 12:00:23 2007 -0.954070 seconds
>
> LinkStation:/sys/devices# find . -print | grep i2
> ./platform/fsl-i2c.1/i2c-0/0-0032
> ./platform/fsl-i2c.1/i2c-0/0-0032/name

Yep, that's fine and the address is the same. Have no clue why it should
not work under 2.6.20... You ARE absolutely sure that if you specify
"rtc-rs5c372.probe=0,0x32" your kernel hangs on both KuroboxHG and LS
HS?... Can you send the same "find" output from a 2.6.20 on 1 of the 2
NASs without that command line option? Well, I could suggest 2 ways to
debug it:

1. boot as normal one of your 2 systems with 2.6.20 and do "i2cdetect 0
0x30 0x3f". i2cdetect is in lm-sensors package.

2. Compile rtc-rs5c372 as a module and (after issuing "sync" 3 times:-))
and while logging with netcat do "modprobe rtc-rs5x372 probe=0,0x32"

Hm, something rings the bell... I think, they changed the register access
to rs5c372 to "method 3" with 2.6.20... But that works on my and some
other systems...

Thanks
Guennadi
---
Guennadi Liakhovetski

Ok, I am not sure what a Linkstation HS exactly is. The stock kernel / bootloader configuration has been tested so far on KuroBox HG and HD. Is the LS HS hardware identical to kuro HG? Looks like there might be a slight difference. Maybe you'll need a special device tree. To clarify that, please post your complete dmesg captured with your nc. Would also be good to see dmesg from a running kernel on such a system, as well as output from lspci -vv, /proc/interrupts.

My u-boot config for CONFIG_BOOTARGS looks like #define CONFIG_BOOTARGS "root=/dev/sda1
netconsole=6666@.../,@192.168.0.7/00:11:D8:1A:78:21"
(Incidently, the instructions say to have rtc-rs5c372.probe=0,0x32 in
there to, but I found that this causes no kernel messages to be
displayed in nc)

This also hints at some differences in the hardware.

With those linkstation pro's  you have to set the shared folder
permission to FTP, to allow it to show. You will then see the shared
folder in Disk1.

You have functionality, but to get to the shared folders that you
have,  go into the admin web interface and then go into shared
folders, then select the shared folder you want to allow ftp access
to, and check FTP in those settings (sorry I don't have the gui
available to tell you the name of the setting).

One important note is that if the access permissions are not set, this
folder will be considered anonymous, so anyone and everyone will be
able to read/write to that folder (even delete).

As a general precaution, its best to set the folder to have access
restrictions if you choose to share that folder,  then you can set
read and write permissions.

Sorry for the delay in responding.

Hope this helps.

-goat


--- In LinkStation_General@yahoogroups.com, Steve Pulfrey <steve@...>
wrote:
>
>
> I have an LS-250GL and I am trying to set up access to it from the
outside
> world via the internet.  I dont mind whether it's ftp access or any
other
> type of access, as long as I can read/write to it.
>
> My broadband has a dynamic IP address, but I have set up an account with
> dyndns so that's not a problem.
>
> I have tried two Virtual Server setups in my router, one using port
80 and
> the other, port 21.  With the port 80 setup, when I go to my dyndns
address
> in Internet Explorer, I get to the admin system of the Linkstation
where it
> askes me to log in with my admin password.  This proves that I can
reach the
> Linkstation but obviousley I have no access to the information
stored on it.
> With the port 21 setup, if I ftp to the dyndns address from internet
> explorer, I get to the root of the drive which shows 2 directories,
'Info' &
> 'Disk 1'.  I can open the info directory and view/download the files
> contained within, but can't see or access the area of the drive where my
> info is stored.
>
> Sorry if this is all a bit basic for all the clever people who use this
> forum, but I'm way out of my depth with this type of thing and don't
know
> what else to try.
>
> I hope someone will be kind enough to give me some pointers on what I'm
> doing wrong and what I should try next.
>
> Many thanks
>
>
> --
> View this message in context:
http://www.nabble.com/LS-250GL-Internet-FTP-Server-Help-tf3154436.html#a8747028
> Sent from the Buffalo LinkStation mailing list archive at Nabble.com.
>

Is there a way to make this thing run more quietly???

What thing?  which linkstation do you have?

Usually there are only two reasons for the noise, the hard drive, or
the fan.
The fan is usually more common to be the noise maker.

Are you in your warranty?  If so, replace it,  if not,  take a look
here for replacement possibilities. (may involve soldering)

http://linkstationwiki.net/index.php?title=Fan_noise


-goat

--- In LinkStation_General@yahoogroups.com, "pstorage0001"
<pelachrum@...> wrote:
>
> Is there a way to make this thing run more quietly???
>

i have HD-HG400LAN, the gigabit home server

yes it does sound like a fan noise. i do have warranty but are you
suggesting that the fan might be bad? how is it that they would
replace it for better model under warranty?

i'll check out the link, thanks




--- In LinkStation_General@yahoogroups.com, "musikgoat"
<musikgoat@...> wrote:
>
> What thing?  which linkstation do you have?
>
> Usually there are only two reasons for the noise, the hard drive, or
> the fan.
> The fan is usually more common to be the noise maker.
>
> Are you in your warranty?  If so, replace it,  if not,  take a look
> here for replacement possibilities. (may involve soldering)
>
> http://linkstationwiki.net/index.php?title=Fan_noise
>
>
> -goat
>
> --- In LinkStation_General@yahoogroups.com, "pstorage0001"
> <pelachrum@> wrote:
> >
> > Is there a way to make this thing run more quietly???
> >
>

I haven't personally gone through a replacement, but I would suspect
that they would either repair it or more likely, replace it.
I would suggest that you call the tech support to find out more info
about that, in the mean time, remember that opening the unit voids the
warranty with Buffalo.

-goat


--- In LinkStation_General@yahoogroups.com, "pstorage0001"
<pelachrum@...> wrote:
>
> i have HD-HG400LAN, the gigabit home server
>
> yes it does sound like a fan noise. i do have warranty but are you
> suggesting that the fan might be bad? how is it that they would
> replace it for better model under warranty?
>
> i'll check out the link, thanks
>
>
>
>
> --- In LinkStation_General@yahoogroups.com, "musikgoat"
> <musikgoat@> wrote:
> >
> > What thing?  which linkstation do you have?
> >
> > Usually there are only two reasons for the noise, the hard drive, or
> > the fan.
> > The fan is usually more common to be the noise maker.
> >
> > Are you in your warranty?  If so, replace it,  if not,  take a look
> > here for replacement possibilities. (may involve soldering)
> >
> > http://linkstationwiki.net/index.php?title=Fan_noise
> >
> >
> > -goat
> >
> > --- In LinkStation_General@yahoogroups.com, "pstorage0001"
> > <pelachrum@> wrote:
> > >
> > > Is there a way to make this thing run more quietly???
> > >
> >
>

Here in the mailing list for buffalo,
"musikgoat" <musikgoat@...> spake unto us, saying:

>I haven't personally gone through a replacement, but I would suspect
>that they would either repair it or more likely, replace it.

I just had a fan in my 250GB LinkStation die while it was still in
warranty, so I called them, and they swapped the old unit for a new
250GB LinkStation Pro.  That was a rather nice upgrade.  :-)

--
  -Rich Steiner >>>---> http://www.visi.com/~rsteiner >>>---> Mableton, GA USA
     Mainframe/Unix bit twiddler by day, OS/2+Linux+DOS hobbyist by night.
        WARNING: I've seen FIELDATA FORTRAN V and I know how to use it!
                    The Theorem Theorem: If If, Then Then.

Whos installs openlink or freelink in their linkstation pro ?

Looking for some answers on openlink and freelink, But found that
posting on the http://forum.linkstationwiki.net/ forum is like hitting
your head against a brick wall .

Found that the Linkstation pro may have the best hardware, but the
NSLU2 has the support.

--- In LinkStation_General@yahoogroups.com, "peter224722"
<peter224722@...> wrote:
> Looking for some answers on openlink and freelink, But found that
> posting on the http://forum.linkstationwiki.net/ forum is like hitting
> your head against a brick wall .

I found it always very helpful to post there. Maybe you link here to
your posts there and then you will get the answers you need?

--- In LinkStation_General@yahoogroups.com, "haberschnasel"
<haberschnasel@...> wrote:

>
> I found it always very helpful to post there. Maybe you link here to
> your posts there and then you will get the answers you need?
>

Thank you for you help , This is my problem :-

http://forum.linkstationwiki.net/index.php?action=vthread&forum=16&topic=2349

I`m a Linux newbie who as slowly getting to know Linux, but after been
on Microsoft products since Dos takes time.

Learning bash and general Linux commands, But don`t know how to do the
more complex stuff.

Thanks again Peter

Welcome to Dependency Hell!

I tried to post this to the tread on the wiki but it looks like I
got locked out of the my account there again.  Maybe I forgot an
obscure password or something.  Anyway here is some specifics of
what might help you.  I'll follow it with some more general
background information to help you understand what is going on if
needed.

There is a command called "ldd"  (example: ldd /usr/bin/rtorrent)
which will list out all the required shared libraries (and versions)
that are required to make this program run.  Hopefully the list
won't be too long, because then you will need to verify that you
have all these, and of acceptable versions on your system.  As in
the case with your "ld.linux.so" library, sometimes you just need to
symlink the specific version you have to its more generic name.
This normally needs to be done with all shared libraries on your
system and usually a Linux with decent package management will do
this for you.  Openlink unfortunately does not have this luxury so
you have do thisyourself, probably on an as-need basis. If you don't
have the libraries at all, you'll have to find them somewhere.  I
used to grab stuff from Debian-Woody which tended to work with the
LS-1 original OS (and therefore Openlink for it), but other older
linux distributions will have these too as long as they support your
architecture's processor.

This is all a real pain, and reason I use Freelink (actually its
predecessor) instead.  Then I get to use Debians package management
system to deal with all these problems automatically.

Now for background information:

For a program to run on Linux, several "dependencies" must be met.
Not only does the program have to be compiled for the architecture
that your linux system runs on (ie PPC, MIPS, or what ever) but it
has to be compiled "against" a set of libraries that are compatible
with what is being used on the host OS.  This can really become a
tangled web.  The situation is similar, but worse to the problems
that used to exist with old Windows 3.x and all those
conflicting .dll versions (remember those horrible days?)

This is why most Linux based OS's are distributed in what is known
as "distributions", or with a set of programs that are all compiled
together to be compatible.  When you just grab a "binary" program
from somewhere else, it is a real hit-n-miss proposition as to
wheather it will work or not.

I think what is going on in your case is that the rtorrent program
was probably compiled to run on Openlink or Freelink (but not both)
and you have the opposite of what it was compiled for.  These days,
Openlink tends use a much older set of these sets of shared
libraries than Freelink, so programs compiled for one will probably
not run on the other. Another possibility is that was compiled for a
different version of Openlink, or perhaps even for the wrong
hardware.  If you can E-mail the person that put that binary on the
wiki, maybe you can compare what he/she has to what you have if
you'd like to know why it doesn't work.

If you are running Openlink, The brute force way to fix this problem
is to compile the program yourself starting with getting or creating
a "tool chain" for it.  This tends to be a lot of work IMHO, which
is why I was an early advocate of what eventually became "Freelink".

With Freelink, all you have to do is enter the command: "apt-get
install rtorrent" would download, install, and preconfigure
rtorrent.  (yes Debian has rtorrent, and about 20,000 other
precompiled program packages!).

--- In LinkStation_General@yahoogroups.com, "peter224722"
<peter224722@...> wrote:
>
> --- In LinkStation_General@yahoogroups.com, "haberschnasel"
> <haberschnasel@> wrote:
>
> >
> > I found it always very helpful to post there. Maybe you link
here to
> > your posts there and then you will get the answers you need?
> >
>
> Thank you for you help , This is my problem :-
>
>
http://forum.linkstationwiki.net/index.php?action=vthread&forum=16&topic=2349
>
> I`m a Linux newbie who as slowly getting to know Linux, but after
been
> on Microsoft products since Dos takes time.
>
> Learning bash and general Linux commands, But don`t know how to do
the
> more complex stuff.
>
> Thanks again Peter
>

If you do decide to go with freelink,  it seems that others have had
good results with rtorrent, and some other torrent utils

http://forum.linkstationwiki.net/index.php?action=vthread&forum=16&topic=2336

here's the article showing how to install it.

http://linkstationwiki.net/index.php?title=FreeLink_for_the_Linkstation_Pro

keep in mind that this is the first release, and it seems that its in
active development.

--- In LinkStation_General@yahoogroups.com, "James Stewart"

Hi James, thank you for your informative reply.
Didn't know or use the Idd command, But this is the output generated :-

   sr/lib/libtorrent.so.10)
         libncurses.so.5 => /usr/lib/libncurses.so.5 (0x40020000)
         libtorrent.so.10 => /usr/lib/libtorrent.so.10 (0x40067000)
         libsigc-2.0.so.0 => not found
         libcurl.so.3 => not found
         libgssapi_krb5.so.2 => /usr/local/lib/libgssapi_krb5.so.2
(0x40131000)
         libkrb5.so.3 => /usr/local/lib/libkrb5.so.3 (0x4014f000)
         libk5crypto.so.3 => /usr/local/lib/libk5crypto.so.3 (0x401bc000)
         libkrb5support.so.0 => /usr/local/lib/libkrb5support.so.0
(0x401e7000)
         libcom_err.so.2 => /lib/libcom_err.so.2 (0x401f2000)
         libresolv.so.2 => /lib/libresolv.so.2 (0x401fc000)
         libidn.so.11 => not found
         libdl.so.2 => /lib/libdl.so.2 (0x40217000)
         libssl.so.0.9.8 => not found
         libcrypto.so.0.9.8 => not found
         libz.so.1 => not found
         libstdc++.so.6 => /usr/local/lib/libstdc++.so.6 (0x40222000)
         libm.so.6 => /lib/libm.so.6 (0x402e8000)
         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40399000)
         libc.so.6 => /lib/libc.so.6 (0x403aa000)
         libcrypto.so.0.9.8 => not found
         libsigc-2.0.so.0 => not found
         libcom_err.so.3 => /usr/local/lib/libcom_err.so.3 (0x404c0000)

Yes, I'm 99.9% sure it was compiled for freelink and not openlink, so
it time to give up on running rtorrent on openlink. ( no real biggie )
I guess at some time I will have to install Freelink instead, but I
want to know how to dig myself out of the hole before I start digging
the hole.

Thanks again Peter

--- In LinkStation_General@yahoogroups.com, "peter224722" <peter224722@...>
wrote:
> --- In LinkStation_General@yahoogroups.com, "James Stewart"
>         libsigc-2.0.so.0 => not found
>         libcurl.so.3 => not found
>         libidn.so.11 => not found
>         libssl.so.0.9.8 => not found
>         libcrypto.so.0.9.8 => not found
>         libz.so.1 => not found
>         libcrypto.so.0.9.8 => not found
>         libsigc-2.0.so.0 => not found

Quite a few dependies.

> Yes, I'm 99.9% sure it was compiled for freelink and not openlink, so
> it time to give up on running rtorrent on openlink. ( no real biggie )

Either that, or compile your own rtorrent.

> I guess at some time I will have to install Freelink instead, but I
> want to know how to dig myself out of the hole before I start digging
> the hole.

"Compiled for FreeLink" may not be what you think though. You'll get a basic
Debian
system and identify and install such extras manually.

-Andre

--- In LinkStation_General@yahoogroups.com, "James Stewart"
<wartstew@...> wrote:
>
> Welcome to Dependency Hell!
>
> I tried to post this to the tread on the wiki but it looks like I
> got locked out of the my account there again.  Maybe I forgot an
> obscure password or something.  Anyway here is some specifics of
> what might help you.  I'll follow it with some more general
> background information to help you understand what is going on if
> needed.
>

tell me which user you have and i will reset your password.

-- mindbender
www.linkstationwiki.net

Hi, it's time where I'm thinking off replacing the Oh1jty Firmware mod
with a version of freelink for my Linkstation pro.
But checking up on a couple of things before I go ahead:-

It's said that if you can't bear the idea of having a new brick, you
shouldn't do it.

My definition of a brick is :- ( Hardware damaged, or
software/firmware totally unrepairable – or it leased by myself )

Is it true that if I don't "update boot" in debug of the update tool
I'm totally safe of bricking the Linkstation pro ( My definition ).

Eg there is a way out by removing the hard disk.

With freelink do I have to set up all the conf files myself, or is
they a web admin, just like stock, but different.


Thanks in advance Peter

Hi,

i need to mount a SMB share on my LS1 (with stock firmware and root
access). Has anyone compiled SMBMOUNT / or whatever might be
necessary for the PPC and could upload it?

Any related hints are appreciated.

Thanks in advance
Gonzo

Hi experts,

I'm trying to install u-boot on my LinkStation HG. I've got everything
working but one detail: When running u-boot as a RAM build using
uloader.o the AVR isn't initialized by either u-boot or the booted
kernel. It can't be initialized manually either. Commands sent to
it are ignored and the machine reboots after about 5 minutes.

Is this supposed to happen and will be all right once the flash build is
flashed or is something wrong with my setup? I'm reluctant to try
flashing it because I don't have a serial console or JTAG for the box.

My setup:

- current Gentoo ~ppc with glibc-2.3.6 and gcc-4.1.1
- kernel 2.6.20 ppc-based started using loader.o
- uloader.o for stock kernel 2.4.20_mvl31-ppc_linkstation compiled using
    gcc-2.95.3
- kernel 2.6.19.2 ppc-based
- kernel 2.6.20 powerpc-fdt-based
- u-boot-1.1.4 with LS patch 2.1.0
- u-boot-86xx git current with Guennadi Liakhovetski's patches

What I've tried so far:

- ppc-based kernel with u-boot-1.1.4
- powerpc-based kernel with u-boot-86xx-git
- powerpc-based kernel with u-boot-86xx-git compiled using gcc-3.4.6
- flboot of stock kernel using u-boot-86xx-git
- sending commands to different ttys (ttyS0 [no change], ttyS2 [i/o
    error])

In all cases the power led keeps blinking rapidly, commands sent to the
AVR are ignored and the machine reboots after a few minutes. Also the
minimal console using the power button doesn't work. Otherwise
everything behaves as expected: netconsole works in u-boot, loading of
uImage kernels works for ppc-based and powerpc-fdt-based kernels,
netconsole works for the kernel and the system runs normally.

I've seen that the RAM build doesn't initialise the UARTs in
early_init.S. Does this have something to do with my observations?

Any help would be greatly appreciated because this is the last obstacle
in switching to u-boot.
--
bye, Micha
I like Kaba!

On Sun, Feb 18, 2007 at 10:23:46PM +0100, Michael Weiser wrote:

> In all cases the power led keeps blinking rapidly, commands sent to the
> AVR are ignored and the machine reboots after a few minutes. Also the
> minimal console using the power button doesn't work. Otherwise

Addendum: When loading a 2.6.20 ppc-based kernel using loader.o, the avr
can be initialised manually using echo -n "[[[[" >/dev/ttyS1 and the
like. The problem seems to be uboot-specific, not hardware-related.
--
bye, Micha

Hello,

Can anyone help me finding the firmware version 1.45 or older for me
Linkstation HS-D300GL. I need run a firmware that support telnet for
installing a Slimserver software for my new Squeezebox device.


Best regards

Ulrik Skrydstrup

--- In LinkStation_General@yahoogroups.com, "ulrikskrydstrup"
<ulrikskrydstrup@...> wrote:
>
> Hello,
>
> Can anyone help me finding the firmware version 1.45 or older for me
> Linkstation HS-D300GL. I need run a firmware that support telnet for
> installing a Slimserver software for my new Squeezebox device.
>
>
> Best regards
>
> Ulrik Skrydstrup
>

you are messing up firmwares from the LS1 and the LS HS.

look at www.linkstationwiki.net

if the built-in upnp-server is not important for you (as it isn`t that
good anyway...there are better replacements like twonkyvision) then
you should convert your HS to a HG and install Openlink 0.51b
http://downloads.linkstationwiki.net/openlink/hg-openlink-051b.zip

download a HS-stock-firmware..for example this one:
http://www.unet.univie.ac.at/~a0025690/development/hs-glan_149_telnet.zip

do not flash this firmware....it is the one thing you requested...but
believe me i think you will run into issues when trying to run slimserver.

unzip both firmwares-packages....copy the firmware-updater.exe from
the hs-package to the hg-openlink package....and then update the
firmware there by executing it.

afterwards you have a full hg-openlink...installation of slimserver
should be straightforward then.

-- mindbender
www.linkstationwiki.net

Hi,

Regarding my request concerning the updating of Linkstation DST info,
I have a Linkstation v.1 (250GB).

	 --Marc

Hi,

Has anyone updated the DST info on their Linkstation? I checked
ftp://elsie.nci.nih.gov/pub/, but this doesn't appear to be current.

	 --Marc

Hi,

I'm toying around with the idea to put the OpenLink firmware on my LS.
Just wondering, if OpenLink supports user passwords longer than 8
characters (the most annoying limitation in the original firmware)?

Thanks
  - O

Hey all,

I reset and then reflashed my LS pro and now my shares are no where to
be found.  The drive still says the data is there (50% full) but I
have no idea how to find them and then reset them up.

Can anyone help?

Thanks!

--- In LinkStation_General@yahoogroups.com, "rmn1644" <rmn1644@...> wrote:
>
> Hey all,
>
> I reset and then reflashed my LS pro and now my shares are no where to
> be found.  The drive still says the data is there (50% full) but I
> have no idea how to find them and then reset them up.
>
> Can anyone help?
>
> Thanks!
>

Sound like your data is still on the internal disk ( /mnt/disk1 ) ,
but that no share are set up.

if you had shares, have you tried remaking them ?

Sounds like a Samba problem !!

all the best Peter