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

  • From: Stephan Assmus <superstippi@xxxxxx>
  • To: haiku-commits@xxxxxxxxxxxxx
  • Date: Mon, 12 Oct 2009 19:32:55 +0200

Hi Bruno,

On 2009-10-12 at 17:34:00 [+0200], Bruno Albuquerque <bga@xxxxxxxxxxxxx> 
wrote:
> 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.

Currently, the only servers being launched before the mount_server are the 
registrar, debug_server, app_server and net_server. The way the 
mount_server is started requires messaging to work, so the registrar needs 
to be running. The mount_server is also a BApplication, so the app_server 
needs to run as well. That leaves the MIME data base and app_server add-ons 
as problems if home is on another partition. In any case, the mount server 
is very little code and it wouldn't be a big problem to change it so that 
it can run even before anything else. But as you are well aware, it was and 
is still possible to hack the Bootscript to mount other partitions as the 
first thing, so the issue is not a pressing one. What I found very annoying 
are the issues I pointed at in the commit message, those are fixed now and 
so I don't feel any personal itches anymore with regards to mounting stuff 
at the right time... :-) Feel free to mess with the mount_server as you see 
fit to solve remaining problems.

Best regards,
-Stephan



Other related posts: