date:20120130

On 30/01/2012 13:57, hvn wrote:
 Using v.FreeBSD 8.2, I'm trying to install Firefox 9 by pkg_add -r 
 firefox. According to the docs, this should work. However, instead of v9 
 it tries to install v 3.6 which goes wrong because of dependency 
 conflicts. Any idea on how to solve this or what goes wrong?

What FTP URL are you connecting to in order to download the firefox
package?  Firefox 9.0 postdates FreeBSD 8.2 release, so it won't be in
the packages-8.2-release collection:

ftp pwd
Remote directory: /pub/FreeBSD/ports/amd64/packages-8.2-release/Latest
ftp ls firefox.tbz
229 Entering Extended Passive Mode (|||51545|)
150 Opening ASCII mode data connection for '/bin/ls'.
lrwxr-xr-x  1 1006  1006  27 Jan 20  2011 firefox.tbz -
../All/firefox-3.6.13,1.tbz
226 Transfer complete.

However, if you use the packages-8-stable collection, you should get
firefox-9:

ftp pwd
Remote directory: /pub/FreeBSD/ports/amd64/packages-8-stable/Latest
ftp ls firefox.tbz
229 Entering Extended Passive Mode (|||63627|)
150 Opening ASCII mode data connection for '/bin/ls'.
lrwxr-xr-x  1 1006  1006  26 Jan 17 21:28 firefox.tbz -
../All/firefox-9.0.1,1.tbz
226 Transfer complete.

Packages compiled for FreeBSD 8.2-STABLE should work perfectly well on
8.2-RELEASE-pX with the possible exception of a few things like lsof
that go poking directly into kernel memory structures.

Read about the PACKAGESITE environment variable in pkg_add(1)

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: problem installing Firefox using pkg_add -r

2012-01-30 Thread hvn

On Mon, 30 Jan 2012 14:25:42 +, Matthew Seaman wrote:

 On 30/01/2012 13:57, hvn wrote:
 Using v.FreeBSD 8.2, I'm trying to install Firefox 9 by pkg_add -r
 firefox. According to the docs, this should work. However, instead of
 v9 it tries to install v 3.6 which goes wrong because of dependency
 conflicts. Any idea on how to solve this or what goes wrong?
 
 What FTP URL are you connecting to in order to download the firefox
 package?  Firefox 9.0 postdates FreeBSD 8.2 release, so it won't be in
 the packages-8.2-release collection:

The FTP URL is ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-
release/Latest/
So this effectively means I should upgrade or do a clean install. I did 
try to install PC-BSD 9 on an x64, but the BIOS somehow doesn't like the 
partitioning. This 8.2 runs on an old PIII with 500 MB RAM (xfce), so not 
really suitable for demanding stuff.


___
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: Trouble upgrading packages after 9.0 upgrade

On Sun, Jan 22, 2012 at 8:26 PM, Joshua Isom jri...@gmail.com wrote:

It should be 9.0-release. I suspect a problem with pkg_upgrade any not
FreeBSD.

Install misc/compat8x and you won't need to upgrade all the ports at once,
they'll still work.

Yes But I want to be able to upgrade the binary packages all at once. The
fact is, it shouldnt be that hard. This should work right out of the box. I
should not have to configure anything for this to work. Why can't FreeBSD
make something so basic work out of the box? It is important for having a
useable OS to be able to install and upgrade everythinbg from binary
packages out of the box like can be done on Ubuntu.

I dont know whats wrong with this freebsd 9.0-release stuff or how to fix
that error message. Your response does not tell me how to fix it. The thing
is, I should not have to fix this because it should work out of the box.

On 1/22/2012 12:42 PM, David Jackson wrote:

I upgraded to 9.0. But when i use pkg_upgrade -a, i get this:
ftp://ftp.freebsd.org/pub/**FreeBSD/ports/i386/packages-9-**release/INDEXftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-release/INDEX:
File
unavailable. Why? Also portupgrade -PP -a also fails spectacurly. Why. It
seems like it is getting more and more difficult to use FreeBSD. To
upgrade
to the most recent packages should be a one step process of typing a
simple
upgrade command.it should work out of the box. It seems like the
difficulties of getting FreeBSD to work make it unuseable for most people.
__**_
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-**
unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org

__**_
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-**
unsubscr...@freebsd.org 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: Problems with libz since libz.so.5 is gone...

2012-01-30 Thread Pierre-Luc Drouin

On Fri, Jan 27, 2012 at 6:19 PM, Pierre-Luc Drouin pldro...@pldrouin.netwrote:



 On Fri, Jan 27, 2012 at 11:44 AM, Pierre-Luc Drouin pldro...@pldrouin.net
  wrote:



 On Fri, Jan 27, 2012 at 10:41 AM, Pierre-Luc Drouin 
 pldro...@pldrouin.net wrote:



 On Fri, Jan 27, 2012 at 9:58 AM, Pierre-Luc Drouin 
 pldro...@pldrouin.net wrote:



 On Fri, Jan 27, 2012 at 9:55 AM, Pierre-Luc Drouin 
 pldro...@pldrouin.net wrote:

 On Thu, Jan 26, 2012 at 5:40 PM, Dan Nelson 
 dnel...@allantgroup.comwrote:

 In the last episode (Jan 26), Pierre-Luc Drouin said:
  so various ports, in particular the java ports, are giving me
 headaches
  since /lib/libz.so.5 was replaced by /lib/libz.so.6.  I managed to
 update
  most of my ports, but the binary java ports, such as diablo-jdk16,
 are now
  installing broken binary files.  Even if I put an entry such as
 
  libz.so.4 libz.so.6
 
  in /etc/libmap.conf

 libmap (or symlinking) only works for libraries that have a
 compatible ABI.
 The version number of libz was bumped precisely because the ABI
 changed :)

 Install the misc/compat8x port to get libz.so.5 back until you can
 replace
 diablo-jdk16 with openjdk6.

 --
Dan Nelson
dnel...@allantgroup.com


 Hi,

 sorry I tried to install compat8x but it did not solve the problem, as
 that package does not install libz.so.5

 Thanks


 Sorry it did install libz.so.5, but diablo-jdk16 is still crashing for
 some reason...


 Ok, so I installed linux-sun-jdk16 that does not seem to get broken by
 FreeBSD 9, then I hacked the port Makefile for openjdk16 to bootstrap
 itself with linux-sun-jdk16 and so far it seems to be compiling fine...


 That solution did ont work either because jni_md.h is missing with
 linux-sun-jdk16. So now I am trying to compile gcj by hand and use it to
 bootstrap openjdk. This chicken and egg problem is getting really
 annoying...


 So I discovered that openjdk cannot be bootstrapped with gcj, but then I
 discovered that there was an openjdk6 package available for FreeBSD 9
 (generated on January 15th). I installed it, but event that one does not
 work. I am wondering if the problem is not with vsnprintf instead of libz:


 ---  T H R E A D  ---

 Current thread (0x2863d800):  JavaThread Unknown thread [_thread_in_vm,
 id=100896, stack(0xbf9af000,0xbf9ff000)]

 siginfo:si_signo=SIGBUS: si_errno=0, si_code=3 (BUS_OBJERR),
 si_addr=0x2812718c

 Registers:
 EAX=0xbf9fddb0, EBX=0x281de884, ECX=0x28c77737, EDX=0xbf9fe5a0
 ESP=0xbf9fdc48, EBP=0xbf9fdd50, ESI=0xbf9fe738, EDI=0x07d0
 EIP=0x2812718c, EFLAGS=0x00010206

 Top of Stack: (sp=0xbf9fdc48)
 0xbf9fdc48:   bf9fdf44 bf9fe76c bf9fe0f0 2889545e
 0xbf9fdc58:   bf9fe76c 0001 0003 28cd92d4
 0xbf9fdc68:    bf9fe76c bf9fe0f0 28bd5b19
 0xbf9fdc78:   bf9fe76c 00e1 28cd6108 28cd6208
 0xbf9fdc88:   b7f9  fff8 0001
 0xbf9fdc98:   bf9fdefc bf9fdd70 bf9fdd4c 28cd92d4
 0xbf9fdca8:   28427284 28427270 bf9fdcc0 28c35c73
 0xbf9fdcb8:   28cd92d4 bf9fdee0 bf9fdcf0 2896d834

 Instructions: (pc=0x2812718c)
 0x2812716c:   90 90 90 90 55 89 e5 53 57 56 81 ec fc 00 00 00
 0x2812717c:   e8 00 00 00 00 5b 81 c3 03 77 0b 00 66 0f ef c0
 0x2812718c:   0f 29 45 d8 0f 29 45 c8 0f 29 45 b8 0f 29 45 a8
 0x2812719c:   0f 29 45 98 0f 29 45 88 0f 29 85 78 ff ff ff 0f

 Register to memory mapping:

 EAX=0xbf9fddb0 is pointing into the stack for thread: 0x2863d800
 EBX=0x281de884: __nsdefaultsrc+0xd38 in /lib/libc.so.7 at 0x280da000
 ECX=0x28c77737: _ZTV18AdaptiveSizePolicy+0x1b7 in
 /usr/local/openjdk6/jre/lib/i386/client/libjvm.so at 0x2880
 EDX=0xbf9fe5a0 is pointing into the stack for thread: 0x2863d800
 ESP=0xbf9fdc48 is pointing into the stack for thread: 0x2863d800
 EBP=0xbf9fdd50 is pointing into the stack for thread: 0x2863d800
 ESI=0xbf9fe738 is pointing into the stack for thread: 0x2863d800
 EDI=0x07d0 is an unknown value


 Stack: [0xbf9af000,0xbf9ff000],  sp=0xbf9fdc48,  free space=315k

 Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
 code)
 C  [libc.so.7+0x4d18c]  vsnprintf+0x1c

 I compiled FreeBSD (world+kernel) with clang. Is that possible that the
 clang compilation of FreeBSD makes any native JDK (jdk16, openjdk6, etc)
 unusable?

 Thanks!


So it seems that vsnprintf is indeed broken on FreeBSD 9 when it is built
with clang. I submitted a problem report...
___
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: problem installing Firefox using pkg_add -r

