Curious behavior of HAL in 2.18
oberman at es.net
Wed Mar 21 04:08:50 UTC 2007
> From: Joe Marcus Clarke <marcus at marcuscom.com>
> Date: Tue, 20 Mar 2007 23:54:21 -0400
> On Tue, 2007-03-20 at 15:10 -0700, Kevin Oberman wrote:
> > Following up my own message, It is not the mounting or umounting of a
> > system that triggers it. It is the creation or deletion of a device in
> > /dev.
> > I can understand this triggering HAL, but I don't know why it wants to
> > alway remount all of the system partitions.
> Please provide a step-by-step procedure of what you're doing to create
> this behavior as well as the version of FreeBSD.
Only one step:
mdconfig -f file
mdconfig -d -u 1
In stable, the first would have been "mdconfig -a -t vnode -f file".
FreeBSD slan.es.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon Mar 19 09:07:43 PDT
A couple of seconds after I issue the command (which creates or deletes
/dev/md1), I get the messages.
All ports are current except p5-Cairo which won't build the new version.
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 224 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20070321/a3aa7379/attachment.pgp
More information about the freebsd-gnome