NSLU2-Linux
view · edit · print · history

Unslung.Ext3flash History

Hide minor edits - Show changes to markup

February 15, 2009, at 09:12 PM by mwester -- The wiki is for articles, not Q&A.
Deleted lines 19-26:

2008.04.19 - bluebear: Is it normal that after doing the .ext3flash trick the booting takes a small eternity?

20080515 - BenMcDui - It took my system 2min.

2009.02.08 - bluebear: Uhm... okay, my NSLU2 needs 5 minutes, don't know why. Fortunately (re)booting is not an operation performed very often by me.

February 08, 2009, at 10:08 PM by bluebear --
Changed lines 24-27 from:
to:

2009.02.08 - bluebear: Uhm... okay, my NSLU2 needs 5 minutes, don't know why. Fortunately (re)booting is not an operation performed very often by me.

May 15, 2008, at 02:55 PM by BenMcDui --
Added line 21:
May 15, 2008, at 02:54 PM by BenMcDui -- Comment added
Changed lines 21-22 from:
to:

20080515 - BenMcDui - It took my system 2min.

April 19, 2008, at 04:39 PM by bluebear --
Changed lines 20-22 from:

2008.04.19: Is it normal that after doing the .ext3flash trick the booting takes a small eternity?

to:

2008.04.19 - bluebear: Is it normal that after doing the .ext3flash trick the booting takes a small eternity?

April 19, 2008, at 04:38 PM by bluebear --
Added lines 17-22:

2008.04.19: Is it normal that after doing the .ext3flash trick the booting takes a small eternity?

Changed line 82 from:

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% of 32Mb left...., so it seems. However, the 4900 Kb allocated to the buffers is available for programs directly. Linux is just using this for buffering data for the disks. The 1736 kB which is free, is in effect wasted; it's not used for any purpose.

to:

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% of 32Mb left...., so it seems. However, the 4900 Kb allocated to the buffers is available for programs directly. Linux is just using this for buffering data for the disks. The 1736 kB which is free, is in effect wasted; it's not used for any purpose.

December 10, 2007, at 09:55 PM by Joop Verdoorn -- Added experience with script, after one year of use
Changed lines 29-31 from:

I've applied the spindown script, which copy all files from /dev and /var into a Ram-filesystem,taken from: http://www.nslu2-linux.org/wiki/FAQ/SpinDownUSBHarddisks. It is a bit dangerous, as the RAM-fs eats up more of the tot available 32Mb, while Ext3flash already has disabled swap....

to:

I've applied the spindown script, which copy all files from /dev and /var into a Ram-filesystem,taken from: http://www.nslu2-linux.org/wiki/FAQ/SpinDownUSBHarddisks. It is a bit dangerous, as the RAM-fs eats up more of the tot available 32Mb, while Ext3flash already has disabled swap.... After a year of using this script, I haven't had problems with this configuration. I can happily use the firefly mediaserver, nfs and the transmission torrent-client, and have no crashes.

Changed lines 76-79 from:

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% of 32Mb left...., so it seems. However, the 4900 Kb allocated to the buffers is available for programs directly. Linux is just using this for buffering data for the disks. The 1736 kB which is free, is in effect wasted; it's not used for any purpose.

Note after a few weeks of applying this script: I can happily use the firefly mediaserver, bash, samba and the libbt-library with the torrent-scripts, and have no crashes. Using Amulehowever is impossible; it crashes because of lack of memory after a few minutes. As I read more about Amule-crashes in forums and that people have observed that at least appr. 30 Mb is needed for the administration that emule-clients have to keep, I'm inclined to think that only applying Ext3flash is already enough to let Amule crash, as Ext3flash reduces SWAP-memory to zero.

to:

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% of 32Mb left...., so it seems. However, the 4900 Kb allocated to the buffers is available for programs directly. Linux is just using this for buffering data for the disks. The 1736 kB which is free, is in effect wasted; it's not used for any purpose.

September 30, 2007, at 06:39 PM by Lars Bager --
Changed lines 18-19 from:

Nothing is ever free - and these changes also carry a potential cost. Certain applications may use the "last-accessed" timestamp, and these may misbehave when the accessed-time stamp is disabled. Swap space is used when the operating system runs low on main memory. And since the NSLU2 has only a small amount of RAM to begin with, large applications or many applications at the same time may run the system out of memory.

to:

Nothing is ever free - and these changes also carry a potential cost. Certain applications may use the "last-accessed" timestamp, and these may misbehave when the accessed-time stamp is disabled (e.g. dropbear started via inetd). Swap space is used when the operating system runs low on main memory. And since the NSLU2 has only a small amount of RAM to begin with, large applications or many applications at the same time may run the system out of memory.

March 26, 2007, at 12:58 PM by Joop Verdoorn --
Changed line 79 from:

I can happily use the firefly mediaserver, bash, samba and the libbt-library with the torrent-scripts, and have no crashes. Using Amulehowever is impossible; it crashes because of lack of memory after a few minutes. As I read more of these Amule-crashes in forums, I'm inclined to think that only applying Ext3flash is already enough to let Amule crash, as Ext3flash reduces SWAP-memory to zero.

to:

I can happily use the firefly mediaserver, bash, samba and the libbt-library with the torrent-scripts, and have no crashes. Using Amulehowever is impossible; it crashes because of lack of memory after a few minutes. As I read more about Amule-crashes in forums and that people have observed that at least appr. 30 Mb is needed for the administration that emule-clients have to keep, I'm inclined to think that only applying Ext3flash is already enough to let Amule crash, as Ext3flash reduces SWAP-memory to zero.

March 26, 2007, at 07:15 AM by Joop Verdoorn -- Evaluation on script
Changed line 28 from:

Try-out, reducing the number of writing even more

to:

Reducing the number of writing even more

March 26, 2007, at 07:14 AM by Joop Verdoorn -- Evaluation on script
Added lines 77-79:

Note after a few weeks of applying this script: I can happily use the firefly mediaserver, bash, samba and the libbt-library with the torrent-scripts, and have no crashes. Using Amulehowever is impossible; it crashes because of lack of memory after a few minutes. As I read more of these Amule-crashes in forums, I'm inclined to think that only applying Ext3flash is already enough to let Amule crash, as Ext3flash reduces SWAP-memory to zero.

March 06, 2007, at 06:47 PM by Joop Verdoorn --
Changed line 76 from:

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% of 32Mb left.... When I play music on my Roku, streaming form the firefly, the amount of free RAM sinks to appr. 800. However, all seems stable. I 'll remove this try-out if it renders unstable.

to:

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% of 32Mb left...., so it seems. However, the 4900 Kb allocated to the buffers is available for programs directly. Linux is just using this for buffering data for the disks. The 1736 kB which is free, is in effect wasted; it's not used for any purpose.

March 05, 2007, at 11:24 AM by Joop Verdoorn --
Changed lines 67-68 from:

The result on my Unslung6.8 slug with Ext3flash also applied (32 Mb RAM is almost used now):

to:

The result on my Unslung6.8 slug with Ext3flash also applied:

March 05, 2007, at 11:23 AM by Joop Verdoorn --
Changed lines 29-31 from:

I've applied the spindown script, which copy all files from /dev and /var into a Ram-filesystem,taken from: http://www.nslu2-linux.org/wiki/FAQ/SpinDownUSBHarddisks. It is a bit dangerous, as the RAM-fs eats up more of the tot available 32Mb, while Ext3flash already has disabled swap..

to:

I've applied the spindown script, which copy all files from /dev and /var into a Ram-filesystem,taken from: http://www.nslu2-linux.org/wiki/FAQ/SpinDownUSBHarddisks. It is a bit dangerous, as the RAM-fs eats up more of the tot available 32Mb, while Ext3flash already has disabled swap....

Changed lines 67-68 from:

The result on my Unslung6.8 slug with Ext3flash also apllied (32 Mb RAM is almost used now):

to:

The result on my Unslung6.8 slug with Ext3flash also applied (32 Mb RAM is almost used now):

Changed line 76 from:

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% left.... When I play music on my Roku, streaming form the firefly, the amount of free RAM sinks to appr. 800. However, all seems stable. I 'll remove this note if it renders unstable.

to:

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% of 32Mb left.... When I play music on my Roku, streaming form the firefly, the amount of free RAM sinks to appr. 800. However, all seems stable. I 'll remove this try-out if it renders unstable.

March 05, 2007, at 11:21 AM by Joop Verdoorn --
Changed lines 31-66 from:

@@/.

  1. !/bin/sh
  2. /etc/init.d/mount_var_dev.sh
  3. Script section to create ramdisk for /var and for /dev
  4. disable the oom-killer to use the full swap

/sbin/sysctl -w vm.overcommit_memory=1

  1. From JNC : this command does not exist on my slug (release 2.7)
  2. better only use /var/log then the full /var
  3. following lines might need to be adjusted according to your OS and/or installed services

