On Thu, 28 Aug 2008, Rogério Brito wrote:

> > Your model should be supported by it directly without any further patches.
> > However, I cannot verify, since I don't have this hardware.
>
> And do you know the status of the dtc thing? Does it still need to be done?

Yes, sure. You could try to use a wrapper and link the device tree with
the kernel, but this is currently not supported on LS / Kuro and I don't
know how difficult it is to configure this.

> What I find surprising is that all this knowledge is not included in the
> distributions, but scattered on some pages and to get a proper recent system
> with all security updates one has to have a quite good mental compilation of
> the state of the things.

The lack of interest and man-power?

> For instance, it one thing that was new to me was the necessity of having a
> daemon like avr_evtd (or the programs you sent me attached before).

This is platform-specific.

> Another was the need to use extra init scripts to send strings like EEEE to
> /dev/ttyS1 to get shutdown to work properly (at least with the version of the
> kernel that I still have here, which is the stock 2.4.17).

As you probably know by now, the daemons are not really _necessary_ with
recent kernels - the watchdog is switched off automatically by the kernel.

> The dtc thing was also news to me, even though I had used Linux on PowerPC for
> some time now.

First it is relatively new - since about two years, I think. Secondly, you
only need it on (ppc) systems, that don't have OF. Your Macs do have OF,
and the device tree is actually a replacement of the OF on Macs and other
machines.

> I would like to change the state of things, to have them packaged in
> systematic ways so that users (and that includes me) can only install some
> packages and forget about the differences between a Kurobox standard and a
> plain NewWorld Macintosh or a common x86 machine. That's my purpose and I
> would appreciate any help that I can get, since I know very little about this
> machine.

Well, if you have time, sure, would be nice. But just think how many
people will benefit from your work? Those ppc-based machines are not
produced any more. There are some others, I think, based on the same
CPU...

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

Hi, Guennadi.

On Aug 29 2008, Guennadi Liakhovetski wrote:
> On Thu, 28 Aug 2008, Rogério Brito wrote:
>
> > And do you know the status of the dtc thing? Does it still need to be
> > done?
>
> Yes, sure. You could try to use a wrapper and link the device tree with
> the kernel, but this is currently not supported on LS / Kuro and I don't
> know how difficult it is to configure this.

No problems. I think that I can deal with it once that I can get a recent
kernel to boot.

> > What I find surprising is that all this knowledge is not included in
> > the distributions, but scattered on some pages and to get a proper
> > recent system with all security updates one has to have a quite good
> > mental compilation of the state of the things.
>
> The lack of interest and man-power?

Well, as long as it depends on interest, I would be willing to contribute
whatever I make.

> > Another was the need to use extra init scripts to send strings like
> > EEEE to /dev/ttyS1 to get shutdown to work properly (at least with the
> > version of the kernel that I still have here, which is the stock
> > 2.4.17).
>
> As you probably know by now, the daemons are not really _necessary_ with
> recent kernels - the watchdog is switched off automatically by the
> kernel.

Now, I didn't know this. I even packaged avr_evtd and plan on getting it
into the distribution, as it would matter for the people doing work on
embedded platforms (and for projects like emdebian).

> > The dtc thing was also news to me, even though I had used Linux on
> > PowerPC for some time now.
>
> First it is relatively new - since about two years, I think. Secondly,
> you only need it on (ppc) systems, that don't have OF. Your Macs do have
> OF, and the device tree is actually a replacement of the OF on Macs and
> other machines.

Thanks. I didn't know the purpose of that information contained in a
compiled file that should be put on the side of the kernel.

> > I would like to change the state of things, to have them packaged in
> > systematic ways so that users (and that includes me) can only install
> > some packages and forget about the differences between a Kurobox
> > standard and a plain NewWorld Macintosh or a common x86 machine. That's
> > my purpose and I would appreciate any help that I can get, since I know
> > very little about this machine.
>
> Well, if you have time, sure, would be nice. But just think how many
> people will benefit from your work? Those ppc-based machines are not
> produced any more. There are some others, I think, based on the same
> CPU...

Well, the userland is simply the same as the other powerpc binaries and, as
such, I would use it for development (that's the purpose of Charles Plessy
having sent me the Kuro Box). And it would also be a learning experience
and, perhaps, this learning experience could be materialized in support for
another sub-architecture of powerpc.

Now, I would like to ask your help here. As you mentioned to me on an
earlier post, I went to some forums and wikis and consulted their
documentation, but I am still unsure of many things and I would appreciate
your help here, since you seem to be knowledgeable about these boxes.

I have, right now, a pure etch distribution (which I installed after some
painful hours without sleep) and I am using the stock firmware with the
2.4.17_kuro-box kernel and loading a self-compiled (patched) 2.6.15 kernel
with the loader.o trick (not uloader.o).

I really want to get rid of these tricks and I have a "normal" system,
with the recent kernels that I'm used to work with and to test the
distribution on the Kuro-Box.

I wrote this
http://buffalo.nas-central.org/forums/viewtopic.php?p=86166#p86166 which
gives a precompiled uBoot and a precompiled firmimg.bin with kernel
2.4.33.3.

