On Wed, Mar 25, 2009 at 6:11 PM, cpu <[email protected]> wrote: > > On windows the exe/dll separation it was meant to simplify upgrade but > in practice the > exe changes frequently enough that we still need to support exe > upgrading in place.
(resending) While the exe changing issue is annoying, and we have to handle in-use file swapping, it's not the main issue with updates. When you update in place, resources can be changed, removed, etc. So let's say that some dll hasn't been loaded yet, but then an autoupdate happens. Now you trigger loading the dll, and you crash, because this kind of forwards compatibility is never tested (nor should it be). This can happen with simple data files as well (although we don't have many of those at the moment). This is why all of the loaded code and resources are in a versioned directory (minus dictionaries, but that's a separate issue). How will in-place updating work on the Mac and Linux? Erik > > We always wanted to have a do nothing exe that just loads the chrome > dll but that never > happened, reasons: 1) the sandbox 2) breakpad 3) google_update. All > this things are living on > the exe. > > We could move to a no-dll world easier than moving to a dumb exe > world. > > > On Mar 24, 9:50 pm, Craig Schlenter <[email protected]> wrote: >> On Tue, Mar 24, 2009 at 8:45 PM, Thomas Van Lenten<[email protected]> >> wrote: >> >> [snip] >> >> > Linux currently builds as one executable also. But Adam proposed we create >> > a second executable (via hardlink?) for AppArmor as a sandbox? >> >> Will a hard link work for selinux btw.? I'm under the impression that >> selinux is inode based so Fedora etc. would have to do something >> different there. >> >> As for the shared library overhead that Dean mentioned, there is some >> interesting work on linux that is mentioned >> herehttp://lwn.net/Articles/192624/... hopefully some of that has made it >> into the default toolchain by now. >> >> Pre-linking is enabled by default on Fedora btw. ... I'm unsure of >> other distributions. >> >> --Craig > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
