All of lore.kernel.org
 help / color / mirror / Atom feed
From: PFC <lists@peufeu.com>
To: reiserfs-list@namesys.com
Subject: Re: Relocating files for faster boot/start-up on reiser(fs/4)
Date: Mon, 18 Sep 2006 11:36:44 +0200	[thread overview]
Message-ID: <op.tf2ibi00cigqcu@apollo13> (raw)
In-Reply-To: <200609151520.39826.lists@qutek.net>


	Windows already does this.

	It has a service which monitors filesystem usage, and writes data to disk  
; the defragmenter uses this data to lay the files on disk so that boot is  
very fast.

	However think it optimizes only the time to the login screen ; so windows  
boot is extremely fast ; of course, once you have logged in, you have to  
wait forever until all the crap system tray apps launch themselves and eat  
all your RAM...

	My own repacker is very simple, and it handles any filesystem !

- boot from Kanotix CD
- tar cv /mnt/my_disk | lzop -c | ssh -c blowfish other_machine "cat  
>backup.tar.lzo"
- umount, mkfs, mount
- ssh -c blowfish other_machine "cat backup.tar.lzo" | lzop -cd | tar xv

	You can also use an USB disk, or other disks in the machine. The effects  
are pretty visible.
	I do the first part often to make a full disk backup to a USB harddrive.

	Anyway, IMHO the best way to have a super responsive system would be :

Have a daemon which monitors which files, or parts of files, are read, and  
in what context :

- boot to fully loaded KDE/Gnome
- launching an application

You already have this apparently...

The repacker would then use this information to lay files on disk (just  
like windows does).

Then, the daemon would trigger readahead, when booting or detecting the  
launch of an application, and read everything in (which would be a nice  
sequential read)...


  parent reply	other threads:[~2006-09-18  9:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 20:51 Relocating files for faster boot/start-up on reiser(fs/4) Quinn Harris
2006-09-13 21:10 ` Peter
2006-09-14  3:10   ` Quinn Harris
2006-09-14 19:55     ` David Masover
2006-09-14 22:09       ` Quinn Harris
2006-09-14 22:23         ` David Masover
2006-09-15  5:15           ` Toby Thain
2006-09-15 21:20             ` Quinn Harris
2006-09-15 22:27               ` David Masover
2006-09-16  0:01                 ` Quinn Harris
2006-09-16  8:59                   ` David Masover
2006-09-18  9:36               ` PFC [this message]
2006-09-18 22:32                 ` Quinn Harris
2006-09-14 14:01   ` cmaurand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=op.tf2ibi00cigqcu@apollo13 \
    --to=lists@peufeu.com \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.