Re: how do i cross build world/kernel with clang?

[David Chisnall]

On 15 Sep 2013, at 23:28, "Joe Holden"  wrote:

> Are you still playing with this?  Reason I ask is that I tried to build
> world with clang for the crack and it bails with:
> 
> /usr/obj/mips.mips64/pseudosrc/tmp/usr/bin/ld:
> /usr/obj/mips.mips64/pseudosrc/tmp/usr/lib/crtn.o: warning: linking PIC
> files with non-PIC files

This is an old bug in LLVM, where it didn't set the cpic bit in the e_flags 
field of the ELF header.  We fixed it a little while ago, but it hasn't been 
imported into head yet.

> exect.So: In function `exect':
> (.text+0x18): relocation truncated to fit: R_MIPS_PC16 against `__cerror'
> setjmp.So: In function `botch':
> (.text+0x124): relocation truncated to fit: R_MIPS_PC16 against `abort'
> _setjmp.So: In function `botch':
> (.text+0xac): relocation truncated to fit: R_MIPS_PC16 against `abort'
> _sigwait.So: In function `err':
> (.text+0x18): relocation truncated to fit: R_MIPS_PC16 against `__cerror'
> _getlogin.So: In function `err':
> (.text+0x18): relocation truncated to fit: R_MIPS_PC16 against `__cerror'
> aio_mlock.So: In function `err':
> (.text+0x18): relocation truncated to fit: R_MIPS_PC16 against `__cerror'
> pipe2.So: In function `err':
> (.text+0x18): relocation truncated to fit: R_MIPS_PC16 against `__cerror'
> accept4.So: In function `err':
> (.text+0x18): relocation truncated to fit: R_MIPS_PC16 against `__cerror'
> chflagsat.So: In function `err':
> (.text+0x18): relocation truncated to fit: R_MIPS_PC16 against `__cerror'
> connectat.So: In function `err':
> (.text+0x18): relocation truncated to fit: R_MIPS_PC16 against `__cerror'
> bindat.So: In function `err':
> (.text+0x18): additional relocation overflows omitted from the output

Most of these are due to our linker not being able to correctly insert PLT 
entries on MIPS (recent GNU binutils doesn't have this problem, but 
unfortunately also can't target FreeBSD.  I believe Warner is working on 
forward-porting our patches to a new binutils).  We might be able to hack LLVM 
to always emit 24-bit relocations, but that seems a bit of a hack.  I'm 
inclined to wait until we import MCLinker, which now has MIPS32/64 support, and 
should be much easier to fix if it has this kind of issue.

David

___
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: -ffunction-sections, -fdata-sections and -Wl,--gc-sections

[David Chisnall]

On 16 Sep 2013, at 07:52, Dimitry Andric  wrote:

> On Sep 16, 2013, at 03:08, Adrian Chadd  wrote:
>>> The results are interesting. On amd64:
>>> 
>>> - devd suddenly becomes 500 KB in size, instead of a megabyte,
>>> - init's size drops from 900 KB to 600 KB,
>>> - clang becomes a megabyte smaller.
>>> 
>> 
>> .. so, I'd like to know specific information as to why these three are now
>> smaller. So what's going on?
> 
> 
> This is simply unreferenced code and data being eliminated.  It is quite
> normal for libraries (libc, the LLVM libs, etc) to contain functions
> that aren't called by the program you are linking.  However, any .o file
> with multiple functions in it will be linked in as a whole, even if just
> one of the functions is called.
> 
> I really think functions and data should always be separately "packaged"
> in object files, but for some reason this has never been the default for
> GNU tools, and everybody has apparently copied the behavior. :-)

Apple's ld, lld, and MCLinker all prefer to use a finer-grained model (atoms or 
fragments) than segments, and so are intended to do this sort of thing by 
default.  This isn't an issue for dlsym(), as long as the functions that you 
may wish to resolve using dlsym() are explicitly marked (typically by including 
them in the version script) as not being eligible for deletion - only functions 
and data reachable from the public entry points should be retained.  Of course, 
if you're building a shared library and there is unreachable code or data, you 
probably have a bug...

Even in the shared library case, it's useful as it allows the linker to 
rearrange functions and data to perform optimisations to minimise PLT usage and 
improve cache and TLB usage by keeping functions that call each other together 
and data with the functions that use it (profiling can also help here, to 
prioritise hot functions).  

David

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

unbound? -- Conf file?

[Larry Rosenman]

I took the minimalist file from man unbound.conf, and the unbound-checkconf
and unbound itself does NOT like it:

# unbound-checkconf
/etc/unbound/unbound.conf:2: error: syntax error
read /etc/unbound/unbound.conf failed: 1 errors in configuration file
# ^D$
$ pwd
/home/ler
$ cat /etc/unbound/unbound.conf
   # unbound.conf(5) config file for unbound(8).
   server:
directory: "/etc/unbound"
username: unbound
# make sure unbound can access entropy from inside the chroot.
# e.g. on linux the use these commands (on BSD, devfs(8) is used):
#  mount --bind -n /dev/random /etc/unbound/dev/random
# and  mount --bind -n /dev/log /etc/unbound/dev/log
chroot: "/etc/unbound"
# logfile: "/etc/unbound/unbound.log"  #uncomment to use logfile.
pidfile: "/etc/unbound/unbound.pid"
# verbosity: 1  # uncomment and increase to get more logging.
# listen on all interfaces, answer queries from the local subnet.
interface: 0.0.0.0
interface: ::0
access-control: 10.0.0.0/8 allow
access-control: 2001:DB8::/64 allow
$


So, what's the real problem, as the syntax error message is useless.

Thanks!

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 108 Turvey Cove, Hutto, TX 78634-5688
___
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: iSCSI boot ... root?

[Edward Tomasz Napierała]

Wiadomość napisana przez Zaphod Beeblebrox  w dniu 16 wrz 
2013, o godz. 07:35:
> Is it now possible to boot from iSCSI?  I'm not talking about an iSCSI
> controller, but with
> 
> pxe -> dhcp -> tftp (loads loader) -> (something) -> boot (mounts root from
> iSCSI)

Not yet.  The iSCSI initiator requires iscsid(8) in order to work, and you can't
run it before mounting root.

I think the proper way to do this would be by doing something similar to Linux'
initrd; i.e. booting from mdroot loaded by loader(8), run iscsid(8) from there,
setup iSCSI session, then mount the real root and pivot to it.  I'm not sure if 
it's
possible right now.
___
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"

Moused + HAL + rc.conf + Boot

[Nilton Jose Rizzo]

  Hi all,

   I'm here again!

   When I start my box, the moused is run.  My mouse is an USB mouse.
   I put in rc.conf this knob: moused_enable="NO", but is ignored by 
   start up script and moused is run, this is a problem to the HAL, because 
   the HAL try to open /dev/ums0 again and can't do it.  I  need  to change
   to text console and kill the moused process. I have to  logout from  
   account X ( via gdm) and I login again to mouse work.  It's started in 
   two night ago.

see:
FreeBSD valfenda 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #4 r255503: Fri Sep 13
08:18:27 BRT 2013 rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA  amd64

TIA,

Rizzo

___
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: Moused + HAL + rc.conf + Boot

[Hans Petter Selasky]

On 09/16/13 13:06, Nilton Jose Rizzo wrote:


   Hi all,

I'm here again!

When I start my box, the moused is run.  My mouse is an USB mouse.
I put in rc.conf this knob: moused_enable="NO", but is ignored by
start up script and moused is run, this is a problem to the HAL, because
the HAL try to open /dev/ums0 again and can't do it.  I  need  to change
to text console and kill the moused process. I have to  logout from
account X ( via gdm) and I login again to mouse work.  It's started in
two night ago.

see:
FreeBSD valfenda 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #4 r255503: Fri Sep 13
08:18:27 BRT 2013 rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA  amd64

TIA,

Rizzo


No big changes in the USB code recently.

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

Re: ZFS secondarycache on SSD problem on r255173

[Borja Marcos]

On Sep 13, 2013, at 2:18 PM, Steven Hartland wrote:

> This is a recent bit of code by Justin cc'ed, so he's likely the best person 
> to
> investigate this one.

Hmm. There is still a lot of confusion surrounding all this, and it's a time 
bomb waiting to explode.

A friend had serious problems on 9.2 with the gnop trick in order to force a 4 
KB block size. After a reboot,
ZFS would insist on trying to find the .nop device for the ZIL which, of 
course, did no longer exist. In his case, for some reason,
ZFS didn't identify the labelled gpt/name or gptpd/uuid devices as valid, and 
the pool wouldn't attach. Curiously, it did identify the L2ARC 
without problems.

The cure was to disable GPT labels using loader.conf (I don't remember if he 
disabled kern.geom.label.gptid.enable, kern.geom.label.gpt.enable or both) in
order to force it to use the "classical" daXpY nomenclature.

As I said, this sounds like a time bomb in the works. There seems to be some 
confusion in the ZFS between the different naming schemes you
can use for a disk partition right now ( daXpY, gpt label or gptid).





Borja.

___
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 secondarycache on SSD problem on r255173

[Steven Hartland]

Cant say I've ever had a issue with gnop, but I haven't used it for
some time.

I did have a quick look over the weekend at your issue and it looks
to me like warning for the cache is a false positive, as the vdev
for cache doesn't report an ashift in zdb so could well be falling
back to a default value.

I couldn't reproduce the issue for log here, it just seems to work
for me, can you confirm what ashift is reported for your devices
using: zdb 

   Regards
   Steve
- Original Message - 
From: "Borja Marcos" 

To: "Steven Hartland" 
Cc: "Dmitryy Makarov" ; ; "Justin T. 
Gibbs" 
Sent: Monday, September 16, 2013 12:06 PM
Subject: Re: ZFS secondarycache on SSD problem on r255173



On Sep 13, 2013, at 2:18 PM, Steven Hartland wrote:


This is a recent bit of code by Justin cc'ed, so he's likely the best person to
investigate this one.


Hmm. There is still a lot of confusion surrounding all this, and it's a time 
bomb waiting to explode.

A friend had serious problems on 9.2 with the gnop trick in order to force a 4 
KB block size. After a reboot,
ZFS would insist on trying to find the .nop device for the ZIL which, of course, did no longer exist. In his case, for some 
reason,
ZFS didn't identify the labelled gpt/name or gptpd/uuid devices as valid, and the pool wouldn't attach. Curiously, it did identify 
the L2ARC

without problems.

The cure was to disable GPT labels using loader.conf (I don't remember if he disabled kern.geom.label.gptid.enable, 
kern.geom.label.gpt.enable or both) in

order to force it to use the "classical" daXpY nomenclature.

As I said, this sounds like a time bomb in the works. There seems to be some confusion in the ZFS between the different naming 
schemes you

can use for a disk partition right now ( daXpY, gpt label or gptid).





Borja.




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Moused + HAL + rc.conf + Boot

[Sergey V. Dyatko]

On Mon, 16 Sep 2013 08:06:48 -0300
"Nilton Jose Rizzo"  wrote:

> 
>   Hi all,
> 
>I'm here again!
> 
>When I start my box, the moused is run.  My mouse is an USB
> mouse. I put in rc.conf this knob: moused_enable="NO", but is ignored
> by start up script and moused is run, this is a problem to the HAL,
> because the HAL try to open /dev/ums0 again and can't do it.  I
> need  to change to text console and kill the moused process. I have
> to  logout from account X ( via gdm) and I login again to mouse
> work.  It's started in two night ago.
> 
> see:
> FreeBSD valfenda 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #4 r255503: Fri Sep
> 13 08:18:27 BRT 2013
> rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA  amd64
> 
> TIA,
> 

read 'usb mouse and xorg' thread.

p.s. I don't know what exactly helps me.. 
rebuilding hal/dbus/xf86-input-mouse (again!) or  
moused_nondefault_enable=NO +
moused_enable=NO on rc.conf
but now I have working usb mouse :)

> Rizzo



-- 
wbr, tiger
___
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: Problem running VirtualBox

[Jimmy Kelley]

I had the same problem.  Turned out that the offending libstdc++.so.6
had be installed by the compat8x package, which had been installed
by the bootstrap-openjdk package.  Deleted both of those, and now
Virtualbox finds and use the one supplied by the GCC compiler
used to build it.

Jimmy


On Sun, Sep 15, 2013 at 11:42:04AM -0400, Alex wrote:
> Hi:
> 
> When I try to run VirtualBox I get the following error:
> 
> VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
> VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",)
> failed: /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15
> required by /usr/local/lib/virtualbox/VBoxRT.so not found
> 
> Reinstalling does not solve the issue. Does anyone know what could be
> going wrong?
> 
> FreeBSD 10.0-CURRENT #31 r255465
> 
> -- 
> Alex
> 
___
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[2]: ZFS secondarycache on SSD problem on r255173

[Dmitriy Makarov]

There is no problem with ZIL devices, they reports  ashift: 12 

   children[1]: 
    type: 'disk' 
    id: 1 
    guid: 6986664094649753344 
    path: '/dev/gpt/zil1' 
    phys_path: '/dev/gpt/zil1' 
    whole_disk: 1 
    metaslab_array: 67 
    metaslab_shift: 25 
    ashift: 12 
    asize: 4290248704 
    is_log: 1 
    create_txg: 22517 

Problem with cache devices only, but in zdb output tere is nothing at all about 
them. 

--- Исходное сообщение --- 
От кого: "Steven Hartland" < kill...@multiplay.co.uk > 
Дата: 16 сентября 2013, 14:18:31 

Cant say I've ever had a issue with gnop, but I haven't used it for
some time.

I did have a quick look over the weekend at your issue and it looks
to me like warning for the cache is a false positive, as the vdev
for cache doesn't report an ashift in zdb so could well be falling
back to a default value.

I couldn't reproduce the issue for log here, it just seems to work
for me, can you confirm what ashift is reported for your devices
using: zdb 

Regards
Steve
- Original Message - 
From: "Borja Marcos" < 

--- 
Дмитрий Макаров 
___
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[3]: ZFS secondarycache on SSD problem on r255173

[Dmitriy Makarov]

And have to say that ashift of a main pool doesn't matter. 
I've tried to create pool with ashift 9 (default value) and with ashift 12 with 
creating gnops over gpart devices, export pool, destroy gnops, import pool.  
There is the same problem with cache device. 

There is no problem with ZIL devices, they reports  ashift: 12 

   children[1]: 
    type: 'disk' 
    id: 1 
    guid: 6986664094649753344 
    path: '/dev/gpt/zil1' 
    phys_path: '/dev/gpt/zil1' 
    whole_disk: 1 
    metaslab_array: 67 
    metaslab_shift: 25 
    ashift: 12 
    asize: 4290248704 
    is_log: 1 
    create_txg: 22517 

Problem with cache devices only, but in zdb output tere is nothing at all about 
them. 

--- Исходное сообщение --- 
От кого: "Steven Hartland" < kill...@multiplay.co.uk > 
Дата: 16 сентября 2013, 14:18:31 

Cant say I've ever had a issue with gnop, but I haven't used it for
some time.

I did have a quick look over the weekend at your issue and it looks
to me like warning for the cache is a false positive, as the vdev
for cache doesn't report an ashift in zdb so could well be falling
back to a default value.

I couldn't reproduce the issue for log here, it just seems to work
for me, can you confirm what ashift is reported for your devices
using: zdb 

Regards
Steve
- Original Message - 
From: "Borja Marcos" < 

--- 
Дмитрий Макаров 


--- 
Дмитрий Макаров 
___
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: Re[3]: ZFS secondarycache on SSD problem on r255173

[Steven Hartland]

Thats correct the new code knows the what the ashift of the underlying disk 
should
be so if it detects a vdev with a lower ashift you get this warning.

I suspect the issue is that cache devices don't have an ashift, so when the 
check
is done it gets a default value and hence the warning.

I'd have to did some more to see how ashift in cache devices is or isn't 
implemented.

   Regards
   Steve

- Original Message - 
From: "Dmitriy Makarov" 

To: "Steven Hartland" 
Cc: "Borja Marcos" ; ; "Justin T. 
Gibbs" 
Sent: Monday, September 16, 2013 1:29 PM
Subject: Re[3]: ZFS secondarycache on SSD problem on r255173



And have to say that ashift of a main pool doesn't matter.
I've tried to create pool with ashift 9 (default value) and with ashift 12 with creating gnops over gpart devices, export pool, 
destroy gnops, import pool. There is the same problem with cache device.


There is no problem with ZIL devices, they reports ashift: 12

children[1]:
type: 'disk'
id: 1
guid: 6986664094649753344
path: '/dev/gpt/zil1'
phys_path: '/dev/gpt/zil1'
whole_disk: 1
metaslab_array: 67
metaslab_shift: 25
ashift: 12
asize: 4290248704
is_log: 1
create_txg: 22517

Problem with cache devices only, but in zdb output tere is nothing at all about 
them.

--- Исходное сообщение --- 
От кого: "Steven Hartland" < kill...@multiplay.co.uk >

Дата: 16 сентября 2013, 14:18:31

Cant say I've ever had a issue with gnop, but I haven't used it for
some time.

I did have a quick look over the weekend at your issue and it looks
to me like warning for the cache is a false positive, as the vdev
for cache doesn't report an ashift in zdb so could well be falling
back to a default value.

I couldn't reproduce the issue for log here, it just seems to work
for me, can you confirm what ashift is reported for your devices
using: zdb 

   Regards
   Steve
- Original Message - 
From: "Borja Marcos" <


--- 
Дмитрий Макаров



--- 
Дмитрий Макаров






This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

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

Fwd: Virtualbox "Settings" don't show any window (FreeBSD-10 current)

[Mike C.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Perhaps this is best placed in "current" list!

-  Original Message 
Subject: Virtualbox "Settings" don't show any window (FreeBSD-10 current)
Date: Sun, 15 Sep 2013 18:35:02 +
From: Mike C. 
To: freebsd-emulat...@freebsd.org


I've successfully installed virtualbox in my Latptop running Freebsd-10
current...

Everything seems fine except for when I click the "Settings button" it
doesn't show any window and the current windows stays "locked" (I can't
click anything)...

Running VirtualBox from the command-line I don't see any error...

Has anyone tried VirtualBox in FreeBSD-10?

Thanks!


-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.21 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSNxItAAoJEGKyFhaKt9g3utAP/34rlyrLGntXCIDa9LHv3Qly
nmRRcIWgkT//MEDFG2OZMdWo+50DQ12k9L0qAAoUkezhDqfZXTo+U5DOn2mr0MEf
2KOXT5yMkqNBtab54a/nCDxp0bCAiaMSJjsKqXjF6mq6fqoj6aVEFJY6rgzG+Qb1
cAjHlBfbOBcOFtWd4xt0+w1m5VodnJ8dsd5CTVfkazTRRfk32qlLMraRUmQT1x+C
STi2Dt4xDJzbx6MThDcwjOfudPQeQiQ1SnFn65aNRCxSj//pNcZW0DeU3efKq730
1RA2yPjpoqzrPklkkW4wF0Kv/50rGGytS1WYcA01uwBq8noBdVmW9J7GfeqmVuF8
vATRX8eDYNVtkJLZmBqgUgXPT0BocHpoW7qPpTmRHG2OJ8TQTIytGT+nx08rG/T3
EEWssgY/kOKDfYgB9DYcgLyGIPcLt0JuwCWL/sm5wzX1bogNyVhrn5hmJTTiFAng
O4cbyXDPaEHdZhQ9SibqiJ2H1FfUa4keD0d2JW2ZhR5cSFD3oW1s8WprNf/ujBWn
Bc7Z78qy4z0feqrYUabFKMxhmJJtwVfW7Y7Kmuzuvk08CHYjsAikQjumkKNm4Onz
iYFFDfYXbEF73KJslr7tY+kWIY1iRuFc4xnjjaucEIbG/Bp7SvgMhTsNgQ7d//z5
ZVwvJTV0HsyqF+VPz1Ei
=kQa4
-END PGP SIGNATURE-
___
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: Problem running VirtualBox

[Alex]

On Mon, 16 Sep 2013 06:33:00 -0500
Jimmy Kelley  wrote:

> I had the same problem.  Turned out that the offending libstdc++.so.6
> had be installed by the compat8x package, which had been installed
> by the bootstrap-openjdk package.  Deleted both of those, and now
> Virtualbox finds and use the one supplied by the GCC compiler
> used to build it.
> 
> Jimmy
> 
> 
> On Sun, Sep 15, 2013 at 11:42:04AM -0400, Alex wrote:
> > Hi:
> > 
> > When I try to run VirtualBox I get the following error:
> > 
> > VirtualBox: Error -610 in supR3HardenedMainInitRuntime!
> > VirtualBox: dlopen("/usr/local/lib/virtualbox/VBoxRT.so",)
> > failed: /usr/local/lib/compat/libstdc++.so.6: version GLIBCXX_3.4.15
> > required by /usr/local/lib/virtualbox/VBoxRT.so not found
> > 
> > Reinstalling does not solve the issue. Does anyone know what could
> > be going wrong?
> > 
> > FreeBSD 10.0-CURRENT #31 r255465
> > 
> > -- 
> > Alex
> > 

That worked for me, thank you.

-- 
Alex
___
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: Moused + HAL + rc.conf + Boot

[Warren Block]

On Mon, 16 Sep 2013, Nilton Jose Rizzo wrote:



 Hi all,

  I'm here again!

  When I start my box, the moused is run.  My mouse is an USB mouse.
  I put in rc.conf this knob: moused_enable="NO", but is ignored by
  start up script and moused is run, this is a problem to the HAL, because
  the HAL try to open /dev/ums0 again and can't do it.  I  need  to change
  to text console and kill the moused process. I have to  logout from
  account X ( via gdm) and I login again to mouse work.  It's started in
  two night ago.

see:
FreeBSD valfenda 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #4 r255503: Fri Sep 13
08:18:27 BRT 2013 rizzo@valfenda:/usr/obj/usr/src/sys/VALFENDA  amd64


moused is started by devd when a USB mouse is connected.  To disable it, 
add


  moused_nondefault_enable="

to /etc/rc.conf.  But it's generally preferable to disable xorg's use of 
HAL by adding


  Option "AutoAddDevices" "Off"

to the ServerLayout section of xorg.conf.
___
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: unbound? -- Conf file?

[Nathan Whitehorn]

On 09/16/13 03:54, Larry Rosenman wrote:
I took the minimalist file from man unbound.conf, and the 
unbound-checkconf

and unbound itself does NOT like it:


A related note: it seems like the /etc bits for unbound have not been 
hooked up. There is no default config (this post) but also no RC script, 
for example.

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

General Protection Fault in prelist_remove()

[Hans Petter Selasky]

Hi,

I caught a General protection fault in prelist_remove. Any clues what 
this might be?


FreeBSD-10 from one month back approx.


80a95810 :
80a95810:   55  push   %rbp
80a95811:   48 89 e5mov%rsp,%rbp
80a95814:   41 57   push   %r15
80a95816:   41 56   push   %r14
80a95818:   53  push   %rbx
80a95819:   48 83 ec 38 sub$0x38,%rsp
80a9581d:   49 89 ffmov%rdi,%r15
80a95820:   48 8b 04 25 c0 de 3bmov0x813bdec0,%rax
80a95827:   81
80a95828:   48 89 45 e0 mov%rax,-0x20(%rbp)
80a9582c:   49 c7 47 44 00 00 00movq   $0x0,0x44(%r15)
80a95833:   00
80a95834:   41 f6 47 6c 01  testb  $0x1,0x6c(%r15)
80a95839:   74 4d   je 80a95888 

80a9583b:   4c 89 ffmov%r15,%rdi
80a9583e:   e8 fd 00 00 00  callq  80a95940 

80a95843:   41 89 c6mov%eax,%r14d
80a95846:   45 85 f6test   %r14d,%r14d
80a95849:   74 3d   je 80a95888 

80a9584b:   8b 04 25 c4 a6 56 81mov0x8156a6c4,%eax
80a95852:   85 c0   test   %eax,%eax
80a95854:   74 32   je 80a95888 

80a95856:   49 8d 77 20 lea0x20(%r15),%rsi
80a9585a:   48 8d 7d b0 lea-0x50(%rbp),%rdi
80a9585e:   e8 1d fa fd ff  callq  80a75280 

80a95863:   41 0f b6 4f 78  movzbl 0x78(%r15),%ecx
80a95868:   4d 8b 07mov(%r15),%r8
80a9586b:   49 83 c0 28 add$0x28,%r8
80a9586f:   bf 03 00 00 00  mov$0x3,%edi
80a95874:   48 c7 c6 c6 17 fa 80mov$0x80fa17c6,%rsi
80a9587b:   48 89 c2mov%rax,%rdx
80a9587e:   45 89 f1mov%r14d,%r9d
80a95881:   30 c0   xor%al,%al
80a95883:   e8 08 f0 e5 ff  callq  808f4890 
80a95888:   41 83 7f 7c 00  cmpl   $0x0,0x7c(%r15)
80a9588d:   7f 6c   jg 80a958fb 

80a9588f:   49 8b 47 08 mov0x8(%r15),%rax
80a95893:   48 85 c0test   %rax,%rax
80a95896:   74 0a   je 80a958a2 

80a95898:   49 8d 4f 08 lea0x8(%r15),%rcx
80a9589c:   48 39 48 10 cmp%rcx,0x10(%rax)

 crash here

80a958a0:   75 72   jne80a95914 

80a958a2:   49 8b 4f 10 mov0x10(%r15),%rcx


Non-reproducable.

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

Re: iSCSI boot ... root?

[Kristjan Eentsalu]

On 16.09.2013 13:35, Edward Tomasz Napierała wrote:> Wiadomość napisana
przez Zaphod Beeblebrox  w dniu 16 wrz 2013, o godz.
07:35:
>> Is it now possible to boot from iSCSI?  I'm not talking about an iSCSI
>> controller, but with
>>
>> pxe -> dhcp -> tftp (loads loader) -> (something) -> boot (mounts root
from
>> iSCSI)
>
> Not yet.  The iSCSI initiator requires iscsid(8) in order to work, and
you can't
> run it before mounting root.
>
> I think the proper way to do this would be by doing something similar to
Linux'
> initrd; i.e. booting from mdroot loaded by loader(8), run iscsid(8) from
there,
> setup iSCSI session, then mount the real root and pivot to it.  I'm not
sure if it's
> possible right now.
> ___
> 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"
>

Don't know if it works with CURRENT but You can use iPXE(formerly gPXE)
chainloading and isboot module.

http://ipxe.org/howto/chainloading
http://ipxe.org/howto/dhcpd
http://lists.freebsd.org/pipermail/freebsd-scsi/2012-August/005570.html


Kristjan
___
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: General Protection Fault in prelist_remove()

[Mark Johnston]

On Mon, Sep 16, 2013 at 05:27:30PM +0200, Hans Petter Selasky wrote:
> Hi,
> 
> I caught a General protection fault in prelist_remove. Any clues what 
> this might be?

Any chance you were creating or destroying interfaces around the time
this crash happened?

There is no locking in the code which manipulates the prefix list (or
any of the global NDP data structures), so it's possible to get crashes
if, for instance, the prefix expiry callout races with in6_ifdetach() to
delete a prefix. It's not clear what caused your crash (not without a
crash dump at least), but I imagine it has something to do with this.

I've partially fixed this at work by adding a rw lock to protect access
to the the prefix, default router, and DAD lists. The patch is here:
http://people.freebsd.org/~markj/patches/ndp-locking.diff

If anyone can review or test this patch, please let me know.

Thanks,
-Mar

> 
> FreeBSD-10 from one month back approx.
> 
> > 80a95810 :
> > 80a95810:   55  push   %rbp
> > 80a95811:   48 89 e5mov%rsp,%rbp
> > 80a95814:   41 57   push   %r15
> > 80a95816:   41 56   push   %r14
> > 80a95818:   53  push   %rbx
> > 80a95819:   48 83 ec 38 sub$0x38,%rsp
> > 80a9581d:   49 89 ffmov%rdi,%r15
> > 80a95820:   48 8b 04 25 c0 de 3bmov
> > 0x813bdec0,%rax
> > 80a95827:   81
> > 80a95828:   48 89 45 e0 mov%rax,-0x20(%rbp)
> > 80a9582c:   49 c7 47 44 00 00 00movq   $0x0,0x44(%r15)
> > 80a95833:   00
> > 80a95834:   41 f6 47 6c 01  testb  $0x1,0x6c(%r15)
> > 80a95839:   74 4d   je 80a95888 
> > 
> > 80a9583b:   4c 89 ffmov%r15,%rdi
> > 80a9583e:   e8 fd 00 00 00  callq  80a95940 
> > 
> > 80a95843:   41 89 c6mov%eax,%r14d
> > 80a95846:   45 85 f6test   %r14d,%r14d
> > 80a95849:   74 3d   je 80a95888 
> > 
> > 80a9584b:   8b 04 25 c4 a6 56 81mov
> > 0x8156a6c4,%eax
> > 80a95852:   85 c0   test   %eax,%eax
> > 80a95854:   74 32   je 80a95888 
> > 
> > 80a95856:   49 8d 77 20 lea0x20(%r15),%rsi
> > 80a9585a:   48 8d 7d b0 lea-0x50(%rbp),%rdi
> > 80a9585e:   e8 1d fa fd ff  callq  80a75280 
> > 
> > 80a95863:   41 0f b6 4f 78  movzbl 0x78(%r15),%ecx
> > 80a95868:   4d 8b 07mov(%r15),%r8
> > 80a9586b:   49 83 c0 28 add$0x28,%r8
> > 80a9586f:   bf 03 00 00 00  mov$0x3,%edi
> > 80a95874:   48 c7 c6 c6 17 fa 80mov
> > $0x80fa17c6,%rsi
> > 80a9587b:   48 89 c2mov%rax,%rdx
> > 80a9587e:   45 89 f1mov%r14d,%r9d
> > 80a95881:   30 c0   xor%al,%al
> > 80a95883:   e8 08 f0 e5 ff  callq  808f4890 
> > 
> > 80a95888:   41 83 7f 7c 00  cmpl   $0x0,0x7c(%r15)
> > 80a9588d:   7f 6c   jg 80a958fb 
> > 
> > 80a9588f:   49 8b 47 08 mov0x8(%r15),%rax
> > 80a95893:   48 85 c0test   %rax,%rax
> > 80a95896:   74 0a   je 80a958a2 
> > 
> > 80a95898:   49 8d 4f 08 lea0x8(%r15),%rcx
> > 80a9589c:   48 39 48 10 cmp%rcx,0x10(%rax)
>  crash here
> > 80a958a0:   75 72   jne80a95914 
> > 
> > 80a958a2:   49 8b 4f 10 mov0x10(%r15),%rcx
> 
> Non-reproducable.
> 
> --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"

sysctl: unknown oid 'kern.random.sys.harvest.interrupt

[Joel Dahl]

Hi,

I noticed the following during boot on a machine running HEAD from today:

Entropy harvesting:sysctl: unknown oid 'kern.random.sys.harvest.interrupt': No 
such file or directory
 interruptssysctl: unknown oid 'kern.random.sys.harvest.ethernet': No such file 
or directory
 ethernetsysctl: unknown oid 'kern.random.sys.harvest.point_to_point': No such 
file or directory
 point_to_point kickstart.

Known problem?

-- 
Joel
___
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 10.0 ALPHA1

[ajtiM]

Hi!

I installed FreeBSD 10.0 ALPHA1 on my iMac 11,1 with ATI Radeon HD 4850, GPU 
because I fought that Xor will works now. But I see that I need to do more. 
I have not experience with FreeBSD current and I didn't use svn except for Area 
51 (KDE). I fought that is svn (subversion) default on the FreeBSD 10.0 ALPHA1 
but when I run svn checkout https://svn0….. it looks like that is not. How 
should I install subversion, please? If I use portsnap it will install ports 
from 9 release.
 Thank you very much.

Mitja

http://www.redbubble.com/people/lumiwa

___
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: General Protection Fault in prelist_remove()

[Hans Petter Selasky]

Hi Mark,

-Original message-
> From:Mark Johnston mailto:ma...@freebsd.org> >
> Sent: Monday 16th September 2013 19:09
> To: Hans Petter Selasky   >
> Cc: freebsd-current@freebsd.org  
> Subject: Re: General Protection Fault in prelist_remove()
> 
> On Mon, Sep 16, 2013 at 05:27:30PM +0200, Hans Petter Selasky wrote:
> > Hi,
> > 
> > I caught a General protection fault in prelist_remove. Any clues what 
> > this might be?
> 
> Any chance you were creating or destroying interfaces around the time
> this crash happened?

Yes, I have some tunneling software running, which create and destroy tunX 
nodes regularly.

> 
> There is no locking in the code which manipulates the prefix list (or
> any of the global NDP data structures), so it's possible to get crashes
> if, for instance, the prefix expiry callout races with in6_ifdetach() to
> delete a prefix. It's not clear what caused your crash (not without a
> crash dump at least), but I imagine it has something to do with this.
> 
> I've partially fixed this at work by adding a rw lock to protect access
> to the the prefix, default router, and DAD lists. The patch is here:
> http://people.freebsd.org/˜markj/patches/ndp-locking.diff 
>  
> 
> If anyone can review or test this patch, please let me know.
> 

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

Installing ports without info files

[Mattia Rossi]

Hi all,

I've build a world with the following constraints: -DWITHOUT_INFO 
-DWITHOUT_MAN -DWITHOUT_SHAREDOCS -DWITHOUT_EXAMPLES -DWITHOUT_HTML


as I don't need that stuff. Turns out, this prevents tools like 
install-info being built.
Now trying to build devel/gettext I can't get it installed, as it always 
wants to install info files using install-info, which of course fails.


How do I tell the system not to build info files (or manpages or all of 
the stuff above I don't want in the first place) when building ports?


I've tried with "make -DWITHOUT_INFO install" as well as with putting 
WITHOUT_INFO=yes in make.conf.


Gettext will still fail to install.
Is this a gettext problem? Or a generic ports problem?

I'm running current on arm (thanks again to freebsd-arm people for 
fixing it):

FreeBSD dreamplug 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #15 r255499M:

It's also not possible to "make index" for INDEX-10 if you use a 
stripped-down ports tree (none of the language ports), as there are some 
dependencies in the tree to french (cad-astk) and russian (stardict-*) 
which obviously can't be resolved.


Help is appreciated!

Cheers,

Mat
___
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: Virtualbox "Settings" don't show any window (FreeBSD-10 current)

[Eric Camachat]

I run it on my 10-ALPHA1 without problem.
There were many fix for clang/libc++ in ports recently.
Try to update ports and rebuild all dependencies.

Eric


On Mon, Sep 16, 2013 at 7:14 AM, Mike C.  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Perhaps this is best placed in "current" list!
>
> -  Original Message 
> Subject: Virtualbox "Settings" don't show any window (FreeBSD-10 current)
> Date: Sun, 15 Sep 2013 18:35:02 +
> From: Mike C. 
> To: freebsd-emulat...@freebsd.org
>
>
> I've successfully installed virtualbox in my Latptop running Freebsd-10
> current...
>
> Everything seems fine except for when I click the "Settings button" it
> doesn't show any window and the current windows stays "locked" (I can't
> click anything)...
>
> Running VirtualBox from the command-line I don't see any error...
>
> Has anyone tried VirtualBox in FreeBSD-10?
>
> Thanks!
>
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.21 (FreeBSD)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJSNxItAAoJEGKyFhaKt9g3utAP/34rlyrLGntXCIDa9LHv3Qly
> nmRRcIWgkT//MEDFG2OZMdWo+50DQ12k9L0qAAoUkezhDqfZXTo+U5DOn2mr0MEf
> 2KOXT5yMkqNBtab54a/nCDxp0bCAiaMSJjsKqXjF6mq6fqoj6aVEFJY6rgzG+Qb1
> cAjHlBfbOBcOFtWd4xt0+w1m5VodnJ8dsd5CTVfkazTRRfk32qlLMraRUmQT1x+C
> STi2Dt4xDJzbx6MThDcwjOfudPQeQiQ1SnFn65aNRCxSj//pNcZW0DeU3efKq730
> 1RA2yPjpoqzrPklkkW4wF0Kv/50rGGytS1WYcA01uwBq8noBdVmW9J7GfeqmVuF8
> vATRX8eDYNVtkJLZmBqgUgXPT0BocHpoW7qPpTmRHG2OJ8TQTIytGT+nx08rG/T3
> EEWssgY/kOKDfYgB9DYcgLyGIPcLt0JuwCWL/sm5wzX1bogNyVhrn5hmJTTiFAng
> O4cbyXDPaEHdZhQ9SibqiJ2H1FfUa4keD0d2JW2ZhR5cSFD3oW1s8WprNf/ujBWn
> Bc7Z78qy4z0feqrYUabFKMxhmJJtwVfW7Y7Kmuzuvk08CHYjsAikQjumkKNm4Onz
> iYFFDfYXbEF73KJslr7tY+kWIY1iRuFc4xnjjaucEIbG/Bp7SvgMhTsNgQ7d//z5
> ZVwvJTV0HsyqF+VPz1Ei
> =kQa4
> -END PGP SIGNATURE-
> ___
> 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: FreeBSD 10.0 ALPHA1

[Herbert J. Skuhra]

On Mon, 16 Sep 2013 13:28:06 -0400
ajtiM wrote:

> Hi!
> 
> I installed FreeBSD 10.0 ALPHA1 on my iMac 11,1 with ATI Radeon HD
> 4850, GPU because I fought that Xor will works now. But I see that I
> need to do more.
> I have not experience with FreeBSD current and I didn't use svn
>  except for Area 51 (KDE). I fought that is svn (subversion) default
>  on the FreeBSD 10.0 ALPHA1 but when I run svn checkout
>  https://svn0….. it looks like that is not. How should I install
>  subversion, please? If I use portsnap it will install ports from 9
>  release.  Thank you very much.

Try 'svnlite checkout' instead.

-- 
Herbert
___
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: unbound? -- Conf file?

[Dag-Erling Smørgrav]

Nathan Whitehorn  writes:
> A related note: it seems like the /etc bits for unbound have not been
> hooked up. There is no default config (this post) but also no RC
> script, for example.

...yet.

DES
-- 
Dag-Erling Smørgrav - d...@des.no
___
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 ports without info files

[Ian Lepore]

On Mon, 2013-09-16 at 21:50 +0200, Mattia Rossi wrote:
> Hi all,
> 
> I've build a world with the following constraints: -DWITHOUT_INFO 
> -DWITHOUT_MAN -DWITHOUT_SHAREDOCS -DWITHOUT_EXAMPLES -DWITHOUT_HTML
> 
> as I don't need that stuff. Turns out, this prevents tools like 
> install-info being built.
> Now trying to build devel/gettext I can't get it installed, as it always 
> wants to install info files using install-info, which of course fails.
> 
> How do I tell the system not to build info files (or manpages or all of 
> the stuff above I don't want in the first place) when building ports?
> 
> I've tried with "make -DWITHOUT_INFO install" as well as with putting 
> WITHOUT_INFO=yes in make.conf.
> 
> Gettext will still fail to install.
> Is this a gettext problem? Or a generic ports problem?
> 
> I'm running current on arm (thanks again to freebsd-arm people for 
> fixing it):
> FreeBSD dreamplug 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #15 r255499M:
> 
> It's also not possible to "make index" for INDEX-10 if you use a 
> stripped-down ports tree (none of the language ports), as there are some 
> dependencies in the tree to french (cad-astk) and russian (stardict-*) 
> which obviously can't be resolved.
> 
> Help is appreciated!
> 
> Cheers,
> 

I fought with the info problem for a few hours at $work and never got it
resolved, I had to remove the WITHOUT_INFO so that the tools would be
there to let ports build, and then rely on an mtree pruning script to
keep the actual info files out of the filesystem image.

-- Ian


___
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 ports without info files

[John Hein]

Ian Lepore wrote at 14:53 -0600 on Sep 16, 2013:
 > On Mon, 2013-09-16 at 21:50 +0200, Mattia Rossi wrote:
 > > Hi all,
 > >
 > > I've build a world with the following constraints: -DWITHOUT_INFO
 > > -DWITHOUT_MAN -DWITHOUT_SHAREDOCS -DWITHOUT_EXAMPLES -DWITHOUT_HTML
 > >
 > > as I don't need that stuff. Turns out, this prevents tools like
 > > install-info being built.
 > > Now trying to build devel/gettext I can't get it installed, as it always
 > > wants to install info files using install-info, which of course fails.
 > >
 > > How do I tell the system not to build info files (or manpages or all of
 > > the stuff above I don't want in the first place) when building ports?
 > >
 > > I've tried with "make -DWITHOUT_INFO install" as well as with putting
 > > WITHOUT_INFO=yes in make.conf.
 > >
 > > Gettext will still fail to install.
 > > Is this a gettext problem? Or a generic ports problem?
 > >
 > > I'm running current on arm (thanks again to freebsd-arm people for
 > > fixing it):
 > > FreeBSD dreamplug 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #15 r255499M:
 > >
 > > It's also not possible to "make index" for INDEX-10 if you use a
 > > stripped-down ports tree (none of the language ports), as there are some
 > > dependencies in the tree to french (cad-astk) and russian (stardict-*)
 > > which obviously can't be resolved.
 > >
 > > Help is appreciated!
 > >
 > > Cheers,
 > >
 >
 > I fought with the info problem for a few hours at $work and never got it
 > resolved, I had to remove the WITHOUT_INFO so that the tools would be
 > there to let ports build, and then rely on an mtree pruning script to
 > keep the actual info files out of the filesystem image.
 >
 > -- Ian

I have a patch for this that was going to go through a ports
run, but stalled in the machine.

I'll dig it out.

___
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: FreeBSD 10.0 ALPHA1

[Alexander Panyushkin]

16.09.2013 20:28, ajtiM пишет:

Hi!

I installed FreeBSD 10.0 ALPHA1 on my iMac 11,1 with ATI Radeon HD 4850, GPU 
because I fought that Xor will works now. But I see that I need to do more.
I have not experience with FreeBSD current and I didn't use svn except for Area 
51 (KDE). I fought that is svn (subversion) default on the FreeBSD 10.0 ALPHA1 
but when I run svn checkout https://svn0….. it looks like that is not. How 
should I install subversion, please? If I use portsnap it will install ports 
from 9 release.
  Thank you very much.

Mitja

http://www.redbubble.com/people/lumiwa

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


After rebuild world from svn,  Xorg does not start and the box goes to 
reboot.


 svn info
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/head
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 255608
Node Kind: directory
Schedule: normal
Last Changed Author: kib
Last Changed Rev: 255608
Last Changed Date: 2013-09-16 09:25:54 +0300

dmesg:
Sep 16 20:26:07 scorpion dbus[1713]: [system] Activating service 
name='org.freedesktop.ConsoleKit' (using servicehelper)
Sep 16 20:26:08 scorpion dbus[1713]: [system] Activating service 
name='org.freedesktop.PolicyKit1' (using servicehelper)
Sep 16 20:26:08 scorpion dbus[1713]: [system] Successfully activated 
service 'org.freedesktop.PolicyKit1'
Sep 16 20:26:08 scorpion dbus[1713]: [system] Successfully activated 
service 'org.freedesktop.ConsoleKit'
Sep 16 20:26:08 scorpion console-kit-daemon[1734]: WARNING: kvm_getenvv 
failed:
Sep 16 20:26:09 scorpion kernel: keyrate scrnmap font8x16 blanktime 
allscreens.




___
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 secondarycache on SSD problem on r255173

[Justin T. Gibbs]

Sorry for being slow to chime in on this thread.  I live in Boulder, CO and 
we've had a bit of rain. :-)

As Steven pointed out, the warning is benign, but does show that the code I 
committed to -current is not optimizing the allocation size for L2ARC devices.  
The fix for this is to find the best place during pool creation/load/import to 
call vdev_ashift_optimize() on L2ARC devices.  I will look into this tomorrow, 
but feel free to suggest a good spot if you look at it before I can.

--
Justin

On Sep 16, 2013, at 6:43 AM, Steven Hartland  wrote:

> Thats correct the new code knows the what the ashift of the underlying disk 
> should
> be so if it detects a vdev with a lower ashift you get this warning.
> 
> I suspect the issue is that cache devices don't have an ashift, so when the 
> check
> is done it gets a default value and hence the warning.
> 
> I'd have to did some more to see how ashift in cache devices is or isn't 
> implemented.
> 
>   Regards
>   Steve
> 
> - Original Message - From: "Dmitriy Makarov" 
> To: "Steven Hartland" 
> Cc: "Borja Marcos" ; ; 
> "Justin T. Gibbs" 
> Sent: Monday, September 16, 2013 1:29 PM
> Subject: Re[3]: ZFS secondarycache on SSD problem on r255173
> 
> 
>> And have to say that ashift of a main pool doesn't matter.
>> I've tried to create pool with ashift 9 (default value) and with ashift 12 
>> with creating gnops over gpart devices, export pool, destroy gnops, import 
>> pool. There is the same problem with cache device.
>> 
>> There is no problem with ZIL devices, they reports ashift: 12
>> 
>> children[1]:
>> type: 'disk'
>> id: 1
>> guid: 6986664094649753344
>> path: '/dev/gpt/zil1'
>> phys_path: '/dev/gpt/zil1'
>> whole_disk: 1
>> metaslab_array: 67
>> metaslab_shift: 25
>> ashift: 12
>> asize: 4290248704
>> is_log: 1
>> create_txg: 22517
>> 
>> Problem with cache devices only, but in zdb output tere is nothing at all 
>> about them.
>> 
>> --- Исходное сообщение --- От кого: "Steven Hartland" < 
>> kill...@multiplay.co.uk >
>> Дата: 16 сентября 2013, 14:18:31
>> 
>> Cant say I've ever had a issue with gnop, but I haven't used it for
>> some time.
>> 
>> I did have a quick look over the weekend at your issue and it looks
>> to me like warning for the cache is a false positive, as the vdev
>> for cache doesn't report an ashift in zdb so could well be falling
>> back to a default value.
>> 
>> I couldn't reproduce the issue for log here, it just seems to work
>> for me, can you confirm what ashift is reported for your devices
>> using: zdb 
>> 
>>   Regards
>>   Steve
>> - Original Message - From: "Borja Marcos" <
>> 
>> --- Дмитрий Макаров
>> 
>> 
>> --- Дмитрий Макаров
> 
> 
> 
> This e.mail is private and confidential between Multiplay (UK) Ltd. and the 
> person or entity to whom it is addressed. In the event of misdirection, the 
> recipient is prohibited from using, copying, printing or otherwise 
> disseminating it or any information contained in it. 
> In the event of misdirection, illegible or incomplete transmission please 
> telephone +44 845 868 1337
> or return the E.mail to postmas...@multiplay.co.uk.
> 
> ___
> 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"

portmaster

[ajtiM]

Again me…
I was (am) long postmaster user. Is it possible to use on FreeBSD 10 too, 
please? Or is better to use something different?

Thank in advance.

Mitja

http://www.redbubble.com/people/lumiwa

___
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: problems with libiconv into kernel

[John-Mark Gurney]

Nilton Jose Rizzo wrote this message on Sun, Sep 15, 2013 at 13:14 -0300:
> Last night, I has tried to put in my kernel config the libiconv with this
> knobs from LINT:
> 
> options CD9660_ICONV
> options MSDOSFS_ICONV
> options UDF_ICONV
> options LIBICONV
> 
> but this results int this error:
> 
> 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../../..
> -I../../../contrib/altq -I../../../contrib/libfdt -D_KERNEL
> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h  -fno-omit-frame-pointer
> -mno-omit-leaf-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  ../../../libkern/iconv.c
> ../../../libkern/iconv.c:39:10: fatal error: 'iconv_converter_if.h' file not
>   found
> #include "iconv_converter_if.h"
>  ^
> 1 error generated.
> *** Error code 1
> 
> Stop.
> make: stopped in /usr/src/sys/amd64/compile/VALFENDA
> 
> What am I doing wrong? My svn version is 255531

How are you building your kernel?  are you using config and make or
are you using buildkernel?  If you are using config and make, did you
run: make cleandepend && make depend first before make like said?

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 "All that I will do, has been done, All that I have, has not."
___
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: FreeBSD 10.0 ALPHA1

[ajtiM]

Do you have with_org_new, with_kms and with_gallium in make.conf? Do you 
applied http://people.freebsd.org/~zeising/xorg-mesaupdate.diff
I didn't try yet to build Xorg. Maybe tomorrow.


On Sep 16, 2013, at 5:16 PM, Alexander Panyushkin  wrote:

> 16.09.2013 20:28, ajtiM пишет:
>> Hi!
>> 
>> I installed FreeBSD 10.0 ALPHA1 on my iMac 11,1 with ATI Radeon HD 4850, GPU 
>> because I fought that Xor will works now. But I see that I need to do more.
>> I have not experience with FreeBSD current and I didn't use svn except for 
>> Area 51 (KDE). I fought that is svn (subversion) default on the FreeBSD 10.0 
>> ALPHA1 but when I run svn checkout https://svn0….. it looks like that is 
>> not. How should I install subversion, please? If I use portsnap it will 
>> install ports from 9 release.
>>  Thank you very much.
>> 
>> Mitja
>> 
>> http://www.redbubble.com/people/lumiwa
>> 
>> ___
>> 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"
> 
> After rebuild world from svn,  Xorg does not start and the box goes to reboot.
> 
> svn info
> Path: .
> Working Copy Root Path: /usr/src
> URL: svn://svn.freebsd.org/base/head
> Repository Root: svn://svn.freebsd.org/base
> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
> Revision: 255608
> Node Kind: directory
> Schedule: normal
> Last Changed Author: kib
> Last Changed Rev: 255608
> Last Changed Date: 2013-09-16 09:25:54 +0300
> 
> dmesg:
> Sep 16 20:26:07 scorpion dbus[1713]: [system] Activating service 
> name='org.freedesktop.ConsoleKit' (using servicehelper)
> Sep 16 20:26:08 scorpion dbus[1713]: [system] Activating service 
> name='org.freedesktop.PolicyKit1' (using servicehelper)
> Sep 16 20:26:08 scorpion dbus[1713]: [system] Successfully activated service 
> 'org.freedesktop.PolicyKit1'
> Sep 16 20:26:08 scorpion dbus[1713]: [system] Successfully activated service 
> 'org.freedesktop.ConsoleKit'
> Sep 16 20:26:08 scorpion console-kit-daemon[1734]: WARNING: kvm_getenvv 
> failed:
> Sep 16 20:26:09 scorpion kernel: keyrate scrnmap font8x16 blanktime 
> allscreens.
> 
> 
> 
> ___
> 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"

Mitja

http://www.redbubble.com/people/lumiwa

___
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: FreeBSD 10.0 ALPHA1

[ajtiM]

Thank you. I used portsnap and installed subversion. Than rm /usr/ports and 
/vard/db/portsnap and use svn and it works :).

On Sep 16, 2013, at 5:12 PM, "Herbert J. Skuhra"  wrote:

> On Mon, 16 Sep 2013 13:28:06 -0400
> ajtiM wrote:
> 
>> Hi!
>> 
>> I installed FreeBSD 10.0 ALPHA1 on my iMac 11,1 with ATI Radeon HD
>> 4850, GPU because I fought that Xor will works now. But I see that I
>> need to do more.
>> I have not experience with FreeBSD current and I didn't use svn
>> except for Area 51 (KDE). I fought that is svn (subversion) default
>> on the FreeBSD 10.0 ALPHA1 but when I run svn checkout
>> https://svn0….. it looks like that is not. How should I install
>> subversion, please? If I use portsnap it will install ports from 9
>> release.  Thank you very much.
> 
> Try 'svnlite checkout' instead.
> 
> -- 
> Herbert
> ___
> 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"

Mitja

http://www.redbubble.com/people/lumiwa

___
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: portmaster

[Matthias Andree]

Am 17.09.2013 01:04, schrieb ajtiM:
> Again me…
> I was (am) long postmaster user. Is it possible to use on FreeBSD 10 too, 
> please? Or is better to use something different?

Portmaster works for me on FreeBSD 10-CURRENT. Be sure to use an
up-to-date ports tree and install an up-to-date portmaster.

___
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: portmaster

[ajtiM]

Thank ou.

On Sep 16, 2013, at 7:15 PM, Matthias Andree  wrote:

> Am 17.09.2013 01:04, schrieb ajtiM:
>> Again me…
>> I was (am) long postmaster user. Is it possible to use on FreeBSD 10 too, 
>> please? Or is better to use something different?
> 
> Portmaster works for me on FreeBSD 10-CURRENT. Be sure to use an
> up-to-date ports tree and install an up-to-date portmaster.
> 

Mitja

http://www.redbubble.com/people/lumiwa

___
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: [RFC][CFT] GEOM direct dispatch and fine-grained CAM locking

[Marius Strobl]

On Tue, Sep 03, 2013 at 11:48:38PM +0200, Olivier Cochard-Labbé wrote:
> On Tue, Sep 3, 2013 at 8:10 PM, Outback Dingo  wrote:
> > Can anyone confirm how well tested/stable this patch set might be?? if
> > theres positive input i have a zoo of dev machines i could load it on, to
> > help further it.
> > Just checking to see how widely its been tested,
> 
> I've installed this patch on 3 differents machines there status after
> about 12hours:
> - SUN FIRE X4170 M2 (amd64: r255178) with 6 SAS harddrives in one big
> zraid (LSI MegaSAS Gen2 controller): Used for generating package with
> poudriere? no probleme since;
> - HAL/Fujitsu SPARC64-V (sparc64: r255178) with two SCSI-3 disks in
> gmirror: Used for generating package with poudriere too? no probleme
> since;

For testing GEOM direct dispatch on sparc64, please additionally use
the following patch:
http://people.freebsd.org/~marius/sparc64_GET_STACK_USAGE.diff

Marius

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

Something's really rotten with the build on CURRENT

[Garrett Cooper]

When I was trying to do a source upgrade from 2 month old sources on 
CURRENT, I've run into 3 different build failures that I've been filing PRs 
for, and that's probably just the start of it. bmake's a part of the problem, 
but it isn't the only problem as I've been running into consistent build 
failures when I don't specify TARGET/TARGET_ARCH explicitly on the command 
line. And while my kernel is slightly tainted and my userland is tainted with 
some libc fixes, POSIX conformance fixes, test code and all that jazz, I run 
into multiple problems with bmake/fmake, clang/gcc, and my git checkout and an 
untainted svn checkout on 2 systems that I have running FreeBSD CURRENT on. My 
stable/9 build is still going strong.
I've run into issues with cam (weird linker unresolved symbol issue 
with gcc; doesn't appear with clang), iconv (had to turn it off because it 
wasn't working with the default due to a missing symbol in the file), and 
unbound (it's looking for the static library in the wrong directory in 
${MAKEOBJDIRPREFIX}). I just checked the mailing list archives and it appears 
that there have been a slew of build failures related to features being turned 
on and off, and other things before the 10.0-ALPHA2 code slush. But seriously… 
this is ridiculous and I haven't run into build failures like this for years. 
Can people PLEASE build/test their changes on and off on multiple VMs?
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"

Re: Something's really rotten with the build on CURRENT

[Glen Barber]

On Mon, Sep 16, 2013 at 04:53:14PM -0700, Garrett Cooper wrote:
> Can people PLEASE build/test their changes on
> and off on multiple VMs?

Welcome to the world two weeks after the code freeze.

We would have had cookies, but ... well, they don't build right now.

Glen



pgpLaSRXKP4Y6.pgp
Description: PGP signature

Re: Something's really rotten with the build on CURRENT

[Garrett Cooper]

On Sep 16, 2013, at 6:12 PM, Glen Barber wrote:

> On Mon, Sep 16, 2013 at 04:53:14PM -0700, Garrett Cooper wrote:
>> Can people PLEASE build/test their changes on
>> and off on multiple VMs?
> 
> Welcome to the world two weeks after the code freeze.
> 
> We would have had cookies, but ... well, they don't build right now.

Well at least the stuff we're frozen on is broken, right :( *sighs*?
___
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: Something's really rotten with the build on CURRENT

[Adrian Chadd]

On 16 September 2013 21:01, Garrett Cooper  wrote:

> On Sep 16, 2013, at 6:12 PM, Glen Barber wrote:
>
> > On Mon, Sep 16, 2013 at 04:53:14PM -0700, Garrett Cooper wrote:
> >> Can people PLEASE build/test their changes on
> >> and off on multiple VMs?
> >
> > Welcome to the world two weeks after the code freeze.
> >
> > We would have had cookies, but ... well, they don't build right now.
>
> Well at least the stuff we're frozen on is broken, right :( *sighs*?
>
>

Nope.

I applaud re@ for trying to shoehorn this stuff together.


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