Re: watchdog question
On 30/07/12 14:58, Konrad Neuwirth wrote: Now, my question: I read the kernel.watchdog.auto and kernel.watchdog.period knobs to mean the kernel can auto-update the kernel; on the other hand, the documentation refers me to the watchdogd daemon. The latter one claims /dev/wdog isn't writable. But why have two solutions to one problem? Doesn't the kernel auto updating suffice, anyway? There are two options: the kernel auto-refreshing or a userland process (watchdogd) refreshing. Whether you want one or the other depends; obviously the kernel auto-refresh is more convenient, but it may not be sufficient for your scenario. Just picture userland processes hanging but bits of the kernel going on. This is a scenario that only the latter option will get you out of. HTH, Alex
Re: Unable to mount hammer file system Undo failed
On 19/07/12 09:25, Wojciech Puchar wrote: this is example of what i fear about hammer. One error results in unability to mount. If it is just software error in hammer that's great. If it is design... not great. This is not a hammer problem but a problem with the underlying disk. It couldn't read from the disk - that is pretty much a file-system independent problem; UFS would fail equally miserably. Cheers, Alex
Re: dragonfly site nntp server dead?
Hi, On 21/06/12 17:07, codeb...@inbox.lv wrote: But a month or so ago the news server stopped responding. Trying again today it appears still offline. Does anybody know/care about this? I would prefer to use the nntp interface rather than the mailing lists if possible. Thanks. nntp service was indeed decommissioned - there was an email on 11/01/12 to users@ by Matt. You are definitely not alone in preferring nntp access to the mailing lists, and there was some activity to get them up and running a few months ago, but nothing has come of it. Cheers, Alex
Re: Is there a size limit of natacontrol?
Hi, On 27/02/12 12:20, Zenny wrote: I tried to create a RAID10 with natacontrol with 4 2TB HDDs, but it only shows 2TB (1718306MB) size of ar0 created instead of 4TB. In principle there is no such limit that I'm aware of, apart from the MBR partition size limit. It all depends where you are seeing those 2 TB. If it's a partition size, try using GPT.
Re: Forcing crash dump doesn't work
call dumpsys at the db prompt On 04/02/12 05:44, Pierre Abbat wrote: My computer rebooted itself again. (I'm pretty sure now it's a bug in hammer, from the time when it does it and the left periodic.cunsolerfu files.) I typed in the disk password, then it finished booting except for X, which failed to start. I removed the stale lockfile, killed kdm, logged into X, and switched back to the console to examine the periodic.* files. Suddenly I got a db prompt. I switched to my other machine and looked up the website for what to do next. I typed panic, and it output a whole bunch of stuff and gave me a prompt again. I typed call dumpsys and it rebooted. But then I found no new dumps in /var/crash. How do I get one? Pierre
Re: Is anyone still using gcc 4.1 on master?
It is always good to have an older gcc version, too, especially given that other BSDs stick to them. Importing clang is not an option unless you are volunteering. Cheers, Alex On 07/11/11 07:59, elekktrett...@exemail.com.au wrote: Is it time to get rid of it? It seems like a waste of space/compile time. Maybe replace it with clang-3? Is anyone using GCC 4.1 over 4.4? Petr
Re: CPAN Cannot Guess build type.
It is already telling you how to fix it: update your config.guess. Cheers, Alex On 31/10/11 08:25, Siju George wrote: Hi, I got the following error trying to install File::RsyncP on 2.13-DEVELOPMENT DragonFly v2.13.0.76.g0a4d48-DEVELOPMENT How do I fix it? Thanks --Siju === dfly-bkpsrv# cpan -i File::RsyncP AutoSplitting ../blib/lib/File/RsyncP/FileList.pm (../blib/lib/auto/File/RsyncP/FileList) ./configure configure: Configuring File::RsyncP::FileList based on rsync 2.6.3 checking build system type... ./config.guess: unable to guess system type This script, last modified 2003-10-03, has failed to recognize the operating system you are using. It is advised that you download the most up to date version of the config scripts from ftp://ftp.gnu.org/pub/gnu/config/ If the version you run (./config.guess) is already up to date, please send the following data and any information you think might be pertinent to config-patc...@gnu.org in order to provide the needed information to handle your system. config.guess timestamp = 2003-10-03 uname -m = i386 uname -r = 2.13-DEVELOPMENT uname -s = DragonFly uname -v = DragonFly v2.13.0.76.g0a4d48-DEVELOPMENT #1: Tue Oct 25 15:20:39 IST 2011 root@dfly-bkpsrv.hifxnx.local:/usr/obj/Backup1/src/sys/GENERIC /usr/bin/uname -p = i386 /bin/uname -X = hostinfo = /bin/universe = /usr/bin/arch -k = /bin/arch = /usr/bin/oslevel = /usr/convex/getsysinfo = UNAME_MACHINE = i386 UNAME_RELEASE = 2.13-DEVELOPMENT UNAME_SYSTEM = DragonFly UNAME_VERSION = DragonFly v2.13.0.76.g0a4d48-DEVELOPMENT #1: Tue Oct 25 15:20:39 IST 2011 root@dfly-bkpsrv.hifxnx.local:/usr/obj/Backup1/src/sys/GENERIC configure: error: cannot guess build type; you must specify one *** Error code 1 Stop in /root/.cpan/build/File-RsyncP-0.70-7H5iDY/FileList. *** Error code 1 Stop in /root/.cpan/build/File-RsyncP-0.70-7H5iDY. CBARRATT/File-RsyncP-0.70.tar.gz /usr/bin/make -- NOT OK Running make test Can't test without successful make Running make install Make had returned bad status, install seems impossible
Re: onboard sound
Devices are automatically created by devfs. MAKEDEV is obsolete. If you don't know which sound driver is the one you need, there is a pseudo-driver that depends on all others (sound.ko, iirc). If you load that, and you still don't get /dev/dsp and family, then odds are we don't support your card. Cheers, Alex On 31/10/11 16:25, Pierre Abbat wrote: On Monday 31 October 2011 11:01:16 Ed Berger wrote: I'd try adding the following to /boot/loader.conf #current hda sound driver snd_hda_load=YES #older ac97 sound driver snd_ich_load=YES I haven't rebooted, but I ran kldload snd_hda and it accepted the command. Now I need to create the device files. http://www.dragonflybsd.org/docs/handbook/handbook-sound-setup/ says to run MAKEDEV, but there is no MAKEDEV. How do I do this? Pierre
Re: Performance results / VM related SMP locking work - committed (3)
Great work! Nonetheless I feel that the last few changes nerf a quad-core machine way too much; you are killing 50% of what you gained in the -j48 case for buildkernel and even worse than in the original case with -j4, which is the most common case. buildworld -j8 on test29 also loses 50% of the original improvement with commit 2 or 3. I don't think this is a good trade-off at all; are we really optimizing for 4-socket 48-core machines and letting the way more common 4-8 core machines out? Simply adding lwkt_yield()s all over the place doesn't really sound like a great strategy in the first place. It sounds more like a stopgap or debug solution for a 48-core machine than something that should be committed (straight ahead). Cheers, Alex Hornung On 29/10/11 00:28, Matthew Dillon wrote: 89.61 real 196.30 user59.04 sys test29 -j4 (patch) 86.55 real 195.14 user49.52 sys test29 -j4 (commit) 93.77 real 195.94 user67.68 sys test29 -j4 (commit 3) 167.62 real 360.44 user 4148.45 sys monster -j48 (prepatch) 110.26 real 362.93 user 1281.41 sys monster -j48 (patch) 101.68 real 380.67 user 1864.92 sys monster -j48 (commit 1) 59.66 real 349.45 user 208.59 sys monster -j48 (commit 3) 96.37 real 209.52 user63.77 sys test29 -j48 (patch) 85.72 real 196.93 user52.08 sys test29 -j48 (commit 1) 90.01 real 196.91 user70.32 sys test29 -j48 (commit 3) Kernel build results are as expected for the most part. -j 48 build times on the many-cores monster are GREATLY improved, from 101 seconds to 59.66 seconds (and down from 167 seconds before this work began). That's a +181% improvement, almost 3x faster. The -j 4 build and the quad-core test29 build were not expected to show any improvement since there isn't really any spinlock contention with only 4 cores. There was a slight nerf on test28 (the quad-core box) but that might be related to some of the lwkt_yield()s added and not so much the PQ_INACTIVE/PQ_ACTIVE vm_page_queues[] changes.
Re: UFS in CF for /boot and Hammer for the rest and failover+load balancing
Regarding disk encryption, there are basically two approaches now. One is tcplay(8), which is a TrueCrypt compatible BSD-licensed solution, but fairly experimental. The more stable/well tested solution is the GPL-licensed cryptsetup(8), which is the same as on Linux. Both use dm_target_crypt underneath and both are fully supported for cryptdisks(8), crypttab(5) and mkinitrd(8). Using the initrd approach you can encrypt your / with any of the above approaches, but /boot needs to be unencrypted. HTH, Alex Hornung On 03/10/11 08:15, Zenny wrote: Thank you Justin for a comprehensive reply. Appreciate it! I shall check with the vkernel stuffs to limit resources for jails (seems like a sharp learning curve ;-) ) Since you stated that 4 drives are overkill, does hammer allow create a pool like in ZFS of two master drives and two slave drives with remote machine which works exactly as a failover + load balancing (as in the case of DRBD in Linux or HAST in the coming FreeBSD-9). Where exactly can find the detailed document for scripting for a streaming the HAMMER data to the remote machines? As I stated earlier, I want: /boot in CF or SanDisk / in HDD and other data swapcahce in SSD or in HAMMER / in order to separate data from the operating system. But I could not find documents for manual installation mode to meet my requirements. Let me know if there are any. Thanks! On Sun, Oct 2, 2011 at 11:50 PM, Justin Sherrill jus...@shiningsilence.com mailto:jus...@shiningsilence.com wrote: I'm not sure about the jails. They I think work the same on DragonFly, though the resource limits aren't there. You could potentially use virtual kernels to get a similar effect. See the vkernel man page for that. You should be able to set up the root and other volumes normally. 4 hard drives may be overkill - you can stream from master to slave volumes in Hammer, for which 2 drives will work. If you want more duplication, hardware RAID may be a good idea; people have been trying out Areca cards with success recently. AES256 is supported, or at least I see the tcplay(8) man page has an example using it. I haven't used disk encryption enough to know it well. You can use Hammer to stream data to other machines, and then in the event of something going wrong, promote the slave drive in the surviving unit to master. This would require some scripting or manual intervention; this isn't covered with an automatic mechanism. On Sun, Oct 2, 2011 at 5:50 AM, Zenny garbytr...@gmail.com mailto:garbytr...@gmail.com wrote: Hi: I am pretty new to Dragonfly or BSD world. HammerFS seems to be very innovative. Thanks to Matt and team for their hard work. I would like to do something with Hammer+UFS like the following, inspired by Paul's work (http://www.psconsult.nl/talks/NLLGG-BSDdag-Servers/), but could not figure out exactly: 1) Creation of a server with a jail with minimal downtime as offered by nanobsd scripts in FreeBSD. Two failover kernels. Is there such scripts for DragonflyBSD? 2) I want to have the minimal boot (ro UFS) and configurations like that of the nanobsd image on a compact flash while the entire root and data in an array of HDDs (at least 4) with of course an SSD for swapcache. The latter could be Hammer to avoid softraid. 3) All HDDs should be encrypted with AES256 (I could not find whether DragonflyBSD supports that), and accessible either in the /boot of CF or somewhere else (could be ssh tunneled from another network). 4) I could not figure out the features of jail available for DragonflyBSD. FreeBSD-9-CURRENT has the resource containers (http://wiki.freebsd.org/Hierarchical_Resource_Limits). Are they applicable in DragonflyBSD's case. 5) Is there any way that the two similar servers in two different locations can securely mirror for failover as well as load-balancing? Appreciate your thoughtful inputs! Apology in advance if my post above appears to be pretty naive. Thanks in advance to the entire DF community and developers! zenny
Re: Firefox 2011Q2 compile error
Siju, sorry, I don't really know. just apply it manually, but I see no reason for it to fail. Cheers, Alex On 13/09/11 07:11, Siju George wrote: Hi, Please Alex, Marino or some one give me a clue on why this failed? Am I using a wrong version of src? Thanks On Mon, Aug 29, 2011 at 11:42 AM, Siju George sgeorge...@gmail.com wrote: On Wed, Aug 24, 2011 at 6:38 PM, Alex Hornung ahorn...@gmail.com wrote: http://gitweb.dragonflybsd.org/dragonfly.git/commit/e7322b09faff75b1298e9bfe444633425d173536 Hi I wonder if i made any mistake in patching. Please see and help Thanks --Siju blk-build# patch pthread.h-diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |--- a/include/pthread.h |+++ b/include/pthread.h -- File to patch: include/pthread.h Patching file include/pthread.h using Plan A... Hunk #1 failed at 140. 1 out of 1 hunks failed--saving rejects to include/pthread.h.rej done blk-build# pwd /usr/src blk-build# git describe v2.11.0-743-g593fea8 blk-build# cat include/pthread.h.rej @@ -140,136 +140,136 @@ * Thread function prototype definitions: */ __BEGIN_DECLS -intpthread_atfork(void (*)(void), void (*)(void), void (*)(void)); -intpthread_attr_destroy(pthread_attr_t *); +intpthread_atfork(void (*)(void), void (*)(void), void (*)(void)) __exported; +intpthread_attr_destroy(pthread_attr_t *) __exported; intpthread_attr_getguardsize(const pthread_attr_t * __restrict, - size_t *); + size_t *) __exported; intpthread_attr_getstack(const pthread_attr_t * __restrict, - void ** __restrict, size_t * __restrict); -intpthread_attr_getstacksize(const pthread_attr_t *, size_t *); -intpthread_attr_getstackaddr(const pthread_attr_t *, void **); -intpthread_attr_getdetachstate(const pthread_attr_t *, int *); -intpthread_attr_init(pthread_attr_t *); -intpthread_attr_setguardsize(pthread_attr_t *, size_t); -intpthread_attr_setstack(pthread_attr_t *, void *, size_t); -intpthread_attr_setstacksize(pthread_attr_t *, size_t); -intpthread_attr_setstackaddr(pthread_attr_t *, void *); -intpthread_attr_setdetachstate(pthread_attr_t *, int); -intpthread_barrier_destroy(pthread_barrier_t *); + void ** __restrict, size_t * __restrict) __exported; +intpthread_attr_getstacksize(const pthread_attr_t *, size_t *) __exported; +intpthread_attr_getstackaddr(const pthread_attr_t *, void **) __exported; +intpthread_attr_getdetachstate(const pthread_attr_t *, int *) __exported; +intpthread_attr_init(pthread_attr_t *) __exported; +intpthread_attr_setguardsize(pthread_attr_t *, size_t) __exported; +intpthread_attr_setstack(pthread_attr_t *, void *, size_t) __exported; +intpthread_attr_setstacksize(pthread_attr_t *, size_t) __exported; +intpthread_attr_setstackaddr(pthread_attr_t *, void *) __exported; +intpthread_attr_setdetachstate(pthread_attr_t *, int) __exported; +intpthread_barrier_destroy(pthread_barrier_t *) __exported; intpthread_barrier_init(pthread_barrier_t *, - const pthread_barrierattr_t *, unsigned); -intpthread_barrier_wait(pthread_barrier_t *); -intpthread_barrierattr_destroy(pthread_barrierattr_t *); -intpthread_barrierattr_init(pthread_barrierattr_t *); + const pthread_barrierattr_t *, unsigned) __exported; +intpthread_barrier_wait(pthread_barrier_t *) __exported; +intpthread_barrierattr_destroy(pthread_barrierattr_t *) __exported; +intpthread_barrierattr_init(pthread_barrierattr_t *) __exported; intpthread_barrierattr_getpshared(const pthread_barrierattr_t *, - int *); -intpthread_barrierattr_setpshared(pthread_barrierattr_t *, int); -void pthread_cleanup_pop(int); -void pthread_cleanup_push(void (*) (void *), void *); -intpthread_condattr_destroy(pthread_condattr_t *); -intpthread_condattr_init(pthread_condattr_t *); + int *) __exported; +intpthread_barrierattr_setpshared(pthread_barrierattr_t *, int) __exported; +void pthread_cleanup_pop(int) __exported; +void pthread_cleanup_push(void (*) (void *), void *) __exported; +intpthread_condattr_destroy(pthread_condattr_t *) __exported; +intpthread_condattr_init(pthread_condattr_t *) __exported; -intpthread_condattr_getpshared(const pthread_condattr_t
Re: Firefox 2011Q2 compile error
http://gitweb.dragonflybsd.org/dragonfly.git/commit/e7322b09faff75b1298e9bfe444633425d173536 On 24 August 2011 13:46, Siju George sgeorge...@gmail.com wrote: Hi, I get this compiling firefox from pkgsrc-2011Q2 0n v2.11.0.586.ga700a-DEVELOPMENT :-( c++ -o jsnativestack.o -c -I./../../dist/system_wrappers_js -include ./config/gcc_hidden.h -DOSTYPE=\DragonFly2.11-DEVELOPMENT\ -DOSARCH=DragonFly -DEXPORT_JS_API -D__STDC_LIMIT_MACROS -DJS_HAS_CTYPES -DDLL_PREFIX=\lib\ -DDLL_SUFFIX=\.so\ -Ictypes/libffi/include -I. -I. -I. -I./../../dist/include -I./../../dist/include/nsprpub -I/usr/pkgsrc/devel/xulrunner/work/mozilla-2.0/dist/include/nspr -I. -I./assembler -I./yarr -fPIC -I/usr/include -I/usr/pkg/include -I/usr/pkg/include/freetype2 -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -I/usr/include -I/usr/pkg/include -I/usr/pkg/include/freetype2 -fno-strict-aliasing -pthread -pipe -DNDEBUG -DTRIMMED -O2 -DUSE_SYSTEM_MALLOC=1 -DENABLE_ASSEMBLER=1 -DENABLE_JIT=1 -I/usr/include -I/usr/pkg/include -I/usr/pkg/include/freetype2 -DMOZILLA_CLIENT -include ./js-confdefs.h -MD -MF .deps/jsnativestack.pp jsnativestack.cpp jsnativestack.cpp: In function 'void* js::GetNativeStackBaseImpl()': jsnativestack.cpp:207: error: 'pthread_getattr_np' was not declared in this scope gmake[3]: *** [jsnativestack.o] Error 1 gmake[3]: Leaving directory `/usr/pkgsrc/devel/xulrunner/work/mozilla-2.0/js/src' gmake[2]: *** [libs_tier_js] Error 2 gmake[2]: Leaving directory `/usr/pkgsrc/devel/xulrunner/work/mozilla-2.0' gmake[1]: *** [tier_js] Error 2 gmake[1]: Leaving directory `/usr/pkgsrc/devel/xulrunner/work/mozilla-2.0' gmake: *** [all] Error 2 *** Error code 2 Stop. bmake: stopped in /usr/pkgsrc/devel/xulrunner *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/devel/xulrunner *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/www/firefox *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/www/firefox You have new mail. blk-build# Thanks --Siju
Re: pkgsrc-update failes with core dumps
Firefox needs some manual tweaking here and there; there's a NetBSD PR about it. It boils down to us not having a buggy compiler and firefox basically requiring a buggy compiler to build :) XOrg pretty much always builds fine. Stay with a quarterly if you want to be sure things work as intended. Cheers, Alex On 23/08/11 14:41, Siju George wrote: On Tue, Aug 23, 2011 at 5:55 PM, Max Herrgard herrg...@gmail.com wrote: On 23 aug 2011, at 14.08, Siju George wrote: Should i use 2011Q1 or 2011Q2 ? 2011Q2 is orgin/master same as origin/pkgsrc-2011Q2 ? No. master is pkgsrc-current, the development branch. 2011Q2 is the stable release branch. This machine will be testing/learning bulk builds also I need to know what branch is best for my desktop :-) I'm using -current (the git master branch) myself. does xorg and firefox compile well in master? Thanks --Siju
Re: /usr/libexec/ld-elf.so.2: Shared object libintl.so.3 not found in many places.
http://bugs.dragonflybsd.org/issue2110 On 9 August 2011 10:25, Siju George sgeorge...@gmail.com wrote: Hi, I installed the development version and while compling packages I am getting this error with many packages. /usr/libexec/ld-elf.so.2: Shared object libintl.so.3 not found I first faced this while starting lynx installed from packages. Then i had to re-compile the lynx and then bash and then a lot of stuff. Now compiling firefox I get this == libtool: link: ar cru .libs/im-xim.a gtkimcontextxim.o imxim.o libtool: link: ranlib .libs/im-xim.a libtool: link: ( cd .libs rm -f im-xim.la ln -s ../im-xim.la im-xim.la ) ../../gtk/gtk-query-immodules-2.0 im-am-et.la im-cedilla.la im-cyrillic-translit.la im-inuktitut.la im-ipa.la im-multipres im-xim.la gtk.immodules /usr/libexec/ld-elf.so.2: Shared object libintl.so.3 not found, required by libgtk-x11-2.0.so.0 gmake[3]: *** [gtk.immodules] Error 1 gmake[3]: Leaving directory `/usr/pkgsrc/x11/gtk2/work/gtk+-2.24.5/modules/input' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/pkgsrc/x11/gtk2/work/gtk+-2.24.5/modules' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/pkgsrc/x11/gtk2/work/gtk+-2.24.5' gmake: *** [all] Error 2 *** Error code 2 Stop. bmake: stopped in /usr/pkgsrc/x11/gtk2 *** Error code 1 == Trying to compile gtk2 i get this error = /usr/pkgsrc/devel/xulrunner/work/mozilla-release/js/src/jsnativestack.cpp:150: undefined reference to `pthread_attr_get_np' /usr/libexec/binutils221/elf/ld: js: hidden symbol `pthread_attr_get_np' isn't defined /usr/libexec/binutils221/elf/ld: final link failed: Bad value gmake[4]: *** [js] Error 1 gmake[4]: Leaving directory `/usr/pkgsrc/devel/xulrunner/work/mozilla-release/js/src/shell' gmake[3]: *** [libs] Error 2 gmake[3]: Leaving directory `/usr/pkgsrc/devel/xulrunner/work/mozilla-release/js/src' gmake[2]: *** [libs_tier_js] Error 2 gmake[2]: Leaving directory `/usr/pkgsrc/devel/xulrunner/work/mozilla-release' gmake[1]: *** [tier_js] Error 2 gmake[1]: Leaving directory `/usr/pkgsrc/devel/xulrunner/work/mozilla-release' gmake: *** [all] Error 2 *** Error code 2 === is there any way to permnantly fix this? Thanks --Siju
Re: pkgsrc reports
Rumko, the patch that was proposed by OBATA Akio / oba...@netbsd.org works correctly and is a good solution. I've also submitted it upstream[1]. The remaining build issue is something that needs investigation and affects a number of packages. It might well not be mono related, so there is absolutely no reason to hold off this patch. The other issue happens due to the linker script forcing the __progname symbol to be local by using local: *. Similar things happen to xchat and asterisk, at least. This issue might well be in other toolsuites, since NetBSD doesn't seem to be affected. Cheers, Alex [1]: http://bugzilla.xamarin.com/show_bug.cgi?id=123 On 22 May 2011 17:21, Rumko rum...@gmail.com wrote: On Sunday 15. of May 2011 08:45:25 Francois Tigeot wrote: On Sat, May 14, 2011 at 07:43:45PM +0200, Rumko wrote: Francois Tigeot wrote: On Wed, May 11, 2011 at 07:56:29AM +0100, Alex Hornung wrote: It seems that to get mono building again we just need a simple patch (upstream and pkgsrc ideally :)) to mono/utils/mono-sigcontext.h, as well as undefining the defined(UCONTEXT_GREGS) (config? Makefile?) option. I've opened a PR with patch a month ago: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=44846 It has been assigned to dfly-pkg-people@ and never been committed afaik. AFAIR I was told that the patch in the PR did not in fact fix the build, it just made it move along further. Please finish the patches or if they in fact do fix the build, nudge me again and I'll look into it. The next error is unrelated and is possibly caused by a problem in our toolchain. Please look into the error in order to make the package actually build. Now if you want to sit on patches so be it; I won't waste anymore time trying to fix mono. Have you upstreamed these patches? P.S.: IIRC I saw some mono related commits lately in pkgsrc, maybe the patches now fix all build-time errors? -- Regards, Rumko
Re: pkgsrc-update failes with core dumps
Yah, happens quite often, not hardware related. Just try again and again and eventually it works. Haven't really looked into why it happens... Cheers, Alex On 30 July 2011 18:12, Mark Doe mark.doe.p...@gmail.com wrote: Hi, I am running a 2.11-DEVEL 64Bit dfBSD on an intel STBL Server Board with 8GB RAM. Server, Hardware, Disks, RAM and everything is brand new. Running with LINUX and NetBSD either didnt show any kind of problems. I can't get the pkgsrc with git and get 2 different errors (create checkout and just update). Any help is appreciated! Code: mkdir -p /usr/pkgsrc cd /usr/pkgsrc git init Initialized empty Git repository in /usr/pkgsrc/.git/ cd /usr/pkgsrc git remote add origin git://git.dragonflybsd.org/pkgsrcv2.git cd /usr/pkgsrc git fetch origin remote: Counting objects: 1608685, done. remote: Compressing objects: 100% (481721/481721), done. remote: Total 1608685 (delta 1129219), reused 1575226 (delta 1102729) Receiving objects: 100% (1608685/1608685), 477.66 MiB | 1.10 MiB/s, done. Resolving deltas: 100% (1129219/1129219), done. From git://git.dragonflybsd.org/pkgsrcv2 * [new branch] dragonfly-2010Q3 - origin/dragonfly-2010Q3 *** Signal 10 Stop in /usr. bash-4.2# make pkgsrc-create-repo If problems occur you may have to rm -rf pkgsrc and try again. mkdir -p /usr/pkgsrc cd /usr/pkgsrc git init Reinitialized existing Git repository in /usr/pkgsrc/.git/ cd /usr/pkgsrc git remote add origin git://git.dragonflybsd.org/pkgsrcv2.git fatal: remote origin already exists. *** Error code 128 Stop in /usr. bash-4.2# make pkgsrc-update cd /usr/pkgsrc git pull From git://git.dragonflybsd.org/pkgsrcv2 * [new branch] dragonfly-master - origin/dragonfly-master * [new branch] master - origin/master Bus error (core dumped) *** Error code 1 Stop in /usr
Re: Can DFly mount ext4?
To keep it short, no. There might be some ext4 fs that it might be able to mount (with specific inode size, lacking all sorts of ext4 features, etc), but in the general case it's not possible. I'd recommend you grab your ubuntu CD, start the live system and fix it from there. Cheers, Alex On 27/06/11 01:44, Pierre Abbat wrote: A friend gave me an Ubuntu laptop which I proceeded to install a few programs on and then hose. It came with a user a which I decided to change to phma. I renamed the home directory, edited /etc/passwd and /etc/group, and rebooted. I had forgotten to edit /etc/shadow, so I can't log in. It's set up to show Ubuntu and four dots instead of a GRUB prompt. I tried mounting it in the USB enclosure on my Linux box; it said unsupported features, which a bit of googling tells me means it's an ext4 filesystem. I try mounting it on DragonFly as ext2fs and get invalid argument. Is there a way to mount ext4fs? Pierre
Re: HEADS DOWN: via padlock possibly broken on master
Hi all, The new padlock rng code has now been tested on both i386 and x86_64 (on a Via Nano L2200) and seems stable. Many thanks to Sascha Wildner for helping out with the testing. Cheers, Alex On 18/06/11 01:29, Alex Hornung wrote: Hi all, I just commited something that might well cause a kernel panic if you are using a via cpu with padlock and use the padlock module. I added support to make use of Via's on-chip RNG, but someone needs to test it to confirm that it works as expected; I don't have a VIA CPU for testing. Regards, Alex Hornung
Re: Add AHCI workaround for Intel mobo / Intel SSD probing bug
Yes, if the ISO has been built after the date, and it has, it'll be included. Just download the master snapshot, not the release. Cheers, Alex Hornung On 19/06/11 16:41, Edward Martinez wrote: Hi, I hope this time my email goes through, first time I accidentally send it to the wrong email address.:-[ I'm wondering if Add AHCI workaround for Intel mobo / Intel SSD probing bug fix is included in the lastest DragonFlyBSD snapshot iso (jun 19)? http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/f2dba7003b2add226b3999a41a99fd278cc5a26f Regards, ED
Re: HEADS DOWN: via padlock possibly broken on master
Chris, simply put, because nobody will test it. Padlock is not on by default, it has to be enabled in the kernel config or the module loaded. In any case, with the most recent commit, this should work just fine, I managed to test it on my NAS which has a via nano. Cheers, Alex On 18/06/11 22:03, Chris Turner wrote: On Sat, Jun 18, 2011 at 01:29:21AM +0100, Alex Hornung wrote: I added support to make use of Via's on-chip RNG, but someone needs to test it to confirm that it works as expected; I don't have a VIA CPU for testing. As someone recently bit by a similar type of issue ( rum(4) not being up-ported for new wifi stuff) this seems like a bad idea - If the code is untested and not 'core' -- why not commit it with some kind of 'options' guard or somesuch until someone is able to test, etc? /2c - Chris
HEADS DOWN: via padlock possibly broken on master
Hi all, I just commited something that might well cause a kernel panic if you are using a via cpu with padlock and use the padlock module. I added support to make use of Via's on-chip RNG, but someone needs to test it to confirm that it works as expected; I don't have a VIA CPU for testing. Regards, Alex Hornung
Re: system update question
No. You can checkout directly.
On Jun 6, 2011 7:02 PM, Justin Sherrill jus...@shiningsilence.com wrote:
Wouldn't he need to do this once, to establish the local copy of the
branch?
cd /usr/src git branch DragonFly_RELEASE_2_10
origin/DragonFly_RELEASE_2_10
On Mon, Jun 6, 2011 at 11:16 AM, Matthias Rampke
matthias.ram...@googlemail.com wrote:
Hi,
to switch to the stable branch
cd /usr/src git checkout DragonFly_RELEASE_2_10
from that point on git pull in /usr/src or make src-update in /usr will
keep
you up to date on the stable branch.
For more info, have a look at /usr/src/{README,UPDATING} and section 7 of
the man pages, esp. build(7).
Regards,
matthiasr
Re: Fwd: pkgbox64 pkgsrc 2011Q1 DragonFly 2.11/x86_64 2011-06-03 02:14
On 06/06/11 04:36, Justin Sherrill wrote: pkgsrc bulk build report DragonFly 2.11/x86_64 Compiler: gcc Build start: 2011-06-03 02:14 Build end: 2011-06-06 03:10 Full report: http://avalon.dragonflybsd.org/reports/i386/2.11/20110603.0214/meta/report.html it's not there (yet?). Can you please re-upload it? Regards, Alex
Re: cryptsetup failed to access temporary keystore device
It would be helpful if you could provide some more information, specifically: a) dmesg (up to the moment when this happens) b) kldstat c) dmsetup ls Cheers, Alex On 03/06/11 22:18, Pierre Abbat wrote: # cryptsetup luksFormat /dev/da8s0e WARNING!!! Possibly insecure memory, missing mlockall() WARNING! This will overwrite data on /dev/da8s0e irrevocably. Are you sure? (Type uppercase yes): YES Enter LUKS passphrase: Verify passphrase: Failed to access temporary keystore device. When I dump it, there are no keyslots in use. What's wrong? This is the external drive on the USB cable; I have created a Hammer filesystem on another partition. Pierre
Re: cryptsetup failed to access temporary keystore device
The issue, as far as I can tell, is with the usb stack. The contigmalloc_map failures in dmesg just after creating the dm volume probably come from somewhere there. I'm not sure how to work around this, you could probably try on a freshly rebooted system or without ehci. Regards, Alex On 04/06/11 18:52, Pierre Abbat wrote: On Saturday 04 June 2011 06:37:28 Alex Hornung wrote: It would be helpful if you could provide some more information, specifically: a) dmesg (up to the moment when this happens) b) kldstat c) dmsetup ls # dmsetup ls crypt (255, 504430599) # kldstat Id Refs AddressSize Name 1 17 0xc010 88a9d4 kernel 21 0xc098b000 26ce4linux.ko 31 0xc09b2000 78d04acpi.ko 41 0xc0a2b000 134ccahci.ko 51 0xc0a3f000 97cc ehci.ko 62 0xc0a49000 b9f8 dm.ko 71 0xcc74d000 a000 linprocfs.ko 81 0xccf44000 9000 i915.ko 91 0xccf4d000 13000drm.ko 101 0xcd26 18000dm_target_crypt.ko 111 0xd2e8 12000ext2fs.ko dmesg is attached. Pierre
Re: md5 sums and hammerfs encryption
Hi, On 24/05/11 18:42, Milo wrote: - On wikipedia I found that hammerfs is supporting transparent encryption but I was unable to find more details about that while checking linked to article's page man pages and notes. Can you shed some light on this topic? HAMMER itself doesn't provide any encryption support. Our transparent encryption is file-system agnostic (you can also encrypt your swap and UFS, for example) and is implemented in the device mapper (dm) as dm_target_crypt. To use it, you should check out the cryptsetup man page, or for that matter, any linux dm-crypt disk encryption tutorial, since we have the same *userland* tools. The installer also has support for creating encrypted volumes on install already. Hope that helps, Alex Hornung
Re: md5 sums and hammerfs encryption
On 25/05/11 15:47, Pierre Abbat wrote: Last I checked, I get only one chance to type the password, and as the keyboard layout isn't set yet, I usually mess it up. Ubuntu has an early cryptdisks init script and a later one, and gives me three tries (which is the default according to the man page). I was intending to do a number of changes to the encryption stuff this summer anyway, so I'll take that into account. I'll probably up the default number of tries of the root volume to 2 or 3. Also, if root is not encrypted but some other partition is, can the init script time out and continue booting without the encrypted partition? For rebooting remotely this would be useful. Yes, I also want to introduce a few changes to crypttab, which is where these changes would reside. Adding support for a variety of options including a timeout is in my plans already. Regards, Alex
Re: pkgsrc reports
It seems that to get mono building again we just need a simple patch (upstream and pkgsrc ideally :)) to mono/utils/mono-sigcontext.h, as well as undefining the defined(UCONTEXT_GREGS) (config? Makefile?) option. I'd appreciate it if someone could give it a shot, it should be fairly straight forward. Regards, Alex On 11/05/11 05:18, Justin Sherrill wrote: I have two reports on recent pkgsrc builds, so I'll just send the URLs instead of forwarding each: DragonFly 2.11, x86_64, pkgsrc-2011Q1: http://avalon.dragonflybsd.org/reports/x86_64/2.11/20110508.2107/meta/report.html DragonFly 2.10, i386, pkgsrc-2011Q1: (x86_64 report filepath has been fixed for next build) http://avalon.dragonflybsd.org/reports/x86_64/2.11/20110510.2020/meta/report.html security/heimdal is the only real stumbling block right now.
Re: pkgsrc and DragonFly current DragonFly 2.9/x86_64 2011-03-11 15:00
Considering that 500 of those are broken because of a checksum mismatch... no, it's not that bad. Regards, Alex On 22/03/11 02:02, elekktrett...@exemail.com.au wrote: Thats quite a few packages not building (around 800) since the switch, at least in comparison to previous bulk build. Is any other BSD using GCC 4.4? Petr
Re: Unable to boot vkernel: Permission denied
Did you enable the vkernel sysctl? Cheers, Alex On 15/03/11 08:47, Chirag Kantharia wrote: On Tue, Mar 15, 2011 at 10:35:23AM +0400, Nuno Antunes wrote: | Do you have permission to create the memory file? Hi Nuno, I'm executing ./boot/kernel as root user. I assume that should be enough.
Re: cannot mount disk with hammer file system
The issue boils down to VirtualBox not having the same serial numbers for disks as vmware does. You should be able to figure out which one the right one is by listing the da* and ad* devices in /dev from a live CD. Alternatively, if VirtualBox supports disk serial numbers, doing ls /dev/serno will yield the information, as others have told you. By the way, if you have attached screenshots, they definitely haven't arrived here Can you please repost them somehow, possibly on imageshack or so and providing a link? Kind Regards, Alex Hornung On 23 February 2011 12:27, Úlfar Ellenarson u...@applicon.is wrote: HI Antonio. Thank you for your posts and help. I have taken a screenshot of the mounted etc/fstab or better said /mnt/etc/fstab and I have also ls –l /mnt/dev/serno. The only thing is I have not looked into the loader.conf which I reckon is mostly likely either in /boot or /etc. I think the problem is that dragonflybsd is not creating the devices upon boot because I have moved the system from vmware workstation 6.5 to virtualbox 4.04. I have looked into the man 8 boot page, however there is considerably less information about dragonfly bsd on the web than linux. I have converted linux physical machines using rsync, cpio, and netcat to vmware, but I have little experience with dragonfly. Kind regards, Úlfar Ellenson *From:* Antonio Huete Jimenez [mailto:ahuete.de...@gmail.com] *Sent:* Wednesday, February 23, 2011 12:14 PM *To:* Úlfar Ellenarson *Cc:* users@crater.dragonflybsd.org *Subject:* Re: cannot mount disk with hammer file system Hi Úlfar, Boot the livecd and mount the disk where DFly is installed in, then provide this: - Do a 'ls -l /dev/serno' - fstab of the installed system (not the LiveCD) - loader.conf from the installed system (it should be in the boot directory) Thanks, Antonio Huete 2011/2/23 Úlfar Ellenarson u...@applicon.is Added information regarding boot problem. The message upon boot is: Mounting root from hammer:serno/1.s1d tryroot serno/01.s1d no disk named 'serno/001.s1d' hammer_mountroot: can't find devvp boot mount failed: 6 mountroot *From:* users-err...@crater.dragonflybsd.org [mailto: users-err...@crater.dragonflybsd.org] *On Behalf Of *Úlfar Ellenarson *Sent:* Tuesday, February 22, 2011 12:35 PM *To:* users@crater.dragonflybsd.org *Subject:* cannot mount disk with hammer file system Hi. My first time posting on this list. My problem in a nutshell is I installed dragonfly bsd 2.8 in vmware workstation. I reinstalled the host system that vmware workstation was on and decided on using virtualbox. I imported my dragonfly bsd vmware workstatation vmdk files into virtualbox. Upon boot in virtualbox I run into the problem of mounting the disk. I am prompted at the boot prompt to detect the disk that the system resides on. I have tried hammer:ad0s1, hammer:ad0s1a, hammer:ad0s1d and just ad0s1. I am however not able to boot the system. I have also booted from the live iso image and mounted the system manually into /mnt using mount_hammer /dev/ad0s1a /mnt and took a screenshot of /etc/fstab. I however ask if there is a simple way to fix my mount problem. Any information needed in regards to solving this problem will be gladly appended. *kær kveðju/kind regards,* * * *Úlfar Ellenarson* SAP ráðgjafi / SAP Consultant [image: cid:image001.jpg@01CAE862.EFF59A90] Borgartúni 37 105 Reykjavík, Ísland *T: *+354 563 6226 *E: * u...@applicon.is h...@applicon.is *W:* www.applicon.is image001.jpg
Re: SV: cannot mount disk with hammer file system
Thanks, but serno.jpg is missing the most important bit; the window had a scrollbar and the last bit of every line was cut. Can you please resend without the scrollbar? Regards, Alex On 23/02/11 21:31, Úlfar Ellenarson wrote: Hi Alex. Here is a screenshot of /mnt/boot/loader.conf/mnt/dev/serno/mnt/dev/ad1s* and /mnt/etc/fstab sent as an attachment. *Frá:* Alex Hornung [ahorn...@gmail.com] *Sent:* 23. febrúar 2011 13:44 *Viðtakandi:* Úlfar Ellenarson *Afrit:* users@crater.dragonflybsd.org *Efni:* Re: cannot mount disk with hammer file system The issue boils down to VirtualBox not having the same serial numbers for disks as vmware does. You should be able to figure out which one the right one is by listing the da* and ad* devices in /dev from a live CD. Alternatively, if VirtualBox supports disk serial numbers, doing ls /dev/serno will yield the information, as others have told you. By the way, if you have attached screenshots, they definitely haven't arrived here Can you please repost them somehow, possibly on imageshack or so and providing a link? Kind Regards, Alex Hornung On 23 February 2011 12:27, Úlfar Ellenarson u...@applicon.is mailto:u...@applicon.is wrote: HI Antonio. Thank you for your posts and help. I have taken a screenshot of the mounted etc/fstab or better said /mnt/etc/fstab and I have also ls –l /mnt/dev/serno. The only thing is I have not looked into the loader.conf which I reckon is mostly likely either in /boot or /etc. I think the problem is that dragonflybsd is not creating the devices upon boot because I have moved the system from vmware workstation 6.5 to virtualbox 4.04. I have looked into the man 8 boot page, however there is considerably less information about dragonfly bsd on the web than linux. I have converted linux physical machines using rsync, cpio, and netcat to vmware, but I have little experience with dragonfly. Kind regards, Úlfar Ellenson *From:*Antonio Huete Jimenez [mailto:ahuete.de...@gmail.com mailto:ahuete.de...@gmail.com] *Sent:* Wednesday, February 23, 2011 12:14 PM *To:* Úlfar Ellenarson *Cc:* users@crater.dragonflybsd.org mailto:users@crater.dragonflybsd.org *Subject:* Re: cannot mount disk with hammer file system Hi Úlfar, Boot the livecd and mount the disk where DFly is installed in, then provide this: - Do a 'ls -l /dev/serno' - fstab of the installed system (not the LiveCD) - loader.conf from the installed system (it should be in the boot directory) Thanks, Antonio Huete 2011/2/23 Úlfar Ellenarson u...@applicon.is mailto:u...@applicon.is Added information regarding boot problem. The message upon boot is: Mounting root from hammer:serno/1.s1d tryroot serno/01.s1d no disk named 'serno/001.s1d' hammer_mountroot: can't find devvp boot mount failed: 6 mountroot *From:*users-err...@crater.dragonflybsd.org mailto:users-err...@crater.dragonflybsd.org [mailto:users-err...@crater.dragonflybsd.org mailto:users-err...@crater.dragonflybsd.org] *On Behalf Of *Úlfar Ellenarson *Sent:* Tuesday, February 22, 2011 12:35 PM *To:* users@crater.dragonflybsd.org mailto:users@crater.dragonflybsd.org *Subject:* cannot mount disk with hammer file system Hi. My first time posting on this list. My problem in a nutshell is I installed dragonfly bsd 2.8 in vmware workstation. I reinstalled the host system that vmware workstation was on and decided on using virtualbox. I imported my dragonfly bsd vmware workstatation vmdk files into virtualbox. Upon boot in virtualbox I run into the problem of mounting the disk. I am prompted at the boot prompt to detect the disk that the system resides on. I have tried hammer:ad0s1, hammer:ad0s1a, hammer:ad0s1d and just ad0s1. I am however not able to boot the system. I have also booted from the live iso image and mounted the system manually into /mnt using mount_hammer /dev/ad0s1a /mnt and took a screenshot of /etc/fstab. I however ask if there is a simple way to fix my mount problem. Any information needed in regards to solving this problem will be gladly appended. *kær kveðju/kind regards,* ** *Úlfar Ellenarson* SAP ráðgjafi / SAP Consultant cid:image001.jpg@01CAE862.EFF59A90 Borgartúni 37 105 Reykjavík, Ísland *T: *+354 563 6226 *E: *u...@applicon.is mailto:h...@applicon.is *W:*www.applicon.is http://www.applicon.is/
Re: How big is fully loaded?
On 17 Feb 2011, at 04:14, Pierre Abbat p...@phma.optus.nu wrote: I was thinking, if I wanted /home to be encrypted, or shared with Linux on the same laptop, or both (LUKS is LUKS, right?), how much disk space should I allocate to everything but /home? Yes, luks on DragonFly should be compatible with linux, except for some less common IV algorithms such as benbi. If you stick to aes and essiv or plain iv it should definitely work. You of course also need an FS that is supported by both linux and DragonFly. I also saw lvm next to cryptsetup. Does it work the same way as in Linux? I've been using lvm since at least 2007. Yes, lvm on DragonFly is compatible with Linux but there are some caveats or rather missing features such as mirroring and snapshots, iirc. What works are linear and striped LVM volumes. Regards, Alex
Re: System has insufficient buffers to rebalance the tree
Around 768MB of RAM needs to be installed in the system for the nbuf message to go away. Regards, Alex On 02/02/11 04:19, Pierre Abbat wrote: On Monday 31 January 2011 16:17:11 Matthew Dillon wrote: It's based on memory size and while it is possible to change it the problem is that your system doesn't have enough memory for what the hammer rebalance code really needs to operate. How much memory does it need to do the hammer rebalance? Pierre
Re: Hammer Benchmark Fun
On 08/01/11 06:12, Siju George wrote: Hi, Some one send this to me http://www.phoronix.com/scan.php?page=articleitem=dragonfly_hammernum=1 [...] http://en.wikipedia.org/wiki/Phoronix_Test_Suite#Controversies While I don't want to get into how useful or useless their tests are, it would have been nice to see those same tests with a different scheduler, to see if it made any impact. Especially in the blogbench case it made a huge difference during my initial testing. Overall I think our I/O performance has improved a lot since previous releases and we are at a comparable level to, at least, other BSDs. All of this is anecdotal evidence and gut feeling of course :) Regards, Alex Hornung
Re: kernel crash
On 07/01/11 09:00, Dragon Fly wrote: Hi, When I try to mount ntfs the system crashes. Here is my last crash log www.pastebin.ca/2040170 I'm always getting a '500 - Internal Server Error' from that link. can you please post it somewhere else? Regards, Alex
Re: Encrypted root questions
Hi Tim, On 20/12/10 03:10, Tim Darby wrote: [...] It issues the kill command but udevd apparently never responds. This might explain why /tmp fails to unmount and also the seg-fault error. I tried editing the rc script to change kill $UDEVD_PID to kill -9 and those messages went away. So what would cause udevd to not respond to SIGTERM? I basically forgot to exit from the SIGTERM handler; I'll fix it ASAP, thanks for reporting it. - What are all these policies it keeps nagging about and should I care? They are the dsched scheduling policy messages. Every time a disk is created/inserted in the system, dsched looks for a scheduling policy for it. Since 'dm' creates virtual disks, these messages will appear for every dm volume created. cryptsetup in particular sets up these temporary volumes mapper/temporary-cryptsetup-N to check that the key is correct, etc. In short: no, you shouldn't care. Regards, Alex
Re: kdebase-workspace4 error gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2
On 14/12/2010 04:44, Siju George wrote: On Mon, Dec 13, 2010 at 5:41 PM, Alex Hornungahorn...@gmail.com wrote: I have answered this question quite often on this mailing list. Kde4 as in pkgsrc doesn't compile on DragonFly. I have submitted patches upstream to kde a few months ago. I searched and got http://leaf.dragonflybsd.org/~alexh/kdebase-workspace4.patch from http://leaf.dragonflybsd.org/mailarchive/users/2010-01/msg00030.html but that patch URL gives http 404 error. Why cant't it be committed directly to the dragonfly-pkgsrc branch? Well I don't know much about this but I thought dragonfly-pkgsrc branch was made just for this? thanks :-) --Siju Try this: http://bugsfiles.kde.org/attachment.cgi?id=50108 Regards, Alex
Re: kdebase-workspace4 error gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2
I have answered this question quite often on this mailing list. Kde4 as in pkgsrc doesn't compile on DragonFly. I have submitted patches upstream to kde a few months ago. If you want a workaround just search for my patches on this ml or on bugs.kde4.org. Regards, Alex On 13 Dec 2010 11:25, Siju George sgeorge...@gmail.com wrote: Hi, on 2.9-DEVELOPMENT DragonFly v2.9.1.183.g32fe4-DEVELOPMENT #5: Tue Dec 7 19:38:14 IST 2010 I get this error during bmake update EP' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:134: error: 'SWAIT' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:135: error: 'SLOCK' was not declared in this scope /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp: In member function 'bool KSysGuard::ProcessesLocal::Private::readProcCmdline(long int, KSysGuard::Process*)': /usr/pkgobj/bootstrap/work/pkgsrc/x11/kdebase-workspace4/work/kdebase-workspace-4.4.5/libs/ksysguard/processcore/processes_freebsd_p.cpp:158: warning: unused variable 'p' gmake[2]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/processes_local_p.o] Error 1 gmake[1]: *** [libs/ksysguard/processcore/CMakeFiles/ksysguardprocesslist_helper.dir/all] Error 2 gmake: *** [all] Error 2 *** Error code 2 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase-workspace4 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/x11/kdebase4 *** Error code 1 thanks --Siju
Re: Encrypted root questions
I'm assuming you are using the 'master' branch, otherwise the
dm_target_crypt_load=YES is not necessary. For whatever it's worth,
I've added a task to google code-in a few weeks ago to document all this
dm stuff, both cryptsetup and lvm, basically. Hopefully there will be a
taker.
For encrypted swap you definitely should be running the 'master' branch,
as the release dm_target_crypt, while it supports it, would have
problems under memory pressure. In any case: to set it up, you'd use the
/etc/crypttab file; just add a line a la:
swap/dev/da0s1bnonenone
or, possibly, setting a keyfile, if that's what you'd like to use, as
the third parameter. Man page should help you out on that. Then just add
the following line to fstab:
/dev/mapper/swapnoneswapsw10
and you'll be all set up.
Regards,
Alex Hornung
On 13/12/2010 06:24, Tim Darby wrote:
I'm trying to set up an encrypted root filesystem with disk A
containing /boot and swap and disk B containing the encrypted root.
Having never done this before, I figured I'd
use /share/examples/rconfig/encrypted_root.sh as a guide. However, I
ran into a couple of snags, so maybe someone can tell me what I'm
doing wrong.
First, this command appears to have a typo:
cryptsetup -y luksFormat /dev/${disk}s1 == shouldn't this be s1d?
Second, in these lines for loader.conf:
dm_load=YES
initrd.img_load=YES
initrd.img_type=md_image
vfs.root.mountfrom=ufs:md0s0
vfs.root.realroot=crypt:hammer:/dev/${disk}s1d:root
This failed for me during boot right after it prompted me for the
passphrase. Eventually, I realized that it was not able to find
dm_target_crypt.ko at the point where it was trying to open the
encrypted filesytem and I was only able to get the machine to
successfully boot all the way by adding the line:
dm_target_crypt_load=YES
I'm also interested in encrypted swap. Is there anything tricky about
setting that up?
Thanks,
Tim
Re: Device fd0
On 29/11/2010 19:00, Clark Chapman wrote: When I try to access the floppy drive I get a kernel panic. For example fdformat /dev/fd0.1440 I am running release 2.8.2. There was no problem with 2.6. I tried changing the drive and the cable but that made no difference. Thanks You need to provide more information, such as, at least, the backtrace of the panic. Ideally even a kgdb backtrace of a kernel core (or simply the core.txt.N). Regards, Alex
Re: /var/vkernel/boot/kernel -my -params permission denied
On 26/11/2010 16:00, Nikolai Lifanov wrote: Hello. I just installed a new 2.8.2 system, upgraded it to 2.9.x, and compiled a VKERNEL64. However, when I try to boot it, I get a Permission denied. error. This is the first for me; I did the obvious of chmodding it to +x, but I'm at a loss here. Did something change? How should I proceed? Did you enable the vkernel sysctl? Cheers, Alex
Re: Printer Daemon (Update)
On 25/11/2010 16:35, Tim Darby wrote: - Just to satisfy my own curiosity about the code: how does lpr.c eventually get to unp_connect()? I followed it as far as connect() in startdaemon.c and then lost the trail. I haven't really followed this thread, but to answer this question: connect - sys_connect - ... - some routine eventually sends an lwkt message to the protocol handler for connect, which for this case will be unp_connect() Cheers, Alex Hornung
Re: gupnp-simple-igd.c:290: error: 'AF_INET6' undeclared (first use in this function) for pkgsrc dragonfly-2010Q3 pidgin
Some extra info on the issue, since I just ran into the same problem building 'empathy': 6:28:00 alex-laptop:/usr/pkgsrc/net/gupnp-igd dragonfly-2010Q3 # grep -R socket\.h * Binary file work/.buildlink/lib/libdbus-1.a matches Binary file work/.buildlink/lib/libproxy.so.0 matches Binary file work/.buildlink/lib/libproxy.a matches Binary file work/.buildlink/lib/libproxy.so.0.0.0 matches Binary file work/.buildlink/lib/libproxy.so matches work/.buildlink/.buildlink_glib2_done:/usr/pkg/include/glib/glib-2.0/gio/gsocket.h work/.buildlink/.buildlink_libsoup24_done:/usr/pkg/include/libsoup-2.4/libsoup/soup-socket.h work/.buildlink/include/gcrypt.h:# include sys/socket.h work/.buildlink/include/libsoup-2.4/libsoup/soup-portability.h:#include sys/socket.h work/.buildlink/include/libsoup-2.4/libsoup/soup-enum-types.h:/* enumerations from soup-socket.h */ work/.buildlink/include/libsoup-2.4/libsoup/soup.h:#include libsoup/soup-socket.h work/.buildlink/include/glib/glib-2.0/gio/gsocketconnection.h:#include gio/gsocket.h work/.buildlink/include/glib/glib-2.0/gio/gio.h:#include gio/gsocket.h work/.buildlink/include/python2.6/pyconfig.h:/* struct sockaddr_storage (sys/socket.h) */ work/.buildlink/include/python2.6/pyconfig.h:/* Define to 1 if you have the sys/socket.h header file. */ work/.buildlink/include/python2.6/pyconfig.h:/* Define to `int' if sys/socket.h does not define. * On 11/08/10 08:41, Siju George wrote: Hi, Compiling for pidgin on 2.9 dragonfly-2010Q3 I get the following error === === Building for gupnp-igd-0.1.7 /usr/pkg/bin/gmake all-recursive gmake[1]: Entering directory `/usr/pkgobj/bootstrap/work/pkgsrc/net/gupnp-igd/work/gupnp-igd-0.1.7' Making all in libgupnp-igd gmake[2]: Entering directory `/usr/pkgobj/bootstrap/work/pkgsrc/net/gupnp-igd/work/gupnp-igd-0.1.7/libgupnp-igd' echo #include \glib-object.h\ gupnp-simple-igd-marshal.c.tmp echo #include \gupnp-simple-igd-marshal.h\ gupnp-simple-igd-marshal.c.tmp glib-genmarshal --body --prefix=_gupnp_simple_igd_marshal ./gupnp-simple-igd-marshal.list gupnp-simple-igd-marshal.c.tmp mv gupnp-simple-igd-marshal.c.tmp gupnp-simple-igd-marshal.c glib-genmarshal --header --prefix=_gupnp_simple_igd_marshal ./gupnp-simple-igd-marshal.list gupnp-simple-igd-marshal.h.tmp mv gupnp-simple-igd-marshal.h.tmp gupnp-simple-igd-marshal.h /usr/pkg/bin/gmake all-am gmake[3]: Entering directory `/usr/pkgobj/bootstrap/work/pkgsrc/net/gupnp-igd/work/gupnp-igd-0.1.7/libgupnp-igd' CC gupnp-simple-igd.lo gupnp-simple-igd.c: In function 'validate_ip_address': gupnp-simple-igd.c:287: error: 'AF_INET' undeclared (first use in this function) gupnp-simple-igd.c:287: error: (Each undeclared identifier is reported only once gupnp-simple-igd.c:287: error: for each function it appears in.) gupnp-simple-igd.c:290: error: 'AF_INET6' undeclared (first use in this function) gmake[3]: *** [gupnp-simple-igd.lo] Error 1 gmake[3]: Leaving directory `/usr/pkgobj/bootstrap/work/pkgsrc/net/gupnp-igd/work/gupnp-igd-0.1.7/libgupnp-igd' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/pkgobj/bootstrap/work/pkgsrc/net/gupnp-igd/work/gupnp-igd-0.1.7/libgupnp-igd' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/pkgobj/bootstrap/work/pkgsrc/net/gupnp-igd/work/gupnp-igd-0.1.7' gmake: *** [all] Error 2 *** Error code 2 Stop. bmake: stopped in /usr/pkgsrc/net/gupnp-igd *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/net/gupnp-igd *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/multimedia/farsight2 *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc/chat/pidgin dfly-vmsrv# == What could be the problem? thanks --Siju
Re: How to test and debug Dragonfly BSD?
Hi Marcin, first off I'd recommend you join the IRC channel on efnet, #dragonflybsd. Most committers hang out there and it's the easiest way to get some initial help (and probably any help). There are a number of solutions that people use to develop DragonFly, ranging from purely virtual using VMWare, VirtualBox or kvm/qemu (kqemu?) to dedicated physical test machines. I personally have an installation on my laptop and also develop using VMWare on my desktop. As someone already mentioned, DragonFly offers vkernels which are a nice way to develop kernel stuff without any complications as machines not booting, etc... everything except hardware drivers, of course. Debugging of kernel issues usually occurs via a kernel core dump or, sometimes, by debugging a vkernel with gdb. Hope that helps, Alex Hornung On 8 November 2010 20:07, Marcin Ropa marcinr...@gmail.com wrote: Hello, A few weeks ago I decided to spend my free time working on dfbsd and i started digging in code. I have experience as developer but there everything is new for me and probably I will have to spend many time before i will be helpful for the project. :) I have my first question.: How do you organize your work on DragonFly BSD? I am not going to ask you about your editor but how do you run, test and debug your code. Do you use VirtualBox, qemu or seperate machine? Does VirtualBox run on dfbsd or you run VirtualBox on another system, e.g.: FreeBSD and this is your development platform? I know you are busy, but if you find time please give me some hints how to organize work on operating system. thanks a lot and Greeting Marcin
Re: hammering the drive
On 21/10/10 04:44, Pierre Abbat wrote: I clicked on the tabs of a Firefox window I have up, and it responded very slowly. I can't say much about the wear and tear of the drive. Regarding the unresponsiveness when Hammmer functions are running I'd suggest you give dsched_fq a try, the fair-queuing disk scheduling policy. It should improve interactivity during heavy I/O. Regards, Alex Hornung
Re: hammering the drive
On 21/10/10 11:05, Pierre Abbat wrote: dogla# dschedctl -l dschedctl: open(/dev/dsched): No such file or directory Am I missing something? Yes. dschedctl doesn't exist anymore. Please take a look at the manpage. The right way to do it now is via sysctl. Regards, Alex
Re: No package installation method works
On 20/10/10 20:54, Torbjorn Granlund wrote: Method 3 (from docs/handbook/handbook-pkgsrc-sourcetree-using/): # cd /usr # cvs -d anon...@anoncvs.us.netbsd.org:/cvsroot co pkgsrc # cd shells/bash # make Use bmake for this as outlined in http://www.dragonflybsd.org/docs/howtos/HowToPkgsrc/. About method 2: use pkgsrc2.git not pkgsrc.git About method 1: no idea, not a heavy binary package user. Kind Regards, Alex Hornung
Re: mount question
Hi Andrei, BSDs use disklabels on top of what one calls partitions. DragonFly in particular uses disklabel64 which Linux has no support for as far as I know. So the structure would be: --- | Partition | -- | | disklabel partition | | | -- | | disklabel partition | | | -- --- | Partition | Kind regards, Alex Hornung On 12/10/2010 11:02, Andrei Lomov wrote: I had installed DragonFly 2.6.3 on 40Gb IDE ATA slave drive (on second (ATA) controller) During DragonFly installation it ask to set ufs instead of hummer (in view of lesser 50 Gb drive space) and I agree. I don't install any bsd boot loaders preferring to setup lilo. In linux fdisk, bsd partition looks fine: # fdisk /dev/hdb ... Disk /dev/hdb: 40.0 GB, 40020664320 bytes 256 heads, 63 sectors/track, 4846 cylinders Units = cylinders of 16128 * 512 = 8257536 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/hdb1 * 1484639078112+ a5 FreeBSD To configure lilo I try to mount bsd partition from linux but it fails: # mount -t ufs -o ufstype=44bsd /dev/hdb1 bsd mount: wrong fs type, bad option, bad superblock on /dev/hdb1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so I'm newbie in bsd and need an advice Thanks in advance -- Andrei
Re: KDE 3 and 4 in recent pkgsrc
On 10/10/2010 11:40, Francois Tigeot wrote: Both are in -head; you can choose one or the other. I'm not sure kde4 is fully complete though. KDE4 doesn't compile out of the box. A few months ago I submitted 4 patches upstream to KDE to fix it, but only one has been merged so far. KDE people seem relly slow in that regard. Regards, Alex Hornung
Re: FreeBSD isn't Free - Does this affect DragonFLY?
On 07/10/2010 11:41, Siju George wrote: Hi, http://marc.info/?l=openbsd-miscm=128634319422034w=2 http://marc.info/?l=openbsd-miscm=128639321930440w=2 http://www.listware.net/201010/freebsd-questions/18454-like-it-or-not-theo-has-a-point-freebsd-is-shipping-export-restricted-software-in-the-core.html Thanks --Siju We have the same acpica (with the same terms, etc), if that's the question. Kind Regards, Alex Hornung
Re: Misleading directory names
On 28/09/10 11:44, Przemysław Pawełczyk wrote: A real example - I installed DFBSD and I wanted to have some applications too. I went to the page: http://www.dragonflybsd.org/docs/howtos/HowToPkgsrc/#index4h2 There is setenv PKG_PATH .../i386/... defining the path to packages' database. For whatever it's worth, if you just mentioned the actual problem first instead of criticizing that there are two different directories for the same architecture on a mirror, your criticism/comments would be very useful from the start. I much appreciate that you let us know which issues you find but raising the actual issue instead of talking around it and only getting to it 3 mails later isn't as useful as it could be. Regards, Alex
Re: Linuxulator question
On 25/09/10 15:52, Tim Darby wrote: What's the status of the Linuxulator? I saw that Alex put a lot of work into it, so is it basically done and just needs testers? Linuxulator works quite nicely on x86; at least Java works and as far as I know Flash, too. On x86_64 there is no linuxulator at all. There was someone who started porting it to that platform, but as far as I know there's nothing to show for it. Personally I'd like to see it ported to x86_64 but I don't have the time. If anyone wants to volunteer, he can count on my support. Cheers, Alex Hornung
Re: make installkernel error You need to install a new /boot before you can install a new kernel, kernels are now installed
No, only the first time to update to the new loader (dloader). After doing it once you can do the usual buildworld buildkernel installkernel installworld. Cheers, Alex On 24 September 2010 08:12, Siju George sgeorge...@gmail.com wrote: On Fri, Sep 24, 2010 at 12:37 PM, Matthew Dillon dil...@apollo.backplane.com wrote: :How do I fix this? : :thanks : :--Siju buildworld / installworld first, then buildkernel / installkernel. Thanks :-) Is that going to be order from now on? --Siju
Re: Weird entry in ISO
On 24/09/10 13:37, Przemysław Pawełczyk wrote: I know, and I would expect such answer. No offense please, but for how long yet such attitude will prevail in Unix community? It lingers from 80s of the last... Cenury of the last Millennium. ;-) Sorry, but I simply fail to see why we need 'mc' and 'lynx' in base. If someone can't use the standard unix commands, he should possibly learn before using a unix system. In any case, you are free to install whatever software you want/need, and that's the main reason why we don't 'need' to ship 'mc', 'lynx' and similar stuff. Regarding your pkg_radd problem, just use pkg_radd -f. You just have the wrong package repo or so in use. Regards, Alex
Re: Looking for some programming tasks to do
On 24/09/10 13:56, elekktrett...@exemail.com.au wrote: Please don't use C++ arbitrarily. C will do fine for all those projects as far as I can tell and is the preferred way. Even for userland? Petr I am talking about userland; yes. Unless you have a compelling reason to do something in C++, please refrain from doing so. Regards, Alex
Re: OpenOffice
On 30/08/2010 13:41, Pierre Abbat wrote: ... How do I fix this? openoffice-setup, mentioned in handbook-desktop-productivity, does not exist. I ran pango-querymodules but still got the error. For whatever it's worth, I recently (~2 weeks ago) installed openoffice from /usr/pkgsrc (openoffice3-bin, iirc) and it worked just fine. Cheers, Alex
Re: Utility to list /dev/nodes serno's
For whatever it's worth it would also be possible to use libdevattr, which offers a fairly easy way to query for all disk devices and get additional information such as serial number, device path, disk type (optical, floppy, raid, ...). This approach might require that the serial number is added to the udev device dictionary in subr_disk.c as soon as the serno becomes available, but it is a more flexible approach and definitely better than adding another ioctl. Cheers, Alex Hornung On 06/08/10 21:27, Matthew Dillon wrote: :Hi people, : :is there a way to easily list all disks and their associated serno's ? :Something like 'blkid' utility of Linux, if you happen to know it. :I could happily hack something like that, if we lack it. : : :Cheers, :Stathis There isn't, and that would be cool. It is fairly easy to match up device numbers from devfs. You can use sysctl kern.disks output to get a list of disk devices, then you can scan /dev and pick those base names out and stat them, and you can scan /dev/serno and stat those babies and match up the st_rdev's with the ones from /dev to getting related serial numbers. If we wanted to get more involved we could add an ioctl() to retrieve the serial number (if available), but it can definitely be scripted right now without that. -Matt Matthew Dillon dil...@backplane.com
Re: Is it time to dump disklabel and use GPT instead?
On 28/07/10 03:30, Adam Vande More wrote: [...] although I am curious to know why GEOM wasn't chosen. It's both more powerful, and easier to use IMO. Some examples of that would be gmirror, glabel, gstripe, HAST, etc -- all easier than the Linux equivalents. The mdadm stuff is reliable, but a real PITA. For me anyways, including more GPL tools is a turnoff. This is getting hugely off-topic, but here go my reasons for preferring to stay away from geom. Just a side note first: mdadm and md-raid do not use device mapper, they use their own in-kernel stuff. Now my opinion on why geom is not the way to go but dm is can be summarized in the following points: - geom is NOT easier to use from a developer's perspective. Device Mapper targets are, imo, much easier to write. - geom forces all the I/O onto one (or two?) threads that transport it across a hugely complicated system. IMO this won't scale well in the future, when the bottleneck moves away from the disks (as already is starting to be the case with SSDs) - We don't need to reinvent the wheel. We have good MBR, disklabel and decent but improvable GPT support already in our disk subsystem. - geom wants to do everything in kernel-land while device mapper devices usually rely on a userland configuration program that reads and parses metadata. This is *much* more flexible than having to implement huge parsers in kernel-land, such as the one required for lvm, just to name one. - Device Mapper offers compatibility with Linux, the most used non-windows operating system afaik. And as a matter of fact we were talking about Linux users here, so they would definitely have much more issues with geom. [...] If GEOM where to be completed, gpart should be useable too then only the boot bits need to be solved. We already have GPT support in the kernel, and gpart would offer no advantage that I know of. The support everyone else is talking about is GPT support in the loader. Cheers, Alex Hornung
Re: DragonflyBSD GEOM? (Re: Is it time to dump disklabel and use GPT instead?)
On 28 July 2010 17:14, Adam Vande More amvandem...@gmail.com wrote: [...] Well it's 3 main actually(up, down, and event threads basically), and depending on the module you can spawn other kernel threads to handle asynchronous stuff to pass off when it's ready. The design has awfully nice performance characteristics like there is a centralized place for bio stuff, optimization would seem to be much easier to implement. You can see evidence of this when using something like gjournal. On gjournaled device, single threaded IO takes a big hit putting it in the Linux realm of performance, however as the threads grow, so does the ability to optimize requests being sent to physical devices. That's why gjournal devices scale so much better as concurrency grows. I have not observed any performance bottlenecks on my GEOM ssd devices and I have no idea what a theoretical or real-world maximum would be on the GEOM design. I absolutely don't see how forcing the I/O from N different threads onto 2 (events are not I/O effectively) is better than having each I/O maintain (mostly) it's own context. Your particular case may not suffer from any performance impact, but I was mostly talking about a future-proof solution. [...] Are you taking about the g_linux_lvm module? I would not consider that huge ~1200 lines. That's tiny compared to what you had to go through to import. Now let's see you write an io scheduler for the new devices. See my point? I mean every module that needs metadata. From the top of my head I could mention the lvm parser and geli, but I'd suspect most others, too. So GEOM has a lvm parser that is utterly incomplete and obviously offers no management whatsoever. How is that superior to having most of the lvm functionality (in userland), easy to keep up to date and offering the same tools as on Linux? In any case this is not about LVM vs geom since LVM is only one consumer of the device mapper. Now let's see... you write an I/O scheduler on DragonFly... you simply use the dsched framework which fits nicely on top of the disk subsystem. As a matter of fact I could even change dm slightly to use the disk subsystem, too, and hence allow I/O schedulers, mbr, gpt and disklabels on top of dm devices, but I don't think there's much point to it at this time. [...] Perhap they would, hard to say though. If someone is able to learn LVM/DM stuff though, they certainly would be able to GEOM. LVM does have a few advantages over GEOM like being able to resize on the fly, but that functionality does not work here. My point is that there's no need to learn anything new. Also, this is completely subjetive. Maybe you prefer GEOM; I'd argue some of the Linux counterparts are way more intuitive. LVM is only one consumer of device mapper as I said before, so there's really no point in doing this comparison. LVM was imported strictly because of the compatibility with Linux. cryptsetup is another consumer of device mapper, which offers a different interface. My point here is that it's extremely simple to write userland tools to fit anyone's needs. I'm currently working on a mirror target for the device mapper; it'll also have its own userland tool, and not dependent on LVM which you seem to find cumbersome. [...] I know of the differences I guess I didn't relay my whole thought here. gpart was brought up because it's a geom class, and it does have more functionality than the existing D_BSD support(the man page notes there is much to be done). My point is that loader support would also be easier to import if it had the same target, the geom_part_gpt class. I still don't get your point. GPT support in the loader is not assisted in any way by geom or any other similar mess. Cheers, Alex Hornung
Re: DragonflyBSD GEOM? (Re: Is it time to dump disklabel and use GPT instead?)
On 28/07/10 21:58, Adam Vande More wrote: [...] It's not just that combination though. HammerFS could be used on other modules like gvinum, gconcat, etc, etc. I'm interested in using Dragonfly for some embedded system, but having more GPL stuff is essentially a non-starter for me as well. I really like HammerFS and would have preferred to see that in FreeBSD over ZFS. Just use vinum. It has been there forever and will provide the features you seem to be interested in without the GPL burden. I absolutely fail to see any of your points in why we would want to have geom and I would definitely not welcome having it, for whatever it's worth. If GPL stuff is a non-starter for you, as you put it, then gcc should pose a problem to you as well... Regards, Alex Hornung
HEADS UP: dm, lvm, cryptsetup and initrd on master
Hi, as you know I've been working on getting dm and lvm into DragonFly. I've just committed my work so far which includes the following: - dm kernel part (including linear, stripe and crypt targets) - dm userland library - lvm userland tools - cryptsetup (with LUKS stuff) - some further modifications to the initrd stuff First off, note that this is rather a HEADS DOWN notice; the stuff should be considered experimental. It has proven safe and reliable in my tests, but that does not mean that it's bug/problem-free. The dm kernel part, ported from NetBSD, is compiled by default as a module now and can be compiled into the kernel, as usual, in the kernel config. The port from NetBSD includes a linear and stripe target; on top of that I've also written a crypt target which aims to be (mostly) compatible with cryptsetup. I've not actually tried reading a dm-crypt (linux) volume with my crypto implementation, but volumes created from scratch with cryptsetup on DragonFly work as expected. I'd definitely welcome some more testing of the crypt target as it is definitely the target that has had less testing, since it doesn't exist in NetBSD. Next I'll start working on a mirror target so vinum isn't our only choice anymore for software RAID1. The dm/lvm userland tools (basically dmsetup and lvm) offer a set of tools to manage general dm volumes and in case of lvm, specifically lvm volumes. I've tried with several LVM volumes and everything seems to work just fine. An rc script for lvm is also included so that lvm volumes are automatically discovered on boot. You just need to set lvm_enabled=YES (or lvm=YES) in rc.conf, as usual. Note that the lvm rc script also needs udevd, but I think that dependency would be enabled automatically. Now comes the interesting part: using crypt or lvm volumes as root device. And this is where mkinitrd comes in. As the mkinitrd(8) man page explains, mkinitrd creates an md image that can be used as an early root, much like linux' initrd/initramfs. This initrd has a tiny /sbin/init as well as a set of rc scripts that are run. To enable the use of initrd, one has to create an initrd image with mkinitrd, add the tunables as explained in mkinitrd(8) to loader.conf to preload the initrd.img in /boot, and adjust vfs.root.mountfrom to ufs:md0s0. By default, the initrd image also runs a discovery of lvm volumes prior to mounting the real root device. The initrd image reads the loader tunable vfs.root.realroot (via a sysctl) to identify from which device and how to mount the actual root device. Right now the initrd system supports two types of 'realroot': 'crypt' and 'local', which are specified with all their options in mkinitrd(8), too, but here are two examples: vfs.root.realroot=local:ufs:/dev/vg00/lv0 vfs.root.realroot=crypt:ufs:/dev/ad0s0a:foocrypt The first one tells initrd to mount a local file system, of type ufs, from /dev/vg00/lv0. This is alright, since the lvm discovery is run by default prior to reading and interpreting the realroot setting. The second one tells initrd to launch the rcmount_crypt script on the image, which basically will set up the crypt volume that is supposed to be on /dev/ad0s0a as volume 'foocrypt' (or rather: /dev/mapper/foocrypt). cryptsetup will then (probably) ask for a key and set up the volume so it is ready for mounting. Afterwards, knowing that the system is a ufs file system, it will mount /dev/mapper/foocrypt as a ufs file system as the now root device. After this initialization sequence has run, the initrd init will take back control, switch the root and pass control to the /sbin/init on the real root device, and everything will (hopefully) work as expected. If you care about the details of how this works, here it goes: the /sbin/init on the initrd will chroot into /new_root (which is the mount point of the new root, as the name gives away) and also issue a system call to chroot_kernel, which will then set the 'rootnch' and 'rootvnode' globals in the kernel to the /new_root nch and vnode entries. After this process, the initrd init will execv into the actual /sbin/init. I'd like to note here that I see also other possible use cases for the initrd image; it can be used to configure any complicated root device without having to write complicated kernel code to handle it. An ISCSI target root should be easily achievable with this approach just to name one further possibility. The whole process is not without its drawbacks: since the md image is preloaded by the loader, there is no way of freeing up the memory used by it (15MB currently, but could be shrunk to 7 or 8 MB). Ideally we would want an initrd image that can be completely freed after using it to reclaim any otherwise wasted memory. Cheers, Alex Hornung
Re: paraphysics down
Try one of the other efnet servers, there are plenty. And the channel is called #dragonflybsd. Cheers, Alex On 3 May 2010 13:53, Pierre Abbat p...@phma.optus.nu wrote: I just brought up my IRC client and am getting this error trying to connect to the server hosting #dragonfly: [08:47] [Info] Server found, connecting... [08:47] [Error] Connection to Server irc.paraphysics.net lost: no error. Trying to reconnect. [08:47] [Info] Looking for server irc.paraphysics.net:6667... [08:47] [Info] Server found, connecting... [08:47] [Error] Connection to Server irc.paraphysics.net lost: network failure occurred. Trying to reconnect. [08:47] [Info] Looking for server irc.paraphysics.net:6667... [08:47] [Info] Server found, connecting... Pierre -- .i toljundi do .ibabo mi'afra tu'a do .ibabo damba do .ibabo do jinga .icu'u la ma'atman.
RE: Insufficients buffers for rebalance
: I get this with even 512MB of ram, as it does not seem to be : something we need people to worry about can we subdue the message : unless vfs.hammer.debug.general is 0x0080?? FWIW, I had a VM with 512MB RAM showing exactly the same message. Bumping it to 1 GB did the trick for me. Of course that's a bit trickier for physical machines :) Cheers, Alex Hornung
RE: make buildworld error: field 'sysctl_ctx' has incomplete type
I'm aware of this issue and currently trying out a fix. Cheers, Alex Hornung : -Original Message- : From: users-err...@crater.dragonflybsd.org [mailto:users- : err...@crater.dragonflybsd.org] On Behalf Of Siju George : Sent: 26 April 2010 08:54 : To: users@crater.dragonflybsd.org : Subject: make buildworld error: field 'sysctl_ctx' has incomplete type : : Hi, : : My Dragonfly system ( 2.7-DEVELOPMENT DragonFly : v2.7.0.54.g0754fe-DEVELOPMENT #18: Wed Apr 7 10:09:21 IST 2010 ) : paniced and dropped to ddb prompt with some hammer ioctl error in : the morning. I rebooted it thinking I will get the error in the logs : but it iwas not there in 'messages' or 'dmesg'. : : So Thinking there is something wrong with this development version I : tried to upgrade. : : dfly-bkpsrv# git describe : v2.7.2-62-g907aee5 : : but got this error during : : #make buildworld : : : === usr.bin/kdump : cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace : -I/usr/src/usr.bin/kdump -I/usr/src/usr.bin/kdump/../.. : -I/usr/src/usr.bin/kdump/../../sys -Wsystem-headers -Werror -Wall -W : -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes : -Wpointer-arith -Wold-style-definition -Wreturn-type -Wcast-qual : -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter : -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c : /usr/src/usr.bin/kdump/kdump.c : cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace : -I/usr/src/usr.bin/kdump -I/usr/src/usr.bin/kdump/../.. : -I/usr/src/usr.bin/kdump/../../sys -Wsystem-headers -Werror -Wall -W : -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes : -Wpointer-arith -Wold-style-definition -Wreturn-type -Wcast-qual : -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter : -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c : ioctl.c : In file included from ioctl.c:108: : /usr/src/usr.bin/kdump/../../sys/sys/dsched.h:112: error: field : 'sysctl_ctx' has incomplete type : *** Error code 1 : : Stop in /usr/src/usr.bin/kdump. : *** Error code 1 : : Stop in /usr/src/usr.bin. : *** Error code 1 : : Stop in /usr/src. : *** Error code 1 : : Stop in /usr/src. : *** Error code 1 : : Stop in /usr/src. : You have new mail. : : Thanks : : --Siju
RE: make buildworld error: field 'sysctl_ctx' has incomplete type
: My Dragonfly system ( 2.7-DEVELOPMENT DragonFly : v2.7.0.54.g0754fe-DEVELOPMENT #18: Wed Apr 7 10:09:21 IST 2010 ) : paniced and dropped to ddb prompt with some hammer ioctl error in : the morning. I rebooted it thinking I will get the error in the logs : but it iwas not there in 'messages' or 'dmesg'. On another note it would be more useful if you could type 'call dumpsys' whenever you are dropped to the ddb prompt, so that we can take a look at the issue. Cheers, Alex Hornung
RE: make buildworld error: field 'sysctl_ctx' has incomplete type
: /usr/src/usr.bin/kdump/../../sys/sys/dsched.h:112: error: field : 'sysctl_ctx' has incomplete type : *** Error code 1 This issue is fixed in commit 22befd90ce33cce626d1b4c5eafca9bc2770ceea[1]. Cheers, Alex Hornung [1]: http://gitweb.dragonflybsd.org/dragonfly.git/commit/22befd90ce33cce626d1b4c5 eafca9bc2770ceea
HEADS UP: tunables for dsched have changed, serno support
Hi all, Just a short heads-up: I've just committed another change to the loader tunables for dsched. They now are named dsched.* instead of kern.dsched.*. This is to use the same namespace as the dsched sysctl tree. Dsched now also support sernos, e.g.: dsched.policy.WD19339191 = fq Cheers, Alex Hornung
RE: page fault while installer exits setup and umounts
: A page fault is encountered when the installer exits the setup : and umounts. This has already been mentioned in the bug tracker; please update that ticket. Cheers, Alex Hornung
RE: installer crash while configuring interface nfe0
: The installer crashes while trying to configure 'nfe0' interface : using DHCP. All the user settings are destroyed This has also been reported already, so again, please update that ticket. Thanks, Alex Hornung
RE: DragonFly main rsync mirror (chlamydia) DOWN
: Who will fix the images not being displayed in : : http://www.dragonflybsd.org/docs/handbook/handbook-InstallFirstSteps/ I'm currently redoing the handbook, see [1] for WIP. It's only the first 10 chapters so far, and there are still a few TODOs in the wiki markup (look for !-- XXX foo --) and overall the format isn't quite as nice as I'd like to. Cheers, Alex Hornung [1]: http://www.dragonflybsd.org/docs/newhandbook/?updated : -Original Message- : From: users-err...@crater.dragonflybsd.org [mailto:users- : err...@crater.dragonflybsd.org] On Behalf Of Siju George : Sent: 18 March 2010 21:03 : To: users@crater.dragonflybsd.org : Subject: Re: DragonFly main rsync mirror (chlamydia) DOWN : : On Wed, Mar 17, 2010 at 8:11 PM, Antonio Huete Jimenez : ahuete.de...@gmail.com wrote: : Thanks for reporting that Saifi. It's fixed now :) : : : : ;-) : : thanks : : --Siju
linuxulator update
Hi all, As you may already know, I've been working on an extensive update of our linux emulation layer over the past week. Just now I've committed this update and you can expect it to make it into the 2.6 release. I've tested it with Apache Tomcat 6, Java, Opera and Acrobat Reader, but I would welcome more testing; as a matter of fact, as much testing as possible so we can take care of possible issues before the release. While I also tried getting Flash running, there still seems to be an issue with it. Given my little familiarity with Flash, I'd appreciate some insight on this. I've tried it also with the standalone player of flash9 and a local .swf, but the problem remains; the swf doesn't seem to get loaded. The browser plugin says movie not loaded when doing right click on it. Over the next few months I'll slowly clean up the code a bit more, breaking out machine independent bits from sys/emulation/linux/i386 and organizing header files better, to make it easier to port to amd64 eventually. This is of no priority to me, so if anyone wants to get this working soon, they can work on it. Of course, feel free to contact me if you have any queries about this or anything else regarding the linuxulator. Regards, Alex Hornung
RE: Fatal trap 12 during bootup on Dell Cpt with acpi enabled
: I was experimenting with the latest Dragonfly build on a spare Dell Cpt : laptop. If you boot with acpi enabled, you get a kernel fault right : after it outputs ata0: ATA channel 0 on atapci0 Could you please start up without acpi loaded, and then try loading acpi later with kldload and see if that panics, too? If so, try and get a dump by writing 'call dumpsys' at the ddb prompt. Once you have the dump, when you reboot again (without acpi loaded, so it doesn't panic), the dump will be written to /var/crash. If you can then upload that dump somewhere, someone might be able to figure out what the problem is. Cheers, Alex Hornung
RE: /compat/linux/dev/null
You should be mounting devfs in that directory. For convenience you can use a null mount to achieve that. Also, I'm currently working on a huge update of linuxulator, so if it doesn't work, it might well be worth waiting a while or so for me to commit the whole mess. Cheers, Alex : -Original Message- : From: users-err...@crater.dragonflybsd.org [mailto:users- : err...@crater.dragonflybsd.org] On Behalf Of Pierre Abbat : Sent: 08 March 2010 11:59 : To: users@crater.dragonflybsd.org : Subject: /compat/linux/dev/null : : I'm trying to get OpenOffice to run. It was giving a permission error : on /dev/null. Since it's a Linux binary, I checked the one in : /compat/linux, : and found that it was writable only by root. It appears to be a regular : file, : rather than a character device. All other files in /compat/linux/dev/ : are : symlinks. Why isn't null? : : Pierre : -- : When a barnacle settles down, its brain disintegrates. : Já não percebe nada, já não percebe nada.
RE: /compat/linux/dev/null
: Hm, there's an hda in there; DFly calls that ad0 (although the hda is a : symlink to a nonexistent wd0d). If the point is to have something called hda, linking to ad0, you can do exactly that, link it. : Great! I look forward to it. Could you include sed and awk in one of : the suse : packages? They are needed to run ltp. I'm already running LTP using a gentoo stage3 base, which includes everything to both build and run LTP. Cheers, Alex Hornung
RE: kde-workspace4 on DragonFly
: I've been trying to update my workstation to kde4 but the last package : kde-workspace4 fails to build with this error: : : http://avalon.dragonflybsd.org/reports/20091123.0451/kdebase- : workspace4-4.3.1/build.log : : Is this difficult to fix? : : Thanks, : Petr Absolutely not and I already submitted a patch[1] to Hasso a few months ago (~ September). Don't know what happened to it. For the time being, just apply the patch and be happy :) It would be good if someone could make sure that this patch *REALLY* makes its way upstream now, as I don't have the time right now to follow up on this. Cheers, Alex Hornung [1]: http://leaf.dragonflybsd.org/~alexh/kdebase-workspace4.patch
Re: linux syscall madvise
Sure, but point is that this won't fix much. You can, if you want to, submit a patch with the relevant code, it's straight forward. Main aim still remains to get LTP running, so all missing syscalls, most of them way more important than madvise, can be identified. Thanks for your effort, Alex Hornung 2010/1/5 Pierre Abbat p...@phma.optus.nu: On Tuesday 05 January 2010 12:56:43 Alex Hornung wrote: madvise is of no real relevance and is normally not a big deal either. Implementing an empty dummy function will work perfectly fine as it isn't required to do anything. True, but there is a madvise in DFly, so the Linux call can be implemented as the DFly call for the functions they both have, and dummy for the rest. Pierre -- .i toljundi do .ibabo mi'afra tu'a do .ibabo damba do .ibabo do jinga .icu'u la ma'atman.
Re: linux syscall madvise
madvise is of no real relevance and is normally not a big deal either. Implementing an empty dummy function will work perfectly fine as it isn't required to do anything. Cheers, Alex Hornung 2010/1/4 Pierre Abbat p...@phma.optus.nu: I haven't managed to get ltp running, but I have run some Linux programs. I get this message in dmesg: linux: syscall madvise is obsoleted or not implemented This call is used to tell the kernel what the program plans to do with a region of memory. Values used in Linux but not BSD, according to the man pages, are: MADV_REMOVE: seems to mean the same as MADV_FREE MADV_DONTFORK: when fork() is next called, the child will not inherit the memory MADV_DOFORK: opposite of MADV_DONTFORK Pierre -- li ze te'a ci vu'u ci bi'e te'a mu du li ci su'i ze te'a mu bi'e vu'u ci
Re: tried to run ltp
Didn't get anywhere near trying to test the Linux ABI. How do I get around the missing programs and /proc/cpuinfo? Am not quite sure about the programs, but mounting linprocfs should do the trick for /proc.
Re: packages not available as binaries, encountered when installing kdevelop
Niklasro is a bot with A.I. (see http://niklasro.appspot.com) and it is about time that we ban it from the mailing lists as it is always spamming with useless crap and confusing people.
Re: pkgsrc-current DragonFly 2.4.1/i386 2009-12-19 18:02
Packages breaking the most other packages Package Breaks Maintainer - www/php4 82 jdole...@netbsd.org devel/boost-libs 49 j...@netbsd.org lang/kaffe 44 to...@netbsd.org x11/gtkmm 28 a...@netbsd.org multimedia/py-gstreamer0.10 21 pkgsrc-us...@netbsd.org wm/metacity 13 pkgsrc-us...@netbsd.org x11/py-gnome2-desktop 9 pkgsrc-us...@netbsd.org security/xmlsec1 8 pkgsrc-us...@netbsd.org lang/sun-jre14 8 pkgsrc-us...@netbsd.org lang/sun-jre15 7 pkgsrc-us...@netbsd.org First off, thanks for the continous effort on building pkgsrc packages! Now as you said on your blog, bost-libs is fixed, and as a matter of fact so should wm/metacity by the signal code changes, and especially the introduction of the CLD_EXITED #define. xmlsec1 seems to try to find libdl. This should be fixable; anyone got more insight and some time to fix that? Then some seem to have trouble finding python libs. Does anyone have any insight on that? Cheers, Alex Hornung
Re: Updating USB stack from FBSD 8.x and others
I've suggested this a long time ago, and I've also provided some people with guidance on how to do it, as I've been in contact with the HPS, the author of usb4bsd. The main point here is that his i4b repo contains usb4bsd and a userland wrapper for it. Hence usb4bsd can be elegantly ported to dragonfly by modifying as little as possible from the real code and just wrapping it around as his userland wrapper shows. Any attempt to port this should be aiming for this solution so to avoid a huge mess and keep the code maintainable. Cheers, Alex Hornung 2009/12/12 Alexander Polakov polac...@gmail.com: 2009/12/12, elekktrett...@exemail.com.au elekktrett...@exemail.com.au: Hi all, 1) I think we desperately need to bring our USB stack into reality. Is anyone working on bringing in the new FreeBSD USB code or maybe one from other BSDs? How difficult would it be? Lets dicuss. I am going to port FreeBSD 8 stack.
Re: trying to compile ltp
LTP should be compiled on a linux box and then made to run in the linuxulator. Thanks for getting started on this. Cheers, Alex Hornung 2009/12/9 Pierre Abbat p...@phma.optus.nu: I tried to compile ltp (to test the linuxulator) and got some error with yy in it. So I installed flex and bison. I tried again, and got the following: make[4]: Entering directory `/usr/src/ltp-intermediate-20091122/testcases/kernel/security/tomoyo' gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I/usr/src/ltp-intermediate-20091122/testcases/kernel/include -I../../../../include -I../../../../include -L../../../../lib newns.c -lltp -o newns gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I/usr/src/ltp-intermediate-20091122/testcases/kernel/include -I../../../../include -I../../../../include -L../../../../lib tomoyo_file_test.c -lltp -o tomoyo_file_test make[4]: Leaving directory `/usr/src/ltp-intermediate-20091122/testcases/kernel/security/tomoyo' make[3]: Leaving directory `/usr/src/ltp-intermediate-20091122/testcases/kernel/security' make[3]: Entering directory `/usr/src/ltp-intermediate-20091122/testcases/kernel/syscalls' make[3]: *** No rule to make target `/usr/src/ltp-intermediate-20091122/testcases/kernel/syscalls/libevent/test/Makefile', needed by `libevent-all'. Stop. make[3]: Leaving directory `/usr/src/ltp-intermediate-20091122/testcases/kernel/syscalls' make[2]: *** [all] Error 2 make[2]: Leaving directory `/usr/src/ltp-intermediate-20091122/testcases/kernel' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/ltp-intermediate-20091122/testcases' make: *** [testcases-all] Error 2 Any idea what's wrong? Or should I just download the latest snapshot and try again? Pierre -- li ze te'a ci vu'u ci bi'e te'a mu du li ci su'i ze te'a mu bi'e vu'u ci
RE: linuxulator update
Diablo JDK has never needed the linuxemu, but I think it is built with it. What I was referring to was the official sun jre/jdk. In any case, jre/jdk is just one of many things that potentially use linuxemu. As far as OpenJDK goes, that involves getting gcj, icedtea, etc working which is a considerable effort. But again, this is not only about java but in general about the linuxulator. Cheers, Alex Hornung
RE: linuxulator update
Pierre, Any date is fine. This has been waiting for years, it's not about two weeks or a month anymore. Thanks for the interest in doing this! In any case, if someone else also wants to work on it, say so here so the effort is easier to coordinate. Don't be put off by the fact that someone already has announced his interest. It's all about collaboration here, and several people might get a usable result faster/easier. Cheers, Alex Hornung -Original Message- From: users-err...@crater.dragonflybsd.org [mailto:users-err...@crater.dragonflybsd.org] On Behalf Of Pierre Abbat Sent: 27 November 2009 14:34 To: users@crater.dragonflybsd.org Subject: Re: linuxulator update On Friday 27 November 2009 09:10:15 Alex Hornung wrote: Hi, With our outdated linux emu (linuxulator) we can't run most of the software that can run on FreeBSD, such as newer jre/jdk, ... ( see bug report 1141 [1] for more details). To actually be able to update the linuxulator, it would be very helpful to have LTP (Linux Test Project)[2] working on DragonFly. This is a relatively simple task that many end-users (as in non-developers) could do, and which would make it possible to identify what exactly we are lacking, what needs updating and once it is updated, directly testing to see if it works as expected. LTP would be compiled on some linux machine, and then made to run on our current linuxulator to identify these issues. If anyone would step up to do this task, we could immediately start updating the code with considerably less effort than without LTP. So please, if someone wants to start contributing without actual coding, this is a great opportunity which would result in great benefit for everyone. I could do this, but would have to wait until after December 8, as I'm still in school. Is that okay? I have Linux 2.6.20 and DF 2.5.1. Pierre -- li fi'u vu'u fi'u fi'u du li pa
RE: increasing vkernel memory
Use rehash? or reboot? Cheers, Alex Hornung -Original Message- From: users-err...@crater.dragonflybsd.org [mailto:users-err...@crater.dragonflybsd.org] On Behalf Of Siju George Sent: 18 November 2009 10:33 To: users@crater.dragonflybsd.org Subject: Re: increasing vkernel memory On Wed, Nov 18, 2009 at 2:08 PM, Sascha Wildner s...@online.de wrote: Well, you'll have to obtain the pkgsrc tree first via cvs, tarball, whatever. Then you can bootstrap it: cd /usr/pkgsrc/bootstrap ./bootstrap After bootstrap I get this error dfly-vk1# bmake search key=git bmake: Command not found. dfly-vk1# Thanks for your reply :-) --Siju
Re: dhclient dependency on bpf ?
probably because it needs to get packets that are directed to broadcast and not your machine. Just take a look at the source code. Sincerely, Alex Hornung
watchdog, gpio, soekris net5501 and more
Hi, I've just committed my soekris net5501 branch, on which I have been adding support for this particular piece of hardware. The ported hardware drivers are: * glxsb (Geode LX Security Block) * nsclpcsio (A Super I/O chip with gpio and sensors) * CS5536 and sc1100 geode (watchdog, timer and gpio for the companion chip CS5536 and sc1100 cpu) As a side effect to the above hardware drivers, I've also developed a watchdog and gpio framework. The watchdog framework is written completely from scratch but remains mostly compatible from a userland point of view with OpenBSD's implementation. Major difference is that the watchdog is reset from userland via ioctl and not sysctl. I've also imported OpenBSD's watchdogd and modified to suit my watchdog implementation, but as one can see, only few changes were needed. If anyone wants to add support for some watchdog, best way to go about it is to check out the pc32/i386/cs5536.c implementation of watchdogs. By default, if watchdogs are enabled by the options WATCHDOG_ENABLE kernel option, a timeout of 10 seconds is set and the kernel takes care of resetting the watchdog. There's also an option WDOG_DISABLE_ON_PANIC which will disable all watchdog timers on panic. This is useful so that the watchdog doesn't reset the hardware in midst of a debugging session. The two relevant sysctls are kern.watchdog.auto, which enables automatic in-kernel reset of the watchdog, and kern.watchdog.period, which is used to set the watchdog period. The gpio (General Purpose I/O) framework is somewhat based on OpenBSD's, maintaining a similar API and similar data structures to make porting of gpio drivers and consumers as painless as possible. While the internals are quite different, this should not difficult the porting process. So far the gpio framework itself and a consumer, gpio_led, are available. The cs5536 driver uses the gpio_led gpio consumer on net5501 as an example. As a goodie there's also a ERROR_LED_ON_PANIC option, which, if enabled, will search for a gpio_led called error and turn it on if a panic occurs. I will also add a gpioctl userland utility at some point, but I didn't have the time yet. While both the watchdog and gpio frameworks have behaved well during my tests, especially the gpio framework should be treated with care and only be used on development machines. Please consider the gpio framework experimental. I've tested compilation of both amd64 and x86 with these changes, and they don't seem to break anything, but let me know if something went wrong! Cheers, Alex Hornung
Re: Experimental pkgsrc GIT repo for DragonFly users
Matt, Just mirroring pkgsrc using git is of course fine; actually it's great, but I wasn't referring to that but rather to those *possible* future plans of, I quote, do[ing] some sort of local mod thing in the future using another branch. Cheers, Alex Hornung
RE: Experimental pkgsrc GIT repo for DragonFly users
While the idea of having a git mirror of pkgsrc is nice, I totally disagree with the idea of using it for local modifications. If we do that, we can just call it a fork directly and no need to call it pkgsrc anymore. Also, the solution to getting stuff working isn't keeping local modifications, but rather submitting the modifications to pkgsrc and even better, upstream, to the developers of the software themselves. I can already see how people get eager to fix stuff, put it in our own pkgsrc-branch, but completely forget about getting it fixed where it should be fixed, upstream and the real pkgsrc. While I understand it may take some time until these fixes reach pkgsrc, I think this is the (only) way to go about it. Also, I'm not familiar with how NetBSD takes care of pkgsrc, but I'm sure it could be possible to get some commit access to pkgsrc for someone of us and add our own patches when needed. This would significantly reduce the waiting time. Anyone with some experience with NetBSD - pkgsrc care to comment? Sincerely, Alex Hornung
unix98 ptys
Hi all, I've recently commited both the kernel and userland part of unix98 ptys, so I'm giving a short description of what happened and what to do if problems arise. What are unix98 ptys? Unix98 ptys are just a new standard for ptys. They basically revolve around /dev/ptmx (to open a master pty) and /dev/pts/XXX, where XXX is a number, for slaves. BSD ptys are limited to 256 ptys, due to the chosen nomenclature. Unix98 ptys are limited to 1000 ptys due to the line length of utmp (8 bytes), which allows for at most pts/999 (plus a terminating '\0'). See utmp(5) man page for more info on this. What happened? New userland functions in libc are: * posix_openpt[1] - Implemented as standard dictates (basically just opening /dev/ptmx) * ptsname[2] - Implemented as standard dictates * grantpt[3] - No-op, as the kernel already creates the pty dynamically with all the right permissions and ownership (see permissions further down). Following the standard would add a security risk here, imho. Every single bit of code I've ever seen using grantpt, only does so to follow the standard, not expecting it to do anything. * unlockpt[4] - No-op, as it really has no use whatsoever with dynamically created ptys. I've also migrated openpty(3) to first try and use unix98 ptys, and if any part of that fails, to fall back to the old BSD ptys. Old BSD ptys can still be used as they always have been used; nothing has changed for them. As a matter of fact some programs, as xterm 247 and aterm don't even use openpty(3) and just find a free BSD pty (/dev/pty**), so expect to still see quite a few /dev/pty** and family. Permissions (as specified in grantpt standard[3]) are the following: For slaves: real uid, group tty, 0620 For master: real uid, group wheel, 0600 but it doesn't matter, because the master device cannot be opened more than once. Every time /dev/ptmx is opened, a different master is acquired. Troubleshooting? Make sure you have all the commits relating to unix98 ptys. If something is still wrong, please do: sysctl kern.pty_debug=1 This will enable some basic debugging for unix98 ptys which should be enough for most (critical) problems. If you find any other problem, especially with some program doing something weird, don't hesitate to contact me. Cheers, Alex Hornung References: [1]: http://www.opengroup.org/onlinepubs/95399/functions/posix_openpt.html [2]: http://www.opengroup.org/onlinepubs/95399/functions/ptsname.html [3]: http://www.opengroup.org/onlinepubs/95399/functions/grantpt.html [4]: http://www.opengroup.org/onlinepubs/95399/functions/unlockpt.html
Re: is dev_ops_add() permanently removed ?
Hi, there's no direct substitute; instead just use make_dev properly :) No, there are no plans to bring it back ever, it is not needed anymore with devfs. If you need help fixing your kernel module(s) do not hesitate to contact me. Sincerely, Alex Hornung 2009/8/13 Naoya Sugioka naoya.sugi...@gmail.com: Hi, I have a question. By recent change (http://gitweb.dragonflybsd.org/dragonfly.git/commit/3e82b46c18bc48fdb3c1d60729c7661b3a0bf6bf) dev_ops_add() is no longer existing in sys/device.h. Can someone give me a clue what is a substitute, or any recovery plan it will be back soon ? I'm using dev_ops_add() in kqemu module modevent() routine. thank you, -Naoya
Re: Lost all Data
That's because on one you have devfs mounted and on the other one you don't. Sincerely, Alex Hornung 2009/8/11 Siju George sgeorge...@gmail.com: On Tue, Aug 11, 2009 at 9:45 PM, Simon 'corecode' Schubertcorec...@fs.ei.tum.de wrote: as i wrote before, use HAMMER (yes, not intuitive.) Yes it worked Now i have all data :-)) but my /dev on the second disk has more files than /dev on the first disk. I have updated the base system on the second disk also using chroot . Is it because i have not booted from the second disk after the upgade? for comparision. /dev on the first disk # ls /dev acd0 ad6s1a bpf3 klog random ttyv2 ttyvf acpi ad6s1b bpsm0 kmem serno ttyv3 tun ad4 ad6s1d cd0 log stderr ttyv4 tun0 ad4s1 ad6s1e console lpt0 stdin ttyv5 tun1 ad4s1a ad6s1f consolectl lpt0.ctl stdout ttyv6 tun2 ad4s1b ad6s1g cuaa0 md0 sysmouse ttyv7 tun3 ad4s1d ad6s1h cuaia0 mem tty ttyv8 urandom ad4s1e apm cuala0 null ttyd0 ttyv9 usb ad4s1f ata devctl pass0 ttyid0 ttyva usb0 ad4s1g bpf devfs pci ttyld0 ttyvb usb1 ad4s1h bpf0 fd ppi0 ttyp0 ttyvc xpt0 ad6 bpf1 io psm0 ttyv0 ttyvd zero ad6s1 bpf2 kbd0 ptyp0 ttyv1 ttyve /dev on the second disk # ls /mnt/2ndDisk/dev/ acd0 ad6s2 ccd2s1 da13s4 da6s0a fd1s2 twed0s1e acd0a ad6s3 ccd2s1a da14 da6s0b fd1s3 twed0s1f acd0c ad6s4 ccd2s1b da14s0 da6s0c fd1s4 twed0s1g acd0s0 ad7 ccd2s1c da14s0a da6s0d fw0 twed0s1h acpi ad7s0 ccd2s1d da14s0b da6s0e fw0.0 twed0s1i ad0 ad7s0a ccd2s1e da14s0c da6s0f fw0.1 twed0s1j ad0s0 ad7s0b ccd2s1f da14s0d da6s0g fw0.2 twed0s1k ad0s0a ad7s0c ccd2s1g da14s0e da6s0h fw0.3 twed0s1l ad0s0b ad7s0d ccd2s1h da14s0f da6s0i fwmem0 twed0s1m ad0s0c ad7s0e ccd2s1i da14s0g da6s0j fwmem0.0 twed0s1n ad0s0d ad7s0f ccd2s1j da14s0h da6s0k fwmem0.1 twed0s1o ad0s0e ad7s0g ccd2s1k da14s0i da6s0l fwmem0.2 twed0s1p ad0s0f ad7s0h ccd2s1l da14s0j da6s0m fwmem0.3 twed0s2 ad0s0g ad7s0i ccd2s1m da14s0k da6s0n i4b twed0s3 ad0s0h ad7s0j ccd2s1n da14s0l da6s0o i4bctl twed0s4 ad0s0i ad7s0k ccd2s1o da14s0m da6s0p i4brbch0 ucom0 ad0s0j ad7s0l ccd2s1p da14s0n da6s1 i4brbch1 ucom1 ad0s0k ad7s0m ccd2s2 da14s0o da6s1a i4btel0 ucom2 ad0s0l ad7s0n ccd2s3 da14s0p da6s1b i4btel1 ucom3 ad0s0m ad7s0o ccd2s4 da14s1 da6s1c i4bteld0 ugen0 ad0s0n ad7s0p ccd3 da14s1a da6s1d i4bteld1 ugen0.1 ad0s0o ad7s1 ccd3s0 da14s1b da6s1e i4btrc0 ugen0.10 ad0s0p ad7s1a ccd3s0a da14s1c da6s1f i4btrc1 ugen0.11 ad0s1 ad7s1b ccd3s0b da14s1d da6s1g iic0 ugen0.12 ad0s1a ad7s1c ccd3s0c da14s1e da6s1h iic1 ugen0.13 ad0s1b ad7s1d ccd3s0d da14s1f da6s1i io ugen0.14 ad0s1c ad7s1e ccd3s0e da14s1g da6s1j ipauth ugen0.15 ad0s1d ad7s1f ccd3s0f da14s1h da6s1k
Re: HEADS UP - DEVFS ON MASTER
Just a short *WARNING*: do *NOT* activate the loading of any sound modules in loader.conf: it'll cause a panic, probably due to a bug in the kernel linker. Cheers, Alex Hornung 2009/8/4 Matthew Dillon dil...@apollo.backplane.com: Alex's GSOC project, DEVFS is now on master and active. Some care must be taken when upgrading. * A full buildworld, buildkernel, installkernel, installworld sequence is needed. No changes to fstab are needed, /dev will be mounted from devfs automatically by the kernel. * If you run a new kernel with an old world (without devfs) you will not be able to login as root, but you will still be able to login as a user and su, and you should still be able to boot single-user. In otherwords, things will be messed up but in a fixable way, until both the world and the kernel are in sync. * A great deal of testing of basic functions has been done, but there is still a very good chance of breakage. Please test and report any issues. Very few GUI components have been tested, so if X or sound stops working it may be a day or two before we can get it whacked back into shape. * The master branch may be unstable for a week as wider testing is done. * PEOPLE RUNNING CHROOTS: Character and block devices in the filesystem NO LONGER WORK. If you have chrooted or jailed areas with their own /dev, you have to use mount_devfs in those areas. Many features are now working. We have auto-cloning support for numerous devices but only a few userland utilities have been adjusted to use it. To reduce issues DEVFS will pre-create a bunch of units for numerous devices so the non-cloning userland utilities still work. In addition, fully automatic slice and partition probing and reprobing is now operational. When you fdisk a drive the slices will pop up in /dev, and when you disklabel a slice the partitinos will pop up as well. MBR and disklabel edits will properly and automatically reprobe the drive. IMHO this is a very, very cool feature. The nrelease build still has a few issues. It will work and the intaller will come up, but the installer may have trouble seeing newly created partitions (a 'retry' usually solves the problem). This is a known issue and will be fixed. -Matt Matthew Dillon dil...@backplane.com
required/suggested devfs userland tool functionality
Hi, as I soon want to start with the userland tool for devfs, I would like to hear some thoughts on what userland functionality is needed for devfs. While my original intentions were to also replace the current devd, I don't see the need for it, neither do I think it's appropriate as it for example can execute commands for devices that nobody ( as in: no driver ) attached to, which is something devfs won't be able to do. So what is left for devfs userland tool to do is to apply certain permissions/rules to devices that are created. I currently see two solutions to this: 1) notify the userland tool of every single device attach/detach and give it some time to answer with a set of permissions for the newly created device. This approach requires running the devfs userland tool as a daemon, with one instance per devfs mount point. This has the advantage that rules could be kept in userspace. 2) let the userland tool load a whole set of rules (for each devfs mount point) into the kernel. In turn the kernel applies the set of rules every time a device is attached. This has several advantages: - userland wouldn't have to be asked for every device attach - rules would continue to be applied even if the userland tool isn't running - for that same reason, userland tool wouldn't have to be a daemon. While I prefer the second approach, I would like to hear your thoughts about this before making a final decision on which one to use. I'd also welcome suggestions of other things you think the userland devfs tool should be able to do. Cheers, Alex Hornung
Re: required/suggested devfs userland tool functionality
As a matter of fact I only intended to do partial string matching, at best a few special formatters or so to specify a beginning or end of a string. Do we need anything besides that? In my opinion you normally would want to match them by prefix or device group (ad*, da*, ...) or so, no need for fancy regexps... And also I'd prefer not having to rely on a daemon to do all the ruling, it's probably safer and easier to just load rules. As for chmod/chown, you can already use that; that hasn't much to do with the userland tool. Cheers, Alex 2009/7/6 Simon 'corecode' Schubert corec...@fs.ei.tum.de: Matthew Dillon wrote: :2) let the userland tool load a whole set of rules (for each devfs :mount point) into the kernel. In turn the kernel applies the set of :rules every time a device is attached. This has several advantages: :- userland wouldn't have to be asked for every device attach :- rules would continue to be applied even if the userland tool isn't running :- for that same reason, userland tool wouldn't have to be a daemon. : :While I prefer the second approach, I would like to hear your thoughts :about this before making a final decision on which one to use. I'd :also welcome suggestions of other things you think the userland devfs :tool should be able to do. : :Cheers, :Alex Hornung I like the second approach. Particularly since you already have a a VOP interface so loading the rules into devd could be as simple as doing a write() to a special node in devd. But do you really want to perform regexp/glob matching in the kernel? Or do you want to restrict the users to prefix matching? I think we basically need to deal with multiple things here: 1. no race conditions when creating device nodes 2. give the user enough flexibility 3. allow the user to use chmod/chown? I don't have an opinion yet what is better, but maybe we should assess which kind of rules a user is expected to write (which rules do we want to ship per default?), and then we can decide whether it is worthwhile to put the rules management in the kernel, or whether it better goes into userland. cheers simon -- 3 the future +++ RENT this banner advert +++ ASCII Ribbon /\ rock the past +++ space for low CHF NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Re: Sun Virtual Box 2.2.2
Meh, I tried answering but didn't send it to the list... here we go again: As you may or may not know, VirtualBox does not provide guest additions for DragonFly, so vboxsf is not a valid FS. If you want to access windows stuff or DF stuff, you can either use samba or ssh fs (SftpDrive or similar). Cheers, Alex On Wed, 2009-05-13 at 11:53 +0100, Miguel Soares wrote: ola Dfly users! Scenario : Host Windows Vista Ultimate Guest DragonFly2.2.1 CD version Goal : Trying to mount a share to connect DF to Windows Problem : When i execute mount -t vboxsf c:\DFShare /mnt/winI get an error saying vboxsf is not reconized. Anyone knows a solution to this ? thanks.
Re: atheros card and wpa_supplicant
Hi, I downloaded those bits and pieces, and I used athdebug to set the debug variable. Will try to give you all the info I have so far, including some new bits thats must be due to the debugging being enabled. When if_ath is loaded... ath0: Atheros 5212 mem 0x8801-0x08801 irq 4 at device 0.0 on cardbus0 ath0: tx_proc_q01234= ath0: MAC Address: MY MAC ADDRESS ath0: mac 7.9 phy 4.5 radio 5.6 Having twiddled that debug variable, upon ifconfig ath0 up i get ath_init: if_flags 0x8803 ath_stop_no_pwchg: invalid 0 if_flags 0x8803 now ifconfig ath0 down gives ath_stop_no_pwchg: invalid 0 if_flags 0x8842 I have also seen an invalid if_flags message with the number as 0x8802 i think, but cant remeber exactly how i triggered it (i think it was after the device timeouts running the supplicant. I am probably being numb, but what other messages should i have been seeing? (I havent really ever debugged anything like this, so I apologise for taking teeny tiny steps). I guess that means interrupts may not be getting through.. Also, running systat -vmstat i dont see an irq4 or ath0 entry...but i really am not sure if that was something that it helps to check. Cheers, Alex J Burke.
Re: atheros card and wpa_supplicant
On 01/05/06, Sepherosa Ziehau [EMAIL PROTECTED] wrote: BTW, which rate control algo are you using with ath(4)? Hi, I had been using rate_amrr for all my first round of testing, but since then have tried them all. While the broadcasting of the SSID on the AP was on, i tried each rate algo and made it do an ifconfig ath0 up scan, and nothing. I was reading the FreeBSD manual page for ifconfig also, and found the list ap command - not sure if that should work on DFly, but since (I believe) the ifconfig was recently synced I tried that also - to no avail. It seems the issue I have here is that no matter which rate algo I use, and no matter what encryption I have set the AP to use (or not as the case may be) it just is not finding the AP at all, hence why it cannot connect. I am still a bit suspicious about that ath0: device timeout message that gets spewed after it says Setting scan request: 5 sec 0 usec, but dont really know if that is related to my other problems and/or how to go about finding the cause. BTW, just to mention - I am using your third diff to the 802_11 stuff, and the atheros code contained in the ath.tbz file. I tested the module dependency fix btw, and if i kldunload ath_rate before if_ath, it now stays in the kernel until i also unload if_ath. If there is anything else you would like me to try, I will do my best to help out. Just one request, since people have said that the 802_11 code seems solid and you will likely commit itcould you also possibly commit (only if you deem it fit of course) the cardbus patch? It would really help people with machines with those devices in the machine at boot (and I guess also onboard). Again, thank you for all your help, Alex J Burke.
Re: atheros card and wpa_supplicant
I also cloak the SSID, hence the scan_ssid=1. Would it be worth lowering the security level on my AP to see if that helps? Please turn off hiding ssid on AP and give it a try again. Best Regards, sephe -- Live Free or Die Hello, Sorry I didnt reply sooner - I did as you asked, turned the AP SSID masking off and it still shows the same behaviour as it did before, it never associates and then spits out the device timeout message. This behaviour then repeats itself until i exit the supplicant. I havent yet had a chance to try your latest 802.11 patch, so maybe that is another thing I should do. Also, again if you think it will make a difference I could knock my network back to WPA instead of 2 (or even WEP I guess). The only other thing I was not totally sure about was under FreeBSD 6 I had to kldload wlan and wlan_tkip (plus possibly wlan_ccmp). I tried kldload'ing wlan under DFly, but kldstat didnt show anything so I am not sure if that was a necessary step. Again, apologies if I have done something stupid. I really appreciate all the help you have given me with this. Thanks, Alex J Burke.