/bin/echo "Creating ramfs for /var/log:" /bin/mount -t ramfs ramfs /mnt -o maxsize=256 /bin/cp -rp /var/log/* /mnt/ /bin/mount -o bind /var/log /var/log.state /bin/mount -o bind /mnt /var/log /bin/umount /mnt

/bin/echo "Creating ramfs for /dev:" /bin/mount -t ramfs ramfs /mnt -o maxsize=256 cd /dev find . -print0 -mount | cpio -p -0 -d -m -u /mnt

  1. you can not use cp command for /dev

/bin/mount -o bind /dev /dev.state /bin/mount -o bind /mnt /dev /bin/umount /mnt

  1. Uncomment the following line when using debianslug
  2. mount devpts /dev/pts -t devpts
  3. Return and continue execution of system rc.

return 1

  1. [EOF]

@@

to:
 #!/bin/sh
 # /etc/init.d/mount_var_dev.sh
 # Script section to create ramdisk for /var and for /dev

 # disable the oom-killer to use the full swap
 /sbin/sysctl -w vm.overcommit_memory=1
 # From JNC : this command does not exist on my slug (release 2.7)

 # better only use /var/log then the full /var
 # following lines might need to be adjusted according to your OS and/or installed services
 /bin/echo "Creating ramfs for /var/log:"
 /bin/mount -t ramfs ramfs /mnt -o maxsize=256
 /bin/cp -rp /var/log/* /mnt/
 /bin/mount -o bind /var/log /var/log.state
 /bin/mount -o bind /mnt /var/log
 /bin/umount /mnt

 /bin/echo "Creating ramfs for /dev:"
 /bin/mount -t ramfs ramfs /mnt -o maxsize=256
 cd /dev
 find . -print0 -mount | cpio -p -0 -d -m -u /mnt
 # you can not use cp command for /dev
 /bin/mount -o bind /dev /dev.state
 /bin/mount -o bind /mnt /dev
 /bin/umount /mnt

 # Uncomment the following line when using debianslug
 #mount devpts /dev/pts -t devpts

 # Return and continue execution of system rc.
 return 1
 # [EOF]
Changed line 69 from:

bash-3.2# free

to:
 bash-3.2# free
March 05, 2007, at 11:18 AM by Joop Verdoorn --
Changed line 31 from:

@@/

to:

@@/.

March 05, 2007, at 11:18 AM by Joop Verdoorn --
Changed line 31 from:
to:

@@/

Changed lines 64-65 from:
to:

@@

March 05, 2007, at 11:17 AM by Joop Verdoorn --
Added line 65:
March 05, 2007, at 11:15 AM by Joop Verdoorn --
Changed lines 26-74 from:

Note: Unslung 5.5 only supports a flash disk as the root drive on USB Port 1. Unslung 6.x supports the use of a flash disk as the root drive on either USB port, although USB Port 2 is often preferred.

to:

Note: Unslung 5.5 only supports a flash disk as the root drive on USB Port 1. Unslung 6.x supports the use of a flash disk as the root drive on either USB port, although USB Port 2 is often preferred.

Try-out, reducing the number of writing even more

I've applied the spindown script, which copy all files from /dev and /var into a Ram-filesystem,taken from: http://www.nslu2-linux.org/wiki/FAQ/SpinDownUSBHarddisks. It is a bit dangerous, as the RAM-fs eats up more of the tot available 32Mb, while Ext3flash already has disabled swap..

  1. !/bin/sh
  2. /etc/init.d/mount_var_dev.sh
  3. Script section to create ramdisk for /var and for /dev
  4. disable the oom-killer to use the full swap

/sbin/sysctl -w vm.overcommit_memory=1

  1. From JNC : this command does not exist on my slug (release 2.7)
  2. better only use /var/log then the full /var
  3. following lines might need to be adjusted according to your OS and/or installed services

/bin/echo "Creating ramfs for /var/log:" /bin/mount -t ramfs ramfs /mnt -o maxsize=256 /bin/cp -rp /var/log/* /mnt/ /bin/mount -o bind /var/log /var/log.state /bin/mount -o bind /mnt /var/log /bin/umount /mnt

/bin/echo "Creating ramfs for /dev:" /bin/mount -t ramfs ramfs /mnt -o maxsize=256 cd /dev find . -print0 -mount | cpio -p -0 -d -m -u /mnt

  1. you can not use cp command for /dev

/bin/mount -o bind /dev /dev.state /bin/mount -o bind /mnt /dev /bin/umount /mnt

  1. Uncomment the following line when using debianslug
  2. mount devpts /dev/pts -t devpts
  3. Return and continue execution of system rc.

return 1

  1. [EOF]

The result on my Unslung6.8 slug with Ext3flash also apllied (32 Mb RAM is almost used now):

bash-3.2# free

              total         used         free       shared      buffers
  Mem:        30524        28788         1736            0         4900
 Swap:            0            0            0

I've got the firefly mediaserver and bash running alongside the original Linksys app and appr. 5% left.... When I play music on my Roku, streaming form the firefly, the amount of free RAM sinks to appr. 800. However, all seems stable. I 'll remove this note if it renders unstable.

March 02, 2006, at 06:48 AM by mwester -- Rewrote portions to reflect recent releases
Changed lines 1-14 from:

Implemented Changes in Unslung 2.13:

(These only happen if /.ext3flash is present at boot time)

  1. Remount root with -o noatime
  2. Remount /share/flash/data -o noatime
  3. Move all of /var and /dev to ramfs (This should use around 20KB of memory depending on the size of your logs)
  4. run swapoff /dev/sda to turn off swapping on a root flash drive.
  5. Note: Log files stored in /var will not be saved over shutdowns and reboots. This includes the miau logs which are now stored in /var/spool. If you need to keep log files over reboots and shutdowns consider adding a copy script to rc.reboot and/or rc.halt (note that doing this hasn't been tested yet - we're not sure if the slug runs rc.reboot or rc.halt on every different way that it shuts down or reboots).

  • To make this work on your system simply type: touch /.ext3flash and then reboot your system
  • Please report all issues and suggestions to the bug tracker.
  • These changes affect both the standard and able variants of the firmware.

to:

Special Handling of a Flash Drive for the Unslung Root Drive

Using a flash drive is often an attractive way to run an Unslung NSLU2. It's quiet, small, low-power, and low-cost.

However, they do have a significant disadvantage compared to the traditional hard-drive -- they wear out much, much faster.

A couple of simple changes to how Unslung uses the flash drive can greatly extend the life of the flash device:

  • Disabling swapping on the device.
  • Disabling the recording of the timestamp each time a file is accessed.

All that is required to instruct Unslung to make the necessary changes is to create a file named /.ext3flash after the system has been successfully unslung and rebooted. The following command will do the trick nicely:

 touch /.ext3flash

Once created, the changes will take effect at the next boot.

Potential Pitfalls

Nothing is ever free - and these changes also carry a potential cost. Certain applications may use the "last-accessed" timestamp, and these may misbehave when the accessed-time stamp is disabled. Swap space is used when the operating system runs low on main memory. And since the NSLU2 has only a small amount of RAM to begin with, large applications or many applications at the same time may run the system out of memory.

Technical Details

During the boot process, if the /.ext3flash file exists, the boot scripts will:

  • remount the root partition with -o noatime
  • remount the conf partition with -o noatime,sync
  • execute swapoff to turn off swapping on the root drive

Note: Unslung 5.5 only supports a flash disk as the root drive on USB Port 1. Unslung 6.x supports the use of a flash disk as the root drive on either USB port, although USB Port 2 is often preferred.

June 15, 2005, at 09:24 AM by dB -- The file needs to be in / not in /share/hdd/conf/
Changed line 11 from:
  • To make this work on your system simply type: touch /share/hdd/conf/.ext3flash and then reboot your system
to:
  • To make this work on your system simply type: touch /.ext3flash and then reboot your system
November 10, 2004, at 12:46 PM by tman --
Changed line 7 from:
  1. run swapoff /dev/sda to turn off swaping on a root flash drive.
to:
  1. run swapoff /dev/sda to turn off swapping on a root flash drive.
November 09, 2004, at 11:10 PM by rwhitby --
Changed line 2 from:

(These only happen if /.ext3flash is present)

to:

(These only happen if /.ext3flash is present at boot time)

Changed line 8 from:
  1. Note: Log files stored in /var will not be saved over shutdowns and reboots. This includes the miau logs which are now stored in /var/spool. If you need to keep log files over reboots and shutdowns consider adding a copy script to rc.reboot.
to:
  1. Note: Log files stored in /var will not be saved over shutdowns and reboots. This includes the miau logs which are now stored in /var/spool. If you need to keep log files over reboots and shutdowns consider adding a copy script to rc.reboot and/or rc.halt (note that doing this hasn't been tested yet - we're not sure if the slug runs rc.reboot or rc.halt on every different way that it shuts down or reboots).
Changed line 11 from:
  • To make this work on your system simply type: touch /.ext3flash and then reboot your system
to:
  • To make this work on your system simply type: touch /share/hdd/conf/.ext3flash and then reboot your system
Deleted lines 14-24:

Files that are modified in the last day on my slug:

/var/lock/samba/browse.dat
/var/log/messages
/var/log/messages.old
/var/log/samba/log.nmbd
/root/.miau
/dev/ptyp0
/dev/ttyp0

November 09, 2004, at 06:48 PM by ChrisE --
Changed line 7 from:
  1. run swapoff /dev/sda to turn off swaping on a root flash drive (People can modify this if they want swapoff -a)?
to:
  1. run swapoff /dev/sda to turn off swaping on a root flash drive.
November 09, 2004, at 06:46 PM by ChrisE --
Changed lines 1-2 from:

Planned Implementations:

These are mostly from TuneUnslungForUsbFlashDisk

to:

Implemented Changes in Unslung 2.13:

(These only happen if /.ext3flash is present)

Changed lines 6-7 from:
  1. Move /dev, /tmp, /var/run, var/spool to ramfs (Uses approximately 18kb of memory depending on size of logs)
  2. /var/lock/samba and /var/log are already ramdisks
to:
  1. Move all of /var and /dev to ramfs (This should use around 20KB of memory depending on the size of your logs)
Changed lines 8-9 from:
  1. These things would only happen if a file called /.flashroot existed with the current Unslung version number inside
  2. Need a mechanism to keep logs like the miau logs over time, but not write them to flash all the time, maybe save them upon shutdown or something? Yeah - I mave modified miau to put stuff in /var/spool - we should retain /var/spool over reboots - we have a rc.reboot diversion script facility.
to:
  1. Note: Log files stored in /var will not be saved over shutdowns and reboots. This includes the miau logs which are now stored in /var/spool. If you need to keep log files over reboots and shutdowns consider adding a copy script to rc.reboot.
Changed lines 11-16 from:

both 1 and 2 above are accomplished by:
mount -o remount,rw,noatime /dev/root /
swapoff -a
will turn off swapping

to:
  • To make this work on your system simply type: touch /.ext3flash and then reboot your system
  • Please report all issues and suggestions to the bug tracker.
  • These changes affect both the standard and able variants of the firmware.

November 09, 2004, at 03:30 AM by ChrisE --
Changed line 8 from:
  1. run swapoff -a to turn off swapping (Can we disable it just on one disk or the other?)
to:
  1. run swapoff /dev/sda to turn off swaping on a root flash drive (People can modify this if they want swapoff -a)?
November 09, 2004, at 03:27 AM by ChrisE --
Changed line 6 from:
  1. Move /dev, /tmp, /var/run to ramfs (Uses approximately 18kb of memory depending on size of logs)
to:
  1. Move /dev, /tmp, /var/run, var/spool to ramfs (Uses approximately 18kb of memory depending on size of logs)
November 08, 2004, at 11:56 PM by rwhitby --
Changed line 10 from:
  1. Need a mechanism to keep logs like the miau logs over time, but not write them to flash all the time, maybe save them upon shutdown or something?
to:
  1. Need a mechanism to keep logs like the miau logs over time, but not write them to flash all the time, maybe save them upon shutdown or something? Yeah - I mave modified miau to put stuff in /var/spool - we should retain /var/spool over reboots - we have a rc.reboot diversion script facility.
November 08, 2004, at 10:12 PM by ChrisE --
Changed lines 5-6 from:
  1. Remount /share/flash/data -o noatime
  2. Move /dev, /tmp, /var/run to ramfs
to:
  1. Remount /share/flash/data -o noatime
  2. Move /dev, /tmp, /var/run to ramfs (Uses approximately 18kb of memory depending on size of logs)
Changed line 8 from:
  1. Run swapon to disable swap device
to:
  1. run swapoff -a to turn off swapping (Can we disable it just on one disk or the other?)
Added line 10:
  1. Need a mechanism to keep logs like the miau logs over time, but not write them to flash all the time, maybe save them upon shutdown or something?
Changed lines 20-28 from:

Files that are modified in the last day on my slug:

/var/lock/samba/browse.dat /var/log/messages /var/log/messages.old /var/log/samba/log.nmbd /root/.miau /dev/ptyp0 /dev/ttyp0

to:

Files that are modified in the last day on my slug:

/var/lock/samba/browse.dat
/var/log/messages
/var/log/messages.old
/var/log/samba/log.nmbd
/root/.miau
/dev/ptyp0
/dev/ttyp0\\

November 08, 2004, at 12:01 PM by rwhitby --
Changed lines 6-7 from:
  1. Move /dev, /tmp, /var/log, /var/run to ramfs
to:
  1. Move /dev, /tmp, /var/run to ramfs
  2. /var/lock/samba and /var/log are already ramdisks
Changed lines 16-28 from:

will turn off swapping

to:

will turn off swapping

Files that are modified in the last day on my slug:

/var/lock/samba/browse.dat /var/log/messages /var/log/messages.old /var/log/samba/log.nmbd /root/.miau /dev/ptyp0 /dev/ttyp0

November 07, 2004, at 09:21 AM by ChrisE --
Deleted line 5:
November 07, 2004, at 02:27 AM by tman --
Deleted lines 2-3:
  1. remount root with -o noatime
  2. remount /share/flash/data -o noatime
Changed lines 4-6 from:
  1. move /dev, /tmp, /var/log, /var/run to ramfs
  2. Run swapon to disable swap device
  3. These things would only happen if a file called /.flashroot existed with the current unlsung version number inside
to:
  1. Remount root with -o noatime
  2. Remount /share/flash/data -o noatime
  3. Move /dev, /tmp, /var/log, /var/run to ramfs
  4. Run swapon to disable swap device
  5. These things would only happen if a file called /.flashroot existed with the current Unslung version number inside
Added line 12:
November 07, 2004, at 01:37 AM by Gerald L Clark --
Changed lines 3-7 from:
  1. Remount root with -o noatime
  2. Remount /share/flash/data -o noatime
  3. Move /dev, /tmp, /var/log, /var/run to ramfs
  4. Run swapon to disable swap device
  5. These things would only happen if a file called /.flashroot existed with the current Unslung version number inside
to:
  1. remount root with -o noatime
  2. remount /share/flash/data -o noatime
  3. move /dev, /tmp, /var/log, /var/run to ramfs
  4. Run swapon to disable swap device
  5. These things would only happen if a file called /.flashroot existed with the current unlsung version number inside

both 1 and 2 above are accomplished by:
mount -o remount,rw,noatime /dev/root /
swapoff -a
will turn off swapping

November 07, 2004, at 01:29 AM by tman --
Changed lines 3-4 from:
  1. remount root with -o noatime
  2. remount /share/flash/data -o noatime
to:
  1. Remount root with -o noatime
  2. Remount /share/flash/data -o noatime
Changed line 7 from:
  1. These things would only happen if a file called /.flashroot existed with the current unlsung version number inside
to:
  1. These things would only happen if a file called /.flashroot existed with the current Unslung version number inside
November 07, 2004, at 01:29 AM by tman --
Changed lines 3-7 from:
  1. Remount root with -o noatime
  2. Remount /share/flash/data -o noatime
  3. move /dev, /tmp, /var/log, /var/run to ramfs
  4. Run swapon to disable swap device
  5. These things would only happen if a file called /.flashroot existed with the current Unslung version number inside
to:
  1. Remount root with -o noatime
  2. Remount /share/flash/data -o noatime
  3. Move /dev, /tmp, /var/log, /var/run to ramfs
  4. Run swapon to disable swap device
  5. These things would only happen if a file called /.flashroot existed with the current Unslung version number inside
November 07, 2004, at 01:11 AM by ChrisE --
Changed line 1 from:

Planned Implementations:\\

to:

Planned Implementations:

November 07, 2004, at 12:41 AM by ChrisE --
Changed lines 1-7 from:

Under Construction

to:

Planned Implementations:
These are mostly from TuneUnslungForUsbFlashDisk

  1. remount root with -o noatime
  2. remount /share/flash/data -o noatime
  3. move /dev, /tmp, /var/log, /var/run to ramfs
  4. Run swapon to disable swap device
  5. These things would only happen if a file called /.flashroot existed with the current unlsung version number inside
November 06, 2004, at 11:34 PM by ChrisE --
Changed line 1 from:

Describe {{Ext3flash}} here.

to:

Under Construction

view · edit · print · history · Last edited by mwester.
Based on work by bluebear, BenMcDui, Joop Verdoorn, Lars Bager, mwester, dB, tman, rwhitby, ChrisE, and Gerald L Clark.
Originally by ChrisE.
Page last modified on February 15, 2009, at 09:12 PM