Re: Question: tracking filesystem changes?
Hi, > > No, won't do the trick either. I cannot afford setting up watchdogs for > > every file or even every directory. And I'm essentially "interested" in > > every one of them (for mirroring purposes). A more general approach is > > needed. E.g., if an unlink call is issued and an inode is within a > > particular filesystem (luckily, most of our data already lives on or can > > be easily moved to a separate filesystem), a notice is sent to some > > userland daemon: "file /www/xxx/yyy.shtml is unlinked". Or opened for > > writing, or renamed... etc. The file is then scheduled for distribution > > to mirrors. The idea seems simple and straightforward, yet I don't know > > if it is achievable. > > > > The essential part is obtaining the full pathname of the file (won't > > bother with hardlinks at first, they aren't used here). Could that be > > done with the FreeBSD's filesystem (vnode/vfs?) code? (which I'm not > > familiar with) > > The TrustedBSD Audit code should be able to fill this need -- the goal of > the Audit code is to be able to track "security critical events" in a > configurable way, so file open/link/symlink/unlink operations are an > important subset of that. We hope to integrate the Audit code into 6.x in > the next few months, and then (in as much as is possible given kernel ABI > requirements) merge for 5.5. However, this is some time away still, so > presumably can't help in the short term. The result, though, is an event > stream file that's mechanically parseable, and the even stream can be > configured to indicate which types of events are important at a fairly > fine granularity. Sounds great. But i have similar tasks (not so huge amount of files) and i'd prefer to extend kqueue/kevent with EVFILT_INODE filter to have ability to monitor changes in file without opening it. -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Intel PRO/Wireless 2200BG/2915ABG
Hi, hackers. Does anybody here work already on this piece of hardware? I'm very interested in getting it work under FreeBSD and ready to help. -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel PRO/Wireless 2200BG/2915ABG
Guys, > Does anybody here work already on this piece of hardware? I'm very > interested in getting it work under FreeBSD and ready to help. Thanks for your answers. I have 2915ABG and Belkin F5D8230-4 access point. Will it be enough to install RELENG_6 to play with iwi stuff? -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intel PRO/Wireless 2200BG/2915ABG
On Tue, Sep 06, 2005 at 03:30:18PM -0700, Darren Pilgrim wrote: > From: Nick Strebkov > > > > Thanks for your answers. I have 2915ABG and Belkin F5D8230-4 > > access point. Will it be enough to install RELENG_6 to play > > with iwi stuff? > > That depends. You'll need firmware before you can use the iwi driver. > One of show-stopper problems with the iwi driver is that connections > which spew large numbers of packets (cvs, cvsup, remote X, etc.) will > make the iwi device suddenly stop working. Hm... It's really sad, but how does this prob relates to selection CURRENT vs RELENG_6? -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Driver for Intel PRO/Wireless 2200BG/2195ABG
Hi, hackers. Does anybody here work already on this piece of hardware? I'm very interested in getting it work under FreeBSD and ready to help. -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: malloc() in kernel and increasing mbuf and cluster size
Hi, Kamal On 17.10.2005 04:49:01, kamal kc wrote: > this may be a trivial question for many of you > but i am confused in doing memory allocation in the > kernel. > > sys/malloc.h has function prototypes for malloc() > kern/kern_malloc.c defines the malloc() > > the malloc() definition is > > void * > malloc(size, type, flags) > unsigned long size; > struct malloc_type *type; > int flags; > > i understand the size and flags but what shall i > do with the malloc_type. man 9 malloc :-) -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
obtaining a kernel crash dump
Hi there. I can't obtain a crash dump. % cat /sys/i386/conf/DEVEL | grep makeoptions makeoptions DEBUG=-g % cat /etc/rc.conf| grep dump dumpdev="/dev/ar0s1b" dumpdir="/var/crash" I'm testing my kernel patch and the following is what I see in /var/log/messages: May 19 16:17:00 devel /kernel: Fatal trap 12: page fault while in kernel mode May 19 16:17:00 devel /kernel: fault virtual address= 0x20a4e920 May 19 16:17:00 devel /kernel: fault code = supervisor write, page not present May 19 16:17:00 devel /kernel: instruction pointer = 0x8:0xc01920d3 May 19 16:17:00 devel /kernel: stack pointer= 0x10:0xe7951e80 May 19 16:17:00 devel /kernel: frame pointer= 0x10:0xe7951ea4 May 19 16:17:00 devel /kernel: code segment = base 0x0, limit 0xf, type 0x1b May 19 16:17:00 devel /kernel: = DPL 0, pres 1, def32 1, gran 1 May 19 16:17:00 devel /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 May 19 16:17:00 devel /kernel: current process = 637 (rtpslave) May 19 16:17:00 devel /kernel: interrupt mask = net May 19 16:17:00 devel /kernel: trap number = 12 May 19 16:17:00 devel /kernel: panic: page fault May 19 16:17:00 devel /kernel: May 19 16:17:00 devel /kernel: syncing disks... 60 3 2 [dd boot kernel messages] May 19 16:17:00 devel savecore: no core dump Thanks in advance. -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: obtaining a kernel crash dump
On Wed, May 19, 2004 at 05:20:04PM +0300, Peter Pentchev wrote: > On Wed, May 19, 2004 at 04:34:42PM +0300, Nick Strebkov wrote: > > Hi there. > > > > I can't obtain a crash dump. > > > > % cat /sys/i386/conf/DEVEL | grep makeoptions > > makeoptions DEBUG=-g > > % cat /etc/rc.conf| grep dump > > dumpdev="/dev/ar0s1b" > > dumpdir="/var/crash" > > > > I'm testing my kernel patch and the following is what I see in > > /var/log/messages: > > Can you force the kernel to dump by using DDB? Place 'options DDB' in > your kernel config, then, when the system is quiescent, hit Ctrl-Alt-Esc > and type 'panic' at the DDB prompt. > > If this works, and you get a crash dump, then the problem might be that > with your kernel patch, the kernel is panicking in a low-level layer, > like memory management or disk drivers or something like that, and it > simply cannot make a crash dump, since that would mean invoking code > that depends on bad data or something. Thanks a lot. I'll try. I modify the ip_input.c in the manner like IPFW do. -- Nick Strebkov Public key: http://humgat.org/~nick/pubkey.txt fpr: 552C 88D6 895B 6E64 F277 D367 8A70 8132 47F5 C1B6 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
