public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <dalek@exceedtech.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Strange traffic says I am using windoze and have a bug.
Date: Mon, 26 Dec 2005 22:40:16 -0600	[thread overview]
Message-ID: <43B0C5B0.2080802@exceedtech.net> (raw)
In-Reply-To: <200512261816.56826.eric@creativecow.net>

Eric Bliss wrote:

>On Monday 26 December 2005 05:20 pm, Dale wrote:
>  
>
>>>You can run "strings" on it, or have a peek in a hex editor...
>>>      
>>>
>>How I do that?  What would I learn from it?  hex editor?  I think I saw 
>>that somewhere.  O_O  I thought KDE used to have something that I could 
>>view it with but since the upgrade I can't find it.  Maybe lde-meta 
>>missed something???
>>
>>    
>>
>
>I think "KDE Menu Button -> Utilities -> More Applications -> Binary Editor 
>(KHexEdit)" is what you're looking for.  Ironically enough, I was just using 
>it.
>
>  
>
Mine was under File instead of More Apps.  Now I have to go download the 
thing again.  I hate windoze and I don't even like storing windoze stuff 
on my rig.  Wonder why? 

My brother got a digital camera for Christmas.  You have to plug in the 
USB camera then reboot winders for it to work.  Is that some crap or 
what?  I updated the drivers for USB too.  It  wouldn't work at all 
before I did that.  It would see the camera then come up with a hardware 
error.  Stupid windoze.  It took me 20 minutes to get it to work in 
Linux and I spent all day screwing with windoze.  Just in the spirit of 
things, reboot to make it work.  That sucks.  He's happy that it works 
at all but I'm not.  I may put Linux on that thing yet.  If I knew I 
wouldn't be moving soon, I would.  I'd put a bigger heatsink on the CPU 
and compile away.  He has seen my Linux and thinks it is cool.  I would 
have to do the admin stuff though.  Ssh comes to mind here.

OK.  I vented a bit.  One more thing to vent though, I HATE WINDOZE!!!  
< makes mad face complete with clenched teeth >

Thanks

Dale
:-)

-- 
To err is human, I'm most certainly human.

I have four rigs:

1:  Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two 80GB hard drives.  Named Smoker
2:  Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive.  Named Swifty
3:  Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 224MBs of ram and a 2.5GB drive.  Named Pokey
4:  Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB SCSI drive.  Named Putput

All run Gentoo Linux, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers.  

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-12-27  4:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26  5:10 [gentoo-user] Strange traffic says I am using windoze and have a bug Dale
2005-12-26 10:51 ` Holly Bostick
2005-12-26 11:17   ` Dale
2005-12-26 12:43     ` Stroller
2005-12-26 13:11       ` W.Kenworthy
2005-12-26 18:46         ` Dale
2005-12-26 16:51     ` Antoine
2005-12-26 17:31       ` Steven Susbauer
2005-12-26 18:52         ` Dale
2005-12-26 20:14           ` darren kirby
2005-12-27  1:20             ` Dale
2005-12-27  2:16               ` Eric Bliss
2005-12-27  4:40                 ` Dale [this message]
2005-12-26 19:47       ` Stroller
2005-12-27  5:42 ` Walter Dnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43B0C5B0.2080802@exceedtech.net \
    --to=dalek@exceedtech.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox