Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
userspace:howto_use_the_scripts_-_a_short_description [2012/01/09 11:11]
Thomas_H
userspace:howto_use_the_scripts_-_a_short_description [2019/02/27 10:01]
Thomas_H
Line 4: Line 4:
  
 written by  //​[[hungerharke@gmx.de|Thomas_H]] 2011/12/16 12:50// written by  //​[[hungerharke@gmx.de|Thomas_H]] 2011/12/16 12:50//
 +edited by //​[[hungerharke@gmx.de|Thomas_H]] 2019/02/27 09:​50// ​
  
 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 11: Line 12:
 This Howto is for the newbies in first line, starting with opsi, trying out the features. With this little Howto they should have the first success by creating a package, without knowing the "​why"​ or "​what"​ in the scripts. The "​why"​ and "​what"​ is something, you will have to learn later and let me say, yes you'll **have** to learn it, otherwise you always will need the help of other users. This Howto is for the newbies in first line, starting with opsi, trying out the features. With this little Howto they should have the first success by creating a package, without knowing the "​why"​ or "​what"​ in the scripts. The "​why"​ and "​what"​ is something, you will have to learn later and let me say, yes you'll **have** to learn it, otherwise you always will need the help of other users.
  
-Of course: best is at last to get some training, you can get informations about training on opsi [[http://www.opsi.org/​en/​support|here]]. Commercial support is also avail.+Of course: best is at last to get some training, you can get informations about training on opsi [[https://uib.de/en/support-training/​support/​|here]]. Commercial support is also avail.
  
  
Line 52: Line 53:
     * wget (if not installed)     * wget (if not installed)
  
-Me for myself ​created a folder named "/​opsi-packages" in the root-directory for creating the packages. My account is a member of opsi-admin and the folder has rwx-rights for group opsi-admin course. Such a folder has many advantages and after creating your packages, you should keep it! Software is changing nearly every day and it's much easier to change the setup.exe and to repack, than to start again and again creating folders, calling the opsi-newprod,​ etc.+Me for myself ​use the folder named "opsiproducts" in the home-directory for creating the packages. My account is a member of opsi-admin and the folder has rwx-rights for group opsi-admin course. Such a folder has many advantages and after creating your packages, you should keep it! Software is changing nearly every day and it's much easier to change the setup.exe and to repack, than to start again and again creating folders, calling the opsi-newprod,​ etc.
  
 //**A remark from bell**: //**A remark from bell**:
Line 63: Line 64:
 Localboot means, the pc starts from it's own HDD. Localboot means, the pc starts from it's own HDD.
  
-In "​product-information-screen"​ we enter some informations,​ for example+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 "/​home/​opsiproducts"​ (like my example) so we first create this directory and change to it. 
 + 
 +<​code>​ 
 +mkdir /​home/​opsiproducts 
 +cd /​home/​opsiproducts 
 +</​code>​ 
 + 
 +Remark from the [[https://​forum.opsi.org/​viewtopic.php?​f=7&​t=3182|forum]],​ added by [[d.oertel]]:​ 
 + 
 +''"​pack opsi products in /​home/​opsiproducts only. 
 + 
 +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''​ <​code>​opsi-setup --set-rights</​code>​ ''​knows this folder and sets the correct rights. A /​home/​mydir/​opsi-install would be ignored. This is important, because the opsi-mackage-manager gives the package to opsiconfd while installation and interrupts on missing rights on the folder.\\ 
 +3. This folder is shared as '​opsi_workbench',​ which makes it easier to update the products using a Windows-Client.\\ 
 + 
 +It's also described in the handbook: 
 +http://​download.uib.de/​opsi4.0/​doc/​html/​en/​opsi-getting-started/​opsi-getting-started.html#​opsi-getting-started-softwintegration-create-opsi-package-handling''​ 
 + 
 +Then we begin by entering the first command for creating an opsi-packet:​ 
 +<​code>​ 
 +opsi-newprod 
 +</​code>​ 
 + 
 +We'll have to go trough some screens. The first is the "​product-information-screen"​. In this screen ​we enter some informations,​ for example
 <​code>​ <​code>​
 product id = tightvnc product id = tightvnc
Line 80: Line 106:
  
 <code winst> <code winst>
---- tightvnc +│ 
-   | - CLIENT_DATA +├ tightvnc 
-   | - OPSI +├ CLIENT_DATA 
-   | |- control +├ OPSI 
-   | |- postinst +│ ├ control 
-   | |- preinst +│ ├ postinst 
-   | - SERVER_DATA+│ └ preinst 
 +└ SERVER_DATA
 </​code>​ </​code>​
  
-Change now to the folder "​CLIENT_DATA":​+Change now to the folder "/​home/​opsiproducts/​tightvnc/​CLIENT_DATA":​
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc # cd CLIENT_DATA+cd CLIENT_DATA
 </​code> ​ </​code> ​
  
Line 103: Line 130:
  
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # wget "​http://​www.tightvnc.com/​download/​2.0.4/​tightvnc-2.0.4-setup.exe"​+wget "​http://​www.tightvnc.com/​download/​2.0.4/​tightvnc-2.0.4-setup.exe"​
 </​code>​ </​code>​
 (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 112: Line 139:
  
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # touch setup.ins +touch setup.ins 
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # joe setup.ins+joe setup.ins
 </​code>​ </​code>​
  
Line 128: Line 155:
  
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # touch uninstall.ins +touch uninstall.ins 
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # joe uninstall.ins+joe uninstall.ins
 </​code>​ </​code>​
  
Line 135: Line 162:
  
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # touch delsub.ins +touch delsub.ins 
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # joe delsub.ins+joe delsub.ins
 </​code>​ </​code>​
  
Line 144: Line 171:
  
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # touch Tightvnc_win7.reg+touch Tightvnc_win7.reg
 </​code> ​ </​code> ​
  
Line 160: Line 187:
  
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # cd ..+cd ..
 </​code>​ </​code>​
 +
 +now we should be in /​home/​opsiproducts/​tightvnc
  
 and pack it by using opsi-makeproductfile. and pack it by using opsi-makeproductfile.
  
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # opsi-makeproductfile+opsi-makeproductfile
 </​code>​ </​code>​
  
Line 173: Line 202:
  
 <​code>​ <​code>​
-minhas-tirith:/​opsi-packages/​tightvnc/​CLIENT_DATA # opsi-package-manager -i *.opsi+opsi-package-manager -i *.opsi
 </​code>​ </​code>​
  

QR Code
QR Code userspace:howto_use_the_scripts_-_a_short_description (generated for current page)