On 30/01/2012 14:43, hvn wrote:
 On Mon, 30 Jan 2012 14:25:42 +, Matthew Seaman wrote:
 
 On 30/01/2012 13:57, hvn wrote:
 Using v.FreeBSD 8.2, I'm trying to install Firefox 9 by pkg_add -r
 firefox. According to the docs, this should work. However, instead of
 v9 it tries to install v 3.6 which goes wrong because of dependency
 conflicts. Any idea on how to solve this or what goes wrong?

 What FTP URL are you connecting to in order to download the firefox
 package?  Firefox 9.0 postdates FreeBSD 8.2 release, so it won't be in
 the packages-8.2-release collection:
 
 The FTP URL is ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.2-
 release/Latest/
 So this effectively means I should upgrade or do a clean install. I did 
 try to install PC-BSD 9 on an x64, but the BIOS somehow doesn't like the 
 partitioning. This 8.2 runs on an old PIII with 500 MB RAM (xfce), so not 
 really suitable for demanding stuff.

Well, if you want to go through all the palaver of upgrading the OS,
then it is up to you.  However, if prefer not to spend all that time,
and just update your installed pkgs, you could do this:

   setenv PACKAGESITE
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All

(csh-like shells)

or

   export
PACKAGESITE=ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/All

(sh-like shells)

Now, you will have to update the packages that firefox depends on.
That's a pretty tedious chore if done manually.  The sort of boring,
repetitive task that computers excel at, given appropriate programming.
Which in this case (IMHO) means portmaster(8).  Once you've set
PACKAGESITE as above, install portmaster:

   # pkg_add -r portmaster-3.11.tbz
   # rehash(if using csh style shell)

Then use portmaster to update dependencies as necessary and install the
firefox-9 port -- obviously, make sure you have good backups before
doing this, even though portmaster does create a backup package of
everything it updates.

   # portmaster -PP -w www/firefox

'-PP' says to only use pre-compiled packages.

'-w' says to keep a copy of any updated shared libraries on-line, a
helpful anti-foot-shooting move.  Actually, if the update starts
replacing low-level stuff which a great number of packages depend on,
you might find it more productive to just upgrade everything (portmaster
-PP -a).  You will be getting about 11 months worth of updates all in
one go in that case, which is going to affect lots of what you have
installed.  If in doubt, please feel free to ask again here.

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

Setting up a syslog server in a jail

2012-01-30 Thread bsd

Hello, 

I would like to setup a syslog server inside a jail 
I have setup couple of other jail and they are already working as a DNS server 
and a HTTP server. 

The next step would be to configure a new jail as a syslog server. 

I have the following parameters : 

jail_enable=YES
jail_mount_enable=YES
jail_set_hostname_allow=NO
jail_sysvipc_allow=YES # for syslog et postgres
jail_socket_unixiproute_only=NO
jail_list=ns0 lacoste logjail
jail_logjail_hostname=logjail.osnet.eu
jail_logjail_ip=1.2.3.4
jail_logjail_rootdir=/jails/j/logjail
jail_logjail_devfs_enable=YES


I have also setup in /etc/sysctl.conf : 

security.jail.allow_raw_sockets=1

• I can ping the remote host (the one sending IP datagram)
• I can dig any domain


I am still not able to get the log correctly sent to the specified jail… ?? 


Any idea ? 

––
- Grégory Bernard Director -
--- www.osnet.eu ---
-- Your provider of OpenSource appliances --
––
OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO

___
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: Setting up a syslog server in a jail

On 30/01/2012 15:40, bsd wrote:
 I am still not able to get the log correctly sent to the specified jail… ?? 

Are you running syslogd in the host environment?  If so, it's probably
bound to INADDR_ANY and thus pre-empted your jailed syslog from binding
to a network port.

Try adding

syslogd_flags=-ss

in the host environment.  That prevents syslogd from listening via a
network port at all, although it will still happily log messages from
the local machine.

Use sockstat(1) to diagnose what addresses syslogd(8)s have bound to.

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: Setting up a syslog server in a jail

2012-01-30 Thread bsd

Le 30 janv. 2012 à 16:59, Matthew Seaman a écrit :

 On 30/01/2012 15:40, bsd wrote:
 I am still not able to get the log correctly sent to the specified jail… ?? 
 
 Are you running syslogd in the host environment?

Yes I am running it both in the host and jail environment. 

  If so, it's probably
 bound to INADDR_ANY and thus pre-empted your jailed syslog from binding
 to a network port.
 
 Try adding
 
 syslogd_flags=-ss

Ok, I have the following sockstat on the host environment : 

surf:root 17:09:02 ~ # sockstat | grep sysl
root syslogd3176  4  dgram  /var/run/log
root syslogd3176  5  dgram  /var/run/logpriv
root syslogd3153  4  dgram  /var/run/log
root syslogd3153  5  dgram  /var/run/logpriv
root syslogd3153  6  udp4   1.2.3.6:514 *:*
root syslogd2191  4  dgram  /var/run/log
root syslogd2191  5  dgram  /var/run/logpriv
root syslogd2191  6  udp4   1.2.3.5:514 *:*
root syslogd1947  4  dgram  /var/run/log
root syslogd1947  5  dgram  /var/run/logpriv
root syslogd1947  6  dgram  /var/run/log
root syslogd1947  7  dgram  /var/named/var/run/log
root syslogd1947  8  udp4   1.2.3.4:514 *:*


