hrm? I've done that twice. First time was in 94, and it involved a fair amount of doc reading, but ended up working nice enough. last time was a month ago, and it just involved going through a couple of menus to put the phone #, account name, etc.
Anyone notice they used FrontPage?
on
MacMafia
·
· Score: 1
it works just fine. worst that can happen is that you need to tell fdisk how many tracks to consider, but that's only under 2.0.36 or older. use 2.2.2 or 2.2.3 and be happy.
hrm? what on earth is wrong with zsh? it's more configurable, and more filled with practical little features, than bash, and, like bash, it derives its scripting language from sh, rather than the braindead csh. The first thing I do on all my new accounts is change my shell to zsh and import my.zshrc from another box...
no, what belongs on Linux is a front-end that looks and acts a lot like Access, and accesses (pun intended) a real SQL server, which doesn't need to be Oracle either, just make it PostrgreSQL by default.
eggs-actly! that's why it's called "local", duh. distros should put their stuff under/usr. and why the fsck do some packages get special treatment and go into/opt? it's not because Sun came up with a dumb idea that Linux actually needs to copy it...
not everything works fine out of the box with SuSE 5.3 either. case in point, their Apache comes with mod_perl, but a simple mod_perl program that tries to use a module that involves loading a shared lib (like MD5, i.e a simple "use MD5;" at the beginning of your perl file) produces a heap of linking errors in the error_log.
not that I really blame them for it, it's a specialized thing and it takes 10 minutes to rebuild an Apache w/ mod_perl once you've done it once and written down the config options.
hmm, that law actually seems quite sensible when you read it, except for one thing: it makes SPOUSES a particular case. what the fuck does being married have to do with what you're allowed to say to each other? make that "close friends" or "people living together" or somesuch, at least.
silly people. license changes are NOT retroactive. RSA couldn't do a thing to prevent the use of MD5 now; they would be laughed to hell and back if they tried to patent it after years of prior use. And it's not in their interest at all.
and make sure you allow the damn thing to dump core, and know hwere the cores will go. as a last resort, strace -p to random httpd processes (not the master one, unless you have 10x the cpu/. currentyl takes!) see if you can catch where the fault happens.
nothign else is even close to cddb, but it only got there because people volunteered to type their stuff, and if they did it once they could do it twice. esp. considering that the db was donwloadable and reusable until a while ago. I don't personally use cddb nor care the very least about this kind of service, but if I were using it, I"d sure as hell stop and join a ML wiht people interested in re-creating a free alternative. tehcnically it's not that hard; just put the whole thing into a mysql db with a bit of C code to read the network and do the queries. and people have already offered to host the thing.
as for dirtying up cddb's database, I don't think it's such a bad thing either; at least it would drive the point home that, when you run a service that depends on its users, you don't want to piss them off, and that the users and the app developpers don't quite belong to two separate, unrelated works. and you could always make it easy (but not trivial) to clean up by including a fixed string in all your bogus entries.
Anti-Microsoft FUD???��??-��??-��??-��??-�n��n��
on
Microsoft and Linux
·
· Score: 1
heh, I htought for a moment taht you were one of these rare birds who have actually managed to make NT work (you know, that OS that's supposedly soooo easy to admin), until you showed off your real reasons: you're afraid of Open Source code being better than what *you* can make and get paid for.
you're making a very dangerous mix-up. writing software like an emulator is *not* and *can never* be a crime (morally at least; countries have made stupid laws before). people may *use* your software in criminal ways, but that's not the software author's fault, unless he actually went and encouraged them to do it.
calm down, Linus and co are *not* clueless, when it comes to licensing. You are allowed to make binary-only modules for Linux, as long as 1) you stick to the published, exported interface (i.e list of symbols), and 2) your module doesn't require specific kernel mods. so MOSIX is wrong on the 2nd count, and no, you can't port Linux to the BlahBlahCrap processor and hide most of the code in a binary-only module, or anything like that. you can, however, hide most of the drivers that way.
why put it on the *kernel*? hte kernel is supposed to be fast and low-level and every cache miss counts. everything on userland using perl as the base language, that's something I could agree to:-)
there's a perl interface to nvi. disclaimer: I haven't used it.
Implementing Awk in Perl? Why not vice versa?
on
Unix in Perl
·
· Score: 1
the difference is that it takes about twice as long in C, even with the regexp library, thanks to having to malloc everything by hand. Python or maybe Java maybe could compare in development speed, certainly not C.
go read the site, dork. the point is not to run a Unix box with the GNU utilities replaced by the perl ones (unless you're doing it for the hack value, of course). it's to get instant-portable utilities on every single thing perl runs on. and it's *not* limited to Unix/Linux and win32.
for chrissake, PERL??
on
Unix in Perl
·
· Score: 1
well, I can see one: these things will be *much* easier to make than the GNU ones ever were, and far easier to debug. the counterpart is, of course, that they will be a little slower and use more memory. then again, no-one is suggesting to replace all of/bin and/usr/bin with perl scripts. *that* would be quite silly. OTOH, I wouldn't mind a system that used perl as its main userland language, with/bin and/usr/bin in perl with a global cache of bytecode-compiled scripts somewhere.
Slashdot Mirror
hrm? I've done that twice. First time was in 94, and it involved a fair amount of doc reading, but ended up working nice enough. last time was a month ago, and it just involved going through a couple of menus to put the phone #, account name, etc.
macintoy is the right word :)
it works just fine. worst that can happen is that you need to tell fdisk how many tracks to consider, but that's only under 2.0.36 or older. use 2.2.2 or 2.2.3 and be happy.
I'm *not* going to stand in line for a long time. I'll just wait till most people have already seen it.. I don't mind seeing it a week or two later.
hrm? what on earth is wrong with zsh? it's more configurable, and more filled with practical little features, than bash, and, like bash, it derives its scripting language from sh, rather than the braindead csh. The first thing I do on all my new accounts is change my shell to zsh and import my .zshrc from another box...
looking at the patch itself, it should. it tests that the processor has the (mis)feature, not that the processor is a p3, before disabling the psn.
this is what I suspected... glad to see it posted by somoene who seems to know more about the process than I do.
no, what belongs on Linux is a front-end that looks and acts a lot like Access, and accesses (pun intended) a real SQL server, which doesn't need to be Oracle either, just make it PostrgreSQL by default.
eggs-actly! that's why it's called "local", duh. distros should put their stuff under /usr. and why the fsck do some packages get special treatment and go into /opt? it's not because Sun came up with a dumb idea that Linux actually needs to copy it...
not that I really blame them for it, it's a specialized thing and it takes 10 minutes to rebuild an Apache w/ mod_perl once you've done it once and written down the config options.
hmm, that law actually seems quite sensible when you read it, except for one thing: it makes SPOUSES a particular case. what the fuck does being married have to do with what you're allowed to say to each other? make that "close friends" or "people living together" or somesuch, at least.
silly people. license changes are NOT retroactive. RSA couldn't do a thing to prevent the use of MD5 now; they would be laughed to hell and back if they tried to patent it after years of prior use. And it's not in their interest at all.
and make sure you allow the damn thing to dump core, and know hwere the cores will go. as a last resort, strace -p to random httpd processes (not the master one, unless you have 10x the cpu /. currentyl takes!) see if you can catch where the fault happens.
as for dirtying up cddb's database, I don't think it's such a bad thing either; at least it would drive the point home that, when you run a service that depends on its users, you don't want to piss them off, and that the users and the app developpers don't quite belong to two separate, unrelated works. and you could always make it easy (but not trivial) to clean up by including a fixed string in all your bogus entries.
heh, I htought for a moment taht you were one of these rare birds who have actually managed to make NT work (you know, that OS that's supposedly soooo easy to admin), until you showed off your real reasons: you're afraid of Open Source code being better than what *you* can make and get paid for.
a silly fool you are. speak backwards Yoda does not. Objects before subjects Yoda puts.
eggs-acktly!
you're making a very dangerous mix-up. writing software like an emulator is *not* and *can never* be a crime (morally at least; countries have made stupid laws before). people may *use* your software in criminal ways, but that's not the software author's fault, unless he actually went and encouraged them to do it.
I pronounce "HP-UX" as "aitch-pee-sucks".
calm down, Linus and co are *not* clueless, when it comes to licensing. You are allowed to make binary-only modules for Linux, as long as 1) you stick to the published, exported interface (i.e list of symbols), and 2) your module doesn't require specific kernel mods. so MOSIX is wrong on the 2nd count, and no, you can't port Linux to the BlahBlahCrap processor and hide most of the code in a binary-only module, or anything like that. you can, however, hide most of the drivers that way.
why put it on the *kernel*? hte kernel is supposed to be fast and low-level and every cache miss counts. everything on userland using perl as the base language, that's something I could agree to :-)
there's a perl interface to nvi. disclaimer: I haven't used it.
the difference is that it takes about twice as long in C, even with the regexp library, thanks to having to malloc everything by hand. Python or maybe Java maybe could compare in development speed, certainly not C.
go read the site, dork. the point is not to run a Unix box with the GNU utilities replaced by the perl ones (unless you're doing it for the hack value, of course). it's to get instant-portable utilities on every single thing perl runs on. and it's *not* limited to Unix/Linux and win32.
well, I can see one: these things will be *much* easier to make than the GNU ones ever were, and far easier to debug. the counterpart is, of course, that they will be a little slower and use more memory. then again, no-one is suggesting to replace all of /bin and /usr/bin with perl scripts. *that* would be quite silly. OTOH, I wouldn't mind a system that used perl as its main userland language, with /bin and /usr/bin in perl with a global cache of bytecode-compiled scripts somewhere.