Can you answer some of the questions that I raise there? For instance, I'm
not sure if the referenced uBoot is able to boot recent 2.6 kernels and I'm
also not sure if I need the new 2.4.33 firmimg.bin flashed in conjunction.

I just wish to get precompiled binaries first and then seeing how they are
done to incorporate whatever is needed for Debian (or, as a last resort, to
keep a private, unofficial repository of packages ready for users who want
to be completely Free, with a Free operating system).

If you have binaries already compiled that would allow me to boot a 2.6
kernel (or if other members of one of these lists have them), I would be
grateful.


Thanks for your help, Rogério Brito.

--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org

The FTP server of the stock firmware of the Linkstation Pro Duo is
such that if you use an FTP client to move files:

  * from one share or folder on the LS to another share or folder on
the LS; or
  * from one share or folder on the LS to a share or folder on an
attached USB drive (or vice versa)

The data is moved from the LS, over the network, to the pc where the
ftp client is running, back over the network were it is written to the
LS. That is *crazy*. If you use acp_commander and telnet to move the
data around, it moves at light speed, if it is only between shares or
folders on the main drive array; slightly slower if going from the
main array to usb or vice versa. I don't understand why the FTP client
doesn't instruct the FTP server just to modify the file allocation
table (or whatever the equivilant is in Linux). What takes seconds
with Telnet can take over an hour with the stock FTP client.

Is the FTP server which comes with any of the modified firmwares
(openlink, freelink, etc.) such that it would move files around the
linkstation at the same speed as Telnet does? If so, what firmware?

--- In LinkStation_General@yahoogroups.com, "g_m_s"
<graystrickland@...> wrote:
>
> The FTP server of the stock firmware of the Linkstation Pro Duo is
> such that if you use an FTP client to move files:
>
>  * from one share or folder on the LS to another share or folder on
> the LS; or
>  * from one share or folder on the LS to a share or folder on an
> attached USB drive (or vice versa)
>
> The data is moved from the LS, over the network, to the pc where the
> ftp client is running, back over the network were it is written to
the
> LS. That is *crazy*. If you use acp_commander and telnet to move the
> data around, it moves at light speed, if it is only between shares
or
> folders on the main drive array; slightly slower if going from the
> main array to usb or vice versa. I don't understand why the FTP
client
> doesn't instruct the FTP server just to modify the file allocation
> table (or whatever the equivilant is in Linux). What takes seconds
> with Telnet can take over an hour with the stock FTP client.
>
> Is the FTP server which comes with any of the modified firmwares
> (openlink, freelink, etc.) such that it would move files around the
> linkstation at the same speed as Telnet does? If so, what firmware?
>

Hello,

No, all firmwares currently support any of the common FTP server
software (predominently ProFTPd) which none support moving files from
one location on the server to another location.  FTP is a
client/server protocol, which only supports transactions from client
to server or back.  not from two different locations on the server.

Its unfortunate, as it would be a great method to move data from USB
to the local disk of the LS, but unfortunately, its not a
functionality that can be performed.

Most people suggest exactly what you've done, which is to move the
files locally through either telnet or ssh.

Hope this helps :-)
-Tim

--- In LinkStation_General@yahoogroups.com, "musikgoat"
<musikgoat@...> wrote:
> Most people suggest exactly what you've done, which is to move the
> files locally through either telnet or ssh.

I've never used SSH. Would moving files through SSH be any *easier*?
Or is using SSH merely more private/secure?

--- In LinkStation_General@yahoogroups.com, "g_m_s"
<graystrickland@...> wrote:
>
> --- In LinkStation_General@yahoogroups.com, "musikgoat"
> <musikgoat@> wrote:
> > Most people suggest exactly what you've done, which is to move the
> > files locally through either telnet or ssh.
>
> I've never used SSH. Would moving files through SSH be any *easier*?
> Or is using SSH merely more private/secure?
>
Its equivilent to telnet over a secure channel.  recommended if you
setup internet access to that process.

You wouldn't want to run telnet over the internet.

locally, it should be fine.

