Re: Unable to access http://sane-project.org/

[Mike Clarke]

On Thursday 01 Aug 2013 11:58:01 Jerry wrote:

> Not really a FreeBSD problem; however, I was wondering if anyone else
> had been unable to access http://sane-project.org/ in the last 24 hours?

http://www.isup.me/ is a useful site for instantly checking this sort of 
thing.

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

Re: Unable to access http://sane-project.org/

[Trond Endrestøl]

On Thu, 1 Aug 2013 06:58-0400, Jerry wrote:

> Not really a FreeBSD problem; however, I was wondering if anyone else
> had been unable to access http://sane-project.org/ in the last 24 hours?

Confirmed inaccessible at work, both when URL was fed directly to my 
web browser and through the use of 
http://www.downforeveryoneorjustme.com/http://sane-project.org/


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

Unable to access http://sane-project.org/

[Jerry]

Not really a FreeBSD problem; however, I was wondering if anyone else
had been unable to access http://sane-project.org/ in the last 24 hours?

-- 
Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__

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

Re: Unable to build "DOC" ports

[Marc Fonvieille]

On Mon, Jul 22, 2013 at 08:47:47AM -0400, Carmel wrote:
> I am having a problem updating some ports since installing the
> "print/texlive-full" port a few days ago. I have: "TEX_DEFAULT=texlive"
> sans quotes at the top of my "/etc/make.conf" file.
> 
[...]

I think you have the reason just above.
For the moment the docproj port relies on print/teTeX-base and not
print/texlive-full.

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

Unable to build "DOC" ports

[Carmel]

I am having a problem updating some ports since installing the
"print/texlive-full" port a few days ago. I have: "TEX_DEFAULT=texlive"
sans quotes at the top of my "/etc/make.conf" file.

For instance, the "en-freebsd-doc-42326,1", and in fact all of the
*-freebsd-doc" ports are refusing to build. This is from the build log:

env UPGRADE_TOOL=portupgrade UPGRADE_PORT=en-freebsd-doc-42095,1 
UPGRADE_PORT_VER=42095,1 make clean
===>  Cleaning for docproj-1.17_13
===>  Cleaning for zh-docproj-0.1.20060303_6
===>  Cleaning for latex-cjk-4.8.2_6
===>  Cleaning for freetype-tools-1.3.1_9
===>  Cleaning for en-freebsd-doc-42326,1
env UPGRADE_TOOL=portupgrade UPGRADE_PORT=en-freebsd-doc-42095,1 
UPGRADE_PORT_VER=42095,1 make
===>  Found saved configuration for en-freebsd-doc-40771_1,1
===> Fetching all distfiles required by en-freebsd-doc-42326,1 for building
===>  Extracting for en-freebsd-doc-42326,1
=> SHA256 Checksum OK for freebsd-doc-42326.tar.gz.
===>  Patching for en-freebsd-doc-42326,1
===>   en-freebsd-doc-42326,1 depends on package: docproj>=1.17 - not found
===>Verifying install for docproj>=1.17 in /usr/ports/textproc/docproj
===>  Found saved configuration for docproj-1.17_12
===> Fetching all distfiles required by docproj-1.17_13 for building
===>  Extracting for docproj-1.17_13
===>  Patching for docproj-1.17_13
===>   docproj-1.17_13 depends on executable: dvips - found
===>   docproj-1.17_13 depends on executable: jadetex - found
===>  Configuring for docproj-1.17_13
===>  Installing for docproj-1.17_13
===>   docproj-1.17_13 depends on executable: fixrtf - found
===>   docproj-1.17_13 depends on executable: links - found
===>   docproj-1.17_13 depends on executable: pngtopnm - found
===>   docproj-1.17_13 depends on executable: scr2png - found
===>   docproj-1.17_13 depends on executable: scr2txt - found
===>   docproj-1.17_13 depends on executable: xsltproc - found
===>   docproj-1.17_13 depends on executable: peps - found
===>   docproj-1.17_13 depends on file: 
/usr/local/share/sgml/docbook/dsssl/modular - found
===>   docproj-1.17_13 depends on file: /usr/local/share/sgml/iso8879 - found
===>   docproj-1.17_13 depends on file: 
/usr/local/share/xml/dtd/xhtml/xhtml.soc - found
===>   docproj-1.17_13 depends on file: 
/usr/local/share/xsl/docbook/html/docbook.xsl - found
===>   docproj-1.17_13 depends on file: 
/usr/local/share/xsl/iso-schematron/xslt1/iso_schematron_skeleton_for_xslt1.xsl 
- found
===>   docproj-1.17_13 depends on file: 
/usr/local/share/xml/docbook/4.5/docbookx.dtd - found
===>   docproj-1.17_13 depends on file: 
/usr/local/share/xsl/docbook/html/docbook.xsl - found
===>   docproj-1.17_13 depends on file: 
/usr/local/share/xsl/iso-schematron/xslt1/iso_schematron_skeleton_for_xslt1.xsl 
- found
===>   docproj-1.17_13 depends on file: 
/usr/local/share/xml/docbook/4.5/docbookx.dtd - found
===>   docproj-1.17_13 depends on file: /usr/local/share/xml/xmlcharent/catalog 
- found
===>   docproj-1.17_13 depends on package: p5-XML-Parser>=2.41 - found
===>   docproj-1.17_13 depends on executable: zip - found
===>   docproj-1.17_13 depends on executable: svn - found
===>   docproj-1.17_13 depends on executable: igor - found
===>   docproj-1.17_13 depends on executable: cjktexsty - not found
===>Verifying install for cjktexsty in /usr/ports/chinese/docproj
===> Fetching all distfiles required by zh-docproj-0.1.20060303_6 for building
===>  Extracting for zh-docproj-0.1.20060303_6
===> Fetching all distfiles required by zh-docproj-0.1.20060303_6 for building
===>  Patching for zh-docproj-0.1.20060303_6
===>   zh-docproj-0.1.20060303_6 depends on shared library: iconv.3 - found
===>  Configuring for zh-docproj-0.1.20060303_6
===>  Building for zh-docproj-0.1.20060303_6
===> cjktexsty (all)
Warning: Object directory not changed from original 
/usr/ports/chinese/docproj/work/src/cjktexsty
lex -t  cjktexsty.l > cjktexsty.c
cc -O2 -pipe -march=athlon64 -fno-strict-aliasing -march=athlon64 
-I/usr/local/include -std=gnu99 -fstack-protector  -c cjktexsty.c
cc -O2 -pipe -march=athlon64 -fno-strict-aliasing -march=athlon64 
-I/usr/local/include -std=gnu99 -fstack-protector   -o cjktexsty cjktexsty.o 
-L/usr/local/lib -liconv
===>  Installing for zh-docproj-0.1.20060303_6
===>   zh-docproj-0.1.20060303_6 depends on executable: gbklatex - not found
===>Verifying install for gbklatex in /usr/ports/print/latex-cjk

===>  latex-cjk-4.8.2_6 conflicts with installed package(s): 
  tex-kpathsea-6.1.0_2
  tex-web2c-20120701_2

  They install files into the same place.
  You may want to stop build with Ctrl + C.

At that point the build continues until the following:

gcc -c -g -O2 -Wall -pedantic -I./../../lib  -I/usr/local/include -I.  
-DHAVE_LIBKPATHSEA=1 -DHAVE_LIBM=1 -DHAVE_LIBINTL=1  errormsg.c
gcc -c -g -O2 -Wall -pedantic -I./../../lib  -I/usr/local/include -I.  
-DHAVE_LIBKPATHSEA=1 -DHAVE_LIBM=1 -DHAVE_LIBINTL=1  filesrch.c
filesrch.c:39: error: conflicting types fo

Re: pkg: Unable to open ports directory /usr/ports: No such file or directory

[Matthew Seaman]

On 13/07/2013 11:17, Leslie Jensen wrote:

> 2013-07-12 13:25, Leslie Jensen skrev:
>>
>> When I run
>>
>> portsnap fetch update
>>
>> pkg version -vIL=
>>
>>
>> It returns
>>
>> pkg: Unable to open ports directory /usr/ports: No such file or directory
>>
>>
>> The directory is there and I can list the contents.
>>
>> What's going on?

> 
> I get this as well
> 
> gunzip: can't stat:
> files/30173a70f7852dc247fda74d2d4babaae21067417fc17e67dc388c9ec85a8e8a.gz:
> No such file or directory
> gunzip: can't stat:
> /var/db/portsnap/files/845df3602aa1742b771872ffbe945ee60e0c834ae1540ba0dab02f224cce56f5.gz:
> No such file or directory
> pkg: Unable to open ports directory /usr/ports: No such file or directory
> 
> I'm a bit lost. Do I have to remove something for this command to succeed?

Let's look at the command line you're using:

pkg version -vIL=

That -I means it's going to try and read the ports INDEX specifically --
ie. /usr/ports/INDEX

Does that file exist?  Does it have sensible contents?

