Live System Persistence
 
 
eco2geek hat folgendes geschrieben:: 
This would be a good time to link to the Debian Live wiki on  how to add a "persistent home" to your "poor man's installation".
  
Well, it's all there in 'man:/live-boot'    , if only one knew which manual to look in    
 
 
eco2geek hat folgendes geschrieben:: 
Tejas hat folgendes geschrieben:: 
Seems to me to be more flexible to have a file which one can move around, rather than to be bound to a particular partition.
 
Why? Are you planning on moving around the 1.1 GB squashfs file between partitions, too?     
 
Actually my just over a year old off-the-shelf 250GB system is beginning to look a bit small when one looks at the 1000 GB off-the-shelf systems coming on offer in the local supermarkets:!: Coming from an 8GB system in danger of cluttering up the disk with unwanted partitions    
 
 
eco2geek hat folgendes geschrieben:: 
Seriously, those instructions say the "live-rw" file just has to be at the root of a partition that can be found and read. It's not tied to any particular partition.
 
Which brings me on to the next puzzling thing ...
 
 
# Create an empty ramdisk image
Code: 
$ dd if=/dev/null of=live-rw bs=1G seek=1 # for a 1GB sized image file
 
Zitat: 
Are you planning on moving around the 1.1 GB squashfs file between partitions, too?     
 
How come you know this results in a 1.1 GB file?
 
 
Code: 
$ sudo mount /dev/sda5 px2
 
$ dd if=/dev/null of=px2/live-rw bs=1G seek=1
 
dd: memory exhausted
 
 
Maybe partition without iso file
 
Code: 
$ dd if=/dev/null of=p8/live-rw bs=1G seek=1
 
dd: memory exhausted
 
 
 
Looks like it"s trying to create a 1 GB buffer, but have just under 1 GB ram., so maybe 1 MB buffer will succeed. at second best
 
Code: 
$ dd if=/dev/null of=px2/live-rw bs=1M seek=1024
 
0+0 records in
 
0+0 records out
 
0 bytes (0 B) copied, 2.9091e-05 s, 0.0 kB/s
 
 
 
Resulting stats
 
Code: 
 
$ ls -l px2
 
drwxr-xr-x 2 root root 4096 May 19 13:04 hx
 
drwxr-xr-x 2 kanotix kanotix 4096 May 19 00:15 kx
 
-rw-r--r-- 1 kanotix kanotix 1073741824 May 19 19:13 live-rw
 
drwx------ 2 root root 16384 May 18 22:29 lost+found
 
$ df -h px2
 
Filesystem Size Used Avail Use% Mounted on
 
/dev/sda5 4.0G 2.4G 1.5G 63% /home/kanotix/px2
 
Which do not tally
 
Code: 
$ ls -l px2/hx
 
-rw-r--r-- 1 kanotix kanotix 1131413504 May 8 01:58 kanotix-2.6.38rc6.iso
 
$ ls -l px2/kx
 
-r--r--r-- 1 kanotix kanotix 20229456 May 11 15:17 initrd.img
 
-rw-r--r-- 1 kanotix kanotix 1319108608 May 18 17:58 kanotix-2.6.38.iso
 
-r--r--r-- 1 kanotix kanotix 4534736 May 11 15:17 vmlinuz
 
 
as sum of all files should exceed 3 GB, 
 
 
# Make ext2 mountable file system
 
Code: 
$ /sbin/mkfs.ext2 -F px2/live-rw
 
mke2fs 1.41.12 (17-May-2010)
 
OS type: Linux
 
Block size=4096 (log=2)
 
65536 inodes, 262144 blocks
 
13107 blocks (5.00%) reserved for the super user
 
First data block=0
 
Maximum filesystem blocks=268435456
 
8 block groups
 
32768 blocks per group, 32768 fragments per group
 
8192 inodes per group
 
Superblock backups stored on blocks:
 
32768, 98304, 163840, 229376
 
Writing inode tables: done
 
Writing superblocks and filesystem accounting information: done
 
but seems to have gone through OK  :So, all I can assume is that this 'dd' creates a file for which space is not allocated, but which grows dynamically up to the max 1 GB. 
 
 
Question: should I wish to move this file to another partition do I use 'mv' or 'dd'? 
 
 
& to be compleat. |