Re: [opensuse] smart conflict
On Thursday 14 June 2007 16:14, Munkii wrote:
On Sat, 2007-06-09 at 01:18 -0400, Bob S wrote:
What I am trying to find out is how to keep my old kernel after a kernel
upgrade. The last few upgrades smart replaced the kernel even though it
is flagged multi-version. Trying to determine if the flag "lock" will
allow a new kernel to be installed and still keep the old one.
"lock" will do what you said
Will try it and see what happens
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- Re: [opensuse] smart conflict
... The last few upgrades smart replaced the kernel even though it is ... flagged multi-version. ... Trying to determine if the flag "lock" will allow a ... "lock" will do what you said ...
- [patch 00/10] PI-futex: -V1
... We are pleased to announce "lightweight userspace priority inheritance" ... No registration, no extra kernel ... only a single owner may own a lock (i.e. no ... Priority Inheritance - why, oh why??? ...
- Re: CFR: New NFS Lock Manager
... It also includes minor fixes to support 64bit architectures and RELENG_7. ... Lock Manager which runs in kernel mode and uses the normal local locking infrastructure for its state. ... A single thread should be sufficient for the NLM since it should rarely block in normal operation. ...
- [patch 3/6] lightweight robust futexes: docs
... +The robust futex ABI ... for kernel assist of cleanup of held locks on task exit. ... will attempt to process both lists on each task ... pointer to a single linked list of 'lock entries', one per lock, ...
- Re: FreeBSD 7.0 crashed when running super-smack upon PostgreSQL
... Is there any chance I can get remote access to a box holding the synchronized kernel, kernel debugging symbols, source code, and core dump? ... It sounds like TCP in a user thread is stumbling over a violation of system invariants (don't sleep while holding a mutex) performed by another thread. ... We need to track down the original thread and figure out why it's sleeping while holding that lock -- perhaps it's a user thread performing a copyin/copyout holding the lock, or perhaps an ithread or other software interrupt thread acquiring a lock of an inappropriate type while holding the lock. ... kgdb has its own thread ID scheme so you'll need to use info threads to track down the right kgdb thread id before you can select the identified kernel thread/process. ...