The below included simple program reliably printfs "error 4\n" on
5.4-RELEASE. Am I understanding something wrong or is this a bug in
libdevinfo?
To continue on this however, if you put say sleep(5) between
devinfo_free() and the second devinfo_init() and manage to change the
device configurat
nding out what is the
corresponding block device for umass devices? The device driver writes
that to syslog, but reading logs for something like that is quite clumsy.
Juho Vuori
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/ma
2 matches
Mail list logo