lemniskett/archbox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Lemniskett 2020-11-18 01:07:02 +07:00 committed by GitHub
parent 33d45a7705
commit ca3cb17370
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -11,8 +11,24 @@ Before creating chroot enviroment, edit your username in ```/etc/archbox.conf```
sudo archbox --create <archlinux tarball download link> sudo archbox --create <archlinux tarball download link>
``` ```
### Configuring filesystem automount ### Configuring filesystem automount
Execute ```/usr/local/share/archbox/bin/archboxinit``` on boot. Execute ```/usr/local/share/archbox/bin/archboxinit start``` on boot.
either create an init service, or create a @reboot cronjob. If you use systemd, you can create a systemd service with this syntax below :
```
[Unit]
Description=Archbox init
PartOf=multi-user.target
[Service]
ExecStart=/usr/local/share/archbox/bin/archboxinit start
Type=oneshot
User=root
[Install]
WantedBy=multi-user.target
```
Thanks to [@SamsiFPV](https://github.com/SamsiFPV)
If you don't use systemd, either create your own init service, or create a @reboot cronjob.
### Removing chroot enviroment ### Removing chroot enviroment
**IMPORTANT**, Make sure you've unmounted everything in chroot enviroment, if you're unsure which partitions must be unmounted, remove the init script and reboot, then delete the folder. **IMPORTANT**, Make sure you've unmounted everything in chroot enviroment, if you're unsure which partitions must be unmounted, remove the init script and reboot, then delete the folder.
### Entering chroot enviroment ### Entering chroot enviroment