My syslog server is supposed to be on 1.2.3.6 

In the jail environment I have : 

logjail# sockstat | grep syslo
root syslogd3153  4  dgram  /var/run/log
root syslogd3153  5  dgram  /var/run/logpriv
root syslogd3153  6  udp4   1.2.3.6:514 *:*

… But still no log from outside the jail… ?  



 
 in the host environment.  That prevents syslogd from listening via a
 network port at all, although it will still happily log messages from
 the local machine.
 
 Use sockstat(1) to diagnose what addresses syslogd(8)s have bound to.
 


Thanks for your answers

   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
 


––
- Grégory Bernard Director -
--- www.osnet.eu ---
-- Your provider of OpenSource appliances --
––
OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO

___
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

Very strange netstat -rna output

2012-01-30 Thread Dave

Hello,
 I'm having a problem on a server of mine that is acting as a bridge,
that whenever I download from the server itself it's very slow. From
machines going through it's bridge there are no problems.

When looking for what could be the cause, I had a look at my routing
table and saw the following --

10.10.10.1   0.12.da.44.e4.0UHLW20 bridge   1200
10.10.10.2   0.14.c2.60.85.75   UHLW1   87 bridge   1110
10.10.10.7   0.17.35.13.60.10   UHLW1  373lo0
10.10.10.30  0.25.90.1.60.83UHLW20 bridge   1110

As you can see the second column which usually shows a MCA is showing
some rather strange output? What could be the cause of this?

Thanks
Dave
___
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

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

still waiting after 60 seconds for xpt_config

2012-01-30 Thread Mike.

I installed 9.0 on my test ThinkPad.  During the boot-up process, I see
the following message after a pause in the boot-up process:

run_interrupt_driven_hooks: still waiting after 60 seconds for
xpt_config


A quick spin through google showed the message occurred in older
versions of FreeBSD, though I did not see it when I installed 7.x and
8.x on the Thinkpad.  I didn't see any resolutions to the problem.

Is the message FreeBSD's way of telling me there is something wrong
with the ThinkPad?  Or is it a problem with FreeBSD?   I don't know
where to start looking for the cause of the message, as I do not know
what the message is trying to tell me.






=== complete dmesg ===

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.0-RELEASE #0: Tue Jan  3 07:15:25 UTC 2012
r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1698.60-MHz 686-class
CPU)
  Origin = GenuineIntel  Id = 0xf24  Family = f  Model = 2  Stepping
= 4
  Features=0x3febf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MC
A,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM
real memory  = 1073741824 (1024 MB)
avail memory = 1031327744 (983 MB)
kbd1 at kbdmux0
acpi0: IBM TP-1G on motherboard
acpi_ec0: Embedded Controller: GPE 0x1c, ECDT port 0x62,0x66 on acpi0
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, 3ff0 (3) failed
Timecounter ACPI-fast frequency 3579545 Hz quality 900
acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0
cpu0: ACPI CPU on acpi0
acpi_lid0: Control Method Lid Switch on acpi0
acpi_button0: Sleep Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
agp0: Intel 82845 host to AGP bridge on hostb0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
vgapci0: VGA-compatible display port 0x3000-0x30ff mem
0xe800-0xefff,0xd010-0xd010 irq 11 at device 0.0 on
pci1
uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port
0x1800-0x181f irq 11 at device 29.0 on pci0
usbus0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0
uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port
0x1820-0x183f irq 11 at device 29.1 on pci0
usbus1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1
uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port
0x1840-0x185f irq 11 at device 29.2 on pci0
usbus2: Intel 82801CA/CAM (ICH3) USB controller USB-C on uhci2
pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0
pci2: ACPI PCI bus on pcib2
cbb0: RF5C476 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at
device 0.0 on pci2
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
cbb1: RF5C476 PCI-CardBus Bridge mem 0x5010-0x50100fff irq 11 at
device 0.1 on pci2
cardbus1: CardBus bus on cbb1
pccard1: 16-bit PCCard bus on cbb1
fwohci0: Ricoh R5C552 mem 0xd0201000-0xd02017ff irq 11 at device 0.2
on pci2
fwohci0: OHCI version 1.0 (ROM=0)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:06:1b:00:10:00:6d:38
fwohci0: Phy 1394a available S400, 2 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0: IEEE1394(FireWire) bus on fwohci0
dcons_crom0: dcons configuration ROM on firewire0
dcons_crom0: bus_addr 0x14a
fwe0: Ethernet over FireWire on firewire0
if_fwe0: Fake Ethernet address: 02:06:1b:00:6d:38
fwe0: Ethernet address: 02:06:1b:00:6d:38
fwip0: IP over FireWire on firewire0
fwip0: Firewire address: 00:06:1b:00:10:00:6d:38 @ 0xfffe,
S400, maxrec 2048
fwohci0: Initiate bus reset
fwohci0: fwohci_intr_core: BUS reset
fwohci0: fwohci_intr_core: node_id=0x, SelfID Count=1,
CYCLEMASTER mode
fxp0: Intel 82801CAM (ICH3) Pro/100 VE Ethernet port 0x8000-0x803f
mem 0xd020-0xd0200fff irq 11 at device 8.0 on pci2
miibus0: MII bus on fxp0
inphy0: i82562ET 10/100 media interface PHY 1 on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto,
auto-flow
fxp0: Ethernet address: 00:0e:9b:2c:c7:f6
isab0: PCI-ISA bridge at device 31.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel ICH3 UDMA100 controller port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f at device 31.1 on
pci0
ata0: ATA channel 0 on atapci0
ata1: ATA channel 1 on atapci0
pci0: serial bus, SMBus at device 31.3 (no driver attached)
pcm0: Intel ICH3 (82801CA) port 0x1c00-0x1cff,0x18c0-0x18ff irq 11 at
device 31.5 on pci0
pcm0: Analog Devices AD1881A AC97 Codec
pci0: simple comms, generic modem at device 31.6 (no driver attached)
acpi_tz0: Thermal Zone on acpi0
attimer0: AT timer port 0x40-0x43 irq 0 on acpi0
Timecounter i8254 frequency 1193182 Hz quality 0
Event timer i8254 frequency 1193182 Hz quality 100
atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0
Event timer RTC frequency 32768 Hz

