Is it posssible to add the full non-open source package into open suse 10, as it is in suse 10.1? I am a newbie to linux.

Download the Suse 10.0 Eval DVD. It contains most of the Retail packages (most common ones) that also includes the Non-OSS packages such as Flash, Acrobat Reader, ect.

Durring online update you can get the NVidia Drivers as well as the MS True Type fonts. Also if you install guru and pacman you will have many many more packages not provided such as mplayer and win32codecs.

Good Luck

So i guess it is not possible, to add the Full non-open source package into open suse 10.0 like download it from the novell website?

Anyway thank you for your advice, i do have suse 10.1 on a dvd but is suse 10.0 eval more stable?

Suse 10.0 is being run on my file server because it does not have the issues that Suse 10.1 had. Novell had just remastered 10.1, but I have not installed from it yet.

Both are good distros especially used with Smart Package Manager.

If you mean software like java, acrobatreader and flashplayer, then yes, it is possible. Have a look at the online repository named inst-source-java on any opensuse mirror. Here you'll find these packages.

<mirror>/distribution/SL-10.0-OSS/inst-source-java/

What about the whole non-open source package witch is in suse 10.1,
can i download that from novells website? that was my question in the first place.

No my question was can i add the whole non-open source package into open suse 10.0, witch is build into the suse 10.1 instaler. like download it from one of the novell download servers? That was my real question but i just wrote in a way that you didnd't Understood in the first place.

Your question was answered. Please re-read this thread. If you have more questions I suggest that you go to the opensuse website at http://en.opensuse.org/Welcome_to_openSUSE.org

I hope this is not redundant...

To me, the way to think of Open Source is simply that anything you receive "open" must be kept "open". You can add "closed" components without violating the basic rule---you just cannot take any action which closes something that was open.

Pix- Yeah generally you are correct, however I would add that generally closed source is proprietary, such as NVidida Drivers. Some closed source (aka Non OSS) have defined methods of distribution. Example:

Generally NVidia & ATI require that consumers download its drivers from their website and not from Linux Distributions and mirrors.

Others such as libdvdcss (CSS for Commercial DVD I/O Read) or win32codecALL are not leagal to distribute in the US. Infact usage of these libraries and codecs violates intellectual property law in the United States. I have yet to see someone convicted for any of these, but that is why they are not included in any retail, open source, etc distribution. If Novell included them, they would surely be punished by the authorities in the United States for treaty violations.

Win32 codecs and other Microsoft Proprietary software is ONLY able to be distributed by Freespire and Linspire due to a deal made between them and Microsoft for not using the Lindows name.

Do you understand what we are saying Suse91? Either buy a retail version and add repositories or download the dvd, cd, etc and add the repositories. Either way that is the extent of what you can do with suse. If you read the liscense agreement from novell, you agree that you can make as many copies of the SuSE OS, but you can not reverse engineer, distribute an altered version using Novell or Suse images, names or trademarks. In essense unless you are to build linux from scratch, you are best to do it the way opensuse has provided. Of course you can add these "extra packages" to a DVD but you will need a lot of experience compiling an install disc and writing your own installer, not to mention a Double Layer DVD burner. Since you are a newbie, I do not think that this is the way you want to go.

You can use Yast->Software->Change installation source to add more sources like the one I posted above. They will be accessible through the normal installation module.

For more detailed instructions, check the section "Downloads->Package Repositories" from usaf_sp's link.