Hi Terry,
> > As has already been covered, the new libraries will be used by new
> > processes without a reboot. There's another method of having a daemon
> > replace itself with an updated version...
>
> So in fact, it is possible to replace libraries in a running Linux system
> without a rebo
On Saturday 15 Mar 2014 16:35:05 Ralph Corderoy wrote:
> As has already been covered, the new libraries will be used by new
> processes without a reboot. There's another method of having a daemon
> replace itself with an updated version...
So in fact, it is possible to replace libraries in a runn
Hi Terry,
> That link says that the only reason that Windows has to reboot is that
> it holds locks on files that are in use so it cannot update them.
> Linux doesn't do this so it can replace files, but they won't get used
> until after the next reboot.
As has already been covered, the new libra
Hi,
Keith wrote:
> Of course, if you reboot, all the old library files will no longer be
> referenced, and the disk space will be marked as free.
To clarify, the library files stop being referenced as the processes die
on a requested shutdown, and the filesystem frees the storage for a now
unrefe
Hi Tim,
> But all of this side-steps another problem that gets fixed by applying
> updates during the boot process: updates are not applied atomically,
> either at the individual package level or the transaction level (the
> whole set of packages). The filesystem doesn't give us a way to do
> that
Hi Tim,
> Thanks for bringing debian-goodies to our attention - one or two gems
> buried away in there (checkrestart, debmany, dpigs).
Regarding dpigs(1), I use
deborphan -a |
sed 's/.* //' |
xargs dpkg-query -f '${package} ${Installed-Size}\n' -W
when I want to find packages that
On Thursday 13 Mar 2014 17:30:31 James Blake wrote:
> hese days data centres will run in virtualised environments with systems
> provisioned and "spun-up” and closed down to handle the peaks-and-troughs
> of service demand. You patch the master provisioning image while the
> virtualised environment
hese days data centres will run in virtualised environments with systems
provisioned and "spun-up” and closed down to handle the peaks-and-troughs of
service demand. You patch the master provisioning image while the virtualised
environments are running the older versions and handling load, then
On Thursday 13 Mar 2014 08:48:19 Tim Allen wrote:
> It stems from Unix's roots as a multi-user OS running on minis, vs
> Microsoft's single-user OS's. On a multi-user OS, regular rebooting is
> clearly not an option. As you said in your second email, the downside is
> that services may be exposed t
On Wed, 2014-03-12 at 21:01 +, Terry Coles wrote:
> That's news to me. I've never thought that an update has not delivered the
> new functionality until after a reboot. So what's the reality?
This sort of thing affects some packages more than others. For instance,
a long-running process suc
Hi Keith
On 12/03/14 20:12, Keith Edmunds wrote:
The 'debian-goodies' package (I don't know about other distros) includes
'checkrestart', which will show you which processes are using old library
files:
kae $ sudo checkrestart
Found 4 processes using old versions of upgraded files
(4 distinct p
Hi Terry
On 12/03/14 18:59, Terry Coles wrote:
Hi,
Can anyone give me an authoritative statement (or link to same) as to why we
generally don't need to reboot after installation of software or an upgrade?
It stems from Unix's roots as a multi-user OS running on minis, vs
Microsoft's single-
On 13/03/14 00:21, Gemma wrote:
On 12/03/14 21:01, Terry Coles wrote:
So what's the reality?
Ah! so now we have it! a philosophy question which has plagued some of
the best minds throughout the ages. To this we can add a good dollop
of Quantum Physics...
... pull up a bollard matey and se
On 12/03/14 21:01, Terry Coles wrote:
So what's the reality?
Ah! so now we have it! a philosophy question which has plagued some of
the best minds throughout the ages. To this we can add a good dollop of
Quantum Physics...
... pull up a bollard matey and settle down, whilst I write a 50,00
On Wednesday 12 Mar 2014 19:28:11 Ralph Corderoy wrote:
> http://www.howtogeek.com/182817/htg-explains-why-does-windows-want-to-reboot
> -so-often/ might help. I only skimmed it.
Hmmm.
That link says that the only reason that Windows has to reboot is that it
holds locks on files that are in use
If an in-use library file is replaced, the file won't be removed from disk
until no more processes are accessing it. You may see a new file (ie, a
new inode number), but old processes are still using the old library file
(which may well have the same name). You can force a daemon to use the new
lib
Hi Terry,
> Can anyone give me an authoritative statement (or link to same) as to
> why we generally don't need to reboot after installation of software
> or an upgrade?
http://www.howtogeek.com/182817/htg-explains-why-does-windows-want-to-reboot-so-often/
might help. I only skimmed it.
Cheers,
Hi,
Can anyone give me an authoritative statement (or link to same) as to why we
generally don't need to reboot after installation of software or an upgrade?
I was bemoaning the multiple reboots that I had to perform to install MS
Visual Studio 2012 on a clean machine and my boss declared that
18 matches
Mail list logo