RIP routing protocol implementation is FreeBSD?


Hi there,

does anyone know if there's an implementation of the RIP version 2 
routing protocol in FreeBSD???



I would like to use it to exchange routes with my Cisco 857W router as 
the BSD machine will provide routing for a virtual test network in VBox.



I did check out the handbook for the enable_routerd=YES and have used 
that before as default gateway of 'last-resort' with NAT but never RIP 
as don't wana use NAT in this case.



OpenBSD definitely has it but since am more familiar with FreeBSD I 
thought let's try here first :-)


Can anyone help me out?


Regards,


Kaya
___
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: make release custom kernel conf not found

2012-01-30 Thread Rick Miller

Thanks Rob...

I put the kernel conf file in the source tree as opposed to linking to
it and it certainly did compile the custom kernel.

What confuses me (not that I expect you to have the answer) is that
Chapter 9 of the handbook has a tip that recommends keeping the kernel
config in /root/kernels and symlinking to it from the source tree.  If
it doesn't work, why is there a tip recommending this practice?

On Sun, Jan 29, 2012 at 10:14 PM, Rob Farmer rfar...@predatorlabs.net wrote:
 On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote:
 Hi All,

 I am performing a `make release` to build a new release with a custom
 kernel.  The `make release` fails with the following error:

 cd /usr/src/release/..;  make TARGET_ARCH=amd64 TARGET=amd64
 KERNCONF=MYKERNEL kernel  DESTDIR=/R/stage/kernels KODIR=/MYKERNEL
 ERROR: Missing kernel configuration file(s) (MYKERNEL).
 *** Error code 1

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

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

 Stop in /usr/src/release.
 + umount /dev
 *** Error code 1

 Stop in /usr/src/release.

 I have the kernel config at /root/kernels/MYKERNEL and
 /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config.
 The applicable environment variables are set in my .profile as
 follows:

 BUILDNAME=8.2-RELEASE-MYKERNEL-1.1
 CHROOTDIR=/app/release
 CVSROOT=/home/cvs
 EXTPORTSDIR=/usr/ports
 EXTSRCDIR=/usr/src
 KERNELS=GENERIC MYKERNEL
 MAKE_DVD=YES
 NODOC=YES
 NO_FLOPPIES=YES

 I am unsure how to get `make release` to realize the location of the
 kernel config.  Also, I notice that in the command to make the kernel,
 DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the
 location where I want the release to be built) is /app/release.

 I am wondering if someone knows how I may resolve the issue so I can
 get the release built.  I appreciate any advice and feedback.  Thanks.


 The kernel is built inside the chroot, so all paths are really
 /app/release/whatever. Your symlink points to
 /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of
 the symlink and copy the actual file into your EXTSRCDIR before
 starting the make release; alternately you could use the LOCAL_PATCHES
 or LOCAL_SCRIPT variables to import it.

 --
 Rob Farmer



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

Re: RIP routing protocol implementation is FreeBSD?

2012-01-30 Thread Michael Sierchio

On Mon, Jan 30, 2012 at 10:33 AM, Kaya Saman kayasa...@gmail.com wrote:
 Hi there,

 does anyone know if there's an implementation of the RIP version 2 routing
 protocol in FreeBSD???

man routed

 The routed utility is a daemon invoked at boot time to manage the network
 routing tables.  It uses Routing Information Protocol, RIPv1 (RFC 1058),
 RIPv2 (RFC 1723), and Internet Router Discovery Protocol (RFC 1256) to
 maintain the kernel routing table.

router_enable=YES in /etc/rc.conf

