Re: chlamydia inconsistency? part II.
On which real platform is it? (Win, Linux, some BSD) Which version of VirtualBox? Did you choose type of OS as FreeBSD or Other? 2010/9/25 Przemysław Pawełczyk pp...@o2.pl: Hi, I was too optimistic. I tried to get MC running using compilation but the procedure also ended up with segmentation fault. See the two pictures from the MC series: http://pp.blast.pl/www.png/dfbsd/df_02.png http://pp.blast.pl/www.png/dfbsd/df_03.png I gave up as for now. ;-) Regards -- Przemysław Pawełczyk (P2O2) [pron. Pshemislav Paveltchick] http://pp.blast.pl, pp...@o2.pl -- “If you’re good at something, never do it for free.” —The Joker
Re: chlamydia inconsistency? part II.
On Sat, 25 Sep 2010 12:28:09 +0200 Tomas Bodzar tomas.bod...@gmail.com wrote: Hi to all, Francois Tigeot and others, I will answer with this e-mail to other posts too. On which real platform is it? (Win, Linux, some BSD) Which version of VirtualBox? Did you choose type of OS as FreeBSD or Other? Not so happy picture emerged. Ad rem. My main workhorse is Scientific Linux (SL) 5.5- one of the Red Hat Enterprise Linux (RHEL) clone (it has all RHEL marks removed but it is pure RHEL just like PC-BSD which runs on pure FreeBSD). VirtualBox 3.2.8 r64453 (rather latest). I used DragonFly-x86_64-LATEST-ISO.iso from September 23. For DFBSD in VBox I chose: Operating System - Other Version - Other/Unknown During installation on virtual disk I selected ***other*** then US keyboard and console fonts (do not ask me which and what else, I didn't save the data). 1. It appeared that a) first, I had declared too small root partition (DFBSD's algorithm did so). b) second, another bug emerged - I pointed to two seg-faults: - on pkg_radd mc - and on pkgsrc during compilation of mc package ad. a) It was a bug, will be removed what Sasha Wildner declared here: http://leaf.dragonflybsd.org/mailarchive/users/2010-09/msg00130.html ad. b) Creating bigger root and home partition were to remove the sig-faults. Alas, it didn't happen. http://pp.blast.pl/www.png/dfbsd/df_06.png - mc compilation http://pp.blast.pl/www.png/dfbsd/df_07.png - kbdmap http://pp.blast.pl/www.png/dfbsd/df_08.png - kbdmap http://pp.blast.pl/www.png/dfbsd/df_09.png - kbdmap http://pp.blast.pl/www.png/dfbsd/df_10.png - kbdmap It seems to me that Francois Tigeot http://leaf.dragonflybsd.org/mailarchive/users/2010-09/msg00125.html was 100% correct. Francis, you wrote: Did you by chance customize any locale value ? I misinterpreted the word any relating it to keyboard language but probably it concerns **ANY** language settings - be it keyboard or console fonts, etc. I'm not sure which settings give the sig-faults as I changed all the three language values but your claims is valid. I hope the above screenshots will help to nail the culprit. Francis Tigeot wrote about devel/gettext-lib, here it was kbdmap. So, 2. a) I have made 10GB virtual disk in VBox, increased root size from 256MB to 512MB, and descreased /usr partition from 8192MB to 6000MB, leaving the saved space to /home partition. http://pp.blast.pl/www.png/dfbsd/df_11.png - sysinstall (old values) http://pp.blast.pl/www.png/dfbsd/df_08.png - df -h (new values) b) I didn't touch the language setting points - there are three of them. All problems vanished. I have written at the beginning that Not so happy picture emerged. becasue using Polish fonts with diacritic signs is essential to me. Perhaps Francis has more to say on the issue. 3. BTW. Why mc says Unknown terminal: cons25? I'm not able to run mc at present. See: http://pp.blast.pl/www.png/dfbsd/df_10.png Thanks all for your help and patience. Regards Przemysław -- Przemysław Pawełczyk (P2O2) [pron. Pshemislav Paveltchick] http://pp.blast.pl, pp...@o2.pl pgpEXJHTfHcQi.pgp Description: PGP signature
Re: chlamydia inconsistency? part II.
BTW.1. pkg_radd prints segmentation fault, see the picture: http://pp.blast.pl/www.png/dfbsd/df_01.png I had to compile MC from sources. I'm not sure, but master branch in git repository is probably pkgsrc -current? DragonFly BSD has pre-bootstrapped pkgsrc 2010Q2 out-of-box currently. I was too optimistic. I tried to get MC running using compilation but the procedure also ended up with segmentation fault. IMO mixing binary packages with source builds isn't good idea, especially with two different version of pkgsrc. Dependency hell is easy to archive. My suggestion is to remove all packages: # pkg_delete -ff '*-*' clean directories: # rm -rf /usr/pkg/* rm -rf /var/db/pkg/* And bootstrap new pkgsrc: # cd /usr/pkgsrc/bootstrap ./bootstrap Then you can start building packages: # cd /usr/pkgsrc/sysutils/mc bmake install Good idea is also using stable branch of pkgsrc - which currently is 2010Q2. If you removed all packages and forgot to checkout pkgsrc repository, you can download it from ftp: # ftp -a ftp://ftp.netbsd.org/pub/pkgsrc/pkgsrc-2010Q2/pkgsrc.tar.bz2 There are other solutions for making dependencies consistent like pkg_rolling-replace, but starting from scratch is the easiest. btw. Sorry for poor english writing. -- Paul Onyschuk bl...@bojary.koba.pl
Re: chlamydia inconsistency? part II.
On Sat, Sep 25, 2010 at 02:01:20PM +0200, Przemysław Pawełczyk wrote: On Sat, 25 Sep 2010 12:28:09 +0200 My main workhorse is Scientific Linux (SL) 5.5- one of the Red Hat Enterprise Linux (RHEL) clone (it has all RHEL marks removed but it is pure RHEL just like PC-BSD which runs on pure FreeBSD). VirtualBox 3.2.8 r64453 (rather latest). I used DragonFly-x86_64-LATEST-ISO.iso from September 23. [...] b) Creating bigger root and home partition were to remove the sig-faults. Alas, it didn't happen. http://pp.blast.pl/www.png/dfbsd/df_06.png - mc compilation http://pp.blast.pl/www.png/dfbsd/df_07.png - kbdmap http://pp.blast.pl/www.png/dfbsd/df_08.png - kbdmap http://pp.blast.pl/www.png/dfbsd/df_09.png - kbdmap http://pp.blast.pl/www.png/dfbsd/df_10.png - kbdmap It seems to me that Francois Tigeot http://leaf.dragonflybsd.org/mailarchive/users/2010-09/msg00125.html was 100% correct. Francis, you wrote: Did you by chance customize any locale value ? I misinterpreted the word any relating it to keyboard language but probably it concerns **ANY** language settings - be it keyboard or console fonts, etc. I'm not sure which settings give the sig-faults as I changed all the three language values but your claims is valid. I hope the above screenshots will help to nail the culprit. Francis Tigeot wrote about devel/gettext-lib, here it was kbdmap. gettext-lib provides a library which is used by all sort of third-party programs for internationalization. sysutils/mc is one of them. I was not aware about the kbdmap issue but I have just run a test and the crash also happens on my system. Since kbdmap does not use gettext-lib from pkgsrc, this must be an other bug. -- Francois Tigeot
Re: chlamydia inconsistency? part II.
On Sat, 25 Sep 2010 16:15:40 +0200 Przemysław Pawełczyk pp...@o2.pl wrote: Got two messages about digest. First digest I removed because it was blocking mc compilation. Old digest (which you get after DragonFly BSD installation) can block compilation. That's why I suggested removing all packages. Command I mentioned before removes everything, even pkg_install etc. The second digets issue illustrate screenshot: http://pp.blast.pl/www.png/dfbsd/df_12.png Bootstraping creates new version of digest and others tools used by pkgsrc. If successful, reloading $PATH is probably needed - you can also simply reboot machine ;) You should also check if /usr/pkg/bin is in your PATH: # echo $PATH Then compilation should work. Moreover I used this solution few weeks ago on DragonFly BSD -current, because I wanted pkgsrc -current, not stable release 2010Q2. -- Paul Onyschuk bl...@bojary.koba.pl
Re: chlamydia inconsistency? part II.
A couple of things note when messing with pkgsrc: * Remember that /usr/pkg also tends to contain configuration files that you may have edited, in /usr/pkg/etc, so don't accidently blow away stuff you need. * When doing major messing around with pkgsrc it might be prudent to create a chroot'd copy of the system and do the messing around inside the chroot instead of on the main system's directory tree. It's easiest to just cpdup a copy of various things into the chroot, and remember to do the second mount_devfs. A more complex scenario would involve a mix of cpdup and mount_null null mounts to construct the chroot environment. Having a lot of disk space helps matters too, particularly when playing with pkgsrc. -Matt
Re: chlamydia inconsistency? part II.
On Sat, 25 Sep 2010 10:53:33 -0700 (PDT) Matthew Dillon dil...@apollo.backplane.com wrote: A couple of things note when messing with pkgsrc: * Remember that /usr/pkg also tends to contain configuration files that you may have edited, in /usr/pkg/etc, so don't accidently blow away stuff you need. * When doing major messing around with pkgsrc it might be prudent to create a chroot'd copy of the system and do the messing around inside the chroot instead of on the main system's directory tree. It's easiest to just cpdup a copy of various things into the chroot, and remember to do the second mount_devfs. A more complex scenario would involve a mix of cpdup and mount_null null mounts to construct the chroot environment. This is my standard recipe for constructing a pkgsrc build chroot in $DIR. mkdir $DIR cd /usr/srr make DESTDIR=$DIR installworld cd etc make DESTDIR=$DIR distribution mkdir $DIR/usr/pkgsrc mount_null /usr/pkgsrc $DIR/usr/pkgsrc mount_null /dev $DIR/dev I build with WRKOBJDIR=/usr/pkgobj so the build doesn't pollute /usr/pkgsrc. -- Steve O'Hara-Smith | Directable Mirror Arrays C:WIN | A better way to focus the sun The computer obeys and wins.|licences available see You lose and Bill collects. |http://www.sohara.org/
Re: chlamydia inconsistency? part II.
On Sat, 25 Sep 2010 10:53:33 -0700 (PDT) Matthew Dillon dil...@apollo.backplane.com wrote: A couple of things note when messing with pkgsrc: * Remember that /usr/pkg also tends to contain configuration files that you may have edited, in /usr/pkg/etc, so don't accidently blow away stuff you need. * When doing major messing around with pkgsrc it might be prudent to create a chroot'd copy of the system and do the messing around inside the chroot instead of on the main system's directory tree. It's easiest to just cpdup a copy of various things into the chroot, and remember to do the second mount_devfs. A more complex scenario would involve a mix of cpdup and mount_null null mounts to construct the chroot environment. Having a lot of disk space helps matters too, particularly when playing with pkgsrc. -Matt Overall, building packages in chrooted environment is way to go. On NetBSD I used pkg_comp a lot, there is even nice tutorial [1]. Something like that for DragonFly BSD would be nice. Using pkgsrc in unprivileged mode is also pretty safe - everything lands in /home/username/pkg and so on. In this case some caution is required when setting PATH. [1] https://wiki.netbsd.org/tutorials/pkgsrc/pkg_comp_pkg_chk/ -- Paul Onyschuk bl...@bojary.koba.pl
chlamydia inconsistency? part II.
Hi, I was too optimistic. I tried to get MC running using compilation but the procedure also ended up with segmentation fault. See the two pictures from the MC series: http://pp.blast.pl/www.png/dfbsd/df_02.png http://pp.blast.pl/www.png/dfbsd/df_03.png I gave up as for now. ;-) Regards -- Przemysław Pawełczyk (P2O2) [pron. Pshemislav Paveltchick] http://pp.blast.pl, pp...@o2.pl pgpdaygEfDkLl.pgp Description: PGP signature
