Hey folks, I'm a visually impaired guy trying to find a way to easily invert the screen colors in KDE (3.5+).

There actually is a way to do this in the Accessibility section (Visible Bell), but unfortunately it only flashes an inverted screen at a minimum of 100 msecs and a maximum of 2000 msec. But ideally I just want to be able to toggle the screen to inverted colors and have it stay that way while I do something like view a PDF file.

The "Visible Bell" feature is triggered whenever the system bell goes off. I thought perhaps running a script to constantly trigger the system bell might work, but it might just end up constantly flashing the screen too, which isn't helpful either.

OR if someone happens to know where the configuration file is where I can try changing the value from 2000 msecs to 9999999 msecs,

Since the code that the "Visible Bell" feature obviously works well enough to invert the screen in brief flashes, then someone who is familiar with the source code for the KDE Accessibility features could eatract it and turn it into a useful program that could be executed with a keyboard shortcut similar to the Mac's control+alt+apple+8 sequence.

Any ideas?

I need a GENERIC (none Vendor specific) command for checking the status of a harddrive inside a hardware raid configuration.

I have the vendor supplied commands for doing this (for HP and Dell), but I need to do this on a generic machine with an Adaptec 5805 card in it.

FOR HP:
# hpacucli controller slot=0 physicaldrive all show status
physicaldrive 1:0 (port 1:id 0, 36.4 GB): OK
physicaldrive 2:0 (port 2:id 0, 36.4 GB): OK
physicaldrive 1:1 (port 1:id 1, ??? GB): Failed
physicaldrive 2:1 (port 2:id 1, ??? GB): Failed

FOR DELL:
# omreport storage adisk controller=0


FOR Generic/Adaptec card
?????????????????

--

Update Nevermind - I found it.

1- Install StorMan
2- /usr/StorMan/arcconf getconfig 1

I am confused.


me@me-laptop:~/aircrack-ng-1.0-rc3$ make
make -C src all
make[1]: Entering directory `/home/me/aircrack-ng-1.0-rc3/src'
make -C osdep
make[2]: Entering directory `/home/me/aircrack-ng-1.0-rc3/src/osdep'
Building for Linux
make[3]: Entering directory `/home/me/aircrack-ng-1.0-rc3/src/osdep'
gcc -g -W -Wall -Werror -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=0 -fPIC -I.. -c -o osdep.o osdep.c
gcc -g -W -Wall -Werror -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=0 -fPIC -I.. -c -o network.o network.c
gcc -g -W -Wall -Werror -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=0 -fPIC -I.. -c -o linux.o linux.c
gcc -g -W -Wall -Werror -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=0 -fPIC -I.. -c -o linux_tap.o linux_tap.c
gcc -g -W -Wall -Werror -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=0 -fPIC -I.. -c -o radiotap-parser.o radiotap-parser.c
gcc -g -W -Wall -Werror -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=0 -fPIC -I.. -c -o common.o common.c
ar cru libosdep.a osdep.o network.o linux.o linux_tap.o radiotap-parser.o common.o
ranlib libosdep.a
touch .os.Linux
make[3]: Leaving directory `/home/me/aircrack-ng-1.0-rc3/src/osdep'
make[2]: Leaving directory `/home/me/aircrack-ng-1.0-rc3/src/osdep'
gcc -g -W -Wall -Werror -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=0 -Iinclude -c -o aircrack-ng.o aircrack-ng.c
In file included from aircrack-ng.c:65:
crypto.h:12:26: error: openssl/hmac.h: No such file or directory
crypto.h:13:25: error: openssl/sha.h: No such file or directory
crypto.h:15:25: error: openssl/rc4.h: No such file or directory
crypto.h:16:25: error: openssl/aes.h: No such file or directory
cc1: warnings being treated as errors
In file included from aircrack-ng.c:69:
sha1-sse2.h: In function ‘calc_4pmk’:
sha1-sse2.h:143: warning: implicit declaration of function ‘HMAC’
sha1-sse2.h:143: warning: implicit declaration of function ‘EVP_sha1’
aircrack-ng.c: In function ‘crack_wpa_thread’:
aircrack-ng.c:3876: warning: implicit declaration of function ‘EVP_md5’
make[1]: *** [aircrack-ng.o] Error 1
make[1]: Leaving directory `/home/me/aircrack-ng-1.0-rc3/src'
make: *** [all] Error 2

I don't know nearly enough to recognize the pattern and know what to do about it.... if anyone can give me info or even a pointer as to how to decipher this and what the problem is, that would be awesome.

And the Winner Is . . .

The votes have been tallied, the results are in, and we have a winner (two, actually). Congratulations to the newly elected user representatives to the LJ Advisory Board: from lj_election_en, it's kylecassidy, and from lj_election_ru, it's nekbke! You can see the full breakdown of results for lj_election_en here and for lj_election_ru here. Thanks to everyone for your participation.

So, here's one for the crowd.

It's been 30 years since networks (and hence, network filesystems) have been common.

So, why are we stuck with NFS and SMB as the best network filesystem protocols (yes, I know there are others but most of them suffer from one or more of the problems I'm about to detail.. and if they don't, TELL ME, please).
( cut for sanity )
Ideas are welcome.