Comment 19 for bug 431040

  Code might be machine dependant in some way. Fed up with the poor performance (SLOW and fsck issues), I borrowed a mountall script someone else wrote, partially debugged it, and modified it to put all fsck runs in one place and give partial usplash support. Attached are the replacement script(still immature code and might act up if no encrypted device is delaying things)and mountall.conf file.

 This script sure as hell boots faster, and on both my intel Atom netbook and AMD Athlon single core machines mounts the bind mounted directories just fine.

  If the various problems in the mountall binary are not fixed by release, every user of Karmic may well have to use a script-and edit the damned thing to suit their machines in a worst case scenario.

  I've looked at the C code for the binary, and it sure as hell is long, though it's only one file. Given that it's job is to call external programs (mount and fsck), I'm not sure how much of an advantage the use of a compiled binary gives.

  Of course, a well-made mountall binary that treated fsck and mount as though they were shared libraries could give a hell of a speed boost once it's properly worked out, but writing this is far beyond my C skills.

> Date: Fri, 2 Oct 2009 16:05:15 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 431040] Re: separate /var and /var/tmp tmpfs dependency loop
>
> Last I tried this (yesterday or the day before or so) it still failed to
> boot.
>
> --
> separate /var and /var/tmp tmpfs dependency loop
> https://bugs.launchpad.net/bugs/431040
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/171222984/direct/01/