It involves some manipulation in the system files to run sshd at
startup, and you would have to port forward in the router for internet
access.   (use a non-default port if using from the internet, and make
sure root is not accessible for logging in from ssh.

But that would be unnecessary for a once-in-a-while file manipulation
process.

Hi Rogério,

and sorry for the delay.

On Mon, 1 Sep 2008, Rogério Brito wrote:

> > > I would like to change the state of things, to have them packaged in
> > > systematic ways so that users (and that includes me) can only install
> > > some packages and forget about the differences between a Kurobox
> > > standard and a plain NewWorld Macintosh or a common x86 machine. That's
> > > my purpose and I would appreciate any help that I can get, since I know
> > > very little about this machine.
> >
> > Well, if you have time, sure, would be nice. But just think how many
> > people will benefit from your work? Those ppc-based machines are not
> > produced any more. There are some others, I think, based on the same
> > CPU...
>
> Well, the userland is simply the same as the other powerpc binaries and, as
> such, I would use it for development (that's the purpose of Charles Plessy
> having sent me the Kuro Box). And it would also be a learning experience
> and, perhaps, this learning experience could be materialized in support for
> another sub-architecture of powerpc.
>
> Now, I would like to ask your help here. As you mentioned to me on an
> earlier post, I went to some forums and wikis and consulted their
> documentation, but I am still unsure of many things and I would appreciate
> your help here, since you seem to be knowledgeable about these boxes.
>
> I have, right now, a pure etch distribution (which I installed after some
> painful hours without sleep) and I am using the stock firmware with the
> 2.4.17_kuro-box kernel and loading a self-compiled (patched) 2.6.15 kernel
> with the loader.o trick (not uloader.o).
>
> I really want to get rid of these tricks and I have a "normal" system,
> with the recent kernels that I'm used to work with and to test the
> distribution on the Kuro-Box.
>
> I wrote this
> http://buffalo.nas-central.org/forums/viewtopic.php?p=86166#p86166 which
> gives a precompiled uBoot and a precompiled firmimg.bin with kernel
> 2.4.33.3.
>
> Can you answer some of the questions that I raise there? For instance, I'm
> not sure if the referenced uBoot is able to boot recent 2.6 kernels and I'm
> also not sure if I need the new 2.4.33 firmimg.bin flashed in conjunction.
>
> I just wish to get precompiled binaries first and then seeing how they are
> done to incorporate whatever is needed for Debian (or, as a last resort, to
> keep a private, unofficial repository of packages ready for users who want
> to be completely Free, with a Free operating system).
>
> If you have binaries already compiled that would allow me to boot a 2.6
> kernel (or if other members of one of these lists have them), I would be
> grateful.

I looked through the thread in the forum. I didn't quite understand, in
one your post you write: "I have some problems with the precompiled uboot
image that I am using" - does this mean that you have flashed the
precompiled u-boot?

I am not sure whether it (version 1.2.0-r2, no idea what "-r2" means) can
handle the Flat Device Tree. This version does already support FDT, but I
do not know how this specific binary was compiled. If you have already
flashed it, just do "help bootm" in u-boot prompt. If it only describes
two parameters - kernel and initrd - bad luck. If it describes three
parameters - you are set up to boot a modern kernel.

Unfortunately, I don't think I am going to be very helpful to you.
Firstly, I have no access to HD systems to test stuff, that's why the
current U-Boot does not support them. Secondly, I don't have much free
time ATM, so, even email replies might be delayed. Otherwise I will be
glad to provide you with any information I have, just ask on mailing lists
as you have done until now. I don't follow forums, so, don't expect me to
answer there.

As for your target to support PPC LS / Kurobox systems in stock Debian, I
think, the best way to do this would be:

1. get the current u-boot version ported to your hardware and merged into
U-Boot mainline;

2. build and test a current kernel and fdt - you should not need any
development for this, everything is already in the mainline kernel;

* These two steps should let you run a current Debian distribution on your
machine - note, you don't necessarily need any AVR daemon, already at this
point you should have a fully functional Debian system.

3. (optional) think about a user-space daemon to handle the AVR chip.
Don't just get avr_evtd because you know it and it seems to work, think
about what functionality you really need from such a daemon and how one
best should implement it. I know I am subjective, but I think, my two
sample programmes I've sent you go in the right direction. Do not install
any custom init-scripts and do not try to programme yet another boot /
reboot / shutdown subsystem. Instead, integrate with existing software,
just interface the AVR with standard packages. For example, when the
reboot button has been pressed, do not spawn a reboot process directly,
instead, just provide a "reboot button pressed" event to the system and
let the user configure a desired action using standard mechanisms.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

Hi, Guennadi.

On 07/09/2008, at 16:35, Guennadi Liakhovetski wrote:
> and sorry for the delay.

No problems. I'm also not able to keep up with my mails. :-) And,
BTW, I've been getting more successful regarding the Kurobox.

> On Mon, 1 Sep 2008, Rogério Brito wrote:
>> I wrote this
>> http://buffalo.nas-central.org/forums/viewtopic.php?p=86166#p86166
>> which
>> gives a precompiled uBoot and a precompiled firmimg.bin with kernel
>> 2.4.33.3.
>>
>> Can you answer some of the questions that I raise there? For
>> instance, I'm
>> not sure if the referenced uBoot is able to boot recent 2.6
>> kernels and I'm
>> also not sure if I need the new 2.4.33 firmimg.bin flashed in
>> conjunction.

Just for further reference for the mailing lists, I own a standard
Kurobox and I'm able to use my own compiled 2.6.27-rc5 kernel on the
Kurobox (which guarantees me that I'm not going to get bitten by a
glibc requirement on the kernel version being too high). At least not
now. :-)

I'm now using software which is completely free on my system (and
this can also be added to the Debian Wiki as a sucessful report of a
current installation that went well, even if I have not followed the
use of d-i, which does not exist at the moment).

