On Wed Jan 12 2011 at 19:23:44 +0100, Manuel Bouyer wrote:
I can live with it for now; having the uprintf output somewhere could help
for atf tests though. I have filled kern/44378 about this.
Thanks, i'll look at it some day hopefully soon.
Curiously enough, during all the time i've been
Hello,
I'm playing with rump, and more specifically rump_ffs.
The mount is rejected (as expected) because the fs image has a feature
which is not yet in the kernel. It's rejected by this code:
if (fs-fs_flags ~(FS_KNOWN_FLAGS | FS_INTERNAL)) {
uprintf(%s: unknown ufs
On Wed Jan 12 2011 at 15:36:02 +0100, Manuel Bouyer wrote:
Hello,
I'm playing with rump, and more specifically rump_ffs.
The mount is rejected (as expected) because the fs image has a feature
which is not yet in the kernel. It's rejected by this code:
if (fs-fs_flags ~(FS_KNOWN_FLAGS
On Wed, Jan 12, 2011 at 04:53:57PM +0200, Antti Kantee wrote:
[...]
but even with RUMP_VERBOSE I never see the uprintf(). Where does it do, and
is there a way to make rump print it (I guess it should just go to
stderr) ?
It goes to the same place as for any process without a tty: the
