userspace:howto_use_the_scripts_-_a_short_description
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
userspace:howto_use_the_scripts_-_a_short_description [2011/12/16 13:12] Thomas_H |
userspace:howto_use_the_scripts_-_a_short_description [2021/08/23 08:37] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== ...use the listed scripts ===== | ===== ...use the listed scripts ===== | ||
| - | written by // | + | written by // |
| + | edited by // | ||
| Welcome to the wiki, initiated by users using opsi very proudly and successful. If you want to use Opsi (**O**pen **P**C **S**erver **I**ntegration) be aware, that this system is - like many other servers - none "out of the box". So get rid of any illusion, that you simply install opsi and right after installing you can install every software and operating system. Some work has to be done before you can do this! And nevertheless there are very(!) good instructions and manuals for opsi it's your's to create the most contents and packages for future installations. | Welcome to the wiki, initiated by users using opsi very proudly and successful. If you want to use Opsi (**O**pen **P**C **S**erver **I**ntegration) be aware, that this system is - like many other servers - none "out of the box". So get rid of any illusion, that you simply install opsi and right after installing you can install every software and operating system. Some work has to be done before you can do this! And nevertheless there are very(!) good instructions and manuals for opsi it's your's to create the most contents and packages for future installations. | ||
| Line 9: | Line 10: | ||
| This wiki shall help to avoid much work to be done twice, because once a package is created successfully, | This wiki shall help to avoid much work to be done twice, because once a package is created successfully, | ||
| - | This Howto is mostly | + | This Howto is for the newbies |
| - | Of course: best is at last to get some training, you can get informations about training on opsi [[http://www.opsi.org/ | + | Of course: best is at last to get some training, you can get informations about training on opsi [[https://uib.de/en/support-training/ |
| ==== Some words before beginning... ==== | ==== Some words before beginning... ==== | ||
| - | * Read the manuals! We expect that you already have installed and configured your opsi-server on the manual named " | + | * Read the manuals! We expect that you already have installed and configured your opsi-server on the manual named [[http:// |
| * The published scripts are tested and they all work | * The published scripts are tested and they all work | ||
| - | * If software is free, so you should find links above the scripts where to get it. If a software is free, and there is no link, so you can add it as a member of the [[http:// | + | * If software, which should be installed |
| * Commercial software has to be bought from the manufacturer and has not to be asked for in the [[http:// | * Commercial software has to be bought from the manufacturer and has not to be asked for in the [[http:// | ||
| * If a script don't work, so ask politely in the [[http:// | * If a script don't work, so ask politely in the [[http:// | ||
| Line 52: | Line 53: | ||
| * wget (if not installed) | * wget (if not installed) | ||
| - | Me for myself | + | Me for myself |
| + | |||
| + | //**A remark from bell**: | ||
| + | "I think, it's easier to pack by using a share, so you can mount it on a testclient. I am usually programming on Windows-Client, | ||
| + | |||
| + | By this you can test the scripts until they function and create at last the packet."// | ||
| + | (Of course this is more a solution for experienced users, who knows, what " | ||
| First follow the instructions on the manual " | First follow the instructions on the manual " | ||
| Localboot means, the pc starts from it's own HDD. | Localboot means, the pc starts from it's own HDD. | ||
| - | After entering some informations on the product-information-screen you enter exactly the names " | + | For creating a new packet we start by changing to our directory, where we want to store our builds in future. |
| + | If our directory should be "/ | ||
| + | |||
| + | < | ||
| + | mkdir / | ||
| + | cd / | ||
| + | </ | ||
| + | |||
| + | Remark from the [[https:// | ||
| + | |||
| + | ''" | ||
| + | |||
| + | The three most important reasons are:\\ | ||
| + | 1. because of the rights on this foilder diffrent persons (if not root) can work in this folder.\\ | ||
| + | 2. The command'' | ||
| + | 3. This folder is shared as ' | ||
| + | |||
| + | It's also described in the handbook: | ||
| + | http:// | ||
| + | |||
| + | Then we begin by entering | ||
| + | < | ||
| + | opsi-newprod | ||
| + | </ | ||
| + | |||
| + | We'll have to go trough | ||
| + | < | ||
| + | product id = tightvnc | ||
| + | product name = TightVNC | ||
| + | </ | ||
| + | |||
| + | the you follow the screens, | ||
| We will not create any dependencies at this moment. Dependencies are needed if a software needs another package before getting installed. For example: CDBurnerXP needs .NetFX installed. So you can define, that the package " | We will not create any dependencies at this moment. Dependencies are needed if a software needs another package before getting installed. For example: CDBurnerXP needs .NetFX installed. So you can define, that the package " | ||
| Line 68: | Line 106: | ||
| <code winst> | <code winst> | ||
| - | --- tightvnc | + | │ |
| - | | - CLIENT_DATA | + | ├ tightvnc |
| - | | - OPSI | + | ├ CLIENT_DATA |
| - | | |- control | + | ├ OPSI |
| - | | |- postinst | + | │ ├ control |
| - | | |- preinst | + | │ ├ postinst |
| - | | - SERVER_DATA | + | │ └ preinst |
| + | └ SERVER_DATA | ||
| </ | </ | ||
| - | Change now to the folder " | + | Change now to the folder "/ |
| < | < | ||
| - | minhas-tirith:/ | + | cd CLIENT_DATA |
| </ | </ | ||
| Line 85: | Line 124: | ||
| ==== Getting the setup-program ==== | ==== Getting the setup-program ==== | ||
| - | First we need to download the setup-program, | + | First we need to download the setup-program, |
| Follow the link and watch for the self-installing package for Windows. Do a rightclick on the link and copy the URL of the file. | Follow the link and watch for the self-installing package for Windows. Do a rightclick on the link and copy the URL of the file. | ||
| Line 91: | Line 130: | ||
| < | < | ||
| - | minhas-tirith:/ | + | wget " |
| </ | </ | ||
| (Attention! The Version-Number 2.0.4 might have changed, when you read this HOWTO!) | (Attention! The Version-Number 2.0.4 might have changed, when you read this HOWTO!) | ||
| Line 100: | Line 139: | ||
| < | < | ||
| - | minhas-tirith:/ | + | touch setup.ins |
| - | minhas-tirith:/ | + | joe setup.ins |
| </ | </ | ||
| Line 116: | Line 155: | ||
| < | < | ||
| - | minhas-tirith:/ | + | touch uninstall.ins |
| - | minhas-tirith:/ | + | joe uninstall.ins |
| </ | </ | ||
| Line 123: | Line 162: | ||
| < | < | ||
| - | minhas-tirith:/ | + | touch delsub.ins |
| - | minhas-tirith:/ | + | joe delsub.ins |
| </ | </ | ||
| Line 132: | Line 171: | ||
| < | < | ||
| - | minhas-tirith:/ | + | touch Tightvnc_win7.reg |
| </ | </ | ||
| Line 148: | Line 187: | ||
| < | < | ||
| - | minhas-tirith:/ | + | cd .. |
| </ | </ | ||
| + | |||
| + | now we should be in / | ||
| and pack it by using opsi-makeproductfile. | and pack it by using opsi-makeproductfile. | ||
| < | < | ||
| - | minhas-tirith:/ | + | opsi-makeproductfile |
| </ | </ | ||
| Line 161: | Line 202: | ||
| < | < | ||
| - | minhas-tirith:/ | + | opsi-package-manager -i *.opsi |
| </ | </ | ||
userspace/howto_use_the_scripts_-_a_short_description.1324041121.txt.gz · Last modified: 2021/08/23 08:37 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
