On Tue, May 27, 2008 at 01:18:52PM -0600, dann frazier wrote:
On Tue, May 27, 2008 at 08:17:09PM +0200, Uwe Schindler wrote:
The problem with updating the aboot package is a little bit more
complicated:
It is not enough to update the aboot package alone! You must also write the
new boot
On Fri, 30 May 2008, Steve Langasek wrote:
On Tue, May 27, 2008 at 01:18:52PM -0600, dann frazier wrote:
I agree, and ideally the boot block would be written out with every
update of aboot. I don't feel comfortable making such a large
behavior change in etch, but I think it'd be great to see
I'm not aware of any method for reliably detecting the boot device from inside
the
running system on alpha.
You could load the srm_env kernel module and look at
/proc/srm_environment/named_variables/booted_dev.
Bob
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Fri, May 30, 2008 at 02:45:32PM -0700, Bob Lindell wrote:
I'm not aware of any method for reliably detecting the boot device from
inside the
running system on alpha.
You could load the srm_env kernel module and look at
/proc/srm_environment/named_variables/booted_dev.
... which I know
4 matches
Mail list logo