This also serves as a report that the vanilla kernel is able to work
well with the standard Kurobox (I seem to recall that you stated only
that it was tested with a Kurobox HG, right?).

I can share the precompiled uboot kernel (as a Debian package) that
I'm using with the Kurobox. For the purposes of this, I have used my
own homebrew cross-toolchain (from x86-64 to powerpc). It has worked
very well for me for compiling the kernels for my weaker powerpc boxes.

>> If you have binaries already compiled that would allow me to boot
>> a 2.6
>> kernel (or if other members of one of these lists have them), I
>> would be
>> grateful.
>
> I looked through the thread in the forum. I didn't quite
> understand, in
> one your post you write: "I have some problems with the precompiled
> uboot
> image that I am using" - does this mean that you have flashed the
> precompiled u-boot?

Yes, it does. Now, when I have some time, I will try to compile a
newer uboot and flash it.

> I am not sure whether it (version 1.2.0-r2, no idea what "-r2"
> means) can
> handle the Flat Device Tree. This version does already support FDT,
> but I

Do you mean the dtb files? Yes, it does.

> do not know how this specific binary was compiled. If you have already
> flashed it, just do "help bootm" in u-boot prompt. If it only
> describes
> two parameters - kernel and initrd - bad luck. If it describes three
> parameters - you are set up to boot a modern kernel.

Interestingly enough, I can't get the uboot netconsole, even though I
*can* boot into EM-mode for rescuing my box (but I guess that now
that I'm with a working kernel, I will rarely need to use such EM-
mode tools).

I think that I will also try to flash that initrd with a newer
kernel, but this can wait until I get more information. It's been a
quite good learning exercise to get all these things together.

> Unfortunately, I don't think I am going to be very helpful to you.
> Firstly, I have no access to HD systems to test stuff, that's why the
> current U-Boot does not support them.

Are you upstream for uboot? Upstram for any project involved?

> Otherwise I will be
> glad to provide you with any information I have, just ask on
> mailing lists
> as you have done until now. I don't follow forums, so, don't expect
> me to
> answer there.

Neither I like to use forums. I prefer the facilities of using
mailing lists (procmail is my friend here).

> As for your target to support PPC LS / Kurobox systems in stock
> Debian, I
> think, the best way to do this would be:
>
> 1. get the current u-boot version ported to your hardware and
> merged into
> U-Boot mainline;

I guess that it already is, but I will check if the current uboot
that I'm using is patched or not.

> 2. build and test a current kernel and fdt - you should not need any
> development for this, everything is already in the mainline kernel;

Done and working fine. And I even reported a bug to linuxppc-dev, but
it was an already known issue. :-)

> * These two steps should let you run a current Debian distribution
> on your
> machine - note, you don't necessarily need any AVR daemon, already
> at this
> point you should have a fully functional Debian system.

Yes, that's were I am.

> 3. (optional) think about a user-space daemon to handle the AVR chip.
> Don't just get avr_evtd because you know it and it seems to work,
> think
> about what functionality you really need from such a daemon and how
> one
> best should implement it.

I seem to understand that you don't like the implementation of
avr_evtd, right?

Well, I also found some bugs on the code (see my package of it at
<http://mentors.debian.net/debian/pool/main/a/avr-evtd/>, in
particular, my patch).

> I know I am subjective, but I think, my two
> sample programmes I've sent you go in the right direction.

Yes, they are small and to the point. I think that I may use them
(and even package them, if I happen to use them). I would only hope
for them to be slightly better documented.

> Instead, integrate with existing software,
> just interface the AVR with standard packages. For example, when the
> reboot button has been pressed, do not spawn a reboot process
> directly,
> instead, just provide a "reboot button pressed" event to the system
> and
> let the user configure a desired action using standard mechanisms.

Yes, using that way, things could be integrated with udev, I think
(sorry if I'm way off here).


Regards, Rogério Brito.

--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org

Hi

On Wed, 10 Sep 2008, Rogério Brito wrote:

> Just for further reference for the mailing lists, I own a standard Kurobox and
> I'm able to use my own compiled 2.6.27-rc5 kernel on the Kurobox (which
> guarantees me that I'm not going to get bitten by a glibc requirement on the
> kernel version being too high). At least not now. :-)
>
> I'm now using software which is completely free on my system (and this can
> also be added to the Debian Wiki as a sucessful report of a current
> installation that went well, even if I have not followed the use of d-i, which
> does not exist at the moment).

Good work!

> This also serves as a report that the vanilla kernel is able to work well with
> the standard Kurobox (I seem to recall that you stated only that it was tested
> with a Kurobox HG, right?).

No, not quite. It has also been tested by someonr from the LS-community on
a HD system, but that was a few kernel releases back. Good to know it
still works:-)

> > I looked through the thread in the forum. I didn't quite understand, in
> > one your post you write: "I have some problems with the precompiled uboot
> > image that I am using" - does this mean that you have flashed the
> > precompiled u-boot?
>
> Yes, it does. Now, when I have some time, I will try to compile a newer uboot
> and flash it.

Wow, brave man... But see below.

