Re: What to do if a box is just "frozen"
Thierry - I have a 4.1 Release box that seems to mimic your 'freezing' encounter. I seem to run into the same thing after having my box up for long periods of time and especially after using anything that requires bpf0. I've wondered if it was just an error in the kernel I compiled, or unusual network activity or the result of bad RAM or a physical hardware problem. I would love to know if anyone else has encountered this oddity. Any feedbak would be appreciated - Janie Thierry Herbelot wrote: > Hello, > > I've got a little application at work which can "just freeze" a > 4.2-Release : the purpose of the application is just a packet blaster > used for telecom equipement test (send as many UDP packets as ordered, > on as many interfaces as there are on a machine). > > So, on my 4.2-R test box (no-thrills BX, P-III 700 intel box), I have > some tens (around 30 of them) of such processes sending their packets, > and after some time (I have to more precisely determine this "some > time"), the box simply locks. > I do not see any message on console. > > I have connected a real keyboard (the box was connected to a KVM > switch), I have DDB enabled in the kernel, and the box is still freezing > (if it were at least panicing, this would be a good start) : I can't > jump with ctrl-alt-esc to DDB (even Ctrl-Alt-Del does not reboot the > machine). > > The memory does not seem to be a problem, as there are around 50 free > megabytes (out of 128), if top is to be believed (the box does not run > anything else than the blaster). the kernel is compiled with 8192 Mbuf > clusters (runs of netstat -m give a use of around 400 out of the 8192 > clusters) > > the "freezing" happens when the blaster is run as root, and also happens > when run as a casual user. > > the box has a reset button, but this obvioulsy erases any data in > memory. > > Is there something I could do to debug this problem ? (is there any way > to force a crash dump, via a serial console perhaps ? what is really > depressing is the loss of control from the keyboard, not being able to > switch to DDB) > > I will try to upgrade the boxes to a more recent -Stable, to see if the > problem still exists. > > TIA for any idea > > -- > Thierry Herbelot > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to start to be a hacker?
When scouring through the threads - this one in particular caught my attention. In my experience, which is still very new, I think all of you make excellent points. For the most part, the novice/average person, believes that hackers are malicious, destructive individuals. A huge number of computer users are misled and misinformed about the true definition of the term 'hacker'. This is unfortunate - if those people could spend some time reading the brilliant posts to this list, they might realize that we are not all 16 year olds, hiding behind the glow of the monitor, reading their email and stealing their passwords and credit card information and posting it on IRC. I have a point. :] The first time I experienced that curiosity - I got a little carried away. eh hem I learned that my skills, which included aptness and dexterity, had been misdirected. Upon my awakening, I was blessed with my mentor. He challenged me to use my skills productively. In retrospect, I learned [the hard way] and gained some experience with some help from my mentor [some of you may know Peter Mountain - BRU2000]. All in all, there are many contributing factors to becoming a hacker. I rarely post to this list - so I hope that my lengthy post doesn't offend. So on that note - I will continue observing the minds at work. Thanks for the opportunity to post - Janie Dykes Wes Peters wrote: > > "G. Adam Stanislav" wrote: > > > > On Sat, Jul 03, 1999 at 01:18:52AM -0600, Wes Peters wrote: > > > > > You either are a hacker, or you are not. It is not something someone else > > > > > can teach you. > > > > > > > > This deserves a FAQ entry. What an awesome response. > > > > > > But it's certainly NOT something that you just are, either. You have to > > > have talent, but you also have to have experience. This is most often > > > done by a mentor. > > > > If you have the innate curiosity mentioned in my message, you will obtain > > experience whether you have a mentor or not. Experience is best obtained > > by trying things. It cannot be imparted by anyone else (although, it can > > be encouraged). > > And, in some cases, disasters averted. I think all of us here have seen > a few graphic examples lately of what happens when the mentoring process > doesn't work. > > I think being a hacker is a combination of talent, ethics, and experience. > I've known talented and experienced programmers who weren't hackers, > either because they didn't have the innate curiousity you mention or > because they were ethically challenged and used their skills to steal, > cheat, and destroy, which are *not* part of the hacker ethos. Hackers > create, crackers steal and destroy. > > But I'm certain you new that. ;^) > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > http://softweyr.com/ [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to start to be a hacker?
When scouring through the threads - this one in particular caught my attention. In my experience, which is still very new, I think all of you make excellent points. For the most part, the novice/average person, believes that hackers are malicious, destructive individuals. A huge number of computer users are misled and misinformed about the true definition of the term 'hacker'. This is unfortunate - if those people could spend some time reading the brilliant posts to this list, they might realize that we are not all 16 year olds, hiding behind the glow of the monitor, reading their email and stealing their passwords and credit card information and posting it on IRC. I have a point. :] The first time I experienced that curiosity - I got a little carried away. eh hem I learned that my skills, which included aptness and dexterity, had been misdirected. Upon my awakening, I was blessed with my mentor. He challenged me to use my skills productively. In retrospect, I learned [the hard way] and gained some experience with some help from my mentor [some of you may know Peter Mountain - BRU2000]. All in all, there are many contributing factors to becoming a hacker. I rarely post to this list - so I hope that my lengthy post doesn't offend. So on that note - I will continue observing the minds at work. Thanks for the opportunity to post - Janie Dykes Wes Peters wrote: > > "G. Adam Stanislav" wrote: > > > > On Sat, Jul 03, 1999 at 01:18:52AM -0600, Wes Peters wrote: > > > > > You either are a hacker, or you are not. It is not something someone > > > > > else > > > > > can teach you. > > > > > > > > This deserves a FAQ entry. What an awesome response. > > > > > > But it's certainly NOT something that you just are, either. You have to > > > have talent, but you also have to have experience. This is most often > > > done by a mentor. > > > > If you have the innate curiosity mentioned in my message, you will obtain > > experience whether you have a mentor or not. Experience is best obtained > > by trying things. It cannot be imparted by anyone else (although, it can > > be encouraged). > > And, in some cases, disasters averted. I think all of us here have seen > a few graphic examples lately of what happens when the mentoring process > doesn't work. > > I think being a hacker is a combination of talent, ethics, and experience. > I've known talented and experienced programmers who weren't hackers, > either because they didn't have the innate curiousity you mention or > because they were ethically challenged and used their skills to steal, > cheat, and destroy, which are *not* part of the hacker ethos. Hackers > create, crackers steal and destroy. > > But I'm certain you new that. ;^) > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr > LLC > http://softweyr.com/ > w...@softweyr.com > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: REQ: Better etiquette next week
hello all ~ I never posted to this list - maybe once, but I learned. I follow threads of brilliant minds at work and I read - and I am amazed by creative and complex issues which are resolved by a group of geeky greats. So - before I begin to drag this out - I wanted to share in agreement with Mr. Hearn about the unrelated posts to this list. I use this list as a learning tool. thanX Janie Dykes - Share your knowledgeit makes you smarter. Sheldon Hearn wrote: > > I find myself looking back at some of the ridiculous mail that found its > way into freebsd-hackers (instead of freebsd-chat or /dev/null) this > week and I wonder how on earth people without my li'l dethread script > survive. No, NO! Don't tell me, publically or privately, I don't care. > > I'd like to encourage everyone on the list to do his or her best next > week to try to adhere to the norms of mailing list etiquette that make > mailing list membership bearable. > > Pretty please, with cherries and syrup on top. > > TIA > Sheldon. > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