Now, given your further comments, it seems something relatively
significant is wrong.  There's on obvious (but fairly easy to fix) thing
it might be.  Have you run out of space on any of your partitions?
What goes 'df -h' report?  Any real partition reporting 100% full is a
problem.  (Don't worry about synthetic filesystems like devfs reporting
100% usage: that's normal.)  If some filesystem is full, then you need
to either delete stuff, or move it onto a filesystem with more space.

You also seem to be having problems with portsnap(8) -- be aware there
was a problem reported recently.  See the thread on freebsd-ports@...
subject 'Latest snapshot' starting with this message:

http://lists.freebsd.org/pipermail/freebsd-ports/2013-July/084833.html

but to summarize several people saw the problem, and the cure was to
delete the files portsnap was using by 'rm -Rf /var/db/portsnap/files'
and then re-run 'portsnap fetch' and 'portsnap extract' -- warning: this
will wipe out everything you have in /usr/ports and download a complete
set of replacements.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.

PGP: http://www.infracaninophile.co.uk/pgpkey
JID: matt...@infracaninophile.co.uk



signature.asc
Description: OpenPGP digital signature

Re: pkg: Unable to open ports directory /usr/ports: No such file or directory

[Leslie Jensen]

2013-07-12 13:25, Leslie Jensen skrev:


When I run

portsnap fetch update

pkg version -vIL=


It returns

pkg: Unable to open ports directory /usr/ports: No such file or directory


The directory is there and I can list the contents.

What's going on?

Thanks

/Leslie

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



I get this as well

gunzip: can't stat: 
files/30173a70f7852dc247fda74d2d4babaae21067417fc17e67dc388c9ec85a8e8a.gz: 
No such file or directory
gunzip: can't stat: 
/var/db/portsnap/files/845df3602aa1742b771872ffbe945ee60e0c834ae1540ba0dab02f224cce56f5.gz: 
No such file or directory

pkg: Unable to open ports directory /usr/ports: No such file or directory

I'm a bit lost. Do I have to remove something for this command to succeed?

Thanks

/Leslie


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

pkg: Unable to open ports directory /usr/ports: No such file or directory

[Leslie Jensen]

When I run

portsnap fetch update

pkg version -vIL=


It returns

pkg: Unable to open ports directory /usr/ports: No such file or directory


The directory is there and I can list the contents.

What's going on?

Thanks

/Leslie

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

Re: courier imap - unable to access shared folders: "operation not supported"

[Mark Felder]

On Tue, 09 Jul 2013 08:23:05 -0500, R Skinner  
 wrote:



Ok. I'll give it a try.
 But why would it work with the NFS server - before the repair and  
without FAM - and not now?


Oh, I misunderstood. I thought you weren't having problems until you  
turned on that enhanced idle feature.


I'd start asking in a courier irc channel or on their mailing lists --  
this sounds quite odd.

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

Re: courier imap - unable to access shared folders: "operation not supported"

[R Skinner]

On 07/09/13 23:05, Mark Felder wrote:
On Tue, 09 Jul 2013 08:00:22 -0500, R Skinner 
 wrote:


No, I don't. But then it was something I thought might help the 
situation and another feature to start playing with. Bit of a stretch 
really... but I was getting desperate.

 Would that have anything to do with the main problem though?


I'm honestly not sure. The doc seem to indicate that it won't work 
without a fam daemon on the NFS server, so maybe that's the root of 
the errors.

Ok. I'll give it a try.

But why would it work with the NFS server - before the repair and 
without FAM - and not now?

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

Re: courier imap - unable to access shared folders: "operation not supported"

[Mark Felder]

On Tue, 09 Jul 2013 08:00:22 -0500, R Skinner  
 wrote:


No, I don't. But then it was something I thought might help the  
situation and another feature to start playing with. Bit of a stretch  
really... but I was getting desperate.

 Would that have anything to do with the main problem though?


I'm honestly not sure. The doc seem to indicate that it won't work without  
a fam daemon on the NFS server, so maybe that's the root of the errors.

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

Re: courier imap - unable to access shared folders: "operation not supported"

[R Skinner]

On 07/09/13 21:56, Mark Felder wrote:

The courier documentation says this about using "enhanced idle" over NFS

FAM (but not Gamin) also works with NFS filesystems. On NFS 
clientsfam transparently forwards file monitoring requests to a peer 
famprocess on the NFS server.


Do you have a peer fam process on the NFS server?
No, I don't. But then it was something I thought might help the 
situation and another feature to start playing with. Bit of a stretch 
really... but I was getting desperate.


Would that have anything to do with the main problem though?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: courier imap - unable to access shared folders: "operation not supported"

[Mark Felder]

The courier documentation says this about using "enhanced idle" over NFS

FAM (but not Gamin) also works with NFS filesystems. On NFS clientsfam  
transparently forwards file monitoring requests to a peer famprocess on  
the NFS server.


Do you have a peer fam process on the NFS server?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

courier imap - unable to access shared folders: "operation not supported"

[R Skinner]

I'm really tearing my hair out here, this was working until I had to do 
a repair on the server hdd and rebuild it, and now I cannot work out why 
this has been working at all- no amount of googling even hints at what 
could be wrong.


I'm trying to access shared folders on a courier-imap server and the 
client simply does nothing, the logs are very obscure as well, and it is 
on these that I have been focusing my searches on and then trying 
generalisations:


Jul  9 12:59:29 server1 imapd: FAMCancelMonitor: Broken pipe
Jul  9 12:59:30 server1 imapd: 
shared-folders//tmp/1373338770.M51083P2034_sync.: 
Operation not supported

Jul  9 12:59:30 server1 imapd: FAMCancelMonitor: Broken pipe
Jul  9 12:59:30 server1 imapd: 
shared-folders//tmp/1373338770.M453207P2034_sync.: Operation 
not supported

Jul  9 12:59:30 server1 imapd: FAMCancelMonitor: Broken pipe
Jul  9 12:59:50 server1 imapd: LOGIN, user=, ip=, 
port=[59585], protocol=IMAP
Jul  9 13:00:12 server1 imapd: LOGIN, user=, ip=, 
port=[30542], protocol=IMAP

Jul  9 13:03:44 server1 imapd: end from FAM server connection
Jul  9 13:03:59 server1 imapd: FAMPending: timeout
Jul  9 13:05:18 server1 imapd: couriertls: read: Connection reset by peer
Jul  9 13:05:18 server1 imapd: DISCONNECTED, user=, ip=, 
headers=0, body=0, rcvd=314, sent=25847, time=306, starttls=1


I cannot find any references anywhere on this at all. The server has a 
mail store over NFS located on a ZFS fileserver, nothing has changed as 
such in the transition and it was working before the hdd repair was 
done. The only change I tried in the past 5 mins was turning the 
enhancedidle switch in the conf, and all that produced was the FAM 
errors you can see.


Does anyone have any clues to this?

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

netgraph network for jail(8) vnet jail unable to reach internet

[Joe]

Hello list.
Trying to get my script to work that creates a netgraph network for a 
jail(8) vnet jail. Every thing seems to work, but from inside of the 
started vnet jail I can not ping the public internet. The host can ping 
the public internet so the problem has to be in the netgraph script. The 
problem must be staring me in the face but I can just not see it. A 
fresh pair of eyes may see things I am missing.


I'm running 9.1-RELEASE with vimage compiled into the kernel. Non-vnet 
jails work fine and bridge/epair networked vnet jails work fine. The 
host has a single ethernet interface (rl0) facing the public internet. 
Dhcp is used to get the hosts ip address and dns server info. The 
vnet.ng script is designed to create a single ng bridge to rl0 and 
connect vnet jails to it as the jails are started. The following is a 
walk through of a test cycle showing what I can see from the host. At 
the end is a listing of the vnet.ng script.


Thanks for your help


# From the host lets see if there is a netgraph network before we start?
# Nope, no netgraph network running
# /root >ngctl ls -l
There are 2 total nodes:
  Name: rl0 Type: ether ID: 0001   Num hooks: 0
  Name: ngctl2850   Type: socketID: 0037   Num hooks: 0



# Here is the jail(8) jail.conf definition statements
# /root >cat /usr/local/etc/vnet/vdir9
vdir9 {
host.hostname   =  "vdir9";
path=  "/usr/jails/vdir9";
mount.fstab =  "/usr/local/etc/fstab/vdir9";
exec.start  =  "/bin/sh /etc/rc";
exec.stop   =  "/bin/sh /etc/rc.shutdown";
exec.consolelog =  "/var/log/vdir9.console.log";
devfs_ruleset   =  "4";
allow.mount.devfs;
vnet;
}



# Lets start the vnet jail
# /root >jail -f /usr/local/etc/qjail.vnet/vdir9 -c
vdir9: created


# Yes it’s really running.
# /root >jls
   JID  IP Address  Hostname  Path
 4  -   vdir9 /usr/jails/vdir9


# Lets start the netgraph network for the running vnet jail
# /root >vnet.ng start vdir9 rl0
Netgraph vnet jail network established successfully!


# Lets check the host for the vnet jail netgraph network
# Yep it’s there and looks complete to me.
# /root >ngctl ls -l

There are 4 total nodes:

  Name: rl0   Type: ether   ID: 0001   Num hooks: 2
  Local hook  Peer name   Peer typePeer ID Peer 
hook
  --  -   ---- 
-
  upper   bridge0 bridge   003dlink1 

  lower   bridge0 bridge   003dlink0 



  Name: bridge0   Type: bridge  ID: 003d   Num hooks: 3
  Local hook  Peer name   Peer typePeer ID Peer 
hook
  --  -   ---- 
-
  link2   vdir9   eiface   0041ether 

  link1   rl0 ether0001upper 


  link0   rl0 ether0001lower

  Name: vdir9 Type: eiface  ID: 0041   Num hooks: 1
  Local hook  Peer name   Peer typePeer ID Peer 
hook
  --  -   ---- 
-
  ether   bridge0 bridge   003dlink2 



 Name: ngctl3126  Type: socket  ID: 0046   Num hooks: 0


# Lets log into the running jail
# /root >jexec vdir9 tcsh

# Lets ping freebsd.org ip address. No public internet connection
# even though host can do same ping and get good reply.
vdir9 / >ping -c4 8.8.178.135
PING 8.8.178.135 (8.8.178.135): 56 data bytes

--- 8.8.178.135 ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
vdir9 / >exit
exit

# Now stop the vnet jails netgraph network
# /root >vnet.ng stop vdir9 rl0
Netgraph vnet jail network shutdown successfully!

# and yes the netgraph network is shutdown
# /root >ngctl ls -l
There are 2 total nodes:
  Name: rl0 Type: etherID: 0001   Num hooks: 0
  Name: ngctl3167   Type: socket   ID: 004b   Num hooks: 0



# Here is the vnet.ng  script
# It starts and stops the vnet jail’s netgraph network

#!/bin/sh
function=$1
jailname=$2
nicname=$3

jid=`jls -j ${jailname} jid`

# Load netgraph kernel modules if not done already.
for module in ng_socket netgraph ng_bridge ng_eiface ng_ether; do
  if ! kldstat -v | grep -qw ${module}; then
 kldload ${module} || exit 1
  fi
done

# mac manufacturer prefix. Modify if need be.
#mac_prefix="00:1d:92"
mac_prefix="07:22:49"

start() {

sysctl net.inet.ip.forwarding=1 > /dev/null 2> /dev/null

jid=`jls -j ${jailname} jid`

if [ "${jid}" -gt "100" ]; then
  echo " "
  echo "WARNING: The JID value is greater then 100."
  echo "This may indicate many cycles of starting/stopping vnet jails"
  echo "which results in lost memory pages. To recover the lost memory,"
  echo "shutdown the host and reboot. This will zero out the JID"
  echo "counter and make all the memo

Re: unable to compile lighttpd form source

[Lowell Gilbert]

"Zyumbilev, Peter"  writes:

> Hi,
>
> I am trying to follow instructions on this page:
>
> http://h264.code-shop.com/trac/wiki/Mod-H264-Streaming-Lighttpd-Version2
>
> and compile lighttpd.
>
> [root@pistolmp01 ~/lighttpd-1.4.28]# ./autogen.sh
> ./autogen.sh: running `libtoolize --copy --force'
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: copying file `m4/libtool.m4'
> libtoolize: copying file `m4/ltoptions.m4'
> libtoolize: copying file `m4/ltsugar.m4'
> libtoolize: copying file `m4/ltversion.m4'
> libtoolize: copying file `m4/lt~obsolete.m4'
> ./autogen.sh: running `aclocal -I m4'
> configure.ac:42: error: automatic de-ANSI-fication support has been removed
> /usr/local/share/aclocal-1.12/protos.m4:12: AM_C_PROTOTYPES is expanded
> from...
> configure.ac:42: the top level
> autom4te-2.69: /usr/local/bin/gm4 failed with exit status: 1
> aclocal-1.12: error: /usr/local/bin/autom4te-2.69 failed with exit status: 1
>
> System version is: FreeBSD 8.3-RELEASE-p3
>
>
> Please give me some hints as I am unable to install lighttpd with h264
> streaming support from both ports and source on FreeBSD.

The port seems to work fine, so I'd recommend you try to figure out
where that goes wrong for you, rather than figuring out version
incompatibilities in autotools...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

unable to compile lighttpd form source

[Zyumbilev, Peter]

Hi,

I am trying to follow instructions on this page:

http://h264.code-shop.com/trac/wiki/Mod-H264-Streaming-Lighttpd-Version2

and compile lighttpd.

[root@pistolmp01 ~/lighttpd-1.4.28]# ./autogen.sh
./autogen.sh: running `libtoolize --copy --force'
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
./autogen.sh: running `aclocal -I m4'
configure.ac:42: error: automatic de-ANSI-fication support has been removed
/usr/local/share/aclocal-1.12/protos.m4:12: AM_C_PROTOTYPES is expanded
from...
configure.ac:42: the top level
autom4te-2.69: /usr/local/bin/gm4 failed with exit status: 1
aclocal-1.12: error: /usr/local/bin/autom4te-2.69 failed with exit status: 1

System version is: FreeBSD 8.3-RELEASE-p3


Please give me some hints as I am unable to install lighttpd with h264
streaming support from both ports and source on FreeBSD.



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

Re: hast, zfs, unable to flush disk cache

[Pawel Jakub Dawidek]

On Fri, Mar 01, 2013 at 10:25:50PM +0200, Mikolaj Golub wrote:
> On Fri, Mar 01, 2013 at 11:39:23AM -0600, Chad M Stewart wrote:
> 
> > I've setup a 2 node cluster using HAST.  I'd previously had this
> > running 9.0 and then rebuilt the nodes using 9.1.  Under 9.0 I used
> > vfs.zfs.vdev.bio_flush_disable=1 but that setting does not appear to
> > work in 9.1.  The other difference, previous build had root disk on
> > UFS, while this build has only ZFS based file systems.
> > 
> > FreeBSD node1.san 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec  4 
> > 06:55:39 UTC 2012 
> > r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
> > 
> > 
> > Mar  1 17:07:25 node1 hastd[1446]: [disk5] (primary) Unable to flush disk 
> > cache on activemap update: Operation not supported by device.
> > Mar  1 17:07:28 node1 hastd[1440]: [disk3] (primary) Unable to flush disk 
> > cache on activemap update: Operation not supported by device.
> > Mar  1 17:07:28 node1 hastd[1437]: [disk2] (primary) Unable to flush disk 
> > cache on activemap update: Operation not supported by device.
> > Mar  1 17:07:28 node1 hastd[1434]: [disk1] (primary) Unable to flush disk 
> > cache on activemap update: Operation not supported by device.
> > Mar  1 17:07:28 node1 hastd[1446]: [disk5] (primary) Unable to flush disk 
> > cache on activemap update: Operation not supported by device.
> > Mar  1 17:07:28 node1 hastd[1443]: [disk4] (primary) Unable to flush disk 
> > cache on activemap update: Operation not supported by device.
> > 
> > I tried setting zfs set zfs:zfs_nocacheflush=1  but that
> > diddn't appear to work either.  I get a lot of lines in my log file
> > because of this.  I have also tried zfs set sync=disabled  but
> > HAST still outputs those lines in the log file.
> 
> These flushes were generated by HAST itself when it tried to flush
> activemap updates, that is why disabling BIO_FLUSH for ZFS dis not
> help much.
> 
> Setting "metaflush off" in hast.conf should help though.
> 
> BTW, hastd tries to detect devices that do not support BIO_FLUSH,
> checking for the returned errno, and automatically disable flushes if
> the errno is EOPNOTSUPP (Operation not supported). Unfortunately, your
> device returned ENODEV (Operation not supported by device).
> 
> What device do you have?
> 
> Pawel, do you think it would be a good idea to automatically disable
> activemap flush for ENODEV case too?

It would be better to find the driver that returns ENODEV and fix it, IMHO.

-- 
Pawel Jakub Dawidek   http://www.wheelsystems.com
FreeBSD committer http://www.FreeBSD.org
Am I Evil? Yes, I Am! http://tupytaj.pl


pgpUGDh098WMq.pgp
Description: PGP signature

Re: hast, zfs, unable to flush disk cache

[Chad M Stewart]

On Mar 1, 2013, at 2:25 PM, Mikolaj Golub wrote:

> What device do you have?

Its an older HP GL380 server, I think.   dmesg below, if you need output from 
something else I'm willing to provide.

Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.1-RELEASE #0 r243826: Tue Dec  4 06:55:39 UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2784.59-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf27  Family = f  Model = 2  Stepping = 7
  
Features=0xbfebfbff
  Features2=0x4400
real memory  = 3221225472 (3072 MB)
avail memory = 3136851968 (2991 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 2 package(s) x 1 core(s) x 2 HTT threads
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP/HT): APIC ID:  1
 cpu2 (AP): APIC ID:  6
 cpu3 (AP/HT): APIC ID:  7
ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 
(20110527/tbfadt-638)
ACPI Warning: Invalid length for Pm1bControlBlock: 32, using default 16 
(20110527/tbfadt-638)
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0  irqs 0-15 on motherboard
ioapic1  irqs 16-31 on motherboard
ioapic2  irqs 32-47 on motherboard
ioapic3  irqs 48-63 on motherboard
kbd1 at kbdmux0
acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
cpu1:  on acpi0
cpu2:  on acpi0
cpu3:  on acpi0
attimer0:  port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x920-0x923 on acpi0
pcib0:  on acpi0
pcib0: Length mismatch for 4 range: 2900 vs 28ff
pci0:  on pcib0
vgapci0:  port 0x2400-0x24ff mem 
0xf100-0xf1ff,0xf0ff-0xf0ff0fff at device 3.0 on pci0
pci0:  at device 4.0 (no driver attached)
pci0:  at device 4.2 (no driver attached)
isab0:  at device 15.0 on pci0
isa0:  on isab0
atapci0:  port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2000-0x200f at device 15.1 on pci0
ata0:  at channel 0 on atapci0
ata1:  at channel 1 on atapci0
ohci0:  mem 0xf0ef-0xf0ef0fff irq 7 at 
device 15.2 on pci0
usbus0 on ohci0
pcib1:  on acpi0
pcib1: Length mismatch for 4 range: 100 vs ff
pci1:  on pcib1
ciss0:  port 0x3000-0x30ff mem 
0xf2cc-0xf2cf,0xf2bf-0xf2bf3fff irq 30 at device 3.0 on pci1
ciss0: PERFORMANT Transport
pcib2:  on acpi0
pci2:  on pcib2
bge0:  mem 
0xf2df-0xf2df irq 29 at device 1.0 on pci2
bge0: CHIP ID 0x1002; ASIC REV 0x01; CHIP REV 0x10; PCI-X 100 MHz
miibus0:  on bge0
brgphy0:  PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge0: Ethernet address: 00:0b:cd:3c:fe:7f
bge1:  mem 
0xf2de-0xf2de irq 31 at device 2.0 on pci2
bge1: CHIP ID 0x1002; ASIC REV 0x01; CHIP REV 0x10; PCI-X 100 MHz
miibus1:  on bge1
brgphy1:  PHY 1 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge1: Ethernet address: 00:0b:cd:3c:fe:7e
pcib3:  on acpi0
pci3:  on pcib3
pcib4:  on acpi0
pcib4: Length mismatch for 4 range: 2000 vs 1fff
pci6:  on pcib4
bge2:  mem 
0xf7ff-0xf7ff irq 26 at device 2.0 on pci6
bge2: CHIP ID 0x0105; ASIC REV 0x00; CHIP REV 0x01; PCI-X 33 MHz
miibus2:  on bge2
brgphy2:  PHY 1 on miibus2
brgphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bge2: Ethernet address: 00:0b:cd:52:66:f1
pci6:  at device 30.0 (no driver 
attached)
acpi_tz0:  on acpi0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
fdc0:  port 0x3f2-0x3f5 irq 6 drq 2 on acpi0
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
pmtimer0 on isa0
orm0:  at iomem 
0xc-0xc7fff,0xc8000-0xcbfff,0xcc000-0xcd7ff,0xcd800-0xcefff,0xee000-0xe 
pnpid ORM on isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
atrtc0:  at port 0x70 irq 8 on isa0
atrtc0: Warning: Couldn't map I/O.
Event timer "RTC" frequency 32768 Hz quality 0
ppc0: parallel port not found.
ctl: CAM Target Layer loaded
p4tcc0:  on cpu0
p4tcc1:  on cpu1
p4tcc2:  on cpu2
p4tcc3:  on cpu3
ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable,
add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS filesystem version 5
ZFS storage pool version 28
Timecounters tick every 1.000 msec
usbus0: 12Mbps Full Speed USB v1.0
ugen0.1: <0x1166> at usbus0
uhub0: <0

Re: hast, zfs, unable to flush disk cache

[Mikolaj Golub]

On Fri, Mar 01, 2013 at 11:39:23AM -0600, Chad M Stewart wrote:

> I've setup a 2 node cluster using HAST.  I'd previously had this
> running 9.0 and then rebuilt the nodes using 9.1.  Under 9.0 I used
> vfs.zfs.vdev.bio_flush_disable=1 but that setting does not appear to
> work in 9.1.  The other difference, previous build had root disk on
> UFS, while this build has only ZFS based file systems.
> 
> FreeBSD node1.san 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec  4 
> 06:55:39 UTC 2012 
> r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
> 
> 
> Mar  1 17:07:25 node1 hastd[1446]: [disk5] (primary) Unable to flush disk 
> cache on activemap update: Operation not supported by device.
> Mar  1 17:07:28 node1 hastd[1440]: [disk3] (primary) Unable to flush disk 
> cache on activemap update: Operation not supported by device.
> Mar  1 17:07:28 node1 hastd[1437]: [disk2] (primary) Unable to flush disk 
> cache on activemap update: Operation not supported by device.
> Mar  1 17:07:28 node1 hastd[1434]: [disk1] (primary) Unable to flush disk 
> cache on activemap update: Operation not supported by device.
> Mar  1 17:07:28 node1 hastd[1446]: [disk5] (primary) Unable to flush disk 
> cache on activemap update: Operation not supported by device.
> Mar  1 17:07:28 node1 hastd[1443]: [disk4] (primary) Unable to flush disk 
> cache on activemap update: Operation not supported by device.
> 
> I tried setting zfs set zfs:zfs_nocacheflush=1  but that
> diddn't appear to work either.  I get a lot of lines in my log file
> because of this.  I have also tried zfs set sync=disabled  but
> HAST still outputs those lines in the log file.

These flushes were generated by HAST itself when it tried to flush
activemap updates, that is why disabling BIO_FLUSH for ZFS dis not
help much.

Setting "metaflush off" in hast.conf should help though.

BTW, hastd tries to detect devices that do not support BIO_FLUSH,
checking for the returned errno, and automatically disable flushes if
the errno is EOPNOTSUPP (Operation not supported). Unfortunately, your
device returned ENODEV (Operation not supported by device).

What device do you have?

Pawel, do you think it would be a good idea to automatically disable
activemap flush for ENODEV case too?

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

hast, zfs, unable to flush disk cache

[Chad M Stewart]

I've setup a 2 node cluster using HAST.  I'd previously had this running 9.0 
and then rebuilt the nodes using 9.1.  Under 9.0 I used 
vfs.zfs.vdev.bio_flush_disable=1 but that setting does not appear to work in 
9.1.  The other difference, previous build had root disk on UFS, while this 
build has only ZFS based file systems.


FreeBSD node1.san 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243826: Tue Dec  4 
06:55:39 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  
i386


Mar  1 17:07:25 node1 hastd[1446]: [disk5] (primary) Unable to flush disk cache 
on activemap update: Operation not supported by device.
Mar  1 17:07:28 node1 hastd[1440]: [disk3] (primary) Unable to flush disk cache 
on activemap update: Operation not supported by device.
Mar  1 17:07:28 node1 hastd[1437]: [disk2] (primary) Unable to flush disk cache 
on activemap update: Operation not supported by device.
Mar  1 17:07:28 node1 hastd[1434]: [disk1] (primary) Unable to flush disk cache 
on activemap update: Operation not supported by device.
Mar  1 17:07:28 node1 hastd[1446]: [disk5] (primary) Unable to flush disk cache 
on activemap update: Operation not supported by device.
Mar  1 17:07:28 node1 hastd[1443]: [disk4] (primary) Unable to flush disk cache 
on activemap update: Operation not supported by device.


I tried setting zfs set zfs:zfs_nocacheflush=1  but that diddn't appear 
to work either.  I get a lot of lines in my log file because of this.  I have 
also tried  zfs set sync=disabled  but HAST still outputs those lines in 
the log file.

Any suggestions?


Thank you,
Chad

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

Re: Unable to install xorg using pkg_add

[Fbsd8]

Ralf Mardorf wrote:

On Thu, 2013-01-10 at 10:30 -0600, Scott Eberl wrote:

[snip] I then updated to 9.1-RELEASE using freebsd-update. Everything
seems to have gone smoothly but now I'm getting the below error when trying
to isntall xorg.


I upgraded from 8.3 to 9.1,
http://lists.freebsd.org/pipermail/freebsd-questions/2012-December/247579.html 
, without fixing anything until now, it was possible to build X today from 
/usr/ports/x11/xorg.

Regarding to your issue, take a look at
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/ , there's no 9.1, IIUC
you need to use stable.

Regards,
Ralf




Add this to your /root/.cshrc file

setenv PACKAGESITE "ftp://ftp.FreeBSD.org/pub/FreeBSD/ports
/i386/packages-current/Latest/"

and when you su to root your pkg_add -r command will now get
current packages.
Its still 6 weeks old, but it's the best FreeBSD has to offer
right now for 9.1 users. Works for me.


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

Re: Unable to install xorg using pkg_add

[Ralf Mardorf]

On Thu, 2013-01-10 at 10:30 -0600, Scott Eberl wrote:
> [snip] I then updated to 9.1-RELEASE using freebsd-update. Everything
> seems to have gone smoothly but now I'm getting the below error when trying
> to isntall xorg.

I upgraded from 8.3 to 9.1,
http://lists.freebsd.org/pipermail/freebsd-questions/2012-December/247579.html 
, without fixing anything until now, it was possible to build X today from 
/usr/ports/x11/xorg.

Regarding to your issue, take a look at
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/ , there's no 9.1, IIUC
you need to use stable.

Regards,
Ralf

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

Re: Unable to install xorg using pkg_add

[Walter Hurry]

On Thu, 10 Jan 2013 10:30:43 -0600, Scott Eberl wrote:

> Hello, I just installed FreeBSD last night using the bootonly image for
> 9.0-RELEASE. I then updated to 9.1-RELEASE using freebsd-update.
> Everything seems to have gone smoothly but now I'm getting the below
> error when trying to isntall xorg.
> 
I suggest:

portsnap fetch
portsnap extract
cd /usr/ports/
make install clean

(with root privileges, of course)

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

Re: Unable to install xorg using pkg_add

[Eric S Pulley]

Read the 9.1 Release notes. This is the expected behavior. You'll need the
DVD iso or build from ports to get xorg going in 9.1 right now.


> Hello, I just installed FreeBSD last night using the bootonly image for
> 9.0-RELEASE. I then updated to 9.1-RELEASE using freebsd-update.
> Everything
> seems to have gone smoothly but now I'm getting the below error when
> trying
> to isntall xorg.
>
> Error: Unable to get
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/xorg.tbz:
> File unavailable (e.g., file not found, no access)
> pkg_add: unable to fetch '
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/xorg.tbz'
> by URL
>
>


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

Re: Unable to install xorg using pkg_add

[Matthew Seaman]

On 10/01/2013 16:30, Scott Eberl wrote:
> Hello, I just installed FreeBSD last night using the bootonly image for
> 9.0-RELEASE. I then updated to 9.1-RELEASE using freebsd-update. Everything
> seems to have gone smoothly but now I'm getting the below error when trying
> to isntall xorg.
> 
> Error: Unable to get
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/xorg.tbz:
> File unavailable (e.g., file not found, no access)
> pkg_add: unable to fetch '
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/xorg.tbz'
> by URL
> 

Alas, this is expected.  Because of the security incident
(http://www.freebsd.org/news/2012-compromise.html) all of the package
building cluster is temporarily quarantined.  So there aren't any
packages built for 9.1-RELEASE.

You should be able to use pkg_tools packages built for any 9.x release
or stable/9 if you can locate them on the FTP servers (although these
will be at least about 2 months old by now) or you can grab the ports
(use of portsnap recommended) and build your own.

Cheers,

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

Unable to install xorg using pkg_add

[Scott Eberl]

Hello, I just installed FreeBSD last night using the bootonly image for
9.0-RELEASE. I then updated to 9.1-RELEASE using freebsd-update. Everything
seems to have gone smoothly but now I'm getting the below error when trying
to isntall xorg.

Error: Unable to get
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/xorg.tbz:
File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch '
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/xorg.tbz'
by URL






output of uname -a
FreeBSD freebsd 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec  4
09:23:10 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
 amd64
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Unable to get crash dump

[Rick Miller]

Hi All,

Running 8.3-STABLE 5/21/2012 on HP DL360.  While testing crash dump
functionality, the dump aborts with the following message:

Aborting dump due to I/O error.
status == 0xb, scsi status == 0x0

** DUMP FAILED (ERROR 5) **
Automatic reboot in 5 seconds - press a key on the console to abort

Googling and searching freebsd.org have produced what appeared to be
some what relevant messages, but I found nothing pointing to a cause
and fix.  I'm hoping someone might be able to point me in a direction
to figuring this out.

-- 
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Unable to update virtualbox-ose-additions 4.1.16

[Alexandre]

Hi,

I got a VM VirtualBox that use FreeBSD 9-STABLE (updated yesterday).
Now I want to update my ports, but I can't update 
I use the command <# portmaster -a -D --no-confirm> to update ports with
portmaster tool.

The error is :
[...]
The failing command:
@cc  -m64   -o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/VBoxClient
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/main.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/clipboard-helper.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/src/VBox/GuestHost/SharedClipboard/x11-clipboard.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/clipboard.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-host.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/seamless-x11.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/thread.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/display.o
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/obj/VBoxClient/hostversion.o
  -L/usr/X11R6/lib32  -L/usr/X11R6/lib  -L/usr/lib  -L/usr/X11R6/lib
 -L/usr/local/lib   -liconv
/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/RuntimeGuestR3.a

/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/VBoxGuestR3Lib.a

/usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-4.1.16/out/freebsd.amd64/release/lib/additions/RuntimeGuestR3.a
  -lX11   -lXrandr   -lXt   -lsupc++   -lgcc_eh   -lXext   -lXmu
-lpthread   -liconv
*** Error code 2

Stop in /usr/ports/emulators/virtualbox-ose-additions.
*** Error code 1

Stop in /usr/ports/emulators/virtualbox-ose-additions.

===>>> make failed for emulators/virtualbox-ose-additions
===>>> Aborting update

===>>> Update for emulators/virtualbox-ose-additions failed
===>>> Aborting update

Terminated
[...]

I posted the full output (with "script") here : http://pastebin.com/cmBbqzKx

This VM is installed on a Windows 7 host (VirtualBox 4.1.16r78094).

# uname -a
FreeBSD VirtualBox 9.0-STABLE FreeBSD 9.0-STABLE #0: Tue Jun  5 16:03:26
CEST 2012 root@VirtualBox:/usr/obj/usr/src/sys/GENERIC  amd64

# pkg_info | grep virtualbox
virtualbox-ose-additions-4.1.8 VirtualBox additions for FreeBSD guests

Thanks for your help.

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

Re: Corrections to: unable to upgrade to mysql55-server

[Matthew Seaman]

On 01/06/2012 00:32, Gene wrote:
> Actually, I did just as above except using portmanager.. Tried deleting the 
> two packages & tried again with portmaster. Still no luck. So I deleted them 
> again and installed from packages. mysql-client-5.4.. installed lib/mysql/
> libmysqlclient.so.18, but mysql-server-5.4... wanted lib/mysql/
> libmysqlclient.so.16. Finally, after giving ritual sacrifice to the backup 
> gods, I went to the ZFS snapshots and just restored directories wholesale and 
> everything is working again albeit with previous versions of mysql (and 
> postfix which also gave me fits) but with the package database entries now 
> missing (for some strange reason, I hadn't been backing up that directory. 
> You'd think I'd learn - if it ain't broke, don't fix it. 

Something is definitely not right with your system.  It really shouldn't
be that painful.

The missing package database entries can usually be recovered by forcing
a reinstall of the package over what is already on disk, but if
everything is working properly, I wouldn't worry too much about the
contents of /var/db/pkg.

I'm thinking that having the registry of installed ports in a completely
separate partition or ZFS (ie /var) to where the ports are installed
(/usr/local) is not ideal, especially when using snapshots to provide a
roll-back capability.  /usr/local/var/db/pkg perhaps?

> Still wonder what went wrong though Seems every time I try to update any 
> ports, things get broken, ports don't compile, etc., etc., ad infinitum, ad 
> nauseum. I've got to be doing something wrong. Incidentally, portmaster, when 
> updating mysql54-server reliably rebooted the system. Hmmm
> 
> Anyone know if there is a good memory test utility that can be run on FBSD 
> AMD64?

Yes -- you could well be having hardware problems.  Try a few passes of
memtest86.  It's in ports, but it's a standalone application you boot
into so concepts of compatibility with particular OSes is irrelevant.

Also do the usual stuff removing any dust or fluff that may be clogging
up the ventilation holes or heatsinks, check that you've still got a
good thermal contact between the heatsink and CPU (replace thermal
compound if necessary).  Also make sure your power supply is up to the
job.  They can fade over time, or you may have added a peripheral too
far.  [Although generally if anything here was wrong, you'ld see the
machine crashing and rebooting rather than it affecting use of the ports...]

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

Re: Corrections to: unable to upgrade to mysql55-server

[Gene]

On Wed, 30 May 2012 18:18:25 +0100, Matthew Seaman wrote
> On 30/05/2012 17:57, Gene wrote:
> >  I've been trying to install the port databases/mysql55-server, updating 
from 
> > the older  5.4 version. mysql55-client installed just fine. However, when 
I 
> > "make" the '-server' port I get the errors shown in the first listing 
below. 
> > So I tried 
> >  "portmanager databases/mysql55-server -l -u"  
> > (latest version of portmanager - 0.4.1_9).
> 
> Did you update to databases/mysql55-client before trying this?
> mysqlXX-server depends on mysqlXX-client for the libmysql shared library
> and related header files.
> 
> Generally to switch from mysql 5.4 to mysql 5.5 you'ld do something like
> this:
> 
>0) Backups, fasting, ritual cleansing, sacrifice of black 
> cockerel,  you know the drill.
> 
>1) Stop MySQL -- plus any web servers or whatever that access mysql.
> 
>   # /usr/local/etc/rc.d/mysql-server stop
>   # ...
> 
>2) If there is any mention of MYSQL related variables in
>   /etc/make.conf, particularly those referring to version 
> numbers,  comment them out.
> 
>3) Upgrade mysql-client:
> 
> # portmaster -o databases/mysql55-client 'mysql-client-5.4.*'
> 
>4) Upgrade mysql-server:
> 
> # portmaster -o databases/mysql55-server 'mysql-server-5.4.*'
> 
>5) If you've got them installed, upgrade mysql-scripts:
> 
> # portmaster -o databases/mysql55-scripts 'mysql-scripts-5.4.*'
> 
>6) Upgrade anything that links against libmysql.so -- you can use
>   sysutils/bsdadminscripts which contains a handy script to tell
>   you what applications on your system are affected.  Or, for the
>   lazy and those with excess spare time:
> 
> # portmaster -r databases/mysql55-client
> 
>   (but this will do far more work than necessary)
> 
>7) Restart mysql and run the supplied program to update schemas etc.
> 
> # /usr/local/etc/rc.d/mysql-server start
> # mysql_upgrade
> 
>8) Restart any applications that use mysql.
> 
>9) Test.
> 
>   Cheers,
> 
>   Matthew
> 
Actually, I did just as above except using portmanager.. Tried deleting the 
two packages & tried again with portmaster. Still no luck. So I deleted them 
again and installed from packages. mysql-client-5.4.. installed lib/mysql/
libmysqlclient.so.18, but mysql-server-5.4... wanted lib/mysql/
libmysqlclient.so.16. Finally, after giving ritual sacrifice to the backup 
gods, I went to the ZFS snapshots and just restored directories wholesale and 
everything is working again albeit with previous versions of mysql (and 
postfix which also gave me fits) but with the package database entries now 
missing (for some strange reason, I hadn't been backing up that directory. 
You'd think I'd learn - if it ain't broke, don't fix it. 

Still wonder what went wrong though Seems every time I try to update any 
ports, things get broken, ports don't compile, etc., etc., ad infinitum, ad 
nauseum. I've got to be doing something wrong. Incidentally, portmaster, when 
updating mysql54-server reliably rebooted the system. Hmmm

Anyone know if there is a good memory test utility that can be run on FBSD 
AMD64?

Anyway - thanks for the assistance...
Gene

> -- 
> Dr Matthew J Seaman MA, D.Phil.
> PGP: http://www.infracaninophile.co.uk/pgpkey


--

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

Re: Corrections to: unable to upgrade to mysql55-server

[Matthew Seaman]

On 30/05/2012 17:57, Gene wrote:
>  I've been trying to install the port databases/mysql55-server, updating from 
> the older  5.4 version. mysql55-client installed just fine. However, when I 
> "make" the '-server' port I get the errors shown in the first listing below. 
> So I tried 
>  "portmanager databases/mysql55-server -l -u"  
> (latest version of portmanager - 0.4.1_9). 

Did you update to databases/mysql55-client before trying this?
mysqlXX-server depends on mysqlXX-client for the libmysql shared library
and related header files.

Generally to switch from mysql 5.4 to mysql 5.5 you'ld do something like
this:

   0) Backups, fasting, ritual cleansing, sacrifice of black cockerel,
  you know the drill.

   1) Stop MySQL -- plus any web servers or whatever that access mysql.

# /usr/local/etc/rc.d/mysql-server stop
# ...

   2) If there is any mention of MYSQL related variables in
  /etc/make.conf, particularly those referring to version numbers,
  comment them out.

   3) Upgrade mysql-client:

# portmaster -o databases/mysql55-client 'mysql-client-5.4.*'

   4) Upgrade mysql-server:

# portmaster -o databases/mysql55-server 'mysql-server-5.4.*'

   5) If you've got them installed, upgrade mysql-scripts:

# portmaster -o databases/mysql55-scripts 'mysql-scripts-5.4.*'

   6) Upgrade anything that links against libmysql.so -- you can use
  sysutils/bsdadminscripts which contains a handy script to tell
  you what applications on your system are affected.  Or, for the
  lazy and those with excess spare time:

# portmaster -r databases/mysql55-client

  (but this will do far more work than necessary)

   7) Restart mysql and run the supplied program to update schemas etc.

# /usr/local/etc/rc.d/mysql-server start
# mysql_upgrade

   8) Restart any applications that use mysql.

   9) Test.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey




signature.asc
Description: OpenPGP digital signature

Corrections to: unable to upgrade to mysql55-server

[Gene]

Running 8.1 amd64. Ports are up to date (via portsnap). 

 I've been trying to install the port databases/mysql55-server, updating from 
the older  5.4 version. mysql55-client installed just fine. However, when I 
"make" the '-server' port I get the errors shown in the first listing below. 
So I tried 
 "portmanager databases/mysql55-server -l -u"  
(latest version of portmanager - 0.4.1_9). 

 Attempts to update produce multiple looping errors as in the second listing 
 below. I've found references to this error, but the latest version of 
 portmanager (I thought) was supposed to fix this (or did it just eliminate 
 infinite loops?). Note that I have attempted to compile some of the 
"looping" ports individually and they compile and install with no problems.

 Does anyone have an idea what might be going on here? 

 Thanks in advance... 

First listing
 === 
  

 /usr/bin/c++   -O2 -fno-strict-aliasing -pipe -Wall -Wno-unused-parameter - 
 fno-implicit-templates -fno-exceptions -fno-rtti -O2 -fno-strict-aliasing - 
 pipe -DDBUG_OFF  -Wl,--export-dynamic CMakeFiles/mysqld.dir/main.cc.o  -o 
 mysqld  -pthread libsql.a ../mysys/libmysys.a ../storage/perfschema/ 
 libperfschema.a ../storage/myisam/libmyisam.a ../storage/csv/libcsv.a ../ 
 storage/myisammrg/libmyisammrg.a ../storage/heap/libheap.a ../storage/ 
 innobase/libinnobase.a libpartition.a ../mysys/libmysys.a ../dbug/libdbug.a 
 ../mysys/libmysys.a ../dbug/libdbug.a -lz -lm ../strings/libstrings.a ../
vio/ 
 libvio.a ../regex/libregex.a -lwrap -lcrypt ../extra/yassl/libyassl.a ../ 
 extra/yassl/taocrypt/libtaocrypt.a -pthread 

 libsql.a(sql_yacc.cc.o)(.text+0xb696): In function `MYSQLparse(void*)': 
 : undefined reference to `vtable for 
Alter_table_truncate_partition_statement' 

 libsql.a(sql_yacc.cc.o)(.text+0xb72a): In function `MYSQLparse(void*)': 
 : undefined reference to `vtable for Alter_table_repair_partition_statement' 

 libsql.a(sql_yacc.cc.o)(.text+0xb77a): In function `MYSQLparse(void*)': 
 : undefined reference to `vtable for Alter_table_check_partition_statement' 

 libsql.a(sql_yacc.cc.o)(.text+0xb7de): In function `MYSQLparse(void*)': 
 : undefined reference to `vtable for 
Alter_table_analyze_partition_statement' 

 libsql.a(sql_yacc.cc.o)(.text+0xb842): In function `MYSQLparse(void*)': 
 : undefined reference to `vtable for 
Alter_table_optimize_partition_statement' 

 *** Error code 1 
 1 error 
 ===

Second listing

skipping tcl-modules-8.5.11 /lang/tcl-modules marked IGNORE reason: looping, 
3rd attempt at make
skipping python26-2.6.8 /lang/python26 marked IGNORE reason: looping, 3rd 
attempt at make
skipping expat-2.0.1_2 /textproc/expat2 marked IGNORE reason: looping, 3rd 
attempt at make
skipping renderproto-0.11.1 /x11/renderproto marked IGNORE reason: looping, 
3rd attempt at make
skipping gmp-5.0.5 /math/gmp marked IGNORE reason: looping, 3rd attempt at 
make



--

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

unable to upgrade to mysql55-server

[Gene]

Greetings:

ZRunning 8.1 amd64. Ports are up to date (via portsnap).

I've been trying to install the port databases/mysql55-server from the older 
5.4 version. mysql55-client installed just fine. However, when I "make" the 
port I get the shown in the first listing below. So I tried 
"portmanager databases/mysql55-server -l -u"  (latest version - -0.4.1_9). 
Attempts to update produce multiple looping errors as in second listing 
below. I've found references to this error, but the latest version of 
portmanager (I thought) was supposed to fix this (or did it just eliminate 
infinite loops?).

Does anyone have an idea what might be going on here?

Thanks in advance...


===


/usr/bin/c++   -O2 -fno-strict-aliasing -pipe -Wall -Wno-unused-parameter -
fno-implicit-templates -fno-exceptions -fno-rtti -O2 -fno-strict-aliasing -
pipe -DDBUG_OFF  -Wl,--export-dynamic CMakeFiles/mysqld.dir/main.cc.o  -o 
mysqld  -pthread libsql.a ../mysys/libmysys.a ../storage/perfschema/
libperfschema.a ../storage/myisam/libmyisam.a ../storage/csv/libcsv.a ../
storage/myisammrg/libmyisammrg.a ../storage/heap/libheap.a ../storage/
innobase/libinnobase.a libpartition.a ../mysys/libmysys.a ../dbug/libdbug.a 
../mysys/libmysys.a ../dbug/libdbug.a -lz -lm ../strings/libstrings.a ../vio/
libvio.a ../regex/libregex.a -lwrap -lcrypt ../extra/yassl/libyassl.a ../
extra/yassl/taocrypt/libtaocrypt.a -pthread 

libsql.a(sql_yacc.cc.o)(.text+0xb696): In function `MYSQLparse(void*)':
: undefined reference to `vtable for Alter_table_truncate_partition_statement'

libsql.a(sql_yacc.cc.o)(.text+0xb72a): In function `MYSQLparse(void*)':
: undefined reference to `vtable for Alter_table_repair_partition_statement'

libsql.a(sql_yacc.cc.o)(.text+0xb77a): In function `MYSQLparse(void*)':
: undefined reference to `vtable for Alter_table_check_partition_statement'

libsql.a(sql_yacc.cc.o)(.text+0xb7de): In function `MYSQLparse(void*)':
: undefined reference to `vtable for Alter_table_analyze_partition_statement'

libsql.a(sql_yacc.cc.o)(.text+0xb842): In function `MYSQLparse(void*)':
: undefined reference to `vtable for Alter_table_optimize_partition_statement'



*** Error code 1
1 error
===



--

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

Re: vdevs in zpool spereated, unable to import

[Daniel Staal]

On Mon, February 13, 2012 2:25 pm, Daniel Staal wrote:
>
> On Mon, February 13, 2012 11:31 am, Adam Coates wrote:
>> More insight into my tomfoolery: I think the "different hostnames" issue
>> may be because of my ignorance. If you can't tell I'm fairly new to zfs,
>> and even newer to the revelation of zpools (I've been using one for over
>> a year but had no idea, I wasn't the one who set it up). When I had
>> finished the fresh os install I was originally trying to /mount/ the
>> drives. I know I was running into an error of:
>>
>> "/dev/da0 is part of active pool 'tank'"
>>
>> with a suggestion that the mount could only proceed with the "-f"
>> argument. I can't recall what exactly I did, but I may have tried to
>> force a mount of da0 to /tank in pool "tank". This would make sense why
>> I now can't import the original pool tank, and why there is a destroyed
>> pool tank. Since these were raidz, is there any chance of recovering
>> from my error?
>
> You may have done some major damage, but things to try (in my thoughts on
> order):
>
> zpool import -f 
>
> That's trying to import by the numeric id, not the name.  At the very
> least, you should get a different error message.  (You may need the -D as
> well.)
>
> zpool import -D -f -d /dev/da0 -d /dev/da1
>
> Now we're trying to import destroyed pools, and looking at both drives
> explicitly for data.
>
> The next is a bit of hail mary, and if anyone else has a good idea, I'd
> try that first...:  You can try mounting /dev/da1 like you did /dev/da0,
> and *then* trying to import.  Basically, at that point you are trying to
> get them both messed up the same way.
>
> Since these were raidz: Where's the third disk?  If you have two of the
> raidz disks, you should be able to rebuild the third.  (It's *possible*,
> it appears, to run a raidz with two disks, but you don't get any benefits
> over mirroring, and you complicate recovery - a mirror in this situation
> would be directly usable.  In theory a two-disk raidz should be
> recoverable from one disk, I think, but it may not have been well-tested.)

Sorry, I went back to check something:

Swap /dev/da0 with /dev/da1, and vice-versa.  I'd gotten which disk you
tried mounting backwards.

Daniel T. Staal

---
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---

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

Re: vdevs in zpool spereated, unable to import

[Daniel Staal]

On Mon, February 13, 2012 11:31 am, Adam Coates wrote:
> More insight into my tomfoolery: I think the "different hostnames" issue
> may be because of my ignorance. If you can't tell I'm fairly new to zfs,
> and even newer to the revelation of zpools (I've been using one for over
> a year but had no idea, I wasn't the one who set it up). When I had
> finished the fresh os install I was originally trying to /mount/ the
> drives. I know I was running into an error of:
>
> "/dev/da0 is part of active pool 'tank'"
>
> with a suggestion that the mount could only proceed with the "-f"
> argument. I can't recall what exactly I did, but I may have tried to
> force a mount of da0 to /tank in pool "tank". This would make sense why
> I now can't import the original pool tank, and why there is a destroyed
> pool tank. Since these were raidz, is there any chance of recovering
> from my error?

You may have done some major damage, but things to try (in my thoughts on
order):

zpool import -f 

That's trying to import by the numeric id, not the name.  At the very
least, you should get a different error message.  (You may need the -D as
well.)

zpool import -D -f -d /dev/da0 -d /dev/da1

Now we're trying to import destroyed pools, and looking at both drives
explicitly for data.

The next is a bit of hail mary, and if anyone else has a good idea, I'd
try that first...:  You can try mounting /dev/da1 like you did /dev/da0,
and *then* trying to import.  Basically, at that point you are trying to
get them both messed up the same way.

Since these were raidz: Where's the third disk?  If you have two of the
raidz disks, you should be able to rebuild the third.  (It's *possible*,
it appears, to run a raidz with two disks, but you don't get any benefits
over mirroring, and you complicate recovery - a mirror in this situation
would be directly usable.  In theory a two-disk raidz should be
recoverable from one disk, I think, but it may not have been well-tested.)

Daniel T. Staal

---
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---

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

vdevs in zpool spereated, unable to import

[Adam Coates]

More insight into my tomfoolery: I think the "different hostnames" issue 
may be because of my ignorance. If you can't tell I'm fairly new to zfs, 
and even newer to the revelation of zpools (I've been using one for over 
a year but had no idea, I wasn't the one who set it up). When I had 
finished the fresh os install I was originally trying to /mount/ the 
drives. I know I was running into an error of:


"/dev/da0 is part of active pool 'tank'"

with a suggestion that the mount could only proceed with the "-f" 
argument. I can't recall what exactly I did, but I may have tried to 
force a mount of da0 to /tank in pool "tank". This would make sense why 
I now can't import the original pool tank, and why there is a destroyed 
pool tank. Since these were raidz, is there any chance of recovering 
from my error?


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

vdevs in zpool spereated, unable to import

[Adam Coates]

I have a problem that could either be easily solved, or potentially coul 
dhave me royally screwed.


I had a FreeBSD 8.0 system crash on me, and I lost some binaries 
including zfs tools. I tried fixing with Fixit but had no such luck so I 
rebuilt world and kernel on a fresh hard drive. The old system had zpool 
raidz containing da0 and da1. Because of the crash I didn't get to 
export this pool, but when I try to import now I get this:


# zpool import tank
cannot import 'tank': one or more devices is currently unavailable

If I take I look at the list I only see this:

# zpool import
  pool: tank
id: 4433502968625883981
 state: UNAVAIL
status: One or more devices contains corrupted data.
action: The pool cannot be imported due to damaged devices or data.
   see: http://www.sun.com/msg/ZFS-8000-5E
config:

tankUNAVAIL  insufficient replicas
  da1   ONLINE

if I list destroyed pools:

# zpool import -D
  pool: tank
id: 12367720188787195607
 state: ONLINE (DESTROYED)
action: The pool can be imported using its name or numeric identifier.
config:

tankONLINE
  da0   ONLINE

TADA! There's the missing drive. So what happened?

if I debug each drive...
bad drive:

# zdb -l /dev/da0

LABEL 0

version=13
name='tank'
state=2
txg=50
pool_guid=12367720188787195607
hostid=2180312168
hostname='proj.bullseye.tv'
top_guid=6830294387039432583
guid=6830294387039432583
vdev_tree
type='disk'
id=0
guid=6830294387039432583
path='/dev/da0'
whole_disk=0
metaslab_array=23
metaslab_shift=36
ashift=9
asize=6998387326976
is_log=0

LABEL 1

version=13
name='tank'
state=2
txg=50
pool_guid=12367720188787195607
hostid=2180312168
hostname='proj.bullseye.tv'
top_guid=6830294387039432583
guid=6830294387039432583
vdev_tree
type='disk'
id=0
guid=6830294387039432583
path='/dev/da0'
whole_disk=0
metaslab_array=23
metaslab_shift=36
ashift=9
asize=6998387326976
is_log=0

LABEL 2

version=13
name='tank'
state=2
txg=50
pool_guid=12367720188787195607
hostid=2180312168
hostname='proj.bullseye.tv'
top_guid=6830294387039432583
guid=6830294387039432583
vdev_tree
type='disk'
id=0
guid=6830294387039432583
path='/dev/da0'
whole_disk=0
metaslab_array=23
metaslab_shift=36
ashift=9
asize=6998387326976
is_log=0

LABEL 3

version=13
name='tank'
state=2
txg=50
pool_guid=12367720188787195607
hostid=2180312168
hostname='proj.bullseye.tv'
top_guid=6830294387039432583
guid=6830294387039432583
vdev_tree
type='disk'
id=0
guid=6830294387039432583
path='/dev/da0'
whole_disk=0
metaslab_array=23
metaslab_shift=36
ashift=9
asize=6998387326976
is_log=0

and good drive:

# zdb -l /dev/da1

LABEL 0

version=13
name='tank'
state=0
txg=4
pool_guid=4433502968625883981
hostid=2180312168
hostname='zproj.bullseye.tv'
top_guid=11718615808151907516
guid=11718615808151907516
vdev_tree
type='disk'
id=1
guid=11718615808151907516
path='/dev/da1'
whole_disk=0
metaslab_array=23
metaslab_shift=36
ashift=9
asize=7001602260992
is_log=0

LABEL 1

version=13
name='tank'
state=0
txg=4
pool_guid=4433502968625883981
hostid=2180312168
hostname='zproj.bullseye.tv'
top_guid=11718615808151907516
guid=11718615808151907516
vdev_tree
type='disk'
id=1
guid=11718615808151907516
path='/dev/da1'
whole_disk=0
metaslab_array=23
metaslab_shift=36
ashift=9
asize=7001602260992
is_log=0

LABEL 2

version=13
name='tank'
state=0
txg=4
pool_guid=4433502968625883981
hostid=2180312168
hostname='zproj.bullseye.tv'
top_guid=11718615808151907516
guid=11718615808151907516
vdev_tree
type='disk'
id=1
guid=11718615808151907516
path='/dev/da1'
whole_disk=0
metaslab

Re: Unable to upgrade packages on FreeBSD

[Eduardo Morras]

At 19:16 01/02/2012, David Jackson wrote:



They seem to have failed because they couldn't find the package on the
download site. Other errors I got were that the package it had downloaded
had an "unrecognized format".

I did not save them, there is really no way to save a copy of them unless I
copy them by hand. I will have to rerun the commands to get the error
messages and then transfer them by hand.


In my first mail i didn't think about this, but:

In your OP you don't say the version of FreeBSD you're running. Show 
a uname -a please. Is it a RELEASE, like 8.2-RELEASEpx? If it's a 
RELEASE perhaps you don't know that the packages are frozen but all 
are known to work  without problems. Switch to -STABLE if you want 
access newer packages but perhaps there will be problems with them 
from time to time. Check -stable maillist.


HTH 



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

Re: Unable to upgrade packages on FreeBSD

[Waitman Gobble]

On Thu, Feb 2, 2012 at 5:18 AM, Bernt Hansson  wrote:

> 2012-02-01 19:16, David Jackson skrev:
>
>
>  I did not save them, there is really no way to save a copy of them unless
>> I
>> copy them by hand.
>>
>
> I take it you are new to FreeBSD. May I introduce you to script
> man script(1)
>
> __**_
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions
> To unsubscribe, send any mail to "freebsd-questions-**
> unsubscr...@freebsd.org "
>


One thing I noticed, which may cause some trouble(?)

http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-10-current/ is
empty, no packages. So pkg_add fails for everything...

Running 10-CURRENT I have to set PACKAGESITE
to http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-current/Latest/

It's been years since I've run a HEAD version of FreeBSD - maybe this is
common knowledge. :)
But It seems like there could be a symlink or something.

Also, I'm still looking into it - but it seems like it would be good to
have an easy way to 'reinstall' a package.
It seems to be pretty stubborn when trying to deinstall/reinstall stuff.
For example, after i upgraded from
9.0-RELEASE to 10-CURRENT, the thing was complaining about libintl,
gettext, iconv.
pkg_add was refusing to 'reinstall' (but this might be related my own
ignorance), so I ended up
going into ports and building, then the system was fulling operational, yay.

However, it could be that these did not need to be "reinstalled". pkg_add
was telling me I already had the
latest versions installed, and when I finally got down to the meat of my
problem I found that my /etc/rc was never replaced.
Either I fat-fingered a mergemaster prompt (but I really thought I was
paying close attention), or mergemaster missed it! :)
There was no /var/tmp/temproot/etc/rc after mergemaster, and mergemaster
reported that only two files were left to do
by hand, which is what I had intended. (ie, groups, master.passwd) But
doing a diff between /usr/src/etc/rc (i think) and /etc/rc I
saw they were different,  copied the file and 10-CURRENT ran perfectly.



Waitman Gobble
San Jose California USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[Bernt Hansson]

2012-02-01 19:16, David Jackson skrev:


I did not save them, there is really no way to save a copy of them unless I
copy them by hand.


I take it you are new to FreeBSD. May I introduce you to script
man script(1)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[David Jackson]

On Tue, Jan 31, 2012 at 12:51 AM, Bernt Hansson  wrote:

> 2012-01-30 18:52, David Jackson skrev:
>
>  I have tried endlessly to no avail to upgrade binary the packages on
>> Freebsd to the latest version. I have tried:
>>
>> *portupgrade -PP -a
>> *portmaster -PP -a
>> *pkg_update
>>
>> All fail miserably and totally and have left the system in an unuseable
>> state.
>>
>
> What is the error message?


They seem to have failed because they couldn't find the package on the
download site. Other errors I got were that the package it had downloaded
had an "unrecognized format".

I did not save them, there is really no way to save a copy of them unless I
copy them by hand. I will have to rerun the commands to get the error
messages and then transfer them by hand.

>
>
>  Why can't FreeBSD just make the package system "just work".
>>
>
> It's already "just works"
>
>
It does for you. I've had big problems with it.


>
>  Right after
>> installing FreeBSD I should be able to type a single command such as
>> update_packages
>>
>
> http://www.se.freebsd.org/doc/**en_US.ISO8859-1/books/**
> handbook/updating-upgrading-**freebsdupdate.html
>
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[David Jackson]

On Tue, Jan 31, 2012 at 12:54 AM, Bernt Hansson  wrote:

> 2012-01-31 01:13, 
> freebsd-lists-erik@**erikosterholm.orgskrev:
>
>  Oh come on, guys. David is the same person who said that FreeBSD was
>> poorly documented.
>>
>> http://osdir.com/ml/freebsd-**questions/2011-12/msg00684.**html
>>
>>  I'll give him the benefit of the doubt a bit longer.
>>
>
> I do not. He is a whino. Blocked here from now on.
>
>
My posts have always been sincere. It would seem to you that anyone who
does not agree with you is whining. I would suggest it is you who have an
unreasonable attitude.


At least respect other people's right to express their views.

__**_
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions
> To unsubscribe, send any mail to "freebsd-questions-**
> unsubscr...@freebsd.org "
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[David Jackson]

On Wed, Feb 1, 2012 at 3:33 AM, Eduardo Morras  wrote:

> At 11:42 31/01/2012, you wrote:
>
>> While your offer is made with the best of intentions, I doubt the
>> project would feel able take you up on it.  The problem is simply one of
>> security -- while crowd-sourcing package compilation would be a pretty
>> sweet technical solution to much of the scaling and resource cost
>> problems, it offers far too much opportunity for people up-to-no-good to
>> be able to introduce trojans, spyware and so forth.
>>
>
> No no, i didn't said i will make them manually, i wanted to said that i
> can add one server amd64 to the pool of automate servers that make the
> packages, i think it works automatically and distribute workload like boinc
> or other similar net. About the people which introduce trojans, rootkits
> etc... i didn't think on that issue and is really a very important stopper.
>
> With the rest of your mail, i agree with you, my idea was completly
> halfthinked (is it the correct word?).
>
>
>
That security issue is a serious problem with that idea. I had thought of
this idea before and discarded it because its unworkable (the crowd
sourcing thing).

> Mental Note to remember: Beside daemons, there are devils.
>
> L
>
> __**_
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions
> To unsubscribe, send any mail to "freebsd-questions-**
> unsubscr...@freebsd.org "
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[Eduardo Morras]

At 11:42 31/01/2012, you wrote:

While your offer is made with the best of intentions, I doubt the
project would feel able take you up on it.  The problem is simply one of
security -- while crowd-sourcing package compilation would be a pretty
sweet technical solution to much of the scaling and resource cost
problems, it offers far too much opportunity for people up-to-no-good to
be able to introduce trojans, spyware and so forth.


No no, i didn't said i will make them manually, i wanted to said that 
i can add one server amd64 to the pool of automate servers that make 
the packages, i think it works automatically and distribute workload 
like boinc or other similar net. About the people which introduce 
trojans, rootkits etc... i didn't think on that issue and is really a 
very important stopper.


With the rest of your mail, i agree with you, my idea was completly 
halfthinked (is it the correct word?).



Mental Note to remember: Beside daemons, there are devils.

L 



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

Re: Unable to upgrade packages on FreeBSD

[Matthew Seaman]

On 31/01/2012 09:56, Eduardo Morras wrote:
> Making a resume/summary of the thread; more hardware, time and people
> are needed to maintain a package system up-to-date. I have a free server
> (amd64 freebsd8.2p6), if i built all packages with their standard
> options, that's without make config, Can i upload them to the official
> package ftp? Should i make my own un-official ftp package server to
> allow others download them?
> 
> Perhaps it's not clear, this answer has ironic mode off, joking mode off
> and i want to collaborate making the standard packages.

While your offer is made with the best of intentions, I doubt the
project would feel able take you up on it.  The problem is simply one of
security -- while crowd-sourcing package compilation would be a pretty
sweet technical solution to much of the scaling and resource cost
problems, it offers far too much opportunity for people up-to-no-good to
be able to introduce trojans, spyware and so forth.

Setting up your own package build system and ftp site -- well, there's
nothing preventing you from doing that, but again, it's a trust thing.
Unless people can believe in the provenance of the packages you provide,
it's not going to be sensible for them to download from you.  So it's
only people that know you personally, friends, relations, workmates and
people that know and trust people willing to trust you; they would be
the initial audience for your new package building and distribution
thing.  Even if you had an enormous social circle all of whom happened
to be avid FreeBSD users, I doubt that would actually provide enough
demand to make the whole venture worthwhile.

The best ways to contribute are (a) to make a donation via the FreeBSD
Foundation and (b) take up maintainership on some ports.  As ever in any
project of this type, most of the work goes through smoothly and it's
that minority of problem ports that eat up so much of the time.
Maintained ports have fewer problems.

Some of the more paranoid amongst you may be asking yourselves if, in
the light of what I say above, you really can trust packages from
anywhere other than the official ftp.freebsd.org server.  Locations like
(for example) ftp.uk.freebsd.org (which, although blessed as an official
mirror site, is run by a completely different set of people.)  The
answer is somewhere on the 'probably -- maybe' continuum.   Can you
actually trust the people running the mirror site?  (In the case of
ftp.uk.freebsd.org, as of a day or so ago that's the UK mirror service
run by the University of Kent who are clearly of unimpeachable
reputation.)  Implementing digital signatures on packages would go a
long way to removing that uncertainty.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: Unable to upgrade packages on FreeBSD

[Eduardo Morras]

At 00:45 31/01/2012, RW wrote:


Making it work like Ubuntu would need a lot more hardware and a lot
more work from port maintainers to support branching the ports tree. At
the moment there aren't really enough to maintain one tree.


Making a resume/summary of the thread; more hardware, time and people 
are needed to maintain a package system up-to-date. I have a free 
server (amd64 freebsd8.2p6), if i built all packages with their 
standard options, that's without make config, Can i upload them to 
the official package ftp? Should i make my own un-official ftp 
package server to allow others download them?


Perhaps it's not clear, this answer has ironic mode off, joking mode 
off and i want to collaborate making the standard packages.


When i needed the package system? When i don't want a downtime if a 
server must be reinstalled. Compiling everything takes too much time 
for non critical ports (bash, gcc4.6, ...), even at first i pkg_add 
important apps, when everything is working, i update them by ports.


L


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

Re: Unable to upgrade packages on FreeBSD

[Chad Perrin]

On Tue, Jan 31, 2012 at 01:52:19AM +0100, Polytropon wrote:
> On Mon, 30 Jan 2012 18:40:50 -0500, David Jackson wrote:
> > On Mon, Jan 30, 2012 at 5:49 PM, Polytropon wrote:
> > >
> > > Other things to keep in mind are language settings. One example is
> > > OpenOffice which needs to have the language setting at compile
> > > time, especially if you're not using the english language.
> >
> > You could compile a version of that for each language and I think
> > thats what Ubuntu does, or, just compile maybe top 1 or 2 most
> > commonly used language version and then other versions could be user
> > compiled.
> 
> There are, I think... at least 10 languages available, and combine this
> with Gnome, KDE and CUPS support OFF or ON, and you have 10*2*2*2 = 80
> packages, and still no scheme to name them. :-)

Don't forget compiling for multiple architectures.  That adds more
options -- and, unlike some of those other options, compiling for
different architectures is often actually a mutually-exclusive option
set.

-- 
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[Greg Groth]

On 1/30/2012 6:13 PM, freebsd-lists-e...@erikosterholm.org wrote:

On Mon, Jan 30, 2012 at 03:28:28PM -0700, Chad Perrin wrote:

You talk a lot about how easy it is to maintain a binary package system.
I would like you to convince me that it is easy, keeping in mind that it
should remain compatible with the ports system.  I am willing to be
convinced.

--
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]


Oh come on, guys. David is the same person who said that FreeBSD was
poorly documented.

http://osdir.com/ml/freebsd-questions/2011-12/msg00684.html

I really hate throwing around the 'T' word, but I'm starting to
wonder.  I'll give him the benefit of the doubt a bit longer.

David, it's increasingly clear that FreeBSD is not going to fit your
needs. If, for some reason, you are interested in the FreeBSD kernel,
but binary packages, consider GNU/kFreeBSD.


I'm finding this conversation very amusing.  After playing with I don't 
know how many Linux distributions since the mid-90's, and running into 
the same problem of things breaking after updating binary packages, I 
moved to FreeBSD around 5.0 for my web server.  Since that time, I've 
forced to do one reinstall due to a hardware failure, somewhere around 
7.0.  I am now running 8.2.  After going through I can't remember how 
many upgrades and updates, I've only had a couple of minor issues over 
the years (most were resolved after reading Updating after the fact ;-) 
).  I'll give up the time savings of binary packages vs. the 
dependability of compiling stuff myself any day.


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

Re: Unable to upgrade packages on FreeBSD

[Polytropon]

On Mon, 30 Jan 2012 18:40:50 -0500, David Jackson wrote:
> On Mon, Jan 30, 2012 at 5:49 PM, Polytropon  wrote:
> 
> > On Mon, 30 Jan 2012 17:04:56 -0500, David Jackson wrote:
> > > I wish to use binary packages and I specifically do not want to compile
> > > anything, it tends to take far too long to compile programs and would
> > > rather install some packages and have it all work right away.
> >
> > That's often true, especially when you're low on resources
> > (CPU speed, disk, RAM).
> >
> >
> >
> > > Binary
> > > packages are a big time saver and are more efficient.
> >
> > More efficient? Depends. In regards of installation, they're
> > often faster. In regards of spped during operation... well,
> > depends. :-)
> >
> > The binary packages are compiled from the ports sources with
> > the maintainer's default options. Those options might not
> > perform optimal on _every_ imaginable system. That's why
> > compiling from source can make programs run faster when
> > certain optimizations (e. g. specific CFLAGS, selection
> > of CPU at compile time) are applied. Also functionality
> > may increase as the default options may leave something
> > out.
> >
> > A common example is mplayer: When compiled, it can have
> > much more functionality and can even work wonders on old
> > systems. The binary package doesn't give you that.
> >
> That is true. Well, unless is a problem with cross CPU compatability, all
> available options should be compiled in by default. Mplayer (or it was some
> video players) has a huge number of display targets for instance, they can
> be runtime selected so support for all of them can be compiled in  my
> default and the user can then select which one to use at runtime. I have
> used video player where you can choose between OpenGL, plain X11, Xvideo,
> and many other display options and I actually liked having these kinds of
> runtime choices.

It's not just the output drivers, it's also the codecs.
There's a sheer plethora of them, and there are basically
three kinds of users:

a) I only install the codecs where I have the corresponding
   files to play; I don't want any other codecs.

b) I want all the codecs, so no matter what file I get, I can
   play it without further installation.

c) I'm frightened because I live in a country where playing
   MP3 is forbidden by law, so I better not install anything
   that could make my elected government suspicious and send
   me a federal trojan. :-)

Okay, two kinds of users.

In addition to the codecs, there's another thing that mplayer
can be selected upon compile time: if to include mencoder.
Further stuff includes gmplayer and gmencoder and the skins
for those programs.

Regarding CPU feature use, it seems that WITHOUT_RUNTIME_CPUDETECTION
(or what the option was called like) in combination with
over-optimized CFLAGS and CPUTYPE create a faster binary,
especially on older systems.



> A package for these programs can be provided and if a user needs a compile
> time option they can then spot compile them as needed.

The default options (which the maintainer chooses) do not
meet any of the two kinds of users mentioned above. In
fact, I would call the default mplayer "partially optimal"
because it's not the "full thing" and also not the "minimal
thing".



> > Other things to keep in mind are language settings. One
> > example is OpenOffice which needs to have the language
> > setting at compile time, especially if you're not using
> > the english language.
> >
> >
> You could compile a version of that for each language and I think thats
> what Ubuntu does, or, just compile maybe top 1 or 2 most commonly used
> language version and then other versions could be user compiled.

There are, I think... at least 10 languages available, and
combine this with Gnome, KDE and CUPS support OFF or ON,
and you have 10*2*2*2 = 80 packages, and still no scheme
to name them. :-)



> > Finally, there may be licensing restrictions that forbid
> > the distribution in binary form, or even the distribution
> > through the FreeBSD system. Traditional Java may be seen
> > as an example.
> >
> >
> This is rare, but it happens. Most programs dont have this problem. a few
> programs must be compiled like this, it is a lot easier to compile that
> handful of programs for me than it is to compile the entire system.

I fully agree. If I remember correctly, mpg123 has been such
a program, but compiling that is nothing compared to KDE. And
with the shrinking importance of Java... :-)



> > > It should be easy for
> > > FreeBSD to make it easy to install the most recent versions of all binary
> > > packages, its beyond belief they cannot pull off such a simple ans
> > straight
> > > forward, and basic part of any OS.
> >
> > Again, it depends. The options maintainers define as the
> > default are typically okay for the build clusters that
> > process them - they create the binary packages from the
> > ports tree. At some occassions, options and dependencies
> > ca

Re: Unable to upgrade packages on FreeBSD

[freebsd-lists-erik]

On Mon, Jan 30, 2012 at 03:28:28PM -0700, Chad Perrin wrote:
> You talk a lot about how easy it is to maintain a binary package system.
> I would like you to convince me that it is easy, keeping in mind that it
> should remain compatible with the ports system.  I am willing to be
> convinced.
> 
> -- 
> Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]


Oh come on, guys. David is the same person who said that FreeBSD was
poorly documented.

http://osdir.com/ml/freebsd-questions/2011-12/msg00684.html

I really hate throwing around the 'T' word, but I'm starting to
wonder.  I'll give him the benefit of the doubt a bit longer.

David, it's increasingly clear that FreeBSD is not going to fit your
needs. If, for some reason, you are interested in the FreeBSD kernel,
but binary packages, consider GNU/kFreeBSD.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[Roland Smith]

On Mon, Jan 30, 2012 at 11:49:46PM +0100, Polytropon wrote:
> > Binary
> > packages are a big time saver and are more efficient.
> 
> More efficient? Depends. In regards of installation, they're
> often faster. In regards of spped during operation... well,
> depends. :-)
> 
> The binary packages are compiled from the ports sources with
> the maintainer's default options. Those options might not
> perform optimal on _every_ imaginable system. 

The defaults may also pull in a lot of stuff that you don't need. E.g, the
math/gnuplot port pulls in pdflib, teTeX and wxWidgets (among other things)!
That is quite heavy for a program for making graphs. 

Pdflib is restricted, and gnuplot has a perfectly working pdf output
when the cairo library is used (which is also the default). It also has X11
output without wxWidgets, and TeX support is only really interesting for TeX
users. That's not to criticize the maintainer, who presumably had good reason
to choose these defaults, but to illustrate a problem.

> Just consider X: With or without HAL? With which drivers?

Without! ;-)

> > The reason that FreeBSD has a smaller user base is because it has a
> > dysfunctional package system and it is hard to upgrade package to the most
> > recent version, making FreeBSD more difficult to use/

I doubt that is the main reason. Maybe for novice desktop users, but those
don't seem to be the majority or even a large part of the userbase.

> I do not agree with this statement. The user base of FreeBSD
> consists of a major amount of people who do not use the
> binary packages, as it seems, because ports work well for
> them.

Agreed.

> > But doing a workable package system is not difficult, it something that
> > FreeBSD should be easily able to make it easy to have a way to upgrade
> > packages to most recent versions out of box anbd in an error free and
> > reliable way.

There is a saying in engineering that everything is easy for the person who
doesn't have to do it.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpY06zzS5rDU.pgp
Description: PGP signature

Re: Unable to upgrade packages on FreeBSD

[Steve Bertrand]

On 2012.01.30 18:40, David Jackson wrote:


Perhaps that is because the people who want to use packages have given up
on FreeBSD.


WTF?!? hint: I'm standing right beside you as you're saying this.

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

Re: Unable to upgrade packages on FreeBSD

[Matthew Seaman]

On 30/01/2012 22:04, David Jackson wrote:
> Binary packages are a big time saver and are more efficient.

Yes, definitely -- this is true for many use cases.  Not all by any
means, but enough that binary packages are a must-have.

> It should be easy for FreeBSD to make it easy to install the most
> recent versions of all binary packages, its beyond belief they cannot
> pull off such a simple ans straight forward, and basic part of any
> OS.

Now this I dispute absolutely.  Whatever gave you the idea that
generating and maintaining an archive of binary packages was at all
"simple and straight forward?"  It is most emphatically neither of those
things.

Firstly there's a matter of the scale of the job -- the ports contains
around 23,000 different software packages.  That's pretty respectable
compared to most Linux distributions, remembering that there are several
hundred packages' worth of stuff in the base system which would have to
be packaged in a comparable Linux system.  Most of those software
packages are under active development, and virtually none of them are
prepared to alter their release schedules one iota to suit FreeBSD.
Just keeping that collection current is a huge task, let alone trying to
maintain and improve the system used to do it.

Then there's the small matter of compiling all that software to produce
the binary packages.  At the moment there are 3 different major OS
versions supported across two Tier-1 architectures (i386, amd64 --
everything is expected to work on Tier-1) and four Tier-2 architectures
(ia64, sparc64, powerpc, pc98 -- which should be supported for package
building, but only on a 'best efforts' basis) plus maybe 3 or 4 other
experimental architectures like arm and mips which have the potential to
become very important in the future as they are the basis of a lot of
embedded computing devices.  And people have the temerity to complain if
updates aren't available online within a few days!

To support all that takes some pretty impressive computing power spread
over three different data centers (I believe), all of which has been
*donated* to the FreeBSD project, and all of the power, cooling,
bandwidth, maintenance and other ongoing hosting costs are similarly
supplied by donation.  Not to mention a hard-core of about 20 key ports
committers, plus maybe a hundred-odd other committers taking a more
peripheral role, and some 4,000 other volunteers that do the work of
maintaining everything.

All of this elides one of the insanely great features of the ports --
which is how configurable and adaptable they are.  The trouble is, the
design of the ports really does work best for compiling from source.
There is functionality there which is somewhere between "incredibly
difficult" and "simply impossible" to push up to a set of pre-compiled
binary packages.  (Which, by the way, is a feature common to all binary
packaging systems: you always get whatever someone else thought was a
good idea at the time.)

The ports really are one of FreeBSD's crown jewels, and as a system for
compiling software from source and installing and maintaining the
results it has few peers.  It is certainly true that FreeBSD's binary
package management could be better.  Binary package management under
FreeBSD has always been seen as bit of a second choice compared to
ports, and consequently it has not had the same sort of development
effort put into it.  Until recently, that is.  We have literally just
had the announcement of the beta test version of the new next-generation
binary packaging system on the freebsd-ports@... list earlier today.
Don't get too excited though -- it will be months at the very least
before pkgng goes into anything like production.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: Unable to upgrade packages on FreeBSD

[Bas Smeelen]

On Tue, 31 Jan 2012 00:02:44 +0100
Bas Smeelen  wrote:

> On Mon, 30 Jan 2012 17:04:56 -0500
> David Jackson  wrote:

To put it bluntly

It's the users fault
from my own experience

Apple: just fsck off
Mcrsft and Oracle and whom they have swallowed so far: just pay enough
bucks, it's still your fault wait for the next update
Ubuntu: just be rude on the mail-lists, wait for the next update or get
involved
FreeBSD: you could have known, RTFM! or get involved it's just as easy
with the FM

Netherlands: Bowmore Islay and others others are fore sale this week :)

Damn laptop is still compiling
Would be nice if there were stills compiling something else

Cheers


Disclaimer: http://www.ose.nl/email

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

Re: Unable to upgrade packages on FreeBSD

[RW]

On Mon, 30 Jan 2012 12:52:07 -0500
David Jackson wrote:

> I have tried endlessly to no avail to upgrade binary the packages on
> Freebsd to the latest version. I have tried:
> 
> *portupgrade -PP -a
> *portmaster -PP -a
> *pkg_update
> 
> All fail miserably and totally and have left the system in an
> unuseable state.

For the benefit of new readers David's question tend to take the form:

   I'm doing this the hard way, I'm refusing to compromise, 
   and yet it still isn't working.

I updated from ports yesterday and it did "just work". If you dropped
at least one of the -P flags, you should have less trouble.

If you need binary packages for a production server, then build your
own.

> Why can't FreeBSD just make the package system "just work". Right
> after installing FreeBSD I should be able to type a single command
> such as update_packages and it should update all packages on the
> system,

Why would you need to update packages after a fresh install? It's
better not to install any stale packages in the first place.


> Why not? Why is something so simple so difficult and impossible?
> Ubuntu can do it, why not FreeBSD?

Ubuntu does pretty much nothing but build packages from third-party
software that's either portable or Linux-centric. A lot of it is
inherited from Debian, it has a comparatively huge user-base, and
financial backing from a commercial company. 

 
> Why cant FreeBSD  Just make the package upgrades work.

You aren't telling us anything new here, *prebuilt* binary package are
a second-class way of updating on FreeBSD. Packages pretty much have
to be built for current and stable development branches for testing
purposes. They are built against a constantly changing ports tree with
variable lag which isn't ideal. 

Making it work like Ubuntu would need a lot more hardware and a lot
more work from port maintainers to support branching the ports tree. At
the moment there aren't really enough to maintain one tree.


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

Re: Unable to upgrade packages on FreeBSD

[David Jackson]

On Mon, Jan 30, 2012 at 5:49 PM, Polytropon  wrote:

> On Mon, 30 Jan 2012 17:04:56 -0500, David Jackson wrote:
> > I wish to use binary packages and I specifically do not want to compile
> > anything, it tends to take far too long to compile programs and would
> > rather install some packages and have it all work right away.
>
> That's often true, especially when you're low on resources
> (CPU speed, disk, RAM).
>
>
>
> > Binary
> > packages are a big time saver and are more efficient.
>
> More efficient? Depends. In regards of installation, they're
> often faster. In regards of spped during operation... well,
> depends. :-)
>
> The binary packages are compiled from the ports sources with
> the maintainer's default options. Those options might not
> perform optimal on _every_ imaginable system. That's why
> compiling from source can make programs run faster when
> certain optimizations (e. g. specific CFLAGS, selection
> of CPU at compile time) are applied. Also functionality
> may increase as the default options may leave something
> out.
>
> A common example is mplayer: When compiled, it can have
> much more functionality and can even work wonders on old
> systems. The binary package doesn't give you that.
>
> That is true. Well, unless is a problem with cross CPU compatability, all
available options should be compiled in by default. Mplayer (or it was some
video players) has a huge number of display targets for instance, they can
be runtime selected so support for all of them can be compiled in  my
default and the user can then select which one to use at runtime. I have
used video player where you can choose between OpenGL, plain X11, Xvideo,
and many other display options and I actually liked having these kinds of
runtime choices.

A package for these programs can be provided and if a user needs a compile
time option they can then spot compile them as needed.


> Other things to keep in mind are language settings. One
> example is OpenOffice which needs to have the language
> setting at compile time, especially if you're not using
> the english language.
>
>
You could compile a version of that for each language and I think thats
what Ubuntu does, or, just compile maybe top 1 or 2 most commonly used
language version and then other versions could be user compiled.


> Finally, there may be licensing restrictions that forbid
> the distribution in binary form, or even the distribution
> through the FreeBSD system. Traditional Java may be seen
> as an example.
>
>
> This is rare, but it happens. Most programs dont have this problem. a few
programs must be compiled like this, it is a lot easier to compile that
handful of programs for me than it is to compile the entire system.


>
> > It should be easy for
> > FreeBSD to make it easy to install the most recent versions of all binary
> > packages, its beyond belief they cannot pull off such a simple ans
> straight
> > forward, and basic part of any OS.
>
> Again, it depends. The options maintainers define as the
> default are typically okay for the build clusters that
> process them - they create the binary packages from the
> ports tree. At some occassions, options and dependencies
> can take into account things that are already installed,
> e. g. "foo" uses "bar" if "bar" is installed, but if it's
> not installed, it fetches and installs "baz" instead.
>
> Just imagine how many packages you would need to map all
> possible combinations of dependencies present, options set
> and languages available, and _then_ come up with a naming
> scheme for the packages. :-)
>
>
Just compile package for the package download site with all optionals and
functionality available. If it has optional dependancies, just install all
of the dependancies when the package that needs them is installed. Then
user can has all features avialable at runtime.

If its an one or the other type option, compile with the most commonly used
setting.

In many cases they use run time options in programs so this is not as much
of an issue in those cases.

if people want to make their own compile time options then they can resort
to compiling the package themselves.


I know it is _partially_ possible, or _has been_ in the
> past. My famous example here is "pkg_add -r de-openoffice"
> to get a full installation of OpenOffice that would work
> (fully functional) and even bring a dictionary. With the
> newer versions, this easy approach isn't possible anymore.
>
> Just consider X: With or without HAL? With which drivers?
> A package plus updates for every possible combination?
>
>
> Probably throw in all options at compile time for packages, such as HAL,
and then it will be available if people need to use it. If people dont want
a component, then they compile on their own.  As far as dependancies, the
program can be compiled to rely on them and they would be installed
automatically when  the depending application  is installed.

Im not sure what HAL does but Ive installed it for X Window System, if

Re: Unable to upgrade packages on FreeBSD

[Bas Smeelen]

On Mon, 30 Jan 2012 17:04:56 -0500
David Jackson  wrote:


> On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelen  wrote:
>   
> > On Mon, 30 Jan 2012 12:52:07 -0500
> > David Jackson  wrote:
> >  
> > > I have tried endlessly to no avail to upgrade binary the packages
> > > on Freebsd to the latest version. I have tried:
> > >
> > > *portupgrade -PP -a
> > > *portmaster -PP -a
> > > *pkg_update
> > >
> > > All fail miserably and totally and have left the system in an
> > > unuseable state.  
> >
> > What's unusable? For instance, servers are perfectly usable without
> > graphical tools. If you have tried `endlessly` why didn't you
> > consult /usr/ports/UPDATING and just recompile the ports without
> > using binary packages?
> > Or you might want to try PCBSD, it's FreeBSD with some fancy stuff
> > taken care of which might solve the problem you complain about.  
> > >  
> >  
> 
> 
> I wish to use binary packages and I specifically do not want to
> compile anything, it tends to take far too long to compile programs
> and would rather install some packages and have it all work right
> away. Binary packages are a big time saver and are more efficient. It
> should be easy for FreeBSD to make it easy to install the most recent
> versions of all binary packages, its beyond belief they cannot pull
> off such a simple ans straight forward, and basic part of any OS.  

I understand your motivations. 
On my 1,6GHz celeron it takes a lot of time to compile the ~600 ports I
use, especially chromium for instance and when I forget to give an
option to not bother me with questions it sits there waiting for me to
enter y or n.
Ports/ packages are not `a basic part` of the FreeBSD OS. I also don't
think it is simple and straight forward to satisfy all different user
requirements and options in a package system. Ubuntu for my taste has
had flukes in many ways many times in the past and still has (often
enough the developers desktop users complain). It works good with
complete upgrades at times, on the other hand it still leaves me
sometimes with an unusable freezing OS on the desktop, and before every
upgrade it has becomes mandatory to me to first try it with an USB boot.
This is something I cannot have on server systems being used 24x7.

> 
>   
> > > Why can't FreeBSD just make the package system "just work". Right
> > > after installing FreeBSD I should be able to type a single command
> > > such as update_packages and it should update all packages on the
> > > system, with no errors and without requiring any configurations
> > > to be troubleshooted, it should work out of the box.
> > >
> > > Why not? Why is something so simple so difficult and impossible?
> > > Ubuntu can do it, why not FreeBSD?  
> >
> > FreeBSD unlike Ubuntu is an entirely volunteer project. Ubuntu has
> > a dedicated corporation working on it and I guess a larger user
> > base.
> >  
> 
> The reason that FreeBSD has a smaller user base is because it has a
> dysfunctional package system and it is hard to upgrade package to the
> most recent version, making FreeBSD more difficult to use/
> 
> But doing a workable package system is not difficult, it something
> that FreeBSD should be easily able to make it easy to have a way to
> upgrade packages to most recent versions out of box anbd in an error
> free and reliable way.
> 
>   
> > >
> > > Why cant FreeBSD  Just make the package upgrades work.  
> >
> > Because uh well it's not up to FreeBSD since the ports work
> > perfectly with the documentation that comes with it or it might
> > depend on the user base also, but _you_ can help to make binary
> > package upgrades work better.
> >
> >
> > A working package system is a part of any good operating system and
> > saves  
> time from having to compile programs. It is more convenient for most
> users to use packages so having a package system will make FreeBSD
> more popular. the reason freebsd is not used by as many people as
> Ubuntu is because of the extreme difficulty and unreliability of
> using FreeBSD.  

Well, if you are talking about desktop work places, you're
probably right. This is what PCBSD is for, or even Ubuntu or other
'Operating Systems'
On servers however FreeBSD is extremely reliable. It requires the
operator to take care of the system, OS updates and upgrades are rock
solid for decades and application (ports/ packages) updates/
upgrades require the operator to evaluate the changes in detail. I have
had a lot of trouble by the ease of upgrade/ update on other 'OS'
applications which I did not encounter on FreeBSD because FreeBSD
required me to think about what I was doing and then it
goes well the first time.

> 
> FreeBSD does not HAVE to make the system reasonably easy to use for
> common users who want to install packages, but it would be the right
> thing to do, especially if FreeBSD wants more users.  

Again PCBSD might be an option.
It depends on what kind of users. Users who think and can rely on a
rock solid OS or users who just 

Re: Unable to upgrade packages on FreeBSD

[Bas Smeelen]

On Mon, 30 Jan 2012 17:04:56 -0500
David Jackson  wrote:

> On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelen  wrote:
> 
> > On Mon, 30 Jan 2012 12:52:07 -0500
> > David Jackson  wrote:
> >
> > > I have tried endlessly to no avail to upgrade binary the packages
> > > on Freebsd to the latest version. I have tried:
> > >
> > > *portupgrade -PP -a
> > > *portmaster -PP -a
> > > *pkg_update
> > >
> > > All fail miserably and totally and have left the system in an
> > > unuseable state.
> >
> > What's unusable? For instance, servers are perfectly usable without
> > graphical tools. If you have tried `endlessly` why didn't you
> > consult /usr/ports/UPDATING and just recompile the ports without
> > using binary packages?
> > Or you might want to try PCBSD, it's FreeBSD with some fancy stuff
> > taken care of which might solve the problem you complain about.
> > >
> >
> 
> 
> I wish to use binary packages and I specifically do not want to
> compile anything, it tends to take far too long to compile programs
> and would rather install some packages and have it all work right
> away. Binary packages are a big time saver and are more efficient. It
> should be easy for FreeBSD to make it easy to install the most recent
> versions of all binary packages, its beyond belief they cannot pull
> off such a simple ans straight forward, and basic part of any OS.

I understand your motivations. 
On my 1,6GHz celeron it takes a lot of time to compile the ~600 ports I
use, especially chromium for instance and when I forget to give an
option to not bother me with questions it sits there waiting for me to
enter y or n.
Ports/ packages are not `a basic part` of the FreeBSD OS. I also don't
think it is simple and straight forward to satisfy all different user
requirements and options in a package system. Ubuntu for my taste has
had flukes in many ways many times in the past and still has (often
enough the developers desktop users complain). It works good with
complete upgrades at times, on the other hand it still leaves me
sometimes with an unusable freezing OS on the desktop, and before every
upgrade it has becomes mandatory to me to first try it with an USB boot.
This is something I cannot have on server systems being used 24x7.

> 
> 
> > > Why can't FreeBSD just make the package system "just work". Right
> > > after installing FreeBSD I should be able to type a single command
> > > such as update_packages and it should update all packages on the
> > > system, with no errors and without requiring any configurations
> > > to be troubleshooted, it should work out of the box.
> > >
> > > Why not? Why is something so simple so difficult and impossible?
> > > Ubuntu can do it, why not FreeBSD?
> >
> > FreeBSD unlike Ubuntu is an entirely volunteer project. Ubuntu has
> > a dedicated corporation working on it and I guess a larger user
> > base.
> >
> 
> The reason that FreeBSD has a smaller user base is because it has a
> dysfunctional package system and it is hard to upgrade package to the
> most recent version, making FreeBSD more difficult to use/
> 
> But doing a workable package system is not difficult, it something
> that FreeBSD should be easily able to make it easy to have a way to
> upgrade packages to most recent versions out of box anbd in an error
> free and reliable way.
> 
> 
> > >
> > > Why cant FreeBSD  Just make the package upgrades work.
> >
> > Because uh well it's not up to FreeBSD since the ports work
> > perfectly with the documentation that comes with it or it might
> > depend on the user base also, but _you_ can help to make binary
> > package upgrades work better.
> >
> >
> > A working package system is a part of any good operating system and
> > saves
> time from having to compile programs. It is more convenient for most
> users to use packages so having a package system will make FreeBSD
> more popular. the reason freebsd is not used by as many people as
> Ubuntu is because of the extreme difficulty and unreliability of
> using FreeBSD.

Well, if you are talking about desktop work places, you're
probably right. This is what PCBSD is for, or even Ubuntu or other
'Operating Systems'
On servers however FreeBSD is extremely reliable. It requires the
operator to take care of the system, OS updates and upgrades are rock
solid for decades and application (ports/ packages) updates/
upgrades require the operator to evaluate the changes in detail. I have
had a lot of trouble by the ease of upgrade/ update on other 'OS'
applications which I did not encounter on FreeBSD because FreeBSD
required me to think about what I was doing and then it
goes well the first time.

> 
> FreeBSD does not HAVE to make the system reasonably easy to use for
> common users who want to install packages, but it would be the right
> thing to do, especially if FreeBSD wants more users.

Again PCBSD might be an option.
It depends on what kind of users. Users who think and can rely on a
rock solid OS or users who just upgrade/ update and then sit wi

Re: Unable to upgrade packages on FreeBSD

[Polytropon]

On Mon, 30 Jan 2012 17:04:56 -0500, David Jackson wrote:
> I wish to use binary packages and I specifically do not want to compile
> anything, it tends to take far too long to compile programs and would
> rather install some packages and have it all work right away.

That's often true, especially when you're low on resources
(CPU speed, disk, RAM).



> Binary
> packages are a big time saver and are more efficient.

More efficient? Depends. In regards of installation, they're
often faster. In regards of spped during operation... well,
depends. :-)

The binary packages are compiled from the ports sources with
the maintainer's default options. Those options might not
perform optimal on _every_ imaginable system. That's why
compiling from source can make programs run faster when
certain optimizations (e. g. specific CFLAGS, selection
of CPU at compile time) are applied. Also functionality
may increase as the default options may leave something
out.

A common example is mplayer: When compiled, it can have
much more functionality and can even work wonders on old
systems. The binary package doesn't give you that.

Other things to keep in mind are language settings. One
example is OpenOffice which needs to have the language
setting at compile time, especially if you're not using
the english language.

Finally, there may be licensing restrictions that forbid
the distribution in binary form, or even the distribution
through the FreeBSD system. Traditional Java may be seen
as an example.



> It should be easy for
> FreeBSD to make it easy to install the most recent versions of all binary
> packages, its beyond belief they cannot pull off such a simple ans straight
> forward, and basic part of any OS.

Again, it depends. The options maintainers define as the
default are typically okay for the build clusters that
process them - they create the binary packages from the
ports tree. At some occassions, options and dependencies
can take into account things that are already installed,
e. g. "foo" uses "bar" if "bar" is installed, but if it's
not installed, it fetches and installs "baz" instead.

Just imagine how many packages you would need to map all
possible combinations of dependencies present, options set
and languages available, and _then_ come up with a naming
scheme for the packages. :-)

I know it is _partially_ possible, or _has been_ in the
past. My famous example here is "pkg_add -r de-openoffice"
to get a full installation of OpenOffice that would work
(fully functional) and even bring a dictionary. With the
newer versions, this easy approach isn't possible anymore.

Just consider X: With or without HAL? With which drivers?
A package plus updates for every possible combination?



> The reason that FreeBSD has a smaller user base is because it has a
> dysfunctional package system and it is hard to upgrade package to the most
> recent version, making FreeBSD more difficult to use/

I do not agree with this statement. The user base of FreeBSD
consists of a major amount of people who do not use the
binary packages, as it seems, because ports work well for
them.

Of course I do not negate the value of the availability of
precompiled packages. In fact, I did use them a lot, but now
that I have sufficient power at home, I feel more comfortable
with building from source. However, I do like the concept of
doing "pkg_add -r " that will install the program
itself and the dependencies if needed, especially for things
that do not need any further tuning.



> But doing a workable package system is not difficult, it something that
> FreeBSD should be easily able to make it easy to have a way to upgrade
> packages to most recent versions out of box anbd in an error free and
> reliable way.

I have named some examples that show how difficult it can get.
That is only for installation. If you consider updating, things
may get a bit more complicated.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[Chad Perrin]

You talk a lot about how easy it is to maintain a binary package system.
I would like you to convince me that it is easy, keeping in mind that it
should remain compatible with the ports system.  I am willing to be
convinced.

-- 
Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[David Jackson]

On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelen  wrote:

> On Mon, 30 Jan 2012 12:52:07 -0500
> David Jackson  wrote:
>
> > I have tried endlessly to no avail to upgrade binary the packages on
> > Freebsd to the latest version. I have tried:
> >
> > *portupgrade -PP -a
> > *portmaster -PP -a
> > *pkg_update
> >
> > All fail miserably and totally and have left the system in an
> > unuseable state.
>
> What's unusable? For instance, servers are perfectly usable without
> graphical tools. If you have tried `endlessly` why didn't you
> consult /usr/ports/UPDATING and just recompile the ports without
> using binary packages?
> Or you might want to try PCBSD, it's FreeBSD with some fancy stuff
> taken care of which might solve the problem you complain about.
> >
>


I wish to use binary packages and I specifically do not want to compile
anything, it tends to take far too long to compile programs and would
rather install some packages and have it all work right away. Binary
packages are a big time saver and are more efficient. It should be easy for
FreeBSD to make it easy to install the most recent versions of all binary
packages, its beyond belief they cannot pull off such a simple ans straight
forward, and basic part of any OS.


> > Why can't FreeBSD just make the package system "just work". Right
> > after installing FreeBSD I should be able to type a single command
> > such as update_packages and it should update all packages on the
> > system, with no errors and without requiring any configurations to be
> > troubleshooted, it should work out of the box.
> >
> > Why not? Why is something so simple so difficult and impossible?
> > Ubuntu can do it, why not FreeBSD?
>
> FreeBSD unlike Ubuntu is an entirely volunteer project. Ubuntu has
> a dedicated corporation working on it and I guess a larger user base.
>

The reason that FreeBSD has a smaller user base is because it has a
dysfunctional package system and it is hard to upgrade package to the most
recent version, making FreeBSD more difficult to use/

But doing a workable package system is not difficult, it something that
FreeBSD should be easily able to make it easy to have a way to upgrade
packages to most recent versions out of box anbd in an error free and
reliable way.


> >
> > Why cant FreeBSD  Just make the package upgrades work.
>
> Because uh well it's not up to FreeBSD since the ports work perfectly
> with the documentation that comes with it or it might depend on the user
> base also, but _you_ can help to make binary package upgrades work
> better.
>
>
> A working package system is a part of any good operating system and saves
time from having to compile programs. It is more convenient for most users
to use packages so having a package system will make FreeBSD more popular.
the reason freebsd is not used by as many people as Ubuntu is because of
the extreme difficulty and unreliability of using FreeBSD.

FreeBSD does not HAVE to make the system reasonably easy to use for common
users who want to install packages, but it would be the right thing to do,
especially if FreeBSD wants more users.



>
> Disclaimer: http://www.ose.nl/email
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscr...@freebsd.org"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to upgrade packages on FreeBSD

[Bas Smeelen]

On Mon, 30 Jan 2012 12:52:07 -0500
David Jackson  wrote:

> I have tried endlessly to no avail to upgrade binary the packages on
> Freebsd to the latest version. I have tried:
> 
> *portupgrade -PP -a
> *portmaster -PP -a
> *pkg_update
> 
> All fail miserably and totally and have left the system in an
> unuseable state.

What's unusable? For instance, servers are perfectly usable without
graphical tools. If you have tried `endlessly` why didn't you
consult /usr/ports/UPDATING and just recompile the ports without
using binary packages?
Or you might want to try PCBSD, it's FreeBSD with some fancy stuff
taken care of which might solve the problem you complain about. 
> 
> Why can't FreeBSD just make the package system "just work". Right
> after installing FreeBSD I should be able to type a single command
> such as update_packages and it should update all packages on the
> system, with no errors and without requiring any configurations to be
> troubleshooted, it should work out of the box.
> 
> Why not? Why is something so simple so difficult and impossible?
> Ubuntu can do it, why not FreeBSD?

FreeBSD unlike Ubuntu is an entirely volunteer project. Ubuntu has
a dedicated corporation working on it and I guess a larger user base.
> 
> Why cant FreeBSD  Just make the package upgrades work.

Because uh well it's not up to FreeBSD since the ports work perfectly
with the documentation that comes with it or it might depend on the user
base also, but _you_ can help to make binary package upgrades work
better.


Disclaimer: http://www.ose.nl/email

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

Unable to upgrade packages on FreeBSD

[David Jackson]

I have tried endlessly to no avail to upgrade binary the packages on
Freebsd to the latest version. I have tried:

*portupgrade -PP -a
*portmaster -PP -a
*pkg_update

All fail miserably and totally and have left the system in an unuseable
state.

Why can't FreeBSD just make the package system "just work". Right after
installing FreeBSD I should be able to type a single command such as
update_packages and it should update all packages on the system, with no
errors and without requiring any configurations to be troubleshooted, it
should work out of the box.

Why not? Why is something so simple so difficult and impossible? Ubuntu can
do it, why not FreeBSD?

Why cant FreeBSD  Just make the package upgrades work.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD 9.0 ICH8M trouble, no HDD found, unable to install.

[Jasper Valentijn]

Mike wrote:
> I do not have this hardware, so these are just a couple of wild guessses
> from the blue on my part.  I am also looking only at 64 bit platforms here,
> so if there is any signifigant difference with 32 bit I can't look/see.

Just to be on the safe side I've also tried the 9.0 amd64 image. Same
results though.

> First, you might try using the "2" option on the boot menu and then 'load 
> acpi_sony' followed by 'boot'.

No change here, on both i386 and amd64.

> You may try disabling AHCI by switching to Legacy IDE mode and see what
> changes. If it works when you do this it confirms this to be where the > 
> problem lies.
> Also ensure you are not using any BIOS config for AHCI+RAID.

Sony has completely stripped the bios, no options to set here.

> You may be able to play around a little using the loader (press "2") to set 
> and unset various variables.
> For example, hint.ahci.X.msi=0 would turn off MSI support.

No luck with this either. Have tried your suggestion and some others
'hint.ata.0.*'.

> As far as specific settings for controlling ATA_CAM and/or other AHCI support 
> I'm fuzzy on this.
> Perhaps if you reach this point someone more knowlegable can chime in.

Same here.

> As far as what I can tell from the PR you mentioned, if you saw the 
> exact same behavior after
> having installed FBSD 8.1 and then subsquently trying to upgrade to 8.2 it 
> would nail it to matching
> the PR.

I have tried the 8.1 i386 memstick image and it does see the drive.
I have tried the 8.2 i386 memstick image and it does not see the drive.
I have tried the 9.0 i386 memstick image and it does not see the drive.
I have tried the 9.0 amd64 memstick image and it does not see the drive.

Didn't do an install of 8.1 and upgrade to 8.2 though. If needed I
could try that, but I'd prefer to do a clean 9.0 install.

> Hope this helps any, as it's just basically just a couple of wild guesses 
> to maybe get you started.

Well, still no FBSD 9.0 on the box but it kept me busy. Thanks anyways!

Jasper

-- 
“We spend the first twelve months of our children's lives teaching
them to walk and talk and the next twelve telling them to sit down and
shut up.”
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD 9.0 ICH8M trouble, no HDD found, unable to install.

[Michael Powell]

Jasper Valentijn wrote:

> L.S.,
> 
> I'm not able to install FreeBSD on a Sony Vaio vgn-cr31s. The problem
> seems to be related to PR kern/153440,
> .
> 
> The "FreeBSD-9.0-RELEASE-i386-memstick.img" was used to try the
> install and extraction of the information below, verbose dmesg output
> and pciconf output.
> 
> Does anybody have a workaround for this problem?
> 
> If I could/should provide more information, just ask.
> 

I do not have this hardware, so these are just a couple of wild guessses 
from the blue on my part.  I am also looking only at 64 bit platforms here, 
so if there is any signifigant difference with 32 bit I can't look/see.

First, you might try using the "2" option on the boot menu and then 'load 
acpi_sony' followed by 'boot'. If this works, then you are indeed fortunate. 
If this is the case, at the end of the install when it gives you the chance 
to edit files put acpi_sony_load="YES" in /boot/loader.conf prior to 
rebooting.

Second has to do with AHCI support, and I'm a little fuzzy here. IIRC Intel 
began AHCI support with the ICH6 chip. With the advent of FreeBSD 9 the 
underlying mechanism has changed to the new ATA_CAM layer, with ahci support 
a default. Check your BIOS (if possible) to see what options are available. 
You may try disabling AHCI by switching to Legacy IDE mode and see what 
changes. If it works when you do this it confirms this to be where the 
problem lies. Also ensure you are not using any BIOS config for AHCI+RAID.

Now you don't really want to run a modern day box without AHCI as you lose 
things like NCQ resulting in performance loss. Especially for SSDs as they 
demand it.  You may be able to play around a little using the loader (press 
"2") to set and unset various variables. For example, hint.ahci.X.msi=0 
would turn off MSI support. As far as specific settings for controlling 
ATA_CAM and/or other AHCI support I'm fuzzy on this. Perhaps if you reach 
this point someone more knowlegable can chime in. But if you were to find a 
sysctl that made it magically work with AHCI you could put it in loader.conf 
to make it permanent.

As far as what I can tell from the PR you mentioned, if you saw the exact 
same behavior after having installed FBSD 8.1 and then subsquently trying to 
upgrade to 8.2 it would nail it to matching the PR. Sometimes there are 
hardware identifiers like PCI ID's that just need to be added to source for 
some minor offshoot/revision chip to be recognized properly. If you got down 
to this by process of elimination you would probably at that point want to 
work with a developer (someone much smarter than me) to get support added. 
If this were to become the case this is desirable as it would remove the 
problem for anyone else coming along later.

Hope this helps any, as it's just basically just a couple of wild guesses to 
maybe get you started.  

-Mike






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

Re: Xorg error: New athlon laptop, radeonhd video - unable to load fbdev

[Da Rock]

On 12/21/11 07:39, Warren Block wrote:

On Tue, 20 Dec 2011, Da Rock wrote:

The laptop is a compaq cq62 with a quad core phenom and a ATI 4200 
Radeon mobility GPU, as well as 6300 GPU.


Sorry, I can't find any specs for a CQ62 with both ATI and NVidia. 
There's a trademark name for the dual GPU systems, at least the 
Intel-plus-something-else kind, but I can't recall it.

No, no- you won't. Both cards in the laptop are ATI.

The HTPC has an onboard NVidia, and a PCIe 16x ATI.


The HTPC/desktop is a whitebox quad core phenom on a ASUS MB (not 
100% sure which) with a NVidia onboard pcie GPU, and an ATI Radeon 
3450. There could be yet another GPU on there, but I can't remember.


That system is running 8.x FBSD (1 or 2- can't quite remember),


The start of /var/log/Xorg.0.log would be interesting, both for the 
version of FreeBSD and the version of xorg-server.  I don't think I 
have anything with dual PCIe X16 slots to test.
I'll have to look closer at it when I get a spare breath, it is a little 
intriguing.


and the laptop I'm installing 9.0-RC3 on, with the view to using 
freebsd-update to RELEASE, because of the lack of Atheros 9285 
support in 8.x (tried for hours, just couldn't get the bird to fly :( ).


From what I understand now, having been able assimilate what has been 
discussed here and through google, it seems there is a conflict when 
dealing with multiple onboard GPUs. What exactly is the issue with 
getting an arbiter for FreeBSD? Aside from time, naturally.


Usually it's finding someone able to do the work that's willing to do 
the work.  The Foundation is funding some of that, and I've heard 
they're interested in getting the KMS for the Radeon driver going.
Is there anyone here that _can_ do the work? What about mentoring? As 
for the financials... thats something else to consider.

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

Re: Xorg error: New athlon laptop, radeonhd video - unable to load fbdev

[Warren Block]

On Tue, 20 Dec 2011, Da Rock wrote:

The laptop is a compaq cq62 with a quad core phenom and a ATI 4200 Radeon 
mobility GPU, as well as 6300 GPU.


Sorry, I can't find any specs for a CQ62 with both ATI and NVidia. 
There's a trademark name for the dual GPU systems, at least the 
Intel-plus-something-else kind, but I can't recall it.


The HTPC/desktop is a whitebox quad core phenom on a ASUS MB (not 100% sure 
which) with a NVidia onboard pcie GPU, and an ATI Radeon 3450. There could be 
yet another GPU on there, but I can't remember.


That system is running 8.x FBSD (1 or 2- can't quite remember),


The start of /var/log/Xorg.0.log would be interesting, both for the 
version of FreeBSD and the version of xorg-server.  I don't think I 
have anything with dual PCIe X16 slots to test.


and the laptop I'm installing 9.0-RC3 on, with the view to using 
freebsd-update to RELEASE, because of the lack of Atheros 9285 support 
in 8.x (tried for hours, just couldn't get the bird to fly :( ).


From what I understand now, having been able assimilate what has been 
discussed here and through google, it seems there is a conflict when dealing 
with multiple onboard GPUs. What exactly is the issue with getting an arbiter 
for FreeBSD? Aside from time, naturally.


Usually it's finding someone able to do the work that's willing to do 
the work.  The Foundation is funding some of that, and I've heard 
they're interested in getting the KMS for the Radeon driver going.

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

Re: Xorg error: New athlon laptop, radeonhd video - unable to load fbdev

[Da Rock]

On 12/20/11 14:33, Warren Block wrote:

On Tue, 20 Dec 2011, Da Rock wrote:

Some newer laptops have dual GPUs, an onboard Intel combined with 
one from another vendor for higher performance.  There's 
hot-switching between the two, but AFAIK it's not supported in 
FreeBSD.  There may be a BIOS option to disable one or the other.  
There should still be two video outputs.


More than one video card at a time is a different issue, which is 
also unsupported on FreeBSD AFAIK:

(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
It appears that it is something that needs to be resolved pretty 
quickly then. The linux guys jumped on it quick as (I'm not ribbing 
by the way) - probably their guys came across it sooner than BSD users.


What has thrown me is the fact that I didn't even consider it as a 
problem because I already had installed on a dual video system- ATI 
card and NVidia onboard, both that will work on a linux system, and 
that FBSD has no problem like this either; it just works. Weird...


It's difficult to tell what you're saying.  It's possible that 
multiple cards would work in some combinations, and just that the ones 
I tried did not.  Also, you're talking about two systems, a laptop and 
a desktop.  So it would be good to get some specifics, like laptop 
brand and model, whether the desktop dual-card setup worked with 
FreeBSD (and which version of FreeBSD).
NP. I thought I was clear, but I'm not always coherent when I 
communicate (apparently... just ask the missus :) ).


The laptop is a compaq cq62 with a quad core phenom and a ATI 4200 
Radeon mobility GPU, as well as 6300 GPU.


The HTPC/desktop is a whitebox quad core phenom on a ASUS MB (not 100% 
sure which) with a NVidia onboard pcie GPU, and an ATI Radeon 3450. 
There could be yet another GPU on there, but I can't remember.


That system is running 8.x FBSD (1 or 2- can't quite remember), and the 
laptop I'm installing 9.0-RC3 on, with the view to using freebsd-update 
to RELEASE, because of the lack of Atheros 9285 support in 8.x (tried 
for hours, just couldn't get the bird to fly :( ).


From what I understand now, having been able assimilate what has been 
discussed here and through google, it seems there is a conflict when 
dealing with multiple onboard GPUs. What exactly is the issue with 
getting an arbiter for FreeBSD? Aside from time, naturally.

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

Re: Xorg error: New athlon laptop, radeonhd video - unable to load fbdev

[Warren Block]

On Tue, 20 Dec 2011, Da Rock wrote:

Some newer laptops have dual GPUs, an onboard Intel combined with one from 
another vendor for higher performance.  There's hot-switching between the 
two, but AFAIK it's not supported in FreeBSD.  There may be a BIOS option 
to disable one or the other.  There should still be two video outputs.


More than one video card at a time is a different issue, which is also 
unsupported on FreeBSD AFAIK:

(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
It appears that it is something that needs to be resolved pretty quickly 
then. The linux guys jumped on it quick as (I'm not ribbing by the way) - 
probably their guys came across it sooner than BSD users.


What has thrown me is the fact that I didn't even consider it as a problem 
because I already had installed on a dual video system- ATI card and NVidia 
onboard, both that will work on a linux system, and that FBSD has no problem 
like this either; it just works. Weird...


It's difficult to tell what you're saying.  It's possible that multiple 
cards would work in some combinations, and just that the ones I tried 
did not.  Also, you're talking about two systems, a laptop and a 
desktop.  So it would be good to get some specifics, like laptop brand 
and model, whether the desktop dual-card setup worked with FreeBSD (and 
which version of FreeBSD).

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

Re: Xorg error: New athlon laptop, radeonhd video - unable to load fbdev

[Da Rock]

On 12/20/11 03:05, Warren Block wrote:

On Mon, 19 Dec 2011, Da Rock wrote:


On 12/19/11 21:31, Da Rock wrote:
I hate to come with this kind of a query, but my googling hasn't 
come across a satisfactory answer.


I'm running an install on a brand new laptop for a client, and I'm 
trying to get X up using xdm- nothing. The logs says it failed to 
load fbdev because there is no data module.


I try uninstalling fbdev and running a rebuild of xorg- its still 
using the builtin configuration and still can't load fbdev. No 
devices detected.


I run Xorg -configure, and it shows the radeon card fine, 2 
displays. Still working with the config file, but it seems fine.
correction - its dual display issue that I've never had trouble with 
before (I also have installed on a HTPC with same memory, phenom quad 
core, uses a radeon HD card and a NVidia HD card). And no, the Xorg 
-config /root/xorg.conf.new [-retro] doesn't work as it is locking up 
and I can't even ctl-alt-backspace, I have to acpi power off to shut 
the system down. Google's still not giving me any hope... :( Last 
time I came across this level of issue was with a solo vintage intel 
card on yet another laptop- it froze the system too.


BTW, who says multicard vga is rare?


Some newer laptops have dual GPUs, an onboard Intel combined with one 
from another vendor for higher performance.  There's hot-switching 
between the two, but AFAIK it's not supported in FreeBSD.  There may 
be a BIOS option to disable one or the other.  There should still be 
two video outputs.


More than one video card at a time is a different issue, which is also 
unsupported on FreeBSD AFAIK:

(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
It appears that it is something that needs to be resolved pretty quickly 
then. The linux guys jumped on it quick as (I'm not ribbing by the way) 
- probably their guys came across it sooner than BSD users.


What has thrown me is the fact that I didn't even consider it as a 
problem because I already had installed on a dual video system- ATI card 
and NVidia onboard, both that will work on a linux system, and that FBSD 
has no problem like this either; it just works. Weird...


So what are my options then? I have 2 high performance cards I can't 
use? VESA is not exactly an exciting solution - or secure: it somehow 
retains the image displayed in memory, and shows it as it loads up X the 
next time.

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

Re: Xorg error: New athlon laptop, radeonhd video - unable to load fbdev

[Warren Block]

On Mon, 19 Dec 2011, Da Rock wrote:


On 12/19/11 21:31, Da Rock wrote:
I hate to come with this kind of a query, but my googling hasn't come 
across a satisfactory answer.


I'm running an install on a brand new laptop for a client, and I'm trying 
to get X up using xdm- nothing. The logs says it failed to load fbdev 
because there is no data module.


I try uninstalling fbdev and running a rebuild of xorg- its still using the 
builtin configuration and still can't load fbdev. No devices detected.


I run Xorg -configure, and it shows the radeon card fine, 2 displays. Still 
working with the config file, but it seems fine.
correction - its dual display issue that I've never had trouble with before 
(I also have installed on a HTPC with same memory, phenom quad core, uses a 
radeon HD card and a NVidia HD card). And no, the Xorg -config 
/root/xorg.conf.new [-retro] doesn't work as it is locking up and I can't 
even ctl-alt-backspace, I have to acpi power off to shut the system down. 
Google's still not giving me any hope... :( Last time I came across this 
level of issue was with a solo vintage intel card on yet another laptop- it 
froze the system too.


BTW, who says multicard vga is rare?


Some newer laptops have dual GPUs, an onboard Intel combined with one 
from another vendor for higher performance.  There's hot-switching 
between the two, but AFAIK it's not supported in FreeBSD.  There may be 
a BIOS option to disable one or the other.  There should still be two 
video outputs.


More than one video card at a time is a different issue, which is also 
unsupported on FreeBSD AFAIK:

(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Xorg error: New athlon laptop, radeonhd video - unable to load fbdev

[Da Rock]

On 12/19/11 21:31, Da Rock wrote:
I hate to come with this kind of a query, but my googling hasn't come 
across a satisfactory answer.


I'm running an install on a brand new laptop for a client, and I'm 
trying to get X up using xdm- nothing. The logs says it failed to load 
fbdev because there is no data module.


I try uninstalling fbdev and running a rebuild of xorg- its still 
using the builtin configuration and still can't load fbdev. No devices 
detected.


I run Xorg -configure, and it shows the radeon card fine, 2 displays. 
Still working with the config file, but it seems fine.
correction - its dual display issue that I've never had trouble with 
before (I also have installed on a HTPC with same memory, phenom quad 
core, uses a radeon HD card and a NVidia HD card). And no, the Xorg 
-config /root/xorg.conf.new [-retro] doesn't work as it is locking up 
and I can't even ctl-alt-backspace, I have to acpi power off to shut the 
system down. Google's still not giving me any hope... :( Last time I 
came across this level of issue was with a solo vintage intel card on 
yet another laptop- it froze the system too.


BTW, who says multicard vga is rare?
WTF? This is essentially the same hardware as another laptop I've 
setup (same video card - same brand CPU, just bigger and faster), and 
its fine. Both are AMD, the original is athlon dual core, the new is 
phenom quad core.


The googling failed as my searches came up with either root has access 
and user doesn't, or mixed intel/ati. Neither are the case here...


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


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

Xorg error: New athlon laptop, radeonhd video - unable to load fbdev

[Da Rock]

I hate to come with this kind of a query, but my googling hasn't come 
across a satisfactory answer.


I'm running an install on a brand new laptop for a client, and I'm 
trying to get X up using xdm- nothing. The logs says it failed to load 
fbdev because there is no data module.


I try uninstalling fbdev and running a rebuild of xorg- its still using 
the builtin configuration and still can't load fbdev. No devices detected.


I run Xorg -configure, and it shows the radeon card fine, 2 displays. 
Still working with the config file, but it seems fine.


WTF? This is essentially the same hardware as another laptop I've setup 
(same video card - same brand CPU, just bigger and faster), and its 
fine. Both are AMD, the original is athlon dual core, the new is phenom 
quad core.


The googling failed as my searches came up with either root has access 
and user doesn't, or mixed intel/ati. Neither are the case here...


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

unable to find device node for /dev/asd0s4 in dev!

[Jacob Minshall]

I have been attempting to install breeBSD 8.2 on my 160GB apple tv 1 hard 
drive. I made it so there was a blank space to partition 100GB. In the 
installer I clicked make slice on that empty space, used the auto partition 
sequence, then clicked all for files to install. After this happened I got the 
error message "Unable to find device node for /dev/.. in dev!". When I got back 
to my regular startup drive and looked at the apple TV drive(connected by a IDE 
to USB by the way) all other partitions were gone, and just a 100GB blank 
looking partition was left. I did the terminal command gpt -r show on the disk, 
and it still had the framework of all it's original partitions, but nothing in 
the 100GB left blank. After repeated attempts to install, even with trying the 
command to erase the entire drive and install freeBSD over it, it always gave 
me the same response. Then I decided to make a 100GB partition in my intel 
macbook pro to see if a freeBSD install there would work. It did now work 
either, which leads me to my current and main problem. Now my laptop does not 
start, I put in the install disk which shows that there is no macintosh HD like 
it showed there was no other drives on the apple tv disk. I have read online 
now that maybe I needed to add 35 blocks on either side to not return with that 
response, but that doesn't answer where my drive went and I don't quite 
understand how to do that. When I go back to the installer, it shows that all 
partitions are there, except the 165(i think) partition for freeBSD that is the 
only one which shows up on disk utility 
partitioner.___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD 8.2-RELEASE Install Failure: Unable to create a new /etc/fstab

[Rick Miller]

Just following up...I resolved the issue by copying /etc/* to /stand/
in the mfsroot.

On Tue, Oct 25, 2011 at 12:54 PM, Rick Miller  wrote:
> Hi All,
>
> I am Installing 8.2-RELEASE via PXE and receive an error stating that
> sysinstall was unable to create new /etc/fstab.  Everything appears to
> function correctly, in that, the system TFTP's the pxeboot and mfsroot
> files as needed.  However, When I switch to the holographic shell and
> poke around a little, I can see that there is no /etc, despite it's
> existence in the mfsroot.gz.
>
> I must be missing something and am hoping that someone might be able
> to point in the right direction.
>
> --
> Take care
> Rick Miller
>



-- 
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

FreeBSD 8.2-RELEASE Install Failure: Unable to create a new /etc/fstab

[Rick Miller]

Hi All,

I am Installing 8.2-RELEASE via PXE and receive an error stating that
sysinstall was unable to create new /etc/fstab.  Everything appears to
function correctly, in that, the system TFTP's the pxeboot and mfsroot
files as needed.  However, When I switch to the holographic shell and
poke around a little, I can see that there is no /etc, despite it's
existence in the mfsroot.gz.

I must be missing something and am hoping that someone might be able
to point in the right direction.

-- 
Take care
Rick Miller
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Install failure: Unable to find device node

[va08bsdf-bfores...@yahoo.com]

Please check the following link:  
http://www.daemonforums.org/showthread.php?t=6373

I am attempting to install FreeBSD from DVD 
(FreeBSD-8.2-RELEASE-amd64-dvd1.iso.xz)

Installing on a Dell PE-2950 with six 300Gb Hds installed via Perc5i Serial 
Attached SCSI. The controller has mirrored drives 0 & 1 creating virtual device 
mfid0.

I can boot the install CD and go through the process of install prep but once I 
answer the last question to begin the install I get the following error: 
"Unable to find device node for /dev/mfid0s1b..."


More details are in the forum on DaemonForums where I first asked.  

Please reply directly AND in the forum because I am not actually a member of 
this list.  Thanks!

Ben 
-- -- -- 
http://themiraclemansion.com
http://www.cbsnews.com/stories/2006/03/16/60minutes/rooney/main1412330.shtml
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

unable to install php5-ldap port

[Frank Bonnet]

Hello

I'm trying to install php5-ldap from ports and I'm facing
to a strange error :

ldap3# cd php5-ldap
ldap3# make config
===> No options to configure
ldap3# make
===>   php5-ldap-5.3.8 depends on file: /usr/local/bin/phpize - found
===>   php5-ldap-5.3.8 depends on file: /usr/local/bin/autoconf-2.68 - found
===>   php5-ldap-5.3.8 depends on shared library: ldap-2.4.8 - found
===>  PHPizing for php5-ldap-5.3.8
Configuring for:
PHP Api Version: 20090626
Zend Module Api No:  20090626
Zend Extension Api No:   220090626
autoconf: required version 2.68 not found
*** Error code 1

Stop in /usr/ports/net/php5-ldap.
ldap3# autoconf -v
autoconf-2.68: error: no input file


As you can see the autoconf version is OK , anyone understand what happen ?

Thanks

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

Re: Unable to build the print/lyx port

[Herbert J. Skuhra]

On Tue, 16 Aug 2011 11:55:42 -1000
Open Slate Project  wrote:

> I was unsuccessful in posting directly so I am forwarding from another 
> account. Apologies for format.
> 
> Gary Dunn  wrote:
> 
> >FreeBSD Questions 
> >
> >
> >Unable to build the print/lyx port. Generic kernal, fresh portsnap
> >fetch /
> >update cycle.
> >
> >$ uname -a
> >FreeBSD my.host.name 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18
> >02:24:46
> >UTC 2011 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC 
> >i386
> >
> >portinstall lyx
> >After long run, picking up output near end:
> >
> >...
> >gmake[4]: Entering directory `/usr/ports/print/lyx/work/lyx-2.0.0/src'
> >  CXXAuthor.o
> >  CXXBidi.o
> >  CXXboost.o
> >  CXXBranchList.o
> >  CXXBuffer.o
> >  CXXbuffer_funcs.o
> >  CXXBufferList.o
> >  CXXBufferParams.o
> >  CXXBufferView.o
> >  CXXBullet.o
> >  CXXChanges.o
> >  CXXChktex.o
> >  CXXCmdDef.o
> >  CXXColor.o
> >  CXXConverterCache.o
> >ConverterCache.cpp:83: warning: 'lyx::FormatCache' has a field
> >'lyx::FormatCache::cache' whose type uses the anonymous namespace
> >  CXXConverter.o
> >  CXXCoordCache.o
> >... (omitted long list of similar lines)
> >  CXXPersonalWordList.o
> >  CXXPrinterParams.o
> >  CXXThesaurus.o
> >  AR liblyxcore.a
> >  AR liblyxgraphics.a
> >  AR liblyxmathed.a
> >  AR liblyxinsets.a
> >  CXXLD  lyx
> >/usr/bin/ld: warning: libicuuc.so.46, needed by
> >/usr/local/lib/libboost_regex.so, not found (try using -rpath or
> >-rpath-link)
> >/usr/bin/ld: warning: libicui18n.so.46, needed by
> >/usr/local/lib/libboost_regex.so, not found (try using -rpath or
> >-rpath-link)
> >/usr/bin/ld: warning: libicudata.so.46, needed by
> >/usr/local/lib/libboost_regex.so, not found (try using -rpath or
> >-rpath-link)
> >/usr/local/lib/libboost_regex.so: undefined reference to
> >`icu_46::Locale::Locale()'
> >/usr/local/lib/libboost_regex.so: undefined reference to
> >`icu_46::Locale::Locale(icu_46::Locale const&)'
> >/usr/local/lib/libboost_regex.so: undefined reference to `u_isblank_46'
> >/usr/local/lib/libboost_regex.so: undefined reference to `u_isspace_46'
> >/usr/local/lib/libboost_regex.so: undefined reference to `u_digit_46'
> >/usr/local/lib/libboost_regex.so: undefined reference to
> >`u_charType_46'
> >/usr/local/lib/libboost_regex.so: undefined reference to `u_tolower_46'
> >/usr/local/lib/libboost_regex.so: undefined reference to
> >`u_charFromName_46'
> >/usr/local/lib/libboost_regex.so: undefined reference to
> >`icu_46::Locale::~Locale()'
> >/usr/local/lib/libboost_regex.so: undefined reference to
> >`icu_46::Collator::createInstance(icu_46::Locale const&, UErrorCode&)'
> >gmake[4]: *** [lyx] Error 1
> >gmake[4]: Leaving directory `/usr/ports/print/lyx/work/lyx-2.0.0/src'
> >gmake[3]: *** [all-recursive] Error 1
> >gmake[3]: Leaving directory `/usr/ports/print/lyx/work/lyx-2.0.0/src'
> >gmake[2]: *** [all] Error 2
> >gmake[2]: Leaving directory `/usr/ports/print/lyx/work/lyx-2.0.0/src'
> >gmake[1]: *** [all-recursive] Error 1
> >gmake[1]: Leaving directory `/usr/ports/print/lyx/work/lyx-2.0.0'
> >gmake: *** [all] Error 2
> >*** Error code 1
> >
> >Stop in /usr/ports/print/lyx.
> >*** Error code 1
> >
> >Stop in /usr/ports/print/lyx.
> >** Command failed [exit code 1]: /usr/bin/script -qa
> >/tmp/portinstall20110808-84103-1lft56n-0 env make
> >** Fix the problem and try again.
> >** Listing the failed packages (-:ignored / *:skipped / !:failed)
> >! print/lyx (linker error)
> >$
> >
> >I have icu version 4.8, looks like libboost is looking for 4.6. Or is
> >the
> >problem with boost?
> >
> >$ pkg_info | grep icu
> >icu-4.8.1   International Components for Unicode (from IBM)
> >
> >$ pkg_version -v | grep boost-libs
> >boost-libs-1.45.0_1 =   up-to-date with port
> >
> >Anyone have this working?

Have you tried to rebuild devel/boost-libs first?

If that doesn't help use sysutils/libchk to find files linked against
the old icu port and 'pkg_info -W file' to find the port the file
belongs to. Rebuild these ports as well.

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

Unable to build the print/lyx port

[Open Slate Project]

I was unsuccessful in posting directly so I am forwarding from another account. 
Apologies for format.

Gary Dunn  wrote:

>FreeBSD Questions 
>
>
>Unable to build the print/lyx port. Generic kernal, fresh portsnap
>fetch /
>update cycle.
>
>$ uname -a
>FreeBSD my.host.name 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri Feb 18
>02:24:46
>UTC 2011 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC 
>i386
>
>portinstall lyx
>After long run, picking up output near end:
>
>...
>gmake[4]: Entering directory `/usr/ports/print/lyx/work/lyx-2.0.0/src'
>  CXXAuthor.o
>  CXXBidi.o
>  CXXboost.o
>  CXXBranchList.o
>  CXXBuffer.o
>  CXXbuffer_funcs.o
>  CXXBufferList.o
>  CXXBufferParams.o
>  CXXBufferView.o
>  CXXBullet.o
>  CXXChanges.o
>  CXXChktex.o
>  CXXCmdDef.o
>  CXXColor.o
>  CXXConverterCache.o
>ConverterCache.cpp:83: warning: 'lyx::FormatCache' has a field
>'lyx::FormatCache::cache' whose type uses the anonymous namespace
>  CXXConverter.o
>  CXXCoordCache.o
>... (omitted long list of similar lines)
>  CXXPersonalWordList.o
>  CXXPrinterParams.o
>  CXXThesaurus.o
>  AR liblyxcore.a
>  AR liblyxgraphics.a
>  AR liblyxmathed.a
>  AR liblyxinsets.a
>  CXXLD  lyx
>/usr/bin/ld: warning: libicuuc.so.46, needed by
>/usr/local/lib/libboost_regex.so, not found (try using -rpath or
>-rpath-link)
>/usr/bin/ld: warning: libicui18n.so.46, needed by
>/usr/local/lib/libboost_regex.so, not found (try using -rpath or
>-rpath-link)
>/usr/bin/ld: warning: libicudata.so.46, needed by
>/usr/local/lib/libboost_regex.so, not found (try using -rpath or
>-rpath-link)
>/usr/local/lib/libboost_regex.so: undefined reference to
>`icu_46::Locale::Locale()'
>/usr/local/lib/libboost_regex.so: undefined reference to
>`icu_46::Locale::Locale(icu_46::Locale const&)'
>/usr/local/lib/libboost_regex.so: undefined reference to `u_isblank_46'
>/usr/local/lib/libboost_regex.so: undefined reference to `u_isspace_46'
>/usr/local/lib/libboost_regex.so: undefined reference to `u_digit_46'
>/usr/local/lib/libboost_regex.so: undefined reference to
>`u_charType_46'
>/usr/local/lib/libboost_regex.so: undefined reference to `u_tolower_46'
>/usr/local/lib/libboost_regex.so: undefined reference to
>`u_charFromName_46'
>/usr/local/lib/libboost_regex.so: undefined reference to
>`icu_46::Locale::~Locale()'
>/usr/local/lib/libboost_regex.so: undefined reference to
>`icu_46::Collator::createInstance(icu_46::Locale const&, UErrorCode&)'
>gmake[4]: *** [lyx] Error 1
>gmake[4]: Leaving directory `/usr/ports/print/lyx/work/lyx-2.0.0/src'
>gmake[3]: *** [all-recursive] Error 1
>gmake[3]: Leaving directory `/usr/ports/print/lyx/work/lyx-2.0.0/src'
>gmake[2]: *** [all] Error 2
>gmake[2]: Leaving directory `/usr/ports/print/lyx/work/lyx-2.0.0/src'
>gmake[1]: *** [all-recursive] Error 1
>gmake[1]: Leaving directory `/usr/ports/print/lyx/work/lyx-2.0.0'
>gmake: *** [all] Error 2
>*** Error code 1
>
>Stop in /usr/ports/print/lyx.
>*** Error code 1
>
>Stop in /usr/ports/print/lyx.
>** Command failed [exit code 1]: /usr/bin/script -qa
>/tmp/portinstall20110808-84103-1lft56n-0 env make
>** Fix the problem and try again.
>** Listing the failed packages (-:ignored / *:skipped / !:failed)
>! print/lyx (linker error)
>$
>
>I have icu version 4.8, looks like libboost is looking for 4.6. Or is
>the
>problem with boost?
>
>$ pkg_info | grep icu
>icu-4.8.1   International Components for Unicode (from IBM)
>
>$ pkg_version -v | grep boost-libs
>boost-libs-1.45.0_1 =   up-to-date with port
>
>Anyone have this working?
>
>
>-- 
>Gary Dunn
>Honolulu

--

Gary Dunn, Honolulu
Open Slate Project
http://openslate.org
 
Sent from my Android phone with K-9 Mail.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Unable to reply immediately Re: [WARNING: VIRUS REMOVED] Delivery reports about your e-mail

[E.S. Sherratt]

I shall be reading emails only very intermittently until August 7th,
but will reply as soon as I can.

If you have a query concerning the MA in Aegean Archaeology, please
contact Kathryn Goldsack (k.golds...@sheffield.ac.uk).

Sue Sherratt

-- 
Dr E.S. Sherratt
Department of Archaeology
University of Sheffield
Northgate House
West Street
Sheffield S1 4ET

http://www.archatlas.dept.shef.ac.uk/Home.php
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to reach bsd-lists via mail [solved]

[Christopher J. Ruwe]

Thank you all for your kind help. The problem was apparently, that the HELO 
message of my postfix server did not match the rDNS.

Thanks again, cheers,
-- 
Christopher J. Ruwe
TZ GMT + 2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to reach bsd-lists via mail

[Christopher J. Ruwe]

On Sun, 19 Jun 2011 14:12:46 +0100
Paul Macdonald  wrote:

> 
> > Thanks for all the effort ... somehow, posting an error message was
> > the *one* thing I forgot:
> >
> > Jun 19 14:23:37 mail postfix/smtp[9416]: CE6A019C50:
> > to=,
> > relay=mx1.freebsd.org[69.147.83.52]:25, delay=944,
> > delays=943/0.03/0.86/0.19, dsn=4.7.1, status=deferred (host
> > mx1.freebsd.org[69.147.83.52] said: 450 4.7.1 Client host rejected:
> > cannot find your hostname, [188.40.164.98] (in reply to RCPT TO
> > command))
> >
> > Thanks again, cheers
> I'm not that familiar with postfix, but the issue does look rdns
> related.
> 
> Under sendmail, on hosts with multiple names you have to make sure
> the hostname it uses to make the connection is the one that all your
> reverse dns is setup for.
> (your rdns does resolve backwards and forwards , but the ptr cruwe.de
> is possibly not what your mail server advertises its hostname with
> ( not neccesarily the same when you telnet in the make an incoming
> conn).
> 
> #dig -x 188.40.164.98 +short
> cruwe.de
> If you mail me direct i can tell you what hostname i see, thats the
> one i'd try adding the rdns for.
> 
> Paul.
> 

I have asked my provider to set rDNS for 188.40.164.98 to
cruwe.de, which he has, and changed the $myhostname to cruwe.de (was
mail.cruwe.de before). Currently, I am waiting for DNS to permeate to
the caches and will try with freebsd-test@ again tomorrow. 

Thanks again,
-- 
Christopher J. Ruwe
TZ GMT + 2


-- 
Christopher J. Ruwe
TZ GMT + 2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to reach bsd-lists via mail

[Paul Macdonald]

Thanks for all the effort ... somehow, posting an error message was the
*one* thing I forgot:

Jun 19 14:23:37 mail postfix/smtp[9416]: CE6A019C50:
to=, relay=mx1.freebsd.org[69.147.83.52]:25,
delay=944, delays=943/0.03/0.86/0.19, dsn=4.7.1, status=deferred (host
mx1.freebsd.org[69.147.83.52] said: 450 4.7.1 Client host rejected:
cannot find your hostname, [188.40.164.98] (in reply to RCPT TO
command))

Thanks again, cheers

I'm not that familiar with postfix, but the issue does look rdns related.

Under sendmail, on hosts with multiple names you have to make sure the 
hostname it uses to make the connection is the one that all your reverse 
dns is setup for.
(your rdns does resolve backwards and forwards , but the ptr cruwe.de is 
possibly not what your mail server advertises its hostname with ( not 
neccesarily the same when you telnet in the make an incoming conn).


#dig -x 188.40.164.98 +short
cruwe.de
If you mail me direct i can tell you what hostname i see, thats the one 
i'd try adding the rdns for.


Paul.


--
-
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-
t: 0131 5548070
m: 07534206249
e: p...@ifdnrg.com
w: http://www.ifdnrg.com
-
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
-


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

Re: unable to reach bsd-lists via mail

[Christopher J. Ruwe]

On Sun, 19 Jun 2011 13:13:22 +0100
Paul Macdonald  wrote:

> On 19/06/2011 13:03, Bernt Hansson wrote:
> > 2011-06-19 08:22, Matthew Seaman skrev:
> >> On 18/06/2011 23:29, Christopher J. Ruwe wrote:
> >>> The mailer answers "220 mail.cruwe.de ESMTP Postfix" when
> >>> telnet'ed, so I guess that is what the mailer returns as hostname.
> >>>
> >>> I did not know about that DNS/rDNS issue ...
> >>
> >> You need the name your mail server HELOs as to resolve both
> >> forwards and reverse ---
> >
> > No. Our mailserver does not resolve DNS/rDNS and I can send mail
> > without problems to freebsd.org.
> >
> >
> reverse dns is definately a good thing to have in place if you want
> your mail to be accepted by remote MTA's.
> 
> I didn't see the OP post an error message in this thread, that would
> be a good place to start.
> 
> 

Thanks for all the effort ... somehow, posting an error message was the
*one* thing I forgot:

Jun 19 14:23:37 mail postfix/smtp[9416]: CE6A019C50:
to=, relay=mx1.freebsd.org[69.147.83.52]:25,
delay=944, delays=943/0.03/0.86/0.19, dsn=4.7.1, status=deferred (host
mx1.freebsd.org[69.147.83.52] said: 450 4.7.1 Client host rejected:
cannot find your hostname, [188.40.164.98] (in reply to RCPT TO
command))

Thanks again, cheers
-- 
Christopher J. Ruwe
TZ GMT + 2

-- 
Christopher J. Ruwe
TZ GMT + 2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to reach bsd-lists via mail

[Paul Macdonald]

On 19/06/2011 13:03, Bernt Hansson wrote:

2011-06-19 08:22, Matthew Seaman skrev:

On 18/06/2011 23:29, Christopher J. Ruwe wrote:

The mailer answers "220 mail.cruwe.de ESMTP Postfix" when telnet'ed, so
I guess that is what the mailer returns as hostname.

I did not know about that DNS/rDNS issue ...


You need the name your mail server HELOs as to resolve both forwards and
reverse ---


No. Our mailserver does not resolve DNS/rDNS and I can send mail
without problems to freebsd.org.


reverse dns is definately a good thing to have in place if you want your 
mail to be accepted by remote MTA's.


I didn't see the OP post an error message in this thread, that would be 
a good place to start.



--
-
Paul Macdonald
IFDNRG Ltd
Web and video hosting
-
t: 0131 5548070
m: 07534206249
e: p...@ifdnrg.com
w: http://www.ifdnrg.com
-
IFDNRG
40 Maritime Street
Edinburgh
EH6 6SA
-


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

Re: unable to reach bsd-lists via mail

[Bernt Hansson]

2011-06-19 08:22, Matthew Seaman skrev:

On 18/06/2011 23:29, Christopher J. Ruwe wrote:

The mailer answers "220 mail.cruwe.de ESMTP Postfix" when telnet'ed, so
I guess that is what the mailer returns as hostname.

I did not know about that DNS/rDNS issue ...


You need the name your mail server HELOs as to resolve both forwards and
reverse ---


No. Our mailserver does not resolve DNS/rDNS and I can send mail
without problems to freebsd.org.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to reach bsd-lists via mail

[Matthew Seaman]

On 18/06/2011 23:29, Christopher J. Ruwe wrote:
> The mailer answers "220 mail.cruwe.de ESMTP Postfix" when telnet'ed, so
> I guess that is what the mailer returns as hostname.
> 
> I did not know about that DNS/rDNS issue ...

You need the name your mail server HELOs as to resolve both forwards and
reverse ---

 mail.cruwe.de  IN A   188.40.164.98
 98.164.40.188.in-addr.arpa IN PTR mail.cruwe.de

That's the thing the FreeBSD mail servers look for[*].

You don't need an A record for cruwe.de at all (at least, not for the
purposes of sending e-mail) MX records are all that is required so that
addresses of the form @cruwe.de will work:

cruwe.de IN MX 10 mail.cruwe.de

Cheers,

Matthew

[*] This HELO name doesn't have to be anything to do with the e-mail
addresses you use, so you could take the lazy path and use
vs532.sys-central.de for this purpose seeing as it already has the
correct forward and reverse mappings.  Mind you, that means you won't be
able to insert SPF records or other e-mail related bits as the zone
doesn't belong to you.

-- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk   Kent, CT11 9PW



signature.asc
Description: OpenPGP digital signature

Re: unable to reach bsd-lists via mail

[Daniel Staal]

--As of June 19, 2011 12:29:02 AM +0200, Christopher J. Ruwe is alleged to 
have said:



(The server is a rented virtual machine.) Am I right that I need to set
the rDNS of 188.40.164.98 to mail.cruwe.de to make the freebsd.org
servers accept my mail or that, should I set the rDNS to cruwe.de, I
should make the mailer on mail.cruwe.de identify itself as cruwe.de
instead of mail.cruwe.de?

Anyway, thank you very much for your help,


--As for the rest, it is mine.

In postfix, the relevant setting is 'myhostname' in main.cf for the 
hostname.


From my experience, it doesn't have to match the rDNS.  It needs to match 
the MX record.  But, you should be able to see what they are saying as a 
rejection notice from your logs.


Daniel T. Staal

---
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to reach bsd-lists via mail

[Christopher J. Ruwe]

On Sat, 18 Jun 2011 15:57:08 -0400
Daniel Staal  wrote:

> On Saturday, June 18, 2011 11:53:57 AM Christopher J. Ruwe wrote:
> > I have a problem with my mail-server configuration so that mail sent
> > will not reach any freebsd adresses. The solutions offered in
> > similar mails already accessible via various archives did not
> > help :-(
> > 
> > I usually send mail from the domain cruwe.de with the mail-server
> > mail.cruwe.de.
> > 
> > My configration is as such, that
> > 
> > $ host cruwe.de
> > cruwe.de has address 188.40.164.98
> > cruwe.de mail is handled by 10 mail.cruwe.de.
> > 
> > and
> > 
> > $ host mail.cruwe.de
> > mail.cruwe.de has address 188.40.164.98
> > mail.cruwe.de mail is handled by 10 mail.cruwe.de.
> [snip]
> > 
> > seems to be OK.
> > 
> > Does anyone have an idea what could be the issue?
> > 
> > Thank you, cheers
> 
> What does you mailer return as the hostname?  (Not the box on which
> your mailer is runing, but the mail server itself.  Often it can be
> set seperately.)  The FreeBSD lists are picky about having that match
> the DNS entries for your domain.
> 
> Daniel T. Staal
> 
> ---
> This email copyright the author.  Unless otherwise noted, you
> are expressly allowed to retransmit, quote, or otherwise use
> the contents for non-commercial purposes.  This copyright will
> expire 5 years after the author's death, or in 30 years,
> whichever is longer, unless such a period is in excess of
> local copyright law.
> ---
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscr...@freebsd.org"

I am not entirely sure what you mean with what the mailer returns as
hostname. The setup is as such, that cruwe.de is a FreeBSD box and
mail.cruwe.de is a jail on cruwe.de, to which the mail ports are
forwarded by packet filter. Both cruwe.de and mail.cruwe.de are
addressed with A records.

The mailer answers "220 mail.cruwe.de ESMTP Postfix" when telnet'ed, so
I guess that is what the mailer returns as hostname.

I did not know about that DNS/rDNS issue ...

$ dig mail.cruwe.de 
; <<>> DiG 9.4.3-P4 <<>> mail.cruwe.de
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2343
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.cruwe.de. IN  A

;; ANSWER SECTION:
mail.cruwe.de.  168 IN  A   188.40.164.98

;; Query time: 1 msec
;; SERVER: 83.133.84.53#53(83.133.84.53)
;; WHEN: Sun Jun 19 00:15:13 2011
;; MSG SIZE  rcvd: 47



$dig -x 188.40.164.98
; <<>> DiG 9.4.3-P4 <<>> -x 188.40.164.98
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23225
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;98.164.40.188.in-addr.arpa.IN  PTR

;; ANSWER SECTION:
98.164.40.188.in-addr.arpa. 57111 INPTR vs532.sys-central.de.

;; Query time: 1 msec
;; SERVER: 83.133.84.53#53(83.133.84.53)
;; WHEN: Sun Jun 19 00:16:08 2011
;; MSG SIZE  rcvd: 78

(The server is a rented virtual machine.) Am I right that I need to set
the rDNS of 188.40.164.98 to mail.cruwe.de to make the freebsd.org
servers accept my mail or that, should I set the rDNS to cruwe.de, I
should make the mailer on mail.cruwe.de identify itself as cruwe.de
instead of mail.cruwe.de?

Anyway, thank you very much for your help,
-- 
Christopher J. Ruwe
TZ GMT + 2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to reach bsd-lists via mail

[Daniel Staal]

On Saturday, June 18, 2011 11:53:57 AM Christopher J. Ruwe wrote:
> I have a problem with my mail-server configuration so that mail sent
> will not reach any freebsd adresses. The solutions offered in similar
> mails already accessible via various archives did not help :-(
> 
> I usually send mail from the domain cruwe.de with the mail-server
> mail.cruwe.de.
> 
> My configration is as such, that
> 
> $ host cruwe.de
> cruwe.de has address 188.40.164.98
> cruwe.de mail is handled by 10 mail.cruwe.de.
> 
> and
> 
> $ host mail.cruwe.de
> mail.cruwe.de has address 188.40.164.98
> mail.cruwe.de mail is handled by 10 mail.cruwe.de.
[snip]
> 
> seems to be OK.
> 
> Does anyone have an idea what could be the issue?
> 
> Thank you, cheers

What does you mailer return as the hostname?  (Not the box on which your 
mailer is runing, but the mail server itself.  Often it can be set 
seperately.)  The FreeBSD lists are picky about having that match the DNS 
entries for your domain.

Daniel T. Staal

---
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: unable to reach bsd-lists via mail

[Jon Radel]

On 6/18/11 11:53 AM, Christopher J. Ruwe wrote:


I have a problem with my mail-server configuration so that mail sent
will not reach any freebsd adresses. The solutions offered in similar
mails already accessible via various archives did not help :-(


And yet, yet, yet, here is your mail.  In duplicate no less.

Next time please:

1)  tell us what you actually mean by "will not reach"
2)  keep in mind that some mailing lists greylist incoming mail

In other words, be specific and patient.

--Jon Radel
j...@radel.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

unable to reach bsd-lists via mail

[Christopher J. Ruwe]

I have a problem with my mail-server configuration so that mail sent
will not reach any freebsd adresses. The solutions offered in similar
mails already accessible via various archives did not help :-(

I usually send mail from the domain cruwe.de with the mail-server mail.cruwe.de.

My configration is as such, that

$ host cruwe.de
cruwe.de has address 188.40.164.98
cruwe.de mail is handled by 10 mail.cruwe.de.

and

$ host mail.cruwe.de
mail.cruwe.de has address 188.40.164.98
mail.cruwe.de mail is handled by 10 mail.cruwe.de.

Now,

$ dig cruwe.de

; <<>> DiG 9.6.3 <<>> cruwe.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32046
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cruwe.de.  IN  A

;; ANSWER SECTION:
cruwe.de.   300 IN  A   188.40.164.98

;; Query time: 73 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sat Jun 18 17:51:14 2011
;; MSG SIZE  rcvd: 42

is right and

[chris@dijkstra:~]$ dig -x 188.40.164.98

; <<>> DiG 9.6.3 <<>> -x 188.40.164.98
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40136
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;98.164.40.188.in-addr.arpa.IN  PTR

;; ANSWER SECTION:
98.164.40.188.in-addr.arpa. 267 IN  PTR cruwe.de.

;; Query time: 10 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sat Jun 18 17:51:48 2011
;; MSG SIZE  rcvd: 66

seems to be OK.

Does anyone have an idea what could be the issue?

Thank you, cheers
-- 
Christopher J. Ruwe
TZ GMT + 2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

unable to reach bsd-lists via mail

[Christopher J. Ruwe]

I have a problem with my mail-server configuration so that mail sent
will not reach any freebsd adresses. The solutions offered in similar
mails already accessible via various archives did not help :-( 

I usually send mail from the domain cruwe.de with the mail-server
mail.cruwe.de.

My configration is as such, that

$ host cruwe.de
cruwe.de has address 188.40.164.98
cruwe.de mail is handled by 10 mail.cruwe.de.

and

$ host mail.cruwe.de
mail.cruwe.de has address 188.40.164.98
mail.cruwe.de mail is handled by 10 mail.cruwe.de.

Now,

$ dig cruwe.de

; <<>> DiG 9.6.3 <<>> cruwe.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32046
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;cruwe.de.  IN  A

;; ANSWER SECTION:
cruwe.de.   300 IN  A   188.40.164.98

;; Query time: 73 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sat Jun 18 17:51:14 2011
;; MSG SIZE  rcvd: 42

is right and

[chris@dijkstra:~]$ dig -x 188.40.164.98

; <<>> DiG 9.6.3 <<>> -x 188.40.164.98
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40136
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;98.164.40.188.in-addr.arpa.IN  PTR

;; ANSWER SECTION:
98.164.40.188.in-addr.arpa. 267 IN  PTR cruwe.de.

;; Query time: 10 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sat Jun 18 17:51:48 2011
;; MSG SIZE  rcvd: 66

seems to be OK.

Does anyone have an idea what could be the issue?

Thank you, cheers
-- 
Christopher J. Ruwe
TZ GMT + 2
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Unable to start KDE4 on freebsd 7.4-RELEASE

[Antonio Olivares]

> I created a new user with an empty $HOME,  added the startkde line to 
> .xinitrc and had the same problem. I did notice that drkonqi is crashing and 
> writing out a .core file, so I'll see if gdb can tell me anything.
> Thanks,
> mnavarre

Read about something called kchildlock :

kchildlock

on an archlinux page:

https://bbs.archlinux.org/viewtopic.php?pid=940823

one solution is to remove kchildlock.  problem now becomes how does one do this?

Regards,

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

Re: Unable to start KDE4 on freebsd 7.4-RELEASE

[Matthew Navarre]

On Jun 5, 2011, at 3:17 PM, Antonio Olivares wrote:

> Mathew,
> 
> On Sun, Jun 5, 2011 at 3:53 PM, Matthew Navarre  wrote:
>> I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my 
>> installed ports in order and updated and installed/updated kde4-4.6.3 and 
>> all its dependancies. Xorg works ( i can run twm successfully), but trying 
>> to start kde bombs out. It looks like kded is barfing trying to get a  a 
>> lock on the shared cache.  Everything's up to date as of a portsnap fetch 
>> this morning. Output from startx follows. Hopefully someone can help, as I'm 
>> out of ideas.
>> 
>> Thanks,
>> mnavarre.
>> 
>> Script started on Sun Jun  5 13:42:25 2011
>> startx
>> xauth:  file /home/mnavarre/.serverauth.59871 does not exist
>> 
>> 
>> X.Org X Server 1.7.7
>> Release Date: 2010-05-04
>> X Protocol Version 11, Revision 0
>> Build Operating System: FreeBSD 7.4-RC3 i386
>> Current Operating System: FreeBSD reichlieu.lan 7.4-RELEASE FreeBSD 
>> 7.4-RELEASE #0: Thu Feb 17 03:51:56 UTC 2011 
>> r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>> Build Date: 28 May 2011  10:30:45PM
>> 
>> Current version of pixman: 0.21.4
>>Before reporting problems, check http://wiki.x.org
>>to make sure that you have the latest version.
>> Markers: (--) probed, (**) from config file, (==) default setting,
>>(++) from command line, (!!) notice, (II) informational,
>>(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>> (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun  5 13:42:25 2011
>> (==) Using default built-in configuration (30 lines)
>> (EE) Failed to load module "fbdev" (module does not exist, 0)
>> expected keysym, got XF86TouchpadToggle: line 123 of inet
>> kbuildsycoca4 running...
>> kbuildsycoca4(59915) KConfigGroup::readXdgListEntry: List entry MimeType in 
>> ".hidden/kommander.desktop" is not compliant with XDG standard (missing 
>> trailing semicolon).
>> startkde: Starting up...
>> Connecting to deprecated signal 
>> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
>> kded(59942)/kdeui (KIconLoader): Unable to find an appropriate lock to guard 
>> the shared cache.  This *should* be essentially impossible. :(
>> kded(59942)/kdeui (KIconLoader): Unable to perform initial setup, this 
>> system probably does not really support process-shared pthreads or 
>> semaphores, even though it claims otherwise.

>> 
>> startkde: Shutting down...
>> klauncher: Exiting on signal 1
>> kde3: not found
>> kde3: not found
>> startkde: Running shutdown scripts...
>> startkde: Done.
>> 
>> waiting for X server to shut down
>> 
>> 
>> Script done on Sun Jun  5 13:42:36 
>> 2011___
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
>> 
> 
> I can see that startx might be looking for kde 3, the line :
> 
> kde3: not found
> kde3: not found
> 

I was wondering about that myself, but KDE has never been installed on this 
machine until now. I thought I'd gotten all the old KDE cruft rm'ed from $HOME
> and you have kde 4.6.3 latest and greatest.
> 
> Question:
> Do you have
> exec startkde in ~/.xinitrc
> 
> or
> 
> exec /usr/local/kde4/bin/startkde in ~/.xinitrc

The kde4 line is in ~/.xinitrc
> 
> Because the first one is for kde 3 while the next one(above) is for
> kde 4.  If you try to create another user and the user is able to
> login, then it might be a problem with the old settings?
> 

I created a new user with an empty $HOME,  added the startkde line to .xinitrc 
and had the same problem. I did notice that drkonqi is crashing and writing out 
a .core file, so I'll see if gdb can tell me anything.
Thanks,
mnavarre
> Regards,
> 
> Antonio
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
> 

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

Re: Unable to start KDE4 on freebsd 7.4-RELEASE

[Antonio Olivares]

Mathew,

On Sun, Jun 5, 2011 at 3:53 PM, Matthew Navarre  wrote:
> I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my 
> installed ports in order and updated and installed/updated kde4-4.6.3 and all 
> its dependancies. Xorg works ( i can run twm successfully), but trying to 
> start kde bombs out. It looks like kded is barfing trying to get a  a lock on 
> the shared cache.  Everything's up to date as of a portsnap fetch this 
> morning. Output from startx follows. Hopefully someone can help, as I'm out 
> of ideas.
>
> Thanks,
> mnavarre.
>
> Script started on Sun Jun  5 13:42:25 2011
> startx
> xauth:  file /home/mnavarre/.serverauth.59871 does not exist
>
>
> X.Org X Server 1.7.7
> Release Date: 2010-05-04
> X Protocol Version 11, Revision 0
> Build Operating System: FreeBSD 7.4-RC3 i386
> Current Operating System: FreeBSD reichlieu.lan 7.4-RELEASE FreeBSD 
> 7.4-RELEASE #0: Thu Feb 17 03:51:56 UTC 2011     
> r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
> Build Date: 28 May 2011  10:30:45PM
>
> Current version of pixman: 0.21.4
>        Before reporting problems, check http://wiki.x.org
>        to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
>        (++) from command line, (!!) notice, (II) informational,
>        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun  5 13:42:25 2011
> (==) Using default built-in configuration (30 lines)
> (EE) Failed to load module "fbdev" (module does not exist, 0)
> expected keysym, got XF86TouchpadToggle: line 123 of inet
> kbuildsycoca4 running...
> kbuildsycoca4(59915) KConfigGroup::readXdgListEntry: List entry MimeType in 
> ".hidden/kommander.desktop" is not compliant with XDG standard (missing 
> trailing semicolon).
> startkde: Starting up...
> Connecting to deprecated signal 
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> kded(59942)/kdeui (KIconLoader): Unable to find an appropriate lock to guard 
> the shared cache.  This *should* be essentially impossible. :(
> kded(59942)/kdeui (KIconLoader): Unable to perform initial setup, this system 
> probably does not really support process-shared pthreads or semaphores, even 
> though it claims otherwise.
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPainter::begin: Paint device returned engine == 0, type: 2
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPainter::begin: Paint device returned engine == 0, type: 2
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPainter::begin: Paint device returned engine == 0, type: 2
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QPainter::begin: Paint device returned engine == 0, type: 2
> QPixmap: It is not safe to use pixmaps outside the GUI thread
> QObject: Cannot create children for a parent that is in a different thread.
> (Parent is KApplication(0xbfbfe35c), parent's thread is QThread(0x2a322050), 
> current thread is QThread(0x2a322c88)
> KGlobal::locale() must be called from the main thread before using i18n() in 
> threads. KApplication takes care of this. If not using KApplication, call 
> KGlobal::locale() during initialization.
> kded(59941): Communication problem with  "kded" , it probably crashed.
> Error message was:  "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name 
> org.kde.kded was not provided by any .service files" "
>
> KCrash: Application 'kded4' crashing...
> KCrash: Attempting to start /usr/local/kde4/lib/kde4/libexec/drkonqi from 
> kdeinit
> sock_file=/home/mnavarre/.kde4/socket-reichlieu.lan/kdeinit4__0
> kcminit(59944)/kdeui (KIconLoader): Unable

Unable to start KDE4 on freebsd 7.4-RELEASE

[Matthew Navarre]

I updated my FreeBSD box from 6.4 to 7.4 using freebsd-update, got my installed 
ports in order and updated and installed/updated kde4-4.6.3 and all its 
dependancies. Xorg works ( i can run twm successfully), but trying to start kde 
bombs out. It looks like kded is barfing trying to get a  a lock on the shared 
cache.  Everything's up to date as of a portsnap fetch this morning. Output 
from startx follows. Hopefully someone can help, as I'm out of ideas.

Thanks,
mnavarre.

Script started on Sun Jun  5 13:42:25 2011
startx
xauth:  file /home/mnavarre/.serverauth.59871 does not exist


X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.4-RC3 i386 
Current Operating System: FreeBSD reichlieu.lan 7.4-RELEASE FreeBSD 7.4-RELEASE 
#0: Thu Feb 17 03:51:56 UTC 2011 
r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Build Date: 28 May 2011  10:30:45PM
 
Current version of pixman: 0.21.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun  5 13:42:25 2011
(==) Using default built-in configuration (30 lines)
(EE) Failed to load module "fbdev" (module does not exist, 0)
expected keysym, got XF86TouchpadToggle: line 123 of inet
kbuildsycoca4 running...
kbuildsycoca4(59915) KConfigGroup::readXdgListEntry: List entry MimeType in 
".hidden/kommander.desktop" is not compliant with XDG standard (missing 
trailing semicolon). 
startkde: Starting up...
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kded(59942)/kdeui (KIconLoader): Unable to find an appropriate lock to guard 
the shared cache.  This *should* be essentially impossible. :( 
kded(59942)/kdeui (KIconLoader): Unable to perform initial setup, this system 
probably does not really support process-shared pthreads or semaphores, even 
though it claims otherwise. 
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPainter::begin: Paint device returned engine == 0, type: 2
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPainter::begin: Paint device returned engine == 0, type: 2
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPainter::begin: Paint device returned engine == 0, type: 2
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPainter::begin: Paint device returned engine == 0, type: 2
QPixmap: It is not safe to use pixmaps outside the GUI thread
QObject: Cannot create children for a parent that is in a different thread.
(Parent is KApplication(0xbfbfe35c), parent's thread is QThread(0x2a322050), 
current thread is QThread(0x2a322c88)
KGlobal::locale() must be called from the main thread before using i18n() in 
threads. KApplication takes care of this. If not using KApplication, call 
KGlobal::locale() during initialization.
kded(59941): Communication problem with  "kded" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.ServiceUnknown" : " "The name 
org.kde.kded was not provided by any .service files" " 

KCrash: Application 'kded4' crashing...
KCrash: Attempting to start /usr/local/kde4/lib/kde4/libexec/drkonqi from 
kdeinit
sock_file=/home/mnavarre/.kde4/socket-reichlieu.lan/kdeinit4__0
kcminit(59944)/kdeui (KIconLoader): Unable to find an appropriate lock to guard 
the shared cache.  This *should* be essentially impossible. :( 
kcminit(59944)/kdeui (KIconLoader): Unable to perform initial setup, this 
system probably does not really support process-shared pthreads or semaphores, 
even though it claims otherwise. 
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI th

Re: Unable to boot installer

[Daniel Staal]

--As of May 15, 2011 5:08:10 AM +0200, Cybil Courraud is alleged to have 
said:



I met the same problem with my x220 which is not resolved but you can
follow this workaround:

1 - Plug an external USB keyboard
2 - boot with a memstick with 8.2
3 - In the loader:
 set hint.atkbd.0.disabled=1
 boot
4 - Follow install via network or other
5 - Setup BIOS: Config > USB UEFI BIOS > disabled
6 - reboot


Thanks, that got me going.  Any idea if this is fixed in -CURRENT?  (I may 
try it anyway.)



You could try with a CD, directly without UEFI, it may work as is (I
didn't burn it for the exercise).


That would be a problem unless you have a dock; turning off the USB UEFI 
BIOS makes it unable to boot from any USB device.


Daniel T. Staal

---
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"