Weirdness in TTY & VT

2016-09-02 Thread Lundberg, Johannes 
​Hi

I'm porting some Linux code and have some weird behavior.

In this (Linux) code fstat() and minor() is used on a /dev/tty file
descriptor to get a tty number to map to. In FreeBSD this returns a number
around 60-70 for st_rdev which means VT_ACTIVATE ioctl call will fail
because it only allows values 0-12.

Should not this be compatible with FreeBSD? If not, what is the FreeBSD way
to do this?

Is there some implementation missing in vt?

Thanks!

​

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Installworld fails when /usr/bin and /usr/sbin are different FS / how to use symlinks in installworld?

2016-09-02 Thread Bryan Drewery 
On 9/2/2016 3:25 PM, Alexander Leidinger wrote:
> Hi,
> 
> background info:
>  - iocage (jail management) uses official release tarballs
>  - I want to install a jail from a specific src I compiled withour
> creating release tarballs (-> faster time to market), so I want to
> convince iocage to use what I provide via installworld
>  - jails of type "basejail" (jails read-only-share the base system) in
> iocage are handled via seperate zfs datasets for each directory
>  - as such /usr/bin and /usr/sbin are different datasets
> 
> I got this error in installworld:
> ---snip---
> ===> usr.sbin/chkgrp (install)
> install  -s -o root -g wheel -m 555   chkgrp
> /iocage/base/12.0-r305149M/root/usr/sbin/chkgrp
> install  -o root -g wheel -m 444  chkgrp.debug
> /iocage/base/12.0-r305149M/root/usr/lib/debug/usr/sbin/chkgrp.debug
> install  -o root -g wheel -m 444 chkgrp.8.gz 
> /iocage/base/12.0-r305149M/root/usr/share/man/man8/
> ===> usr.sbin/chown (install)
> install  -s -o root -g wheel -m 555   chown
> /iocage/base/12.0-r305149M/root/usr/sbin/chown
> install  -o root -g wheel -m 444  chown.debug
> /iocage/base/12.0-r305149M/root/usr/lib/debug/usr/sbin/chown.debug
> install  -o root -g wheel -m 444 chgrp.1.gz 
> /iocage/base/12.0-r305149M/root/usr/share/man/man1/
> install  -o root -g wheel -m 444 chown.8.gz 
> /iocage/base/12.0-r305149M/root/usr/share/man/man8/
> ===> usr.sbin/chown/tests (install)
> install  -o root  -g wheel -m 555  chown-f_test 
> /iocage/base/12.0-r305149M/root/usr/tests/usr.sbin/chown/chown-f_test
> install  -o root  -g wheel -m 444  Kyuafile 
> /iocage/base/12.0-r305149M/root/usr/tests/usr.sbin/chown/Kyuafile
> /usr/bin/chgrp -> /usr/sbin/chown
> install: link /iocage/base/12.0-r305149M/root/usr/sbin/chown ->
> /iocage/base/12.0-r305149M/root/usr/bin/chgrp: Cross-device link
> *** Error code 71
> 
> Stop.
> make[5]: stopped in /usr/src/usr.sbin/chown
> *** Error code 1
> 
> Stop.
> ---snip---
> 
> The error message is obvious, it tries to create a hardlink which is off
> course not possible when src and dest of the link are on different FS.
> 
> My goal of an easy procedure (installworld into target datasets) doesn't
> work like this off course. Do we have an easy way of telling
> installworld to create symlinks instead of hardlinks, or alternatively a
> way to tell to copy instead of doing a hardlink if the install hits the
> cross-device case?

Maybe falling back to symlink could be done.

Couldn't you just make a usr-bin dataset and have usr-bin/bin and
usr-bin/sbin and symlink or nullfs-mount them in though?  I too go crazy
with datasets, but this seems a bit too much.


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Installworld fails when /usr/bin and /usr/sbin are different FS / how to use symlinks in installworld?

2016-09-02 Thread Alexander Leidinger 

Hi,

background info:
 - iocage (jail management) uses official release tarballs
 - I want to install a jail from a specific src I compiled withour  
creating release tarballs (-> faster time to market), so I want to  
convince iocage to use what I provide via installworld
 - jails of type "basejail" (jails read-only-share the base system)  
in iocage are handled via seperate zfs datasets for each directory

 - as such /usr/bin and /usr/sbin are different datasets

I got this error in installworld:
---snip---
===> usr.sbin/chkgrp (install)
install  -s -o root -g wheel -m 555   chkgrp  
/iocage/base/12.0-r305149M/root/usr/sbin/chkgrp
install  -o root -g wheel -m 444  chkgrp.debug  
/iocage/base/12.0-r305149M/root/usr/lib/debug/usr/sbin/chkgrp.debug
install  -o root -g wheel -m 444 chkgrp.8.gz   
/iocage/base/12.0-r305149M/root/usr/share/man/man8/

===> usr.sbin/chown (install)
install  -s -o root -g wheel -m 555   chown  
/iocage/base/12.0-r305149M/root/usr/sbin/chown
install  -o root -g wheel -m 444  chown.debug  
/iocage/base/12.0-r305149M/root/usr/lib/debug/usr/sbin/chown.debug
install  -o root -g wheel -m 444 chgrp.1.gz   
/iocage/base/12.0-r305149M/root/usr/share/man/man1/
install  -o root -g wheel -m 444 chown.8.gz   
/iocage/base/12.0-r305149M/root/usr/share/man/man8/

===> usr.sbin/chown/tests (install)
install  -o root  -g wheel -m 555  chown-f_test   
/iocage/base/12.0-r305149M/root/usr/tests/usr.sbin/chown/chown-f_test
install  -o root  -g wheel -m 444  Kyuafile   
/iocage/base/12.0-r305149M/root/usr/tests/usr.sbin/chown/Kyuafile

/usr/bin/chgrp -> /usr/sbin/chown
install: link /iocage/base/12.0-r305149M/root/usr/sbin/chown ->  
/iocage/base/12.0-r305149M/root/usr/bin/chgrp: Cross-device link

*** Error code 71

Stop.
make[5]: stopped in /usr/src/usr.sbin/chown
*** Error code 1

Stop.
---snip---

The error message is obvious, it tries to create a hardlink which is  
off course not possible when src and dest of the link are on different  
FS.


My goal of an easy procedure (installworld into target datasets)  
doesn't work like this off course. Do we have an easy way of telling  
installworld to create symlinks instead of hardlinks, or alternatively  
a way to tell to copy instead of doing a hardlink if the install hits  
the cross-device case?


Bye,
Alexander.

--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0x8F31830F9F2772BF


pgpBlT2MUqRFA.pgp
Description: Digitale PGP-Signatur

Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4

2016-09-02 Thread Guido Falsi 
On 09/02/16 22:09, Guido Falsi wrote:
> On 09/02/16 20:35, Oliver Böttcher wrote:
>> Hi all,
>>
>> I tried to install 11.0-RC2 on an apu2c4 which stucks on boot and waits
>> forever (screenshot here [1]). So I tried to install 10.3-RELEASE which
>> installed without problems and updated to 11.0-RC2 via freebsd-update,
>> rebooted, hangs right after loading the kernel.
>>
>> I also tried 12-CURRENT but no luck either.
> 
> I have the same hardware and can confirm this problem. I think I
> remember one of the 11.0-BETAs to work with it, but I'm not really that
> sure, where can I find memstick images for the 11.0 BETA to test? they
> are gone from the official mirrors.

