- WLUG - wlug.mailman3.com

OT: HP9k E-class

by Desdinova

A bit OT, if you can reply off-list, that's fine. I just figure there's probably guys who know about crappy old minis here. I've got an E25 and I'm planning to replace the internal scsi drive, it shouldn't be any big deal, but this *is* HP. Are there any gotchas on drive geometry or size that I should watch for? Take care, des

May 17, 2007

Re: [Wlug] Follow-Up to Key Signing Party

by Jamie Guinan

On Thu, 17 May 2007, Eric Martin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thanks to everyone who showed up to tonight's key signing party. Now > that we verified everybody had the correct key info and identification, > we actually have to sign each other's keys. We are using the keyserver > pgp.mit.edu. If that isn't your default, you can set it either in > ~/.gnupg/gpg.conf or at the command line for each command by using the > argument > - --keyserver pgp.mit.edu Is the "hkp://" prefix needed in gpg.conf? keyserver hkp://pgp.mit.edu > Below is an excerpt from the gpg Key Signing Party HowTo that explains > things in detail.(http://www.rubin.ch/pgp/kspa/gpg-party.en.html#ss3.8): > > 3.8 How to sign others' keys > > Step 1: Get a copy of the key > > Normally, you'll be working from a keyserver. However if you are signing > the key that is not available on a keyserver, you can use simply import > the key with gpg --import. If you are working with a keyserver, the > following command will download the key from the keyserver into your > public keyring. > > bash$ gpg --keyserver <keyserver> --recv-keys <Key_ID> > > If you get a read error, it means the keyserver is overloaded. Please, > try again in a few seconds. That worked Ok. > > Step 2: Fingerprint and Verify the key > > bash$ gpg --fingerprint <Key_ID> That too. > GPG will print out the fingerprint of the Key with <Key_ID > (the key > you just downloaded). Check the fingerprint against the checklist that > you where given at the party. Note: Don't check the fingerprint on your > checklist against the fingerprint on the web page as the server may not > send you the same key it displays on the web page. > > Step 3: Sign the key > > bash$ gpg --sign-key <Key_ID> Ok. > > If you have multiple private keys, you can specify which of your private > keys to sign the other persons public key with like this: > > bash$ gpg --default-key <Key_to_use> --sign-key <Key_ID> > > Step 4: Return or Upload the signed key > > If you are working with an entity which does not want their key on a > public keyserver, you should at this point you should return their > signed key back to them by their method of choice - normally encrypted > email. You should not send a public key to a keyserver with out the > permission of the key's owner. Publicizing a public key slightly reduces > the security of a key pair, therefor it is considered rude to make a key > more public than its owner desires. > > Most likely you are working with a keyserver. If that is the case, you > can send the signed key back to the keyserver like this: > > bash$ gpg --keyserver <keyserver> --send-key <Key_ID> > > You should see a success message like this: > > gpg: success sending to `<keyserver>' (status=200) > Congratulations, the signature of the other entity's key is now complete > and your signature has been incorporated into their public key. A trust > path has been established. This looked different for me, $ gpg --send-key A9413B9F gpg: sending key A9413B9F to hkp server pgp.mit.edu $ No affirmative response, it just returned to the prompt. But the exit code was 0. $ echo $? 0 -Jamie [ not yet using gpg for mail ]

May 17, 2007

Follow-Up to Key Signing Party

by Eric Martin

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks to everyone who showed up to tonight's key signing party. Now that we verified everybody had the correct key info and identification, we actually have to sign each other's keys. We are using the keyserver pgp.mit.edu. If that isn't your default, you can set it either in ~/.gnupg/gpg.conf or at the command line for each command by using the argument - --keyserver pgp.mit.edu Below is an excerpt from the gpg Key Signing Party HowTo that explains things in detail.(http://www.rubin.ch/pgp/kspa/gpg-party.en.html#ss3.8): 3.8 How to sign others' keys Step 1: Get a copy of the key Normally, you'll be working from a keyserver. However if you are signing the key that is not available on a keyserver, you can use simply import the key with gpg --import. If you are working with a keyserver, the following command will download the key from the keyserver into your public keyring. bash$ gpg --keyserver <keyserver> --recv-keys <Key_ID> If you get a read error, it means the keyserver is overloaded. Please, try again in a few seconds. Step 2: Fingerprint and Verify the key bash$ gpg --fingerprint <Key_ID> GPG will print out the fingerprint of the Key with <Key_ID > (the key you just downloaded). Check the fingerprint against the checklist that you where given at the party. Note: Don't check the fingerprint on your checklist against the fingerprint on the web page as the server may not send you the same key it displays on the web page. Step 3: Sign the key bash$ gpg --sign-key <Key_ID> If you have multiple private keys, you can specify which of your private keys to sign the other persons public key with like this: bash$ gpg --default-key <Key_to_use> --sign-key <Key_ID> Step 4: Return or Upload the signed key If you are working with an entity which does not want their key on a public keyserver, you should at this point you should return their signed key back to them by their method of choice - normally encrypted email. You should not send a public key to a keyserver with out the permission of the key's owner. Publicizing a public key slightly reduces the security of a key pair, therefor it is considered rude to make a key more public than its owner desires. Most likely you are working with a keyserver. If that is the case, you can send the signed key back to the keyserver like this: bash$ gpg --keyserver <keyserver> --send-key <Key_ID> You should see a success message like this: gpg: success sending to `<keyserver>' (status=200) Congratulations, the signature of the other entity's key is now complete and your signature has been incorporated into their public key. A trust path has been established. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGS+VsaiVxdKlBO58RAs3xAJ0W7SyjfbQtwHwDaHeWG5EgeWWXzgCfQ8pT W40gnhPVnkQ3u7E1jbXALvU= =GM/c -----END PGP SIGNATURE-----

