Could anyone please suggest me a LiveCD (Linux Based) with SSH & FTP Services. Basically I don't want to install anything on my laptop so I just want to boot LiveCD with FTP/SSH services so I can connect from other clients to it and do a FTP/SCP to/from it. Thanks

Slax uses X.org for managing its GUI. However, when I boot Slax (specifically in a VM), the resolution gets capped at 1024x768. How can I increase the resolution to more fully utilize the screen estate available on my display? I have already attempted to follow the old advice from the following sources: - http://old.slax.org/forum.php?action=view&parentID=25516 - http://www.linuxquestions.org/questions/mandriva-30/changing-screen-resolution-552768 - http://slaxlive.blogspot.com/2005/07/slax-linux-step-by-step-first-step.html

Can't delete a file at an NTFS partition, even tried this in LiveCD, but at the same partition delete other files not a problem. The file couldn't be deleted is a Windows system file, maybe with special NTFS permissions. So how can I do in the right behavior? From CLI: sudo rm '/media/.../AppStudio.Uwp.xr.xml' rm: cannot remove '/media/.../AppStudio.Uwp.xr.xml': No such file or directory From GUI: Error removing file /media/.../AppStudio.Uwp.xr.xml: Permission denied

I want to create a final infrastructure to boot a PXE custom kernel image, but through the process I'm stuck creating a middle "live" CD ISO using a previously compiled custom kernel image with the live-build tool. I don't know how/where to specifiy the lb config/live build tool to use my own kernel deb package instead the default amd64-kernel flavour. I think that I have to use the --linux-packages parameter, but I don't really understand how. I can't find any kind of info or example. I have read all the man pages and so on, but I'm stuck. My current auto/lb config: *lb config no auto \ --architectures amd64 \ --distribution stretch \ --system live \ --chroot-filesystem squashfs \ --apt-recommends false \ --apt-indices none \ --memtest none \ --debian-installer false \ --interactive shell \ --bootloaders syslinux \ --bootappend-live "boot=live components hostname=test username=test sudo" \ "${@}"* How can I create a live image with custom compiled kernel?

I want to boot Linux distros from GRUB 2.0 command line. I've tried to do so for couple of distros and at "best" I receive initramfs prompt, no GUI which starts if distro is run stardard way. Resulting file system seams to have files contained in initrd file (less then 100Mb), but not in filesystem.squashfs (which is larger than 1Gb). vmlinux, initrd and filesystem.squashfs files are in casper folder and linux command in menu entry in grub.cnf in distros contains boot=casper, I suspect folder name casper is not necessary for kernel option to work, casper is persistence something option related as far as I understood from wikipedia. Also as far as I understood the problem, when boot process tries to do unionfs thing it could not find SquashFS file with all except kernel distro stuff to add. How do I let it know its' location? Maybe the problem is of other root cause, please tell me so then. ADDED 0: I changed linux (hd0,msdos2)/casper/vmlinuz command adding root=UUID=what ls command gives for partition with distro and now starting, finally getting many lines stdin: Not a typewriter, then (initramfs) Unable to find a medium containing live file system and again CLI prompt. Was stdout on screen same lines as w/out root option... I just don't remember for sure, so many lines during boot. I far as understand from the GRUB manual and my try-and-error, root variable can point to device only, not path inside device, so I see setting it will not point to squashfs file inside casper folder. ADDED 1: I run grep -rnw 'initrd file loop mounted location' -e 'filesystem.squashfs' as per https://stackoverflow.com/questions/16956810/how-do-i-find-all-files-containing-specific-text-on-linux and got nothing, so have no idea how init process finds that squashfs file.

So. Been going at the gentoo install without proper instructions until very recently. After emerge-webrsync stage of the install a message pops up saying "your current profile is invalid". It appears to be a blocker on emerging to kick off the rest of the install. This doesn't seem to be an issue with the laptop (NIC is working and changing ssd does nothing for this issue) and I've validated the SHA-512 against the DIGEST.asc associated with the downloaded tarball. It seems unlikely the livecd I'm using to install would have been rewritten over this network connection. eselect is functioning, and experimentation with the 35 defaults yields no results. Have created a custom profile but am having issues having it appear on eselect. Confused somewhat on the documentation for this, continuing to experiment. Suggestions welcome. Have already run eselect profile list and eselect profile set for the default profiles. The issue persists after an emerge --sync. In fact the issue first occurred after an emerge --sync. Have readlink'd the make.profile in portage and tried a few different symlinks. Resources: * https://wiki.gentoo.org/wiki/Profile_(Portage) * https://wiki.gentoo.org/wiki/Project:Eselect/User_guide * https://wiki.gentoo.org/wiki/User:Sakaki/Sakaki%27s_EFI_Install_Guide/Installing_the_Gentoo_Stage_3_Files

