[haiku-commits] Re: r33555 - in haiku/trunk: data/system/boot src/apps/diskusage src/kits/tracker

  • From: "Bruno Albuquerque" <bga@xxxxxxxxxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Mon, 12 Oct 2009 16:34:00

On Mon, 12 Oct 2009 16:52:17 +0200 (CEST), superstippi@xxxxxx said:

> * Removed auto mounter code from Tracker.
> * Tracker forwards auto mounter related messages to the mount_server.
> * Rewrote AutoMounterSettings to not know AutoMounter and use
>   the layout-management.
> * Moved the "Eject When Unmounting" setting into the Mount Settings.
> * Launch the mount_server during boot, but delay the script until all
>   previously mounted volumes have been mounted. This solves some 
> annoying
>   timing bugs during boot. For example when you have desktop 
> backgrounds
>   on other volumes and some servers don't deal well with the 
> situation
>   of links to add-ons on other volumes becoming valid with a delay...
> * src/kits/tracker/Commands.h includes the private headers/private/
>   mount/MountServer.h header, which made adjustments to the DiskUsage
>   Jamfile necessary.

Hi stippi.

I was thinking here and although this solution of a mount server solves 
some problems, it will not solve all. Ideally we still need a way to 
mount all relevant partitions during boot as the first step before 
trying to do anything else as who knows how the user may have 
configured his partitions? I, for instance, have my entire home dir in 
a partition that is not the boot one and this makes it required to 
mount it before trying to start anything.

Also, I saw the comment about Login needing to be updated. I guess when 
we go multiuser for real the mount_server should not be dependant on a 
user logging in unless, of course, he will only handle the runtime disk 
mounting while the disk mounting during boot would be handled by 
something else.


Other related posts: