Running Fedora 26 in a live environment almost feels like native speed to me, but when I install the OS to a thumb drive and boot into it, everything takes forever to startup. Once things start they're generally much faster but it's practically unusable. Is this considered normal?

I need to setup a portable kali-linux environment that I can boot on any available computer. I don't want to use a virtual environment because I would need to download VMware on the host computer, plus it's not practical since I will need to boot my OS on friends/customers computers. I just want to boot it from the BIOS, do what I have to do and leave without changing or downloading any files/software on machines that aren't mine. I want to leave the hosts like I was never there after I'm done. Of course, I need data persistence so that I can access, change and keep my datas across reboots on different machines. So, if I'm not wrong, what I need is: Adding Persistence to a Kali Linux Live USB Drive Making a Kali Bootable USB Drive (Windows) I have two questions: - Wouldn't something like that run too slow on a classic USB flash drive ? - I kind of want to use a portable SSD for this. I found one that I like and I'd like your opinions on it and if what I want to do with it is possible. Since this SSD has built-in features and software, is it going to be a problem to make it a kali-linux portable environment? For example, what if I need to format the disk to a specific file system type?

On my headless home server I enabled autologin. I put

-ini
ExecStart=-/sbin/agetty --autologin av --noclear %I $TERM

in file /etc/systemd/system/getty.target.wants/getty@tty1.service. Everything worked as it should until some (not every) apt upgrade. I think something rewrites this file during upgrade process. How can I solve this problem?

I have a command line **frugal** install of Tiny Core and I want to have a **persistent home directory**, because the programs I run save results there. I read the persistent option details and followed these instructions . Already added the home=UUID="xxxxxx" boot option to the /mnt/sda1/tce/boot/extlinux/extlinux.conf file and saved it with filetool.sh -b. During the boot process the home=UUID part is printed to the console, the extlinux.conf file stays persistent, but when I create files in the home directory, they disappear after reboot. Is there any way to make this work? If the system stops accidentally, will these permanent files remain there with the latest content, or the system saves them only on shutdown? I also thought about creating a cronjob and execute backup script in every n minutes, but this is the last solution I would like to have.

I am seeing some strange/frustrating behavior with iptables in Pop!_OS, which I am struggling to understand. Firstly, I have a server, on which I want to enable incoming ssh connections. The following set of iptables rules does not seem to work (I can't connect with ssh from a remote machine): Chain INPUT (policy DROP 434 packets, 243K bytes) pkts bytes target prot opt in out source destination 854 85718 ACCEPT all -- lo any anywhere anywhere 0 0 ACCEPT icmp -- any any anywhere anywhere icmp echo-reply 5 420 ACCEPT icmp -- any any anywhere anywhere icmp echo-request 183 27170 ACCEPT udp -- any any anywhere anywhere udp spt:domain 75 9853 ACCEPT tcp -- any any anywhere anywhere tcp dpt:ssh 706 528K ACCEPT tcp -- any any anywhere anywhere tcp spt:https 183K 472M ACCEPT tcp -- any any anywhere anywhere tcp spt:http 0 0 ACCEPT tcp -- any any anywhere anywhere tcp spt:ssh state ESTABLISHED Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 129K packets, 7005K bytes) pkts bytes target prot opt in out source destination However, if I run the following line, the ssh connection from the remote machine does work: $ sudo iptables -A INPUT -i lo -j ACCEPT Chain INPUT (policy DROP 434 packets, 243K bytes) pkts bytes target prot opt in out source destination 854 85718 ACCEPT all -- lo any anywhere anywhere 0 0 ACCEPT icmp -- any any anywhere anywhere icmp echo-reply 5 420 ACCEPT icmp -- any any anywhere anywhere icmp echo-request 183 27170 ACCEPT udp -- any any anywhere anywhere udp spt:domain 75 9853 ACCEPT tcp -- any any anywhere anywhere tcp dpt:ssh 706 528K ACCEPT tcp -- any any anywhere anywhere tcp spt:https 183K 472M ACCEPT tcp -- any any anywhere anywhere tcp spt:http 0 0 ACCEPT tcp -- any any anywhere anywhere tcp spt:ssh state ESTABLISHED 0 0 ACCEPT all -- lo any anywhere anywhere Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 129K packets, 7005K bytes) pkts bytes target prot opt in out source destination This seems particularly puzzling, given that I seemingly had the exact same filter line enabling loopback connections beforehand. Does the ordering of the rules matter in this case? Secondly, I have the systemd netfilter-persistent service enabled, but it doesn't seem to be saving/reloading the iptables settings correctly on boot. When I reboot, the rules revert to the first example. Is anyone able to help shed some light on these issues. I need to have incoming ssh connections enabled on the server, and for the firewall settings to persist on reboot.

I have a Linux VM that has frozen completely. It likely happened because I left it idle for too long. I don't have any snapshots and I don't want to have to set it up again due to having a lot of issues getting everything up and running. When I run a Windows VM on it I can restart it and have it reload as a normal computer. If I shut down a Linux, though, it is completely reset and nothing is saved. Is it possible to restart the Linux VM somehow without losing all my data, configurations, installed programs etc.? I am on VMware Workstation 15 Pro. I installed from a Linux ISO the same way I install Windows VM. I did not remove the installation medium from the drive before rebooting, I can't remove it either because it's in use by VMware. If I remove the ISO then the screen is just black after powered on.

I'm facing an issue with my RAID 0 setup on Linux. I've created a RAID 0 array with 4 disks, but after a few hours of activity and several system reboots, Linux changes the /dev/sd* directives used in the RAID creation. This causes the array to become unsynchronized and ultimately breaks the RAID. Is there a way to persist the /dev/sd* mappings across reboots to prevent this issue? Any help would be greatly appreciated! Obs: using mdadm.

I would like to increase the amount of Encrypted persistence storage for my Kali Linux live USB. It is encrypted with LUKS encryption and is written as a DD image. My USB is a Sandisk with 32GB and I only use about 2GB for Kali, so the rest is free to use. I have done research but can’t figure out how to extend the persistence when it is encrypted and written in DD, even though I can access the system myself. This probably isn’t relevant but I burnt it with the latest Rufus version. Anything I can try?

I have a USB web camera that gives suboptimal results when I plug it in (Linux seems to apply its own V4L2 settings to it that it thinks are best, they are not). Mainly, it operates at a low FPS. But if I open Guvcview, select "Settings" -> "Hardware defaults" in the menu, and add some minor modifications, I can get a higher FPS and overall better quality. If I close Guvcview and open it again, the settings are reset in Guvcview, but the changes I made stay active in other apps like video chat software. However, if I unplug the webcam, the changes are lost everywhere, and after plugging in again I have a worse quality again. What I do for now is I saved the changes in Guvcview as a .gpfl file (menu -> "Settings" -> "Save profile"), and whenever I reconnect the webcam, I open Guvcview and load the profile with "Load profile". How can I make these settings persist so that I never have to do this again, and have them applied to only this specific video device and not others?

I have a 8GB USB Drive where I installed Kali Linux (4GB partition) and then used the other 4GB for the persistent part. Yesterday I did an "apt update && apt upgrade" and it crashed my system. At the time it seemed that there was more than enough space for the updates but today I boot the system, choose the Persistence installation, put my password for the encrypted drive and then I get a black screen with a blinking arrow instead of the login screen. I think it ran out of space... I have a 64GB USB Drive and I wanted to move the installation to there to have more space. Is this possible? If so, how can I do it, and I'm able to change the size of the persistence partition on the new drive?

Whenever I restart my Jetson Nano (Ubuntu 18.04.06), **all changes I made are reset**. The Jetson used to work fine and no major settings have been changed. There are also previous changes on the Jetson Nano that don't disappear when restarted. **To clarify: Changes ANYWHERE on the machine are not saved after restart/shutdown and I'm not using a live USB** I have tried accessing the computer directly with keyboard/mouse as well as through ssh and ensured that the ssh doesn't put you into guest mode. I also checked the disk space and there seems to be plenty. Please let me know if you have any ideas as I am currently stuck! Anything helps! Progress update: Completely stuck for weeks. I would appreciate if someone could offer any advice as I don't have the rep for a bounty.

I have been fiddling with power management and I can't find a way to make the changes I want persistent. For example, I have set the maximum cpu frequency with this command:

sudo cpupower frequency-set --max 2GHz

but the value goes back to its original value on every reboot. Is there a standard way to make this change persistent? I have read about kernel modules but I don't know how they work... can anyone help me? Note. My machine is running Ubuntu 20.04.

All of the information I currently find on this matter is insufficient for my taste. It is either outdated, misleading or even wrong, seems overly complicated or not covering this specific question. **Goals:** - bootable USB drive (both UEFI and legacy BIOS supported) - (based on) live Debian 9 (stretch), or buster or bullseye - persistence (by default and for both UEFI and legacy BIOS) - German keyboard layout per default - fit for troubleshooting other GNU/Linux systems **Reasons:** - having to setup the keyboard layout on every use is a real headache - cryptsetup and efibootmgr are missing in the default Debian live images - gnome-terminal has this annoying white background per default **No solutions:** - (re)building custom debian live image (it seems tedious, although I did not try it yet) - unetbootin (asks for an unknown password when starting up on debian stretch and I think it does not support UEFI anyways) - some foreign automated process where I don't see what is happening Debian live and install images are isohybrid and can be conveniently written to block devices using dd. And they do work from USB drives like that, which is very nice! However, there will be no persistence and no way to start with a non-english keyboard layout per default without editing the grub and isolinux config, which is included in the very read-only ISO9660 filesystem of the live ISO image. So even after writing the live ISO to a USB drive, these parameters still cannot be changed.

I would like to use Debian wherever I go by installing it on a USB flash drive, but I'm not sure how to make it save the settings and be able to install/update packages without loosing them on reboots. So I downloaded a Hybrid ISO image from this link , and I followed the instructions in the FAQ : dd if=image.iso of=/dev/sdb bs=4M; sync This command copied the image to the flash drive by creating a partition which size is the same as the ISO image (1.3 GB out of 8GB), and the rest of the flash drive is unallocated. I searched on how to do this, but every tutorial uses a different approach and some of them are outdated and talk about the old usb-hdd image. So how should I install this hybrid image on the flash drive ? How should I partition my flash drive to be able to install packages and save settings ? and how can I install this image without using dd ?

I have created a persistent usb with Linux Mint on a 128 Gb thumb drive. When I first created it I guess I only allocated 80 Gb for persistence. Now that I have been using it for a couple months the storage I have to work with is running low. I don't use this usb drive for anything else but running and working on Linux Mint so I'd like to use most if not all of the 128 Gb towards this. Is there a way for me to add more storage (increase the partition size allocated for persistence) without having to create a whole new persistent usb with another drive? Some more in-depth information if needed: - Linux Mint 12.1 - Cinnamon Version: 5.6.8 - Linux Kernel: 5.15.0-56-generic *****EDIT***** I did some more digging and found this menu: I notice I can resize Partition 1 to be less, therefore allowing me to make Partition 2 larger. I am guessing that Partition 1 is for the Linux Mint OS and Partition 2 is for all files saved for persistence? Are there any downsides to doing this? What is the minimum amount of storage I should make Partition 1? *****Update***** I created the persistent usb using Rufus. I also have this terminal output for more information:

mint@mint:~$ lsblk -o name,size,fstype,label,mountpoint /dev/sda
NAME     SIZE FSTYPE LABEL      MOUNTPOINT
sda    119.5G                   
├─sda1  44.5G vfat   LINUX MINT /cdrom
└─sda2    75G ext3   casper-rw  /media/mint/casper-rw

I've installed alpine linux on an R-Pi using instructions on Alpine's wiki . The instructions note: > Alpine Linux will be installed in diskless mode , hence, Alpine Local Backup (lbu) is required to save modifications between reboots. I have a persistent package cache setup for apk, and that is working, but as far as the actually installed packages are concerned: the manual for lbu it only saves /etc by default. What I'm struggling with is figuring out how I'm supposed to install packages so they are there ready when the system boots. At the moment, the system boots with nothing new installed and only installs packages I've previously asked for if I type:

apk add

Some of the packages I want (including avahi) have daemons which are supposed to be initiated through scripts in /etc/init.d. Even if I save /etc the daemons will not be installed and ready to start. What am I supposed to do to ensure packages (including daemons) are correctly installed when the system boots?

I'm somewhat of a beginner with Linux, sorry for the dumb question. I installed a persistent Linux Mint install to a USB drive. It has been working well, but now I want to install it directly to a new SSD drive I bought. I thought that using the "Install" option would already copy all my apps and user files to the drive, but as far as I can see it only installed a fresh Linux Mint install, with no apps and my /home folder only has a new user I created with the install. **Question:** How do I make the exact install I have on the USB drive be copied to the SSD drive? **Question 2:** Is it possible and advisable to use Timeshift, Clonezilla or another app to make an image of the old Linux install and then recover that image when booting with the new Linux install?

For my particular use case, I liked to use docker-compose up to provide retry logic for a couple of apps. When shifting gears and pivoting to easy to use CDN infrastructure, it seems as if running shell commands to start everything up in a single docker container will be simpler. However, the only thing I have found that corresponds to anything like "always up" logic is:

while true; do start-app || sleep 1; done

What I was curious about was if there is truly some sort of Unix/BASH 'retry' tool that will make sure a command is always running in addition to whatever the useful features there are for that kind of system-level operation?

I'm currently using a Debian installation for a DIY router. In the interests of security, I'm wondering how I might switch to a non-persistent installation in order to defend against any persistence gained after an exploit against the system (BIOS attacks not in scope). I'm thinking about using a pre-configured live USB. I'd have persistent storage (in the form of a USB) to store rules, configuration, etc. But of course with the core system being read-only I wouldn't be receiving important security updates, so then an attacker would just be able to keep exploiting the system instead of gaining persistence. I want to keep it low-maintenence - I don't want to keep having to look whether there's been a CVE in anything and 'recompile' my live USB each time. A possbility might be a PXE boot from a seperate system which auto-updates the live OS and packages, but then there's the chicken and the egg because if the router goes offline it can't update. Wondering if anyone has any ideas? Thanks

I want to make a persistent live boot in which I can store my data on a debian iso booted from a hard drive. So I downloaded debian-live (here) , modified the grub entry to be able to boot into the live-system:`

menuentry "Debian modified" {
  set iso_path="/live-boot/debian-live.iso"
  export iso_path
  loopback loop $iso_path
  set root=(loop)
  set loopback="findiso=${iso_path}"
  export loopback
  linux /live/vmlinuz-5.10.0-13-amd64 boot=live persistence components keyboard-layouts=de splash verbose "$loopback"
  initrd /live/initrd.img-5.10.0-13-amd64
}

I can boot into my live system but when I want to store data in it, after a reboot the data is lost. Am I doing something wrong in the grub entry here? Here could be also useful information for you, df -ha on the live boot gives me the following output (shortened to relevant parts):

FS        Size  Used   Avail  Use    Mounted on
/dev/sda1 ...   ...    ...    ...    /run/live/persistence/sda1  <= my main partition (also from where the boot is happening)
/dev/loop0 ..   ...    ...    ...    /run/live/medium
/dev/loop1 ..   ...    ...    ...    /run/live/rootfs/filesystem.squashfs
tmpfs     ...   ...    ...    ...    /run/live/overlay
overlay   ...   ...    ...    ...    /
tmpfs     ...   ...    ...    ...    /usr/lib/live/mount
/dev/loop0 ..   ...    ...    ...    /usr/lib/live/mount/medium
/dev/loop1 ..   ...    ...    ...    /usr/lib/live/mount/rootfs/filesystem.squashfs
/dev/sda1  ..   ...    ...    ...    /usr/lib/live/mount/persistence/sda1
tmpfs     ...   ...    ...    ...    /usr/lib/live/mount/overlay

and the fstab on the live boot gives me the following output:

overlay / overlay rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0

The mount | grep overlay returns:

tmpfs on run/live/overlay type tmpfs (rw,noatime,mode=755)
overlay on / type overlay (rw,noatime,lowerdir=/run/live/rootfs/filesystem.squashfs/,upperdir=/run/live/overlay/rw,workdir=/run/live/overlay/work)
tmpfs on /usr/lib/live/mount/overlay type tmpfs (rw,noatime,mode=755)

I also manually tried to mount the overlay directly to the persistent partition (sda1) with the persistent storage as upperdir / workdir which results in

overlay on / type overlay (rw,noatime,lowerdir=/run/live/rootfs/filesystem.squashfs/,upperdir=/run/live/persitence/sda1/rw,workdir=/run/live/persistence/sda1/work

of course, I created those directories there on the persistent partition ;-) ... but it is still not working to store data persistently and I don't know what to do. So how can I modify this all to be able to store data on the live-iso and when rebooting without losing the data stored?