I have installed minimal version of centos6.7 on usb stick, copied/installed some applications/packages and customized accordingly. Now I want to build an ISO of my customized OS and want to install on other systems using ISO. Is that possible? Thanks in Advance.

I made a custom UEFI only bootable ISO file and loaded it to UTM VM. The rootfs is directly stored in the ISO, and I'm using grub2 as boot loader. After I configured the linux, initrd and boot the image, the vm seems stuck forever, why?

How to setup/configure the Arch Linux bootcd (live-CD, ISO) so I can login to it using an SSH client? And which password is by default set for the (automatic login) root account?

I downloaded GhostBSD Live CD but it is asking for an input and a password on boot. Live CDs usually don't need those. I could not find an answer in the GhostBSD Handbook.

I want to install Kali Linux but the problem is, when I start it from the Live CD my wireless adapter works, but when it's installed, my wireless adapter doesn't seems to work. Sorry, but I can't tell you more about that but maybe you could explain why this happens.

I have written a shell script to create a squashfs live system from a hard drive installation, in order to have a linux system running only in ram. But when I run the toram live system, I have the following error in the dmesg: systemd: Failed to open /dev/shm device, ignoring: Inappropriate ioctl for device Despite this error, the toram live system seems to work without problems. The script works only if only one user is created on the installed Linux, because ACL are not supported by squashfs, but needed for the directory /media/username/. Here is the script:

