Re: st(4) and mt eom

2019-03-21 Thread Adrian Bocaniciu
On Thu, 21 Mar 2019 06:48:22 +0100 Frank Kardel wrote: > > For Bacula it wouldn't help right now, thus the EOM code needs fixing. When I referred you to FreeBSD "mt locate -e", my point was not that you should implement the additional FreeBSD features, even if that will also be good. My poi

daily CVS update output

2019-03-21 Thread NetBSD source update
Updating src tree: U src/distrib/sets/lists/debug/md.mipsco U src/distrib/sets/lists/debug/md.mmeye U src/distrib/sets/lists/debug/md.sgimips P src/external/bsd/jemalloc/include/jemalloc/internal/size_classes.h P src/lib/libc/stdio/funopen.3 P src/lib/libcurses/printw.c P src/lib/libnvmm/libnvmm.

Re: xentools411 fails build

2019-03-21 Thread Martin Husemann
This kind of warning (used with -Werror) breaks all sysutils/xentools* builds with gcc >= 7. I started fixing some for xentools48, but ran out of time and gave up on xen instead. Martin $NetBSD$ Elide string truncation warning with newer gcc. --- tools/xenpmd/xenpmd.c.orig 2018-01-23 14:49:58.

Re: /dev/stdin: Device not configured

2019-03-21 Thread Adam
>> crw--w 1 root tty 5, 0 Mar 21 09:39 /dev/fd/0 >> >> Nothing special, right? :) > > For what arch is that supposed to be? > For i386 I would expect 22, 0 instead of 5, 0. I found out I have fdesc mounted on /dev, and that is the source of the problem. When I unmounted it, everything was

Re: init died

2019-03-21 Thread Patrick Welche
On Thu, Mar 21, 2019 at 10:58:10AM +0100, Martin Husemann wrote: > Exit codes in init are unique. 11 is: it could not open /dev/console, > tried to mount a tmpfs on /dev and run /dev/MAKEDEV or /etc/MAKEDEV, > but that somehow failed and there still is no /dev/console. Thanks for the clue! What a

Re: init died

2019-03-21 Thread Martin Husemann
On Thu, Mar 21, 2019 at 09:42:59AM +, Patrick Welche wrote: > Just updated a amd64 box from 8.99.30 -> 8.99.36. > - successfully booted with new kernel+modules > - fail after updating userland with: > > [ 7.9567598] kern.module.path=/stand/amd64/8.99.36/modules > [ 7.9767685] init path (de

Re: init died

2019-03-21 Thread Patrick Welche
On Thu, Mar 21, 2019 at 09:42:59AM +, Patrick Welche wrote: > i.e., failed with /sbin/init, so tried /rescue/init incase my libc somehow > wasn't in sync. (How?!) netbooting... Successfully netbooted identical files: # mount 10.1.1.6:/usr/export/amd64 on / type nfs /dev/raid0a on /mnt type ff

init died

2019-03-21 Thread Patrick Welche
Just updated a amd64 box from 8.99.30 -> 8.99.36. - successfully booted with new kernel+modules - fail after updating userland with: [ 7.9567598] kern.module.path=/stand/amd64/8.99.36/modules [ 7.9767685] init path (default /sbin/init): /rescue/init [ 11.6583668] init: trying /rescue/init [

Re: /dev/stdin: Device not configured

2019-03-21 Thread Martin Husemann
On Thu, Mar 21, 2019 at 09:42:16AM +0100, Adam wrote: > crw--w 1 root tty 5, 0 Mar 21 09:39 /dev/fd/0 > > Nothing special, right? :) For what arch is that supposed to be? For i386 I would expect 22, 0 instead of 5, 0. Martin

Re: /dev/stdin: Device not configured

2019-03-21 Thread Adam
>> After building today's sources (8.99.36), on i386 I get: >> >> # sort >> sort: /dev/stdin: Device not configured >> >> 8.99.29 kernel works correctly. >> >> Same sources, but amd64, also work correctly. >> >> Any suggestions? :) > > what does "ls -l /dev/stdin" show? also -lL. lr-xr-xr-x

Re: st(4) and mt eom

2019-03-21 Thread Frank Kardel
On 03/21/19 07:00, John Nemeth wrote: On Mar 21, 6:48am, Frank Kardel wrote: } } As I wrote, extending MTIO ioctls to support more mt commands is not a } real issue (e. g. add access to the LOCATE command). We just need to } decide which features are useful to support and find the time to } imp