this has nothing to do with NAT, btw.
___
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: RIP routing protocol implementation is FreeBSD?

2012-01-30 Thread Eric Masson

Kaya Saman kayasa...@gmail.com writes:

Hi,

 does anyone know if there's an implementation of the RIP version 2
 routing protocol in FreeBSD???

man 8 routed

 I did check out the handbook for the enable_routerd=YES

I'd try routed_enable = YES instead.

Regards

Éric Masson

-- 
 je crosspost sur fr rec moto pour ce triste modéle d'intolérance. [...]
 PS :Désolé mon logiciel de news ne permet pas les follow up et je n'en
 changerai certainement pas pour vous etre agréable.
 -+- CC in Guide du Neuneu Usenet - Bien configurer son incompétence -+-
___
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: make release custom kernel conf not found

2012-01-30 Thread Lowell Gilbert

Rick Miller vmil...@hostileadmin.com writes:

 Thanks Rob...

 I put the kernel conf file in the source tree as opposed to linking to
 it and it certainly did compile the custom kernel.

 What confuses me (not that I expect you to have the answer) is that
 Chapter 9 of the handbook has a tip that recommends keeping the kernel
 config in /root/kernels and symlinking to it from the source tree.  If
 it doesn't work, why is there a tip recommending this practice?

It works fine; sounds like you just don't understand what a chroot is. 

Once a process is chroot'd to /app/release/, its idea of /root/kernels
is what non-chroot'd processes see as /app/release/kernels. It can't see
*any* files that aren't under /app/release. I would tend to recommend
adding to your build script a command that copies the kernel file into
the chroot before starting the chroot, but I'm sure others have other
preferred approaches.

 - Lowell
___
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: RIP routing protocol implementation is FreeBSD?

2012-01-30 Thread Eric Masson

Eric Masson e...@free.fr writes:

Sorry, Followup to myself.

 I'd try routed_enable = YES instead.

router_enable = YES as Michael stated in another post.

Regards

Éric Masson

-- 
  et me dis quil y a eu une merde avec le serveur truc machin et que ca a
  fait un gros server crash. OU ets la merde?
 Fallait choisir le serveur bidule, c'est pour ça.
 -+- EJ in guide du linuxien pervers - Tout ça c'est de la bidouille -+-
___
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: RIP routing protocol implementation is FreeBSD?


On 01/30/2012 06:47 PM, Michael Sierchio wrote:

On Mon, Jan 30, 2012 at 10:33 AM, Kaya Samankayasa...@gmail.com  wrote:

Hi there,

does anyone know if there's an implementation of the RIP version 2 routing
protocol in FreeBSD???

man routed

  The routed utility is a daemon invoked at boot time to manage the network
  routing tables.  It uses Routing Information Protocol, RIPv1 (RFC 1058),
  RIPv2 (RFC 1723), and Internet Router Discovery Protocol (RFC 1256) to
  maintain the kernel routing table.

router_enable=YES in /etc/rc.conf

this has nothing to do with NAT, btw.


Thanks for the response. sorry I think I wasn't getting my point 
through clearly enough.


Am Cisco Engineer so know the difference between NAT, PAT, Static 
routing and dynamic routing ;-)


Yep I read about it in the handbook and yes I have used it before but 
not for dynamic routing.


The NAT'ing is what I did previously and was just mentioning what I 
'had' used before. which was everything but dynamic routing on 
FreeBSD 8.0 :-)



P.s. sorry if what I'm trying to say isn't getting out clearly enough :-)


Regards,


Kaya
___
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: RIP routing protocol implementation is FreeBSD?


On 01/30/2012 06:53 PM, Eric Masson wrote:

Kaya Samankayasa...@gmail.com  writes:

Hi,


does anyone know if there's an implementation of the RIP version 2
routing protocol in FreeBSD???

man 8 routed


I did check out the handbook for the enable_routerd=YES

I'd try routed_enable = YES instead.

Regards

Éric Masson



Syntax blooper. It's sometimes hard to remember 'EVERYTHING' but 
once I see the /etc/rc.conf file I will know what is needed and how it's 
used :-)



Thanks for the correction though.


Regards,

Kaya
___
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: still waiting after 60 seconds for xpt_config

2012-01-30 Thread Chris Whitehouse


On 30/01/2012 17:41, Mike. wrote:

I installed 9.0 on my test ThinkPad.  During the boot-up process, I see
the following message after a pause in the boot-up process:

run_interrupt_driven_hooks: still waiting after 60 seconds for
xpt_config


A quick spin through google showed the message occurred in older
versions of FreeBSD, though I did not see it when I installed 7.x and
8.x on the Thinkpad.  I didn't see any resolutions to the problem.

Is the message FreeBSD's way of telling me there is something wrong
with the ThinkPad?  Or is it a problem with FreeBSD?   I don't know
where to start looking for the cause of the message, as I do not know
what the message is trying to tell me.


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

includes a workaround, hopefully it will work for you:

disable firewire (IEEE 1394) in BIOS.
rebuild kernel with device sbp disabled and install it.
reboot
if it works re-enable firewire in BIOS.

The reason you didn't see it in some versions is because GENERIC was 
shipped with sbp disabled (I think).


Someone is/was working on a fix.

Chris
___
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: Port upgrade change ownership of port installation directory and files

2012-01-30 Thread Lubomir Matousek








On 1/30/12 2:24 PM, Lubomir Matousek wrote:

I changed apache default user from www to wbserv.

I changed also file ownership from www to wbserv.


Is there any way for portupgrade, that the ownership of installed port
files remains the same? It means wbserv?





On 30.1.2012 14:52, Damien Fleuriot wrote:


You'll want to be more specific, what files do you refer to ?

If you're talking about the binaries and modules, they're owned by root
so this is a non issue.

If you're talking about the configuration files, they're also owned by root.

If you're talking about SSL certificates you've installed them yourself
and a portupgrade will not change their perms.

If you're talking about logfiles, these are your responsibility and,
again, the port won't change them.

Last, if you're talking about your HTML/php/whatever files, these are
also your responsiblity and untouched by the port.



Sorry for not being more specific.

After port upgrade
portupgrade -rR squirrealmail

I have to
chown -R wbserv:wbserv /var/spool/sqirrelmail

Or after upgrade of postfixadmin:
 portupfrade -rR postfixadmin
I have to change perms again:
 chown -R wbserv:wbserv /usr/local/www/postfixadmin

What is the best aprroach? To specify correct file ownership at 
make.conf? How can I do that?


Lubomir
___
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: RIP routing protocol implementation is FreeBSD?


On 01/30/2012 07:11 PM, Eric Masson wrote:

Eric Massone...@free.fr  writes:

Sorry, Followup to myself.


I'd try routed_enable = YES instead.

router_enable = YES as Michael stated in another post.

Regards

Éric Masson



The generic syntax of rc.conf is like so (using mine as example):

zfs_enable=YES
nfs_server_flags=-a -t -n 4
nfs_server_enable=YES
rpc_statd_enable=YES
rpc_lockd_enable=YES
rpcbind_enable=YES
mountd_enable=YES
mountd_flags=-r
munin_node_enable=NO
zabbix_server_enable=NO
zabbix_agentd_enable=NO
icecast_enable=NO
darkice_enable=NO
fail2ban_enable=YES

implying:

routerd_enable=YES


:-) :-) :-)


Best regards,


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

NFS Share with whitespace in its name

2012-01-30 Thread Scott Sanders

In the Linux NFS server it's permissible to share a directory with
whitespace in the directory name by wrapping the first field in the exports
list with double-quotes. This does not seem to be true with the FreeBSD NFS
server. Is there a way to share a directory with spaces in the name?

Thanks in advance,

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

On Mon, 30 Jan 2012 12:52:07 -0500
David Jackson djackson...@gmail.com 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

Re: Setting up a syslog server in a jail [SOLVED]

2012-01-30 Thread bsd


Le 30 janv. 2012 à 17:15, bsd a écrit :

 Le 30 janv. 2012 à 16:59, Matthew Seaman a écrit :
 
 On 30/01/2012 15:40, bsd wrote:
 I am still not able to get the log correctly sent to the specified jail… ?? 
 
 Are you running syslogd in the host environment?
 
 Yes I am running it both in the host and jail environment. 
 
 If so, it's probably
 bound to INADDR_ANY and thus pre-empted your jailed syslog from binding
 to a network port.
 
 Try adding
 
 syslogd_flags=-ss
 
 Ok, I have the following sockstat on the host environment : 
 
 surf:root 17:09:02 ~ # sockstat | grep sysl
 root syslogd3176  4  dgram  /var/run/log
 root syslogd3176  5  dgram  /var/run/logpriv
 root syslogd3153  4  dgram  /var/run/log
 root syslogd3153  5  dgram  /var/run/logpriv
 root syslogd3153  6  udp4   1.2.3.6:514 *:*
 root syslogd2191  4  dgram  /var/run/log
 root syslogd2191  5  dgram  /var/run/logpriv
 root syslogd2191  6  udp4   1.2.3.5:514 *:*
 root syslogd1947  4  dgram  /var/run/log
 root syslogd1947  5  dgram  /var/run/logpriv
 root syslogd1947  6  dgram  /var/run/log
 root syslogd1947  7  dgram  /var/named/var/run/log
 root syslogd1947  8  udp4   1.2.3.4:514 *:*
 
 
 My syslog server is supposed to be on 1.2.3.6 
 
 In the jail environment I have : 
 
 logjail# sockstat | grep syslo
 root syslogd3153  4  dgram  /var/run/log
 root syslogd3153  5  dgram  /var/run/logpriv
 root syslogd3153  6  udp4   1.2.3.6:514 *:*
 
 … But still no log from outside the jail… ?  
 
 
 
 
 in the host environment.  That prevents syslogd from listening via a
 network port at all, although it will still happily log messages from
 the local machine.
 
 Use sockstat(1) to diagnose what addresses syslogd(8)s have bound to.
 
 
 
 Thanks for your answers

Problem was with the IP I was listening on. 

Was the wrong one. 

Found that using the debug option of syslog -d 