#!/bin/bash
    
    # Destination directory:
    DEST=$HOME/squashfs
    
    sudo mkdir -p ${DEST}
    
    # Copying installation in destination directory:
    sudo rsync --progress --specials --perms -av -lXEog --delete / ${DEST} --one-file-system \
    --exclude=/proc/* --exclude=/tmp/* --exclude=/dev/* \
    --exclude=/sys/* --exclude=/boot/* \
    --exclude=/etc/mtab --exclude=${DEST}
    
    # Make /media/username ownership to the user, because squashfs doesn't support ACL
    MEDIA="$USER:$USER $DEST/media/$USER"
    sudo chown $MEDIA
    
    # Remove links to mounted drives in destination directory /media/username/:
    MEDIA="$DEST/media/$USER"
    sudo rm -f $MEDIA/*
    
    # Remove unwanted entries in fstab of the future live system: 
    sudo sed -i '/\/boot\/efi/d' ${DEST}/etc/fstab 
    sudo sed -i '/swap/d' ${DEST}/etc/fstab 
    sudo sed -i '/UUID=.*\ \/\ /d' ${DEST}/etc/fstab
    
    # Mount special files in order to chroot:
    sudo mount -o bind /proc ${DEST}/proc
    sudo mount -o bind /dev ${DEST}/dev
    sudo mount -o bind /dev/pts ${DEST}/dev/pts
    sudo mount -o bind /sys ${DEST}/sys
    sudo cp /etc/resolv.conf ${DEST}/etc/resolve.conf
    
    # upgrade the chrooted system, and install live-boot package 
    # as well as the lastest kernel: 
    sudo chroot ${DEST} apt-get update
    sudo chroot ${DEST} apt-get upgrade
    sudo chroot ${DEST} apt-get remove linux-image*
    sudo chroot ${DEST} apt-get install live-boot
    sudo chroot ${DEST} apt-get install linux-image-amd64
    sudo chroot ${DEST} apt-get clean
    sudo chroot ${DEST} apt clean
    
    # Umount the special files:
    sudo umount ${DEST}/proc
    sudo umount ${DEST}/dev/pts
    sudo umount ${DEST}/dev
    sudo umount ${DEST}/sys
    
    # Delete unwanted files:
    [ -n "$DEST" ] && sudo find ${DEST}/var/mail ${DEST}/var/lock ${DEST}/var/backups ${DEST}/var/tmp -type f -exec rm {} \;

    # Delete only OLD log files:
    [ -n "$DEST" ] && sudo find ${DEST}/var/log -type f -iregex '.*\.[0-9].*' -exec rm -v {} \;
    [ -n "$DEST" ] && sudo find ${DEST}/var/log -type f -iname '*.gz' -exec rm -v {} \;
    
    # Clean current log files:
    [ -n "$DEST" ] && sudo find ${DEST}/var/log -type f | while read file; do echo -n '' | sudo tee $file; done
    
    # Clean Pakcage cache:
    [ -n "$DEST" ] && sudo rm -v ${DEST}/var/cache/apt/archives/*.deb
    
    # Remove old kernel and initrd in the partition where will be installed the live system: 
    sudo rm -f /media/$USER/LIVE/live/initrd.img*
    sudo rm -f /media/$USER/LIVE/live/vmlinuz*    
    
    # Copy new kernel and initrd in the partition where will be installed the live system: 
    sudo mv -f ${DEST}/boot/initrd.img* /media/$USER/LIVE/live/initrd.img
    sudo mv -f ${DEST}/boot/vmlinuz* /media/$USER/LIVE/live/vmlinuz
    
    # Remove old shquashfs in the partition where will be installed the live system: 
    sudo rm -f /media/$USER/LIVE/live/filesystem.squashfs
    
    # Make the new squashfs:
    sudo mksquashfs ${DEST} /media/$USER/LIVE/live/filesystem.squashfs -xattrs -processors 4 -noappend -always-use-fragments

/media/$USER/LIVE/ is where the live system partition is mounted.
   
Then I boot the live system placed on a partition with the kernel options: toram boot=live

Edit: When I run df command, it tells me that /dev/shm is mounted on /run/live/medium. The command mount | grep medium tells me that /dev/shm is also mounted on /usr/lib/live/mount/medium. It seems the system keeps in RAM a copy of the partition where is the squashfs. When I want to umount /run/live/medium, it tells me that it is impossible because the target is active. But I have successfully umounted /usr/lib/live/mount/medium. So I wonder if these problems are linked and if there is a way to umount /run/live/medium ?

How do I find a live linux distribution with a contain at least a specific set of software that I want? If you might be wondering, I am trying to find a live linux distribution (can be live dvd or live cd or live usb) that contains veracrypt and libreoffice that is out of the box (without the need to install).

I've been making a bootable, CLI Alpine Linux recovery disk, but Cfdisk can't find any disks to partition, neither does setup-disk, what are the steps I need to take to have a functioning partition manager on a live Alpine Linux?

I am trying to create a debian install image using a live-build tool. But during installation, the custom kernel I added is not used. I am trying to create a debian install image using a debian live build. My configuration looks like this:

lb config --distribution bullseye --debian-installer netinst --debian-installer-distribution bullseye --debian-installer-gui false --architecture amd64 --archive-areas "main contrib non-free" --binary-filesystem ext4 --system normal --linux-packages linux-image-5.10.180

I put kernel deb packages in a folder config/packages.chroot, deb package name with kernel ending with "_amd64". Also I add the following hook to the folder config/hooks/normal:

#!/bin/sh

set +e

apt -y remove linux-image-5.10.0-*

# make initramfs for installed kernels:
update-initramfs -c -k all

ln -s /boot/initrd.img-5.10.180 /boot/initrd.img
ln -s /boot/config-5.10.180 /boot/config
ln -s /boot/System.map-5.10.180 /boot/System.map
ln -s /boot/vmlinuz-5.10.180 /boot/vmlinuz

update-grub

set -e

Then start lb build The custom kernel is added to the live image, but the custom kernel I added is not used during installation. Please tell me what am I doing wrong.

I'm trying to create a custom Debian live-cd with live-build and debian-installer . I need a "Desktop" Debian Installer . As described in the manual: > "Desktop" Debian Installer: Regardless of the type of Debian Installer included, d-i can be launched from the Desktop by clicking > on an icon. This is user friendlier in some situations. In order to > make use of this, the debian-installer-launcher package needs to be > included. > > Note that by default, live-build does not include Debian > Installer images in the images, it needs to be specifically enabled > with lb config. Also, please note that for the "Desktop" installer to > work, the kernel of the live system must match the kernel d-i uses for > the specified architecture. For example: > >

> $ lb config --architectures i386 --linux-flavours 586 \
>     --debian-installer live 
> $ echo debian-installer-launcher >> config/package-lists/my.list.chroot
>

So, I used lb config to create a live-cd with debian-installer and debian-installer-launcher included and a kernel matching d-i's kernel version. I don't want to install the live system to disk, so I pass --debian-installer cdrom to install Debian by fetching and installing .deb packages using debootstrap, from local media.

lb config \
  --apt-recommends false \
  --apt-indices false \
  --architectures amd64 \
  --binary-images iso-hybrid \
  --debian-installer cdrom \
  --debian-installer-gui true \
  --distribution bullseye \
  --linux-packages "linux-image-5.10.0-20"

cat  config/package-lists/my.list.chroot
user-setup
sudo
debian-installer-launcher
task-lxde-desktop
EOF

lb build

The whole build process occurred well and finished with a live-image-amd64.hybrid.iso file. I successfully booted this ISO and started the live-cd, but when I click on Menu > System Tools > Install Debian the Install process is stuck at the Configure the package manager step and I can't proceed. The Start Installer option from the GRUB menu works nicely. I found this old bug report on Debian mail list : > Unfortunately, what you're probably running into is a battle between > the live image and the installer about what to do with the network. > The live image will configure the network one way (usually > NetworkManager), then the installer will attempt to configure it its > own way (using ifupdown, dropping connection in the live system). > There are a couple of possible workarounds I can think of (but have > not tested): > > 1. disconnect the network in the live system before doing an install and see what happens > > 2. run the installer with the network still up in the live system, but don't configure the network (d-i doesn't really give you an option to > do this; choose a network interface you know will fail because it's > not plugged in). since the live-installer installs from the contents > of the image, it doesn't actually need the network. unfortunately, > configuration of apt and the network then becomes a post-install step > the user has to deal with later. But none of the workarounds work. How can I create a live-cd that launches debian-installer and works properly?

For pxe boot I need iso Ubuntu. The problem is when Clients requests iso from the Server and iso is Standard Desktop Image (around 1.5 GB), Clients just do not have enough RAM... So I need just Live CD with no option 'Install Ubuntu' Is it possible to download only Live CD Image and if it is please share the link. Thanks in advance!

When I load the LIVE version of Debian 11 (xfce edition),I can't login using the login and password live / user,but I should use root / root. On the preseed file I'm using root / root as login / password : d-i passwd/root-password password root d-i passwd/root-password-again password root BUT,I have already tried to change the root password with another password,but it hasn't affected the live session. I still should use root /root otherwise it says "access denied". I'm confused. Where are stored the default user and password used by the LIVE session ? and most of all,why has this information been removed ? I think that I haven't modified it by my own will. In other terms,when I boot the LIVE session I should enter root/root. I don't want to do this. I want that xfce starts automatically like it happens with the untouched ISO image. Instead, on my case,I have modified something that I'm not able to realize and for this reason xfce does not start automatically anymore,but I should enter root/root (in the LIVE session). If you look on internet you will read that the default login and password for the Debian live is user / live. So there was at least some Debian live systems that used or use them. If Debian 11 xfce edition does not use user / live,there is another question to solve : why in my case xfce does not start automatically (but it requires login and password) as it does on the unaltered ISO image ? and what should I do to enable the automatic login for xfce in the LIVE session ? Thanks.

This is bit complicated question let me explain what is expected: I know that we can add GRUB menuentry with location of ISO file and boot from ISO using GRUB entry. (i.e [this](https://askubuntu.com/a/340171/256099) method) But suppose that: - I've ISO file of a GNU/Linux (say Trisquel 7.0) stored in computer (hard-disk) say at /dev/sda3/ - I want to install it on /dev/sda4 - I've Ubuntu 14.04 installation (bootable) disk from which I can install or try the live system. - Consider I've no operating system installed currently or installed system is crashed/corrupted (nothing to do with current boot-loader) The question is: With the Installation disk, running live environment (say try without installing of Ubuntu 14.04), Can I boot from the ISO (of Trisquel 7.0) from /dev/sda3 and install that system on /dev/sda4? How do I? Note:I agree that it is better to create/burn live disk/USB of the system I want to install from iso but If there is no disk/usb available right now then Can I do such operation mentioned in question? I think there is one possible technique: Install GRUB from (Ubuntu's) live environment on HDD pointing the path of ISO (Trisquel) that I finally want to boot from! How to?

I wanted to see what files are added on top of ISO 9660 when LiveUSB Linux is running. When booted with persistence upper and work folders are on USB drive clearly seen. I run mount on Linux booted from LiveUSB "usual way" (w/out persistence) and saw / is mounted via overlayfs and upperdir=/cow/upper. But sudo ls /cow gives no such file or directory. Where is /cow and how to see its contents? Added 1: I was able to extract contents of initrd from liveUSB via unmkinitramfs (see https://unix.stackexchange.com/a/495524/446998) $ find . -type f -exec bash -c 'cat {} | grep "/cow/upper" && ls -l {}' \; if [ ! -d /cow/upper ]; then mkdir -p /cow/upper /cow/lost+found|/cow/upper|/cow/log|/cow/crash|/cow/install-logs-*) continue ;; mv "$cow_content" /cow/upper mount -t overlay -o "upperdir=/cow/upper,lowerdir=$mounts,workdir=/cow/work" "/cow" "$rootmnt" || panic "overlay mount failed" -rw-r--r-- 1 alex alex 33834 Jun 24 2020 ./main/scripts/casper Next step I envision is to understand how /cow is created because is not see in contents of initrd