Mailinglist Archive: opensuse (1885 mails)

["Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Content-ID: <alpine.LSU.2.00.0904111256380.10101@xxxxxxxxxxxxxxxx>


On Saturday, 2009-04-11 at 08:19 +0200, lynn wrote:

> Phew! What is amazing is that NAS' use smb by default.

Indeed.
Instead of, or also, using ftp or nfs. After all, it is linux inside.

> What a mess. I've gone
> totally off the idea of NAS anyway. it's overpriced, low quality processor
> crippled nonsense. For less than a NAS which is any good like the dlink I can
> get a proper quiet=fan box running linux with an hdmi connector which will run
> torrent downloads, backup in the background and serve 20 home user folders.
> the NAS boxes at the same price crippled. A dlink 323 is brought to a
> standstill if you try and do more than two things at a time on it.
>
> There, I've said it!

I have a little box, overpriced, but I got it cheap, which sole purpose is 
to display terrestrial digital TV (TDT, televisón digital terrena), do 
time shift, and save recordings to a HD plugged into its USB port or via 
samba to a computer on the network. Yes, I had problems setting up samba; 
but not with the firewall, just samba itself. The firewall I figured 
myself, I have some practice. Samba is a maze to me.

Being a linux machine inside has some advantages: there is a group of 
hackers that "publish" software upgrades for the box which are actually 
better than what the seller suplies. At least I'm covered till the hackers 
dissapear and go for a shinier box and let me stuck with my "antigualla", 
hopefully years later that the manuafacturer support disapears completely.

The funny thing about these hacker types is that you have to subscribe to 
a forum in order to get the software, which is supposed to be open and 
free and gnu whatever. And I don't see their sources, even though they 
pushed the manufacturer to publish theirs (hidden somewhere in a maze of 
links in their web).


> To get back on thread, I think it's important to remind ourselves that we are
> all guessing when it comes to SuSEfirewall2. Fortunately this was a problem at
> home being forced to use samba. Had I gone for the nice little proper computer
> with a big hard disk running nfs kernel server under a well documented Linux
> distro opensuse for example none of this time wasting for me and my loyal and
> ever so patient listeners would have. . .

The firewall is more or less documented. The configuration file 
(/etc/sysconfig/SuSEfirewall2) has inside lots of comments that explains 
what each option does. Did you read it? There is also a faq, or should say 
was, because it is not mantained anymore. Here:

http://susefaq.sourceforge.net/guides/fw_manual.html

It is dated 2002, but the basics remains the same.

- -- 
Cheers,
       Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkngd3IACgkQtTMYHG2NR9UvXACcCeElLpDMPJdRyN6YjBOjnuEK
eAEAnjQhtOnE4J3C8VExXIBFa6/zwwJV
=v0Qp
-----END PGP SIGNATURE-----