May 17, 2007

Re: [Wlug] PGP Key Signing Party

by Gregory Avedissian

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's my fingerprint: pub 1024D/5DC682A4 2004-04-17 [expires: 2009-04-16] Key fingerprint = 4DF6 E8E1 5521 6ECC 7A3E E7F0 BF02 ADEA 5DC6 82A4 Greg Avedissian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGS8i0vwKt6l3GgqQRAui5AJ4my59DCPMhLXnwIsZSLvvL3Qh62ACeMLt1 hJHV/oml3PBTo5117s9YXOA= =NO0Y -----END PGP SIGNATURE-----

May 17, 2007

Last-Minute Emergency, Unable to Attend

by Terry S

Hello, I had a phone call at 6:07 that required me to go out for a while, and did not have time to email. (I'm the one with the camera.) Hopefully, someone else just "happened" to have one, but I can take pictures at our next meeting if needed. How did the key-signing go? Terry

May 17, 2007

Re: [Wlug] large file performance on linux

by Jeff Moyer

==> On Wed, 16 May 2007 22:19:14 +0000, brad noyes <maitre(a)ccs.neu.edu> said: brad> All, brad> here's a summary of what i have tried so far. I have tried using the O_DIRECT brad> and O_SYNC flags with open(2) and i have been using a non-journalling brad> filesystem, ext2. None of these options have yielded any better performance at brad> the rates i'm looking for. brad> I have not tried AIO. AIO will allow you to drive your disk subsystem better than synchronous writes; I really think this would solve your problem. For an example of an AIO app, you can google for aio-stress.c. Or, send me some code and I'll help get you started. -Jeff

May 16, 2007

Re: [Wlug] large file performance on linux

by brad noyes

All, here's a summary of what i have tried so far. I have tried using the O_DIRECT and O_SYNC flags with open(2) and i have been using a non-journalling filesystem, ext2. None of these options have yielded any better performance at the rates i'm looking for. I have not tried AIO. I don't think i can use a non 32-bit kernel on the xeons. Correct me if i'm wrong (it's happened before). As a temporary solution i created a memory filesystem, by $> mount -t tmpfs tmpfs -o size=6G /data/memory The writes are fast however i need another process to progressively move data out of the memory filesystem since i don't have enough memory to hold all 22GB of data i need. For those interested i have attached a small program which will use different options to open and profile the fwrite calls. To compile simply do $> sh ./testwrite.c $> ./testwrite -h $> ./testwrite -l 16 file.out I just wanted to keep you all updated. Thanks for all your help. I'll keep trying various ideas. I wish i could make it to the meeting to buy you all pizza for your help. Perhaps next month. Thanks, -- Brad

May 16, 2007

Re: [Wlug] Meeting tomight

by Brains

freak4uxxx(a)gmail.com wrote: > I might be slightly delayed tonight, small family thing that needs to be taken care of. I shouldn't be late but I just wanted to let people know. > > -Eric I suspect a lot of people are going to be running a little late this evening, including me... Frank "Rain, sleet, or snow, the LUGman marches on..."

May 16, 2007

Meeting tomight

by freak4uxxx＠gmail.com

I might be slightly delayed tonight, small family thing that needs to be taken care of. I shouldn't be late but I just wanted to let people know. -Eric

May 16, 2007

Re: [Wlug] PGP Key Signing Party

by Mike

Sorry guys. I don't think I am going to be showing up to do the inclement weather. If you see anyone posing as me, well, then it is not me. I can always trade keys w/ peeps next time. Cheers, Mike <quote who="Andy Stewart"> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Eric Martin wrote: >> Just a reminder that we are having a PGP Key Signing Party tomorrow for >> WLUG. If you're name isn't listed below, I do not have your info (and >> you should get it to me if you want to be on the list). I know Andy >> said noon tomorrow but I'll take stuff until 4pm. Don't forget your two >> forms of ID and I'll see you tomorrow. >> >> Eric Martin >> Gregory M. Avedissian >> Walt Sawyer >> Alexander Pennace >> Doug Mildram >> Keith Wright >> Alex Weiss >> Andrew M. Stewart >> James Philip Gray >> >> -Eric > > HI Eric, > > Thanks for sending out the meeting reminder! > > I'll see you all on Wednesday evening with my shiny new passport. :-) > > Later, > > Andy > > > - -- > Andy Stewart, Founder > Worcester Linux Users' Group (http://www.wlug.org) > Chelmsford Linux Meetup Group (http://linux.meetup.com/393) > Amateur Radio: KB1OIQ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (GNU/Linux) > Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org > > iD8DBQFGSkvGHl0iXDssISsRApWmAJ9HpIERvKHryJXnIeBo8ZfoJnqBygCeIF2I > tQxc9xAb6JDHR8dbSTc3yNA= > =v7Xx > -----END PGP SIGNATURE----- > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > -- They who would give up an essential liberty for temporary security, deserve neither liberty or security --Ben Franklin

May 16, 2007