Here is another thought. I'm not confident at all that the problem is with shutting down the system at all. I've noticed that files created on the pendrive when running from the pendrive are often corrupt. One of the things I use pendirive linux for is downloading podcasts while on the road. Often the files end up scrambled together randomly. It's not the podcatching software causing the problem. The files seem to be intact when they are downloaded. The file scrambling seems to happen when transferring files from the pendrive to the mp3 player, memory card or other pendrive. Also, configuration files set up on the device often seem to be corrupt (ie. the config files for frostwire, amule and some other apps were corrupt on my pendrive. Copying working files from my harddrive fixed the problem. I recently tried to build an Ubuntu pendrive for a colleague by copying the fat32 files from my pendrive over to his. The files appeared to be the correct size but were corrupt. I ended up having to boot to Windows and transfer the files from there to get it to work. Then I had to copy my working config files for several apps separately to get them to work. Perhaps the whole problem is that files on usb devices are not being handled properly at all when running from the pendrive?
On Wed, Mar 5, 2008 at 11:21 PM, Mike <[EMAIL PROTECTED]> wrote: > Just a thought - and I am the first to admit my limited knowledge - but > maybe it is not completely the code that is shutting down the system > that is causing the issue. Maybe the more recent version of upstart is > somehow creating a system state that is not created by the earlier > version of upstart. and it is this system state that is not handled > correctly by the code that shuts down the system. I.e. the code that > shuts down the system could be identical, but maybe it is trying to > handle a state that does not exist when the earlier version of upstart > is used. I have no idea whether that is possible . . . just thinking > out loud. I.e. it is an interaction, not just the upstart code. > > -- > failure to umount local filesystems - gutsy tribe 2 > https://bugs.launchpad.net/bugs/125702 > You received this bug notification because you are a direct subscriber > of the bug. > ** Attachment added: "unnamed" http://launchpadlibrarian.net/12964502/unnamed -- failure to umount local filesystems - gutsy tribe 2 https://bugs.launchpad.net/bugs/125702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
