[SOLVED]Problems with symlinks

[JayM]

First of all, thank you for a wonderful product.

I've been implementing the OPSI solution in my institution for a few weeks now, with success. But now I've come up to a problem regarding symlinks. I'll try to explain:

Taking the example of Windows 7 OS, we need to have some different distributions (Volume Licensing, MSDNAA, EN language and PT language).

For what I learned, I may have only one "main" product, and symlink the "winpe", "installfiles" and "drivers" directories of the other products to the same directories on the "main" product.

With the "winpe"and "installfiles", it works flawlessly. But if I symlink the "drivers" directory, I get into a loop when creating the product with opsi-makeproductfile. It keeps on building an endless <productname>.opsi file, and I have to cancel the process or else it would eat up all disk space.

What am I doing wrong? What is the correct way to symlink the "drivers" folder?

Thanks in advance.

[n.wenselowski]

Hello JayM,

we ourselfs are using a symlinked drivers directory.
Please try running opsi-makeproductfile with -h.

If this does not solve the problem for you please run it with -v and post your output.


Kind regards

Niko

[JayM]

I forgot to mention (it may be important), that I'm using the driverpacks from driverpacks.net, and I've run the script "create_driver_links.py" on the "main" product.

[n.wenselowski]

Hello JayM,

did you try what I suggested earlier?


Kind regards

Niko

[ueluekmen]

Hi,

Have you linked drivers directory in the root of the product? If you have, don't do it.

Only link drivers/drivers, NEVER drivers directly. But you must execute create_driver_links in any package.

[JayM]

OK, first of all, thank you all for your suggestions, they were very helpfull.

Here's what I did:

First, let me try to explain my first method of approach (the one that didn't work). I was creating a new win7 package from the existing one, and then I created the symlinks on the /home/opsipruducts folder. Just AFTER that I was creating the package, with opsi-makeproductfile. That resulted in the loop I mentioned earlier.

What I did next, and it worked flawlessly, was creating a new win7 package from the existing one, making the product file and installing the product. Only AFTER that I created the symlinks in the /opt/pcbin/install/win7_xxx folder.

It worked like a charm.

Thanks again