This is an old revision of the document!
iw wlan0 scan |grep PLUSNET-J8GW xrandr --output eDP1 --mode 1368x768
smbclient pnhub1/usb1 -U GUEST -I 192.168.1.254 Slax does not use a config file. It runs xlunch binary with bunch of arguments, in /usr/bin/fbappselect # set keyboard layout fbsetkb $(cat ~/.fluxbox/kblayout) ie, change ~/.fluxbox/kblayout from en to gb ———————————————————- /usr/share/applications to add/remove destop startup items —————————————————————————- https://unix.stackexchange.com/questions/705141/how-to-copy-paste-between-a-console-and-an-x-session <file script> script Script started, file is typescript $ type commands get output … $ exit Then:- less -R typescript </> ————————————————————————————– Tomas M unread, Dec 29, 2017, 2:45:34 PM to Slax users Well, I build Slax this way: 1) install Debian from minimal netinst ISO to hard disk 2) boot it 3) download and extract liveKit to /tmp 4) cd /tmp/linux-live-master/Slax/debian 5) ./build 6) see /tmp for scripts to make ISO Then I need to boot the generated ISO and I can setup additional software, like install Xorg, then use savechanges to make the module, add it to ISO again and boot it and build another Slax base module. So basically there is no simple one-script-for-all yet. —————————————————————————————— Tomas M's profile photo Tomas M unread, Dec 29, 2017, 2:45:34 PM to Slax users Well, I build Slax this way: 1) install Debian from minimal netinst ISO to hard disk 2) boot it 3) download and extract liveKit to /tmp 4) cd /tmp/linux-live-master/Slax/debian 5) ./build 6) see /tmp for scripts to make ISO Then I need to boot the generated ISO and I can setup additional software, like install Xorg, then use savechanges to make the module, add it to ISO again and boot it and build another Slax base module. So basically there is no simple one-script-for-all yet. Tomas M > – > You received this message because you are subscribed to the Google Groups > “Slax users” group. > To unsubscribe from this group and stop receiving emails from it, send an > email to slax-users+…@googlegroups.com. > To post to this group, send email to slax-…@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. Jeremy Suntheimer's profile photo Jeremy Suntheimer unread, Dec 29, 2017, 2:59:10 PM to slax-…@googlegroups.com Okay, thanks! On Fri, Dec 29, 2017 at 9:44 AM, Tomas M <to…@slax.org> wrote: Well, I build Slax this way: 1) install Debian from minimal netinst ISO to hard disk 2) boot it 3) download and extract liveKit to /tmp 4) cd /tmp/linux-live-master/Slax/debian 5) ./build 6) see /tmp for scripts to make ISO Then I need to boot the generated ISO and I can setup additional software, like install Xorg, then use savechanges to make the module, add it to ISO again and boot it and build another Slax base module. So basically there is no simple one-script-for-all yet. Tomas M On Fri, Dec 29, 2017 at 12:07 PM, <jsunth…@gmail.com> wrote: > Hi, assuming I'm running a clean boot of the latest Slax, and I've got a > minimal Debian network install mounted on /mnt/debian, how do I use Linux > Live Kit to build a fresh Slax? I'm at that point. Also, I have cloned the > Linux Live Kit repo into /root/linux-live. > > > – > You received this message because you are subscribed to the Google Groups > “Slax users” group. > To unsubscribe from this group and stop receiving emails from it, send an > email to slax-users+unsubscribe@googlegroups.com. > To post to this group, send email to slax-…@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. – You received this message because you are subscribed to a topic in the Google Groups “Slax users” group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/slax-users/Ko4rh5xMk3k/unsubscribe. To unsubscribe from this group and all its topics, send an email to slax-users+unsubscribe@googlegroups.com. luca….@gmail.com's profile photo luca….@gmail.com unread, Jan 9, 2018, 2:54:17 PM to Slax users I'd like to try apply Linux Live Kit to Devuan Minimal Live: https://files.devuan.org/devuan_jessie/minimal-live/ Not due to the “systemd war”, but because it is based on a 586 non-PAE kernel and because it is extremely light on resource. But before I'd like to know if Linux Live Kit can be applied to it, due to missing systemd and the aufs support. Tomas M's profile photo Tomas M unread, Jan 10, 2018, 7:00:40 AM to Slax users It wont work without aufs Tomas M Dne 9. 1. 2018 3:54 odp. napsal uživatel <luca….@gmail.com>: Lucbertz's profile photo Lucbertz unread, Jan 19, 2018, 5:17:25 PM to Slax users I tried to download Debian net-install and it seems it doesn't contain aufs.ko kernel. How did you obtained aufs to build Slax kernel? Which is the reason you did not use overlayfs, that seems to be more popular? Tomas M's profile photo Tomas M unread, Jan 19, 2018, 5:59:40 PM to Slax users You can get aufs.ko with this command: apt install aufs-dkms You may need to run it AFTER your system is compressed to .sb file, because installing aufs-dkms adds tons of things like compiler etc, but what you only want is aufs.ko after the installation is complete I am not using overlayfs because last time I tried it, it was not working properly. Tomas M > – > You received this message because you are subscribed to the Google Groups “Slax users” group. > To unsubscribe from this group and stop receiving emails from it, send an email to slax-users+…@googlegroups.com. lucbertz's profile photo lucbertz unread, Mar 8, 2019, 3:21:44 PM to Slax users > You can get aufs.ko with this command: > apt install aufs-dkms > > You may need to run it AFTER your system is compressed to .sb file, > because installing aufs-dkms adds tons of things like compiler etc, > but what you only want is aufs.ko after the installation is complete To better understand: - aufs.ko module is needed in initrfs.img ; - it is not needed in 01-core.sb or other modules. So I have to: - prepare “my debian based distro” as I prefer, without installation of aufs-dkms; - launch the build script of Live Kit and keep only the 01-core.sb file from the output; - install aufs-dkms in the “my debian based distro”; - launch the build script of Live Kit and keep only the initramfs.img from the new output. Is there any easier way? I successfully applied Live Kit on Devuan, but, for now, I kept “tons of things like compiler etc” in the output. Furthermore I get the INIT message: “ERROR: could not open /proc/stat: No such file or directory”. But, after this, the system boots anyway and it seems to run fine. lucbertz's profile photo lucbertz unread, Mar 15, 2019, 10:10:35 AM to Slax users > > You can get aufs.ko with this command: > > apt install aufs-dkms For a given kernel (4.9.0-8-686-pae here below), I found it's enough to: - retrieve aufs.ko file from /lib/modules/4.9.0-8-686-pae/kernel/fs/aufs/ folder; - copy the module aufs.ko in /lib/modules/4.9.0-8-686-pae/kernel/fs/aufs/ folder of the new distro not having aufs; - run “depmod” command as root. > I successfully applied Live Kit on Devuan, but, for now, I kept “tons of things like compiler etc” in the output. Furthermore I get the INIT message: > “ERROR: could not open /proc/stat: No such file or directory”. > But, after this, the system boots anyway and it seems to run fine. Does anybody knows how to solve this trivial error? Korben of Slaxsen's profile photo Korben of Slaxsen unread, Aug 27, 2019, 12:36:21 AM to Slax users On Friday, December 29, 2017 at 3:45:34 PM UTC+1, Tomas M wrote: Well, I build Slax this way: 1) install Debian from minimal netinst ISO to hard disk 2) boot it 3) download and extract liveKit to /tmp 4) cd /tmp/linux-live-master/Slax/debian 5) ./build 6) see /tmp for scripts to make ISO The current debian-10.0.0-amd64-netinst.iso is 350mb. Your slax-64bit-9.9.1 iso, incl. 01-core.sb, 02-xorg.sb and 03-desktop.sb, is 145m. I haven't (yet) found any step-by-step guides on what to trim to reach the same minimalixm and isn't linux savvy enought to parse: Remove all unnecessary files, to make your Live Linux system as small as possible (this step is optional). ====It is recommended to remove udev's persistent net rules and other settings of your distro, which may prevent it from functioning correctly on different hardware (from https://www.linux-live.org)==== <file persistent udev.txt> /etc/udev/rules.d/70-persistent-net.rules /sys/devices/pci0000:00/0000:00:1c.3/0000:44:00.0/ieee80211/phy0/rfkill1/persistent /sys/devices/pci0000:00/0000:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.0/bluetooth/hci0/rfkill0/persistent /lib/udev/rules.d/60-persistent-storage.rules /lib/udev/rules.d/60-persistent-v4l.rules /lib/udev/rules.d/75-persistent-net-generator.rules /lib/udev/rules.d/60-persistent-input.rules /lib/udev/rules.d/60-persistent-alsa.rules /lib/udev/rules.d/60-persistent-storage-tape.rules /lib/modules/6.12.7/kernel/drivers/md/persistent-data /lib/modules/6.12.7/kernel/drivers/md/persistent-data/dm-persistent-data.ko /lib/modules/6.6.6/kernel/drivers/md/persistent-data /lib/modules/6.6.6/kernel/drivers/md/persistent-data/dm-persistent-data.ko /boot/initrd-tree/lib/udev/rules.d/60-persistent-storage.rules /boot/initrd-tree/lib/udev/rules.d/60-persistent-v4l.rules /boot/initrd-tree/lib/udev/rules.d/75-persistent-net-generator.rules /boot/initrd-tree/lib/udev/rules.d/60-persistent-input.rules /boot/initrd-tree/lib/udev/rules.d/60-persistent-alsa.rules /boot/initrd-tree/lib/udev/rules.d/60-persistent-storage-tape.rules </file>