> > do not know how this specific binary was compiled. If you have already
> > flashed it, just do "help bootm" in u-boot prompt. If it only describes
> > two parameters - kernel and initrd - bad luck. If it describes three
> > parameters - you are set up to boot a modern kernel.
>
> Interestingly enough, I can't get the uboot netconsole, even though I *can*
> boot into EM-mode for rescuing my box (but I guess that now that I'm with a
> working kernel, I will rarely need to use such EM-mode tools).

Your U-Boot probably uses some network addresses incompatible with your
setup. Try to connect it to your PC directly with a crossover cable, or
over a hub (not switch) and try to sniff the trafic, then you'll get
IP-addresses it uses.

> > Unfortunately, I don't think I am going to be very helpful to you.
> > Firstly, I have no access to HD systems to test stuff, that's why the
> > current U-Boot does not support them.
>
> Are you upstream for uboot? Upstram for any project involved?

Sorry, do not understand. What do you mean "_I_ am upstream?" I am
developing as well for U-Boot as for the kernel, also for other platforms,
and my patches do get "upstream" from time to time, yes. Yoou can just do
"git log" and then search for any name you like:-)

> > 1. get the current u-boot version ported to your hardware and merged into
> > U-Boot mainline;
>
> I guess that it already is, but I will check if the current uboot that I'm
> using is patched or not.

No, it is not. I did include rudimentary support for HD into the U-Boot
patch that went upstream, but it is currently broken. Someone with Jtag
and suitable developer skills has to fix it. The binary you've got is
produced from patched sources, and that patch has no chance to get
upstream in that form.

> > 3. (optional) think about a user-space daemon to handle the AVR chip.
> > Don't just get avr_evtd because you know it and it seems to work, think
> > about what functionality you really need from such a daemon and how one
> > best should implement it.
>
> I seem to understand that you don't like the implementation of avr_evtd,
> right?

Well, I am not specifically emotional about it:-) I just preferred another
solution.

> > I know I am subjective, but I think, my two
> > sample programmes I've sent you go in the right direction.
>
> Yes, they are small and to the point. I think that I may use them (and even
> package them, if I happen to use them). I would only hope for them to be
> slightly better documented.

As I said, they are just "examples." In particular, you should not neet
the ipowerd power daemon, I hope, one can find and use a standard GNU /
Debian application that can be configured to do the same - control system
power states depending on keyboard events. This part should be platform
independent. Whereas buttond is actually the system-dependent part. It
performs communication with the AVR controller, installed only on a couple
of Buffalo systems and using their proprietory protocol.

