I just installed opensuse 11.2 on my laptop, dualboot with Win 7.
I have now installed wireless drivers (wl), and are up’n’go on wireless internet.
VLC is also taken care of, so I can watch my DVDs on the train
As soon as I locate drivers for my wireless Epson Stylus Office BX600FW printer, I am good to go (have found the rpm for the driver, and will install it later on, with Zypper or something).
The last thing is to learn myself to set up file sharing between mey windows boxes and the coming linux boxes - I’ll manage, I am sure.
I read the forums carefully before doing anything…
The point of this posting?
Nothing, except to say I really like openSUSE, especially the forums (which offer tremendous help)!!!
I am pretty sure I’ll convert all my machines (there’s 5 of them) to openSUSE, except one dualboot machine (to play games on).
The thing that messes up most users here (in my experience) is they mess up the firewall on the MS-Windows boxes, and then they blaime Linux because they do not understand Linux.
I have not done this for a while, but with KDE I used to use Konqueror to do this. I would get the IP address of the MS-Windows PC, and then I would type in konqueror’s location bar:
smb://user@ip-address-of-windows-pc
or
smb://ip-address-of-windows-pc
and assuming the MS-Windows firewall is setup correctly, one had access.
One can also set up a samba network for a more integrated setup, but I can never be bothered to do that.
Edit: for windows PCs to access Linux PCs, I would use the windows program WinSCP (if I recall correctly). On the Linux PC one has to open up port#22 and also activate the ssh server daemon.
Yep, that was how it was set up when I used to have win- only pc. For a home- grown peer network samba seems like an overkill and Winscp offers a no-frill setup…
There are many Linux-es to choose from. Glad you’re happy with openSUSE. It’s one of the more popular ones.
If you’re going to set up file and/or print sharing between the window boxes and the Linux box/es, I recommend the full deal with Samba [unlike my colleague oldcpu ;)], but hey, “to each his own”.
