Re: Building/Installing DragonFly from within FreeBSD
Can anybody confirm that this still works? When I try to upgrade a FreeBSD 4.9 system to DragonFly 1.2 following the procedure outlined in this document, make buildworld fails in /usr/src/usr.bin/mklocale. What error do you get? === usr.bin/mklocale (bootstrap-tools) /usr/obj/usr/src/btools_i386/usr/src/usr.bin/mklocale created for /usr/src/usr.bin/mklocale yacc -d /usr/src/usr.bin/mklocale/yacc.y cp y.tab.c yacc.c lex -t /usr/src/usr.bin/mklocale/lex.l lex.c cp /usr/src/usr.bin/mklocale/../../include/runetype.h runetype.h grep '#define._CTYPE_' /usr/src/usr.bin/mklocale/../../include/ctype.h ctype.h rm -f .depend mkdep -f .depend -a-I. -I/usr/src/usr.bin/mklocale yacc.c lex.c In file included from /usr/src/usr.bin/mklocale/yacc.y:54: runetype.h:46: sys/stdint.h: No such file or directory In file included from /usr/src/usr.bin/mklocale/ldef.h:40, from /usr/src/usr.bin/mklocale/lex.l:46: runetype.h:46: sys/stdint.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/usr.bin/mklocale. *** Error code 1 Stop in /usr/src. *** Error code 1
Re: Building/Installing DragonFly from within FreeBSD
Matthew Dillon wrote: I really doubt that you can build the dragonfly kernel from inside FreeBSD any more, short of booting a DragonFly CD in a virtual machine and building it there. Hmm, but he's trying FreeBSD 4 - DragonFly 1.2, something which seems to have been working at some point. Strange.. Sascha -- http://yoyodyne.ath.cx
Re: Building/Installing DragonFly from within FreeBSD
:Hmm, but he's trying FreeBSD 4 - DragonFly 1.2, something which seems :to have been working at some point. : :Strange.. : :Sascha : :-- :http://yoyodyne.ath.cx It's possible that the CVS surgery we've done over the years has messed up 1.2 with regards to building from FreeBSD. Even more likely, changes in FreeBSD have probably made portions of the old 1.2 build incompatible. Some of the FreeBSD folks keep refering to DragonFly as something relative to FreeBSD-4 and that probably causes a lot of confusion. DragonFly was forked from FreeBSD-4 a long time ago, but holds very little in common with it these days. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: Building/Installing DragonFly from within FreeBSD
:Can anybody confirm that this still works? When I try to upgrade a :FreeBSD 4.9 system to DragonFly 1.2 following the procedure outlined in :this document, make buildworld fails in /usr/src/usr.bin/mklocale. :I would like to go this route to migrate some production servers that :are currently running FBSD 4.11 to DragonFly, if possible. : :Thanks! : :Andre I really doubt that you can build the dragonfly kernel from inside FreeBSD any more, short of booting a DragonFly CD in a virtual machine and building it there. -Matt Matthew Dillon [EMAIL PROTECTED]
Re: Building/Installing DragonFly from within FreeBSD
Sascha Wildner wrote: I would like to go this route to migrate some production servers that are currently running FBSD 4.11 to DragonFly, if possible. Yeah, some kind of more or less convenient upgrade path for FreeBSD 4 users would be nice to have. Where is the big difference between doing a buildworld, buildkernel, installkernel, installworld or doing a binary update? Maybe we should encourage people to do this instead? I even thought the installer had an option. If not, just copying over /kernel /modules /usr /bin/sbin and updating /etc should do it as well, right? cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Re: Building/Installing DragonFly from within FreeBSD
On Sat, February 16, 2008 2:27 pm, Sascha Wildner wrote: Andre LeClaire wrote: I would like to go this route to migrate some production servers that are currently running FBSD 4.11 to DragonFly, if possible. Yeah, some kind of more or less convenient upgrade path for FreeBSD 4 users would be nice to have. This seems somewhat bizarre, but: would we be able to apply a Depenguinator style strategy? http://www.daemonology.net/blog/2008-01-29-depenguinator-2.0.html
Building/Installing DragonFly from within FreeBSD
Hi there, though it seems to be supported to build (some releases) of DragonFly on (some releases) of FreeBSD and cross-install them, I can't get it to work. I tried building 1.0, 1.2, 1.4, 1.6 and 1.10 on 4.11, 5.5, 6.0 and 8.0. They all quickly die in buildworld during bootstrap-tools phase. Even plastering over some obvious differences, this seems to be not possible with the given releases. Some background: I'm trying to debug SCSI/CAM/cd(4) on FreeBSD, where my external DVD drive will not read retail DVDs (yes, burned DVDs are fine, please don't ask). And since this worked with DFly 1.8 last time I tried, I'm now in the progress of doing a binary search between, well FreeBSD 4.x and DFly 1.8 to nail down the commit that made this possible in DFly. (right now, I'm blaming GEOM for this no longer working in FreeBSD). I'm trying to install this on a headless machine, using serial consoles only. So popping in an install CD and using monitor/keyboard to install is not that easy. Anyway, so I downloaded the 1.0A ISO and extracted it to ad2s1a, placed an /etc/rc.conf and /etc/fstab there, removed /boot/loader.conf and wanted to boot this. It loads /boot/loader, but when loading (decoding?) the kernel, it hangs solid. I tried without ACPI and safe mode, doesn't help. What am I missing? Is boot, loader, or kernel from the 1.0A ISO not able to boot a kernel from the hard disk. Or is the serial console fucking things up? This is how far I get (using grub) root (hd1,1,a) Filesystem type is ffs, partition type 0xa5 kernel /boot/loader -Dh [FreeBSD-a.out, loadaddr=0x20, text=0x1000, data=0x2d000, bss=0x0, entry =0x20] Console: serial port Console: null port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS 640kB/326644kB available memory DragonFly/i386 bootstrap loader, Revision 1.1 (root@, Wed Jul 1 17:17:37 GMT 2004) Loading /boot/defaults/loader.conf /kernel text=0x386a50 data=0x5c8b4+0x3626c syms=[0x4+0x4bf40+0x4+0x5b104] Loading /boot/defaults/loader.conf | menu /modules/acpi.ko text=0x477c0 data=0x2034+0xc98 syms=[0x4+0x6e60+0x4+0x8bfc] - And then it's dead Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt.
Re: Building/Installing DragonFly from within FreeBSD
Ulrich Spoerlein wrote: /modules/acpi.ko text=0x477c0 data=0x2034+0xc98 syms=[0x4+0x6e60+0x4+0x8bfc] - And then it's dead Are you sure (sure sure) it is dead? I had the situation that it would simply not use the console, and at some point the Login: prompt would show up (maybe won't happen with a serial console). cheers simon -- Serve - BSD +++ RENT this banner advert +++ASCII Ribbon /\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Re: Building/Installing DragonFly from within FreeBSD
On Thu, February 14, 2008 3:08 pm, Ulrich Spoerlein wrote: Hi there, though it seems to be supported to build (some releases) of DragonFly on (some releases) of FreeBSD and cross-install them, I can't get it to work. I tried building 1.0, 1.2, 1.4, 1.6 and 1.10 on 4.11, 5.5, 6.0 and 8.0. They all quickly die in buildworld during bootstrap-tools phase. Even plastering over some obvious differences, this seems to be not possible with the given releases. There's an existing guide: http://www.dragonflybsd.org/docs/upgrade-freebsd.shtml Though it sounds like you've done close to what it says already. The installer supports headless installs. You need to create a file called 'pfi.conf' (for Pre-Flight Installer) and put it on a USB thumb drive or floppy disk or something else that can be mounted and searched. There's an example file at: src/nrelease/installer/etc/defaults/pfi.conf I haven't tried this myself, but it should work.
Re: Building/Installing DragonFly from within FreeBSD
On Thu, 14.02.2008 at 22:16:38 +0100, Simon 'corecode' Schubert wrote: Ulrich Spoerlein wrote: /modules/acpi.ko text=0x477c0 data=0x2034+0xc98 syms=[0x4+0x6e60+0x4+0x8bfc] - And then it's dead Are you sure (sure sure) it is dead? I had the situation that it would simply not use the console, and at some point the Login: prompt would show up (maybe won't happen with a serial console). Guess I'll have to try with a real monitor then. But I switched on ttyd0 in /etc/ttys and nothing happened for like 5-8 minutes. Also no disk activity ... Perhaps I should try the 1.2 Release instead. Cheers, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt.
