Linux distro on NSA325

[WarheadsSE]

And 3.11+

[WarheadsSE]

The 325 has officially been added as a part of linux-kirkwood 3.11.4-3

[SomeoneOnLine]

NICE! Thanks, For all your hard work!

~SOL

[prokrypt]

Watchdog has been neutered?
When might it appear in the repository?

[edit]
Whups, it's already in the repository! Installed and booted.
But...
$this->bbcode_second_pass_code('', '[ 0.000000] Machine: ZyXEL NSA320 2-Bay Power Media Server')
/me cries

[edit #2]
LOL I fail. I've been away from my NSA325 for so long I forgot all about the arcnumber.
My next question was "where does this arcnumber reside"? In the bootloader variables, of course!
... then, "how the heck do I change variables again?!?" ... fw_setenv!

I shall test after I get home from work.

[moonman]

did you set the right arcnumber? (4495)
http://www.arm.linux.org.uk/developer/m ... wnload.php

[WarheadsSE]

Yup, need to change the arcNumber

[anesthetic]

thanks for WarheadsSE's hardwork!!!

so when can we have installation instruction:p

[WarheadsSE]

I need to port it down to the 3.1.10 kernel, and then pull that into a new rootfs. Otherwise, moving forward it should be identical to the 320 other than the arcNumber, minus the ethernet annoyance.

[SomeoneOnLine]

What is the "ethernet annoyance" that you are referring to?

So at this point can I just use the instructions for installing Archlinux on the 320 even though I am installing it on my 325? I have data on my current raid array using factory setup. Will I lose my data if I install Archlinux on the same drive? Or should I maybe use a different set of drives just incase? Will I be able to revert back to a factory setup for in the off chance that archlinux doesnt play well or something like that? lol. I have 1TB of data that I would rather not have to lose or copy off than back on if at all possible.

~SOL

[WarheadsSE]

It will purge attempt to configure partitions and filesystems on sda, so yeah, use a bare drive, like the install says.

As for reverting, yes, there is a "to_stock" command I have in the installation of the u-boot environment, which many people have talked about prior.

The NSA320 has an annoying eth0 spinup that has not been resolved as of yet, in that you have to force on, and leave on resume-on-power enabled.