AUTO: KVVSN Murthy is out of the office. (returning 11/07/2012)
I am out of the office until 11/07/2012. Please coordinate with miss Swetha for my PET related activities. Note: This is an automated response to your message freebsd-questions Digest, Vol 439, Issue 7 sent on 11/3/2012 9:55:02 AM. This is the only notification you will receive while this person is away. Disclaimer This message contains legally privileged and/or confidential information. If you are not the intended recipient(s), or employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this 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: Testing for false email freebsd.org
Hi, Reference: From: Al Plant n...@hdk5.net Date: Fri, 02 Nov 2012 13:17:17 -1000 Message-id: 5094547d.5030...@hdk5.net To: freebsd-t...@freebsd.org, freebsd-questions questi...@freebsd.org Al Plant wrote: Test Read list mandates. Cross posting is deprecated Send test mail only to t...@freebsd.org 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. Not: HTML, multipart/alternative, base64, quoted-printable. ___ 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: ATI HD 4850 driver
Hi, there's something wrong with the dri package list. The original pkg-list (look attachment) shows the reason why the r600 driver was not correctly installed: all drivers in the pkg-list have the same path: /lib/dri/rxx_dri.so except for the r600 driver which is preceded by these characters: %%MESALIB76%%lib/dri/r600_dri.so Is there a reason why the path from the r600_dri.so driver is preceded by the characters %%MESALIB76%% ? kind regards, Dirk On 11/02/12 22:21, Warren Block wrote: On Fri, 2 Nov 2012, ds wrote: I installed stellarium and the 3d acceleration of my ATI 4850 card didn't work in FreeBSD 9.0. The /var/log/Xorg.0.log showed that AIGLX could not load the r600_dri.so driver because it was missing in the /usr/local/lib/dri/ folder. So I recovered the r600_dri.so file from a PCBSD 9.0 installation and copied it to my FreeBSD 9.0 /usr/local/lib/dri/ folder and now my 3d acceleration works. Are there plans to resolve this bug in FreeBSD version 9.1 ? It's hard to say what happened on your system, but it works on others. The DRI libraries are installed by the graphics/dri port. Deinstalling, rebuilding, and reinstalling that port should create them. If it does not, something else is wrong on that system. include/GL/internal/dri_interface.h lib/dri/i810_dri.so lib/dri/i915_dri.so lib/dri/i965_dri.so lib/dri/mach64_dri.so lib/dri/mga_dri.so lib/dri/r128_dri.so lib/dri/r200_dri.so lib/dri/r300_dri.so %%MESALIB76%%lib/dri/r600_dri.so lib/dri/radeon_dri.so lib/dri/savage_dri.so lib/dri/sis_dri.so lib/dri/swrast_dri.so lib/dri/tdfx_dri.so lib/dri/unichrome_dri.so libdata/pkgconfig/dri.pc @dirrm lib/dri @dirrmtry include/GL/internal @dirrmtry include/GL ___ 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: ATI HD 4850 driver
Hello, I've just downloaded the dri-7.4.4,2.tbz from this link : ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.0-release/graphics/ and the r600_dri.so driver is NOT included in the unpacked /lib/dri folder. As I said, I had to copy the r600_dri driver from a working PCBSD 9.0 system to make my ATI HD 4850 work. kind regards, Dirk System information: AMD phenom II X4 on Asus M4A77T/USB3 mainboard 4GB ddr3 Asus ATI 4850 FreeBSD 9.0 amd64 with blackbox window manager. On 11/02/12 22:21, Warren Block wrote: On Fri, 2 Nov 2012, ds wrote: I installed stellarium and the 3d acceleration of my ATI 4850 card didn't work in FreeBSD 9.0. The /var/log/Xorg.0.log showed that AIGLX could not load the r600_dri.so driver because it was missing in the /usr/local/lib/dri/ folder. So I recovered the r600_dri.so file from a PCBSD 9.0 installation and copied it to my FreeBSD 9.0 /usr/local/lib/dri/ folder and now my 3d acceleration works. Are there plans to resolve this bug in FreeBSD version 9.1 ? It's hard to say what happened on your system, but it works on others. The DRI libraries are installed by the graphics/dri port. Deinstalling, rebuilding, and reinstalling that port should create them. If it does not, something else is wrong on that system. ___ 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: ATI HD 4850 driver
On 11/04/12 00:08, ds wrote: Hi, there's something wrong with the dri package list. The original pkg-list (look attachment) shows the reason why the r600 driver was not correctly installed: all drivers in the pkg-list have the same path: /lib/dri/rxx_dri.so except for the r600 driver which is preceded by these characters: %%MESALIB76%%lib/dri/r600_dri.so Is there a reason why the path from the r600_dri.so driver is preceded by the characters %%MESALIB76%% ? Try the ports list - this is a feature to make porting easier; as to why it is denying the install of that particular library I couldn't say right now as its late and I'm tired. If I get a chance I'll have a better look after. Good luck :) kind regards, Dirk On 11/02/12 22:21, Warren Block wrote: On Fri, 2 Nov 2012, ds wrote: I installed stellarium and the 3d acceleration of my ATI 4850 card didn't work in FreeBSD 9.0. The /var/log/Xorg.0.log showed that AIGLX could not load the r600_dri.so driver because it was missing in the /usr/local/lib/dri/ folder. So I recovered the r600_dri.so file from a PCBSD 9.0 installation and copied it to my FreeBSD 9.0 /usr/local/lib/dri/ folder and now my 3d acceleration works. Are there plans to resolve this bug in FreeBSD version 9.1 ? It's hard to say what happened on your system, but it works on others. The DRI libraries are installed by the graphics/dri port. Deinstalling, rebuilding, and reinstalling that port should create them. If it does not, something else is wrong on that system. ___ 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: Faking Gateway
On 11/03/2012 01:35 PM, Jos Chrispijn wrote: I have two gateway ip's in my network: G1 = 8/1m and G2=50/10m. Server1 (S1) is connected to G1 and all network clients are connected to G2. As I sometimes have a lot of ports to download, I thought, let's change the gateway address of S1 to G2. That really works regarding the FTP part, but regarding my mail it is not (logically I am now presenting a domain name that doesn't match its ip address as it is G2 instead of G1). Is there a way of switching to the 'fast' gateway with ftp traffic only (like port updates and manual outward/inbound ftp requests) and have outbound email follow the (standard) G1)? Kind regards, Jos Chrispijn ___ 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 Hi, Some 'match out on $netif to $ext_net port smtp route-to ( $netif $gw_1m )' should work. Regards. ___ 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
before new version
Hi! Could someone explain, please why ports should be frozen before a new version of FreeBSD came out? It happened all the time and after update (if you update or not) there are so many ports for updating. In case for very long waiting for version 9.1 will be thousands of them. Thank you very much. Mitja http://www.redbubble.com/people/lumiwa ___ 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
Subversion - Sync Branch with Trunk
Hello, During my GSoC project, I branched HEAD in order to use it for the development of the client side part of my project. After some changes, I tried to sync my branch with HEAD but I have faced an error. Now, I am trying once again to sync my branch with HEAD, but I get the exact same error. The error is the following: svn: E175002: PROPFIND of '/socsvn/!svn/bc/236241/mirror/FreeBSD/head/sys/dev/usb/controller': 207 Multi-Status (https://socsvn.freebsd.org) svn: E175002: Error reading spooled REPORT request response The error appears after 2 hours of syncing my branch with HEAD, with U (updated) as the svn status code for most of the files, and 4-6 of them that I resolved the conflicts by selecting tf (theirs-full). This is what I do to sync my branch with trunk (as described in the SVN Book [1]): # the root of my working copy, it contains the .svn, client-side, and server-side directories cd /home/tzabal/akcrs svn status if [ no local modifications reported ]; then svn merge https://socsvn.freebsd.org/socsvn/mirror/FreeBSD/head client-side/akcrs-head fi Can you propose any solutions in order to sync my branch with HEAD? Regards [1] Keeping a Branch in Sync, http://svnbook.red-bean.com/en/1.6/svn.branchmerge.basicmerging.html P.S. The project's code is located at http://svnweb.freebsd.org/socsvn/soc2012/tzabal/ -- Tzanetos Balitsaris This message was sent using IMP, the Internet Messaging Program. ___ 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
Booting 2nd(!) FreeBSD installation sitting on same disk
For various reasons I have to use this disk layout: One harddisk with MBR and 3 slices on a i386 box: Slice 1: Windows XP :-( Slice 2: FreeBSD 7.4-STABLE V1 Slice 3: FreeBSD 7.4-STABLE V2 The MBR is configured as: options=packet,noupdate,nosetdrv default_selection=F2 (Slice 2) When booting, I can choose between: F1 Win F2 FreeBSD F3 FreeBSD However, when pressing F3, the system of slice 2(!) is loaded. This is due to the fact that boot1 always loads the first active FreeBSD slice ;-(. I have two possibilities to actually boot slice 3: 1. Playing with currdev when loader(8) is loaded (or using loader.conf of slice 2). 2. Using boot0cfg to allow updating the MBR. 1. is not really fexible and 2. means that the system remembers which slice was booted last (something I do not want). Is there no chance to actually honour the fact that F3 was pressed and boot from slice 3 without updating the MBR before? Thanks, -Andre ___ 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: before new version
On Sat, 3 Nov 2012 11:23:12 -0500, ajtiM wrote: Hi! Could someone explain, please why ports should be frozen before a new version of FreeBSD came out? The idea is to make sure that RELEASE can be shipped with installation media (CD, DVD) for offline use which requires ports mostly to be tested and working in some specific state, and then the packages (those you can access on the installation media) are generated from them. It's handy for systems that do not have Internet access to install software off-line. It happened all the time and after update (if you update or not) there are so many ports for updating. In case for very long waiting for version 9.1 will be thousands of them. That could probably be. Most users who have Internet access and run servers (and also home systems) will tend to update the OS beyond RELEASE and also do so with the ports collection, or alternatively also use pkg_add -r from the Latest/ directory instead of RELEASE (which _always_ contains the ports generated from the frozen ports tree). -- 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: before new version
On Saturday 03 November 2012 12:18:35 Polytropon wrote: On Sat, 3 Nov 2012 11:23:12 -0500, ajtiM wrote: Hi! Could someone explain, please why ports should be frozen before a new version of FreeBSD came out? The idea is to make sure that RELEASE can be shipped with installation media (CD, DVD) for offline use which requires ports mostly to be tested and working in some specific state, and then the packages (those you can access on the installation media) are generated from them. It's handy for systems that do not have Internet access to install software off-line. It happened all the time and after update (if you update or not) there are so many ports for updating. In case for very long waiting for version 9.1 will be thousands of them. That could probably be. Most users who have Internet access and run servers (and also home systems) will tend to update the OS beyond RELEASE and also do so with the ports collection, or alternatively also use pkg_add -r from the Latest/ directory instead of RELEASE (which _always_ contains the ports generated from the frozen ports tree). Thank you very much. BTW: packages are almost all the time outdated. Mitja http://www.redbubble.com/people/lumiwa ___ 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: Booting 2nd(!) FreeBSD installation sitting on same disk
On Sat, Nov 3, 2012 at 9:54 AM, Andre Albsmeier andre.albsme...@siemens.com wrote: For various reasons I have to use this disk layout: One harddisk with MBR and 3 slices on a i386 box: Slice 1: Windows XP :-( Slice 2: FreeBSD 7.4-STABLE V1 Slice 3: FreeBSD 7.4-STABLE V2 The MBR is configured as: options=packet,noupdate,nosetdrv default_selection=F2 (Slice 2) When booting, I can choose between: F1 Win F2 FreeBSD F3 FreeBSD However, when pressing F3, the system of slice 2(!) is loaded. This is due to the fact that boot1 always loads the first active FreeBSD slice ;-(. I have two possibilities to actually boot slice 3: 1. Playing with currdev when loader(8) is loaded (or using loader.conf of slice 2). 2. Using boot0cfg to allow updating the MBR. 1. is not really fexible and 2. means that the system remembers which slice was booted last (something I do not want). Is there no chance to actually honour the fact that F3 was pressed and boot from slice 3 without updating the MBR before? Thanks, -Andre There is the following port for managing boot selections : ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.0-release/Latest/grub2.tbz http://www.freshports.org/sysutils/grub2/ I do NOT know whether it may be useful for you or not . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 9.1 and SU+J
On 03.11.2012 13:48, Doug Hardie wrote: I didn't notice that journaling is on by default and now dump is failing. The only way I can see to disable journaling requires that the file system be dismounted, or read-only. This is a remote machine and journaling is on root. Is there any other way that would not require me to make a long trip out to the site? This is a task for mfsBSD: http://mfsbsd.vx.sk -- 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: before new version
On Sat, 3 Nov 2012 12:25:12 -0500, ajtiM wrote: On Saturday 03 November 2012 12:18:35 Polytropon wrote: On Sat, 3 Nov 2012 11:23:12 -0500, ajtiM wrote: Hi! Could someone explain, please why ports should be frozen before a new version of FreeBSD came out? The idea is to make sure that RELEASE can be shipped with installation media (CD, DVD) for offline use which requires ports mostly to be tested and working in some specific state, and then the packages (those you can access on the installation media) are generated from them. It's handy for systems that do not have Internet access to install software off-line. It happened all the time and after update (if you update or not) there are so many ports for updating. In case for very long waiting for version 9.1 will be thousands of them. That could probably be. Most users who have Internet access and run servers (and also home systems) will tend to update the OS beyond RELEASE and also do so with the ports collection, or alternatively also use pkg_add -r from the Latest/ directory instead of RELEASE (which _always_ contains the ports generated from the frozen ports tree). Thank you very much. BTW: packages are almost all the time outdated. The packages in the RELEASE directory and on the installation media meet the frozen ports tree (frozen _prior_ to the release date), so yes, they are a bit outdated, but they are considered mostly stable and usable when in use with what is distributed. On the server, both _those_ packages _and_ those in Latest/ (which are periodically built from the advancing ports tree after the release date) are often considered not _that_ current as if you would use CVS or SVN to obtain the bleeding edge latest ports tree and build from source. So yes, you could say what you said. :-) -- 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: before new version
On Saturday 03 November 2012 14:11:22 you wrote: BTW: packages are almost all the time outdated. The packages in the RELEASE directory and on the installation media meet the frozen ports tree (frozen _prior_ to the release date), so yes, they are a bit outdated, but they are considered mostly stable and usable when in use with what is distributed. On the server, both _those_ packages _and_ those in Latest/ (which are periodically built from the advancing ports tree after the release date) are often considered not _that_ current as if you would use CVS or SVN to obtain the bleeding edge latest ports tree and build from source. I didn't complain about bleeding edge sofware which we anywhere don't have (Gimp, Xorg, LibreOffice and all dependencies for those applications and more and more which I don't use and I don't need) but I complain about freezing ports too early before new release came out and after that rebuilt 5000 ports for example just because png new version is coming out. Or am I wrong? So yes, you could say what you said. :-) Mitja http://www.redbubble.com/people/lumiwa ___ 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: Booting 2nd(!) FreeBSD installation sitting on same disk
Andre Albsmeier Andre.Albsmeier at siemens.com writes: ... However, when pressing F3, the system of slice 2(!) is loaded. This is due to the fact that boot1 always loads the first active FreeBSD slice ;-(. ... Is there no chance to actually honour the fact that F3 was pressed and boot from slice 3 without updating the MBR before? I do not know the story of active slice in FreeBSD, but I know that neither Windows nor Linux require active partitions (in their jargon) to boot from any more. Perhaps it is time to review this requirement in FreeBSD and drop it if possible. Opinions are welcome. If there are no counterarguments, we will create a PR# to start the process. jb ___ 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: Booting 2nd(!) FreeBSD installation sitting on same disk
jb jb.1234abcd at gmail.com writes: ... I do not know the story of active slice in FreeBSD, but I know that neither Windows nor Linux require active partitions (in their jargon) to boot from any more. Perhaps it is time to review this requirement in FreeBSD and drop it if possible. Opinions are welcome. If there are no counterarguments, we will create a PR# to start the process. I forgot to mention that in such case a new boot option would be introduced to set a default boot item in a boot manager's menu. jb ___ 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: Burning .iso DVD's
On Fri, Nov 2, 2012 at 5:12 PM, Al Plant n...@hdk5.net wrote: Aloha, I am not able to get a successfull burn of .iso DVD's 9.0 or higher FreeBSD. Chapter 19.7 ... of Handbook says to use growisofs with ATAPI support same as I do for 7.* 8.* FreeBSD etc. I get error of no growisofs ..when I run growisofs -dvd-compat -Z /dev/cd0=image.iso growisofs is part of the dvd+rw-tools port/package. -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
