I want to customise an amnesic Debian environment (like Kali Live CD) with everything (Users, background, icons, etc.) set up to work the way I need. This OS should be inside a memory stick, and, most important, it has to have an encrypted partition I can mount and unmount whenever I want to save persistent data.
View 5 RepliesI have Lenny installed. How to create, using live-helper customized Live USB with a persistent /home partition on this USB stick, to save changes between boots?
View 6 Replies View RelatedI'd like to create my own custom Debian live CD — the idea being to have my own rescue CD with my favorite Debian tools installed. I read about bootcd and was going to give that a try, after creating the ideal system in a qemu virtual machine.
How much exactly can you install on a system so that bootcd can still fit it on a CD? I'm presuming there is some kind of compression involved. When I tried to create my VM, I coudln't get Jessie + LXDE to install onto a 2GB virtual drive (net install) so naturally I'm wondering what I'm going to be able to put on a 700MB CD.
I need to have a persistent Debian install on a thumbdrive to run a computer that is currently diskless (dead hard drive). So far I've managed to get it to boot Squeeze live beta by setting up the thumbdrive with UNetBootin, but it's not persistent. I found this, but step 6 is a mystery to me, as I can find no such command or package.
View 12 Replies View RelatedI'm trying to create a persistent live Jessie system on my 8GB USB drive.
If that matters, I'm currently on an Arch Linux system, and I partly followed what's on the relative wiki (Pages Create a new MBR for a USB stick, Manually create a USB flash installation and Install Syslinux), plus a CrunchBang post explaining how to make a persistent live USB out of any Jessie-deriving distro (like their BunsenLabs Hydrogen).
The problem is, even if Debian boots up more than fine, the system isn't persistent at all.
Here's what I did (I know some passages are redundant, but still...):
Downloaded the Cinnamon flavor of Jessie via torrentErased the old MBR
Code: Select all# dd if=/dev/zero of=/dev/sdb bs=512 count=1 && syncCreated a 1.1G W95 FAT32 (LBA) active partition and used the remaining space on a Linux partitionFormatted the first to FAT32 and labelled it "Debian64". Formatted the second to ext4 and labelled it "persistence"
Code: Select all# mkfs.vfat -n Debian64 /dev/sdb1
# mkfs.ext4 /dev/sdb2 -L persistence
Mounted the first partition and the iso
[Code] ....
I've created live squeeze usb-hdd and if I boot first time the udev system writes the MAC address of the network interfaces into /etc/udev/rules.d/70-persistent-net.rules.Because I use full persistence, the file is there on the next boot and I don't get network running automatically on other computers. My problem is, howto remove 70-persistent-net.rules every time during the startup?
View 5 Replies View RelatedHow to enable persistent logging with systemd? I find it really weird that all this machinery that is systemd doesn't store persistent logs, what if I'm trying to retrieve some information regarding previous boots?
For instance: I have random suspend issues, after rebooting the computer there's no trace left in the logs of what happened, and furthermore (at least in Jessie) I can no longer see a pm-suspend log.
So, at first it sounds like all you have to do is edit journald.conf setting #Storage=auto to "persistent" and create the /var/log/journal directory, but then reading here /usr/share/doc/systemd/README.Debian
Code: Select allEnabling persistent logging in journald
=======================================
To enable persistent logging, create /var/log/journal and set up proper permissions:
install -d -g systemd-journal /var/log/journal
setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal
and here [URL] ....
There are two main reasons why I decided to not enable persistent logging just yet ....
We did get corrupt journal files in the past where the journal then no longer worked at all [1]. With volatile you can just reboot and have a clean state again. Admittedly, the journal has seen a lot of improvements in the mean time and hopefully is more robust, so this point is no longer true.
We still install rsyslog by default. That means we get store them twice. This is something we don't want to do atm.
I have a problem defining persistent device naming on a Debian Lenny server.I have:RAID1 controller on the server machine with two SCSI disks.external storage with RAID5. I have / mount on the first partition on the server SCSI disk and /storage mount on the external storage.
I'm experiencing a problem: The system recognizes the system disk (RAID 1), as sda or sdb - randomly.I want: To control the recognition, and tell the system that sda (sda1) will always be the system disk.The motivation: GRUB is configured to work with sda, and when the system disk doesn't, boot process fails, and I end up in the initramfs shell-like interface.
Booting the kernel
.
.
.
mount:mounting /dev on /root/dev failed: No such file or directory
mount:mounting /sys on /root/sys failed: No such file or directory
[code]....
I installed few days ago Debian Jessie (Linux server-1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64 GNU/Linux) for some tests.I tried to install iptables-persistent with the command "apt-get install iptables-persistent".During the install process, I got the following message :
Code: Select allPreconfiguring packages ...
Selecting previously unselected package netfilter-persistent.
(Reading database ... 31677 files and directories currently installed.)
Preparing to unpack .../netfilter-persistent_1.0.3_all.deb ...
Unpacking netfilter-persistent (1.0.3) ...
Selecting previously unselected package iptables-persistent.
[code]....
Some talks about cups, acpid, ipv6 or systemd but nothing has solved the issue in my case.I used iptables-persistent many times with older debian versions.
I have created live persistent usb-hdd (fat32) image, put into USB stick, but now I should create persistent live-rw partition. How this persistent partition should be formatted? Should I format with ext2, or fat32?
View 1 Replies View RelatedI want to create a LiveDVD with lots of packages that do not exist in repos. Stuff that I built from source...
OpenFOAM with my own customized solvers and utilities, Tetgen, Netgen ,GMSH with OpenCascade support, BRL-CAD, Code-Aster, Salome Platform, Code Saturne, FreeMat, K3d...
Some of these apps have been compiled with Intel development toolbox, icc/ifort/mkl. Mainly scientific/Engineering stuff. How do I include all these packages in a custom Live Build...?
On macbook air 6.2, i've installed a Debian jessie mate DE, dual boot using refind. I'm currently fine-tuning it. I've made a script following powertop advice:
Code: Select all[newb@debian /etc/systemd/system]$ cat mba_kb_sp.sh
#!/bin/sh
echo 'auto' > '/sys/bus/usb/devices/1-3.1/power/control';
echo 'auto' > '/sys/bus/usb/devices/1-3.2/power/control';
echo 'auto' > '/sys/bus/usb/devices/1-5/power/control';
exit 0
[Code] ....
All seems to work fine, however when i check the sys file it didn't change. But I can start manually the systemd service and, this time, it works.
I've a problem running jessie on a XEN supervisor; my running kernel and the installed kernel image differ, because the host system forces the kernel at boot time. Current loaded kernel is
Code:
Select all$ uname -r
3.18.12
But I'm not able to install this version from the standard repository.
Code:
Select all# apt-cache search linux-image
linux-headers-3.16.0-4-amd64 - Header-Dateien für Linux 3.16.0-4-amd64
linux-image-3.16.0-4-amd64 - Linux 3.16 für 64-Bit-PCs
linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64
linux-image-2.6.32-5-xen-amd64 - Linux 2.6.32 for 64-bit PCs, Xen dom0 support
Now I'm facing issues loading kernel modules for iptables, because the module path does not exist. Is there an easy way to install a proper kernel image from the standard repositories?
I've setup my own repository which I want to use SSH as the protocol. I managed to get everything working with an SSH key using port 22. Now, I would like to change the SSH port. I've already changed it on the SSH/repo server. Now I can't figure out how to change apt to use a custom port on the client computer.
My sources.list file line which worked over port 22: deb ssh://user@1.1.1.1/home/user/repo lenny main contrib non-free I've tried: deb ssh://user@1.1.1.1:12345/home/user/repo lenny main contrib non-free and it fails and actually says "failed connecting to port 22"
Can this be done? I've searched google for hours and I getting nothing but unrelated data. I've read the man pages. The man page for apt.conf specified that you can set the port this way for HTTP, but doesn't mention anything about ssh ports.
I would like to compile a custom xen dom0 kernel. I installed a Debian Squeeze with precompiled xen kernel, and it works fine, but i would like to compile a custom dom0 kernel from source. I tried install kernel source apt-get source linux-2.6 how can I patch this kernel source with xen? but i alway see only the domU kernel params.
View 3 Replies View RelatedI have squeeze and I've created my own custum kernel. Howto configure grub 2 to boot with this custom kernel automaticaly?
View 5 Replies View RelatedI want to build my own binary package that replaces several from the repositories.But then whenever I install something that depends on libffado2, aptitude wants to uninstall mypkg and install libffado2. Why doesn't Provides work here?
View 3 Replies View RelatedMy university has a secure wireless network that has the following specs: WPA2, 1st Authentication TTLS, 2nd Authentication PAP, Encryption CCMP or AES, Thawte_Premium_Server_CA certificate and username and password.
I have never gotten this to work with wicd. First of all, wicd does not have a default template for this configuration. This led me in the past to quickly install Network-Manager (on top of XFCE...). While this has worked for me just fine. Recently I found out that this functionality is possible in wicd by creating your own template. So I did and here it is!
name = WPA2 Enterprise TTLS
author = Andres Cimmarusti
version = 1
[code]....
I did everything outlined here: [URL] (that is I saved the file as wpa2-ttls and then added this entry to the active file in /etc/wicd/encryption/templates/).
Sadly wicd's gui does not load my template!, the logs show no errors!...it simply refuses to take it. I cannot see any mistake in the above... do you?Is this some debian bug perhaps?This is the most important issue for me, before accepting to use wicd instead of NM.
I've compiled 2.6.35 for my eeepc, but I have noticed that resulting .deb file is 30mb large. After investigating i saw that modules (and maybe kernel) are compiled with debugging symbols enabled.I've checked my lenny router and modules there are without debugging symbols.So stock 2.6.26 from lenny comes without debugging symbols and linux-image .deb file is around 20mb.Stock 2.6.32-5-686 from squeeze comes with debugging symbols enabled - linux-image .deb here is 26mb. (I have used 2.6.32's .config file to build my kernel, then i did make oldconfig.)I guess this is what increase my kernel size, but how to disable it?Or maybe enable stripping of debugging symbols.
View 3 Replies View RelatedI want to build a custom system and I need your opinions. I have an old laptop which I want to configure as a system for troubleshooting purpose, my idea is to have multi-boot system with multiple root file systems, e.g. one root file system has only BIND to work as DNS server, another root file system has only Samba, etc., and I can choose which system to boot into from grub, or a custom menu after booting grub.
I thought of setting multiple partitions and install a full system on each one, but I thought that there might be a better way to do this, I'd like to hear your opinions.
I used make-kpkg to build the 3.0.0 source debian wheezy on a dual 3.4GHz Xeon/L1-16k/L2-1mb/800Mhz bus with 4GB PC2-3200 ECC ram and Ultra 320 SCSI, using CONCURRENCY_LEVEL=4 (2 hyperthreading cpus=4 cores). The build was slower than molasses in January! Top reported cpu usage total between 10% and 25%. Why won't the build use the amount of machine it has available. One footnote: I wasn't using swap space. It literally took over an hour to build the deb kernel package.
My notebook from 2003 is at least three times faster building the 3.0.0 debian kernel source. Is it possible that this might cause improvement: make -j4 KDEB_PKGVERSION=version deb-pkg
over
CONCURRENCY_LEVEL=4 make-kpkg --initrd --revision=123x kernel_image?
Could amd64 vs. i386 have some influence? Could the small processor caches on the XEON cpus have an effect. The 64-bit machine absolutely flies doing everything else. I'm miffed! I've used debian since woody, although I am not an expert, but I'm no slouch!
When I only change a driver file manually, for example /newkernel/linux-source-.6.32/drivers/gpu/drm/i915_drv.h, do I need to run "make config" or similar like "make menuconfig" or can I just skip? I mean these steps:
1.) apt-get install linux-source-2.6.32
2.) mkdir ~/newkernel/
3.) cp /usr/src/linux-source-2.6.32.tar.bz2 ~/newkernel/
4.) cd /newkernel/
5.) tar xjf linux-source-2.6.32.tar.bz2
6.) cd linux-source-2.6.32
7.) cp /boot/config-$(uname -r) ./.config yes "" | make oldconfig
8.) change the driver file /newkernel/linux-source-2.6.32/drivers/gpu/drm/i915_drv.h manually
8.) make-kpkg clean
9.) make-kpkg --rootcmd fakeroot --initrd --revision=custom.001 kernel_image kernel_headers
10.) dpkg -i *.deb
Is this way OK or do I miss something?
I' d like to apply this patch into my squeeze: [URL] Can someone pls explain howto apply driver diff patch into a custom kernel?
View 9 Replies View RelatedI'm attempting to create a persistent live USB. My flash drive is 32 GB, so I plan on creating a 8 or 16 GB ext casper-rw partition for my persistence (as described here.) I would like to have the remainder of the space available as an NTFS partition. However, most of what I'm reading indicates that only FAT32 is possible for a bootable Ubuntu USB.
I've been told that if I simply installed to USB drive as if it were a regular old HDD, it would be bootable and I could simply format the rest as NTFS. I'm wondering if this is true and why all these utilities I've found (Linux Live USB Creator, Universal USB Installer, etc...) insist on FAT32. Persistent (>4GB) bootable usb, with the rest of it a windows-recognizable NTFS partition?
I am running a live (4gb) USB of Fedora_14 with 768mb persistent storage. I am trying to add firmware for broadcom wireless link, as it is not natively supported. When I download tar, extract and copy missing firmware then reboot... all changes are reverted back. How do I make these changes persistent upon reboot.
View 8 Replies View RelatedI'd like to make a "live" USB, probably Ubuntu or a derivative such as Mint. How do I make it persistent? FWIW, this particular project will be primarily used for Ubuntu Studio. My hardware works fine with all versions of Ubu and Deb so there are no driver issues, simply the question of adding persistence to the stick
View 2 Replies View RelatedI've created a live and persistent USB boot of OpenSUSE 11.2 KDE according to the howto. It boots and works fine for about 5 minutes and then hangs. Only the mouse will move but I can't click on anything and it never comes back.
View 3 Replies View RelatedI have tried to create a persistent live usb thumb drive using Startup Disk Creator, but have not had any luck. I have tried running Startup Disk Creator from Linux Mint 9 xfce (currently installed on my machine) as well as from live sessions of ubuntu 11.04 Beta1 and xubuntu 11.04 Beta1. When using Startup Disk Creator in Linux Mint, I am able to set the slider to choose how much reserved space I want, but when I reboot, the USB stick does not load, I get an error message about an unknown name in the file. When using the live sessions of ubuntu or xubuntu, the section with the slider to choose how much of the usb stick to devote to the persistence file is greyed out. I get the same result whether I choose the xubuntu iso or the ubuntu iso as the source disc image. I have used the same USB stick and Startup Disk Creator to make persistent live installs before - is there something about 11.04 that does not allow persistence?
View 9 Replies View RelatedCurrently got a 32bit laptop and im running Ubuntu desktop 10.10 with the 32 bit version, If I upgrading my machine would i need to make a new persistent live usb for the 64 bit machine?
View 3 Replies View RelatedI have an old EeePC 701 4G netbook that I'm about to reconfigure for a friend who needs it to read PDF files, surf the net occasionally and do few other things. I'm going to install Ubuntu Netbook Remix, version 10.4.
Now, the 701 only has four gigabytes of internal storage, and I'm unwilling to spend money on it to expand its memory. When installed UNR takes up about 2.3 gigabytes, which leaves a bit more than a gig available for user data, and that's not much at all.
However, I could copy the live files off the memory stick in the main drive and use the remaining space for a casper-rw partition. Then it'd be only a matter of editing the bootloader in order to have a system that saves changes. This way I could fit the system on only 700 megabytes.
My question is: is there any drawback to running a persistent live off the main drive as the operating system? Something that would make me prefer eating up two thirds of the drive with the system, rather than just a fifth of it?
I imagine upgrades would eventually take up a lot of space, as they'd essentially copy a lot of the system in the live partition, but this is easily solvable by not performing them. I don't think the intended user would miss them, since she'll only really need three or four apps.