Very straight forward after debug was enable. 

 
  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
 
 
 
 ––
 - Grégory Bernard Director -
 --- www.osnet.eu ---
 -- Your provider of OpenSource appliances --
 ––
 OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO
 
 ___
 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


––
- Grégory Bernard Director -
--- www.osnet.eu ---
-- Your provider of OpenSource appliances --
––
OSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetOSnetO

___
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: still waiting after 60 seconds for xpt_config

2012-01-30 Thread Mike.

On 1/30/2012 at 7:26 PM Chris Whitehouse wrote:

|http://www.freebsd.org/cgi/query-pr.cgi?pr=136327
|
|includes a workaround, hopefully it will work for you:
|
|disable firewire (IEEE 1394) in BIOS.
|rebuild kernel with device sbp disabled and install it.
|reboot
|if it works re-enable firewire in BIOS.
|
|The reason you didn't see it in some versions is because GENERIC was 
|shipped with sbp disabled (I think).
|
|Someone is/was working on a fix.
 =


Thanks for the quick reply.   In 9.0, it looks like sbp is commented
out in the GENERIC kernel.

...
# FireWire support
device  firewire# FireWire bus code
# sbp(4) works for some systems but causes boot failure on others
#device sbp # SCSI over FireWire (Requires scbus and da)
device  fwe # Ethernet over FireWire (non-standard!)
device  fwip# IP over FireWire (RFC 2734,3146)
device  dcons   # Dumb console driver
device  dcons_crom  # Configuration ROM for dcons
...


btw, I don't get a boot failure.  Once the 60-second timeout expires,
the boot process continues and ends with a working login prompt.  I'm
just wondering how I can find out what it causing the message



___
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

On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelen b.smee...@ose.nl wrote:

 On Mon, 30 Jan 2012 12:52:07 -0500
 David Jackson djackson...@gmail.com 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: Port upgrade change ownership of port installation directory and files

2012-01-30 Thread Lubomir Matousek




On Mon, 30 Jan 2012 14:24:08 +0100
Lubomir Matousek wrote:


I changed apache default user from www to wbserv.

I changed also file ownership from www to wbserv.


Is there any way for portupgrade, that the ownership of installed
port files remains the same? It means wbserv?


On 30.1.2012 15:08, RW wrote:
If you take a look at the Makefile, the port seems to be using the
variables WWWOWN and WWWGRP which are both defaulted to www.



Thanks for replies. It means, is it sufficient to change my 
/etc/make.conf like this?


vi /etc/make.conf
WWWOWN=wbserv
WWWGRP=wbserv

Lubomir

___
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

2012-01-30 Thread 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

2012-01-30 Thread 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 something 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

On Mon, 30 Jan 2012 17:04:56 -0500
David Jackson djackson...@gmail.com wrote:

 On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelen b.smee...@ose.nl wrote:
 
  On Mon, 30 Jan 2012 12:52:07 -0500
  David Jackson djackson...@gmail.com 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 with
failing application services, database changes and so on, because they
did not read

Re: Unable to upgrade packages on FreeBSD

On Mon, 30 Jan 2012 17:04:56 -0500
David Jackson djackson...@gmail.com wrote:


 On Mon, Jan 30, 2012 at 3:58 PM, Bas Smeelen b.smee...@ose.nl wrote:
   
  On Mon, 30 Jan 2012 12:52:07 -0500
  David Jackson djackson...@gmail.com 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 with
failing application services, database changes and

What is the FreeBSD mdoc (man) to HTML toolchain?

2012-01-30 Thread Jason Massey

Dear FreeBSD masters:

I am looking to understand the toolchain that begins with an mdoc-based
manual page and ends with a nice HTML file (as illustrated by
http://www.freebsd.org/cgi/man.cgi?query=groff_mdocapropos=0sektion=0manpath=FreeBSD+9.0-RELEASEarch=defaultformat=html
).


Hypothetically, were I personally attempting to convert the `groff_mdoc.7'
manual page to HTML, from what I've researched the command should be:

groff -mdoc -Thtml groff_mdoc.7 | tidy  bsdgroff.html



[1]
Is the above command how the FreeBSD project produces its gorgeous HTML man
pages?

[2]
How does one associate a link .../ CSS stylesheet with the resultant
file? I cannot locate a `groff' command switch to stop it from inserting
its own inline style information.



== Research I've performed:

I have read GROFF_MDOC(7) in its entirety.

I have searched GROFF(1) and groff's [Tex]info document.



Most respectfully,

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

On Mon, Jan 30, 2012 at 5:49 PM, Polytropon free...@edvax.de 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 it
makes it work better, I have no problem with installing HAL.


  The

Re: Unable to upgrade packages on FreeBSD

2012-01-30 Thread 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

On Tue, 31 Jan 2012 00:02:44 +0100
Bas Smeelen b.smee...@ose.nl wrote:

 On Mon, 30 Jan 2012 17:04:56 -0500
 David Jackson djackson...@gmail.com 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

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

2012-01-30 Thread 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

2012-01-30 Thread 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

2012-01-30 Thread 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: RIP routing protocol implementation is FreeBSD?