home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.slackware      I think its the one without Selinux crap      87,272 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 85,964 of 87,272   
   Henrik Carlqvist to David Chmelik   
   Re: chroot (overlayfs?)   
   27 Aug 22 09:31:52   
   
   From: Henrik.Carlqvist@deadspam.com   
      
   On Fri, 26 Aug 2022 03:51:47 +0000, David Chmelik wrote:   
   > Now I want to chroot to design/build packages but takes much space I   
   > heard overlayfs saves/duplicates all bare OS space: how would one   
   > install Slackware in chroot/overlayfs?   
      
   I am not sure what you are trying to accomplish by building Slackware   
   packages in a chroot environment?   
      
   Slackware packages are really simple, they are just tar archives with the   
   contents of the package. Then there is a special install directory which   
   may contain a script doinst.sh which is run after the package has been   
   unpacked. That script typically copies some file settings.conf.new to   
   settings.conf only if the old file does not exist. That script is also   
   used to create symbolic links.   
      
   To modify a package, simply unpack the contents of the package in some   
   empty temporary directory, do the modifications you want and rebuild the   
   package with makepkg.   
      
   To create a new package from scratch, simply instead populate that empty   
   temporary directory before creating the package with makepkg. This way   
   you can easily create packages containing both applications and settings   
   like a custom /etc/rc.d/rc.local file. To create a package from scratch   
   in a reproducable way, write a slackbuild script. There are many example   
   scripts to start from in the Slackware source directory and from places   
   like slackbuilds.org.   
      
   If you want to create your packages without being root there is a utility   
   called fakeroot, it is not included in Slackware but is available at   
   slackbuilds.org. This allows normal users to create packages. However,   
   you will still of course need to be root to install packages.   
      
   If you for some reason want to do a complete Slackware installation   
   within a chroot environment I would instead suggest to do that in some   
   virtual machine like qemu.   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca