Re: pkgsrc-HEAD DragonFly 2.3.1/i386 2009-06-01 02:14
-Build start: 2009-05-20 10:24 +Build start: 2009-06-01 02:14 -Total number of packages: 8797 - Successfully built: 7973 - Failed to build: 371 - Depending on failed package: 128 +Total number of packages: 8820 + Successfully built: 7999 + Failed to build: 369 + Depending on failed package: 127 +comms/gammu4 pkgsrc-us...@netbsd.org +devel/p5-Devel-Checklib pkgsrc-us...@netbsd.org +devel/py-subversion g...@netbsd.org +py23-subversion-1.6.2g...@netbsd.org -emulators/bochs pkgsrc-us...@netbsd.org +graphics/p5-clutter oba...@netbsd.org -graphics/py-matplotlib-tkpkgsrc-us...@netbsd.org +graphics/ruby-clutter-gtk 1 oba...@netbsd.org -ham/gnuradio-core-docs 1 w...@netbsd.org +lang/scheme48pkgsrc-us...@netbsd.org -mail/postfix-current 1 mar...@netbsd.org -multimedia/totem 2 pkgsrc-us...@netbsd.org +multimedia/vlc08 pkgsrc-us...@netbsd.org -net/unfs3pkgsrc-us...@netbsd.org -print/p5-LaTeX-Driver 2 pkgsrc-us...@netbsd.org -textproc/p5-XML-Xerces m...@netbsd.org +time/sunbird pkgsrc-us...@netbsd.org -www/clearsilver-base 1 pkgsrc-us...@netbsd.org +www/typolight27-translations t...@netbsd.org -x11/ruby-gnome2-panelapplet1 dieter.net...@pandora.be
Re: amd64 - invitation to test
Aggelos Economopoulos wrote: Jordan Gordeev wrote: It's time public testing of the amd64 port begins. The code is available in my git repo at git://leaf.dragonflybsd.org/~smtms/dragonfly.git in branches "amd64" and "amd64+hacks". The "amd64+hacks" branch contains what "amd64" contains + some band aid to keep the system working even when a proper fix to a known problem is not yet developed. Great! You can now begin to find and report (and fix) bugs. Does it work in an emulator and if so, which ones are known to work? Do you plan to offer a CD image we can install from (not necessarily using the installer, the old cpdup method is fine at this stage)? It is known to work in qemu. See Matt's instructions for using /usr/src/test/amd64. It should work in any emulator that supports DragonFly. It sure works on real hardware. I do not plan to offer a CD image. I'm unable to imagine the use case. The amd64 port is a work in progress, so one should be able to build and re-build from source, and the lack of CD image shouldn't be a problem. Can we build amd64 world and kernel on an amd64 installation? You can. However, I'm yet to test if world and kernel built on amd64 actually work. :-)
Re: Instant crash with Linux OpenOffice
Matthew Dillon wrote: :Hi, : :I have recently upgraded the root fs to Hammer on one of my machines. Since :then, I have been unable to run any version of OpenOffice. :Previously, misc/openoffice2-bin and misc/openoffice3-bin ran fine. : :The OS is DragonFly 2.2.2-RELEASE. : :The splash screen begins to appear and then OpenOffice crashes with some weird :errors: : :$ soffice :javaldx: Could not find a Java Runtime Environment! :sh: g/,: No such file or directory : :$ soffice :javaldx: Could not find a Java Runtime Environment! :sh: -c: line 0: unexpected EOF while looking for matching `'' :sh: -c: line 1: syntax error: unexpected end of file : :I'm not sure how to debug this. : :-- :Francois Tigeot I've had similar issues with OpenOffice but I have never been able to figure out what's wrong. I don't think it is HAMMER per-say, but instead something related to our linux emulation that is breaking. It seems to happen more consistently with HAMMER but issues also pop up with UFS. OO 2.X also consistently useless on Mac OSX 10.3.9 with all-UFS fs. Shows OO splash screen, dies and goes where all responsible bloatware should take itself. OOS 1.X did work on Mac UFS & 10.3.9. OO 2.X works OK on OSX 10.4 with hfs+ fs. It could be related to the path prefixing the linux emulation does to give priority to the emulation directory structure on lookups. -Matt Matthew Dillon Probably a lot more to it than that I'd point at javishness, but Mac's have /* oxymoron warning */ fairly usable java Bill
AHCI driver port update - working with hot-plug
The AHCI driver is now working for DISK and ATAPI attachments, and hot-plug also now works. All major features except port multiplier support are now operational. The hot-plug support is very recent and probably needs some tweaking, but it works with my basic tests. Port multiplier support is upcoming, I expect to get it written fairly quickly once I get the PM hardware I've ordered. TESTING (not for the light hearted) Both the AHCI and the NATA devices may be specified in kernel builds, and AHCI can be loaded as a module too which is how I would suggest people use it for the moment. That is, you can leave NATA in your kernel build and load AHCI as a module in /boot/loader.conf: ahci_load="YES" Note that you must do a full kernel build and install to make sure everything is in sync. Your ATA disk devices, for example, 'ad4', will become SCSI disk devices, for example 'da0'. You thus need to modify your /etc/fstab and if you are using a boot + root HAMMER configuration you also need to adjust the root filesystem mount line in your /boot/loader.conf. It's fairly easy to get it wrong and for the system to not be able to find the root mount, in which case carefully specifying it on the kernel's mountroot> line should get you into single-user. I am particularly interested in systems which have a separate, traditional non-AHCI ATA device as well as one or more AHCI devices, I'd like to know that AHCI picks up the AHCI devices and NATA picks up the non-AHCI devices properly. -Matt
