I worked for a software company a couple years ago that made Linux-based security software, including a hardened Linux distribution, that was partly funded by DoDefense grants. Even back then, I was told by the people who designed the proposals that the department was very partial to proposals with this kind of license.
There's a chance, if someone is willing to port it or maybe if Sun funds it. But the SPARC architecture, while interesting technologically, isn't interesting economically (hence the fact that many of the commerical distros have stopped supporting it) as a Linux platform. Plus, according to the link above, IBM has something based on SG that seems to be already on SPARC.
I really shouldn't respond to trolls, but I guess I am anyway. StackGuard is only currently implemented on x86, but I don't think it actually depends on any x86-isms; likewise, even though it is currently only implemented in Linux, it doesn't really depend on any Linux-isms. It's only limited to Linux x86 because that's all anyone with time or money ever bothered to implement it on. I'm told that a GCC 3 implementation is nearly done. I ask about it everytime I venture downtown to have lunch with the WireX folks (I used to work there, but not in the research side).
I wholly agree. A 99% success rate sounds really bad for a surgery that's basically a convenience. Hell, I think I'd want at least a 1:10,000 chance for something like that. I'd certainly rather fly in an airplane or attempt to climb Mt. Everest.
The 'libtrash' library already mentioned is a reasonable approach. Another approach, however, might be instead of a full back-up made with 'cp' or 'tar' or 'dump', but a periodic 'ln' of files into a special directory somewhere on the filesystem. (I mean a hard link, not a soft link.) A 'find' script could very easily accomplish this and could build time-oriented versioning into it. Of course this approach will keep blocks used for a considerable amount of time, unless you have another script that deletes them periodically.
You will, however, looe the contents of the file if the file is truncated (open(2) is called with 'O_TRUNC'). I do not know whether the file server software (be it Samba, Netatalk, etc) can guarantee that truncation won't happen. I would hope that 'libtrash' includes a wrapper for open(2) that also handles truncation.
Somewhat irrelevant, but I have seen some S/390/zSeries systems on a PCI card that are designed for development workstations. The cost, IIRC, was on the order of a new PC--$2k or so. I'd guess you could find iSeries too, but they'd cost as much.
I know of neither stand-alone GUI apps nor mailers that actually allow you to edit entries on the server, although most mailers now at least let you search for addresses. There are, however, several web-based apps that will let you edit. I forget all the names, but I believe SquirrelMail has a plug-in for it and there are several others on Freshmeat.
It shouldn't be too terribly much work to write a cross-platform app in Python to allow editing and browsing of entries; I'd guess 30-40 man-hours if someone wants to fund the development.
I've been developing a set of Perl modules and Webmin interfaces for managing users and groups, and could probably implement something for Usermin, but I've been too busy trying to make a living to work on it lately.
There's a fair amount that goes into learning how LDAP works, understanding the ACLs, etc., but the basics of setting up a server are pretty easy. Understanding and Deploying LDAP is probably the best book out there (title might not be quite right), published by MacMillan. It's a very thick book and not very cheap, but definitely the best book I've found.
Yes, I know. The thing was, though, that much of this data should have already been committed--the image I saved 10 minutes or so before I left, which means it should have been flushed from the cache. I can understand volatile data like my bookmarks being lost, but not the image file.
For a modern multi-tasking operating system like Linux or BSD, SCSI is a better answer than RAID. I've always found interactive use much better than with IDE, even than the newer ATA-100 and ATA-133 drives. IBM used to make RS/6000s with 2.5" SCSI drives and titanium cases. There were really sweet!
This isn't correct. The ext3 module should be in the initrd, which means it doesn't need to be statically compiled in for the initial rootfs mounting. It may be that the mkinitrd isn't adding the module as it should.
I've seen this. In my case, it was fixed by unmounting and mounting the filesystem again. I've also seen files that one command (like find or rm -rf) would see as a directory and another would see as a file. I don't understand how there can be differences, given that they should all be using the same C library interfaces. These have always been recoverable, however.
Also, I experienced something considerably more distressing: data corruption. After reading the benchmarks comparing ReiserFS and ext3 mounted with 'data=ordered' and 'data=writeback', I decided to try writeback mode. It seemed okay for a while, but lately because of the heat my computer has been shutting itself. Once I came back and found that after hitting the reset button, my Mozilla bookmarks were reduced to a small portion of what they ought to have been. An image I had been working on and saved had been replaced by the content of several e-mail messages. rxvt would no longer start correctly from the KDE panel, even though checking through the properties it looked okay. I re-added the button and it started correctly. There were other things awry too, and probably things I haven't found.
I was using the "offical" kernel from Red Hat for 7.3, 2.4.18-5. In summary, DO NOT USE data=writeback for now.
I hope not, since Red Hat hasn't used inetd for at least 2 years. They're using xinetd now and in the last few releases, everything is off by default, blocked by the basic firewall rules, or only listening on localhost.
In fact, it's hard to imagine 500 lines of inetd or xinetd configuration. He almost surely means/etc/services, which makes him pretty clueless.
If you look in your local computer monthly (most cities have at least one) or newspapers, you're almost certainly going to find a handful of local consultants, who will be happy to build a system for you and install it just as you want it.
I do this, although I generally work locally (in the Portland, Oregon area). I'd be glad to help if you'd like to pay the extra shipping (there's usually shipping to get the parts to me, then I deliver the system myself). I can do post-installation customization if you want to allow an incoming external connection via SSH or FreeS/WAN. I'm building a mail server for a client just this week; cost with on-site installation, local admin training, and integration with their existing systems is going to be around $3000.
I'd even be glad to give you hands-on training and on-site installation if you want to pick up the cost for the flight. (Most don't, which is why I mostly work locally.)
True, I probably wouldn't want to run my fast new sport cars on biodiesel, but then again, I'd probably not run it on diesel in the first place. In the US we've got a lot of older cars; far more than I've seen in Europe (or maybe it's just that our cars are uglier and seem old more quickly). Furthermore, there are also plenty of service vehicles that aren't high-performance and probably don't have engines that are pushing the limits of diesel.
Probably not. My friend Josh is the Veggie Van guy and did this a few years ago. The fast food companies saw it as a way to advertise. The leftover grease is also used for various other cosmetics, like lipstick; at least, it used to be when my grandparents had a drive-in 20 years ago. I doubt they really make that much off selling it for cosmetics, but probably more than having to dispose of it.
You're right though--the restaurants probably won't be interested in continuing to give it away once it's no longer novel. However, it's entirely possible that they might be able to sell the grease for biodiesel and make more than for cosmetics.
In the long run though, recycling the grease from these restaurants isn't as important as being dependent on renewable, domestically-produced, cleaner-burning resources.
Speaking completely out of my ass without bothering to read the bill, I suspect the ban on video taping would cut both ways. While it will (might?) protect our privacy in public (if that's possible), it would likely also make a tape like the Rodney King beating illegal. Not that it did Rodney King much good or the LAPD any bad, but it seems that being able to video tape the cops and other miscreants is important for gathering evidence.
I bought an alarm clock in Germany last fall for about US$7 thatt was set by radio signals (in fact, almost every one I looked at did; I just bought the cheapest). Worked fine in Europe. Wouldn't work in the US, so I got a US made clock at the Sharper Image (Ream-Me-Out-of-My-Money Image) for about $35 that was radio-set too. I've recently seen one at a department store that was only about $20. I suspect it probably costs less than $5 to put this in an appliance. Perhaps for a VCR or microwave oven this is a big expense, but why not put them in cars?
Slashdot Mirror
The previous poster is not a troll! His facts (#1 & #2) are correct and his opinion (#3) is shared by many.
I worked for a software company a couple years ago that made Linux-based security software, including a hardened Linux distribution, that was partly funded by DoDefense grants. Even back then, I was told by the people who designed the proposals that the department was very partial to proposals with this kind of license.
There's a chance, if someone is willing to port it or maybe if Sun funds it. But the SPARC architecture, while interesting technologically, isn't interesting economically (hence the fact that many of the commerical distros have stopped supporting it) as a Linux platform. Plus, according to the link above, IBM has something based on SG that seems to be already on SPARC.
I really shouldn't respond to trolls, but I guess I am anyway. StackGuard is only currently implemented on x86, but I don't think it actually depends on any x86-isms; likewise, even though it is currently only implemented in Linux, it doesn't really depend on any Linux-isms. It's only limited to Linux x86 because that's all anyone with time or money ever bothered to implement it on. I'm told that a GCC 3 implementation is nearly done. I ask about it everytime I venture downtown to have lunch with the WireX folks (I used to work there, but not in the research side).
I wholly agree. A 99% success rate sounds really bad for a surgery that's basically a convenience. Hell, I think I'd want at least a 1:10,000 chance for something like that. I'd certainly rather fly in an airplane or attempt to climb Mt. Everest.
The 'libtrash' library already mentioned is a reasonable approach. Another approach, however, might be instead of a full back-up made with 'cp' or 'tar' or 'dump', but a periodic 'ln' of files into a special directory somewhere on the filesystem. (I mean a hard link, not a soft link.) A 'find' script could very easily accomplish this and could build time-oriented versioning into it. Of course this approach will keep blocks used for a considerable amount of time, unless you have another script that deletes them periodically.
You will, however, looe the contents of the file if the file is truncated (open(2) is called with 'O_TRUNC'). I do not know whether the file server software (be it Samba, Netatalk, etc) can guarantee that truncation won't happen. I would hope that 'libtrash' includes a wrapper for open(2) that also handles truncation.
Well, I'd have guessed an S390/zSeries box for a system that large...
Somewhat irrelevant, but I have seen some S/390/zSeries systems on a PCI card that are designed for development workstations. The cost, IIRC, was on the order of a new PC--$2k or so. I'd guess you could find iSeries too, but they'd cost as much.
I know of neither stand-alone GUI apps nor mailers that actually allow you to edit entries on the server, although most mailers now at least let you search for addresses. There are, however, several web-based apps that will let you edit. I forget all the names, but I believe SquirrelMail has a plug-in for it and there are several others on Freshmeat.
It shouldn't be too terribly much work to write a cross-platform app in Python to allow editing and browsing of entries; I'd guess 30-40 man-hours if someone wants to fund the development.
I've been developing a set of Perl modules and Webmin interfaces for managing users and groups, and could probably implement something for Usermin, but I've been too busy trying to make a living to work on it lately.
There's a fair amount that goes into learning how LDAP works, understanding the ACLs, etc., but the basics of setting up a server are pretty easy. Understanding and Deploying LDAP is probably the best book out there (title might not be quite right), published by MacMillan. It's a very thick book and not very cheap, but definitely the best book I've found.
What are you talking about? It's initrd, loaded by the boot-loader, not /sbin/init.
Yes, I know. The thing was, though, that much of this data should have already been committed--the image I saved 10 minutes or so before I left, which means it should have been flushed from the cache. I can understand volatile data like my bookmarks being lost, but not the image file.
For a modern multi-tasking operating system like Linux or BSD, SCSI is a better answer than RAID. I've always found interactive use much better than with IDE, even than the newer ATA-100 and ATA-133 drives. IBM used to make RS/6000s with 2.5" SCSI drives and titanium cases. There were really sweet!
I should add that this is a SCSI drive, not a funky IDE drive with a non-disableable (!!) write cache.
This isn't correct. The ext3 module should be in the initrd, which means it doesn't need to be statically compiled in for the initial rootfs mounting. It may be that the mkinitrd isn't adding the module as it should.
I've seen this. In my case, it was fixed by unmounting and mounting the filesystem again. I've also seen files that one command (like find or rm -rf) would see as a directory and another would see as a file. I don't understand how there can be differences, given that they should all be using the same C library interfaces. These have always been recoverable, however.
Also, I experienced something considerably more distressing: data corruption. After reading the benchmarks comparing ReiserFS and ext3 mounted with 'data=ordered' and 'data=writeback', I decided to try writeback mode. It seemed okay for a while, but lately because of the heat my computer has been shutting itself. Once I came back and found that after hitting the reset button, my Mozilla bookmarks were reduced to a small portion of what they ought to have been. An image I had been working on and saved had been replaced by the content of several e-mail messages. rxvt would no longer start correctly from the KDE panel, even though checking through the properties it looked okay. I re-added the button and it started correctly. There were other things awry too, and probably things I haven't found.
I was using the "offical" kernel from Red Hat for 7.3, 2.4.18-5. In summary, DO NOT USE data=writeback for now.
But the trolls can be downright unbearable.
I hope not, since Red Hat hasn't used inetd for at least 2 years. They're using xinetd now and in the last few releases, everything is off by default, blocked by the basic firewall rules, or only listening on localhost.
In fact, it's hard to imagine 500 lines of inetd or xinetd configuration. He almost surely means /etc/services, which makes him pretty clueless.
It's too bad too; I had a couple of VA's 2U boxes and they were really well-engineered.
If you look in your local computer monthly (most cities have at least one) or newspapers, you're almost certainly going to find a handful of local consultants, who will be happy to build a system for you and install it just as you want it.
I do this, although I generally work locally (in the Portland, Oregon area). I'd be glad to help if you'd like to pay the extra shipping (there's usually shipping to get the parts to me, then I deliver the system myself). I can do post-installation customization if you want to allow an incoming external connection via SSH or FreeS/WAN. I'm building a mail server for a client just this week; cost with on-site installation, local admin training, and integration with their existing systems is going to be around $3000.
I'd even be glad to give you hands-on training and on-site installation if you want to pick up the cost for the flight. (Most don't, which is why I mostly work locally.)
See Naked Ape Consutling.
There is plenty of farmland that doesn't contribute to run off. Especially when your fields don't have cattle shitting on them.
True, I probably wouldn't want to run my fast new sport cars on biodiesel, but then again, I'd probably not run it on diesel in the first place. In the US we've got a lot of older cars; far more than I've seen in Europe (or maybe it's just that our cars are uglier and seem old more quickly). Furthermore, there are also plenty of service vehicles that aren't high-performance and probably don't have engines that are pushing the limits of diesel.
Probably not. My friend Josh is the Veggie Van guy and did this a few years ago. The fast food companies saw it as a way to advertise. The leftover grease is also used for various other cosmetics, like lipstick; at least, it used to be when my grandparents had a drive-in 20 years ago. I doubt they really make that much off selling it for cosmetics, but probably more than having to dispose of it.
You're right though--the restaurants probably won't be interested in continuing to give it away once it's no longer novel. However, it's entirely possible that they might be able to sell the grease for biodiesel and make more than for cosmetics.
In the long run though, recycling the grease from these restaurants isn't as important as being dependent on renewable, domestically-produced, cleaner-burning resources.
For girls:
Speaking completely out of my ass without bothering to read the bill, I suspect the ban on video taping would cut both ways. While it will (might?) protect our privacy in public (if that's possible), it would likely also make a tape like the Rodney King beating illegal. Not that it did Rodney King much good or the LAPD any bad, but it seems that being able to video tape the cops and other miscreants is important for gathering evidence.
I bought an alarm clock in Germany last fall for about US$7 thatt was set by radio signals (in fact, almost every one I looked at did; I just bought the cheapest). Worked fine in Europe. Wouldn't work in the US, so I got a US made clock at the Sharper Image (Ream-Me-Out-of-My-Money Image) for about $35 that was radio-set too. I've recently seen one at a department store that was only about $20. I suspect it probably costs less than $5 to put this in an appliance. Perhaps for a VCR or microwave oven this is a big expense, but why not put them in cars?