Re: sysctl: OID number(131) is already in use for 'me'

2016-03-23 Thread Eir Nym
Hi,

Is there method to check this with compiled binaries?

I never update world on live system since it is -CURRENT branch and I keep 
possible incompatibility in mind.

You can also look into my build script I’ve published in same repository.

—

Arseny Nasokin
✪

> On 22 Mar 2016, at 19:29, Hans Petter Selasky <h...@selasky.org> wrote:
> 
> Hi,
> 
> Were all kernel modules in /boot/modules rebuilt?
> 
> --HPS
> 
> On 03/21/16 23:32, Arseny Nasokin wrote:
>> I've recently upgrade my machine to FreeBSD-Current revision 297059 and got
>> strange result on first boot lines:
>> 
>> sysctl: OID number(131) is already in use for 'me'
>> 
>> I build system in two stages: first with 'native'/crosstools clang, second
>> in bhyve. This message appears in both times.
>> 
>> I've tried to boot latest FreeBSD-10 and I've seen no such message.
>> 
>> My kernel config is here:
>> https://bitbucket.org/eirnym/bsd/src/7f7e4a234b5bba4b346fd76e5f8b35d58d2bec29/eroese/EirZen.amd64
>> 
>> -- Eir Nym
> 
> 

___
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"

ZFS: unknown file system on boot

2013-12-01 Thread Eir Nym
I use zfs on root setup with system r258777. I've tried my kernel and
generic one.

I found new  feature from r257650 that now loader.4th will load modules
after menu gone (kernel selection). Now I have problem that modules won't
loaded even I selected default kernel.

for example, I have following contents of /boot/loader.conf, but none of
modules will be loaded:
zfs_load=YES
if_re_load=YES

Later on boot I got that system can't  find filesystem zfs! If I break
loader menu and manually load modules one by one, anything will be OK.

How to boot my system correctly?

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


r255903 contrib/unbound/util/configparser.c modified?

2013-09-27 Thread Eir Nym
I have world for current system in /usr/src, but for head in
/usr/head/src.After building the world for -CURRENT
file contrib/unbound/util/configparser.c is in modified state. Paths to the
/usr/head/src has been hardcoded.
As far as I know rules of FreeBSD build system, if file goes to be
modified, it should be where object files are. Should I create the bug
report?

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


Installworld on amd64 fails on libc.a on r255342

2013-09-13 Thread Eir Nym
I get this error for a while, and don't know what to do with.

I build the world, then try to install it into DESTDIR. And at this point I
always get error that libc.a can't be found.

To eliminate any mistakes in commits I've run snapshot r255342 from FTP in
VM and build sources it contains.

my building and installing world with following commands:

 # make toolchain buildworld __MAKE_CONF=/dev/null SRCCONF=src.conf
 # make hierarchy distrib-dirs distribution installworld

some notes:
 * Targets like hierarchy, disturb-dirs and distribution are described in
FreeBSD Handbook in this order
 * Target distribution doesn't install anything, but configuration files.

SRCCONF has following contents:

WITHOUT_AMD=YES
WITHOUT_ASSERT_DEBUG=YES
WITHOUT_BIND=YES
WITH_BMAKE=YES
WITH_BSD_GREP=YES
WITH_CLANG=YES
WITH_CLANG_EXTRAS=YES
WITH_CLANG_FULL=YES
WITH_CLANG_IS_CC=YES
WITH_CTF=YES
WITHOUT_CTM=YES
WITHOUT_DYNAMICROOT=YES
WITHOUT_FLOPPY=YES
WITH_ICONV=YES
WITHOUT_HTML=YES
WITHOUT_IPFILTER=YES
WITHOUT_IPFW=YES
WITHOUT_IPX=YES
WITHOUT_IPX_SUPPORT=YES
WITH_LDNS_UTILS=YES
WITH_LIBCPLUSPLUS=YES
WITH_LIBICONV_COMPAT=YES
WITHOUT_NCP=YES
WITHOUT_NIS=YES
WITHOUT_NLS=YES
WITHOUT_NLS_CATALOGS=YES
WITH_OPENSSH_NONE_CIPHER=YES
WITHOUT_PC_SYSINSTALL=YES
WITHOUT_RCMDS=YES
WITHOUT_SYSINSTALL=YES
WITHOUT_TCSH=YES
WITH_USB_GADGET_EXAMPLES=YES

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


Re: 9.1 - current migration problem

2013-05-14 Thread Eir Nym
-- Eir Nym


On 12 May 2013 19:48, Paul Dokas do...@dokas.name wrote:
 Thanks Dan!  I was hoping that this would be something simple like this.
  The entry in UPDATING that you are referring to is:

   20130121:
 Due to the use of the new -l option to install(1) during build
 and install, you must take care not to directly set the INSTALL
 make variable in your /etc/make.conf, /etc/src.conf, or on the
 command line.  If you with to use the -C flag for all installs
 you may be able to add INSTALL+=-C to /etc/make.conf or
 /etc/src.conf.

 And I was setting INSTALL in /etc/make.conf

   INSTALL=   install -C

 I've commented this out and am rebuilding again.

 Thanks again!



 Paul


I have this problem and I have no clues how to do this without setting
INSTALL http://www.freebsd.org/cgi/query-pr.cgi?pr=178547


 On 05/12/13 09:35, Dan Mack wrote:

 It's sound familiar; in /usr/src/UPDATING there is mention of this '-l'
 issue.   Search for 'install' in UPDATING and I think there is a
 work-around.

 Dan

 On Sun, 12 May 2013, Paul Dokas wrote:

 I have a newly installed 9.1 amd64 VM that I would like to update to
 -current.  I have pulled down head via svn:

  svn co svn://svn.freebsd.org/base/head /usr/src

 and am attempting to buildworld:

  cd /usr/src
  make buildworld

 This build is failing during bootstrap-tools when building makewhatis or
 mklocale.  It seems that something is trying to use the '-l' option to
 install, which is only present in FreeBSD 10.

 Any ideas how to get around this issue?

 Thanks,

 Paul




 # cd /usr/src
 # make buildworld
  .
  .
  .
 === bin/cat (obj,depend,all,install)
 /usr/obj/usr/src/tmp/usr/src/bin/cat created for /usr/src/bin/cat
 rm -f .depend
 mkdep -f .depend -a-I/usr/obj/usr/src/tmp/legacy/usr/include
 -std=gnu99   /usr/src/bin/cat/cat.c
 echo cat: /usr/lib/libc.a /usr/obj/usr/src/tmp/legacy/usr/lib/libegacy.a
 .depend
 cc -O2 -fno-strict-aliasing -pipe -std=gnu99
 -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/bin/cat/cat.c
 ${CTFCONVERT_CMD} expands to empty string
 cc -O2 -fno-strict-aliasing -pipe -std=gnu99
 -I/usr/obj/usr/src/tmp/legacy/usr/include  -static
 -L/usr/obj/usr/src/tmp/legacy/usr/lib -o cat cat.o -legacy
 install -C -s -o root -g wheel -m 555   cat
 /usr/obj/usr/src/tmp/legacy/bin/cat
 === usr.bin/lorder (obj,depend,all,install)
 /usr/obj/usr/src/tmp/usr/src/usr.bin/lorder created for
 /usr/src/usr.bin/lorder
 install -C -o root  -g wheel -m 555  /usr/src/usr.bin/lorder/lorder.sh
 /usr/obj/usr/src/tmp/legacy/usr/bin/lorder
 === usr.bin/makewhatis (obj,depend,all,install)
 /usr/obj/usr/src/tmp/usr/src/usr.bin/makewhatis created for
 /usr/src/usr.bin/makewhatis
 rm -f .depend
 mkdep -f .depend -a-I/usr/obj/usr/src/tmp/legacy/usr/include
 -std=gnu99   /usr/src/usr.bin/makewhatis/makewhatis.c
 echo makewhatis: /usr/lib/libc.a /usr/lib/libz.a
 /usr/obj/usr/src/tmp/legacy/usr/lib/libegacy.a  .depend
 cc -O2 -fno-strict-aliasing -pipe -std=gnu99
 -I/usr/obj/usr/src/tmp/legacy/usr/include -c
 /usr/src/usr.bin/makewhatis/makewhatis.c
 ${CTFCONVERT_CMD} expands to empty string
 cc -O2 -fno-strict-aliasing -pipe -std=gnu99
 -I/usr/obj/usr/src/tmp/legacy/usr/include  -static
 -L/usr/obj/usr/src/tmp/legacy/usr/lib -o makewhatis makewhatis.o -lz
 -legacy
 install -C -s -o root -g wheel -m 555   makewhatis
 /usr/obj/usr/src/tmp/legacy/usr/bin/makewhatis
 install -C -o root  -g wheel -m 555
 /usr/src/usr.bin/makewhatis/makewhatis.local.sh
 /usr/obj/usr/src/tmp/legacy/usr/libexec/makewhatis.local
 /usr/obj/usr/src/tmp/legacy/usr/libexec/catman.local -
 /usr/obj/usr/src/tmp/legacy/usr/libexec/makewhatis.local
 install: illegal option -- l
 usage: install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
   [-o owner] file1 file2
   install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
   [-o owner] file1 ... fileN directory
   install -d [-v] [-g group] [-m mode] [-o owner] directory ...
 *** [_installlinks] Error code 64

 Stop in /usr/src/usr.bin/makewhatis.
 *** [bootstrap-tools] Error code 1

 Stop in /usr/src.
 *** [_bootstrap-tools] Error code 1

 Stop in /usr/src.
 *** [buildworld] Error code 1

 Stop in /usr/src.


 --
 Paul Dokas dokas at dokas.name
 ==
 Don Juan Matus:  an enigma wrapped in mystery wrapped in a tortilla.
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to
 freebsd-current-unsubscr...@freebsd.org



 --
 Paul Dokas dokas at dokas.name
 ==
 Don Juan Matus:  an enigma wrapped in mystery wrapped in a tortilla.
 ___
 freebsd-current

Re: Installing new world failed (install -l)

2013-05-05 Thread Eir Nym
Hack 
INSTALL=/usr/obj/${TARGET}.${TARGET_ARCH}${SRC_PATH}/tmp/legacy/usr/bin/install
is working, but this conversation will become PR.

-- Eir Nym


On 30 April 2013 23:13, Brooks Davis bro...@freebsd.org wrote:
 On Tue, Apr 30, 2013 at 10:17:09PM +0400, Eir Nym wrote:
 -- Eir Nym


 On 29 April 2013 19:25, Brooks Davis bro...@freebsd.org wrote:
  On Sun, Apr 28, 2013 at 11:36:20PM +0400, Eir Nym wrote:
  Since -l switch introduced into install(8), I can't build new FreeBSD
  box at all.
 
  I do following command set to build new box: (http://eroese.org/mkw.sh)
  1) cd /usr/head/src  svn up
  2) make buildworld
  3) make DESTDIR=/path/to/directory hierarchy distrib-dirs distribution
  installworld
 
  heriarchy and distrib-dirs are both pointless here AFACT.
 
 
  This worked for long time but after some point it had been broken. I
  found only 20130425 in UPDATING about this, but installing mergemaster
  gives nothing, obviously.
  I can't compile new install(8) since I have old system like
  FreeBSD-9-RELEASE (FreeBSD-CURRENT, r226748) and it doesn't have
  needed functions.
 
  The tail of install log is below.
 
  .. (lines removed)
  mtree -deU -f /usr/head/src/etc/mtree/BSD.sendmail.dist -p
  /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/
  ./var/spool/clientmqueue missing (created)
  install -l s usr/src/sys 
  /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/sys
  install: illegal option -- l
  usage: install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
 [-o owner] file1 file2
 install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
 [-o owner] file1 ... fileN directory
 install -d [-v] [-g group] [-m mode] [-o owner] directory ...
  *** [distrib-dirs] Error code 64
 
  Are you setting INSTALL= in make.conf, src.conf, etc?
 
  -- Brooks

 I don't set this option at all.
 As far as I know I should not set it setting and I've tested with
 clean environment (like __MAKE_CONF=/dev/null  SRCCONF=/dev/null).
 The PATH should be different for cross-platform build as I do.
 the correct install path is
 ${MAKEOBJDIRPREFIX}/i386.i386/usr/head/src/tmp/legacy/usr/bin/install

 That's not the problem.  I belive that the problem is that the hierarchy
 target is broken when called directly.  As I mention above, it's also
 pointless.  Just use installworld before distribution so installworld
 creates all the required directories rather than pre-creating them with
 hierarchy and distrib-dirs.

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


Re: Installing new world failed (install -l)

2013-04-30 Thread Eir Nym
-- Eir Nym


On 29 April 2013 19:25, Brooks Davis bro...@freebsd.org wrote:
 On Sun, Apr 28, 2013 at 11:36:20PM +0400, Eir Nym wrote:
 Since -l switch introduced into install(8), I can't build new FreeBSD
 box at all.

 I do following command set to build new box: (http://eroese.org/mkw.sh)
 1) cd /usr/head/src  svn up
 2) make buildworld
 3) make DESTDIR=/path/to/directory hierarchy distrib-dirs distribution
 installworld

 heriarchy and distrib-dirs are both pointless here AFACT.


 This worked for long time but after some point it had been broken. I
 found only 20130425 in UPDATING about this, but installing mergemaster
 gives nothing, obviously.
 I can't compile new install(8) since I have old system like
 FreeBSD-9-RELEASE (FreeBSD-CURRENT, r226748) and it doesn't have
 needed functions.

 The tail of install log is below.

 .. (lines removed)
 mtree -deU -f /usr/head/src/etc/mtree/BSD.sendmail.dist -p
 /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/
 ./var/spool/clientmqueue missing (created)
 install -l s usr/src/sys 
 /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/sys
 install: illegal option -- l
 usage: install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 file2
install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 ... fileN directory
install -d [-v] [-g group] [-m mode] [-o owner] directory ...
 *** [distrib-dirs] Error code 64

 Are you setting INSTALL= in make.conf, src.conf, etc?

 -- Brooks

I don't set this option at all.
As far as I know I should not set it setting and I've tested with
clean environment (like __MAKE_CONF=/dev/null  SRCCONF=/dev/null).
The PATH should be different for cross-platform build as I do.
the correct install path is
${MAKEOBJDIRPREFIX}/i386.i386/usr/head/src/tmp/legacy/usr/bin/install
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Installing new world failed (install -l)

