[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: Wed, 14 Oct 2009 08:21:36 -0300

Stephan Assmus wrote:

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.

In my specific use case (the entire home dir is in a different partition ) even this does not work. I guess the problme here is two fold:

1 - Some server wants settings from the home dir and it is still not available when it requests it. 2 - Some servers still read/write to the home dir which is obviously not desired (when we go multiuser, what do do before the user logs in? Not start the servers?

In any case, my solution was simply to explicitly mount the partition I want as the first thing in Bootscript and that works.

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.

The problem could be the mime database. What happens is that although Tracker starts, it does not open any windows (not even the Desktop window).

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.

Yep. That's what I do. What I am thinking is that we ever reach some kind of mainstream status we may even have something like Linux where you can have a very small boot partition that mounts everything else in other partitions and, in this case, we would need something like fstab, able to mount devices *REALLY* early in the boot process.

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.

Ok. I may take a look at it to see if I can at least fix the problem I have with the home dir in a different partition. This would not address every possible option but will at least covers most of them (and, more importantly, wull cover my use case ;) ).


Other related posts: