Re: Problem completing a 9.1 release to 9.2 release upgrade
On 05/10/2013 21:41, Polytropon wrote: On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. Errrmm... The OP is maintaining his system using freebsd-update -- just building and installing a replacement kernel from the source tree installed via freebsd-update is in fact perfectly OK and a supported way to manage a FreeBSD system. While you are quoting the official instructions from /usr/src/UPDATING here (so they are completely correct in that sense) these are the instructions to do something rather different to what the OP intended. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem completing a 9.1 release to 9.2 release upgrade
On Sun, 06 Oct 2013 08:08:42 +0100, Matthew Seaman wrote: On 05/10/2013 21:41, Polytropon wrote: On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. Errrmm... The OP is maintaining his system using freebsd-update -- just building and installing a replacement kernel from the source tree installed via freebsd-update is in fact perfectly OK and a supported way to manage a FreeBSD system. That is true. But if I understand the question (as quoted above) correctly, installing world from source has been involved, that's why my suggestion of following the instructions (or a subset of them, as it applies). While you are quoting the official instructions from /usr/src/UPDATING here (so they are completely correct in that sense) these are the instructions to do something rather different to what the OP intended. I've copied the the instructions from the comment header of /usr/src/Makefile (at least on my outdated system at home they're there). Of course if the _only_ problem of the initial question is to install a custom kernel, with an otherwise updated system using freebsd-update (with world, kernel and sources in sync), just installing a custom kernel from within multi-user mode is fully supported by the system. This implies that only a small subset of the quoted instructions would apply here (steps 1 and 3 - 5), after freebsd-update has been finished successfully. -- 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: Problem completing a 9.1 release to 9.2 release upgrade
On 06/10/2013 04:51, Eric Feldhusen wrote:
I figured I'd walk through those steps from start to finish and just
correct my main problem and any other little glitches I might have.
I'm on step 6 and when I run mergemaster -p, I get the following error.
*** Creating the temporary root environment in /var/tmp/temproot
*** /var/tmp/temproot ready for use
*** Creating and populating directory structure in /var/tmp/temproot
/usr/bin/install: Undefined symbol gid_from_group
*** FATAL ERROR: Cannot copy files to the temproot environment
I found this thread on the Freebsd forums
http://forums.freebsd.org/showthread.php?t=41779 with the same error and if
I do the same diagnostic steps of
truss install -d -g wheel ~/testdirectory
I find an error of
lstat(/usr/local/etc/libmap.d,0x7fffb990) ERR#2 'No such file or
directory'
Any suggestions? Thank you for the help thus far.
The 'undefined symbol' error means you have a binary which is somehow
not dynamically linking against the shared libraries it was compiled to
use. As install(1) has pretty simple dynamic library usage -- just
libmd and libc:
# ldd /usr/bin/install
/usr/bin/install:
libmd.so.5 = /lib/libmd.so.5 (0x800822000)
libc.so.7 = /lib/libc.so.7 (0x800a33000)
... and libmd.so just contains code for computing various checksums,
nothing to do with groups and GIDs. This suggests that your libc.so is
somehow incompatible with your /usr/bin/install. Which really shouldn't
be the case given that you'ld previously used freebsd-update to upgrade
your userland to 9.2-RELEASE.
Things to double check:
* you haven't been faffing about with /etc/libmap.conf -- that file
or any file it includes should basically be empty except in quite
unusual circumstances. Remember folks: libmap is not your
solution of choice. It's what you turn to when there are no other
viable alternatives.
* Your freebsd-update really has been updating the source tree you
attempted to upgrade from. Check /etc/freebsd-update.conf. By
default it contains:
# Components of the base system which should be kept updated.
Components src world kernel
If you don't have src in there your buildworld procedure will at
best be trying to take you back down to 9.1-RELEASE-p???, and at
worst trying to create some unholy mixture of 9.2 kernel with
earlier bits of the system.
I think you should be able to recover to a system managed via
freebsd-update by something like:
# vi /etc/freebsd-update.conf
{ Make sure you're getting 'src world kernel' components as shown
above }
# freebsd-update fetch
# freebsd-update install
but I haven't tested that so ICBW. In any case, this should get you
back to the state where you have a 9.2-RELEASE world but your modified
9.1-RELEASE kernel. If you still need a custom kernel then you can
build and install it like so:
# cd /usr/src
# make KERNCONF=MYKERNEL buildkernel
# make KERNCONF=MYKERNEL installkernel
and reboot. Otherwise, I'm not sure exactly how you'ld revert from a
custom kernel to the standard generic kernel you'ld normally get via
freebsd-update. What I'd try is moving aside my customized kernel and
re-running freebsd-update:
# cd /boot
# mv kernel kernel-MYKERNEL
# freebsd-update install
If that creates a new /boot/kernel and populates with a new kernel and
many loadable modules then you're golden. If not, move your saved
kernel back into place (mv kernel-MYKERNEL kernel) and ask here again.
The 'no such file or directory' error for /usr/local/etc/libmap.d thing
is a false problem: /usr/local/etc/libmap.d is an optional directory --
all you are seeing is install(1) trying to open it and discovering that
it doesn't exist.
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: Problem completing a 9.1 release to 9.2 release upgrade
On 05/10/2013 20:11, Eric Feldhusen wrote: I have a server that was/is running 9.1 release that I tried to upgrade to 9.2 release. I missed the step of updating to the latest 9.1 patches by doing freebsd-update fetch freebsd-update install I went right to freebsd-update upgrade -r 9.2-RELEASE freebsd-update install rebooot freebsd-update install reboot again But my system still comes up as 9.1 release. Any suggestions on the steps to fix my goof? Did you replace the generic kernel from 9.1-RELEASE with something you compiled yourself? If so, you may well have caused freebsd-update to ignore any modifications to the kernel. You can fix that by re-compiling a kernel using the 9.2-RELEASE sources and basically the same kernel configuration as for 9.1 (you will need to check for 9.2 related differences to the configuration, but these are likely to be pretty minor or not needed at all.) If you aren't using a customized kernel, then has the kernel in the standard location on your system actually been updated? You can tell if it's a 9.2 kernel by running strings(1) against the kernel binary, like so: # strings /boot/kernel/kernel | grep RELEASE If that's clearly a 9.2 kernel, then are you actually booting up from a different kernel somewhere else on your system? First of all, are there any other copies of FreeBSD kernels around anywhere -- on memsticks, or on split mirrors perhaps? You may need to fiddle with the bios settings or interrupt the boot sequence and type things directly at the loader if so. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem completing a 9.1 release to 9.2 release upgrade
Ah, yes, when this particular box was a 9.0-release, I had compiled a custom kernel to enable ipsec. When I check the strings, it's a 9.1 release kernel. I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? Thanks for the help. Eric On Sat, Oct 5, 2013 at 3:34 PM, Matthew Seaman matt...@freebsd.org wrote: On 05/10/2013 20:11, Eric Feldhusen wrote: I have a server that was/is running 9.1 release that I tried to upgrade to 9.2 release. I missed the step of updating to the latest 9.1 patches by doing freebsd-update fetch freebsd-update install I went right to freebsd-update upgrade -r 9.2-RELEASE freebsd-update install rebooot freebsd-update install reboot again But my system still comes up as 9.1 release. Any suggestions on the steps to fix my goof? Did you replace the generic kernel from 9.1-RELEASE with something you compiled yourself? If so, you may well have caused freebsd-update to ignore any modifications to the kernel. You can fix that by re-compiling a kernel using the 9.2-RELEASE sources and basically the same kernel configuration as for 9.1 (you will need to check for 9.2 related differences to the configuration, but these are likely to be pretty minor or not needed at all.) If you aren't using a customized kernel, then has the kernel in the standard location on your system actually been updated? You can tell if it's a 9.2 kernel by running strings(1) against the kernel binary, like so: # strings /boot/kernel/kernel | grep RELEASE If that's clearly a 9.2 kernel, then are you actually booting up from a different kernel somewhere else on your system? First of all, are there any other copies of FreeBSD kernels around anywhere -- on memsticks, or on split mirrors perhaps? You may need to fiddle with the bios settings or interrupt the boot sequence and type things directly at the loader if so. Cheers, Matthew -- 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: Problem completing a 9.1 release to 9.2 release upgrade
On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. -- 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: Problem completing a 9.1 release to 9.2 release upgrade
I figured I'd walk through those steps from start to finish and just correct my main problem and any other little glitches I might have. I'm on step 6 and when I run mergemaster -p, I get the following error. *** Creating the temporary root environment in /var/tmp/temproot *** /var/tmp/temproot ready for use *** Creating and populating directory structure in /var/tmp/temproot /usr/bin/install: Undefined symbol gid_from_group *** FATAL ERROR: Cannot copy files to the temproot environment I found this thread on the Freebsd forums http://forums.freebsd.org/showthread.php?t=41779 with the same error and if I do the same diagnostic steps of truss install -d -g wheel ~/testdirectory I find an error of lstat(/usr/local/etc/libmap.d,0x7fffb990) ERR#2 'No such file or directory' Any suggestions? Thank you for the help thus far. Eric On Sat, Oct 5, 2013 at 4:41 PM, Polytropon free...@edvax.de wrote: On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote: I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just be able to do a cd /usr/src make buildworld make installworld reboot and I'll be running up on the 9.2 kernel and then I'll be all set? No. You should follow the procedure mentioned in the comment header of /usr/src/Makefile. From my (old) b-STABLE system: # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # 4. `make installkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC). # [steps 3. 4. can be combined by using the kernel target] # 5. `reboot'(in single user mode: boot -s from the loader prompt). # 6. `mergemaster -p' # 7. `make installworld' # 8. `make delete-old' # 9. `mergemaster'(you may wish to use -i, along with -U or -F). # 10. `reboot' # 11. `make delete-old-libs' (in case no 3rd party program uses them anymore) Pick what you need to do. When kernel and world sources are in sync, a new kernel can always be installed in multi-user mode. To install world, you should drop to single-user mode to avoid interferences with a full-featured system running in the background. This procedure (or parts of it) will also work when you have been using freebsd-update to modify your kernel, world, and sources. -- 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: problem with stoping process
On 15.12.2011 20:00, Коньков Евгений wrote: I am trying to stop process /usr/local/etc/rc.d/radiusd top Stopping radiusd. Waiting for PIDS: 27618 top 27618 freeradius2 20 -20 333M 295M STOP0 4:42 0.00% radiusd ps aux freeradius 27618 0.0 7.4 341144 302528 ?? TLs Fri05AM 685:27.16 /usr/local/sbin/radiusd nothing is happen Why process do not stop? Does it stops when you kill it by hand with kill -15 27618? David. ___ 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 in installing textproc/asciidoc
Hi,
Thank you.
On new 9.1 systems, textproc/asciidoc is being installed as dependency
to many other ports.
But the make install fails with the error:
installing Vim files in //usr/local/share/vim/vimfiles
^
Two slashes here?
That's a copy from the make install, don't ask me why there are two slashes.
cp: /usr/local/ETC/asciidoc.conf.sample: No such file or directory
^^^
Is this correct? In my opinion, the correct path name
should be /usr/local/etc/, _not_ in caps!
Ditto, but there lies the problem, the sample configuration files get
installed in /usr/local/etc/asciidoc, but then the Makefile tries to
copy the .conf.sample file into .conf and at this stage, it searches
for the files in /usr/local/ETC.
I'll write to the maintener of the post.
Best regards,
Olivier
It is consistent on all the machines.
Maybe an error in the port's configuration?
I can install the 20 or so files xxx.conf.sample by hand, it's
tedious, but it works.
That step should be completed by the post-install target
in /usr/ports/textproc/asciidoc/Makefile. Is there some
variable, like ${ETCDIR}, set wrongly?
But then, any other port that depend on asciidoc will fail to install,
saying that asciidoc have not been installed properly.
You could forcedly register the installation of the port that
you have manually completed.
I could not find any answer an Google, so I ask the question here:
what do I do wrong? Or is there something to tweak to make asciidoc
install and work normally?
Check if you have anything suspicious set in /etc/make.conf
or in your environment that might override the logic of the
Makefile. Check the Makefile as well (I've checked 8.6.6's
on my 8.2 home system).
Just to be sure, make clean and re-checkout the port, then
try again.
--
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
___
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 in installing textproc/asciidoc
On Fri, 21 Jun 2013 15:36:35 +0700 (ICT), Olivier Nicole wrote:
Hi,
On new 9.1 systems, textproc/asciidoc is being installed as dependency
to many other ports.
But the make install fails with the error:
installing Vim files in //usr/local/share/vim/vimfiles
^
Two slashes here?
cp: /usr/local/ETC/asciidoc.conf.sample: No such file or directory
^^^
Is this correct? In my opinion, the correct path name
should be /usr/local/etc/, _not_ in caps!
It is consistent on all the machines.
Maybe an error in the port's configuration?
I can install the 20 or so files xxx.conf.sample by hand, it's
tedious, but it works.
That step should be completed by the post-install target
in /usr/ports/textproc/asciidoc/Makefile. Is there some
variable, like ${ETCDIR}, set wrongly?
But then, any other port that depend on asciidoc will fail to install,
saying that asciidoc have not been installed properly.
You could forcedly register the installation of the port that
you have manually completed.
I could not find any answer an Google, so I ask the question here:
what do I do wrong? Or is there something to tweak to make asciidoc
install and work normally?
Check if you have anything suspicious set in /etc/make.conf
or in your environment that might override the logic of the
Makefile. Check the Makefile as well (I've checked 8.6.6's
on my 8.2 home system).
Just to be sure, make clean and re-checkout the port, then
try again.
--
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: Problem creating user account
Den 23.04.2013 13:17, skrev AMS_MDF_operations: LS, What is going ewrong? Problem : Creating user account -bash-2.05b$ uname -a FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 -bash-2.05b$ This version of FreeBSD is 9 years old and long EOL'ed. Have you ever considered upgrading this machine? -bash-2.05b$ sudo adduser Use option ``-silent'' if you don't want to see all warnings and questions. Check /etc/shells Check /etc/master.passwd Check /etc/group Usernames must match regular expression: [Usernames must match regular expression]: Enter your default shell: bash csh date no sh tcsh [bash]: Your default shell is: bash - /usr/local/bin/bash Enter your default HOME partition: [/home]: Copy dotfiles from: /usr/share/skel no [/usr/share/skel]: Send message from file: /etc/adduser.message no [no]: Do not send message Use passwords (y/n) [y]: Ok, let's go. Don't worry about mistakes. I will give you the chance later to correct any input. Enter username [Usernames must match regular expression]: l-ong Username doesn't match the regexp /Usernames must match regular expression/ For this message I deleted an existing user, and try to create this same user. Also this failed, see below I guess someone has modified /etc/adduser.conf or the adduser script after this user has been created. Have you checked? -- 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
Re: Problem creating user account
Herbert J. Skuhra wrote: Den 23.04.2013 13:17, skrev AMS_MDF_operations: LS, What is going ewrong? Problem : Creating user account -bash-2.05b$ uname -a FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 -bash-2.05b$ This version of FreeBSD is 9 years old and long EOL'ed. Have you ever considered upgrading this machine? Wow ! Actually I too still run some 4 (for reasons I won't distract this thread with) as well as other hosts on 9.1-RELEASE etc, but if ams_mdf_operati...@tele2.com needs to stay on 4, he/she should at least consider upgrading to 4.11-RELEASE for various bug fixes while staying on same feature set. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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 creating user account
On Tue, Apr 23, 2013 at 10:10 AM, Julian H. Stacey j...@berklix.com wrote: Herbert J. Skuhra wrote: Den 23.04.2013 13:17, skrev AMS_MDF_operations: LS, What is going ewrong? Problem : Creating user account -bash-2.05b$ uname -a FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 -bash-2.05b$ This version of FreeBSD is 9 years old and long EOL'ed. Have you ever considered upgrading this machine? Wow ! Actually I too still run some 4 (for reasons I won't distract this thread with) as well as other hosts on 9.1-RELEASE etc, but if ams_mdf_operati...@tele2.com needs to stay on 4, he/she should at least consider upgrading to 4.11-RELEASE for various bug fixes while staying on same feature set. looking at the hostname, it simply appears to be a syslog server, so why upgrade it, if it aint broke dont fix it 4.X was rock solid stable and fast Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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: Problem creating user account
Outback Dingo wrote: On Tue, Apr 23, 2013 at 10:10 AM, Julian H. Stacey j...@berklix.com wrote: Herbert J. Skuhra wrote: Den 23.04.2013 13:17, skrev AMS_MDF_operations: LS, What is going ewrong? Problem : Creating user account -bash-2.05b$ uname -a FreeBSD us-syslog01.dcn.versatel.net 4.9-RELEASE-p10 FreeBSD 4.9-RELEASE-p10 #1: Thu Jun 24 10:04:37 GMT 2004 r...@syslog1.versatel.net:/usr/obj/usr/src/sys/SYSLOG i386 -bash-2.05b$ This version of FreeBSD is 9 years old and long EOL'ed. Have you ever considered upgrading this machine? Wow ! Actually I too still run some 4 (for reasons I won't distract this thread with) as well as other hosts on 9.1-RELEASE etc, but if ams_mdf_operati...@tele2.com needs to stay on 4, he/she should at least consider upgrading to 4.11-RELEASE for various bug fixes while staying on same feature set. looking at the hostname, it simply appears to be a syslog server, so why upgrade it, if it aint broke dont fix it 4.X was rock solid stable and fast Yes, 4 was light on resources too, no bloated gcc make worlds thrashing on *insn*.c back then. But I still long ago upgraded all my 4.x to 4.11, just as I similarly raised sundry 6.* hosts to last minor number of 6.4. Raising to last minor numbers is generaly easy, reduces local version diversity, gets free bug fixes without the cost of problems from new features/ changes in new major numbers. Increases the chances someone out there is running the same major.minor combo, even if EOL'd. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with . Send plain text. No quoted-printable, HTML, base64, multipart/alternative. ___ 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 making software distros
Don O'Neil li...@lizardhill.com writes: I've got an older FreeBSD 6.1 install that will no longer allow me to build any software distributions. Any time I try to do a 'configure', the configure seems to run fine, then I get a config.status: error: cannot find input file:. This has happened on several packages from several different sources. Any ideas as to what could be causing this? Is one of my binaries make corrupted possibly? Unlikely to be a corrupted binary. Much more likely to be that configure scripts are trying to use a file as input for their testing, and not finding it. Tracking down *what* file they want shouldn't be too much effort. If it turns out to be, you can always update to something recent enough to be supported, but that's probably unnecessary for this problem. ___ 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 with news/pan
Walter Hurry walterhu...@gmail.com writes: This port (pan-0.139_1) will again not compile on 9.1-RELEASE (amd64). When did you last try it? It was last updated Saturday, and it builds fine for me. If it's still failing, post the error messages. ___ 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 with news/pan
On Mon, 18 Mar 2013 14:51:04 -0400, Lowell Gilbert wrote: Walter Hurry walterhu...@gmail.com writes: This port (pan-0.139_1) will again not compile on 9.1-RELEASE (amd64). When did you last try it? It was last updated Saturday, and it builds fine for me. If it's still failing, post the error messages. Weird. I last tried yesterday (Sunday). However, having re-enabled the GTKSPELL option (i.e. set it back to defaults), it compiles and builds fine. The port (I always use portsnap before updating) has *not* been updated between then and now. However, it's too difficult to pin down the issue at this point. Sorry for the noise. ___ 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 with news/pan
On Sun, 17 Mar 2013 18:04:54 +, Walter Hurry wrote: dould s/dould/could/. No spell checker! ___ 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 with GPA after updating
Gerard ger...@mcom.com writes: FreeBSD-8.3 STABLE gpg (GnuPG) 2.0.19 libgcrypt 1.5.0 gpa 0.9.3 When attempting to run 'gpa', I am greeted with an error message. The message can be viewed here: http://www.seibercom.net/logs/gpa_error.png It seems to indicate that there is a problem with the GPG library returning an unexpected value. I have tried rebuilding 'gnupg', 'gpgme' and 'gpa'. Is there something else I should be looking into? Hard to say (especially because I can't see the error message). Your subject line implies that this started happening after an upgrade. Perhaps you failed to update a dependency somewhere, or missed a notice in UPDATING (perhaps the required rebuild of everything depending on gnutls in a 20130205 entry)? ___ 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 compiling X11 ports under 9.1-RELEASE
Walter Hurry wrote: On Sun, 13 Jan 2013 22:01:25 +, Will Parsons wrote: I've recently installed 9.1-RELEASE on a laptop and am in the process of installing the ports that I want. On several now, I've encountered error messages that I don't know how to deal with and for which I don't see anything in the UPDATING file that seems to be relevant. For example, trying to build both graphics/xv and x11-clocks/wmclock results failure with the primary error message being: imake -DUseInstalled -I/usr/local/lib/X11/config Imakefile.c:16: error: Imake.tmpl: No such file or directory followed by: make: don't know how to make all. Stop This happens both using portmaster (my usual method of installing ports) and installing manually (cd /usr/ports/x/y; make). Imake seems to be installed (pkg_version reports imake-1.0.4,1) so I don't know where to go from here. I tried x11-clocks/wmclock and it compiled successfully in seconds. $ locate Imake.tmpl /usr/local/lib/X11/config/Imake.tmpl $ pkg which /usr/local/lib/X11/config/Imake.tmpl /usr/local/lib/X11/config/Imake.tmpl was installed by package xorg-cf- files-1.0.4 I re-installed devel/imake and compilation problems seem to be solved. -- Will ___ 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 compiling X11 ports under 9.1-RELEASE
On Sun, 13 Jan 2013 22:01:25 +, Will Parsons wrote: I've recently installed 9.1-RELEASE on a laptop and am in the process of installing the ports that I want. On several now, I've encountered error messages that I don't know how to deal with and for which I don't see anything in the UPDATING file that seems to be relevant. For example, trying to build both graphics/xv and x11-clocks/wmclock results failure with the primary error message being: imake -DUseInstalled -I/usr/local/lib/X11/config Imakefile.c:16: error: Imake.tmpl: No such file or directory followed by: make: don't know how to make all. Stop This happens both using portmaster (my usual method of installing ports) and installing manually (cd /usr/ports/x/y; make). Imake seems to be installed (pkg_version reports imake-1.0.4,1) so I don't know where to go from here. I tried x11-clocks/wmclock and it compiled successfully in seconds. $ locate Imake.tmpl /usr/local/lib/X11/config/Imake.tmpl $ pkg which /usr/local/lib/X11/config/Imake.tmpl /usr/local/lib/X11/config/Imake.tmpl was installed by package xorg-cf- files-1.0.4 ___ 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 to compile lang/gcc
On Mon, Jan 07, 2013 at 02:17:46PM +0100, Fleuriot Damien wrote: Hi Fleuriot, On Jan 7, 2013, at 2:15 PM, Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, I try compile lang/gcc port but it stopped with required 'file to patch': root@casa:/usr/ports/lang/gcc # make Making GCC 4.6.3 for i386-portbld-freebsd9.1 [c,c++,objc,fortran,java] === Found saved configuration for gcc-4.6.3 === Extracting for gcc-4.6.3 = SHA256 Checksum OK for gcc-4.6.3.tar.bz2. = SHA256 Checksum OK for ecj-4.5.jar. === gcc-4.6.3 depends on file: /usr/local/bin/perl5.14.2 - found === Patching for gcc-4.6.3 === gcc-4.6.3 depends on file: /usr/local/bin/perl5.14.2 - found === Applying extra patch /usr/ports/lang/gcc/files/java-patch-hier File to patch: No file found--skip this patch? [n] File to patch: No file found--skip this patch? [n] y 1 out of 1 hunks ignored--saving rejects to libjava/Makefile.in.rej Can't create libjava/Makefile.in.rej, output is in /tmp//patchr1fhKR5: No such f ile or directory *** [do-patch] Error code 1 Stop in /usr/ports/lang/gcc. *** [build] Error code 1 Stop in /usr/ports/lang/gcc. root@casa:/usr/ports/lang/gcc # In this case, what to do for continue ? Thanks. First of all, ensure that your ports tree is up to date. My default port tree on current installation of FreeBSD is the default IMG image of 9.1-RELEASE. I update port tree and work fine. 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: problem to compile lang/gcc
On Tue, Jan 08, 2013 at 09:32:38AM +0200, Ivailo Tanusheff wrote: Hi Ivailo, Hi, I think you should update your ports tree :) Yes, your solution work. 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: problem to compile lang/gcc
On Jan 7, 2013, at 2:15 PM, Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, I try compile lang/gcc port but it stopped with required 'file to patch': root@casa:/usr/ports/lang/gcc # make Making GCC 4.6.3 for i386-portbld-freebsd9.1 [c,c++,objc,fortran,java] === Found saved configuration for gcc-4.6.3 === Extracting for gcc-4.6.3 = SHA256 Checksum OK for gcc-4.6.3.tar.bz2. = SHA256 Checksum OK for ecj-4.5.jar. === gcc-4.6.3 depends on file: /usr/local/bin/perl5.14.2 - found === Patching for gcc-4.6.3 === gcc-4.6.3 depends on file: /usr/local/bin/perl5.14.2 - found === Applying extra patch /usr/ports/lang/gcc/files/java-patch-hier File to patch: No file found--skip this patch? [n] File to patch: No file found--skip this patch? [n] y 1 out of 1 hunks ignored--saving rejects to libjava/Makefile.in.rej Can't create libjava/Makefile.in.rej, output is in /tmp//patchr1fhKR5: No such f ile or directory *** [do-patch] Error code 1 Stop in /usr/ports/lang/gcc. *** [build] Error code 1 Stop in /usr/ports/lang/gcc. root@casa:/usr/ports/lang/gcc # In this case, what to do for continue ? Thanks. First of all, ensure that your ports tree is up to date. ___ 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 to compile lang/gcc
Hi, I think you should update your ports tree :) Regards, Ivailo Tanusheff Xavier xavierfreebsdquesti...@gmail.com Sent by: owner-freebsd-questi...@freebsd.org 07.01.2013 15:15 To freebsd-questions@freebsd.org cc Subject problem to compile lang/gcc Hi to all, I try compile lang/gcc port but it stopped with required 'file to patch': root@casa:/usr/ports/lang/gcc # make Making GCC 4.6.3 for i386-portbld-freebsd9.1 [c,c++,objc,fortran,java] === Found saved configuration for gcc-4.6.3 === Extracting for gcc-4.6.3 = SHA256 Checksum OK for gcc-4.6.3.tar.bz2. = SHA256 Checksum OK for ecj-4.5.jar. === gcc-4.6.3 depends on file: /usr/local/bin/perl5.14.2 - found === Patching for gcc-4.6.3 === gcc-4.6.3 depends on file: /usr/local/bin/perl5.14.2 - found === Applying extra patch /usr/ports/lang/gcc/files/java-patch-hier File to patch: No file found--skip this patch? [n] File to patch: No file found--skip this patch? [n] y 1 out of 1 hunks ignored--saving rejects to libjava/Makefile.in.rej Can't create libjava/Makefile.in.rej, output is in /tmp//patchr1fhKR5: No such f ile or directory *** [do-patch] Error code 1 Stop in /usr/ports/lang/gcc. *** [build] Error code 1 Stop in /usr/ports/lang/gcc. root@casa:/usr/ports/lang/gcc # In this case, what to do for continue ? 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 Disclaimer: The information contained in this message is intended solely for the use of the individual or entity to whom it is addressed and to others authorised to receive it. It may contain confidential or legally privileged information. It you are not the intended recipient you are hereby notified that any disclosure, copying, distribution, or taking any action based on the contents of this message is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this e-mail and then delete it from your system. ProCredit Bank is neither liable for the proper and complete transmission for the information contained in this message nor for any delay in its receipt. ___ 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 compling apr1 from ports
On 05/01/2013 19:17, Erik Nørgaard wrote: lt_cv_sys_max_cmd_len=262144 /bin/sh ./buildconf buildconf: checking installation... buildconf: python not found. You need python installed to build APR from SVN. *** [run-autotools] Error code 1 I tried to debug a bit more on this, seems that buildconf calls a script build/PrintPath which returns the path of a program, i.e.: # ./PrintPath perl /usr/bin/perl But when called by buildconf with parameter python it returns nothing, there is no python binary but a python2.6 # ln -s /usr/local/bin/python2.6 /usr/local/bin/python solves the problem, but is it common to create a link for python as with perl? Is that a patch or a hack? Thanks, Erik -- M: +34 666 334 818 T: +34 915 211 157 ___ 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 compling apr1 from ports
On 6 January 2013 07:52, Erik Nørgaard norga...@locolomo.org wrote: On 05/01/2013 19:17, Erik Nørgaard wrote: lt_cv_sys_max_cmd_len=262144 /bin/sh ./buildconf buildconf: checking installation... buildconf: python not found. You need python installed to build APR from SVN. *** [run-autotools] Error code 1 I tried to debug a bit more on this, seems that buildconf calls a script build/PrintPath which returns the path of a program, i.e.: # ./PrintPath perl /usr/bin/perl But when called by buildconf with parameter python it returns nothing, there is no python binary but a python2.6 # ln -s /usr/local/bin/python2.6 /usr/local/bin/python solves the problem, but is it common to create a link for python as with perl? Is that a patch or a hack? Thanks, Erik Hmm, a bland, un-monkey-ed-with install of python27 here: % ls -l /usr/local/bin/python* lrwxr-xr-x 1 root wheel7 Dec 27 10:50 /usr/local/bin/python - python2 lrwxr-xr-x 1 root wheel 14 Dec 27 10:50 /usr/local/bin/python-config - python2-conf ig lrwxr-xr-x 1 root wheel 14 Dec 27 10:50 /usr/local/bin/python-shared - python-share d2 lrwxr-xr-x 1 root wheel 21 Dec 27 10:50 /usr/local/bin/python-shared-config - pytho n-shared2-config lrwxr-xr-x 1 root wheel 16 Dec 27 10:50 /usr/local/bin/python-shared2 - python-shar ed2.7 lrwxr-xr-x 1 root wheel 23 Dec 27 10:50 /usr/local/bin/python-shared2-config - pyth on-shared2.7-config -r-xr-xr-x 1 root wheel 4656 Dec 27 10:50 /usr/local/bin/python-shared2.7 -r-xr-xr-x 1 root wheel 1659 Dec 27 10:50 /usr/local/bin/python-shared2.7-config lrwxr-xr-x 1 root wheel9 Dec 27 10:50 /usr/local/bin/python2 - python2.7 lrwxr-xr-x 1 root wheel 16 Dec 27 10:50 /usr/local/bin/python2-config - python2.7-c onfig -r-xr-xr-x 1 root wheel 1484336 Dec 27 10:49 /usr/local/bin/python2.7 -r-xr-xr-x 1 root wheel 1652 Dec 27 10:50 /usr/local/bin/python2.7-config Do you have something funny set in /etc/make.conf or within your python options? -- -- ___ 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 after installkernel going from 9.0 to CURRENT
On 12/30/2012 7:11 PM, Robert Huff wrote: It indicates that the / partition cannot be mounted to continue booting. Maybe you can interrupt at the boot loader and examine the mount source for /, or manually set it to be ada0p1? I'll try that. OK - I'm at the part of loader2(?) where it shows: OK and wants something of the form disk partitionpath to bootable kernel However, the sample format for the partition is 0:ad(0,a) How do I specify a GPT partition? Robert Huff ___ 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 after installkernel going from 9.0 to CURRENT
On Sun, 30 Dec 2012 17:26:40 -0500, Robert Huff wrote: Used csup (tag=.) to update the source tree as of midnight last night. This seems to be discouraged today. Instead svn should be used. 5) On rebooting, the loader(??) claims to not be able to find a bootable partition - i.e. I get a screen that ends in mountpoint . Are you sure this isn't the mountroot prompt? It indicates that the / partition cannot be mounted to continue booting. Maybe you can interrupt at the boot loader and examine the mount source for /, or manually set it to be ada0p1? Providing the presumptive value by hand returns error 19. No root partition, probably. :-) This is my first time installing to a GPT partitioned system, and I have (obviously) failed to grok something. I checked src/UPDATING and found nothing which covered this. That's why _I_ prefer old-fashioned MBR partitioning with sysinstall which has never failed me. :-) -- 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: problem after installkernel going from 9.0 to CURRENT
On 12/30/2012 6:24 PM, Polytropon wrote: Used csup (tag=.) to update the source tree as of midnight last night. This seems to be discouraged today. Instead svn should be used. I'm using this for ports, will convert for source ... probably in the next round after I deal with this. 5) On rebooting, the loader(??) claims to not be able to find a bootable partition - i.e. I get a screen that ends in mountpoint . Are you sure this isn't the mountroot prompt? Right you are; sorry, typing from memory on a different system. It indicates that the / partition cannot be mounted to continue booting. Maybe you can interrupt at the boot loader and examine the mount source for /, or manually set it to be ada0p1? I'll try that. Providing the presumptive value by hand returns error 19. No root partition, probably. :-) Duh. :-) That's why _I_ prefer old-fashioned MBR partitioning with sysinstall which has never failed me. :-) There's something to be said for that. On the other hand, GPT is the rising tide and one has to learn to swim sometimes. Robert Huff ___ 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 with libpng + Mozilla applications on FreeBSD 8.3
On Sunday 28 October 2012 01:17:46 Manish Jain wrote: Consider me a newbie here. How do I do wide-reinstall ? You can do this with ports-mgmt/portmaster. See the section Using portmaster to do a complete reinstallation of all your ports at the end of the examples section of the man page. I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport Rebuilding everything is the least complicated way of fixing the problem. It's a big job but if you don't do that then you're likely to have to keep doing even more firefighting in the future. -- 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: Problem with connecting FreeBSD 8.3 to wireless network
On 10/28/12 20:50, Manish Jain wrote: # dmesg | grep -i ath Empty output Doesn't look like your atheros network card has been detected by your system. Did you check the ath(4) man page to see if your particular piece of hardware is supported on FreeBSD 8.3? http://www.freebsd.org/cgi/man.cgi?query=athsektion=4manpath=FreeBSD+8.3-RELEASE HARDWARE The ath driver supports all Atheros Cardbus and PCI cards, except those that are based on the AR5005VL chipset. I'm running: box0=; uname -a FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 And my atheros card is supported. box0=; dmesg | grep ath ath0: Atheros 5424/2424 mem 0xd600-0xd600 irq 16 at device 0.0 on pci2 ath0: AR2425 mac 14.2 RF5424 phy 7.0 ___ 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 with connecting FreeBSD 8.3 to wireless network
Forgot to mention the full name of the adapter : Atheros AR5B125 Regards, Manish Jain bourne.ident...@hotmail.com On 29-Oct-12 00:20, Manish Jain wrote: On 28-Oct-12 05:53, Polytropon wrote: On Sun, 28 Oct 2012 05:47:46 +0530, Manish Jain wrote: On 28-Oct-12 01:49, Polytropon wrote: I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. It could very well be the whole Gnome 2 metaport. :-( Hi All, After reading all the replies to my earlier post Problem with libpng + Mozilla applications on FreeBSD 8.3, I finally summoned up the courage to build the GNOME2 metaport from the ports directory. Since this would not be possible within my lifetime with my usual internet connection, I paid for and succeeded in getting temporary access to a wireless network. Win XP connects to the network pretty smoothly, so there was much reason for hope that things would go smoothly on my FreeBSD 8.3 installation too. I tried configuring the Atheros device to the network as explained in the FreeBSD handbook. But I am having usual rate of success, which is not very high. All the required modules are present in the kernel, as can be seen below : # kldload ath kldload: can't load ath: File exists # kldload wlan_tkip kldload: can't load wlan_tkip: File exists But dmesg returns no output for ath0 : # dmesg | grep -i ath Empty output ifconfig returns the following output : # ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c019bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE ether b8:88:e3:45:63:b1 inet6 fe80::ba88:e3ff:fe45:63b1%bge0 prefixlen 64 scopeid 0x2 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (none) status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 nd6 options=3PERFORMNUD,ACCEPT_RTADV tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1500 options=8LINKSTATE inet 10.0.0.1 -- 10.0.0.2 netmask 0xff00 Opened by PID 767 Since there is no mention of ath0, I did not expect creating the wlan0 pseudo-device would be a simple matter, and I was right : # ifconfig wlan0 create wlandev ath0 ifconfig: SIOCIFCREATE2: Device not configured Manually trying to create the pseudo-device ath0 presents equally unpleasant output : # ifconfig ath0 create ifconfig: SIOCIFCREATE2: Invalid argument pciconf does show my device, but I do not know how to make use of the information (please refer the last few lines of the output) : # pciconf -lv hostb0@pci0:0:0:0:class=0x06 card=0x06491025 chip=0x01048086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0:class=0x03 card=0x06491025 chip=0x01068086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:22:0:class=0x078000 card=0x06491025 chip=0x1e3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = simple comms ehci0@pci0:0:26:0:class=0x0c0320 card=0x06491025 chip=0x1e2d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB hdac0@pci0:0:27:0:class=0x040300 card=0x06491025 chip=0x1e208086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = multimedia subclass = HDA pcib1@pci0:0:28:0:class=0x060400 card=0x06491025 chip=0x1e108086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:1:class=0x060400 card=0x06491025 chip=0x1e128086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI ehci1@pci0:0:29:0:class=0x0c0320 card=0x06491025 chip=0x1e268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB isab0@pci0:0:31:0:class=0x060100 card=0x06491025 chip=0x1e5e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:2:class=0x01018f card=0x06491025 chip=0x1e018086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA none1@pci0:0:31:3:class=0x0c0500 card=0x06491025 chip=0x1e228086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus atapci1@pci0:0:31:5:class=0x010185 card=0x06491025 chip=0x1e098086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA bge0@pci0:2:0:0:class=0x02 card=0x06471025 chip=0x16b514e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class
Re: Problem with connecting FreeBSD 8.3 to wireless network
On Mon, 29 Oct 2012, Manish Jain wrote: Those in a position to help but smugly choose not to may soon start experiencing a dramatic decline in their good fortunes. I'm not in a position to help, but I can explain a couple of things. # kldload ath kldload: can't load ath: File exists # kldload wlan_tkip kldload: can't load wlan_tkip: File exists This tells you that the module in question has already been loaded, or is present in the kernel. [snip] none5@pci0:3:0:0: class=0x028000 card=0x661711ad chip=0x0032168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network The 'none..' tells you that no driver was attached to the device. I suspect that Alexander Kapshuk's reply is relevant here: that your Atheros card is not supported by the driver. I know it's not much help, but maybe it's nonzero. Good luck. -- Chris Hill ch...@monochrome.org ** [ Busy Expunging / ] ___ 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 with libpng + Mozilla applications on FreeBSD 8.3
Sometimes placing symlink to the newer version of library instead of older version helps. On Fri, Oct 26, 2012 at 11:06 PM, Polytropon free...@edvax.de wrote: On Sat, 27 Oct 2012 00:06:44 +0530, Manish Jain wrote: Hello Polytropon, Thanks for replying. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. Exactly that would have been the preferred solution. :-) You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. It also blurs the line between OS (/usr/lib) and additional software (/usr/local/lib) directories. However, both directories are used by the linker, so it looks possible (and probably better than messing with symlinks in /usr/local/lib). Problems _might_ occur when updating world. -- 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 -- Best regards, Alex Alexeev http://twitter.com/afiskon ___ 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 with libpng + Mozilla applications on FreeBSD 8.3
On Saturday 27 October 2012 09:42:10 Alexandr Alexeev wrote: Sometimes placing symlink to the newer version of library instead of older version helps. Specifying the alternative version in /etc/libmap.conf (5) is a neater way of doing this. The man page also shows you how to restrict the mapping to apply for only specified executables. -- 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Fri, Oct 26, 2012 at 11:06 PM, Polytropon free...@edvax.de wrote: On Sat, 27 Oct 2012 00:06:44 +0530, Manish Jain wrote: Hello Polytropon, Thanks for replying. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. Exactly that would have been the preferred solution. :-) You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. It also blurs the line between OS (/usr/lib) and additional software (/usr/local/lib) directories. However, both directories are used by the linker, so it looks possible (and probably better than messing with symlinks in /usr/local/lib). Problems _might_ occur when updating world. -- 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 Sometimes placing symlink to the newer version of library instead of older version helps. There is only one symlink (/usr/local/bin/libpng.so) and it points to the newer version. Regards, Manish Jain bourne.ident...@hotmail.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
Re: Problem with libpng + Mozilla applications on FreeBSD 8.3
But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. The problem is not Mozilla-specific. I built Opera web browser from ports, and that too has images missing from its buttons. Looks like I am going to have to contend with being less image-inative in the coming days. Regards, Manish Jain bourne.ident...@hotmail.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
Re: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sun, 28 Oct 2012 01:43:11 +0530, Manish Jain wrote: But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. The problem is not Mozilla-specific. I built Opera web browser from ports, and that too has images missing from its buttons. It seems that the problem is in some dependency, not the top port itself. This usually indicates that something in /usr/local is dangerously out of sync, and in most cases, wide re-installs solve such kind of problem. Looks like I am going to have to contend with being less image-inative in the coming days. You just need to imagine the images. :-) -- 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
Date: Sat, 27 Oct 2012 22:19:16 +0200 From: Polytropon free...@edvax.de Subject: Re: Problem with libpng + Mozilla applications on FreeBSD 8.3 On Sun, 28 Oct 2012 01:43:11 +0530, Manish Jain wrote: Looks like I am going to have to contend with being less image-inative in the coming days. You just need to imagine the images. :-) It's a complex issue. a purely imagine-ary solution is inadequate. *SNICKER* (or *ALMOND*JOY* if you prefer nuts) ___ 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 with libpng + Mozilla applications on FreeBSD 8.3
On 28-Oct-12 01:49, Polytropon wrote: On Sun, 28 Oct 2012 01:43:11 +0530, Manish Jain wrote: But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. The problem is not Mozilla-specific. I built Opera web browser from ports, and that too has images missing from its buttons. It seems that the problem is in some dependency, not the top port itself. This usually indicates that something in /usr/local is dangerously out of sync, and in most cases, wide re-installs solve such kind of problem. Looks like I am going to have to contend with being less image-inative in the coming days. You just need to imagine the images. :-) Hello Poly, wide re-installs Consider me a newbie here. How do I do wide-reinstall ? I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. Thank you Regards, Manish Jain bourne.ident...@hotmail.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
Re: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sun, 28 Oct 2012 05:47:46 +0530, Manish Jain wrote: On 28-Oct-12 01:49, Polytropon wrote: On Sun, 28 Oct 2012 01:43:11 +0530, Manish Jain wrote: But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. The problem is not Mozilla-specific. I built Opera web browser from ports, and that too has images missing from its buttons. It seems that the problem is in some dependency, not the top port itself. This usually indicates that something in /usr/local is dangerously out of sync, and in most cases, wide re-installs solve such kind of problem. Looks like I am going to have to contend with being less image-inative in the coming days. You just need to imagine the images. :-) Hello Poly, wide re-installs Consider me a newbie here. How do I do wide-reinstall ? That's nowhere a correct terminus technicus or established word. It just means that, for example, if you update one small library that is incorporated by a dependency of a dependency of a library part of Gtk, you need to recompile everything in relation to Gtk, all Gtk programs, libraries and dependencies. Manually tracing down the dependency could be possible, and maybe manual overrides with symlinks and libmap.conf can work, but if you update something here, in conclusion something there, it could lead to even more trouble, forcing you to do much more updates than you are willing to perform. I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. It could very well be the whole Gnome 2 metaport. :-( -- 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Fri, 26 Oct 2012 20:03:11 +0530, Manish Jain wrote: Hi All, I recently purchased a laptop (Intel Pentium dual core) and installed FreeBSD 8.3-i386 on it using the 'All' canned distribution. I then downloaded the latest ports tarball and started building them. This ports snapshot is not in sync with the installed world and possibly installed 3rd party programs (ports) anymore. Some of the ports required a newer version of the graphics/png port, so I did a deinstall and reinstall in graphics/png. This removed the previous binary libpng.so.6 and placed version libpng15.so.15 in its stead. Things went wrong here - the GNOME desktop started crashing with the panel not working and practically all desktop icons gone. Exactly my experience with some libjpeg update some years ago. :-) The rule usually is: If you update a port others depend on (read: depend on a specific version), you also need to update those ports. Mixing versions doesn't seem to be a good idea. So I guessed that the canned version of GNOME in the installation DVD had a dependency on libpng.so.6. Correct. I reinstalled FreeBSD 8.3, [...] Why did you reinstall the OS? Things like Gnome or PNG libarary are separated. [...] and copied /usr/local/lib/libpng.so.6 to /usr/lib/libpng.so.6 before building the ports a second time. You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. This time things went a lot more smoothly. GNOME works. But Mozilla applications like Firefox and Thunderbird present a peculiar problem - the buttons on the Tool bar/Menu bar do not have any image on them. It seems that there is some library collision. If you update things, update _all_ of them, in order to avoid version trouble. The best approach (in your case) would be: Install the OS, do not install anything from ports yet. Get the ports tree. Update it to the recent version. Now start installing stuff, and do it from the _same_ ports tree. Alternative: If you go with the programs installed from the media (e. g. the DVD), use pkg_add to get binary installed applications. In case you insist on compiling, get the ports tree of the _state of your installation_ (i. e. the tarball from the DVD) and use that. Do not update it. In this case, you can easily mix compiling from source and installing via binary packages. This alternative is not suggested now. :-) While this is not exactly a catastrophe, it is rankling to say the least. Maybe some gentleman has faced this problem and has sorted it out. If anyone can provide a hint on how to fix the problem, I would be grateful indeed. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. -- 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: Problem with libpng + Mozilla applications on FreeBSD 8.3
Hello Polytropon, Thanks for replying. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. I suspect that there might be folks at Mozilla who might see the light at the end of the tunnel (and the images on their buttons). I'll try roping them in with a separate message. If anything useful comes up, I'll post it to freebsd-questions as a message of possible interest to any other users who might be facing the same problem. Regards, Manish Jain bourne.ident...@hotmail.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
Re: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sat, 27 Oct 2012 00:06:44 +0530, Manish Jain wrote: Hello Polytropon, Thanks for replying. Maybe an update of FF and TB would be sufficient, so it can link to the present (or at least expected) libraries accordingly. Maybe I did not make it clear enough in the original message. The only thing I installed from the installation DVD was the OS and the GNOME2 metaport. Everything else including FF and TB was installed from ports, the tarball of which I downloaded just a couple of days back. I hope you are not suggesting that I build the GNOME2 metaport too from the ports directory : with my internet connection, that really would take me into the next century. Exactly that would have been the preferred solution. :-) You should not manually copy things. At some point, something will crash, and the ports infrastructure cannot take care of it. It's easier to use a port management tool (like portmaster) to deal with installing and updating of ports. For the present issue, it seems logical that I would need 2 versions of libpng : one for GNOME and one for the ports being installed. Having the two versions reside independently in /usr/lib and /usr/local/lib seems to be the only way out. I still must admit that it defeats the purpose of having port management tools. It also blurs the line between OS (/usr/lib) and additional software (/usr/local/lib) directories. However, both directories are used by the linker, so it looks possible (and probably better than messing with symlinks in /usr/local/lib). Problems _might_ occur when updating world. -- 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: Problem upgrading
On Wed, Oct 17, 2012 at 02:14:10PM -0700, Timothy Snowberger wrote: On 10/17/2012 7:27 AM, Jim Trigg wrote: Any suggestions on how to fix this? --- argent(1) /usr/ports/ports-mgmt/portmaster# freebsd-update -r 9.0-RELEASE upgrade Does this look reasonable (y/n)? y ... Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. sed -i '' -e 's/=_/=%@_/' /usr/sbin/freebsd-update See http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064321.html First, a minor change must be made to the freebsd-update code in order for it to accept file names appearing in FreeBSD 9.0 which contain the '%' and '@' characters; without this change, freebsd-update will error out with the message The update metadata is correctly signed, but failed an integrity check. This fixed it. Thanks, Jim ___ 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 upgrading
On 10/17/2012 7:27 AM, Jim Trigg wrote: Any suggestions on how to fix this? --- argent(1) /usr/ports/ports-mgmt/portmaster# freebsd-update -r 9.0-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 8.2-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic src/base src/bin src/cddl src/contrib src/crypto src/etc src/games src/gnu src/include src/krb5 src/lib src/libexec src/release src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin src/usbin world/base world/dict world/doc world/games world/info world/manpages world/proflibs The following components of FreeBSD do not seem to be installed: world/catpages Does this look reasonable (y/n)? y Fetching metadata signature for 9.0-RELEASE from update5.FreeBSD.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. --- Thanks, Jim ___ 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 sed -i '' -e 's/=_/=%@_/' /usr/sbin/freebsd-update See http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064321.html First, a minor change must be made to the freebsd-update code in order for it to accept file names appearing in FreeBSD 9.0 which contain the '%' and '@' characters; without this change, freebsd-update will error out with the message The update metadata is correctly signed, but failed an integrity check. ___ 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 upgrading misc/help2man: missing language files
On 10/02/2012 10:59 AM, Thomas Mueller wrote: I am unable to upgrade misc/help2man, required by autoconf and other ports that I want to upgrade that depend on perl and/or png. Currently installed version of help2man is 1.40.12 and new version is 1.40.13 I get a bundle of error messages like Extracting help2man (with variable substitutions) === Creating a backup package for old version help2man-1.40.12 tar: lib/bindtextdomain.so: Cannot stat: No such file or directory tar: share/locale/de/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/el/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/eo/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/hr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory Hi Tom Isn't this just the creation of the backup package that fails? I encounter errors like this sometimes, but portmaster goed on installing the newer version. tar: share/locale/it/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pl/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pt_BR/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ru/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sv/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/uk/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/vi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ja/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: man/de/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/el/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/eo/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/hr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/it/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pl/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pt_BR/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ru/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sv/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/uk/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/vi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ja/man1/help2man.1.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 So here I am stuck. I don't know whether the fault is with my installed help2man-1.40.12 or the distfile for 1.40.13. Stuck? Or does portmaster continue as it should? How do I get past this impasse? I suppose I could use -x misc/help2man in portmaster commands, but don't really want to do that if 1.40.13 is good but my installation of 1.40.12 is corrupted. Tom ___ 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 -- Systeembeheerder OverNite Software Europe BV Dr. Nolenslaan 157 6136 GM Sittard THE NETHERLANDS phone: +31464200933 fax: +31464200934 web: http://www.ose.nl 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: Problem upgrading misc/help2man: missing language files
On 10/02/2012 10:59 AM, Thomas Mueller wrote: I am unable to upgrade misc/help2man, required by autoconf and other ports that I want to upgrade that depend on perl and/or png. Currently installed version of help2man is 1.40.12 and new version is 1.40.13 I get a bundle of error messages like Extracting help2man (with variable substitutions) === Creating a backup package for old version help2man-1.40.12 Below it looks like the creation of the backup package fails, which get's deleted by default after the new port is installed. I Just update ports on a CURRENT server with csup from cvsup4.nl.FreeBSD.org and the help2man version is still 1.40.12 I will go ahead and update from cvsup9.freebsd.org . . . No help2man-1.40.13 yet. Maybe csup the portstree again and retry portmaster misc/help2man? Did portmaster end with lines like Upgrade of help2man-1.40.11 to help2man-1.40.12 But then help2man-1.40.12 to help2man-1.40.13 instead of the above? The it should be OK. ** http://lists.freebsd.org/mailman/listinfo/svn-ports-all tar: lib/bindtextdomain.so: Cannot stat: No such file or directory tar: share/locale/de/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/el/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/eo/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/fr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/hr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/it/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pl/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/pt_BR/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ru/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sr/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/sv/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/uk/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/vi/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: share/locale/ja/LC_MESSAGES/help2man.mo: Cannot stat: No such file or directory tar: man/de/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/el/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/eo/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/fr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/hr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/it/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pl/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/pt_BR/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ru/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sr/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/sv/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/uk/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/vi/man1/help2man.1.gz: Cannot stat: No such file or directory tar: man/ja/man1/help2man.1.gz: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 So here I am stuck. I don't know whether the fault is with my installed help2man-1.40.12 or the distfile for 1.40.13. How do I get past this impasse? I suppose I could use -x misc/help2man in portmaster commands, but don't really want to do that if 1.40.13 is good but my installation of 1.40.12 is corrupted. Tom ___ 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 -- Systeembeheerder OverNite Software Europe BV Dr. Nolenslaan 157 6136 GM Sittard THE NETHERLANDS phone: +31464200933 fax: +31464200934 web: http://www.ose.nl 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: Problem with r-o access in jail
Want a nullfs filesystem to be read-only for tech people to search-only maillog files. host machine's files: /var/log/mx1/maillog* files the maillog files are all 644 and r bit is set all along the path using ezjail jail root is /var/jails jail name is fixit mkdir -p /var/jails/fixit/mx1 fixit/mx1 dir has 644 and r bit is set all along the path The directory permissions should have the execute bit set, it should be set to 755 instead of 644. mount_nullfs -o ro /var/log/mx1 /var/jails/fixit/mx1 ezjail-admin console fixit as fixit jail root user I add a user fixit:fixit ssh logon to fixit jail's ip as user fixit ll /mx1 gives nothing but: ls: maillog.45.bz2: Permission denied ls: maillog.46.bz2: Permission denied ls: maillog.47.bz2: Permission denied ls: maillog.48.bz2: Permission denied ls: maillog.49.bz2: Permission denied ls: maillog.5.bz2: Permission denied ls: maillog.50.bz2: Permission denied ls: maillog.51.bz2: Permission denied If your permissions are set to 644 on the directories, this is the result of 'ls'. After changing the directories permissions to 755, the 'Permission denied' errors will stop. ezjail-admin console fixit ...shows the /mx1/maillog* files all to be 644 If move the jail fixit user from group fixit to group wheel, user fixit has access to /mx1/maillog* files. suggestions? thanks, Len -- Regards, James Edwards ___ 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 report cannot be delivered
Sorry for asking , firewall settings on our side ... Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, kheu...@gwdg.de On Tue, 14 Aug 2012, Konrad Heuer wrote: Hi everyone, a colleague of mine sent a problem report this morning by send-pr which cannot be delivered: gwdu60# mailq /var/spool/mqueue (1 request) -Q-ID- --Size-- -Q-Time- Sender/Recipient--- q7E8jguW058857 3186 Tue Aug 14 10:45 tkoe...@gwdu60.gwdg.de (Deferred: Connection refused by mx1.freebsd.org.) freebsd-gnats-sub...@freebsd.org Total requests: 1 Are there any known problems? Best regards Konrad Heuer GWDG, Am Fassberg, 37077 Goettingen, Germany, kheu...@gwdg.de ___ 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: problem
On Sun, 12 Aug 2012 22:55:08 +0330, Web webmaster wrote: hi Direct Admin and enter the desired installation package gives error Command:pkg_add -r gmake perl Error: Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7.4-release/Latest/gmake.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch ' ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7.4-release/Latest/gmake.tbz' by URL Broken pipe You're running a quite old version (7.4/amd64), but that's not a problem. You need to change the root for fetching the packages to a different path, i. e. ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/Latest/ See man pkg_add for details - PACKAGEROOT has to be set to the mentioned path. There are no 7.4-release packages on the FTP server, but the 7-stable packages should work. You could also use ftp to manually fetch the packages and then install them without the -r flag; note that this case does not involve any dependency resolution! ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/Latest/gmake.tbz ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/Latest/perl.tbz If possible, you may consider updating your system to a newer version, 8.3 or 9.0 if it fits your requirements. -- 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: Problem with sendmail update
On 02/08/2012 16:07, Mervyn Passmore wrote: We've made installed 8.14.5 and both the new and old versions seem to be installed and running according to PS. Whatever is starting sendmail is initiating the old version. If you're replacing the system sendmail with the version from ports, then you need to update /etc/mail/mailer.conf -- something like this: # $FreeBSD: stable/9/etc/mail/mailer.conf 93858 2002-04-05 04:25:14Z gshapiro $ # # Execute the real sendmail program, named /usr/local/sbin/sendmail # sendmail/usr/local/sbin/sendmail send-mail /usr/local/sbin/sendmail mailq /usr/local/sbin/sendmail newaliases /usr/local/sbin/sendmail hoststat/usr/local/sbin/sendmail purgestat /usr/local/sbin/sendmail Also, don't confuse the version of the sendmail from the config file with the version in the binary -- both of them show up in the SMTP banner: % telnet localhost smtp Trying ::1... Connected to localhost. Escape character is '^]'. 220 smtp.infracaninophile.co.uk ESMTP Sendmail 8.14.5/8.14.5; Fri, 3 Aug 2012 09:34:40 +0100 (BST) ^ The first one is the version of the binaries, the second is the configuration version, which you can easily change by modifying the DZ8.14.5 line in sendmail.cf Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem with pkgconf and glib.
On 07/30/2012 21:55, Jeff Tipton wrote: On 07/30/2012 20:32, Christopher Hilton wrote: On Jul 30, 2012, at 1:21 PM, Jeff Tipton wrote: On 07/30/2012 19:46, Bas Smeelen wrote: On 07/30/12 18:21, Michael Powell wrote: Jeff Tipton wrote: On 07/30/2012 17:19, Christopher Hilton wrote: [snip] Yes, but try now to rebuild X, or emacs (as Christopher). For me, it dies at devel/gobject-introspection with the following: GISCAN GLib-2.0.gir g-ir-scanner: GLib: warning: 484 warnings suppressed (use --warn-all to see them) GISCAN GObject-2.0.gir g-ir-scanner: GObject: warning: 27 warnings suppressed (use --warn-all to see them) GISCAN GModule-2.0.gir g-ir-scanner: GModule: warning: 1 warnings suppressed (use --warn-all to see them) gmake[2]: *** No rule to make target `/usr/local/include/usr/local/include/usr/local/include/usr/local/include/gio-unix-2.0/gio/*.h', needed by `Gio-2.0.gir'. Stop. gmake[2]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake: *** [all] Error 2 *** Error code 1 I don't know what to do with this, I'm already considering ports downgrade. I traced through the Makefiles in devel/gobject-introspection. They are relying on pkg-config, devel/pkgconf in the newer code, to provide the location. That's how you end up with: /usr/local/include/usr/local/include/usr/local/include/usr/local/include/gio-unix-2.0/gio/*.h Which clearly shouldn't be there as a path. I added the line: date=2012.07.21.00.00.00 to my ports supconfig and then did csup /etc/ports-supfile That pulled my ports collection back to 2012/07/21 which restored pkg-config and removed pkgconf. It probably reverted some other stuff too but I can wait a week for this thing to play out. -- 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 Thanks, Chris, for sharing this. I'll, too, try it this way. -Jeff ___ 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 BTW, While we were talking, pkgconf was changed. I just refreshed the ports tree, and devel/gobject-introspection builds fine now. -Jeff ___ 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 with pkgconf and glib.
On 07/30/2012 17:19, Christopher Hilton wrote: I'm trying to build emacs with gtk2 on my build box and I'm running into trouble with pkgconf from /usr/ports/devel/pkgconf. The build process dies in devel/gobject-introspection and complains that it cannot find header files for gio-unix-2.0. From what I can see the problem looks like the fact that pkgconf is returning the wrong include path for these header files, running: # pkg-config --variable=includedir gio-unix-2.0 returns: /usr/local/include/usr/local/include/usr/local/include I'm not sure if this is part of the problem but it appears that pkgconf returns one instance of /usr/local/include for each dependency listed in the package. E.g. # pkg-config --variable=includedir glib-2.0 returns: /usr/local/include To repeat this problem I started with a fresh FreeBSD virtual machine built from 8-STABLE, an empty /usr/local tree and an empty /var/db/pkg directory. Then I traversed to /usr/ports/devel/gobject-introspection and did: # make install Any help would be appreciated. -- Chris Chris Hilton e: chris /at/ vindaloo /dot/ com All I was doing was trying to get home from work! -- Rosa Parks ___ 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 have the same problem with devel/gobject-introspection. It's also a dependecy for Xorg. A couple of days ago devel/pkg-config was removed from ports as deprecated, and replaced with devel/pkgconf, and consequently the build dependencies of many ports were changed. Maybe this recent change is not thoroughly worked out? Jeff ___ 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 with pkgconf and glib.
Jeff Tipton wrote: On 07/30/2012 17:19, Christopher Hilton wrote: I'm trying to build emacs with gtk2 on my build box and I'm running into trouble with pkgconf from /usr/ports/devel/pkgconf. The build process dies in devel/gobject-introspection and complains that it cannot find header files for gio-unix-2.0. From what I can see the problem looks like the fact that pkgconf is returning the wrong include path for these header files, running: [snip] I have the same problem with devel/gobject-introspection. It's also a dependecy for Xorg. A couple of days ago devel/pkg-config was removed from ports as deprecated, and replaced with devel/pkgconf, and consequently the build dependencies of many ports were changed. Maybe this recent change is not thoroughly worked out? When I first saw it in UPDATING and did the command I believe it was not completely correct, as it did nothing. That was something on the order of 3 or 4 days ago. Just csup'd today and the command in UPDATING I think contained something slightly different, and is now correct. Before, it did not remove/replace pkg-config. Today it did. Perhaps a ports tree refresh and if using portupgrade do this: portupgrade -fo devel/pkgconf pkg-config-\* This did remove pkg-config and replace it with pkgconf, like I expected it to do 3-4 days ago and didn't. -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: Problem with pkgconf and glib.
On 07/30/12 18:21, Michael Powell wrote: Jeff Tipton wrote: On 07/30/2012 17:19, Christopher Hilton wrote: I'm trying to build emacs with gtk2 on my build box and I'm running into trouble with pkgconf from /usr/ports/devel/pkgconf. The build process dies in devel/gobject-introspection and complains that it cannot find header files for gio-unix-2.0. From what I can see the problem looks like the fact that pkgconf is returning the wrong include path for these header files, running: [snip] I have the same problem with devel/gobject-introspection. It's also a dependecy for Xorg. A couple of days ago devel/pkg-config was removed from ports as deprecated, and replaced with devel/pkgconf, and consequently the build dependencies of many ports were changed. Maybe this recent change is not thoroughly worked out? When I first saw it in UPDATING and did the command I believe it was not completely correct, as it did nothing. That was something on the order of 3 or 4 days ago. Just csup'd today and the command in UPDATING I think contained something slightly different, and is now correct. Before, it did not remove/replace pkg-config. Today it did. Perhaps a ports tree refresh and if using portupgrade do this: portupgrade -fo devel/pkgconf pkg-config-\* This did remove pkg-config and replace it with pkgconf, like I expected it to do 3-4 days ago and didn't. -Mike I had about the same issues on a fresh RELENG_9 laptop wih xfce4, firefox and thunderbird. Just removing pkg-config (pkg_delete -f) then installing pkgconf and do a portmaster --check-depends solved it for me. 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: Problem with pkgconf and glib.
On Jul 30, 2012, at 12:21 PM, Michael Powell wrote: Jeff Tipton wrote: On 07/30/2012 17:19, Christopher Hilton wrote: I'm trying to build emacs with gtk2 on my build box and I'm running into trouble with pkgconf from /usr/ports/devel/pkgconf. The build process [snip] When I first saw it in UPDATING and did the command I believe it was not completely correct, as it did nothing. That was something on the order of 3 or 4 days ago. Just csup'd today and the command in UPDATING I think contained something slightly different, and is now correct. Before, it did not remove/replace pkg-config. Today it did. Perhaps a ports tree refresh and if using portupgrade do this: portupgrade -fo devel/pkgconf pkg-config-\* This did remove pkg-config and replace it with pkgconf, like I expected it to do 3-4 days ago and didn't. -Mike I'll look at UPDATING again but from what I see devel/pkgconf is supposed to be a drop in replacement for devel/pkg-config that solves a bootstrapping problem between pkg-config and devel/glib. I'm not convinced on drop in if devel/pkg-config says the the include files for gio-unix-2.0 are in /usr/local/include while devel/pkgconf says that they are in /usr/local/include/usr/local/include/usr/local/include. To hedge my bets I'm using csup to revert the ports collection on my machine to before the change. -- 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: Problem with pkgconf and glib.
On 07/30/2012 19:46, Bas Smeelen wrote: On 07/30/12 18:21, Michael Powell wrote: Jeff Tipton wrote: On 07/30/2012 17:19, Christopher Hilton wrote: I'm trying to build emacs with gtk2 on my build box and I'm running into trouble with pkgconf from /usr/ports/devel/pkgconf. The build process dies in devel/gobject-introspection and complains that it cannot find header files for gio-unix-2.0. From what I can see the problem looks like the fact that pkgconf is returning the wrong include path for these header files, running: [snip] I have the same problem with devel/gobject-introspection. It's also a dependecy for Xorg. A couple of days ago devel/pkg-config was removed from ports as deprecated, and replaced with devel/pkgconf, and consequently the build dependencies of many ports were changed. Maybe this recent change is not thoroughly worked out? When I first saw it in UPDATING and did the command I believe it was not completely correct, as it did nothing. That was something on the order of 3 or 4 days ago. Just csup'd today and the command in UPDATING I think contained something slightly different, and is now correct. Before, it did not remove/replace pkg-config. Today it did. Perhaps a ports tree refresh and if using portupgrade do this: portupgrade -fo devel/pkgconf pkg-config-\* This did remove pkg-config and replace it with pkgconf, like I expected it to do 3-4 days ago and didn't. -Mike I had about the same issues on a fresh RELENG_9 laptop wih xfce4, firefox and thunderbird. Just removing pkg-config (pkg_delete -f) then installing pkgconf and do a portmaster --check-depends solved it for me. 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 Yes, but try now to rebuild X, or emacs (as Christopher). For me, it dies at devel/gobject-introspection with the following: GISCAN GLib-2.0.gir g-ir-scanner: GLib: warning: 484 warnings suppressed (use --warn-all to see them) GISCAN GObject-2.0.gir g-ir-scanner: GObject: warning: 27 warnings suppressed (use --warn-all to see them) GISCAN GModule-2.0.gir g-ir-scanner: GModule: warning: 1 warnings suppressed (use --warn-all to see them) gmake[2]: *** No rule to make target `/usr/local/include/usr/local/include/usr/local/include/usr/local/include/gio-unix-2.0/gio/*.h', needed by `Gio-2.0.gir'. Stop. gmake[2]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake: *** [all] Error 2 *** Error code 1 I don't know what to do with this, I'm already considering ports downgrade. -Jeff ___ 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 with pkgconf and glib.
On Jul 30, 2012, at 1:21 PM, Jeff Tipton wrote: On 07/30/2012 19:46, Bas Smeelen wrote: On 07/30/12 18:21, Michael Powell wrote: Jeff Tipton wrote: On 07/30/2012 17:19, Christopher Hilton wrote: [snip] Yes, but try now to rebuild X, or emacs (as Christopher). For me, it dies at devel/gobject-introspection with the following: GISCAN GLib-2.0.gir g-ir-scanner: GLib: warning: 484 warnings suppressed (use --warn-all to see them) GISCAN GObject-2.0.gir g-ir-scanner: GObject: warning: 27 warnings suppressed (use --warn-all to see them) GISCAN GModule-2.0.gir g-ir-scanner: GModule: warning: 1 warnings suppressed (use --warn-all to see them) gmake[2]: *** No rule to make target `/usr/local/include/usr/local/include/usr/local/include/usr/local/include/gio-unix-2.0/gio/*.h', needed by `Gio-2.0.gir'. Stop. gmake[2]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake: *** [all] Error 2 *** Error code 1 I don't know what to do with this, I'm already considering ports downgrade. I traced through the Makefiles in devel/gobject-introspection. They are relying on pkg-config, devel/pkgconf in the newer code, to provide the location. That's how you end up with: /usr/local/include/usr/local/include/usr/local/include/usr/local/include/gio-unix-2.0/gio/*.h Which clearly shouldn't be there as a path. I added the line: date=2012.07.21.00.00.00 to my ports supconfig and then did csup /etc/ports-supfile That pulled my ports collection back to 2012/07/21 which restored pkg-config and removed pkgconf. It probably reverted some other stuff too but I can wait a week for this thing to play out. -- 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: Problem with pkgconf and glib.
On Mon, Jul 30, 2012 at 08:21:21PM +0300, Jeff Tipton wrote: On 07/30/2012 19:46, Bas Smeelen wrote: On 07/30/12 18:21, Michael Powell wrote: Jeff Tipton wrote: On 07/30/2012 17:19, Christopher Hilton wrote: I'm trying to build emacs with gtk2 on my build box and I'm running into trouble with pkgconf from /usr/ports/devel/pkgconf. The build process dies in devel/gobject-introspection and complains that it cannot find header files for gio-unix-2.0. From what I can see the problem looks like the fact that pkgconf is returning the wrong include path for these header files, running: [snip] Yes, but try now to rebuild X, or emacs (as Christopher). For me, it dies at devel/gobject-introspection with the following: GISCAN GLib-2.0.gir g-ir-scanner: GLib: warning: 484 warnings suppressed (use --warn-all to see them) GISCAN GObject-2.0.gir g-ir-scanner: GObject: warning: 27 warnings suppressed (use --warn-all to see them) GISCAN GModule-2.0.gir g-ir-scanner: GModule: warning: 1 warnings suppressed (use --warn-all to see them) gmake[2]: *** No rule to make target `/usr/local/include/usr/local/include/usr/local/include/usr/local/include/gio-unix-2.0/gio/*.h', needed by `Gio-2.0.gir'. Stop. gmake[2]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake: *** [all] Error 2 *** Error code 1 I don't know what to do with this, I'm already considering ports downgrade. -Jeff While I'm sure that this is just a temporary glitch, in my case the target box is the build machine that I use to maintain all my packages for a set of FreeBSD servers. I unfortunately don't have to time to trace the problem in pkgconf today. I'll try to run it through gdb during the week to see why it's tripple the /usr/local/include part of the include path. -- Chris Chris Hilton e: chris|at|vindaloo|dot|com The pattern juggler lifts his hand; The orchestra begin. As slowly turns the grinding wheel in the court of the crimson king. -- Ian McDonald / Peter Sinfield ___ 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 with pkgconf and glib.
On 07/30/2012 20:32, Christopher Hilton wrote: On Jul 30, 2012, at 1:21 PM, Jeff Tipton wrote: On 07/30/2012 19:46, Bas Smeelen wrote: On 07/30/12 18:21, Michael Powell wrote: Jeff Tipton wrote: On 07/30/2012 17:19, Christopher Hilton wrote: [snip] Yes, but try now to rebuild X, or emacs (as Christopher). For me, it dies at devel/gobject-introspection with the following: GISCAN GLib-2.0.gir g-ir-scanner: GLib: warning: 484 warnings suppressed (use --warn-all to see them) GISCAN GObject-2.0.gir g-ir-scanner: GObject: warning: 27 warnings suppressed (use --warn-all to see them) GISCAN GModule-2.0.gir g-ir-scanner: GModule: warning: 1 warnings suppressed (use --warn-all to see them) gmake[2]: *** No rule to make target `/usr/local/include/usr/local/include/usr/local/include/usr/local/include/gio-unix-2.0/gio/*.h', needed by `Gio-2.0.gir'. Stop. gmake[2]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.10.8' gmake: *** [all] Error 2 *** Error code 1 I don't know what to do with this, I'm already considering ports downgrade. I traced through the Makefiles in devel/gobject-introspection. They are relying on pkg-config, devel/pkgconf in the newer code, to provide the location. That's how you end up with: /usr/local/include/usr/local/include/usr/local/include/usr/local/include/gio-unix-2.0/gio/*.h Which clearly shouldn't be there as a path. I added the line: date=2012.07.21.00.00.00 to my ports supconfig and then did csup /etc/ports-supfile That pulled my ports collection back to 2012/07/21 which restored pkg-config and removed pkgconf. It probably reverted some other stuff too but I can wait a week for this thing to play out. -- 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 Thanks, Chris, for sharing this. I'll, too, try it this way. -Jeff ___ 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 with RAID 1 and requesting for solutions
Dear Sir/Madam, Iam really appreciate if you take a look into below email and advise me any update. On 6/16/12 7:01 PM, info smartelcom i...@smartelcom.net wrote: HI there, hope my email find you well, i recently order a server with below configuration INTEL 1x Quad-Core i5-2500 3.3GHz, 6M Cache 16GB DDR3 2x 500GB SATAII then ask from my COLOCATION to install FreeBSD 8.2 or 8.3 with RAID 1, after many times of fail in installation from colocation they said that we have problem with RAID 1.we suggest them to play with different kind of RAID like RAID 5 and they said as our requested server only have 2 HDD, its not possible to set up RAID 5. now they said us that the only way for having backup of DATA in this condition is set up a scheduled task to put back up of data in the second HDD . now i really need to know if there is a only way for having data back up in this condition or you have better idea according to your experience.also if its the only way , would it be a good level of data security ? looking forward to hear from your side soon. Regards, Smartelcom Team Regards Shahram Haghnia Technical Director Smartelcom Communications Global Wholesale Services ___ 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 with routing in VmWare VMS
On Fri, Jun 22, 2012 at 3:13 PM, UNIX developer @ Google.com developeru...@gmail.com wrote: Ok, I understud! I remove from rc.conf this rows: static_routes=clnet route_clnet=-net 192.168.2.0/24 192.168.1.10 new rc.conf: ifconfig_em0= inet 192.168.1.10 netmask 255.255.255.0 ifconfig_em1= inet 192.168.2.1 netmask 255.255.255.0 defaultrouter=192.168.1.1 gateway_enable=YES now after reboot the problem still the same. ping -S 192.168.2.1 192.168.1.1 PING 192.168.1.1 (192.168.1.1) from 192.168.2.1: 56 data bytes ^C --- 192.168.1.1 ping statistics --- 8 packets transmitted, 0 packets received, 100.0% packet loss netstat -nr Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.1.1UGS 0 38em0 127.0.0.1 link#4 UH 00lo0 192.168.1.0/24 link#1 U 0 1153em0 192.168.1.10 link#1 UHS 06lo0 192.168.2.0/24 link#2 U 00em1 192.168.2.1link#2 UHS 06lo0 Where more can be trouble? - Вы писали 22 июня 2012 г., 0:56:49: On Thu, 21 Jun 2012 15:59:36 -0500, UNIX developer @ Google.com developeru...@gmail.com wrote: /etc/rc.conf ifconfig_em0= inet 192.168.1.10 netmask 255.255.255.0 ifconfig_em1= inet 192.168.2.1 netmask 255.255.255.0 defaultrouter=192.168.1.1 gateway_enable=YES static_routes=clnet route_clnet=-net 192.168.2.0/24 192.168.1.10 You simply CANNOT do this. Traffic for 192.168.2.0/24 is bound to em1 and cannot be changed. You setup a static route that basically says to find 192.168.2.0/24, don't use em1 but instead ask 192.168.1.10 how to find it? This makes no sense at all. -- С уважением, UNIX mailto:developeru...@gmail.com Hi, Your problem, as Mark told you, is that you are buildinga gateway to connect two networks on the same subnet. 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: Problem with routing in VmWare VMS
On Thu, 21 Jun 2012 15:59:36 -0500, UNIX developer @ Google.com developeru...@gmail.com wrote: /etc/rc.conf ifconfig_em0= inet 192.168.1.10 netmask 255.255.255.0 ifconfig_em1= inet 192.168.2.1 netmask 255.255.255.0 defaultrouter=192.168.1.1 gateway_enable=YES static_routes=clnet route_clnet=-net 192.168.2.0/24 192.168.1.10 You simply CANNOT do this. Traffic for 192.168.2.0/24 is bound to em1 and cannot be changed. You setup a static route that basically says to find 192.168.2.0/24, don't use em1 but instead ask 192.168.1.10 how to find it? This makes no sense at all. ___ 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 with spamlogd
On 17/06/2012 11:45, Doug Hardie wrote:
I am using spamd on several systems and started encountering a problem awhile
ago with FreeBSD 7.2 servers, but let it go since I am in the process of
upgrading the servers. However, I now am encountering the same issue on
FreeBSD 9.0 with spamlogd. It never reads pflog0. pflogd reads the entries
just fine. I set up syslog to log all the spamlogd messages and when
spamlogd is started it gives:
spamlogd: Listening on pflog0 for all interfaces.
lsof shows that it is connected to bpf0 as is pflogd. However, pflogd shows
an offset into the file that appears to be the end of the file. spamlogd
shows an offset of 0. It is periodically reading the file as shown by ktrace
but always getting back a 0 size return. spamd itself is working just fine.
However, the expiration times are not being updated so white entries are
timed out way too often. spamlogd used to update them. The rc.conf entries
are:
obspamd_enable=YES
obspamd_flags=-G 2:1:1728
obspamd_setup_flags=
obspamd_grey=YES
obspamlogd_enable=YES
obspamlogd_flags=-W 1728
These were established a few years ago and worked up till short while ago. I
don't recall any changes I made to anything, but…
Looking through the spamlogd source it appears to be building a filter for
the pcap routines with:
ip and port 25 and action pass and tcp[13]0x12=0x2
Using that filter on pflog yields no output. I believe the pass item
requires there to be some logging of the pass actions and those are not
appearing in the pflog or in the pfctl counts for those rules. I suspect
that is the problem. The pf.conf is: (mail server is on this machine)
ext_if=em0
table blackhole persist file /etc/blackhole
table spamd persist
table spamd-white persist
table spamd-white-local persist file /etc/mail/whitelist
no rdr on { lo0, lo1 } from any to any
no rdr on { lo0, lo1 } from any to any
MAILHOSTS = {zool.lafn.org 10.0.1.10}
rdr pass log on $ext_if inet proto tcp from spamd-white-local to port smtp
- 127.0.0.1 port smtp
rdr pass log on $ext_if inet proto tcp from spamd-white to port smtp -
127.0.0.1 port smtp
rdr pass log on $ext_if inet proto tcp to $MAILHOSTS port smtp - 127.0.0.1
port spamd
pass in on lo0
pass in log on $ext_if inet proto tcp to 127.0.0.1 port smtp
pass out log on $ext_if inet proto tcp from 127.0.0.1 to any port smtp
block in quick log on $ext_if from blackhole to any
You seem to be logging all the SMTP traffic that passes through pf in
any direction. Which doesn't make a lot of sense to me -- obspamlogd
will see the logged SMTP packets, assume that's valid traffic and add
the hosts to the whitelist. Even if that's the incoming SYN packet from
some dubious mailer trying to inject you full of spam.
You should only log the SYN packets going out of your upstream (egress)
interface for obspamlogd -- that way it immediately whitelists anyone
you send email to, so they can reply without delay due to greylisting.
A good way of doing that is to log SMTP traffic to a separate log
device. eg:
pass log (to pflog1) on $ext_if proto tcp \
from any to any port smtp\
flags S/SA keep state
then in /etc/rc.conf, tell obspamlogd to use pflog1:
obspamlogd_enable=YES
obspamlogd_flags=-i em0
obspamlogd_pflog_if=pflog1
That way you can keep pflog0 for doing the normal packet logging that is
usual with pf -- typically, logging anything that gets dropped by the
firewall -- without getting obspamlogd confused.
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 with spamlogd
On 17 June 2012, at 06:29, Matthew Seaman wrote:
On 17/06/2012 11:45, Doug Hardie wrote:
I am using spamd on several systems and started encountering a problem
awhile ago with FreeBSD 7.2 servers, but let it go since I am in the process
of upgrading the servers. However, I now am encountering the same issue on
FreeBSD 9.0 with spamlogd. It never reads pflog0. pflogd reads the entries
just fine. I set up syslog to log all the spamlogd messages and when
spamlogd is started it gives:
spamlogd: Listening on pflog0 for all interfaces.
lsof shows that it is connected to bpf0 as is pflogd. However, pflogd shows
an offset into the file that appears to be the end of the file. spamlogd
shows an offset of 0. It is periodically reading the file as shown by
ktrace but always getting back a 0 size return. spamd itself is working
just fine. However, the expiration times are not being updated so white
entries are timed out way too often. spamlogd used to update them. The
rc.conf entries are:
obspamd_enable=YES
obspamd_flags=-G 2:1:1728
obspamd_setup_flags=
obspamd_grey=YES
obspamlogd_enable=YES
obspamlogd_flags=-W 1728
These were established a few years ago and worked up till short while ago.
I don't recall any changes I made to anything, but…
Looking through the spamlogd source it appears to be building a filter for
the pcap routines with:
ip and port 25 and action pass and tcp[13]0x12=0x2
Using that filter on pflog yields no output. I believe the pass item
requires there to be some logging of the pass actions and those are not
appearing in the pflog or in the pfctl counts for those rules. I suspect
that is the problem. The pf.conf is: (mail server is on this machine)
ext_if=em0
table blackhole persist file /etc/blackhole
table spamd persist
table spamd-white persist
table spamd-white-local persist file /etc/mail/whitelist
no rdr on { lo0, lo1 } from any to any
no rdr on { lo0, lo1 } from any to any
MAILHOSTS = {zool.lafn.org 10.0.1.10}
rdr pass log on $ext_if inet proto tcp from spamd-white-local to port smtp
- 127.0.0.1 port smtp
rdr pass log on $ext_if inet proto tcp from spamd-white to port smtp -
127.0.0.1 port smtp
rdr pass log on $ext_if inet proto tcp to $MAILHOSTS port smtp - 127.0.0.1
port spamd
pass in on lo0
pass in log on $ext_if inet proto tcp to 127.0.0.1 port smtp
pass out log on $ext_if inet proto tcp from 127.0.0.1 to any port smtp
block in quick log on $ext_if from blackhole to any
You seem to be logging all the SMTP traffic that passes through pf in
any direction. Which doesn't make a lot of sense to me -- obspamlogd
will see the logged SMTP packets, assume that's valid traffic and add
the hosts to the whitelist. Even if that's the incoming SYN packet from
some dubious mailer trying to inject you full of spam.
Right now, I would like spamlogd to be a bit confused ;-) However, its not
seeing any of the logging. It never receives any input from pflog0. From the
filter, the pass action indicates it won't look at any of the rdr logging
(which is in the log) but is waiting for the pass rules to log something. The
tcp[13]0x12=0x2 item is the TCP SYN flag so it should be able to separate out
what it wants from the log. However, the pass rules are never being used and
hence they never generate any log entries. pfctl -vvsr shows all zeros for
both of those rules.
I understand that the pass rules are applied after the rdr rules but apparently
I am getting the matching criteria wrong. At this point switching them to a
separate log stream won't help since it would never get anything logged to it.
You should only log the SYN packets going out of your upstream (egress)
interface for obspamlogd -- that way it immediately whitelists anyone
you send email to, so they can reply without delay due to greylisting.
A good way of doing that is to log SMTP traffic to a separate log
device. eg:
pass log (to pflog1) on $ext_if proto tcp \
from any to any port smtp\
flags S/SA keep state
then in /etc/rc.conf, tell obspamlogd to use pflog1:
obspamlogd_enable=YES
obspamlogd_flags=-i em0
obspamlogd_pflog_if=pflog1
That way you can keep pflog0 for doing the normal packet logging that is
usual with pf -- typically, logging anything that gets dropped by the
firewall -- without getting obspamlogd confused.
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
___
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 with spamlogd
After many hundreds of tests, I have uncovered something that I never found in
any of the pf documents or man pages. If an incoming packet is processed by an
rdr rule, it will always be logged as rdr with the rdr rule number. The pass
action is never logged, even if the rdr rule does not include log and the pass
rule does.
As a result, since spamlogd is specifically looking for a pass action, it will
never see those log entries. Hence, you must ensure that the packets which do
get sent to the mailserver (real one) never are processed by a rdr rule. I
ended up having to use no rdr rules for those to get the logging done such that
spamlogd would find them:
no rdr inet proto tcp from spamd-white-local to any port smtp
no rdr inet proto tcp from spamd-white to any port smtp
rdr pass on $ext_if inet proto tcp to $MAILHOSTS port smtp - 127.0.0.1 port spa
md
pass in log on $ext_if inet proto tcp to $MAILHOSTS port smtp
This setup works on FreeBSD 7.2 and 9.0. I couldn't find any other that
actually worked including those in the various pf books, man pages, and other
writings on pf.
On 17 June 2012, at 09:40, Doug Hardie wrote:
On 17 June 2012, at 06:29, Matthew Seaman wrote:
On 17/06/2012 11:45, Doug Hardie wrote:
I am using spamd on several systems and started encountering a problem
awhile ago with FreeBSD 7.2 servers, but let it go since I am in the
process of upgrading the servers. However, I now am encountering the same
issue on FreeBSD 9.0 with spamlogd. It never reads pflog0. pflogd reads
the entries just fine. I set up syslog to log all the spamlogd messages
and when spamlogd is started it gives:
spamlogd: Listening on pflog0 for all interfaces.
lsof shows that it is connected to bpf0 as is pflogd. However, pflogd
shows an offset into the file that appears to be the end of the file.
spamlogd shows an offset of 0. It is periodically reading the file as
shown by ktrace but always getting back a 0 size return. spamd itself is
working just fine. However, the expiration times are not being updated so
white entries are timed out way too often. spamlogd used to update them.
The rc.conf entries are:
obspamd_enable=YES
obspamd_flags=-G 2:1:1728
obspamd_setup_flags=
obspamd_grey=YES
obspamlogd_enable=YES
obspamlogd_flags=-W 1728
These were established a few years ago and worked up till short while ago.
I don't recall any changes I made to anything, but…
Looking through the spamlogd source it appears to be building a filter for
the pcap routines with:
ip and port 25 and action pass and tcp[13]0x12=0x2
Using that filter on pflog yields no output. I believe the pass item
requires there to be some logging of the pass actions and those are not
appearing in the pflog or in the pfctl counts for those rules. I suspect
that is the problem. The pf.conf is: (mail server is on this machine)
ext_if=em0
table blackhole persist file /etc/blackhole
table spamd persist
table spamd-white persist
table spamd-white-local persist file /etc/mail/whitelist
no rdr on { lo0, lo1 } from any to any
no rdr on { lo0, lo1 } from any to any
MAILHOSTS = {zool.lafn.org 10.0.1.10}
rdr pass log on $ext_if inet proto tcp from spamd-white-local to port
smtp - 127.0.0.1 port smtp
rdr pass log on $ext_if inet proto tcp from spamd-white to port smtp -
127.0.0.1 port smtp
rdr pass log on $ext_if inet proto tcp to $MAILHOSTS port smtp - 127.0.0.1
port spamd
pass in on lo0
pass in log on $ext_if inet proto tcp to 127.0.0.1 port smtp
pass out log on $ext_if inet proto tcp from 127.0.0.1 to any port smtp
block in quick log on $ext_if from blackhole to any
You seem to be logging all the SMTP traffic that passes through pf in
any direction. Which doesn't make a lot of sense to me -- obspamlogd
will see the logged SMTP packets, assume that's valid traffic and add
the hosts to the whitelist. Even if that's the incoming SYN packet from
some dubious mailer trying to inject you full of spam.
Right now, I would like spamlogd to be a bit confused ;-) However, its not
seeing any of the logging. It never receives any input from pflog0. From
the filter, the pass action indicates it won't look at any of the rdr logging
(which is in the log) but is waiting for the pass rules to log something.
The tcp[13]0x12=0x2 item is the TCP SYN flag so it should be able to
separate out what it wants from the log. However, the pass rules are never
being used and hence they never generate any log entries. pfctl -vvsr shows
all zeros for both of those rules.
I understand that the pass rules are applied after the rdr rules but
apparently I am getting the matching criteria wrong. At this point switching
them to a separate log stream won't help since it would never get anything
logged to it.
You should only log the SYN packets going out of your upstream (egress)
interface for obspamlogd -- that
Re: Problem with SSL ans net/sendemail
Carmel carmel...@hotmail.com wrote: Error message: invalid SSL_version specified at /usr/local/lib/perl5/site_perl/5.14.2/IO/Socket/SSL.pm line 308 This is generated by the sendEmail program. The net/sendemail port compiled with SSL support. make showconfig === The following configuration options are available for sendEmail-1.56: SSL=on Enable SSL support This was working fine until today. This all started after a reboot of the system. ssh -V OpenSSH_5.4p1_hpn13v11 FreeBSD-20100308, OpenSSL 0.9.8q 2 Dec 2010 openssl version OpenSSL 1.0.1a 19 Apr 2012 It appears I have two different versions of OpenSSL installed. I deliberately installed the newer version and placed this in the /etc/make.conf file: WITH_OPENSSL_PORT=yes I have no idea what happened or how to correct this problem. I tried rebuilding Perl and the two ports listed in the sendemail port and the sendemail port itself without a satisfactory result. By the way, I noticed that OpenSSH 6.0 was released April 22, 2012. Are there any plans to get that into the ports system, or better yet, replace the aging base system? -- Carmel ✌ carmel...@hotmail.com I'm currently traveling, with no computer nearby. Please ping me in 3 days. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. ___ 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 with npviewer.bin
On 10 May 2012 08:14, Carmel carmel...@hotmail.com wrote: I am continuing to have a problem with certain flash videos not displaying with Firefox on FreeBSD-8.3. I have discovered numerous messages like this in the system log file. May 10 07:59:04 scorpio kernel: linux: pid 96942 (npviewer.bin): syscall pipe2 not implemented I have also discovered: npviewer.bin.core files in my HOME directory. Is there something that I can do to correct this problem? Which version of flash are you using? -- Eitan Adler ___ 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 with dhclient after update to FreeBSD-8.3
On 05/05/2012 19:30, Carmel wrote: I just updated my system to FreeBSD 8.3-STABLE #0 from version 8.2. I was getting warning messages regarding webcamd at boot-up; however, I got them fixed (I think) I loaded: cuse4bsd_load=YES in the loader.conf file and placed: webcamd_enable=YES in the rc.conf file. I had never used it before; however, I am assuming that the 8.3 version somehow requires it. What's happening is that 8.3 has introduced more comprehensive support for a wider range of USB devices. It's just picking up on the presence of a webcam now and suggesting software that could manage it. You don't need to enable the webcam at all: the kernel will recognise it as a webcam from its built-in identifying codes, but unless you enable some software to deal with it, it won't be able to do anything. This usually shows up with USB ethernet devices suddenly appearing and cluttering up ifconfig(8) output -- unlike webcams, ethernet interfaces generally do have kernel level support automatically enabled. devd will try and run dhclient on the interface to configure it, which I guess is where your extra dhclent invocation is coming from. It is possible to turn this behaviour off by adding something like: hint.usb.0.disabled=1 into /boot/loader.conf but this is using a sledgehammer to crack a nut, as that turns off that usb bus entirely. (Warning: This may well have deleterious effects on your ability to use a keyboard or mouse with the system: use cautiously. Also, change that '0' to the appropriate bus number if you need to) dhclient is listed as starting at the beginning of the log and again at the end. I never had this happen when using FreeBSD-8.2. I am still confused as to why devd wants to start webcamd devd only wants to start webcamd because you've installed the webcamd software including /usr/local/etc/devd/webcamd.conf If you pkg_delete the webcamd stuff and then restart devd, it won't try starting up webcamd any more. All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: problem with dhclient after update to FreeBSD-8.3
On Sun, 6 May 2012, Matthew Seaman wrote: On 05/05/2012 19:30, Carmel wrote: All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. http://www.freebsd.org/cgi/query-pr.cgi?pr=165477 may be relevant. It's on 9-stable, I haven't compared with 8.3. ___ 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 with dhclient after update to FreeBSD-8.3
On Sun, 6 May 2012 04:25:52 -0600 (MDT) Warren Block articulated: On Sun, 6 May 2012, Matthew Seaman wrote: On 05/05/2012 19:30, Carmel wrote: All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. http://www.freebsd.org/cgi/query-pr.cgi?pr=165477 may be relevant. It's on 9-stable, I haven't compared with 8.3. Warren, I posted an addendum to that PR to indicate that the behavior is also occurring on 8.3 systems as well. Do you think it would be prudent to open a new PR with my info since it concerns FreeBSD-8.3 STABLE and not the 9.0 branch? I was also wondering if anyone other than myself is seeing this phenomenon on the 8.3 version. -- Carmel ✌ carmel...@hotmail.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
Re: problem with dhclient after update to FreeBSD-8.3
On Sun, 06 May 2012 10:48:31 +0100 Matthew Seaman articulated: On 05/05/2012 19:30, Carmel wrote: I just updated my system to FreeBSD 8.3-STABLE #0 from version 8.2. I was getting warning messages regarding webcamd at boot-up; however, I got them fixed (I think) I loaded: cuse4bsd_load=YES in the loader.conf file and placed: webcamd_enable=YES in the rc.conf file. I had never used it before; however, I am assuming that the 8.3 version somehow requires it. What's happening is that 8.3 has introduced more comprehensive support for a wider range of USB devices. It's just picking up on the presence of a webcam now and suggesting software that could manage it. You don't need to enable the webcam at all: the kernel will recognise it as a webcam from its built-in identifying codes, but unless you enable some software to deal with it, it won't be able to do anything. While that may well be true, it does clutter up the boot-up process with a lot of sinister if only benign looking warning messages. There should be a way to silence them or at least make the warning message less sinister looking. Something like: webcamd present but not enabled like is done for other devices. This usually shows up with USB ethernet devices suddenly appearing and cluttering up ifconfig(8) output -- unlike webcams, ethernet interfaces generally do have kernel level support automatically enabled. devd will try and run dhclient on the interface to configure it, which I guess is where your extra dhclent invocation is coming from. It is possible to turn this behaviour off by adding something like: hint.usb.0.disabled=1 into /boot/loader.conf but this is using a sledgehammer to crack a nut, as that turns off that usb bus entirely. (Warning: This may well have deleterious effects on your ability to use a keyboard or mouse with the system: use cautiously. Also, change that '0' to the appropriate bus number if you need to) I think I will skip the sledgehammer technique for now. Thanks for the suggestion though. :) dhclient is listed as starting at the beginning of the log and again at the end. I never had this happen when using FreeBSD-8.2. I am still confused as to why devd wants to start webcamd devd only wants to start webcamd because you've installed the webcamd software including /usr/local/etc/devd/webcamd.conf If you pkg_delete the webcamd stuff and then restart devd, it won't try starting up webcamd any more. I don't think removing it is really an option: pkg_info -R webcamd-3.5.0.2 Information for webcamd-3.5.0.2: Required by: gstreamer-plugins-all-1.3.0.10.1_12 gstreamer-plugins-v4l2-0.10.30,3 kde-4.7.4_1 kde-workspace-4.7.4_1 kdeartwork-4.7.4_1 kdenetwork-4.7.4_2 kdeplasma-addons-4.7.4_1 kdetoys-4.7.4_1 kdeutils-4.7.4_2 phonon-gstreamer-4.5.1 qt4-4.7.4 qt4-qtconfig-4.7.4 Interestingly enough, I never had webcamd initiated in the /etc/rc.conf file and never received a warning message about it having to be initialized until the update to FreeBSD-8.3. I am not sure if this should be considered a BUG or what. It doesn't appear that any of the software that requires it to be installed also require it to be running at boot-up. I don't even know who, if anyone, I should report this behavior to. All I guess I really have to get corrected is the dhclient thing, assuming it is a real problem and just not some useless noise. The 'dhclient already running' message is untidy, but harmless. It's the rc system refusing to start a duplicate dhclient process on some interface. As your network interface is via a PCI device, I can't see why devd would think it should try and restart dhclient for it. There does appear to be a PR listed against this behavior as noted in Warren's post on this thread. http://www.freebsd.org/cgi/query-pr.cgi?pr=165477 Thanks for your assistance Matthew. -- Carmel ✌ carmel...@hotmail.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
Re: Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Try disabling hardware VLAN tagging like so, I know we had problems a few years back with it. in /etc/rc.conf : ifconfig_igb2= -vlanhwtag -tso -lro up 2012/4/11 KES kes-...@yandex.ua: Пересылаемое сообщение 11.04.2012, 13:14, KES kes-...@yandex.ua: 10.04.2012, 08:50, Da Rock freebsd-questi...@herveybayaustralia.com.au: On 04/10/12 05:02, Коньков Евгений wrote: Yes, I have tested. and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012 but last two days: reboot ~ Mon Apr 9 19:50 reboot ~ Mon Apr 9 18:30 reboot ~ Sun Apr 8 20:55 reboot ~ Sun Apr 8 20:00 reboot ~ Sun Apr 8 19:49 reboot ~ Sun Apr 8 17:43 reboot ~ Sun Apr 8 10:58 reboot ~ Sat Apr 7 21:13 reboot ~ Sat Apr 7 16:37 reboot ~ Sat Apr 7 16:07 I remembered. One thing changed. I add vlans to igb2, but no traffic flow on that devices yet. Perhaps you should test removing the vlans and see if things improve? I have removed vlans, two day server works without reboots Before this I have use: igb0, igb1, igb3 igb0@pci0:1:0:0: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb1@pci0:1:0:1: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb2@pci0:1:0:2: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet igb3@pci0:1:0:3: class=0x02 card=0x00018086 chip=0x15218086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' class = network subclass = ethernet ifconfig_vlan100=inet 192.168.0.1 netmask 255.255.255.0 vlan 100 vlandev igb2 #nALL ifconfig_vlan101=inet 192.168.1.1 netmask 255.255.255.0 vlan 101 vlandev igb2 #n2 p24 ifconfig_vlan102=inet 192.168.2.1 netmask 255.255.255.0 vlan 102 vlandev igb2 #n1 p23 ifconfig_vlan103=inet 192.168.3.1 netmask 255.255.255.0 vlan 103 vlandev igb2 #n3 p22 ifconfig_vlan104=inet 192.168.4.1 netmask 255.255.255.0 vlan 104 vlandev igb2 #n7,9 p21 ifconfig_vlan105=inet 192.168.5.1 netmask 255.255.255.0 vlan 105 vlandev igb2 #n11 p20 ifconfig_vlan106=inet 192.168.6.1 netmask 255.255.255.0 vlan 106 vlandev igb2 #n13 p19 ifconfig_vlan107=inet 192.168.7.1 netmask 255.255.255.0 vlan 107 vlandev igb2 #n223 p18 ifconfig_vlan108=inet 192.168.8.1 netmask 255.255.255.0 vlan 108 vlandev igb2 #n225 p17 ifconfig_vlan109=inet 192.168.9.1 netmask 255.255.255.0 vlan 109 vlandev igb2 #n221 p16 ifconfig_vlan110=inet 192.168.10.1 netmask 255.255.255.0 vlan 110 vlandev igb2 #n229 p15 ifconfig_vlan111=inet 192.168.11.1 netmask 255.255.255.0 vlan 111 vlandev igb2 #n233 p14 ifconfig_vlan112=inet 192.168.12.1 netmask 255.255.255.0 vlan 112 vlandev igb2 #n231 p13 ifconfig_vlan113=inet 192.168.13.1 netmask 255.255.255.0 vlan 113 vlandev igb2 #n237 p12 ifconfig_vlan114=inet 192.168.14.1 netmask 255.255.255.0 vlan 114 vlandev igb2 #n424 p11 ifconfig_vlan115=inet 192.168.15.1 netmask 255.255.255.0 vlan 115 vlandev igb2 # PAP Nothing logged in /var/log/* or crashes that exist in /var/crash PAP would indicate to me some sort of hardware related problem. PAP Have you tested your hardware lately and know that it is in operational order? PAP ~Paul PAP On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote: Hi. Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST FSCK Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG Apr 9 20:09:22 kernel: running manually: # fsck -y /dev/ad8s1e ** /dev/ad8s1e (NO WRITE) ** Last Mounted on /tmp ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 99 files, 10 used, 506477 free (45 frags, 63304 blocks, 0.0% fragmentation) Server reboot two or three time per day # uname -a FreeBSD flux 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #3 r231881: Fri Feb 24 17:07:48 UTC 2012 adm@flux:/usr/obj/usr/src/sys/KES_KERN_v8 amd64 before this it works about month without problems /var/crash - empty, in
Re: problem with Xorg
2012-04-10 16:50, Da Rock skrev: It gives a black screen. Vesa or not. Is that with the retro option? No it was not. Now I have fixed it, wife on my back so I had to fix it quickly. Pkg_delete \* cd x11-wm/xfce4 so now it starts up without errors. Thank you all for your input. ___ 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 with Xorg
On 04/12/12 02:28, Bernt Hansson wrote: 2012-04-10 16:50, Da Rock skrev: It gives a black screen. Vesa or not. Is that with the retro option? No it was not. Now I have fixed it, wife on my back so I had to fix it quickly. Pkg_delete \* cd x11-wm/xfce4 so now it starts up without errors. Thank you all for your input. Good to hear. Wives have a way of getting things done quickly, don't they? :) ___ 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 with Xorg
On 04/11/12 00:30, Bernt Hansson wrote: 2012-04-09 13:57, Da Rock skrev: On 04/09/12 21:38, Bernt Hansson wrote: 2012-04-09 13:03, Da Rock skrev: On 04/09/12 20:38, Bernt Hansson wrote: Hello list. When I try to start X I'm getting this error Yep. This one will be fun... :) No. Not really. Never is, let me tell you. X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.2-RELEASE i386 Current Operating System: FreeBSD kw.fqdn 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 Build Date: 09 April 2012 02:21:53AM Current version of pixman: 0.24.2 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: Mon Apr 9 12:30:37 2012 (==) Using default built-in configuration (30 lines) (EE) LoadModule: Module fbdevhw does not have a fbdevhwModuleData data object. (EE) Failed to load module fbdevhw (invalid module, 0) Setting master The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, butRALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xinit: connection to X server lost waiting for X server to shut down Dropping master First some questions: 1. Does the machine lock up when you run X? No It doesn't but no picture. 2. Do you know what video card you're using? Intel 845 3. What is the output of pciconf -lv, dmesg? pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x chip=0x25608086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'DRAM Controller / Host-Hub I/F Bridge (82845G/GL/GV/GE/PE)' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x00b90e11 chip=0x25628086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82845G/GL/GV/GE/PE Integrated Graphics Device' class = display subclass = VGA uhci0@pci0:0:29:0: class=0x0c0300 card=0x00b90e11 chip=0x24c28086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller *1' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0x00b90e11 chip=0x24c48086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller *2' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0x00b90e11 chip=0x24cd8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 2.0 EHCI Controller' class = serial bus subclass = USB pcib1@pci0:0:30:0: class=0x060400 card=0x chip=0x244e8086 rev=0x81 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x chip=0x24c08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:1:class=0x01018a card=0x00b90e11 chip=0x24cb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL (ICH4/ICH4-L) UltraATA/100 EIDE Controller' class = mass storage subclass = ATA pcm0@pci0:0:31:5: class=0x040100 card=0x00ad0e11 chip=0x24c58086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'Realtek AC97 Audio (82801DBM SoundMAXController (ICH4-M B0 step))' class = multimedia subclass = audio fxp0@pci0:5:8:0:class=0x02 card=0x00120e11 chip=0x103b8086 rev=0x81 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL (ICH4/ICH4-L) PRO/100 VM Network Connection' class = network subclass = ethernet 4. What does Xorg -configure produce? No idea, haven't tried it. Using HAL. Given your previous answers, I'd say you _have_ to run it. Then the last option I offered _will_ work. You need to force it to use vesa and that is the only way. It gives a black screen. Vesa or not. Is that with the retro option? As a last chance perhaps run X -conf /root/xorg.conf.new -retro and see if it does happen to work; this shows up the old test pattern so that you can see that X is actually running instead of a black screen. Finally, can you change the driver setting in the xorg.conf.new to
Re: problem with Xorg
On Mon, Apr 09, 2012 at 12:38:45PM +0200, Bernt Hansson wrote: Hi Bernt, Hello list. When I try to start X I'm getting this error X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.2-RELEASE i386 Current Operating System: FreeBSD kw.fqdn 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 Build Date: 09 April 2012 02:21:53AM Current version of pixman: 0.24.2 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: Mon Apr 9 12:30:37 2012 Please, can you paste ^^^ thsi file to ie. pastebin.com and share the URL ? For better help. Thanks, see you. ___ 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 with Xorg
On 04/09/12 20:38, Bernt Hansson wrote: Hello list. When I try to start X I'm getting this error Yep. This one will be fun... :) X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.2-RELEASE i386 Current Operating System: FreeBSD kw.fqdn 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 Build Date: 09 April 2012 02:21:53AM Current version of pixman: 0.24.2 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: Mon Apr 9 12:30:37 2012 (==) Using default built-in configuration (30 lines) (EE) LoadModule: Module fbdevhw does not have a fbdevhwModuleData data object. (EE) Failed to load module fbdevhw (invalid module, 0) Setting master The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xinit: connection to X server lost waiting for X server to shut down Dropping master First some questions: 1. Does the machine lock up when you run X? 2. Do you know what video card you're using? 3. What is the output of pciconf -lv, dmesg? 4. What does Xorg -configure produce? Finally, can you change the driver setting in the xorg.conf.new to vesa and run X -conf /root/xorg.conf.new and see if it works then? Good luck! ___ 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 with Xorg
On 04/09/12 21:38, Bernt Hansson wrote: 2012-04-09 13:03, Da Rock skrev: On 04/09/12 20:38, Bernt Hansson wrote: Hello list. When I try to start X I'm getting this error Yep. This one will be fun... :) X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 8.2-RELEASE i386 Current Operating System: FreeBSD kw.fqdn 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 Build Date: 09 April 2012 02:21:53AM Current version of pixman: 0.24.2 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: Mon Apr 9 12:30:37 2012 (==) Using default built-in configuration (30 lines) (EE) LoadModule: Module fbdevhw does not have a fbdevhwModuleData data object. (EE) Failed to load module fbdevhw (invalid module, 0) Setting master The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, butRALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server xinit: connection to X server lost waiting for X server to shut down Dropping master First some questions: 1. Does the machine lock up when you run X? No It doesn't but no picture. 2. Do you know what video card you're using? Intel 845 3. What is the output of pciconf -lv, dmesg? pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x chip=0x25608086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'DRAM Controller / Host-Hub I/F Bridge (82845G/GL/GV/GE/PE)' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x00b90e11 chip=0x25628086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82845G/GL/GV/GE/PE Integrated Graphics Device' class = display subclass = VGA uhci0@pci0:0:29:0: class=0x0c0300 card=0x00b90e11 chip=0x24c28086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller *1' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0x00b90e11 chip=0x24c48086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller *2' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0x00b90e11 chip=0x24cd8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 2.0 EHCI Controller' class = serial bus subclass = USB pcib1@pci0:0:30:0: class=0x060400 card=0x chip=0x244e8086 rev=0x81 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x chip=0x24c08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:1:class=0x01018a card=0x00b90e11 chip=0x24cb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL (ICH4/ICH4-L) UltraATA/100 EIDE Controller' class = mass storage subclass = ATA pcm0@pci0:0:31:5: class=0x040100 card=0x00ad0e11 chip=0x24c58086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'Realtek AC97 Audio (82801DBM SoundMAXController (ICH4-M B0 step))' class = multimedia subclass = audio fxp0@pci0:5:8:0:class=0x02 card=0x00120e11 chip=0x103b8086 rev=0x81 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB/DBL (ICH4/ICH4-L) PRO/100 VM Network Connection' class = network subclass = ethernet 4. What does Xorg -configure produce? No idea, haven't tried it. Using HAL. Given your previous answers, I'd say you _have_ to run it. Then the last option I offered _will_ work. You need to force it to use vesa and that is the only way. As a last chance perhaps run X -conf /root/xorg.conf.new -retro and see if it does happen to work; this shows up the old test pattern so that you can see that X is actually running instead of a black screen. Finally, can you change the driver setting in the xorg.conf.new to vesa and run X -conf /root/xorg.conf.new and see if it works then? Well, starting X from remote it seems to catch on. HmmmOnly as root. Well I'll try to rebuild it without SUID. This is from remote AND root
Re: problem with Xorg
On Mon, 9 Apr 2012, Da Rock wrote: On 04/09/12 21:38, Bernt Hansson wrote: 4. What does Xorg -configure produce? No idea, haven't tried it. Using HAL. Given your previous answers, I'd say you _have_ to run it. Then the last option I offered _will_ work. You need to force it to use vesa and that is the only way. Xorg autoconfigures itself. If HAL is used, it is only used for input devices, mouse and keyboard. Intel 845G should work with the x11-drivers/xf86-video-intel driver. ___ 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 with Xorg
On 04/10/12 00:36, Warren Block wrote: On Mon, 9 Apr 2012, Da Rock wrote: On 04/09/12 21:38, Bernt Hansson wrote: 4. What does Xorg -configure produce? No idea, haven't tried it. Using HAL. Given your previous answers, I'd say you _have_ to run it. Then the last option I offered _will_ work. You need to force it to use vesa and that is the only way. Xorg autoconfigures itself. If HAL is used, it is only used for input devices, mouse and keyboard. Intel 845G should work with the x11-drivers/xf86-video-intel driver. Should, but not always. At least vesa will get it going for the moment until a permanent solution arrives. ___ 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 bind in jail
On 05/04/2012 18:24, bsd wrote: I have decided to recompile bind in the latest version and I am running into a problem which is caused by bind port not following the FreeBSD requisites and trying to install things in /usr/include/isc What on earth gives you the idea that dns/bind98 doesn't conform to hier(7)? The bind ports are all installing stuff correctly: the only files that get installed in an 'isc' or 'isccc' sub-directory are c-language header files. That's perfectly legal according to the rules. No problem there. I suggest turning off the REPLACE_BASE option in the port. You really don't need it -- install as normal under /usr/local (which I guess should fix the writablity problems). Then all you need to enable the ports version of named is to put the following in /etc/rc.conf: named_enable=YES named_program=/usr/local/sbin/named That's it. You can now start up the ports version of named by: /etc/rc.d/named start The bind port creates symlinks for named.conf, rndc.conf and rndc.key in /usr/local/etc so you can control the ports version of bind in the usual way using rndc(8). (Well, assuming you've set up /etc/namedb/named.conf properly.) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem installing bind in jail
On 04/06/12 03:24, bsd wrote: Hi, I have followed the tutorial provided in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-application.html I have now five jails up and running and I am very happy with the system. One of my jail is acting as an important DNS server and It needs to be up to date. I have decided to recompile bind in the latest version and I am running into a problem which is caused by bind port not following the FreeBSD requisites and trying to install things in /usr/include/isc making all in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc/x86_32 making all in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc/x86_32/include making all in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc/x86_32/include/isc making install in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc/include making all in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc/include/isc making install in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc/include/isc /bin/sh ../../../../mkinstalldirs /usr/include/isc mkdir /usr/include/isc mkdir: /usr/include/isc: Read-only file system *** Error code 1 Stop in /s/portbuild/usr/ports/dns/bind98/work/bind-9.8.2/lib/isc/include/isc. […] I am not certain of the path I should take to solve this issue… Most probably I should simlink from the RO part of the system to the RW… but I am not 100% sure how to proceed. Why is ISC trying to setup things in this location and not on /usr/local/include/ ? I think I would need to simlink from the RO portion of the system /usr/include/isc to /usr/local/include/isc but I am not certain how to proceed. Assuming your replacing the base version, you cannot use symlinks but you can use a nullfs mount. You can make any part RW this way as long as its a directory. As Matthew pointed out, all is in order here. No rule breaks happening... :) ___ 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
On 04/01/12 13:18, jangkawij...@students.itb.ac.id wrote:
I've got the problem like this
Apr 1 17:03:15 johannesang named[576]: zone 79.205.167.in-addr.arpa/IN:
loading from master file /etc/namedb/master/db.johannesang failed: extra input
text
Apr 1 17:03:15 johannesang named[576]: zone 79.205.167.in-addr.arpa/IN: not
loaded due to errors.
Apr 1 17:03:15 johannesang named[576]:
/etc/namedb/master/localhost-reverse.db:2: no current owner name
Apr 1 17:03:15 johannesang named[576]: zone 0.ip6.arpa/IN: loading from master
file /etc/namedb/master/localhost-reverse.db failed: no owner
Apr 1 17:03:15 johannesang named[576]: zone 0.ip6.arpa/IN: not loaded due to
errors.
Apr 1 17:03:15 johannesang named[576]: zone 8.B.D.0.1.0.0.2.IP6.ARPA/IN: zone
serial (0) unchanged. zone may fail to transfer to slaves.
Apr 1 17:03:15 johannesang named[576]: dns_rdata_fromtext:
/etc/namedb/master/db.domain:5: near '3h': extra input text
Apr 1 17:03:15 johannesang named[576]: zone johannesang.com/IN: loading from
master file /etc/namedb/master/db.domain failed: extra input text
Apr 1 17:03:15 johannesang named[576]: zone johannesang.com/IN: not loaded due
to errors
here is localhost-reverse.db file
$FreeBSD: src/etc/namedb/master/localhost-reverse.db,v 1.1.14.1 2010/02/10
00:2
$TTL 3h
@ SOA localhost. nobody.localhost. 42 1d 12h 1w 3h
Serial, Refresh, Retry, Expire, Neg. cache TTL
NS localhost.
1.0.0 PTR localhost.
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 PTR localhost.
here is my db.domain file
$TTL3600
johannesang.com. IN SOA host.johannesang.com. root.johannesang.com. (
201204010042 1d12h 1w 3h
Serial, Refresh, Retry, Expire, Neg. cache TTL
;DNS Servers
johannesang.com. IN NS host.johannesang.com.
;Machine Names
host.johannesang.com.IN A 167.205.79.105
;Aliases
www IN CNAME host.johannesang.com.
here is my db.johannesang file
$TTL3600
79.205.167.in-addr.arpa. IN SOA host.johannesang.com. root.johannesang.com.
201204010042 1d12h 1w 3h
Serial, Refresh, Retry, Expire, Neg. cache TTL
DNS Servers
Is this a typo or actually in the file?
79.205.167.in-addr.arpa. IN NS host.johannesang.com.
;Machine IPs
105IN PTR host.johannesang.com.
105IN PTR www.johannesang.com.
and here is my named.conf
key rndc-key {
algorithm hmac-md5;
secret +W8n6komoiD9BRAfbbT//QsntsFScEs6gUXArJuH4Nk=;
};
zone johannesang.com {
type master;
file /etc/namedb/master/db.domain;
allow-transfer { localhost; };
allow-update { key rndc-key; };
};
zone 79.205.167.in-addr.arpa {
type master;
file /etc/namedb/master/db.johannesang;
allow-transfer { localhost; };
allow-update { key rndc-key; };
};
I need your help thanks
Did you update your serials?
I'd go back and check your zone files (for starters), and reread the
bind admin book on their format.
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: problem
The format of named files isn't quite as free-form as you apparently think. :-) Compare one of mine: $TTL 1H @ IN SOA ns3.radel.com. jon.radel.com. ( 2010100400 ; serial 1H ; refresh 15M ; retry 2W ; expiry 30M ) ; minimum IN NS ns.radel.com. IN NS ns2.radel.com. IN NS ns3.radel.com. IN NS ns4.radel.com. with yours: $TTL3600 OK johannesang.com. IN SOA host.johannesang.com. root.johannesang.com. ( OK; @ in mine is shorthand for the domain which this zone file defines, but giving the domain explicitly works fine. 201204010042 1d12h 1w 3h Starts as OK syntax, but a 42 second refresh with 1 day retry strikes me as dubious at best and then you have an extra value on the end. Actually, I suspect that 42 is actually your extra value. 2012040100 is the serial number, you know. Serial, Refresh, Retry, Expire, Neg. cache TTL This line is extraneous garbage, as you've not commented it out; that's what the semi-colons do in my example. I suspect that's why one error message moans about an error in the vicinity of the 3h, as that's an extra value followed by garbage. Missing close parenthesis. ;DNS Servers johannesang.com. IN NS host.johannesang.com. Looks fine. ;Machine Names host.johannesang.com.IN A 167.205.79.105 Looks fine ;Aliases www IN CNAME host.johannesang.com. Looks fine here is my db.johannesang file $TTL3600 79.205.167.in-addr.arpa. IN SOA host.johannesang.com. root.johannesang.com. 201204010042 1d12h 1w 3h missing open and close parenthesis, extra value Serial, Refresh, Retry, Expire, Neg. cache TTL extraneous garbage Etc. You're pretty close and it should work fine after you clean up your syntax a bit. --Jon Radel j...@radel.com
Re: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
Hi, I have the same error with virtualbox-ose-kmod 4.1.10 but only with FreeBSD 8.0 and 8.0-p2. With FreeBSD 8.2, no problem. Hope this help you for investigating this bug since I need it working on FreeBSD 8.0. Regards -- View this message in context: http://freebsd.1045724.n5.nabble.com/Problem-compiling-emulators-virtualbox-ose-kmod-4-1-8-2-tp5561048p5597254.html Sent from the freebsd-questions mailing list archive at Nabble.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
Re: Problem gnome2-2.32.1_4 not work libgcrypt-1.5.0 (freebsd 8.2 release)
On 25/03/2012 15:49, Андріан wrote: Hi, I use freebsd version 8.2-RELEASE, installed graphical shell gnome2-2.32.1_4, works without problems, I am satisfied, but that the problem appeared when I put the package remmina-0.9.3_1. But is the problem is that the package remmina-0.9.3_1 requires the presence of the package libgcrypt-1.5.0, and not work with the package libgcrypt-1.4.6, but gnome2-2.32.1_4 not work with libgcrypt-1.5.0 requires libgcrypt-1.4 .6. What to do? That's because the libgcrypt ABI version was incremented between 1.4.6 and 1.5.0 The standard approach to dealing with this is to recompile every port that contains applications linking against that shared library. The detailed instructions on how best to do that are in the 20110705 entry in /usr/ports/UPDATING. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
Mike Clarke jmc-freeb...@milibyte.co.uk writes:
On Friday 16 March 2012, Lowell Gilbert wrote:
My best advice is: clean out the directory for that port, update
again, and see if the problem is the same.
I've now deleted everything in /usr/ports/emulators/virtualbox-ose-kmod and
downloaded a fresh copy of the
port (4.1.10) from the FreeBSD website but still get the same problem when
compiling.
/data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.10/out/freebsd.x86/
release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405: error:
invalid type argument of '-'
*** Error code 1
That line is supposed to be an assignment in between a VM_OBJECT_LOCK
and the corresponding VM_OBJECT_UNLOCK. Can you confirm that the patches
cause this to be the case? It is a little tricky for me to edit files in
an i386 environment, but the next step is to track down the definition
of PRTR0MEMOBJFREEBSD, assuming that is the dereference giving the error
on your system, and determining whether it ought to have the structure
entry being dereferenced.
I've also updated the source files for the base system and built a new kernel
in case it's a header problem
since I noticed that /usr/src/include/unistd.h and
/usr/src/lib/libc/include/libc_private.h were both updated
in security advisory SA-11:07 (for which I only did a binary update at the
time) but this didn't cure the
problem.
I've had no problem building earlier versions but it went pear shaped with
4.1.8_2
As an experiment I've used portdowngrade to try compiling a few older
versions
number date portversion comment
1 2012/03/15 09:32:29 VirtualBox-${DISTVERSION} - Update to 4.1.10
2 2012/03/09 21:46:18 VirtualBox-${DISTVERSION}_2 - Reenabled fixed
memobj r0 patch
3 2012/02/22 22:09:41 VirtualBox-${DISTVERSION}_1 - Revert memobj r0
patch until the problems on i386
are solved
4 2012/02/21 14:31:54 VirtualBox-${DISTVERSION} - Update to 4.1.8
Of these, the only one to compile OK was 4.1.8_1 so it looks like the fixed
memobj r0 patch still has problems
on my system.
FreeBSD curlew.lan 8.1-RELEASE-p8 FreeBSD 8.1-RELEASE-p8 #0: Tue Mar 20
19:00:39 GMT 2012
r...@curlew.lan:/usr/obj/usr/src/sys/GENERIC i386
I can't reproduce the problem. My i386 system is a little weird, so that
may not say much.
Also, my system code trees are updated more recently than yours, which
may well matter for a kernel module, such as this port builds. You might
want to try updating your system or trying the -legacy version of the port.
Be well.
___
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 compiling emulators/virtualbox-ose-kmod 4.1.8_2
On Wednesday 21 March 2012, Lowell Gilbert wrote:
/data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-
4.1.10/out/freebsd.x86/
release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405:
error: invalid type argument of '-'
*** Error code 1
That line is supposed to be an assignment in between a VM_OBJECT_LOCK
and the corresponding VM_OBJECT_UNLOCK. Can you confirm that the
patches cause this to be the case?
Yes, that's where it is.
401 if (fContiguous)
402 {
403 Assert(enmType == RTR0MEMOBJTYPE_PHYS);
404 VM_OBJECT_LOCK(pMemFreeBSD-pObject);
405 pMemFreeBSD-Core.u.Phys.PhysBase =
VM_PAGE_TO_PHYS(vm_page_find_least(pMemFreeBSD-pObject, 0));
406 VM_OBJECT_UNLOCK(pMemFreeBSD-pObject);
407 pMemFreeBSD-Core.u.Phys.fAllocated = true;
408 }
It is a little tricky for me to
edit files in an i386 environment, but the next step is to track down
the definition of PRTR0MEMOBJFREEBSD, assuming that is the
dereference giving the error on your system, and determining whether
it ought to have the structure entry being dereferenced.
This takes me out of my depth in my very limited experience of C but would it
be
this, also in memobj-r0drv-freebsd.c:
50 /**
51 * The FreeBSD version of the memory object structure.
52 */
53 typedef struct RTR0MEMOBJFREEBSD
54 {
55 /** The core structure. */
56 RTR0MEMOBJINTERNAL Core;
57 /** Type dependent data */
58 /** The VM object associated with the allocation. */
59 vm_object_t pObject;
60 } RTR0MEMOBJFREEBSD, *PRTR0MEMOBJFREEBSD;
and then:
109 PRTR0MEMOBJFREEBSD pMemFreeBSD = (PRTR0MEMOBJFREEBSD)pMem;
[snip]
You might want to try updating your system or trying the -legacy
version of the port.
Version 4.1.8_1 seems to be working OK for me so I'll probably stick with that
for
the time being unless a fix turns up before I upgrade to 9.0-RELEASE which I'm
planning to do shortly.
--
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: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
Bernhard Froehlich de...@freebsd.org writes: Pointyhat has triggered the same compile error so it is real. Probably avg has a clue how to fix it. A (quick) look at pointyhat only shows me amd64 errors. My main build server (on amd64, building for i386 and amd64) doesn't see those problems, and neither does my i386 sandbox. This seems to be quite conditional, and I don't see much guidance as to what the conditions need to be. As good as Andriy has been on keeping up, I can't provide a debug case to solve for this problem. I'll try to come up with something more useful, but until/unless I can reproduce the problem, I'm not sure how to make progress. Be well. . ___ 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 compiling emulators/virtualbox-ose-kmod 4.1.8_2
On Friday 16 March 2012, Lowell Gilbert wrote:
My best advice is: clean out the directory for that port, update
again, and see if the problem is the same.
I've now deleted everything in /usr/ports/emulators/virtualbox-ose-kmod and
downloaded a fresh copy of the
port (4.1.10) from the FreeBSD website but still get the same problem when
compiling.
/data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.10/out/freebsd.x86/
release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405: error:
invalid type argument of '-'
*** Error code 1
I've also updated the source files for the base system and built a new kernel
in case it's a header problem
since I noticed that /usr/src/include/unistd.h and
/usr/src/lib/libc/include/libc_private.h were both updated
in security advisory SA-11:07 (for which I only did a binary update at the
time) but this didn't cure the
problem.
I've had no problem building earlier versions but it went pear shaped with
4.1.8_2
As an experiment I've used portdowngrade to try compiling a few older versions
number date portversion comment
1 2012/03/15 09:32:29 VirtualBox-${DISTVERSION} - Update to 4.1.10
2 2012/03/09 21:46:18 VirtualBox-${DISTVERSION}_2 - Reenabled fixed
memobj r0 patch
3 2012/02/22 22:09:41 VirtualBox-${DISTVERSION}_1 - Revert memobj r0
patch until the problems on i386
are solved
4 2012/02/21 14:31:54 VirtualBox-${DISTVERSION} - Update to 4.1.8
Of these, the only one to compile OK was 4.1.8_1 so it looks like the fixed
memobj r0 patch still has problems
on my system.
FreeBSD curlew.lan 8.1-RELEASE-p8 FreeBSD 8.1-RELEASE-p8 #0: Tue Mar 20
19:00:39 GMT 2012
r...@curlew.lan:/usr/obj/usr/src/sys/GENERIC i386
--
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: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
On Friday 16 March 2012, Adam Vande More wrote: On Tue, Mar 13, 2012 at 9:13 AM, Mike Clarke jmc-freeb...@milibyte.co.ukwrote: in /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox- 4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv. I ran portsnap immediately before portmaster so my ports are up to date. Any suggestions? Did you follow the relevant /usr/src/UPDATING instructions? The latest relevant one appears to be this: 20120221: AFFECTS: users of emulators/virtualbox-ose AUTHOR: de...@freebsd.org virtualbox-ose has been updated to 4.1.8 and requires the latest devel/kBuild-devel now. It is only a build dependency so it is safe to remove it before updating. # pkg_delete -f kBuild-\* I did this some time ago and the earlier version, 4.1.8_1, compiled fine but I started to have problems with 4.1.8_2 -- 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: Problem compiling emulators/virtualbox-ose-kmod 4.1.8_2
Mike Clarke jmc-freeb...@milibyte.co.uk writes: portmaster -a fails with: cc -O -pipe -march=athlon-mp -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_X86 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c: In function 'rtR0MemObjFreeBSDAllocPhysPages': /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405: error: invalid type argument of '-' *** Error code 1 Stop in /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv. I ran portsnap immediately before portmaster so my ports are up to date. Any suggestions? There have been more updates to the port since, and I don't see any failures in the automated builds. I've got a build on my fast system (RELENG_8, amd64) running now for a check, but it will take a while to grab the distfiles. You might want to grab the latest port and try it. ___ 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 compiling emulators/virtualbox-ose-kmod 4.1.8_2
Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org writes: Mike Clarke jmc-freeb...@milibyte.co.uk writes: portmaster -a fails with: cc -O -pipe -march=athlon-mp -DRT_OS_FREEBSD -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -w -DVBOX_WITH_HARDENING -DVBOX_WITH_64_BITS_GUESTS -DRT_ARCH_X86 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -Iinclude -I. -Ir0drv -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c: In function 'rtR0MemObjFreeBSDAllocPhysPages': /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv/r0drv/freebsd/memobj-r0drv-freebsd.c:405: error: invalid type argument of '-' *** Error code 1 Stop in /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv. I ran portsnap immediately before portmaster so my ports are up to date. Any suggestions? There have been more updates to the port since, and I don't see any failures in the automated builds. I've got a build on my fast system (RELENG_8, amd64) running now for a check, but it will take a while to grab the distfiles. You might want to grab the latest port and try it. And it builds fine for me. My best advice is: clean out the directory for that port, update again, and see if the problem is the same. ___ 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 compiling emulators/virtualbox-ose-kmod 4.1.8_2
On Tue, Mar 13, 2012 at 9:13 AM, Mike Clarke jmc-freeb...@milibyte.co.ukwrote: in /data1/tmp/usr/ports/emulators/virtualbox-ose-kmod/work/VirtualBox-4.1.8_OSE/out/freebsd.x86/release/bin/src/vboxdrv. I ran portsnap immediately before portmaster so my ports are up to date. Any suggestions? Did you follow the relevant /usr/src/UPDATING instructions? -- Adam Vande More ___ 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 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
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: 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
