4 Feb 00:06
5 Feb 01:30
5 Feb 01:30
5 Feb 09:09
Re: crossdev stability database
My apologies, I didn't realize that I wasn't just starting a new thread by erasing whatever contents were in a message and changing the subjectOn Sunday 04 February 2007, Mike Frysinger wrote: > On Saturday 03 February 2007, Christopher Friedt wrote: > > Does anyone if there is some sort of stability table for various > > combinations of > no such thing exists > -mike > P.S. stop hijacking threads :p
8 Feb 07:18
Re: Re: crossdev stability database
On Monday 05 February 2007, Christopher Friedt wrote: > My apologies, I didn't realize that I wasn't just starting a new thread > by erasing whatever contents were in a message and changing the subject
8 Feb 17:36
conntrackd on uclibc?
Hi, Has anybody got conntrackd work on hardened/uclibc? https://bugs.gentoo.org/show_bug.cgi?id=165669 Looks like an uclibc issue to me. Compiles fine against glibc om my 64 bit desktop. Any pointers? if i386-gentoo-linux-uclibc-gcc -DPACKAGE_NAME=\"conntrackd\" -DPACKAGE_TARNAME=\"conntrackd\" -DPACKAGE_VERSION=\"0.9.2\" -DPACKAGE_STRING=\"conntrackd\ 0.9.2\" -DPACKAGE_BUGREPORT=\"pablo@...\" -DPACKAGE=\"conntrackd\" -DVERSION=\"0.9.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DYYTEXT_POINTER=1 -DHAVE_LINUX_CAPABILITY_H=1 -DHAVE_LIBNFNETLINK=1 -DHAVE_LIBNETFILTER_CONNTRACK=1 -DHAVE_LIBPTHREAD=1 -DHAVE_ARPA_INET_H=1 -DHAVE_INET_PTON=1 -DHAVE_INET_PTON_IPV6=1 -I. -I. -I../include -march=i386 -Os -pipe -fomit-frame-pointer -MT cache_persistence.o -MD -MP -MF ".deps/cache_persistence.Tpo" \ -c -o cache_persistence.o `test -f 'cache_persistence.c' || echo './'`cache_persistence.c; \ then mv -f ".deps/cache_persistence.Tpo" ".deps/cache_persistence.Po"; \ else rm -f ".deps/cache_persistence.Tpo"; exit 1; \ fi In file included from /usr/include/sys/uio.h:24, from /usr/include/sys/socket.h:27, from /usr/include/libnfnetlink/libnfnetlink.h:19, from proxy.c:19: /usr/include/sys/types.h:61: error: conflicting types for 'dev_t'(Continue reading)
9 Feb 07:56
Getting "new device" events
I'm working on setting up an embedded system where I need to know if the user has inserted a CD-ROM, an USB memmory stick, an USB harddrive or an SD-Card. Now, udev could probably do this, but because of the limited resources I would like to know if I there are other (better) alternatives. To sum up: does anybody know of ways to execute some commands/code whenever a new device (from the list above), is added? /peter
9 Feb 08:35
Re: Getting "new device" events
On Fri, 2007-02-09 at 07:56 +0100, Peter Poulsen wrote: > I'm working on setting up an embedded system where I need to know if the > user has inserted a CD-ROM, an USB memmory stick, an USB harddrive or an > SD-Card. Now, udev could probably do this, but because of the limited > resources I would like to know if I there are other (better) alternatives. > > To sum up: does anybody know of ways to execute some commands/code > whenever a new device (from the list above), is added? busybox mdev. Natanael Copa
9 Feb 10:03
Re: Getting "new device" events
<snip> >> >> To sum up: does anybody know of ways to execute some commands/code >> whenever a new device (from the list above), is added? > > busybox mdev. > Thanks, it certainly gets some of the work I want. However, I need to execute some code that will inform the user that a new device has been detected. So what I'm looking for is a "hook" where I can attach my code. In udev I would use the RUN+=... argument in the udev rule, but I'm looking for an alternativ. /peter
9 Feb 12:02
Re: Getting "new device" events
On Fri, 2007-02-09 at 10:03 +0100, Peter Poulsen wrote: > <snip> > >> > >> To sum up: does anybody know of ways to execute some commands/code > >> whenever a new device (from the list above), is added? > > > > busybox mdev. > > > Thanks, it certainly gets some of the work I want. However, I need to > execute some code that will inform the user that a new device has been > detected. So what I'm looking for is a "hook" where I can attach my code. > > In udev I would use the RUN+=... argument in the udev rule, but I'm > looking for an alternativ. You can run whatever code you want when a device is attatched or detattched with mdev. /etc/mdev.conf: sd[a-z][0-9]* root:disk 0660 */usr/local/bin/newusbdisk.sh Wil execute /usr/local/bin/newusbdisk.sh every time an usbdisk is either attatched or detached. > /peter >
RSS Feed