![]() ![]() You can't activate a module from within your live filesystem -if you try to activate it, the system will relocate it to /mnt/live/memory/modules and then activate it (and it will disappear from your 'modwork' directory). This module is ready to use, as it has no dependencies. Use tab autocompletion for the package name (i.e., enter mv ~/Downloads/aterm, then press TAB and the rest of the filename will autocomplete), and the module name can be anything you want, but it's easier to keep your modules oganized if you use a specific name that includes the version number. Now, let's move our slack package to our workspace and convert it into a module: #creates nested folders inside our home directory (i.e., /root/ or /home/guest/) The first thing we're going to do is set up a clean workspace, to keep from cluttering up our system: I'm logged in as root (you should log in as root as well, or use su for the command line apps), and I've saved it to: /root/Downloads/aterm-1.0.1-i486-6sl.txz Go installpkg download#Now, scroll back up and click on "select mirror", then "binary package" to download this file to your Desktop. Go installpkg install#The files in /install/ are used by the install or conversion scripts to create symlinks and other files that are not contained in the slackware package, but should be included in our module. ![]() All of these files will be incorporated into our module in the same directory structure, with the exception of the files in /install/. These are all of the files that are contained in the aterm slackware package (slackware packages have the. Scroll down on that page a bit, and you'll see a list of files and directories: Ok, we're going to start off with obtaining a slackware package (rpms or debs would also suffice and can be converted to Porteus modules with deb2xzm or rpm2xzm, but since Porteus is slackware based, let's start with a slackware package): The first thing we're going to do is download a program that does not require any dependencies, and convert it into a module, then extract it to a folder, tinker with the files, and then convert that folder back to a module. ![]() Do not execute text that is preceded by a # sign, these are comments to help describe the commands you are being asked to perform. Means you should enter the text, exactly as it appears, in your console. Pick any package you like, but if it requires dependencies, your program won't run in our first example.Ĭonventions: As you read through this document, perform any actions inside codeblocks in a console. If you are using the 64-bit edition, the same commands apply, but you should use 64-bit packages, or the modules won't work. Note: this tutorial was written for the 32-bit edition of Porteus (V1.0). Please read the doc on our main site, "What are Porteus Modules" before proceeding. Much of this will be with command line tools, which offer the best way to really get "under the hood", but you can just as easily perform many of these steps from the GUI, using the right-click menus in your file manager. In this tutorial, we'll get our hands dirty with some real examples of Porteus modules, by creating them, extracting them, editing them, and generally messing around with them. If you're like me, then you learn and understand concepts better as you use and apply them, rather than simply reading about them. etc/nf -> /poudriere/jails/13amd64/etc/resolv.To view or contibute to the discussion about this tutorial, visit this thread on our forum. done Recording filesystem state for clean. ![]() done Fetching lib32 for FreeBSD 13.1-RELEASE amd64 poudriere/jails/13amd64/fromftp/src.txz 154 MB 4178 kBps 38s done Fetching src for FreeBSD 13.1-RELEASE amd64 poudriere/jails/13amd64/fromftp/base.txz 125 MB 4110 kBps 31s Fetching base for FreeBSD 13.1-RELEASE amd64 done Using pre-distributed MANIFEST for FreeBSD 13.1-RELEASE amd64 # poudriere jail -c -j 13amd64 -v 13.1-RELEASE Creating 13amd64 fs at /poudriere/jails/13amd64. Common Address Redundancy Protocol (CARP) File and Print Services for Microsoft® Windows® Clients (Samba) Dynamic Host Configuration Protocol (DHCP) Lightweight Directory Access Protocol (LDAP) Locale Configuration for Specific Languages FreeBSD as a Guest on VMware Fusion for macOS® FreeBSD as a Guest on Parallels Desktop for macOS® RAID3 - Byte-level Striping with Dedicated Parity GEOM: Modular Disk Transformation Framework Debian / Ubuntu Base System with debootstrap(8) Installing Applications: Packages and Ports Accounts, Time Zone, Services and Hardening ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |