The reason DeCSS violates the DMCA is that allows people to circumvent copy protection mechanisims. If a book explains how to circumvent a copy right protection mechanism THAT IT DOES VIOLATE THE DMCA. The real question is whether moding an xbox can be considered circumvention.
yeah sorta. the scripts do work fine, they just take a long time to write to disk. i have about 30,000+ lines of configs that need to be written to 20+ machines (hehe, don't ask:)) those machines then need to have apache read the configs back in. (it takes about two minutes for the whole process to take place). luckily its not that often that the entire server farm gets restarted and even less often that all of the configs get rewritten from scratch. it seems like that time could be cut in half if you cut that middle step out.
I've had great luck with Electric Fence, it even smacks your hand when you mix new/delete and *malloc. Too bad it doesn't keep me from writing crappy code in the first place.
I've been using linux since pre 1.0.x kernels and only happened to start using linux cause some other folks around had been messing with it and it looked like fun (coming from Irix on SGIs where the machines shipped with juggling balls I was very into having fun with new oses.:).
I only just tried BSD (freebsd and openbsd) a few months ago. I've never had a thing against BSD, I just never thought to try it. I was super impressed. I downloaded a boot disk from the freebsd site and three hours later I had installed a kicking box with gnome, kde, gimp, the works. I was even able to get a usb mouse working. I was blown away by the excellent security (took me a bit to get the hang of swithing security levels to let me start x but that kind of security rocks). I think the weakest part of linux is its lack of kernel level security.
So anyway, so here's my gripe about startup scripts:
Most Linux distributions have their System V startup scripts symbolically linked from an init.d directory to the rc(n).d directories, for example,/etc/rc.d/init.d to/etc/rc.d/rc(n).d in Red Hat. This is a potentially confusing scheme, and you can't customize these scripts unless you properly add the runlevel info at the top of the file.
Umm confusing? I love the init scripts setup in linux. Maybe i've just gotten used to being able to uniformly start and stop any daemon on my box by typing:/etc/rc.d/init.d/httpd start. and i think writing scripts for new daemons is cake Am I missing something or is there an easy way to start and stop any service on a freebsd box (short of doing something like killall -9 sendmail)? Some daemons have more involved startup and shutdowns (like database servers) and its nice to have one spot for everything. Am I missing something? (I know, I know, RTFM) I definately don't think it reflects badly on bsd (it only takes about 5 minutes to tweak things to work the way I'm confortable with on flavor of unix) but it would be cool if there was a better way of doing things and I just missed it.
None the less, mucho cudos to the freebsd and openbsd crowd. If I had the time I would convert more of my boxes to bsd.
-tem
been running linux on 64 bit alphas for years now (any one else buy an alpha udb box from onsale for $300 during the mid 90's? what a steal). my question is why its taken so long for intel to catch up to the rest of the chip market? and why is the general trend in computer technology that the poorest platform/os/etc holds the greatest market share? got me.
Slashdot Mirror
The reason DeCSS violates the DMCA is that allows people to circumvent copy protection mechanisims. If a book explains how to circumvent a copy right protection mechanism THAT IT DOES VIOLATE THE DMCA. The real question is whether moding an xbox can be considered circumvention.
yeah sorta. the scripts do work fine, they just take a long time to write to disk. i have about 30,000+ lines of configs that need to be written to 20+ machines (hehe, don't ask:)) those machines then need to have apache read the configs back in. (it takes about two minutes for the whole process to take place). luckily its not that often that the entire server farm gets restarted and even less often that all of the configs get rewritten from scratch. it seems like that time could be cut in half if you cut that middle step out.
I've had great luck with Electric Fence, it even smacks your hand when you mix new/delete and *malloc. Too bad it doesn't keep me from writing crappy code in the first place.
I've been using linux since pre 1.0.x kernels and only happened to start using linux cause some other folks around had been messing with it and it looked like fun (coming from Irix on SGIs where the machines shipped with juggling balls I was very into having fun with new oses. :).
/etc/rc.d/init.d to/etc/rc.d/rc(n).d in Red Hat. This is a potentially confusing scheme, and you can't customize these scripts unless you properly add the runlevel info at the top of the file.
/etc/rc.d/init.d/httpd start. and i think writing scripts for new daemons is cake Am I missing something or is there an easy way to start and stop any service on a freebsd box (short of doing something like killall -9 sendmail)? Some daemons have more involved startup and shutdowns (like database servers) and its nice to have one spot for everything. Am I missing something? (I know, I know, RTFM) I definately don't think it reflects badly on bsd (it only takes about 5 minutes to tweak things to work the way I'm confortable with on flavor of unix) but it would be cool if there was a better way of doing things and I just missed it.
I only just tried BSD (freebsd and openbsd) a few months ago. I've never had a thing against BSD, I just never thought to try it. I was super impressed. I downloaded a boot disk from the freebsd site and three hours later I had installed a kicking box with gnome, kde, gimp, the works. I was even able to get a usb mouse working. I was blown away by the excellent security (took me a bit to get the hang of swithing security levels to let me start x but that kind of security rocks). I think the weakest part of linux is its lack of kernel level security.
So anyway, so here's my gripe about startup scripts:
Most Linux distributions have their System V startup scripts symbolically linked from an init.d directory to the rc(n).d directories, for example,
Umm confusing? I love the init scripts setup in linux. Maybe i've just gotten used to being able to uniformly start and stop any daemon on my box by typing:
None the less, mucho cudos to the freebsd and openbsd crowd. If I had the time I would convert more of my boxes to bsd. -tem
been running linux on 64 bit alphas for years now (any one else buy an alpha udb box from onsale for $300 during the mid 90's? what a steal). my question is why its taken so long for intel to catch up to the rest of the chip market? and why is the general trend in computer technology that the poorest platform/os/etc holds the greatest market share? got me.