Nikolai Wendorf | 23 Nov 13:49 2014

net boot sparc64

just wondering if this page is still a good description for loading up 9.3

CD-ROM is defunct on my E-450

freebsd-questions <at> mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at>"



I recently browsed through your business website and wanted to highlight  
some key points for consideration.

I am sure it will complement your-SEO work to help your website attract  
only quality visitors and make it scale high on the search .engine results  
page (SERP) gradually.

Would you be interested in receiving the details?

Best regards,
Holley | Director MKT

Brandroot MEDIA PTY. LTD. Headquarters: Office 7003 X2 Tower, Melbourne  
Vic. 3000
Other Branches: Sydney | Perth | Brisbane | Adelaide | Hobart
Global Offices: China & Hong Kong | USA | | UAE | Singapore

Disclaimer: This e-mail is private and confidential. If you are not the  
intended recipient, please advise us by return e-mail immediately, and  
delete the e-mail and any attachments without using or disclosing the  
contents in any way. The views expressed in this e-mail are those of the  
author, and do not represent those of this company unless this is clearly  
indicated. You should scan this e-mail and any attachments for viruses.  
This company accepts no liability for any direct or indirect damage or loss  
resulting from the use of any attachments to this e-mail. All quotes  
received from BrandRoot by email are informal and not binding until a  
formal quote is agreed upon by both the parties.

(Continue reading)

lnrt | 23 Nov 00:44 2014

Full disk encryption on FreeBSD 10.1-RELEASE?

While installing a FreeBSD 10.1-RELEASE system I want to use UFS and 
encrypt the entire disk. I select "Open a shell and partition by hand" 
and follow these steps:

# gpart destroy -F ada0

# gpart create -s gpt ada0

# gpart add -t freebsd-boot -s 512k -a 4k ada0
# gpart add -t freebsd-ufs -l boot -s 1g -a 1m ada0
# gpart add -t freebsd-ufs -l encrypted -a 1m ada0

# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0

# geli init -b -l 256 -s 4096 ada0p3
# geli attach ada0p3

# newfs -U /dev/ada0p2
# newfs -U /dev/ada0p3.eli

# mount /dev/ada0p3.eli /mnt
# mkdir /mnt/unencrypted
# mount /dev/ada0p2 /mnt/unencrypted
# mkdir /mnt/unencrypted/boot
# ln -s unencrypted/boot /mnt/boot

# vi /tmp/bsdinstall_etc/fstab

/dev/ada0p2     /unencrypted   ufs     rw,noatime   1   1
(Continue reading)

Christopher J. Ruwe | 23 Nov 00:32 2014

value of maintaining emacs-mode packages in ports

I am well aware that very probably I might be starting a rant thread,
however, I am genuinely interested in opinions from the community.

Since version 24, Emacs, the very good operating system missing only a
decent editor, has developed a package manager for Emacs
extensions. Some good repos exist, packages are usually installed to
~/.emacs.d and I have come to really enjoy that way of installing

In that light and as the ports maintainer of math/ess, the Emacs
speaks statistics R-mode of emacs, I am asking myself specifically
whether I add any real benefit in maintaining math/ess. More
generally, I am interested in community answers as to whether it is
really useful to maintain Emacs-extension-packages in ports.

Thanks for your thoughts, cheers,


freebsd-questions <at> mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at>"

Matthias Apitz | 22 Nov 15:41 2014

problem compiling pidgin 2.10.10


I have problems compiling pidgin 2.10.10 from source in one of my laptops, running
FreeBSD 10.x:

$ gmake
Making all in plugins
gmake[3]: Entering directory `/usr/local/guru/pidgin-2.10.10/finch/plugins'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/usr/local/guru/pidgin-2.10.10/finch/plugins'
gmake[3]: Entering directory `/usr/local/guru/pidgin-2.10.10/finch'
  CCLD     finch
/usr/bin/ld: i: invalid DSO for symbol `cur_term' definition
/usr/local/lib/ could not read symbols: Bad value
cc: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[3]: *** [finch] Error 1
gmake[3]: Leaving directory `/usr/local/guru/pidgin-2.10.10/finch'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/usr/local/guru/pidgin-2.10.10/finch'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/local/guru/pidgin-2.10.10'
gmake: *** [all] Error 2

the shared lib /usr/local/lib/ seems to be fine, for

$ nm /usr/local/lib/ | fgrep cur_term
00025b58 B cur_term
(Continue reading)

Alberto Mijares | 22 Nov 12:50 2014

RootOnZFS FreeBSD 10.1 can't boot after install

Hi list,

I never tried a RootOnZFS with RAIDZ{1,2} before. After 10.1-RELEASE
(couple days ago) I did.

I'm using VirtualBox on Debian. The VM has 3 or 4 disks (I've tried
both) and after a successful install, the VM doesn't boot. All I can
see is

ZFS: i/o error - all block copies unavailable
ZFS: can't find dataset u
ZFS: can't open root filesystem
gptzfsboot: failed to mount default pool zroot

FreeBSD/x86 boot
Default: zroot:

And it expects specific input that I can't guest. What I'm missing?
Plase give me some hint.

