Re: Can't install WindowMaker
On 11 March 2012 04:17, Sabine Baer wrote: > Sorry if I'm totally wrong here but I don't know where to ask. > > I'm using WindowMaker as my window manager for some years. I do not > remember why, but some days ago, I deinstalled ist. Now, I can't > install it. > > $uname -rp > |7.4-STABLE amd64 > > #portmaster -aD > |all up to date (had a long run of updating gcc46 and others this > |morning) > > #portmaster /x11-wm/windomaker > |[...] > |handlers.c:542: warning: implicit declaration of function 'FD_ISSET' > |*** Error code 1 I know I'm going back a ways here but: Unless you have WERROR set, I don't think that warning is the thing giving you "*** Error code 1". Look up a bit (or a lot) higher. -- -- ___ 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: Can't install WindowMaker
On Mon, Mar 19, 2012 at 11:49:20AM +, Frank Shute wrote: [...] > You're not by any chance using gcc46 to compile Windowmaker? $gcc --version gcc (GCC) 4.2.2 20070831 prerelease [FreeBSD] [...] $ > If so, don't. Use the base compiler. It might be that I had installed some newer versions, but since I made a 'pkg_delete *', 'ls /var/db/pkg/gcc* gives only 'gccmakedep' which is installed by some of the freshly installed ports. Sabine -- Le cardinal César Baronius avait raison: "Le Saint-Esprit nous apprend comment aller au ciel et non pas comment va le ciel". (Kardinal Poupard) ___ 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 9's SSH HPN
Is the HPN patchset included with the base OpenSSH the full patchset? Does it include the threaded CTR patch? I can't seem to find a clear answer to this. Thanks, Mark ___ 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: Dualboot with Windows 7
On 19 March 2012 17:46, David Demelier wrote: > On 19/03/2012 17:53, Leslie Jensen wrote: >> >> >> >> 2012-03-19 08:53, Da Rock skrev: >>> >>> On 03/19/12 17:49, Polytropon wrote: On Mon, 19 Mar 2012 08:29:22 +0100, David Demelier wrote: > > On 19/03/2012 07:28, Polytropon wrote: >> >> On Sun, 18 Mar 2012 23:05:58 +0100, David Demelier wrote: >>> >>> Hello, >>> >>> I try to create a dualboot with Windows 7, I set up partitions like >>> that : >>> >>> ada0s1 -> NTFS (windows recovery) >>> ada0s2 -> NTFS (windows main partition) >>> ada0s3 -> BSD >>> ada0s3a -> freebsd-swap (3G) >>> ada0s3b -> freebsd-ufs / (remaining space from drive) >> >> Erm... according to traditional partitioning, isn't >> the 'a' partition reserved for booting, 'b' for swap? >> I see you have installed everything into one / partition >> which technically is no problem and should work, but >> it's not on the boot partition. >> >> > You're right, but I made a mistake while writing, my a partition is / > and b is swap. Okay. >>> And then I let the installer complete the step, because FreeBSD >>> didn't >>> let you (since 9.0) choose between the boot manager nothing was >>> installed and the boot directly goes to Windows 7. >> >> You need to install all the required stages for booting. >> If I understand the process correctly, the slice 's3' needs >> code to "branch" to the boot partition (which is supposed >> to be the 'a' partition), and the boot selector needs to >> be accessed from the "beginning of the disk" - you said >> you're using EasyBCD for this which is okay. >> >> > I followed the part 13.3.2 from > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html > > > > I think this should be enough, isn't it? it says bsdlabel -B will > replace the boot1 and boot2 stage so all of them are installed. Looks correct. > Now the question is how to branch the a partition as the "boot > partition" ? No need. As soon as the "branching" from ada0-"start" -> ada0s3 has been processed, the 'a' partition ada0s3a will be accessed as it is the boot partition. It will then continue stage 1 and 2 and finally access the loader, which will load the kernel. In 13.3.2 it is explained as follows: They [Stage One, /boot/boot1, and Stage Two, /boot/boot2] are located outside file systems, in the first track of the boot slice, starting with the first sector. This is where boot0, or any other boot manager, expects to find a program to run which will continue the boot process. The number of sectors used is easily determined from the size of /boot/boot. In your case, the "boot slice" (for FreeBSD) is ada0s3 where the boot manager EasyBCD will "branch" to. Getting just a cursor (as you described) makes it hard to identify where the process hangs. If EasyBCD is the last thing you see, I assume the FreeBSD boot process isn't even initiated. Every part of it (MBR boot manager, boot0, boot1, boot2 and loader) would issue some kind of text when accessed. >>> >>> I couldn't say exactly how to do this now (been a long time), but >>> you should be able to boot using the Windows loader (this may have >>> changed in recent editions. Don't think so though). This will give you a >>> choice between Windows or FreeBSD and defaults, timers, etc during boot. >>> Used to be able to do it under system properties I believe; run a google >>> search should provide some examples. >> >> >> >> Using EasyBCD you must ensure that your Windows partition has the boot >> flag set. >> >> /Leslie >> >> >> >> >> >> >> >> >> >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscr...@freebsd.org" >> >> ___ >> 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 reinstalled using the auto scheme, by adding a partition now it works. > Thanks for your answers! > > Cheers, > > -- > David Demelier > > ___ > 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" have you tried fdisk -B ada0 to install the bsd bootloader? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscrib
Re: Problems with portaudit after update to 0.6.0
On Mon, 19 Mar 2012 11:14:13 -0300 "Fábio Jr." wrote: > Hi folks, > > I'm facing problems after updating the portaudit to 0.6.0. This is > happening on 2 server I own, both with FreeBSD 6.2. Check this out: You obviously have missed that FreeBSD 6.x is no longer supported. RELENG_6's EOL was November 30, 2010: http://article.gmane.org/gmane.os.freebsd.security.announce/194 You should upgrade to 7.4 or 8.2 (soon 8.3). -- 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: Problems with portaudit after update to 0.6.0
El día 19 de marzo de 2012 08:14, "Fábio Jr." escribió: > Hi folks, > > I'm facing problems after updating the portaudit to 0.6.0. This is happening > on 2 server I own, both with FreeBSD 6.2. Check this out: > > /# portaudit -Fda/ > /auditfile.tbz 100% of 75 kB 381 > kBps/ > /unknown option '-sha256'/ > /options are/ > /-c to output the digest with separating colons/ > /-d to output debug info/ > /-hex output as hex dump/ > /-binary output in binary form/ > /-sign file sign digest using private key in file/ > /-verify file verify a signature using public key in file/ > /-prverify file verify a signature using private key in file/ > /-keyform arg key file format (PEM or ENGINE)/ > /-signature file signature to verify/ > /-binary output in binary form/ > /-engine e use engine e, possibly a hardware device./ > /-md5 to use the md5 message digest algorithm (default)/ > /-md4 to use the md4 message digest algorithm/ > /-md2 to use the md2 message digest algorithm/ > /-sha1 to use the sha1 message digest algorithm/ > /-sha to use the sha message digest algorithm/ > /-mdc2 to use the mdc2 message digest algorithm/ > /-ripemd160 to use the ripemd160 message digest algorithm/ > /portaudit: Database contains invalid signature./ > /Old database restored./ > /portaudit: Download failed./ > > This happens too when I try to update any other package. This is what I > already tried to do to solve the problem: > > - portsnap fetch update / portupgrade on the portaudit folder in ports > - portsnap fetch update / make deinstall / make install the package > - make deinstall / portsnap fetch update / make install the package > - portsnap fetch extract / make deinstall / make install the package > - make deinstall / portsnap fetch extract / make install the package > > None of this solved the problem. > > Anybody else having the same issue, or some idea on how to solve it? > Try verbose mode. portaudit -Fv 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"
Re: Dualboot with Windows 7
On 19/03/2012 17:53, Leslie Jensen wrote: 2012-03-19 08:53, Da Rock skrev: On 03/19/12 17:49, Polytropon wrote: On Mon, 19 Mar 2012 08:29:22 +0100, David Demelier wrote: On 19/03/2012 07:28, Polytropon wrote: On Sun, 18 Mar 2012 23:05:58 +0100, David Demelier wrote: Hello, I try to create a dualboot with Windows 7, I set up partitions like that : ada0s1 -> NTFS (windows recovery) ada0s2 -> NTFS (windows main partition) ada0s3 -> BSD ada0s3a -> freebsd-swap (3G) ada0s3b -> freebsd-ufs / (remaining space from drive) Erm... according to traditional partitioning, isn't the 'a' partition reserved for booting, 'b' for swap? I see you have installed everything into one / partition which technically is no problem and should work, but it's not on the boot partition. You're right, but I made a mistake while writing, my a partition is / and b is swap. Okay. And then I let the installer complete the step, because FreeBSD didn't let you (since 9.0) choose between the boot manager nothing was installed and the boot directly goes to Windows 7. You need to install all the required stages for booting. If I understand the process correctly, the slice 's3' needs code to "branch" to the boot partition (which is supposed to be the 'a' partition), and the boot selector needs to be accessed from the "beginning of the disk" - you said you're using EasyBCD for this which is okay. I followed the part 13.3.2 from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html I think this should be enough, isn't it? it says bsdlabel -B will replace the boot1 and boot2 stage so all of them are installed. Looks correct. Now the question is how to branch the a partition as the "boot partition" ? No need. As soon as the "branching" from ada0-"start" -> ada0s3 has been processed, the 'a' partition ada0s3a will be accessed as it is the boot partition. It will then continue stage 1 and 2 and finally access the loader, which will load the kernel. In 13.3.2 it is explained as follows: They [Stage One, /boot/boot1, and Stage Two, /boot/boot2] are located outside file systems, in the first track of the boot slice, starting with the first sector. This is where boot0, or any other boot manager, expects to find a program to run which will continue the boot process. The number of sectors used is easily determined from the size of /boot/boot. In your case, the "boot slice" (for FreeBSD) is ada0s3 where the boot manager EasyBCD will "branch" to. Getting just a cursor (as you described) makes it hard to identify where the process hangs. If EasyBCD is the last thing you see, I assume the FreeBSD boot process isn't even initiated. Every part of it (MBR boot manager, boot0, boot1, boot2 and loader) would issue some kind of text when accessed. I couldn't say exactly how to do this now (been a long time), but you should be able to boot using the Windows loader (this may have changed in recent editions. Don't think so though). This will give you a choice between Windows or FreeBSD and defaults, timers, etc during boot. Used to be able to do it under system properties I believe; run a google search should provide some examples. Using EasyBCD you must ensure that your Windows partition has the boot flag set. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ 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 reinstalled using the auto scheme, by adding a partition now it works. Thanks for your answers! Cheers, -- David Demelier ___ 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: Dualboot with Windows 7
2012-03-19 08:53, Da Rock skrev: On 03/19/12 17:49, Polytropon wrote: On Mon, 19 Mar 2012 08:29:22 +0100, David Demelier wrote: On 19/03/2012 07:28, Polytropon wrote: On Sun, 18 Mar 2012 23:05:58 +0100, David Demelier wrote: Hello, I try to create a dualboot with Windows 7, I set up partitions like that : ada0s1 -> NTFS (windows recovery) ada0s2 -> NTFS (windows main partition) ada0s3 -> BSD ada0s3a -> freebsd-swap (3G) ada0s3b -> freebsd-ufs / (remaining space from drive) Erm... according to traditional partitioning, isn't the 'a' partition reserved for booting, 'b' for swap? I see you have installed everything into one / partition which technically is no problem and should work, but it's not on the boot partition. You're right, but I made a mistake while writing, my a partition is / and b is swap. Okay. And then I let the installer complete the step, because FreeBSD didn't let you (since 9.0) choose between the boot manager nothing was installed and the boot directly goes to Windows 7. You need to install all the required stages for booting. If I understand the process correctly, the slice 's3' needs code to "branch" to the boot partition (which is supposed to be the 'a' partition), and the boot selector needs to be accessed from the "beginning of the disk" - you said you're using EasyBCD for this which is okay. I followed the part 13.3.2 from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html I think this should be enough, isn't it? it says bsdlabel -B will replace the boot1 and boot2 stage so all of them are installed. Looks correct. Now the question is how to branch the a partition as the "boot partition" ? No need. As soon as the "branching" from ada0-"start" -> ada0s3 has been processed, the 'a' partition ada0s3a will be accessed as it is the boot partition. It will then continue stage 1 and 2 and finally access the loader, which will load the kernel. In 13.3.2 it is explained as follows: They [Stage One, /boot/boot1, and Stage Two, /boot/boot2] are located outside file systems, in the first track of the boot slice, starting with the first sector. This is where boot0, or any other boot manager, expects to find a program to run which will continue the boot process. The number of sectors used is easily determined from the size of /boot/boot. In your case, the "boot slice" (for FreeBSD) is ada0s3 where the boot manager EasyBCD will "branch" to. Getting just a cursor (as you described) makes it hard to identify where the process hangs. If EasyBCD is the last thing you see, I assume the FreeBSD boot process isn't even initiated. Every part of it (MBR boot manager, boot0, boot1, boot2 and loader) would issue some kind of text when accessed. I couldn't say exactly how to do this now (been a long time), but you should be able to boot using the Windows loader (this may have changed in recent editions. Don't think so though). This will give you a choice between Windows or FreeBSD and defaults, timers, etc during boot. Used to be able to do it under system properties I believe; run a google search should provide some examples. Using EasyBCD you must ensure that your Windows partition has the boot flag set. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ 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"
Problems with portaudit after update to 0.6.0
Hi folks, I'm facing problems after updating the portaudit to 0.6.0. This is happening on 2 server I own, both with FreeBSD 6.2. Check this out: /# portaudit -Fda/ /auditfile.tbz 100% of 75 kB 381 kBps/ /unknown option '-sha256'/ /options are/ /-c to output the digest with separating colons/ /-d to output debug info/ /-hexoutput as hex dump/ /-binary output in binary form/ /-sign filesign digest using private key in file/ /-verify fileverify a signature using public key in file/ /-prverify file verify a signature using private key in file/ /-keyform argkey file format (PEM or ENGINE)/ /-signature file signature to verify/ /-binary output in binary form/ /-engine e use engine e, possibly a hardware device./ /-md5 to use the md5 message digest algorithm (default)/ /-md4 to use the md4 message digest algorithm/ /-md2 to use the md2 message digest algorithm/ /-sha1 to use the sha1 message digest algorithm/ /-sha to use the sha message digest algorithm/ /-mdc2 to use the mdc2 message digest algorithm/ /-ripemd160 to use the ripemd160 message digest algorithm/ /portaudit: Database contains invalid signature./ /Old database restored./ /portaudit: Download failed./ This happens too when I try to update any other package. This is what I already tried to do to solve the problem: - portsnap fetch update / portupgrade on the portaudit folder in ports - portsnap fetch update / make deinstall / make install the package - make deinstall / portsnap fetch update / make install the package - portsnap fetch extract / make deinstall / make install the package - make deinstall / portsnap fetch extract / make install the package None of this solved the problem. Anybody else having the same issue, or some idea on how to solve it? Thank 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: dbus, epiphany, rekonq
On 03/19/12 23:07, Anton Shterenlikht wrote: On Mon, Mar 19, 2012 at 01:44:23PM +0100, Polytropon wrote: On Mon, 19 Mar 2012 12:21:29 +, Anton Shterenlikht wrote: I can't lauch www/epiphany or www/rekonq on ia64 -current, due to some dbus issue: TZAV> ps ax|grep dbus 1435 - Is 0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --sess 1434 2- I0:00.01 dbus-launch --autolaunch=fb0372ea595109904f5a068e0180 --binary-synta 41284 5 RL+ 0:00.00 grep dbus TZAV> epiphany ** (epiphany:41285): WARNING **: Unable to connect to session bus: Failed to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or directory TZAV> rekonq unnamed app(41291): KUniqueApplication: Cannot find the D-Bus session server: "Failed to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or directory" unnamed app(41290): KUniqueApplication: Pipe closed unexpectedly. TZAV> ps ax | grep dbus 1435 - Is 0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --sess 1434 2- I0:00.01 dbus-launch --autolaunch=fb0372ea595109904f5a068e0180 --binary-synta 41294 5 RL+ 0:00.00 grep dbus What am I doing wrong? Have you checked the presence of the /tmp/dbus-dyUjnhLBwE socket? sure, it's not there. I understand dbus is a required part of a modern browser, it is no longer an option, right? What?! I don't think that this is an acceptable opinion. :-) Both browsers you mentioned are part of KDE or Gnome. THOSE heavily rely on DBUS, that's right, and due to the transition of dependencies, _their_ web browsers also do. For example, I'm not running DBUS here, but I run modern web browsers. I just don't run _those_ two. :-) So did you properly build your KDE and Gnome components with DBUS enabled, and all of their configurable dependencies also with DBUS enabled? It _may_ be that the use of DBUS is not among the default building options for one of the nested dependencies, and that one might be _the one_ that now shoots your foot. :-) Your ps listing indicates that you are running DBUS, so that shouldn't be the problem. Missing DBUS support in one of the required components _could_ be. ok, this makes is clearer. My dbus comes from www/firefox36: TZAV> pwd /usr/ports/www/firefox36 TZAV> make showconfig ===> The following configuration options are available for firefox-3.6.28,1: DBUS=on "Enable D-BUS support" SMB=off "Enable smb:// URI support using gnomevfs" DEBUG=off "Build a debugging image" LOGGING=off "Enable additional log messages" OPTIMIZED_CFLAGS=off "Enable some additional optimizations" ===> Use 'make config' to modify these settings TZAV> and firefox36 works fine. I build from ports. Neither rekonq nor epiphany have dbus options. My reading of the rekonq Makefile is that it uses devel/dbus-qt4. Anyway, these are installed: TZAV> pkg info -xo dbus dbus-1.4.14_2: devel/dbus dbus-glib-0.94: devel/dbus-glib eggdbus-0.6_1: devel/eggdbus libdbusmenu-qt-0.9.0: devel/libdbusmenu-qt qt4-dbus-4.7.4: devel/dbus-qt4 qt4-qdbusviewer-4.7.4: devel/qt4-qdbusviewer TZAV> Many thanks Have you got this in your session startup? May or may not be necessary if you're using kdm/gdm. ## test for an existing bus daemon, just to be safe if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then ## if not found, launch a new one eval 'dbus-launch --sh-syntax --exit-with-session' echo "D-Bus per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS" fi ___ 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: dbus, epiphany, rekonq
On Mon, Mar 19, 2012 at 01:44:23PM +0100, Polytropon wrote: > On Mon, 19 Mar 2012 12:21:29 +, Anton Shterenlikht wrote: > > I can't lauch www/epiphany or www/rekonq > > on ia64 -current, due to some dbus issue: > > > > TZAV> ps ax|grep dbus > > 1435 - Is 0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 > > --print-address 7 --sess > > 1434 2- I0:00.01 dbus-launch > > --autolaunch=fb0372ea595109904f5a068e0180 --binary-synta > > 41284 5 RL+ 0:00.00 grep dbus > > > > TZAV> epiphany > > > > ** (epiphany:41285): WARNING **: Unable to connect to session bus: Failed > > to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or directory > > > > TZAV> rekonq > > unnamed app(41291): KUniqueApplication: Cannot find the D-Bus session > > server: "Failed to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or > > directory" > > > > unnamed app(41290): KUniqueApplication: Pipe closed unexpectedly. > > > > TZAV> ps ax | grep dbus > > 1435 - Is 0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 > > --print-address 7 --sess > > 1434 2- I0:00.01 dbus-launch > > --autolaunch=fb0372ea595109904f5a068e0180 --binary-synta > > 41294 5 RL+ 0:00.00 grep dbus > > > > What am I doing wrong? > > Have you checked the presence of the /tmp/dbus-dyUjnhLBwE socket? sure, it's not there. > > I understand dbus is a required part of > > a modern browser, it is no longer an option, right? > > What?! I don't think that this is an acceptable opinion. :-) > > Both browsers you mentioned are part of KDE or Gnome. > THOSE heavily rely on DBUS, that's right, and due to > the transition of dependencies, _their_ web browsers > also do. > > For example, I'm not running DBUS here, but I run modern > web browsers. I just don't run _those_ two. :-) > > So did you properly build your KDE and Gnome components > with DBUS enabled, and all of their configurable dependencies > also with DBUS enabled? It _may_ be that the use of DBUS > is not among the default building options for one of the > nested dependencies, and that one might be _the one_ that > now shoots your foot. :-) > > Your ps listing indicates that you are running DBUS, so > that shouldn't be the problem. Missing DBUS support in one > of the required components _could_ be. ok, this makes is clearer. My dbus comes from www/firefox36: TZAV> pwd /usr/ports/www/firefox36 TZAV> make showconfig ===> The following configuration options are available for firefox-3.6.28,1: DBUS=on "Enable D-BUS support" SMB=off "Enable smb:// URI support using gnomevfs" DEBUG=off "Build a debugging image" LOGGING=off "Enable additional log messages" OPTIMIZED_CFLAGS=off "Enable some additional optimizations" ===> Use 'make config' to modify these settings TZAV> and firefox36 works fine. I build from ports. Neither rekonq nor epiphany have dbus options. My reading of the rekonq Makefile is that it uses devel/dbus-qt4. Anyway, these are installed: TZAV> pkg info -xo dbus dbus-1.4.14_2: devel/dbus dbus-glib-0.94: devel/dbus-glib eggdbus-0.6_1: devel/eggdbus libdbusmenu-qt-0.9.0: devel/libdbusmenu-qt qt4-dbus-4.7.4: devel/dbus-qt4 qt4-qdbusviewer-4.7.4: devel/qt4-qdbusviewer TZAV> Many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: Can't install WindowMaker
On Sun, Mar 11, 2012 at 09:17:50AM +0100, Sabine Baer wrote: > > Sorry if I'm totally wrong here but I don't know where to ask. > > I'm using WindowMaker as my window manager for some years. I do not > remember why, but some days ago, I deinstalled ist. Now, I can't > install it. > > $uname -rp > |7.4-STABLE amd64 > > #portmaster -aD > |all up to date (had a long run of updating gcc46 and others this > |morning) You're not by any chance using gcc46 to compile Windowmaker? If so, don't. Use the base compiler. > > #portmaster /x11-wm/windomaker > |[...] > |handlers.c:542: warning: implicit declaration of function 'FD_ISSET' > |*** Error code 1 > |mv -f .deps/findfile.Tpo .deps/findfile.Plo > |1 error > |*** Error code 1 > |1 error > |*** Error code 1 > |1 error > |*** Error code 2 > |1 error > |*** Error code 1 > | > |Stop in /usr/ports/x11-wm/windowmaker. > | > |===>>> make failed for x11-wm/windowmaker > |===>>> Aborting update > | > |Terminated > | > |===>>> You can restart from the point of failure with this command > |line: > | portmaster x11-wm/windowmaker > > I haven't any clue what might go wrong. Searching google didn't bring > any help. > I can use fluxbox or twm, but I want my WindowMaker back :-( > > Sabine Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpC2hNXn4FWt.pgp Description: PGP signature
Re: dbus, epiphany, rekonq
On Mon, 19 Mar 2012 12:21:29 +, Anton Shterenlikht wrote: > I can't lauch www/epiphany or www/rekonq > on ia64 -current, due to some dbus issue: > > TZAV> ps ax|grep dbus > 1435 - Is 0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 > --print-address 7 --sess > 1434 2- I0:00.01 dbus-launch > --autolaunch=fb0372ea595109904f5a068e0180 --binary-synta > 41284 5 RL+ 0:00.00 grep dbus > > TZAV> epiphany > > ** (epiphany:41285): WARNING **: Unable to connect to session bus: Failed to > connect to socket /tmp/dbus-dyUjnhLBwE: No such file or directory > > TZAV> rekonq > unnamed app(41291): KUniqueApplication: Cannot find the D-Bus session server: > "Failed to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or > directory" > > unnamed app(41290): KUniqueApplication: Pipe closed unexpectedly. > > TZAV> ps ax | grep dbus > 1435 - Is 0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 > --print-address 7 --sess > 1434 2- I0:00.01 dbus-launch > --autolaunch=fb0372ea595109904f5a068e0180 --binary-synta > 41294 5 RL+ 0:00.00 grep dbus > > What am I doing wrong? Have you checked the presence of the /tmp/dbus-dyUjnhLBwE socket? > I understand dbus is a required part of > a modern browser, it is no longer an option, right? What?! I don't think that this is an acceptable opinion. :-) Both browsers you mentioned are part of KDE or Gnome. THOSE heavily rely on DBUS, that's right, and due to the transition of dependencies, _their_ web browsers also do. For example, I'm not running DBUS here, but I run modern web browsers. I just don't run _those_ two. :-) So did you properly build your KDE and Gnome components with DBUS enabled, and all of their configurable dependencies also with DBUS enabled? It _may_ be that the use of DBUS is not among the default building options for one of the nested dependencies, and that one might be _the one_ that now shoots your foot. :-) Your ps listing indicates that you are running DBUS, so that shouldn't be the problem. Missing DBUS support in one of the required components _could_ be. -- 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"
dbus, epiphany, rekonq
I can't lauch www/epiphany or www/rekonq on ia64 -current, due to some dbus issue: TZAV> ps ax|grep dbus 1435 - Is 0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --sess 1434 2- I0:00.01 dbus-launch --autolaunch=fb0372ea595109904f5a068e0180 --binary-synta 41284 5 RL+ 0:00.00 grep dbus TZAV> epiphany ** (epiphany:41285): WARNING **: Unable to connect to session bus: Failed to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or directory TZAV> rekonq unnamed app(41291): KUniqueApplication: Cannot find the D-Bus session server: "Failed to connect to socket /tmp/dbus-dyUjnhLBwE: No such file or directory" unnamed app(41290): KUniqueApplication: Pipe closed unexpectedly. TZAV> ps ax | grep dbus 1435 - Is 0:00.02 /usr/local/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --sess 1434 2- I0:00.01 dbus-launch --autolaunch=fb0372ea595109904f5a068e0180 --binary-synta 41294 5 RL+ 0:00.00 grep dbus What am I doing wrong? I understand dbus is a required part of a modern browser, it is no longer an option, right? Many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: Dualboot with Windows 7
On 03/19/12 17:49, Polytropon wrote: On Mon, 19 Mar 2012 08:29:22 +0100, David Demelier wrote: On 19/03/2012 07:28, Polytropon wrote: On Sun, 18 Mar 2012 23:05:58 +0100, David Demelier wrote: Hello, I try to create a dualboot with Windows 7, I set up partitions like that : ada0s1 -> NTFS (windows recovery) ada0s2 -> NTFS (windows main partition) ada0s3 -> BSD ada0s3a -> freebsd-swap (3G) ada0s3b -> freebsd-ufs / (remaining space from drive) Erm... according to traditional partitioning, isn't the 'a' partition reserved for booting, 'b' for swap? I see you have installed everything into one / partition which technically is no problem and should work, but it's not on the boot partition. You're right, but I made a mistake while writing, my a partition is / and b is swap. Okay. And then I let the installer complete the step, because FreeBSD didn't let you (since 9.0) choose between the boot manager nothing was installed and the boot directly goes to Windows 7. You need to install all the required stages for booting. If I understand the process correctly, the slice 's3' needs code to "branch" to the boot partition (which is supposed to be the 'a' partition), and the boot selector needs to be accessed from the "beginning of the disk" - you said you're using EasyBCD for this which is okay. I followed the part 13.3.2 from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html I think this should be enough, isn't it? it says bsdlabel -B will replace the boot1 and boot2 stage so all of them are installed. Looks correct. Now the question is how to branch the a partition as the "boot partition" ? No need. As soon as the "branching" from ada0-"start" -> ada0s3 has been processed, the 'a' partition ada0s3a will be accessed as it is the boot partition. It will then continue stage 1 and 2 and finally access the loader, which will load the kernel. In 13.3.2 it is explained as follows: They [Stage One, /boot/boot1, and Stage Two, /boot/boot2] are located outside file systems, in the first track of the boot slice, starting with the first sector. This is where boot0, or any other boot manager, expects to find a program to run which will continue the boot process. The number of sectors used is easily determined from the size of /boot/boot. In your case, the "boot slice" (for FreeBSD) is ada0s3 where the boot manager EasyBCD will "branch" to. Getting just a cursor (as you described) makes it hard to identify where the process hangs. If EasyBCD is the last thing you see, I assume the FreeBSD boot process isn't even initiated. Every part of it (MBR boot manager, boot0, boot1, boot2 and loader) would issue some kind of text when accessed. I couldn't say exactly how to do this now (been a long time), but you should be able to boot using the Windows loader (this may have changed in recent editions. Don't think so though). This will give you a choice between Windows or FreeBSD and defaults, timers, etc during boot. Used to be able to do it under system properties I believe; run a google search should provide some examples. ___ 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: Dualboot with Windows 7
On Mon, 19 Mar 2012 08:29:22 +0100, David Demelier wrote: > On 19/03/2012 07:28, Polytropon wrote: > > On Sun, 18 Mar 2012 23:05:58 +0100, David Demelier wrote: > >> Hello, > >> > >> I try to create a dualboot with Windows 7, I set up partitions like that : > >> > >> ada0s1 -> NTFS (windows recovery) > >> ada0s2 -> NTFS (windows main partition) > >> ada0s3 -> BSD > >>ada0s3a -> freebsd-swap (3G) > >>ada0s3b -> freebsd-ufs / (remaining space from drive) > > > > Erm... according to traditional partitioning, isn't > > the 'a' partition reserved for booting, 'b' for swap? > > I see you have installed everything into one / partition > > which technically is no problem and should work, but > > it's not on the boot partition. > > > > > > You're right, but I made a mistake while writing, my a partition is / > and b is swap. Okay. > >> And then I let the installer complete the step, because FreeBSD didn't > >> let you (since 9.0) choose between the boot manager nothing was > >> installed and the boot directly goes to Windows 7. > > > > You need to install all the required stages for booting. > > If I understand the process correctly, the slice 's3' needs > > code to "branch" to the boot partition (which is supposed > > to be the 'a' partition), and the boot selector needs to > > be accessed from the "beginning of the disk" - you said > > you're using EasyBCD for this which is okay. > > > > > > I followed the part 13.3.2 from > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html > > I think this should be enough, isn't it? it says bsdlabel -B will > replace the boot1 and boot2 stage so all of them are installed. Looks correct. > Now the question is how to branch the a partition as the "boot partition" ? No need. As soon as the "branching" from ada0-"start" -> ada0s3 has been processed, the 'a' partition ada0s3a will be accessed as it is the boot partition. It will then continue stage 1 and 2 and finally access the loader, which will load the kernel. In 13.3.2 it is explained as follows: They [Stage One, /boot/boot1, and Stage Two, /boot/boot2] are located outside file systems, in the first track of the boot slice, starting with the first sector. This is where boot0, or any other boot manager, expects to find a program to run which will continue the boot process. The number of sectors used is easily determined from the size of /boot/boot. In your case, the "boot slice" (for FreeBSD) is ada0s3 where the boot manager EasyBCD will "branch" to. Getting just a cursor (as you described) makes it hard to identify where the process hangs. If EasyBCD is the last thing you see, I assume the FreeBSD boot process isn't even initiated. Every part of it (MBR boot manager, boot0, boot1, boot2 and loader) would issue some kind of text when accessed. -- 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: Can't install WindowMaker
On Mon, 19 Mar 2012 07:51:04 +0100, Sabine Baer wrote: > On Sat, Mar 17, 2012 at 07:07:33PM +0100, lokada...@gmx.de wrote: > > [...] > > I see that you have a german mailadress, so i will write in germany. > > Dann kann ich ja auch mal auf Deutsch antworten, ich hoffe, man sieht > uns das nach. > > > Guck mal nach, ob du unter /etc/ eine Datei mit dem Namen > > portsnap.conf hast. > > Ja, habe ich, habe ich aber bisher noch nie benutzt, ich nehme immer > cvsup -g ports-supfile (mit host=cvsup.freebsd.org). Das dauert zwar > ewig, aber ist doch gleichermassen aktuell, oder? Nein, es ist oftmals "noch aktueller" (more current). :-) Explaination: The portsnap provides a snapshot of the ports tree. It's _not_ updated as fast as what you can get via differentials using csup (which can change a file within half an hour). When many file changes are scheduled, portsnap is faster, and it's especially useful to download a complete ports tree. For being "bleeding-edge current", csup is the better method, especially if you update your ports tree regularly. > > Wenn du eine Flatrate hast, kannst du vielleicht auch mal dein > > ganzes System auf 9.0 aktualisieren (freebsd-update ist für die > > Standardinstallation ohne Kompilierung ganz gut). > > Ich habe bisher davon abgesehen, 7.n zu verlassen, weil ich aus dem > Augenwinkel gesehen habe, dass bei Versionen >7.n die Einstellungen > fuer die seriellen Schnittstellen veraendert werden muessen, und da > hatte ich keine Lust zu. Dass die funktionieren, ist fuer mich aber > absolut unabdingbar, ich habe naemlich ein echtes Terminal daran > haengen You should note that 7.4 is a legacy release which is "rather old", but I can understand the urge _not_ to fiddle with things that "just work" (and especially if it's something _that_ special like a _real_ serial terminal). > > Einige Probleme treten auf, wenn die Libarys auf dem System zu alt > > sind, aber in den Ports aktuelle benötigt werden. > > Vielleicht ist das bei windowmaker tatsaechlich so. Ich habe noch mal > alles 'runtergeschmissen, ein make clean in ?usr/ports gemacht, alle > distfiles 'rausgeschmissen und /usr/local/* komplett geloescht. Und > auf einmal konnte ich Ports installieren, die zuvor alle Fehler > erbracht haben - ImageMagick, dia, gimp, /lang/lua (fuer nmap). Ist manchmal echt das beste. Hier zeigt sich mal wieder, daß die Trennung von OS und Programmen sehr sinnvoll sein kann! > Ich habe es ohne 'sophisticated tools', nur mit cd > /usr/ports/*/$ANWENDUNG, make config und make install clean gemacht, > es hat lange gedauert, aber war erfolgreich. See "man 7 ports", the target "make config-recursive" to get rid of build interruptions due to forced interactivity. > Nur der windowmaker weigert sich nach wie vor zu kompilieren. Da ich > aller 'rausgeschmissen habe, weiss ich auch nicht mehr, ob ich zuvor > eine aeltere Version installiert hatte. Im Zweifelsfall installier Dir mal "portdowngrade" und zieh eine ältere Version von WindowMaker, vielleicht compiliert die ja? Ich halte es in solchen Fällen oft für sinnvoll, nach der Komplettreinigung und dem mtree-Lauf mit _dem_ Port zu beginnen, den man eigentlich haben will. Alle Dependencies, die der braucht, sollten automatisch gezogen werden, so hat man eine minimale (kontrollierte) Umgebung, in der möglichst wenig Stolpersteine liegen sollten. > Ich bedanke mich jedenfalls bei Dir und 'Polýtropon' fuer die Hilfe, > sie hat mir wirklich geholfen, wenn ich auch immer noch keinen > windowmaker wieder habe. On my voluminous voyage through window manager and desktop environemnts, I've always come back to WindowMaker. As I said, installing it on v8 hasn't been a problem, but when I did use it on v7 (with the sources being current at _that_ time) it also worked. Maybe the current sources are really "too new", and a portdowngrade could work? At least the port is not maked _not_ to build on v7, so it basically _should_ work. So, nun haben wir hier schönes Sprech-Mischmasch, mashed language so to say... :-) -- 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: Dualboot with Windows 7
On 19/03/2012 07:28, Polytropon wrote: On Sun, 18 Mar 2012 23:05:58 +0100, David Demelier wrote: Hello, I try to create a dualboot with Windows 7, I set up partitions like that : ada0s1 -> NTFS (windows recovery) ada0s2 -> NTFS (windows main partition) ada0s3 -> BSD ada0s3a -> freebsd-swap (3G) ada0s3b -> freebsd-ufs / (remaining space from drive) Erm... according to traditional partitioning, isn't the 'a' partition reserved for booting, 'b' for swap? I see you have installed everything into one / partition which technically is no problem and should work, but it's not on the boot partition. You're right, but I made a mistake while writing, my a partition is / and b is swap. And then I let the installer complete the step, because FreeBSD didn't let you (since 9.0) choose between the boot manager nothing was installed and the boot directly goes to Windows 7. You need to install all the required stages for booting. If I understand the process correctly, the slice 's3' needs code to "branch" to the boot partition (which is supposed to be the 'a' partition), and the boot selector needs to be accessed from the "beginning of the disk" - you said you're using EasyBCD for this which is okay. I followed the part 13.3.2 from http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html I think this should be enough, isn't it? it says bsdlabel -B will replace the boot1 and boot2 stage so all of them are installed. Now the question is how to branch the a partition as the "boot partition" ? I installed EasyBCD to add a new entry to FreeBSD on the third partition, but when I choose the FreeBSD entry nothing happens, only the _ character blinking. I assume missing boot characteristics as described above. Please review your installation process and maybe re-do it. In worst case, drop to command line for using the "traditional toolset" to apply the proper slicing and partitioning. According to "man fdisk" and "man bsdlabel", you should be able to write the required boot characteristics to allow the correct boot process. Thus I tried bsdlabel -B ada0s3 from the FreeBSD iso shell but it didn't solve. What can I do to boot FreeBSD now? As this part is done, I suppose incorrect partitioning. 2.6.5 Creating Partitions Using Disklabel http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.html Refer to table 2-2: "Partition Layout for First Disk". Boot manager and MBR handling are also covered in this chapter. -- David Demelier ___ 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"