2013-04-29 Thread Eir Nym
On 29 April 2013 10:19, Gleb Smirnoff gleb...@freebsd.org wrote:
 On Sun, Apr 28, 2013 at 11:36:20PM +0400, Eir Nym wrote:
 E Since -l switch introduced into install(8), I can't build new FreeBSD
 E box at all.
 E
 E I do following command set to build new box: (http://eroese.org/mkw.sh)
 E 1) cd /usr/head/src  svn up
 E 2) make buildworld
 E 3) make DESTDIR=/path/to/directory hierarchy distrib-dirs distribution
 E installworld
 E
 E This worked for long time but after some point it had been broken. I
 E found only 20130425 in UPDATING about this, but installing mergemaster
 E gives nothing, obviously.
 E I can't compile new install(8) since I have old system like
 E FreeBSD-9-RELEASE (FreeBSD-CURRENT, r226748) and it doesn't have
 E needed functions.
 E
 E The tail of install log is below.
 E
 E .. (lines removed)
 E mtree -deU -f /usr/head/src/etc/mtree/BSD.sendmail.dist -p
 E /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/
 E ./var/spool/clientmqueue missing (created)
 E install -l s usr/src/sys 
 /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/sys
 E install: illegal option -- l
 E usage: install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
 E[-o owner] file1 file2
 Einstall [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
 E[-o owner] file1 ... fileN directory
 Einstall -d [-v] [-g group] [-m mode] [-o owner] directory ...
 E *** [distrib-dirs] Error code 64

 I came to the following recipe when upgrading from a stale current to
 a modern one. This workarounds problem with install(1) and failure of
 clang bootstrap with old time.h in /usr/include.

 cd usr.bin/xinstall
 make  make install  make clean
 cd -
 make hierarchy
 make includes

 Now, make buildworld is possible.


I've tried this, but with no hope:

Warning: Object directory not changed from original
/usr/head/src/usr.bin/xinstall
cc -O2 -pipe  -I/usr/head/src/usr.bin/xinstall/../../contrib/mtree
-I/usr/head/src/usr.bin/xinstall/../../lib/libnetbsd
-I/usr/head/src/usr.bin/xinstall/../../lib/libmd -DNDEBUG -std=gnu99
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
-Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
-Wnested-externs -Wredundant-decls -Wold-style-definition
-Wno-pointer-sign -c xinstall.c
xinstall.c: In function 'main':
xinstall.c:301: warning: implicit declaration of function 'gid_from_group'
xinstall.c:301: warning: nested extern declaration of 'gid_from_group'
xinstall.c:311: warning: implicit declaration of function 'uid_from_user'
xinstall.c:311: warning: nested extern declaration of 'uid_from_user'
xinstall.c: In function 'metadata_log':
xinstall.c:1331: warning: implicit declaration of function 'strsvis'
xinstall.c:1331: warning: nested extern declaration of 'strsvis'
cc -O2 -pipe  -I/usr/head/src/usr.bin/xinstall/../../contrib/mtree
-I/usr/head/src/usr.bin/xinstall/../../lib/libnetbsd
-I/usr/head/src/usr.bin/xinstall/../../lib/libmd -DNDEBUG -std=gnu99
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
-Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
-Wnested-externs -Wredundant-decls -Wold-style-definition
-Wno-pointer-sign -c
/usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c
/usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c: In
function 'setup_getid':
/usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c:137:
warning: implicit declaration of function 'pwcache_groupdb'
/usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c:137:
warning: nested extern declaration of 'pwcache_groupdb'
/usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c:139:
warning: implicit declaration of function 'pwcache_userdb'
/usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c:139:
warning: nested extern declaration of 'pwcache_userdb'
cc -O2 -pipe  -I/usr/head/src/usr.bin/xinstall/../../contrib/mtree
-I/usr/head/src/usr.bin/xinstall/../../lib/libnetbsd
-I/usr/head/src/usr.bin/xinstall/../../lib/libmd -DNDEBUG -std=gnu99
-fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W
-Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
-Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
-Wnested-externs -Wredundant-decls -Wold-style-definition
-Wno-pointer-sign  -o xinstall xinstall.o getid.o -lmd
xinstall.o: In function `metadata_log':
xinstall.c:(.text+0x169): undefined reference to `strsvis'
xinstall.c:(.text+0x20e): undefined reference to `strsvis'
xinstall.o: In function `main':
xinstall.c:(.text+0x2472): undefined reference to `gid_from_group'
xinstall.c:(.text+0x24f8): undefined reference to `uid_from_user'
getid.o: In function

Re: Installing new world failed (install -l)

2013-04-29 Thread Eir Nym
On 29 April 2013 12:42, Gleb Smirnoff gleb...@freebsd.org wrote:
 On Mon, Apr 29, 2013 at 12:39:06PM +0400, Eir Nym wrote:
 E  I came to the following recipe when upgrading from a stale current to
 E  a modern one. This workarounds problem with install(1) and failure of
 E  clang bootstrap with old time.h in /usr/include.
 E 
 E  cd usr.bin/xinstall
 E  make  make install  make clean
 E  cd -
 E  make hierarchy
 E  make includes
 E 
 E  Now, make buildworld is possible.
 E 
 E
 E I've tried this, but with no hope:
 E
 E Warning: Object directory not changed from original
 E /usr/head/src/usr.bin/xinstall
 E cc -O2 -pipe  -I/usr/head/src/usr.bin/xinstall/../../contrib/mtree
 E -I/usr/head/src/usr.bin/xinstall/../../lib/libnetbsd
 E -I/usr/head/src/usr.bin/xinstall/../../lib/libmd -DNDEBUG -std=gnu99
 E -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W
 E -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
 E -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
 E -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
 E -Wnested-externs -Wredundant-decls -Wold-style-definition
 E -Wno-pointer-sign -c xinstall.c
 E xinstall.c: In function 'main':
 E xinstall.c:301: warning: implicit declaration of function 'gid_from_group'
 E xinstall.c:301: warning: nested extern declaration of 'gid_from_group'
 E xinstall.c:311: warning: implicit declaration of function 'uid_from_user'
 E xinstall.c:311: warning: nested extern declaration of 'uid_from_user'
 E xinstall.c: In function 'metadata_log':
 E xinstall.c:1331: warning: implicit declaration of function 'strsvis'
 E xinstall.c:1331: warning: nested extern declaration of 'strsvis'
 E cc -O2 -pipe  -I/usr/head/src/usr.bin/xinstall/../../contrib/mtree
 E -I/usr/head/src/usr.bin/xinstall/../../lib/libnetbsd
 E -I/usr/head/src/usr.bin/xinstall/../../lib/libmd -DNDEBUG -std=gnu99
 E -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W
 E -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
 E -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
 E -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
 E -Wnested-externs -Wredundant-decls -Wold-style-definition
 E -Wno-pointer-sign -c
 E /usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c
 E /usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c: In
 E function 'setup_getid':
 E /usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c:137:
 E warning: implicit declaration of function 'pwcache_groupdb'
 E /usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c:137:
 E warning: nested extern declaration of 'pwcache_groupdb'
 E /usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c:139:
 E warning: implicit declaration of function 'pwcache_userdb'
 E /usr/head/src/usr.bin/xinstall/../../contrib/mtree/getid.c:139:
 E warning: nested extern declaration of 'pwcache_userdb'
 E cc -O2 -pipe  -I/usr/head/src/usr.bin/xinstall/../../contrib/mtree
 E -I/usr/head/src/usr.bin/xinstall/../../lib/libnetbsd
 E -I/usr/head/src/usr.bin/xinstall/../../lib/libmd -DNDEBUG -std=gnu99
 E -fstack-protector -Wsystem-headers -Wall -Wno-format-y2k -W
 E -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes
 E -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch
 E -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline
 E -Wnested-externs -Wredundant-decls -Wold-style-definition
 E -Wno-pointer-sign  -o xinstall xinstall.o getid.o -lmd
 E xinstall.o: In function `metadata_log':
 E xinstall.c:(.text+0x169): undefined reference to `strsvis'
 E xinstall.c:(.text+0x20e): undefined reference to `strsvis'
 E xinstall.o: In function `main':
 E xinstall.c:(.text+0x2472): undefined reference to `gid_from_group'
 E xinstall.c:(.text+0x24f8): undefined reference to `uid_from_user'
 E getid.o: In function `setup_getid':
 E getid.c:(.text+0x7c2): undefined reference to `pwcache_groupdb'
 E getid.c:(.text+0x7e2): undefined reference to `pwcache_userdb'
 E *** Error code 1

 Your current is even older than mine was. Looks like you need to
 build and install new libc, then continue with install(1).

 --
 Totus tuus, Glebius.

I have r226748 which is near FreeBSD-9-Release.
It was I trying to do. But if I'll build libc.. and other things, all
my system will be unavailable.

PS: install from toolchain is correct.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Installing new world failed (install -l)

2013-04-28 Thread Eir Nym
Since -l switch introduced into install(8), I can't build new FreeBSD
box at all.

I do following command set to build new box: (http://eroese.org/mkw.sh)
1) cd /usr/head/src  svn up
2) make buildworld
3) make DESTDIR=/path/to/directory hierarchy distrib-dirs distribution
installworld

This worked for long time but after some point it had been broken. I
found only 20130425 in UPDATING about this, but installing mergemaster
gives nothing, obviously.
I can't compile new install(8) since I have old system like
FreeBSD-9-RELEASE (FreeBSD-CURRENT, r226748) and it doesn't have
needed functions.

The tail of install log is below.

.. (lines removed)
mtree -deU -f /usr/head/src/etc/mtree/BSD.sendmail.dist -p
/usr/home/root/logs/2013-04-28/16.18.03/distro.i386/
./var/spool/clientmqueue missing (created)
install -l s usr/src/sys /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/sys
install: illegal option -- l
usage: install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
   [-o owner] file1 file2
   install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
   [-o owner] file1 ... fileN directory
   install -d [-v] [-g group] [-m mode] [-o owner] directory ...
*** [distrib-dirs] Error code 64

Stop in /usr/head/src/etc.
*** [hierarchy] Error code 1

Stop in /usr/head/src.
*** Error code 1

Stop in /usr/head/src.

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


Re: Installing new world failed (install -l)

2013-04-28 Thread Eir Nym
What should I do in this situation?

-- Eir Nym


On 28 April 2013 23:36, Eir Nym eir...@gmail.com wrote:
 Since -l switch introduced into install(8), I can't build new FreeBSD
 box at all.

 I do following command set to build new box: (http://eroese.org/mkw.sh)
 1) cd /usr/head/src  svn up
 2) make buildworld
 3) make DESTDIR=/path/to/directory hierarchy distrib-dirs distribution
 installworld

 This worked for long time but after some point it had been broken. I
 found only 20130425 in UPDATING about this, but installing mergemaster
 gives nothing, obviously.
 I can't compile new install(8) since I have old system like
 FreeBSD-9-RELEASE (FreeBSD-CURRENT, r226748) and it doesn't have
 needed functions.

 The tail of install log is below.

 .. (lines removed)
 mtree -deU -f /usr/head/src/etc/mtree/BSD.sendmail.dist -p
 /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/
 ./var/spool/clientmqueue missing (created)
 install -l s usr/src/sys 
 /usr/home/root/logs/2013-04-28/16.18.03/distro.i386/sys
 install: illegal option -- l
 usage: install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 file2
install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
[-o owner] file1 ... fileN directory
install -d [-v] [-g group] [-m mode] [-o owner] directory ...
 *** [distrib-dirs] Error code 64

 Stop in /usr/head/src/etc.
 *** [hierarchy] Error code 1

 Stop in /usr/head/src.
 *** Error code 1

 Stop in /usr/head/src.

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


Are clang unsigned comparison warnings in kern/kern_* ok?

2012-09-05 Thread Eir Nym
I've got following warnings [no errors had been generated while
-Werror is in command line] and want to know if they are ok. There are
much more same warnings in modules, but I worry about kernel :
Kernel config: http://eroese.org/_/_/pub/bsd/240070/GENERIC_PF.amd64
src.conf: http://eroese.org/_/_/pub/bsd/240070/src.conf
make.conf: /dev/null
kernel build logs: http://eroese.org/_/_/pub/bsd/240070/kernel.amd64.GENERIC_PF

cc -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality -nostdinc  -I.
-I/usr/head/src/sys -I/usr/head/src/sys/contrib/altq -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
-fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-Werror  /usr/head/src/sys/kern/kern_cpuset.c
/usr/head/src/sys/kern/kern_cpuset.c:654:16: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
for (i = 0; i  (_NCPUWORDS - 1); i++) {
~ ^ 
1 warning generated.

/usr/head/src/sys/kern/kern_poll.c:173:10: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
if (val  0 || val  99)
~~~ ^ ~
1 warning generated.

cc -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality -nostdinc  -I.
-I/usr/head/src/sys -I/usr/head/src/sys/contrib/altq -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
-fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-Werror  /usr/head/src/sys/kern/kern_umtx.c
/usr/head/src/sys/kern/kern_umtx.c:3312:19: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
if (ts32.tv_sec  0 ||
~~~ ^ ~
/usr/head/src/sys/kern/kern_umtx.c:3314:20: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
ts32.tv_nsec  0)
 ^ ~
/usr/head/src/sys/kern/kern_umtx.c:3338:25: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
if (t32.timeout.tv_sec  0 ||
~~ ^ ~
/usr/head/src/sys/kern/kern_umtx.c:3339:63: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
t32.timeout.tv_nsec = 10 || t32.timeout.tv_nsec  0)
 ~~~ ^ ~
4 warnings generated.


cc -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality -nostdinc  -I.
-I/usr/head/src/sys -I/usr/head/src/sys/contrib/altq -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
-fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-Werror  /usr/head/src/sys/kern/uipc_syscalls.c
/usr/head/src/sys/kern/uipc_syscalls.c:356:16: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
if (*namelen  0)
 ^ ~
/usr/head/src/sys/kern/uipc_syscalls.c:1487:12: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
if (*alen  0)
~ ^ ~
/usr/head/src/sys/kern/uipc_syscalls.c:1587:12: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
if (*alen  0)
~ ^ ~
3 warnings generated.

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


Re: Can't build FreeBSD-head with CLANG

2012-09-01 Thread Eir Nym
-- Eir Nym


On 1 September 2012 03:12, Dimitry Andric d...@freebsd.org wrote:
 On 2012-08-30 18:43, Eir Nym wrote:

 On 30 August 2012 20:16, Dimitry Andric d...@freebsd.org wrote:

 ...

 It seems the WERROR= in the xfs module Makefile was right there from the
 start, but it was never removed.  I have compiled it using gcc, and
 there are actually no warnings from gcc at all.  With clang, there are
 several warnings, so I have added a few workaround -Wno-xxx flags for
 them.


 I committed the fixes in r239959.  I tried building your GENERIC_PF
 kernel configuration, and it worked just fine now.

Thank you! I'll review my configurations and rebuild my box.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Can't build FreeBSD-head with CLANG

2012-08-30 Thread Eir Nym
-- Eir Nym


On 30 August 2012 20:16, Dimitry Andric d...@freebsd.org wrote:
 On 2012-08-29 10:41, Eir Nym wrote:
 ...

 /usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
 'fbno' is used uninitialized whenever 'if' condition is false
 [-Werror,-Wsometimes-uninitialized]
   else if (args-minlen == 1  args-alignment == 1 
 !args-isfl
 

 ^~~



 Weird, how are you building the xfs module?  It has WERROR= in its
 Makefile, so the '-Werror' option above should not be there.  This is
 because the XFS code was imported more than 6 years ago, and is very
 unlikely to ever be fixed. :)


 head SVN revision 239793,
 http://eroese.org/_/_/pub/bsd/GENERIC_PF.amd64 — kernel config


 Aha, I finally had some time to look at this again, and it seems that
 when xfs is statically linked into your kernel, the disabling of -Werror
 does not take place.  [Note that linking GPL-contaminated code into your
 kernel proper is, shall we say, ideologically impure ;-)  But that is
 not the issue here.]


I don't like ideological contradictions in any way, but I should
review real using modules in the kernel.

 It seems the WERROR= in the xfs module Makefile was right there from the
 start, but it was never removed.  I have compiled it using gcc, and
 there are actually no warnings from gcc at all.  With clang, there are
 several warnings, so I have added a few workaround -Wno-xxx flags for
 them.


My kernel  world builds correctly with gcc too, but I want to almost
stop using it.

 Currently I'm running a make universe to see if this doesn't cause any
 trouble, and if it completes successfully, I will commit the changes.

 Then I'll mail a note here so you can update your tree and try it out.


Oh! Thank you for your efforts!
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Can't build FreeBSD-head with CLANG

2012-08-29 Thread Eir Nym
-- Eir Nym


On 29 August 2012 01:19, Dimitry Andric d...@freebsd.org wrote:
 On 2012-08-28 23:05, Eir Nym wrote:
 ...

 This one for example:
 cc -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall
 -Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
 -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
 -fdiagnostics-show-option  -Wno-error-tautological-compare
 -Wno-error-empty-body  -Wno-error-parentheses-equality -nostdinc  -I.
 -I/usr/head/src/sys -I/usr/head/src/sys/contrib/altq -D_KERNEL
 -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
 -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
 -mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
 -Werror  /usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c
 -I/usr/head/src/sys/gnu/fs/xfs/FreeBSD
 -I/usr/head/src/sys/gnu/fs/xfs/FreeBSD/support
 -I/usr/head/src/sys/gnu/fs/xfs
 /usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
 'fbno' is used uninitialized whenever 'if' condition is false
 [-Werror,-Wsometimes-uninitialized]
  else if (args-minlen == 1  args-alignment == 1  !args-isfl
 

 ^~~


 Weird, how are you building the xfs module?  It has WERROR= in its
 Makefile, so the '-Werror' option above should not be there.  This is
 because the XFS code was imported more than 6 years ago, and is very
 unlikely to ever be fixed. :)

head SVN revision 239793,
http://eroese.org/_/_/pub/bsd/GENERIC_PF.amd64 — kernel config
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Can't build FreeBSD-head with CLANG

2012-08-29 Thread Eir Nym
-- Eir Nym


On 29 August 2012 12:41, Eir Nym eir...@gmail.com wrote:
 -- Eir Nym


 On 29 August 2012 01:19, Dimitry Andric d...@freebsd.org wrote:
 On 2012-08-28 23:05, Eir Nym wrote:
 ...

 This one for example:
 cc -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall
 -Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
 -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
 -fdiagnostics-show-option  -Wno-error-tautological-compare
 -Wno-error-empty-body  -Wno-error-parentheses-equality -nostdinc  -I.
 -I/usr/head/src/sys -I/usr/head/src/sys/contrib/altq -D_KERNEL
 -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
 -fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
 -mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
 -Werror  /usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c
 -I/usr/head/src/sys/gnu/fs/xfs/FreeBSD
 -I/usr/head/src/sys/gnu/fs/xfs/FreeBSD/support
 -I/usr/head/src/sys/gnu/fs/xfs
 /usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
 'fbno' is used uninitialized whenever 'if' condition is false
 [-Werror,-Wsometimes-uninitialized]
  else if (args-minlen == 1  args-alignment == 1  !args-isfl
 

 ^~~


 Weird, how are you building the xfs module?  It has WERROR= in its
 Makefile, so the '-Werror' option above should not be there.  This is
 because the XFS code was imported more than 6 years ago, and is very
 unlikely to ever be fixed. :)

 head SVN revision 239793,
 http://eroese.org/_/_/pub/bsd/GENERIC_PF.amd64 — kernel config
http://eroese.org/_/_/pub/bsd/kernel.amd64.GENERIC_PF — full logs for it.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Can't build FreeBSD-head with CLANG

2012-08-28 Thread Eir Nym
I can't build FreeBSD (GENERIC  custom kernel) with clang. Build
finishes for i386 and fails for amd64 for same kernels

I have bsd box with following clang version:
 FreeBSD clang version 3.0 (branches/release_30 142614) 20111021
 Target: x86_64-unknown-freebsd10.0
 Thread model: posix

I try to compile it with /dev/null as make.conf and following src.conf:
 WITHOUT_AMD=YES
 WITHOUT_ASSERT_DEBUG=YES
 WITHOUT_ATM=YES
 WITH_BIND_LARGE_FILE=YES
 WITH_BIND_SIGCHASE=YES
 WITH_BSD_GREP=YES
 WITHOUT_CTM=YES
 WITH_CLANG=YES
 WITH_CLANG_EXTRAS=YES
 WITH_CLANG_IS_CC=YES
 WITH_CTF=YES
 WITHOUT_DYNAMICROOT=YES
 WITHOUT_FLOPPY=YES
 WITH_ICONV=YES
 WITHOUT_IPFILTER=YES
 WITHOUT_IPFW=YES
 WITHOUT_IPX=YES
 WITHOUT_IPX_SUPPORT=YES
 WITHOUT_NCP=YES
 WITHOUT_NIS=YES
 WITHOUT_NLS_CATALOGS=YES
 WITHOUT_TCSH=YES
 WITHOUT_RCMDS=YES

but I constantly get warnings (not long ago they was errors) in kernel
like this:
/usr/head/src/sys/netgraph/ng_parse.c:1263:14: warning: comparison of
unsigned expression  0 is always false [-Wtautological-compare]
if (index  0 || eptr - (s + *off) != len) {
~ ^ ~
1 warning generated.

Also I get not initialized warnings and so on.

I don't want build it with gcc.

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


Re: Can't build FreeBSD-head with CLANG

2012-08-28 Thread Eir Nym
-- Eir Nym


On 28 August 2012 22:49, Dimitry Andric d...@freebsd.org wrote:
 On 2012-08-28 18:31, Eir Nym wrote:

 I can't build FreeBSD (GENERIC  custom kernel) with clang. Build
 finishes for i386 and fails for amd64 for same kernels


 What is the error you were getting on amd64?


i386 never failed, amd64 — always

 I have bsd box with following clang version:

 FreeBSD clang version 3.0 (branches/release_30 142614) 20111021
 Target: x86_64-unknown-freebsd10.0
 Thread model: posix


 This is rather old, we went through clang 3.1 some time ago, and
 recently updated it to 3.2.



I use to be sure I use latest clang
make kernel-toolchain buildkernel ${other_args}


 I try to compile it with /dev/null as make.conf and following src.conf:

 ...

 but I constantly get warnings (not long ago they was errors) in kernel
 like this:
 /usr/head/src/sys/netgraph/ng_parse.c:1263:14: warning: comparison of
 unsigned expression  0 is always false [-Wtautological-compare]
  if (index  0 || eptr - (s + *off) != len) {
  ~ ^ ~
 1 warning generated.

 Also I get not initialized warnings and so on.


 You can safely ignore those.  They are just an incentive for the
 maintainers to fix them eventually.  Those tautological comparison
 warnings specifically are quite harmless: the compiler will optimize the
 unused code away anyhow.

I know about ignorance, but compiler fails at them.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Can't build FreeBSD-head with CLANG

2012-08-28 Thread Eir Nym
-- Eir Nym


On 28 August 2012 23:51, Eir Nym eir...@gmail.com wrote:
 -- Eir Nym


 On 28 August 2012 22:49, Dimitry Andric d...@freebsd.org wrote:
 On 2012-08-28 18:31, Eir Nym wrote:

 I can't build FreeBSD (GENERIC  custom kernel) with clang. Build
 finishes for i386 and fails for amd64 for same kernels


 What is the error you were getting on amd64?


 i386 never failed, amd64 — always

 I have bsd box with following clang version:

 FreeBSD clang version 3.0 (branches/release_30 142614) 20111021
 Target: x86_64-unknown-freebsd10.0
 Thread model: posix


 This is rather old, we went through clang 3.1 some time ago, and
 recently updated it to 3.2.



 I use to be sure I use latest clang
 make kernel-toolchain buildkernel ${other_args}


 I try to compile it with /dev/null as make.conf and following src.conf:

 ...

 but I constantly get warnings (not long ago they was errors) in kernel
 like this:
 /usr/head/src/sys/netgraph/ng_parse.c:1263:14: warning: comparison of
 unsigned expression  0 is always false [-Wtautological-compare]
  if (index  0 || eptr - (s + *off) != len) {
  ~ ^ ~
 1 warning generated.

 Also I get not initialized warnings and so on.


 You can safely ignore those.  They are just an incentive for the
 maintainers to fix them eventually.  Those tautological comparison
 warnings specifically are quite harmless: the compiler will optimize the
 unused code away anyhow.

 I know about ignorance, but compiler fails at them.

my simple make world script is in attachment
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Can't build FreeBSD-head with CLANG

2012-08-28 Thread Eir Nym
-- Eir Nym


On 29 August 2012 00:28, Dimitry Andric d...@freebsd.org wrote:
 On 2012-08-28 21:51, Eir Nym wrote:

 On 28 August 2012 22:49, Dimitry Andric d...@freebsd.org wrote:

 On 2012-08-28 18:31, Eir Nym wrote:
 What is the error you were getting on amd64?

 i386 never failed, amd64 — always


 Please post the *exact* error message, otherwise I will not be able to
 help you.


This one for example:
cc -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality -nostdinc  -I.
-I/usr/head/src/sys -I/usr/head/src/sys/contrib/altq -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h
-fno-omit-frame-pointer -mno-aes -mno-avx -mcmodel=kernel
-mno-red-zone -mno-mmx -mno-sse -msoft-float
-fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-Werror  /usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c
-I/usr/head/src/sys/gnu/fs/xfs/FreeBSD
-I/usr/head/src/sys/gnu/fs/xfs/FreeBSD/support
-I/usr/head/src/sys/gnu/fs/xfs
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
'fbno' is used uninitialized whenever 'if' condition is false
[-Werror,-Wsometimes-uninitialized]
else if (args-minlen == 1  args-alignment == 1  !args-isfl 
 ^~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1492:11: note: uninitialized
use occurs here
*fbnop = fbno;
 ^~~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:7: note: remove the 'if'
if its condition is always true
else if (args-minlen == 1  args-alignment == 1  !args-isfl 
 ^~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
'fbno' is used uninitialized whenever '' condition is false
[-Werror,-Wsometimes-uninitialized]
else if (args-minlen == 1  args-alignment == 1  !args-isfl 
 ^~~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1492:11: note: uninitialized
use occurs here
*fbnop = fbno;
 ^~~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: note: remove the
'' if its condition is always true
else if (args-minlen == 1  args-alignment == 1  !args-isfl 
 ^~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
'fbno' is used uninitialized whenever '' condition is false
[-Werror,-Wsometimes-uninitialized]
else if (args-minlen == 1  args-alignment == 1  !args-isfl 
 ^
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1492:11: note: uninitialized
use occurs here
*fbnop = fbno;
 ^~~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: note: remove the
'' if its condition is always true
else if (args-minlen == 1  args-alignment == 1  !args-isfl 
 ^~~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
'fbno' is used uninitialized whenever '' condition is false
[-Werror,-Wsometimes-uninitialized]
else if (args-minlen == 1  args-alignment == 1  !args-isfl 
 ^
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1492:11: note: uninitialized
use occurs here
*fbnop = fbno;
 ^~~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: note: remove the
'' if its condition is always true
else if (args-minlen == 1  args-alignment == 1  !args-isfl 
 ^~~~
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1430:20: note: initialize the
variable 'fbno' to silence this warning
xfs_agblock_t   fbno;
^
 = 0
4 errors generated.
*** [xfs_alloc.o] Error code 1
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: What is current VIMAGE status?

2011-11-13 Thread Eir Nym
I'm sorry it's about VIMAGE option.
-- Eir Nym



On 14 November 2011 02:52, Eir Nym eir...@gmail.com wrote:
 I don't see it in NOTES for LINT and amd64/i386 arch, but it's
 possible to turn it on. Can I consider that this option is currently
 experimental and shouldn't be used critical places?

 -- Eir Nym

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


What is current VINET status?

2011-11-13 Thread Eir Nym
I don't see it in NOTES for LINT and amd64/i386 arch, but it's
possible to turn it on. Can I consider that this option is currently
experimental and shouldn't be used critical places?

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


Re: ZFS boot fails with two pools

2011-07-09 Thread Eir Nym
On 8 July 2011 09:28, Berczi Gabor free...@berczi.be wrote:

 On Jul 7, 2011, at 12:19 PM, Volodymyr Kostyrko wrote:

 2. Try to convince bios to boot from the disk of pool2.

 There is no disk with a singular ZFS pool.

 Any disk from bootable pool.

 Every disk contains two pools. And the BIOS sees only two (maybe three) of 
 them.

 3. You can possibly try deploying /boot/boot0 MBR selector code over disks 
 of data pool. Supplied boot0 code can be used to choose another disk to 
 jump to it during boot process and will remember the last choice.

 I'm not really sure how to do this with GPT. Should I use boot0 instead of 
 pmbr?

 boot0cfg is your old friend

 Cool, how do we get acquinted?

 Actuall I think that code on that stages just tries to boot from the pool on 
 the current disk.

 There are two pools on it...


gpart(8) can set 'bootme' flag for GPT partition, so there no problem
to specify from which partition to boot.


-- Eir Nym

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

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


Re: keyboard driver problem?

2011-07-01 Thread Eir Nym
On 1 July 2011 16:05, Hans Petter Selasky hsela...@c2i.net wrote:
 On Friday 01 July 2011 13:21:35 ti bugmenot wrote:
 I met with the same problem. I do not know how to solve this problem:

 http://lists.freebsd.org/pipermail/freebsd-current/2011-January/022022.html


 Hi,

 Our USB keyboard driver is very simple and does not parse the HID descriptors
 of the keyboard. Maybe that is the reason it is not working.


 Try to set the UQ_KBD_BOOTPROTO for your keyboard.

 usbconfig -d X.Y add_quirk UQ_KBD_BOOTPROTO

 Replug keyboard.


I have same with MS USB keyboard (only numlock, capslock are working).
r221858 doesn't have this bug(?)

-- Eir Nym

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

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


Re: Thoughts on TMPFS no longer being considered highly experimental

2011-06-27 Thread Eir Nym
On 27 June 2011 17:42, David O'Brien obr...@freebsd.org wrote:
 Hi KIB,
 Thanks for the list of issues you know about -- I don't believe we have
 PRs covering those.


 On Thu, Jun 23, 2011 at 11:21:53PM +0300, Kostik Belousov wrote:
 - I believe Peter Holm has more test cases that fails with tmpfs. He
 would have more details. I somewhat remember some panic on execve(2) the
 binary located on tmpfs.

 I've been following the patches you've been passing to Peter Holm as part
 of this thread.  Seems good progress has been made in fixing some of the
 issues.


 Removing the warning will not make the issues coming away.

 Quite true, but is there any other subsystem where we know we have bugs
 and have put up such a scary warning?

 I've never used ZFS on i386, but I understand it is trivial to panic
 with out-of-the-box settings.  We don't print a dire warning for ZFS
 usage on 32-bit platforms.  So I'm not sure we should keep it for TMPFS.

amd64 with 4G ram is also not the best for heavy-loaded ZFS server. I
have to increase kernel memory up to 1.5-2 G to be sure if it works
stable and fast.

-- Eir Nym



 I cannot tell from your response if you're OK or against removing
 the warning.  [especially if your patches pass the Peter Holm test
 and remove some of the bugs]

 --
 -- David  (obr...@freebsd.org)
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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


Re: [Testing wanted] USB patch for HAL

2011-06-24 Thread Eir Nym
On 24 June 2011 17:31, Hans Petter Selasky hsela...@c2i.net wrote:
 Hi,

 [...]


There're no attached file. Please check content type for attachments.
I think, if you'll make shar archive, it'll be better.

-- Eir Nym

 [...]

 --HPS

 ___
 freebsd-gn...@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
 To unsubscribe, send any mail to freebsd-gnome-unsubscr...@freebsd.org


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


Re: Latest -current 100% hang at the late boot stage

2011-06-19 Thread Eir Nym
On 19 June 2011 20:01, Andrey Chernov a...@freebsd.org wrote:
 See subj. It hangs deadly.
 Boot verbose shows nothing unusual. No errors are shown during the boot.
 It always happens before trying to mount root.
 Breaking to DDB shows nothing particular, at least for me:
 http://img196.imageshack.us/img196/2128/19062011.jpg
 (sorry for bad screenshot quality, thats all my mobile can)
 World  kernel are from the same date (today).
 Last working kernel was from May 28.

Which svn revisions and which kernel/world configurations have you tested?

I know that svn revision 222913 works fine (custom kernel).

-- Eir Nym

 --
 http://ache.vniz.net/
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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


Re: Latest -current 100% hang at the late boot stage

2011-06-19 Thread Eir Nym
On 19 June 2011 20:53, Andrey Chernov a...@freebsd.org wrote:
 On Sun, Jun 19, 2011 at 08:11:54PM +0400, Eir Nym wrote:
 On 19 June 2011 20:01, Andrey Chernov a...@freebsd.org wrote:
  See subj. It hangs deadly.
  Boot verbose shows nothing unusual. No errors are shown during the boot.
  It always happens before trying to mount root.
  Breaking to DDB shows nothing particular, at least for me:
  http://img196.imageshack.us/img196/2128/19062011.jpg
  (sorry for bad screenshot quality, thats all my mobile can)
  World  kernel are from the same date (today).
  Last working kernel was from May 28.
 
 Which svn revisions and which kernel/world configurations have you tested?

 I know that svn revision 222913 works fine (custom kernel).

 223296
 I do no test -current builds everyday, so many potentially dangerous
 changes can be sneaked in since May 28.


Thanks, I want to install 223078 soon, and I'll be aware about this.

-- Eir Nym
 --
 http://ache.vniz.net/

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


Re: WITHOUT_INSTALLLIB broken?

2011-06-16 Thread Eir Nym
On 16 June 2011 16:55, Ruslan Ermilov r...@freebsd.org wrote:
 On Thu, Jun 16, 2011 at 01:50:17PM +0200, Milan Obuch wrote:
 Hi,

 I encountered an error when WITHOUT_INSTALLLIB option is specified
 for 'make buildworld' process. I documented this issue with build logs
 at my page, http://www.dino.sk/build/2011-06-16-log1 and
 http://www.dino.sk/build/2011-06-16-log2 show how to test this. At this
 time, there is no /etc/make.conf nor /etc/src.conf.

 Any idea what's wrong with libegacy.a here?

 This option wasn't designed for build, only for install.  It's like
 WITHOUT_TOOLCHAIN, which is documented to not work for build targets.


Should this be simply ignored for build targets?


 --
 Ruslan Ermilov
 r...@freebsd.org
 FreeBSD committer
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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


Re: WITHOUT_INSTALLLIB broken?

2011-06-16 Thread Eir Nym
On 17 June 2011 00:18, Ruslan Ermilov r...@freebsd.org wrote:
 On Thu, Jun 16, 2011 at 05:09:05PM +0400, Eir Nym wrote:
 On 16 June 2011 16:55, Ruslan Ermilov r...@freebsd.org wrote:
  On Thu, Jun 16, 2011 at 01:50:17PM +0200, Milan Obuch wrote:
  Hi,
 
  I encountered an error when WITHOUT_INSTALLLIB option is specified
  for 'make buildworld' process. I documented this issue with build logs
  at my page, http://www.dino.sk/build/2011-06-16-log1 and
  http://www.dino.sk/build/2011-06-16-log2 show how to test this. At this
  time, there is no /etc/make.conf nor /etc/src.conf.
 
  Any idea what's wrong with libegacy.a here?
 
  This option wasn't designed for build, only for install.  It's like
  WITHOUT_TOOLCHAIN, which is documented to not work for build targets.
 

 Should this be simply ignored for build targets?

 build targets utilize install targets internally, so this is
 hardly doable.


cd ${.CURDIR}  make ${CURRENT_BUILD FLAGS} ${SUPPORTED_BUILD_FLAGS}
__MAKE_CONF=/dev/null SRC_CONF=/dev/null  targets ?

-- Eir Nym

 --
 Ruslan Ermilov
 r...@freebsd.org
 FreeBSD committer

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


Re: rc.d script to load kernel modules

2011-06-13 Thread Eir Nym
On 11 June 2011 22:17, Doug Barton do...@freebsd.org wrote:
 Howdy,

 Per discussion on -arch and the svn list about improving boot time and
 stripping down the kernel to just that-which-cannot-be-modularized I created
 the attached script to kldload modules that don't need to be in loader.conf.
 It cut quite a bit of time off my boot, so hopefully it will be useful to
 others as well.

 To use it just put everything that is being _load'ed in loader.conf into
 kld_list in rc.conf[.local]. For example, mine has:

 kld_list='umass coretemp ichwd linux nvidia if_wpi'

 If there is agreement that this is a good direction to go I'll be happy to
 commit this along with the relevant /etc/defaults/rc.conf and rc.conf.5
 changes.


How do you would suggest set tunables, which are readonly or have no
sysctl(8) equivalent after boot-time? AFAIK loader can't set tunable
if module is not loaded at boot-time.


 hth,

 Doug

 --

        Nothin' ever doesn't change, but nothin' changes much.
                        -- OK Go

        Breadth of IT experience, and depth of knowledge in the DNS.
        Yours for the right price.  :)  http://SupersetSolutions.com/


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

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


Re: rc.d script to load kernel modules

2011-06-13 Thread Eir Nym
On 13 June 2011 06:32, Garrett Cooper yaneg...@gmail.com wrote:
 On Sun, Jun 12, 2011 at 11:11 PM, Eir Nym eir...@gmail.com wrote:
 On 11 June 2011 22:17, Doug Barton do...@freebsd.org wrote:
 Howdy,

 Per discussion on -arch and the svn list about improving boot time and
 stripping down the kernel to just that-which-cannot-be-modularized I created
 the attached script to kldload modules that don't need to be in loader.conf.
 It cut quite a bit of time off my boot, so hopefully it will be useful to
 others as well.

 To use it just put everything that is being _load'ed in loader.conf into
 kld_list in rc.conf[.local]. For example, mine has:

 kld_list='umass coretemp ichwd linux nvidia if_wpi'

 If there is agreement that this is a good direction to go I'll be happy to
 commit this along with the relevant /etc/defaults/rc.conf and rc.conf.5
 changes.


 How do you would suggest set tunables, which are readonly or have no
 sysctl(8) equivalent after boot-time? AFAIK loader can't set tunable
 if module is not loaded at boot-time.

    Not true. Kernel tunables are really not that different (in
 concept) from kernel-level environment variables. Certainly, they
 would have less value if one's loading modules at boot (depending when
 things are done -- i.e. how closely the sysctl pseudo service is run
 to the proposed kld pseudo service), but sysctls can't be set until
 the module (or respective OID leaf) has been created by the kernel
 (somehow, i.e. via driver initialization, etc).
 Thanks,
 -Garrett

I see,

 I use tunables and it will be great if I can add tunables for module
while load them from user space with rc(8).
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


boot0cfg in future releases.

2011-06-13 Thread Eir Nym
Hi folks,

I haven't see man page for boot0cfg(8) for FreeBSD 9-Current on
FreeBSD website, but it exists for 8.x and earlier versions. Is it
website bug or this utility will be removed in the future?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-10 Thread Eir Nym
2011/6/10 Andrey V. Elsukov bu7c...@yandex.ru:
 On 10.06.2011 10:50, Eir Nym wrote:
 messages on the start of this dmesg are for more pages of (I have see
 them for several seconds on same hardware)
 kernel config : http://eroese.org/_/_/pub/bsd/222889/GENERIC_PF

 You have mixed old partitioning classes with GEOM_PART.
 You should remove from the kernel at least:
 options         GEOM_BSD
 options         GEOM_MBR
 options         GEOM_PC98
 options         GEOM_VOL


This should be documented.

 --
 WBR, Andrey V. Elsukov


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


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-10 Thread Eir Nym
On 10 June 2011 11:08, Eir Nym eir...@gmail.com wrote:
 2011/6/10 Andrey V. Elsukov bu7c...@yandex.ru:
 On 10.06.2011 10:50, Eir Nym wrote:
 messages on the start of this dmesg are for more pages of (I have see
 them for several seconds on same hardware)
 kernel config : http://eroese.org/_/_/pub/bsd/222889/GENERIC_PF

 You have mixed old partitioning classes with GEOM_PART.
 You should remove from the kernel at least:
 options         GEOM_BSD
 options         GEOM_MBR
 options         GEOM_PC98
 options         GEOM_VOL


 This should be documented.

[r222913] After rebuilding and reinstalling world without these
options, anything become OK as I see. Thanks for advice.


 --
 WBR, Andrey V. Elsukov



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


Re: 9.0-CURRENT-201105-amd64 install kernel panic

2011-06-10 Thread Eir Nym
On 10 June 2011 19:48, K. Macy km...@freebsd.org wrote:
 This recent commit changed the way that the value for size being
 passed to m_getjcl is initialized. Not seeing any obvious bugs, and
 not having any additional context I would guess that that you're
 receiving an interrupt before adapter-rx_mbuf_sz is set. I trust jfv@
 to look in to this shortly.

 http://svnweb.freebsd.org/base/head/sys/dev/e1000/if_em.c?r1=214362r2=214363;

 Thanks



You can try my custom kernel  world if you find it applicable for
your tasks. I use it for my computer
http://eroese.org/_/_/pub/bsd/222913

I don't know how to roll world and kernel to USB image without mount
and other privileges, so you need to tar -xpf world and kernel.

 On Fri, Jun 10, 2011 at 9:19 PM, Kim Culhan w8hd...@gmail.com wrote:
 On Fri, June 10, 2011 11:22 am, Kim Culhan wrote:
 Booting from FreeBSD-9.0-CURRENT-201105-amd64-memstick
 the kernel panics:

 panic: m_getzone: m_getjcl: invalid cluster type

 Found a ps2 keyboard works in the debugger (not usb) and backtrace is here:

 http://www.flickr.com/photos/opensolaris/5819107302/in/photostream
 -kim
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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

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


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Eir Nym
On 8 June 2011 23:12, Vladislav V. Prodan univers...@ukr.net wrote:
 08.06.2011 17:54, Eir Nym wrote:

 On 8 June 2011 16:10, Vladislav V. Prodanunivers...@ukr.net  wrote:

 08.06.2011 11:10, Eir Nym wrote:

 gpart show is work now, but not when I load zfs into memory and try to
 add zpool into.

 and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'

 Output:
 gpart show ada0

 #gpart show ada0
 =         63  1250263665  ada0  MBR  (596G)
           63   411807627     1  freebsd  (196G)
    411807690          54        - free -  (27k)
    411807744      202752     2  !239  (99M)
    412010496      204800     3  ntfs  [active]  (100M)
    412215296   838045696     4  ntfs  (399G)
   1250260992        2736        - free -  (1.3M)
 #gpart show ada0s1
 =         0  411807627  ada0s1  BSD  (196G)
           0  402653247       1  freebsd-zfs  (192G)
   402653247    9154380       2  freebsd-swap  (4.4G)



 gpart modify -i 1 -l disk0 ada0s1
gpart: Invalid argument

after recreate ada0s1 there gpart shows 4 GEOMs with BSD partitioning
(numbers are same as above):
ada0s1
ada0s1
ada0s1c
ada0s1c


--
If I create BSD scheme with old good bsdlabel(8): (numbers are written
by hands to minimize reboot count)
#gpart delete -i 1 ada0s1
#gpart delete -i 2 ada0s1
#gpart destroy ada0s1
#bsdlabel -w ada0s1
#gpart show ada0s1
= 0 411807627 ada0s1 BSD (196G)
  0 16 -free - (8.0k) --- used by
BSDLabel data
 16 411807611 1 !0 (196G)  --- ada0s1a

and this label is correct.

I think that GEOM part create and add commands must add some gap
before partitions for any schemes and bug is here.

 and after reboot try:
 zpool create tank /dev/gpt/disk0






 --
 Vladislav V. Prodan
 VVP24-UANIC
 +380[67]4584408
 +380[99]4060508
 vla...@jabber.ru
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Eir Nym
On 9 June 2011 10:45, Eir Nym eir...@gmail.com wrote:
 On 8 June 2011 23:12, Vladislav V. Prodan univers...@ukr.net wrote:
 08.06.2011 17:54, Eir Nym wrote:

 On 8 June 2011 16:10, Vladislav V. Prodanunivers...@ukr.net  wrote:

 08.06.2011 11:10, Eir Nym wrote:

 gpart show is work now, but not when I load zfs into memory and try to
 add zpool into.

 and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'

 Output:
 gpart show ada0

 #gpart show ada0
 =         63  1250263665  ada0  MBR  (596G)
           63   411807627     1  freebsd  (196G)
    411807690          54        - free -  (27k)
    411807744      202752     2  !239  (99M)
    412010496      204800     3  ntfs  [active]  (100M)
    412215296   838045696     4  ntfs  (399G)
   1250260992        2736        - free -  (1.3M)
 #gpart show ada0s1
 =         0  411807627  ada0s1  BSD  (196G)
           0  402653247       1  freebsd-zfs  (192G)
   402653247    9154380       2  freebsd-swap  (4.4G)



 gpart modify -i 1 -l disk0 ada0s1
 gpart: Invalid argument

 after recreate ada0s1 there gpart shows 4 GEOMs with BSD partitioning
 (numbers are same as above):
 ada0s1
 ada0s1
 ada0s1c
 ada0s1c


 --
 If I create BSD scheme with old good bsdlabel(8): (numbers are written
 by hands to minimize reboot count)
 #gpart delete -i 1 ada0s1
 #gpart delete -i 2 ada0s1
 #gpart destroy ada0s1
 #bsdlabel -w ada0s1
 #gpart show ada0s1
 = 0 411807627 ada0s1 BSD (196G)
  0 16 -free - (8.0k)                                     --- used by
 BSDLabel data
  16 411807611 1 !0 (196G)                          --- ada0s1a

 and this label is correct.

 I think that GEOM part create and add commands must add some gap
 before partitions for any schemes and bug is here.


http://www.freebsd.org/cgi/query-pr.cgi?pr=157723
http://www.freebsd.org/cgi/query-pr.cgi?pr=157724

 and after reboot try:
 zpool create tank /dev/gpt/disk0






 --
 Vladislav V. Prodan
 VVP24-UANIC
 +380[67]4584408
 +380[99]4060508
 vla...@jabber.ru
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


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


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Eir Nym
2011/6/9 Andrey V. Elsukov a...@freebsd.org:
 On 09.06.2011 11:31, Eir Nym wrote:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=157723

 Can't reproduce.
Which revision do you use?

Following link for mail is about this.


 http://www.freebsd.org/cgi/query-pr.cgi?pr=157724

 First of read this tread:
 http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/062744.html

 and after reboot try:
 zpool create tank /dev/gpt/disk0


 --
 WBR, Andrey V. Elsukov



I've already compilled r222889 and will check it today.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Eir Nym
2011/6/9 Andrey V. Elsukov bu7c...@yandex.ru:
 On 09.06.2011 13:32, Eir Nym wrote:
 Which revision do you use?

 Following link for mail is about this.
 http://www.freebsd.org/cgi/query-pr.cgi?pr=157724

 First of read this tread:
 http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/062744.html

 I mean that BSD scheme created with gpart(8) is not invalid.
 You always can use -b start_offset when creating partitions to preserve
 metadata area. Also you can use partition with zero offset for UFS.

 I've already compilled r222889 and will check it today.

 I have r222733. But it is no matter, nothing was changed in this area
 for 2-3 weeks.

GEOM will say it only after reboot.
part of dmesg log:

GEOM_LABEL[1]: MSDOSFS: gzero: no FAT signature found.
ugen0.1: Intel at usbus0
uhub0: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0
ugen1.1: Intel at usbus1
uhub1: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus1
ugen2.1: Intel at usbus2
uhub2: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus2
ugen3.1: Intel at usbus3
uhub3: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus3
ugen4.1: Intel at usbus4
uhub4: Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus4
GEOM_LABEL[1]: MSDOSFS: gzero: no FAT signature found.
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: SAMSUNG HM641JI 2AJ10001 ATA-8 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 610480MB (1250263728 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
SMP: AP CPU #1 Launched!
Timecounter TSC frequency 1666519680 Hz quality 800
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
GEOM_LABEL[1]: MSDOSFS: ada0: FAT12/16 volume not valid.
GEOM_LABEL[1]: MSDOSFS: ada0s1: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s2: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s3: FAT32 volume not valid.
GEOM_LABEL[1]: Label for provider ada0s3 is ntfs/System Reserved.
GEOM_LABEL[1]: MSDOSFS: ada0s4: FAT32 volume not valid.
GEOM_LABEL[1]: MSDOSFS: ada0s1: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s2: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s2, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s3: FAT32 volume not valid.
GEOM_LABEL[1]: Label System Reserved(ntfs/System Reserved) already
exists (ada0s3).
g_dev_taste: make_dev_p() failed (gp-name=ada0s3, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s4: FAT32 volume not valid.
g_dev_taste: make_dev_p() failed (gp-name=ada0s4, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
GEOM: ada0s1a: invalid disklabel.
GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1c: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
GEOM: ada0s1a: invalid disklabel.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1c: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1c, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1ca: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1cb: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1aa: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1ab: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1ac: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1ca: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1ca, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1cb: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1cb, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1aa: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1aa, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1ab: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1ab, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1ac: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1ac, error=17)


 --
 WBR, Andrey V. Elsukov


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


[r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-08 Thread Eir Nym
I have FreeBSD-CURRENT r77. I try to install ZFS root into MBR
using manual on wiki page.

There is some problem with GEOM and BSD label:

# gpart create -s BSD ada0s1
# gpart add -s 192G -t freebsd-zfs ada0s1
# gpart add -t freebsd-swap ada0s1
#gpart show ada0s1
...

gpart show is work now, but not when I load zfs into memory and try to
add zpool into.

and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'


PS: there're too much bsdlabel devices (previous releases gives much
less device nodes (there was no aa, ab, ac, ca, cb)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-08 Thread Eir Nym
On 8 June 2011 16:10, Vladislav V. Prodan univers...@ukr.net wrote:
 08.06.2011 11:10, Eir Nym wrote:

 gpart show is work now, but not when I load zfs into memory and try to
 add zpool into.

 and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'

 Output:
 gpart show ada0

#gpart show ada0
=63  1250263665  ada0  MBR  (596G)
  63   411807627 1  freebsd  (196G)
   411807690  54- free -  (27k)
   411807744  202752 2  !239  (99M)
   412010496  204800 3  ntfs  [active]  (100M)
   412215296   838045696 4  ntfs  (399G)
  12502609922736- free -  (1.3M)
#gpart show ada0s1
=0  411807627  ada0s1  BSD  (196G)
  0  402653247   1  freebsd-zfs  (192G)
  4026532479154380   2  freebsd-swap  (4.4G)


 --
 Vladislav V. Prodan
 VVP24-UANIC
 +380[67]4584408
 +380[99]4060508
 vla...@jabber.ru
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

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


Re: IPv4 broken on r222048

2011-06-08 Thread Eir Nym
On 7 June 2011 22:11, Garrett Cooper yaneg...@gmail.com wrote:
 On Tue, Jun 7, 2011 at 11:00 AM, Garrett Cooper yaneg...@gmail.com wrote:
 On Tue, Jun 7, 2011 at 10:41 AM, Bjoern A. Zeeb
 bzeeb-li...@lists.zabbadoz.net wrote:

 On Jun 7, 2011, at 5:29 PM, Garrett Cooper wrote:

 Hi,
    I'm running into an issue where ifconfig isn't executing properly,
 and is emitting the following message:

 # ifconfig re0 inet w.x.y.z
 ifconfig: can't set link-level netmask or broadcast
 #
 ...
    I haven't traced down what commit exactly is causing this, but the
 issue appears to be a purely userland based problem so far (I
 accidentally forgot to swap kernels before booting up the second time
 and the symptoms are exactly the same).

 Yes, you lost.  My changes did that.  You are the second to hit it.
 Your kernel does not have FEATURES()  present and the new user space
 that came a couple of days later expect it and disable your IPv4
 because of that.

 The real problem is when people update the kernel, then update world
 and then figure out they need to go back to kernel.old.
 I'll add an UPDATING entry.

 That I would expect, but I just built the kernel last night, installed
 it, and am running it right now and I run into the same issue as I do
 with the older kernel :). Was there any magic foo that I needed to use
 to get FEATURES working properly, or was it supposed to be seamless? I
 don't know because I never had a need to fiddle around with the
 framework..

 Is there a tool I can use (minus banging on the interfaces in C) to
 determine what the features are on the machine to diagnose why things
 aren't working for me?

 Answering my own question:

 sysctl kern.features.inet
 sysctl kern.features.inet6

 Hmmm... they turn up unknown OIDs. Need to do some digging to discover
 why that's the case..


Oh... And no UPDATING messages. It's bad practice for this features.

 You need an old user land or a new kernel to recover.

 Looks like I need an old userland, because a new kernel/userland combo
 doesn't seem to work as advertised :/...

    I have both INET and INET6 built into my kernel and userland, but
 my immediate upstream router only supports IPv4 right now. I tried
 building with WITHOUT_INET6=yes to see if it made a difference, and it
 didn't.
    I'll test any patches needed to remedy the issue. Thankfully I
 have flash media I can use in the meantime to push code between my two
 boxes :)

 Welcome to FreeBSD HEAD, being a developer and not following the rule;-)

 Sorry for the hassle though.

 It's ok -- that's why I have two near workstations -- one for daily
 use and the other for testing :).

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

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


Re: screen: Could not write /nonexistent

2011-02-27 Thread Eir Nym
On 19 February 2011 21:38, Joachim Tingvold joac...@tingvold.com wrote:
 Hi,

 I did a rebuild of my system today. The last time I did this was friday, 4th
 of february 13:39. After I rebuilt the system, screen produces a short
 error-message in it's splash-screen (both when starting a new
 screen-session, and when attaching to an existing session), stating Could
 not write /nonexistent. After a few searches online, I cannot seem to find
 anything specific to this problem. Screen seems to running fine, though, so
 the only issue so far is that it's annoying. (-:

 I guess this could be caused by different things, but as it worked
 yesterday, I can only assume that this happened because I did a rebuild. I
 also tried to reinstall screen, but without luck.

 Any ideas?


I have same issues, but no idea. Also there're some problems with writing utmp

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


Re: Wow... (-- blown away at performance)

2011-02-22 Thread Eir Nym
On 22 February 2011 11:15, Garrett Cooper yaneg...@gmail.com wrote:
    I don't know what to say, but r218938 screams with flash videos
 (native Linux speed). Not sure if it's the new binutils or if it's the
 new linuxulator patches, but I can run multiple instances of youtube
 in parallel (5 total with other miscellaneous flash animation) without
 it totally lagging out Firefox/X11, and it appears to close the
 instances of firefox properly now. Hopefully this version fares better
 than r218113 did (I think I hit a kernel bug after 2 weeks uptime,
 where my system just hardlocked for no apparent reason).
    Anyhow, hope others have similar results.
 Cheers!
 -Garrett

 $ uname -a
 FreeBSD bayonetta.local 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r218938M:
 Mon Feb 21 23:10:51 PST 2011
 gcooper@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA  amd64
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Which FlashPlayer version do you test? Adobe has made significant
performance changes in 10.2 (from 10.1). You can search for StageVideo
performance to learn more about. Youtube already use them since 10.2
beta
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Can't buildworld since Clang update

2011-02-22 Thread Eir Nym
On 22 February 2011 21:11, Dimitry Andric d...@freebsd.org wrote:
 On 2011-02-22 18:38, datastream datastream.freecity wrote:

 In /etc/make.conf, I only add 'CFLAGS+=-fno-omit-frame-pointer'.And
 removed
 all files in /usr/obj. /usr/src sync with
 http://svn.freebsd.org/base/head.
 #make buildkernel

 Before you do make buildkernel, always run make buildworld, or at
 least make kernel-toolchain.  This ensures you have an up-to-date ld
 (and other tools) under /usr/obj.

 That said, these steps are normally only needed when e.g. binutils or
 other toolchain components have been upgraded.  This has happened so
 seldom in the past few years, that people seem to have forgotten how
 bootstrapping works. :)

Nope! `make kernel-toolchain` is also important for cross-compile
builds to be sure that anything is done.

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

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


Re: current repeateble crash in 2 places

2011-02-22 Thread Eir Nym
On 21 February 2011 13:26, Andrey Smagin samsp...@mail.ru wrote:
 today current
 crash with loaded mpd5

 1st place:
 ipwf_chk
 ipfw_check_hook
 pfil_run_hooks
 ip_output
 tcp_output      repeated
 tcp_mtudisc    ~20 times
 tcp_ctlinput
 icmp_input
 ip_input
 swi_net
 intr_event_execute_handlers

 2nd place
 flowtable_lookup
 flowteble_lookup_mbuf
 ip_output
 tcp_output           ~ repeated
 tcp_mtudisc            20 times
 tcp_ctlinput
 icmp_input
 ip_input
 netisr_dispatch_src
 ng_iface_rcvdata
 ng_apply_item                                repeated
 ng_snd_item                                   3
 ng_pppoe_rcvdata_ether             times
 ng_apply_item
 ng_snd_item
 ether_demux
 ether_input
 em_rxeof
 em_msix_rx
 inthr_event_execute_handlers
 ithread_loop



What does it mean?

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

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


Sade(8) compile problem

2011-02-20 Thread Eir Nym
Hello guys,

I have amd64 FreeBSD-Current box (r214751) and want to build fresh
system to install, but compile fails every time . Configuration files
are same.

The failure is in sade(8), where compiller try to find dialog h in
/usr/src/usr.sbin/../../gnu/lib/libdialog/dialog.h , not in libadialog
directory. First appearance of this failure  is about month ago (I
have autobuild system)

make.conf is /dev/null
src.conf contains following keys turned on:

WITHOUT_ATM
WITHOUT_AMD
WITH_BSD_GREP
WITHOUT_CTM
WITHOUT_FLOPPY
WITHOUT_FREEBSD_UPDATE
WITHOUT_IPFILTER
WITHOUT_IPFW
WITHOUT_IPX
WITHOUT_NIS
WITHOUT_NLS_CATALOGS
WITHOUT_RCMDS
WITHOUT_TCSH
WITH_BIND_LARGE_FILE
WITH_BIND_SIGCHASE
WITH_GPIO
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: tmpfs out of space (ZFS related?)

2010-11-21 Thread Eir Nym
On 22 November 2010 00:22, Ivan Voras ivo...@freebsd.org wrote:
 I got a curious error today while starting PostgreSQL, complaining about
 out of space errno while creating lock file on /tmp.

 /tmp on this machine is mounted as tmpfs and indeed, here is the statistic:

 biggie:/# df -i
 Filesystem    1M-blocks  Used  Avail Capacity iused     ifree %iused Mounted
 on
 /dev/mfid0s1a      9912  5193   3926    57%  306079   1012831   23%   /
 devfs                 0     0      0   100%       0         0  100%   /dev
 fdescfs               0     0      0   100%       4     11092    0% /dev/fd
 tmpfs                 0     0      0   100%       9         0  100%   /tmp
 tank             376044     0 376044     0%       4 770138347    0%   /tank
 tank/ports       376658   614 376044     0%  145919 770138347    0%
 /usr/ports
 tank/mysql       376073    29 376044     0%     102 770138347    0%
 /var/db/mysql
 tank/pgdata90    400469 24425 376044     6%    1047 770138347    0%
 /tank/pgdata90

 On the other hand, top reports this:

 last pid: 79667;  load averages:  0.08,  0.68,  0.77    up 1+09:12:13
 00:11:33
 44 processes:  1 running, 43 sleeping
 CPU:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
 Mem: 13M Active, 46M Inact, 15G Wired, 232K Cache, 1458M Buf, 8358M Free
 Swap: 1024M Total, 1024M Free

 Note the 8358M free report.

 The server has ZFS and was doing IO intensive database work on it; the 8 GB
 free memory comes from PostgreSQL being restarted and freeing the memory
 (but failing to start again...).

 Starting PostgreSQL gets me this message:
 Nov 22 00:18:24 biggie postgres[79696]: [1-1] FATAL:  could not write lock
 file /tmp/.s.PGSQL.5432.lock: No space left on device

 This is 8-STABLE amd64.

 Running touch /tmp/abc works, and creates a file. Running echo abc 
 /tmp/abc doesn't return an error but *doesn't write anything to the file*,
 just creates a directory entry.

 The status doesn't change over time, i.e. df on tmpfs always shows 0
 free.


Which type of MFS do you use? I think you shold use swap-backed for
your /tmp, not malloc-based. Last type is only for in-kernel file
system.

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

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


Re: tmpfs out of space (ZFS related?)

2010-11-21 Thread Eir Nym
On 22 November 2010 00:47, Bruce Cran br...@cran.org.uk wrote:
 On Mon, 22 Nov 2010 00:43:03 +0300
 Eir Nym eir...@gmail.com wrote:

 Which type of MFS do you use? I think you shold use swap-backed for
 your /tmp, not malloc-based. Last type is only for in-kernel file
 system.

 It's tmpfs(5), not md(4).


ah, sorry, I use md(4) for this in current configuration

 --
 Bruce Cran

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


Re: tmpfs out of space (ZFS related?)

2010-11-21 Thread Eir Nym
On 22 November 2010 01:00, Eir Nym eir...@gmail.com wrote:
 On 22 November 2010 00:47, Bruce Cran br...@cran.org.uk wrote:
 On Mon, 22 Nov 2010 00:43:03 +0300
 Eir Nym eir...@gmail.com wrote:

 Which type of MFS do you use? I think you shold use swap-backed for
 your /tmp, not malloc-based. Last type is only for in-kernel file
 system.

 It's tmpfs(5), not md(4).



I wonder if you can create FIFO and sockets with md(4). md(4) is
geometry, not filesystem.
tmpfs(5) doesn't support this file types as I can see in FreeBSD source code.


 --
 Bruce Cran


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


Re: Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel.

2010-11-13 Thread Eir Nym
On 13 November 2010 15:52, crocket crockabisc...@yahoo.com wrote:
 TEKEN_XTERM turns on xterm mode.
 I compiled a kernel with TEKEN_XTERM, and changed cons25 to xterm in 
 /etc/ttys.

 When I executed vim on a console, the keyboard acted weirdly.
 After setting TERM back to cons25 again, vim acted normally again on consoles.
 I could assign xterm console characters in /etc/termcap to fkeys by writing 
 keychanges=fkeycode consolecharacter in /etc/rc.conf, but it is just a 
 quick hack, and it is just a solution for me but not for everyone.


Oh... you can do `vidcontrol -T xterm` and your keybindings will be correct.

 I would be glad keymaps in X11 and consoles became the same with TEKEN_XTERM 
 in the kernel.
 If the keymaps in consoles and X11 are the same, 99% of configurations I 
 needed to make in applications will be unneeded. It will benefit everyone.



As Ed said some days before, you should use TEKEN_XTERM _or_
TEKEN_CONS25 in your kernel.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Keymaps in X11 and consoles should be the same with TEKEN_XTERM in the kernel.

2010-11-13 Thread Eir Nym
On 13/11/2010, crocket crockabisc...@yahoo.com wrote:
 Does Delete key match \E[3~ on FreeBSD-CURRENT xterm mode?
 It's nice to see backspace key match ^?(ASCII DEL), too, since ^H(Ctrl-H) is
 reserved by such applications as vim and emacs.


For witch action C-H is reserved in vim(1) ? vim, emacs, zsh, and many
others use termcap(5) to determine which key generate which sequence.

Please note, that xterm and xterm-colors termcap entries are differs,
and last is not usable in FreeBSD-CURRENT TEKEN_XTERM console.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Syscons and termcap

2010-11-11 Thread Eir Nym
On 9 November 2010 20:45, Ed Schouten e...@80386.nl wrote:
 * Renato Botelho rbga...@gmail.com, 20101109 17:08:
 Well, few weeks ago I moved from ISO-8859-1 to UTF-8 on my Xorg
 environment, and after reading this I decided to make a test.

 I rebuilt my 9.0-current (r215031) with option TEKEN_UTF8 in kernel
 config, and after configure my syscons to use cp850-* fonts i can
 see UTF-8 chars properly \o/

 Well, the point here is that it just performs some really hackish
 translation to CP437, not CP850, on the output path. It is really not
 robust. Copy-pasting is also broken because of it, because it pastes
 CP437 characters.

 The only thing i cannot do here is to type chars with accent like áé
 on console, because it seems to don't respect deadkeys, when I
 press ' the char ' is show and never wait the next char to compose
 a new one when necessary. Is it a knwon issue or i'm doing
 something wrong?

 This is a known issue, since there is no translation from Unicode code
 points to UTF-8 sequences. In other words, if you press ë, the keyboard
 layer will properly send a 235 to Syscons, but instead of encoding it as
 0xC3 0xA9, will just emit a single byte, having value 0xE9.

 Maybe a patch like this could already get that working, but it's just a
 quick hack.

        http://80386.nl/pub/syscons-utf8.txt

 Greetings,
 --
  Ed Schouten e...@80386.nl
  WWW: http://80386.nl/


Thanks Ed, I'll move back to CONS25 before I can load codepage into
kernel. I don't like to always see question marks instread normal
characters in SC_PIXEL_MODE.

PS: I prefer kernel console driver for some reasons.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Syscons and termcap

2010-11-08 Thread Eir Nym
I've compiled -CURRENT kernel with UTF-8 and CONS25 support. ( r214751 )

in xterm emulation mode I have problems with bindings for some keys,
such as Home
If I start vis(1) and press Home, I always get ^[[H sequence instead
of ^[OH which is defined in termcap (5) file.

I get correct results after switching to cons25.

What do I wrong ? Does sc(4) driver in current correctly support
xterm-like key bindings?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: having 'src' and 'obj' in some other place

2010-11-01 Thread Eir Nym
On 31 October 2010 23:15, Matthias Apitz g...@unixarea.de wrote:

 Hello,

 I compiled a 9-CURRENT from SVN but having it in a non default place,
 in /home/guru/9-CURRENT/src. To compile kernel and world I set
 MAKEOBJDIRPREFIX to /home/guru/9-CURRENT/obj and all went fine. Then I
 installed kernel und world to the USB key using DESTDIR set to /mnt.

 Because the idea is to use the USB key for further installation a copied
 the 'src' and 'obj' to it as well with:

 # cp -Rp /home/guru/9-CURRENT/src /mnt/usr
 # cp -Rp /home/guru/9-CURRENT/obj /mnt/usr

 The USB key boots fine. From this USB key I now wanted to install the
 system to a partitioned hard disk, again with something like:

 # cd /usr/src
 # make installworld DESTDIR=/mnt

 where below /mnt now the file system of the disk was mounted. This failed
 with messages about 'install: ... not found' and the way around was to
 move /usr/src again on the USB key to a faked location of
 /home/guru/9-CURRENT/src, and as well 'obj'. After this all went fine.


You can experiment with moving /usr/obj//home/guru/9-CURRENT/src to
/usr/obj/usr/src

 Question: Why is this so hardwired bound to the original location of
 'src' and 'obj'?


you can see /usr/share/mk/bsd.obj.mk for details. make(1) creates
directory ${MAKEOBJDIRPREFIX}/${.CURDIR} . It is useful when you make
world for yourself, do some development stuff with another things,
etc.

 Thanks

        matthias
 --
 Matthias Apitz
 t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
 e g...@unixarea.de - w http://www.unixarea.de/
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


I do installation with another method:
On build server I make world, install it into some directory, and make
cpio(1) archive to save file rights. Then I copy archive to usb and
unpack it into new system.

One more question for community: does cpio(1) archive format save file
flags (see chflags(1))?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


BIND from system and from ports

2010-04-07 Thread Eir Nym
All is good in BIND in system, except it depends on ports tree with
various options.
I have to do followed algorithm, to enable these options:
1) make and install base system
2) install needed dependencies from ports tree
3) rebuild and reinstall world

This is more complex than:
1) make and install base system
2) install same(?) BIND from ports tree with same options

Why does base system has any dependencies from ports?
I know about application features, but special cases aren't special
enough to break the rules, isn't it?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org