Thanks in advance

Alberto Mijares
freebsd-questions <at> mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at>"

(Continue reading)

Anders Jensen-Waud | 22 Nov 11:53 2014

iwn wi-fi and hostap


I am trying to set up an older IBM laptop as a wireless access point.
FreeBSD 10.1 (amd64) correctly identifies the wireless card:

iwn0 <at> pci0:3:0:0:        class=0x028000 card=0x11118086 chip=0x42308086
rev=0x61 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'PRO/Wireless 4965 AG or AGN [Kedron] Network Connection'
    class      = network

In trying to set it up with hostap, I get the following error:

root <at> beastie> ifconfig wlan0 create wlandev iwn0 wlanmode hostap bssid
authmode open ssid bsdwifi
ifconfig: SIOCIFCREATE2: Operation not supported

Is there some method of configuring iwn so that it can function as an
access point?


freebsd-questions <at> mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at>"

BS 2015 | 22 Nov 07:25 2014

BS2015: Extended Deadline for Abstract Submission - Dec 10, 2014


To unsubscribe, send an email to: unsubscribe-240482 <at> with the address:
questions <at> in the subject line.
freebsd-questions <at> mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at>"

françai s | 21 Nov 21:57 2014

A FreeBSD developer told me via private message that the the most FreeBSD developers don’t develop in machine code

This subject is irresistible to me,I like so much of this issue that get
out tears out of my eyes.

This topic is mainly for developers of FreeBSD that develop in machine
code, until even in binary code.

A FreeBSD developer told me via private message that the  the most FreeBSD
developers don’t develop in machine code, in other words, the  minority
FreeBSD developers develop in machine code, until even in binary code.

Thought I'd share and hope that someone can get some use out of it.

He told me this:

"We either create a macro expands to something like ".word <foo> “ or
sometimes the .word <foo> is just hard coded inline when there’s only going
to be one of them. Sometimes we expose them both in assembly and in C code,
in which case what we do varies a bit to accommodate the different
language’s syntax. It is rare, but has happened, that we only expose it to
C code.

Generally, though, we try to add support for the opcodes to gas so that we
get the constraint testing it does (making sure the opcode is supported at
the level you are compiling, making sure it isn’t in a delay slot or
violating some other precondition for its use)."

"You pointed me at macros that defined operations in terms of opcodes the
assembler didn’t understand with the workaround being the assembler
directive using .word followed by by some hex value to encode the opcode."

(Continue reading)

Ian Smith | 21 Nov 17:36 2014

Re: sysinstall fails to fetch; pkg install succeeds

In freebsd-questions Digest, Vol 546, Issue 3, Message: 7
On Tue, 18 Nov 2014 22:10:12 -0700 Gary Aitken <freebsd <at>> wrote:

 > I'm in the process of installing a 9.3 system.
 > "pkg install foo" seems to work fine, fetching from the network.
 > However, if I run sysinstall (forgot to include the handbook), it fails
 > when trying to fetch from the network.  I've tried both FTP mode and
 > FTP through firewall mode.  What does sysinstall do that's different when 
 > trying to fetch from the network?

sysinstall only knows about the old pkg_tools (pkg_add etc) which have 
been defunct for quite a while.  I don't know why the pkg_* binaries are 
even left in place (let alone executable) on pkg(8)-using systems, as I 
found out the hard way after pkg2ng'ing 9.2R, then ungrokingly running 
the old not-yet-pkg-aware portmaster, managing to make quite a mess.

For anyone running an 8.x or 9.x system using pkg(8) exclusively, maybe 
via pkg2ng, I'd recommend considering - if rm seems drastic - at least:

 # chmod a-x /usr/sbin/pkg_*

Try bsdconfig(8) which I think still (re)installs the docs, and provides 
a (working?) front end for installing packages.  Let's know how it goes?

bsdconfig provides most if not all 'post-installation' functions from 
sysinstall, similar look'n'feel to bsdinstall (invoked for disk setup).

 > This is going through a firewall running natd and ipfw, so it may be a
 > firewall rule problem.  But I would have thought they would either both
(Continue reading)

Giuseppe Pagnoni | 21 Nov 12:17 2014

webcamd for integrated ricoh webcam on sony vaio VGN-SZ4XN/C laptop (linux driver r5u870)

Dear all,

I am trying with no success to make the camera on my laptop work under
FreeBSD 10.1 i386. The laptop is a Vaio VGN-SZ4XN/C, and the
integrated webcam is a Ricoh-made one.  Under Linux, it is recognized
as: "05ca:1835 Sony Visual Communication Camera VGP-VCC5" and is
supported by the driver r5u870.

I am unable to make it work under FreeBSD. I installed the packages:
- lib4l
- v4l_compat
- webcamd
- cuse4BSD-kmod

And entered in /boot/loader.conf:

and in /etc/rc.conf:

The camera is attached to usb 4.3. Now, if I enter:
# webcamd -d ugen4.3 -i 0 -v 0

I get:
Attached to ugen4.3[0]
webcamd: cannot find USB device

Any suggestions?

thanks in advance!
(Continue reading)