> > Instead, integrate with existing software,
> > just interface the AVR with standard packages. For example, when the
> > reboot button has been pressed, do not spawn a reboot process directly,
> > instead, just provide a "reboot button pressed" event to the system and
> > let the user configure a desired action using standard mechanisms.
>
> Yes, using that way, things could be integrated with udev, I think (sorry if
> I'm way off here).

No, you are not. I am using udev to launch both thoes daemons (I think). I
can look up my udev rules for you if you want. And it's the ipowerd that
should be replaced with a more generic standard tool, I hope.

Would also be nice to teach buttond more operations, like controlling the
watchdog, LEDs, the fan, the eth PHY, etc. - if anyone wants those.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

--- In LinkStation_General@yahoogroups.com, "Gary Smith" <gary@...>
wrote:
>
> Is there anyway to check the speed at which my Linkstaiton is
working. Its
> the original *HD-HGLAN
> (HG)*<http://buffalo.nas-central.org/index.php/Category:HG> model.
>
>
> Data Transfer speed seems at times to be very very slow. I've
rebooted the
> Linkstation but this doesnt seem to have helped. I don't use the
USB printer
> option - which I had seen somewhere may cause problems.
>
> I've recently added a 1TB Drive Station to the USB port and moving
data from
> the LinkStation to the DriveStation is taking for ever.
>
> Any advice would be much appreciated.
>
> Thanks
>

I cannot attest to the transfer speeds of the unit (I've read arount
7Mbps, but I don't know), however I think that your issue with
transfers from the Linkstation to the USB drivestation are slow
because you are initiating the request from your PC.

I am assuming what you are doing is opening a windows explorer view
of your Linkstation and copying that data to a windows explorer view
of the drivestation.

If so, the data is transferring from the Linkstation, to your
machine, then to the drivestation.  This happens because Samba/CIFS
does not support direct file movement between different samba shares
on the server.

In my opinion, if you want to achieve quick transfers from the
Linkstation to your usb drivestation,  you should gain telnet access
to the device, and initiate the movement of data from inside the
linkstation.

If you are intending to perform backups instead, from the linkstation
to the drivestation, then setting up rsync in the device would be
suggested (again through a telnet session).

More information can be found on this page, http://buffalo.nas-
central.org/index.php/Category:OpenLink
which discusses installing the firmware with telnet support.
But caution with the HG, there is a series that was prone to
bricking, so see this page as well.
http://buffalo.nas-central.org/index.php/Non_Flashable_HD-HG300

Hope this helps

Hi, Gary.

--- In LinkStation_General@yahoogroups.com, "Gary Smith" <gary@...>
wrote:
> Is there anyway to check the speed at which my Linkstaiton is
> working. Its
> the original *HD-HGLAN
> (HG)*<http://buffalo.nas-central.org/index.php/Category:HG> model.

I don't know how you're using your Linkstation. On my "pure Debian"
standard kurobox, I have many  utilities which I installed and one of
them is mii-tool (I'm a die-hard Unix user).

If you don't have this one, ethtool is also able to tell you with
which speed you're connected and if you're using full duplex or not.


Hope this helps, Rogério Brito.

--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org

--- In LinkStation_General@yahoogroups.com, "musikgoat"
<musikgoat@...> wrote:
> In my opinion, if you want to achieve quick transfers from the
> Linkstation to your usb drivestation,  you should gain telnet access
> to the device, and initiate the movement of data from inside the
> linkstation.

To expand a tiny bit on what MusikGoat wrote, you need to download
ACP_COMMANDER from SourceForge. It's a Java applet. You run it from a
DOS/Windows command prompt. This unlocks Telnet on the Linkstation.
You usually only have to run acp_commander once (until your LS is next
rebooted). Before running it, you must turn off your PC's firewall, or
modify your firewall to open the correct ports. I find it easier to
just turn off the f/w while running telnet.

After acp_commander says you can get into your LS, you run Telnet [ip
address of LS] at a command prompt on your pc. Then you can move files
between folders and shares of the LS. Here are a few things you may
need to know if you're not familiar with Linux.

LS command is like "dir" command in Dos/Windows

LS -l gives a detailed listing

If you just type "ls" at a prompt, you won't appear to get anything,
because you're above the root. "ls /" will give you the contents of
the root. "ls /mnt/" will give you the volumes of drives. If your LS
has raid, "ls /mnt/array1" lists the contents of the raid
array. "ls /mnt/usbdisk1" lists contents of usb disk one.

CP command is like "xcopy" in Dos/Windows

CHMOD lets you modify permissions on files and folders.
*EVERYTHING* in Linux is case sensitive, so wear a motorcycle helmet
if you dont' want to pull out all your hair in frustration

I can move about 20gb of stuff from usb to main array in about 5
minutes. Using Windows explorer, it could take over a half hour.

I'm still a noob at Linkstations and Linux, so ask guru's like
Musikgoat for specific details.

--- In LinkStation_General@yahoogroups.com, "sheller185"
<sheller185@...> wrote:
>
> ok what i am really looking to do is network my linkstation live
> online. my friend is going to iraq in the army. he is allowed to bring
> a laptop and will have internet accesss, but he cannot have anything
> stored on his harddrive. i wanted to be able to allow him access to a
> mapped drive to store information and media so that he has something
> to do while he is out there. this will also allow him to send back
> videos of what he is doing out there. i was trying to research hamachi
> and have been unable to get it to work, are there any other solutions
> to my problem? i know a vpn might work but i am not very familiar with
> them. thank you in advance.
> -steve

Well first, the DOD is making those restrictions precisely to prevent
him from doing things like this.

regardless the newest LS Live firmware has a Shared web access feature
http://www.buffalotech.com/technology/our-technology/web-access/

I don't know if it's secured in the same way that OpenVPN (or even
PoPToP) would be but it would probably be the easiest way.  At some
point depending on data movement, the website/IP that you end up using
may end up being blocked (corporations do this all the time when they
see large data flows to unknown IP/servers)

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the LinkStation_General
group.

   File        : /8usb.tgz
   Uploaded by : paules_p <paules_p@...>
   Description : Expand Linkstation Pro to 8 USB Drives (Fw 1.11a,1.12a)

You can access this file at the URL:
http://groups.yahoo.com/group/LinkStation_General/files/8usb.tgz

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/l/us/yahoo/groups/original/members/web/index.htmlfiles

Regards,

paules_p <paules_p@...>

Sorry to ask but but am I missing something?

I have just bought a 1Tb new verion linkstation live  the LS-CH1.0TL
that is supposed according to the box be fully compatible with Itunes
and the Iphone.

Thing is after going through 70 pages of instructions (twice just
incase I missed it the first time) I have found no details on how to
link itunes or the iphone to this NAS.

If buffalo are advertising the feature I would have expected the
instructions or the website at least to have something about it but
no...

If I wanted to just map a drive and dump my music on it I could saved
a load of money and bought something else.

As you might have gathered I'm less than impressed with this thing.

If I have missed the instrucions then just tell me where and I will
go hang my head in shame and sit in the naughty corner....

--- In LinkStation_General@yahoogroups.com, "davideastaugh"
<davideastaugh@...> wrote:
>
> Sorry to ask but but am I missing something?
>
> I have just bought a 1Tb new verion linkstation live  the LS-CH1.0TL
> that is supposed according to the box be fully compatible with
Itunes
> and the Iphone.
>
> Thing is after going through 70 pages of instructions (twice just
> incase I missed it the first time) I have found no details on how to
> link itunes or the iphone to this NAS.
>
> If buffalo are advertising the feature I would have expected the
> instructions or the website at least to have something about it but
> no...
>
> If I wanted to just map a drive and dump my music on it I could
saved
> a load of money and bought something else.
>
> As you might have gathered I'm less than impressed with this thing.
>
> If I have missed the instrucions then just tell me where and I will
> go hang my head in shame and sit in the naughty corner....
>

Hi,

I don't know if you are missing anything in particular, but if there
are references to dlna server, then you may want to try turning that
on.  it could be tied to the itunes server (same on switch or
something).

I would suggest visiting the nas-central forums, if you haven't
already, there is a thread in there:  http://buffalo.nas-
central.org/forums/viewtopic.php?f=37&t=11391

gl

the harddrive of my hd-hg400lan went bad and I have to replace it. Can
some one tell me how to install the new drive. What type of programs I
have to install, formatting, partitioning, etc.  Any information will
be appreciated. Thanks

--- In LinkStation_General@yahoogroups.com, "alphaomegared35"
<alphaomegared35@...>
wrote:
>
> the harddrive of my hd-hg400lan went bad and I have to replace it. Can
> some one tell me how to install the new drive. What type of programs I
> have to install, formatting, partitioning, etc.  Any information will
> be appreciated. Thanks

The new HDD must be unpartitioned. Flash the firmware twice. The first run will
create the
partitions etc., the second the 'visible part'.

-A

--- In LinkStation_General@yahoogroups.com, "lalunas10"
<lalunas10@...> wrote:
>
> --- In LinkStation_General@yahoogroups.com, "alphaomegared35"
<alphaomegared35@>
> wrote:
> >
> > the harddrive of my hd-hg400lan went bad and I have to replace it. Can
> > some one tell me how to install the new drive. What type of programs I
> > have to install, formatting, partitioning, etc.  Any information will
> > be appreciated. Thanks
>
> The new HDD must be unpartitioned. Flash the firmware twice. The
first run will create the
> partitions etc., the second the 'visible part'.
>
> -A

Thank YOu for the info, I did the firmware and it did created
everything just like you said. I just ran into a problem during the
procedure, the drive froze and the "DISK FULL" light came one...and a
message popped out that "firmware installation failed". I tried to
access the drive through the ip address and no luck. Does the firmware
installs the web interface too? What can be the problem?

Thanks in advance...
>

--- In LinkStation_General@yahoogroups.com, "alphaomegared35"
<alphaomegared35@...> wrote:
>
> --- In LinkStation_General@yahoogroups.com, "lalunas10"
> <lalunas10@> wrote:
> >
> > --- In LinkStation_General@yahoogroups.com, "alphaomegared35"
> <alphaomegared35@>
> > wrote:
> > >
> > > the harddrive of my hd-hg400lan went bad and I have to replace
it. Can
> > > some one tell me how to install the new drive. What type of
programs I
> > > have to install, formatting, partitioning, etc.  Any information
will
> > > be appreciated. Thanks
> >
> > The new HDD must be unpartitioned. Flash the firmware twice. The
> first run will create the
> > partitions etc., the second the 'visible part'.
> >
> > -A
>
> Thank YOu for the info, I did the firmware and it did created
> everything just like you said. I just ran into a problem during the
> procedure, the drive froze and the "DISK FULL" light came one...and a
> message popped out that "firmware installation failed". I tried to
> access the drive through the ip address and no luck. Does the firmware
> installs the web interface too? What can be the problem?
>
> Thanks in advance...
> >
>

What kind of hard drive did you replace it with.

The first flashing of the firmware should fail.   THen you want to run
the updater again, and it should install the web interface and all the
software to make it run.

What exactly have you done thus far?

Does anyone know what has happened to the nas-central.org site? The
site is a great resource for Linkstation/Kurobox information and it
has been down for at least 24 hours, maybe longer.

If you know what's going on, please let us know. Thanks!

The internal HDD on my 4-year-old Linkstation is > 90% full, and I think
a 4 year old HDD needs replacing anyway, so the magic question is: what
is the largest HDD anyone has successfully put in one of these? Sure I
could go USB, but the unit is slow enough. I could out and out replace
it with a larger NAS, but I want to see if it's practical to upgrade
rather than replace.

--- In LinkStation_General@yahoogroups.com, "gigabit_speed"
<dlowther@...> wrote:
>
> Does anyone know what has happened to the nas-central.org site? The
> site is a great resource for Linkstation/Kurobox information and it
> has been down for at least 24 hours, maybe longer.
>
> If you know what's going on, please let us know. Thanks!
>
The administrators are currently working on the problem.  It started
small, but it looks like it was going to take longer than expected.

I'm sure it will be back up soon, nothing to worry about.

The nas-central site appears to be down for the last couple of days and
I was wanting to install Twonky this weekend.

--- In LinkStation_General@yahoogroups.com, Brian Cowan <brcowan@...>
wrote:
>
> The internal HDD on my 4-year-old Linkstation is > 90% full, and I
think
> a 4 year old HDD needs replacing anyway, so the magic question is:
what
> is the largest HDD anyone has successfully put in one of these? Sure I
> could go USB, but the unit is slow enough. I could out and out replace
> it with a larger NAS, but I want to see if it's practical to upgrade
> rather than replace.
>

I recently upgraded my LinkStation V1 with a 500GB Samsung IDE drive
without problem if that's of any help. If you're going to open up the
unit, after 4 years, you might want to replace the cooling fan at the
same time if that's getting noisy.

--- In LinkStation_General@yahoogroups.com, "musikgoat"
<musikgoat@...> wrote:
>
> --- In LinkStation_General@yahoogroups.com, "alphaomegared35"
> <alphaomegared35@> wrote:
> >
> > --- In LinkStation_General@yahoogroups.com, "lalunas10"
> > <lalunas10@> wrote:
> > >
> > > --- In LinkStation_General@yahoogroups.com, "alphaomegared35"
> > <alphaomegared35@>
> > > wrote:
> > > >
> > > > the harddrive of my hd-hg400lan went bad and I have to replace
> it. Can
> > > > some one tell me how to install the new drive. What type of
> programs I
> > > > have to install, formatting, partitioning, etc.  Any information
> will
> > > > be appreciated. Thanks
> > >
> > > The new HDD must be unpartitioned. Flash the firmware twice. The
> > first run will create the
> > > partitions etc., the second the 'visible part'.
> > >
> > > -A
> >
> > Thank YOu for the info, I did the firmware and it did created
> > everything just like you said. I just ran into a problem during the
> > procedure, the drive froze and the "DISK FULL" light came one...and a
> > message popped out that "firmware installation failed". I tried to
> > access the drive through the ip address and no luck. Does the firmware
> > installs the web interface too? What can be the problem?
> >
> > Thanks in advance...
> > >
> >
>
> What kind of hard drive did you replace it with.
>
> The first flashing of the firmware should fail.   THen you want to run
> the updater again, and it should install the web interface and all the
> software to make it run.
>
> What exactly have you done thus far?


Sorry for the delay but I was kind of busy this week.
I installed the hardrive ran the hd-hglan firmware updater, it runs
but at the end gives a msg "attempt ti renew firmware has failed"
i run it again and it those the same thing. I ran another utility that
gave me the same info as the ip utility, but it had a massege that
indicated that the hardrive was not formatted. If I cant do it through
the firmware updater, what program should I use to format the drive.

--- In LinkStation_General@yahoogroups.com, "musikgoat"
<musikgoat@...> wrote:
>
> --- In LinkStation_General@yahoogroups.com, "alphaomegared35"
> <alphaomegared35@> wrote:
> >
> > --- In LinkStation_General@yahoogroups.com, "lalunas10"
> > <lalunas10@> wrote:
> > >
> > > --- In LinkStation_General@yahoogroups.com, "alphaomegared35"
> > <alphaomegared35@>
> > > wrote:
> > > >
> > > > the harddrive of my hd-hg400lan went bad and I have to replace
> it. Can
> > > > some one tell me how to install the new drive. What type of
> programs I
> > > > have to install, formatting, partitioning, etc.  Any information
> will
> > > > be appreciated. Thanks
> > >
> > > The new HDD must be unpartitioned. Flash the firmware twice. The
> > first run will create the
> > > partitions etc., the second the 'visible part'.
> > >
> > > -A
> >
> > Thank YOu for the info, I did the firmware and it did created
> > everything just like you said. I just ran into a problem during the
> > procedure, the drive froze and the "DISK FULL" light came one...and a
> > message popped out that "firmware installation failed". I tried to
> > access the drive through the ip address and no luck. Does the firmware
> > installs the web interface too? What can be the problem?
> >
> > Thanks in advance...
> > >
> >
>
> What kind of hard drive did you replace it with.
>
> The first flashing of the firmware should fail.   THen you want to run
> the updater again, and it should install the web interface and all the
> software to make it run.
>
> What exactly have you done thus far?
>
I forgot to mentioned that when I get the error the "disk Ful"and the
"Diag" ligths start flashing...

tim and myself(mindbender) are aware of the problem.

check back later this week, it might take some time to get all
services from nas-central.org up and running again.


--- In LinkStation_General@yahoogroups.com, "musikgoat"
<musikgoat@...> wrote:
>
> --- In LinkStation_General@yahoogroups.com, "gigabit_speed"
> <dlowther@> wrote:
> >
> > Does anyone know what has happened to the nas-central.org site? The
> > site is a great resource for Linkstation/Kurobox information and it
> > has been down for at least 24 hours, maybe longer.
> >
> > If you know what's going on, please let us know. Thanks!
> >
> The administrators are currently working on the problem.  It started
> small, but it looks like it was going to take longer than expected.
>
> I'm sure it will be back up soon, nothing to worry about.
>

Hi,

since nas-central.org is down an I've running unfs with performance
problems I must change to kernel nfs.
I hove anybody here can give me the nesasary Infos and files to do it.


Thanks

Frank