Playing around with it I found out I was able to make it boot from an SD
card with a custom RC2 nanobsd image. I know there are various variables
at play here (it's also running a custom kernel), but it's anyway some
information.

-- 
Guido Falsi 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 11.0-RC2 and 12-CURRENT won't boot on apu2c4

2016-09-02 Thread Guido Falsi 
On 09/02/16 20:35, Oliver Böttcher wrote:
> Hi all,
> 
> I tried to install 11.0-RC2 on an apu2c4 which stucks on boot and waits
> forever (screenshot here [1]). So I tried to install 10.3-RELEASE which
> installed without problems and updated to 11.0-RC2 via freebsd-update,
> rebooted, hangs right after loading the kernel.
> 
> I also tried 12-CURRENT but no luck either.

I have the same hardware and can confirm this problem. I think I
remember one of the 11.0-BETAs to work with it, but I'm not really that
sure, where can I find memstick images for the 11.0 BETA to test? they
are gone from the official mirrors.

I have tested a 12.0 snapshot from ftp.freebsd.org
(amd64-20160809-r303880) and it's showing the same problem. I need to
test older images, but I have to produce those before. Not even sure if
the problem is with the kernel or the loader.

I'm going to try to narrow it down further anyway, but will need some time.

I think you should open a bug report and post the number here so
feedback about this can be collected there.

-- 
Guido Falsi 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Jenkins build is back to normal : FreeBSD_HEAD #587

2016-09-02 Thread jenkins-admin 
See 

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

11.0-RC2 and 12-CURRENT won't boot on apu2c4

2016-09-02 Thread Oliver Böttcher 
Hi all,

I tried to install 11.0-RC2 on an apu2c4 which stucks on boot and waits
forever (screenshot here [1]). So I tried to install 10.3-RELEASE which
installed without problems and updated to 11.0-RC2 via freebsd-update,
rebooted, hangs right after loading the kernel.

I also tried 12-CURRENT but no luck either.

I would love to have 11.0-RELEASE on this device but have no clue how to
narrow down my issue (and debugging FreeBSD anyway). Any help is highly
appreciated.

Thanks in advance
Oliver


[1]: https://files.oliverboettcher.de/s/8vtg5shAPpY9J6M



signature.asc
Description: OpenPGP digital signature

Build failed in Jenkins: FreeBSD_HEAD #586

2016-09-02 Thread jenkins-admin 
See 

--
[...truncated 321955 lines...]
[192.168.10.2] out: bin/sh/parser/functional_test:dollar_quote6  ->  passed  
[0.047s]
[192.168.10.2] out: bin/sh/parser/functional_test:dollar_quote7  ->  passed  
[0.089s]
[192.168.10.2] out: bin/sh/parser/functional_test:dollar_quote8  ->  passed  
[0.047s]
[192.168.10.2] out: bin/sh/parser/functional_test:dollar_quote9  ->  passed  
[0.049s]
[192.168.10.2] out: bin/sh/parser/functional_test:empty_braces1  ->  passed  
[0.049s]
[192.168.10.2] out: bin/sh/parser/functional_test:empty_cmd1  ->  passed  
[0.057s]
[192.168.10.2] out: bin/sh/parser/functional_test:for1  ->  passed  [0.046s]
[192.168.10.2] out: bin/sh/parser/functional_test:for2  ->  passed  [0.047s]
[192.168.10.2] out: bin/sh/parser/functional_test:func1  ->  passed  [0.048s]
[192.168.10.2] out: bin/sh/parser/functional_test:func2  ->  passed  [0.046s]
[192.168.10.2] out: bin/sh/parser/functional_test:func3  ->  passed  [0.048s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc1  ->  passed  [0.074s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc10  ->  passed  
[0.056s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc11  ->  passed  
[0.057s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc12  ->  passed  
[0.061s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc13  ->  passed  
[0.053s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc2  ->  passed  [0.056s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc3  ->  passed  [0.047s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc4  ->  passed  [0.057s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc5  ->  passed  [0.062s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc6  ->  passed  [0.048s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc7  ->  passed  [0.049s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc8  ->  passed  [0.048s]
[192.168.10.2] out: bin/sh/parser/functional_test:heredoc9  ->  passed  [0.061s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont1  ->  passed  
[0.044s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont10  ->  passed  
[0.045s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont11  ->  passed  
[0.052s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont2  ->  passed  
[0.045s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont3  ->  passed  
[0.047s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont4  ->  passed  
[0.048s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont5  ->  passed  
[0.046s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont6  ->  passed  
[0.052s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont7  ->  passed  
[0.046s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont8  ->  passed  
[0.045s]
[192.168.10.2] out: bin/sh/parser/functional_test:line_cont9  ->  passed  
[0.048s]
[192.168.10.2] out: bin/sh/parser/functional_test:no_space1  ->  passed  
[0.054s]
[192.168.10.2] out: bin/sh/parser/functional_test:no_space2  ->  passed  
[0.047s]
[192.168.10.2] out: bin/sh/parser/functional_test:nul1  ->  passed  [0.052s]
[192.168.10.2] out: bin/sh/parser/functional_test:only_redir1  ->  passed  
[0.047s]
[192.168.10.2] out: bin/sh/parser/functional_test:only_redir2  ->  passed  
[0.047s]
[192.168.10.2] out: bin/sh/parser/functional_test:only_redir3  ->  passed  
[0.045s]
[192.168.10.2] out: bin/sh/parser/functional_test:only_redir4  ->  passed  
[0.044s]
[192.168.10.2] out: bin/sh/parser/functional_test:pipe_not1  ->  passed  
[0.049s]
[192.168.10.2] out: bin/sh/parser/functional_test:set_v1  ->  passed  [0.052s]
[192.168.10.2] out: bin/sh/parser/functional_test:var_assign1  ->  passed  
[0.063s]
[192.168.10.2] out: bin/sh/set-e/functional_test:and1  ->  passed  [0.041s]
[192.168.10.2] out: bin/sh/set-e/functional_test:and2  ->  passed  [0.044s]
[192.168.10.2] out: bin/sh/set-e/functional_test:and3  ->  passed  [0.044s]
[192.168.10.2] out: bin/sh/set-e/functional_test:and4  ->  passed  [0.042s]
[192.168.10.2] out: bin/sh/set-e/functional_test:background1  ->  passed  
[0.042s]
[192.168.10.2] out: bin/sh/set-e/functional_test:cmd1  ->  passed  [0.044s]
[192.168.10.2] out: bin/sh/set-e/functional_test:cmd2  ->  passed  [0.043s]
[192.168.10.2] out: bin/sh/set-e/functional_test:elif1  ->  passed  [0.044s]
[192.168.10.2] out: bin/sh/set-e/functional_test:elif2  ->  passed  [0.042s]
[192.168.10.2] out: bin/sh/set-e/functional_test:eval1  ->  passed  [0.045s]
[192.168.10.2] out: bin/sh/set-e/functional_test:eval2  ->  passed  [0.043s]
[192.168.10.2] out: bin/sh/set-e/functional_test:for1  ->  passed  [0.041s]
[192.168.10.2] out: bin/sh/set-e/functional_test:func1  ->  passed  [0.042s]
[192.168.10.2] out: bin/sh/set-e/functional_test:func2  ->  passed  [0.044s]
[192.168.10.2] out: bin/sh/set-e/functional_test:if1  ->  passed

Re: 11.0-RELEASE status update

2016-09-02 Thread Piotr Kubaj 
Can somebody also look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211959 ?

It happens on two PC's.



signature.asc
Description: OpenPGP digital signature