Sounds like you want Actuate e.Reporting Suite. Hopefully in the future you will realize that 1 second spent with Google is equivalent to 1000 Ask Slashdot posts.
Anyway my personal opinion is that HTML is wrong wrong wrong for this stuff. Generate TeX output and convert to postscript, or *roff, or generate postscript directly. If the target is dead trees you should use dead-tree-era technology.
The time is yours. You must decide what you think is fair. If you are not allowed to go out of town on certain days, you should decide how much money that means to you, demand it from your employer, and either get it or walk away. If monitoring servers takes away from your spare time, you should set a value on that. Each individual is responsible for his own compensation.
My advice can only come from my own perspective. In any job, I insist that the duties are specifically detailed and known in advance. I do not put up with open-ended assignments, or requests to work outside of normall business hours which are brought up less than two weeks in advance. After all, I notify my employer two weeks before I intend to take vacation, or resign. If your job consists of monitoring operations at certain times of the day, week, or month, I would simply require that all those hours spent monitoring operations be compensated at the hourly rate. If you have to be on-call but not actively working, bill those hours at a reduced rate, but bill them just the same.
Tech workers who put up with a lot of BS should get paid for it. Auto mechanics and welders leave their work behind at 5:00 spot on, their brains synchronized precisely to the atomic clock of the Naval Observatory. The electricians and builders who work in my building work, by my honest observation, 2 hours per day. They certainly can't be reached outside of the 9:00-15:00 time window. If your employer wants you to spend your entire life at work, you should either say no or get paid accordingly.
I'm sure the density would be a lot better with the DL360, a 2xCPU SCSI machine in the same box as the 320. The Rackable stuff is 33% higher density than standard 1U machines, and the cabling is easier to manage.
Sorry for the crass reply to myself, but I forgot to relay my latest anecdote. I started a new job a few weeks back. First day on the job, I notice a lot of wanky shit happening on a development machine. Took a closer look, and the machine had been rootkitted. Took a closer closer look, and EVERY machine had been rootkitted. They were all default RH 6.2 "Server" installations, and they had all been rooted through a bind hole. Slackware, of course, doesn't start bind unless you specifically add it to the init procedure. Solution: replace r00t hat boxes with Slackware boxes. No more worries:)
Actually, they will not be back for 7.2. David Cantrell said in this post that floppy installs are now gone. Also, if you look at -current, there are several packages which are too large for floppies. a1/modules.tgz is 5MB. n1/samba.tgz is 6MB.
Is it possible to install Red Hat without installing X? I tried once, on a Multia, but gave up after 30 minutes of trying. It seems like enabling any package brought in a dependency on X (and/or tcl/tk, WTF?)
I use it, and not for "old times' sake". It is just stable, period. I use it on all my company's servers, and I have used it on the servers of my employers for years. I also use it on my own desktop at work and at home. Slackware is just so easy. I have never had any library version headaches of any kind, whereas with Debian and Red Hat I have. (Example: I can't get consistent libs, headers, and binaries for gnome and gnome-devel on debian testing). I also enjoy the flexibility of having both SysV and BSD init at the same time.
Slackware is also a handy base to start a new ditribution from. At my employers, I simply make new tag files, burn CDs, and I have automatic slack installers. At home, I have created an LDAP-authenticated distribution off Slackware. Again, no headaches, no unstable libraries, no balky compilers.
Yabbut, VA Linux is working on new machines using two AMD CPUs and the AMD 760MP chipset. The news has been on several hardware sites and VA employees have been posting to linux-kernel their patches to make the AMD 760 MP work well in Linux.
Good thing these defenders of peace and freedom require cookies before you can use their site. Otherwise, some hippie with cookies turned off might get to read the secret documents!
As you note, there were several problems. The original design was weak. Then the builder unilaterally decided to build the box beams the way they did. They also did not want to thread the entire length of the rod, so they changed the design to two rods. The hotel's prime contractor would not allow the engineering firm to be represented on site, for cost reasons. All of this added up to the disaster. The hotel was even fucked up before it was complete: 2000 square feet of roof collaped during construction.
One of my old professors put up a page about it with lots of picures. Check out this picture of the distressed box beam from the walkway that didn't collapse.
errno.h was needed to declare errno. Otherwise, gcc won't build without warnings. If I were to just declare extern int errno, I might be stepping on an implementation that uses macros for errno.
I don't think that's really a bug, because if stdout is not valid, rc will be less than zero and errno will be set to EBADF. If stdout was a pipe that was closed, the program will receive SIGPIPE, which is not handled and thus the program will exit via the default handler.
That was a famous accident. The hotel was in kansas city, IIRC. The design of the original structure was sound: a long rod suspended from the roof supported two catwalks, by supporting them both from underneath. Thus, each catwalk support had to hold the load of a fraction of one catwalk. As the drawing passed from the chief engineer down to the detail draftsman, the design of one long rod was changed to two shorter rods. So the builder suspended the upper platform from the roof, and suspended the lower platform from the upper one. The supports for the upper catwalk were loaded with twice the load they were designed for, and the offset of the lower rods caused a torque unanticipated by the designer.
I love my TiBook, but it is not gaming machine. The Rage 128 is slow, slow, slow no matter if Steve Jobs gets up on stage and says its faster than any video card available for PCs.
I hope that the current domain structure ceases to be the primary addressing tool used by everyday people on the internet. We have seen that it has serious limitations and causes many conflicts. We have also seen that its namespace is quickly exhausted, it isn't internationalizable, and the rules for the big three top level domains are not followed well.
I hope that it is replaced in the next year or two by a more sane directory structure. If I am trying to find a web page for a business, I imagine looking up the entry for Businesses/ACME Tools (of Hayward, California, USA), not www.acmetools.com, or maybe acme-tools.com, or haywardacme.com, or even getsometools.com! I can imagine looking up the entry for Publications/The Onion: America's Finest News Source.
If a system suh as this existed with 1) a defined network protocol, 2) an easy way to add and change entries, and 3) a widely-accepted algorithm for solving naming conflicts, I think it would handily replace the DNS as the primary lookup system. Of course DNS would still be used, for namenumber translation and whatnot.
You still didn't answer my question. What part of this has anything to do with the kernel? The kernel is process agnostic. You could build a system on top of the kernel that doesn't even use usernames and passwords.
What the hell are you talking about with number 5? The kernel doesn't give a rat fuck about console logins or any other kind of login. It just starts itself, and hands some filehandles off to an initial process. The kernel doesn't care what happens from there on.
Datapoints: PacBell service to my home in San Francisco reliably runs at 1.5 mpbs for $40/month. PacBell DSL to my former workplace routinely ran at 4 mbps for $200/month. Concentric DSL at my current workplace runs at a very bursty 100 kbps-ish.
The solution to this problem is very simple for cities. The local government, either the city or the county, needs to own the physical infrastructure. They need to run the wires or fibers into every building in town, and run the other end into large, empty, central offices. Then the building owner or whoever is at the end of the wire gets to decide what to hook up to his wire in the central office. If he chooses an Internet service provider, that ISP has to lease space in the publically owned central office and install its own equipment. There would not be any exclusion of anyone from central office space, as long as they could pay the rent and someone wanted their services.
Actually the particular rootikit in question doesn't replace pstools. I found a trojaned stock RH 6.2 machine at work, and the worm was trying to replicate itself. It was running "hack.sh" and "scan.sh". A little after that I found the rootkit in/dev/.lib
Hey get over yourself already. LAN parties are a lot more fun than just sitting in your study alone playing games. Capture the flag games are vastly more interesting when each team is in a room with each other, communicating efficiently, and everyone has a 1ms ping.
LAN parties are certainly a big improvement over the stlye of party that seems to engage most 20-30 year-old Americans: getting together to drink and make vapid conversation, then having the least drunk draggin the most drunk back to their homes.
Slashdot Mirror
Anyway my personal opinion is that HTML is wrong wrong wrong for this stuff. Generate TeX output and convert to postscript, or *roff, or generate postscript directly. If the target is dead trees you should use dead-tree-era technology.
My advice can only come from my own perspective. In any job, I insist that the duties are specifically detailed and known in advance. I do not put up with open-ended assignments, or requests to work outside of normall business hours which are brought up less than two weeks in advance. After all, I notify my employer two weeks before I intend to take vacation, or resign. If your job consists of monitoring operations at certain times of the day, week, or month, I would simply require that all those hours spent monitoring operations be compensated at the hourly rate. If you have to be on-call but not actively working, bill those hours at a reduced rate, but bill them just the same.
Tech workers who put up with a lot of BS should get paid for it. Auto mechanics and welders leave their work behind at 5:00 spot on, their brains synchronized precisely to the atomic clock of the Naval Observatory. The electricians and builders who work in my building work, by my honest observation, 2 hours per day. They certainly can't be reached outside of the 9:00-15:00 time window. If your employer wants you to spend your entire life at work, you should either say no or get paid accordingly.
I'm sure the density would be a lot better with the DL360, a 2xCPU SCSI machine in the same box as the 320. The Rackable stuff is 33% higher density than standard 1U machines, and the cabling is easier to manage.
The ironic shot of the guy about to steal the webcam out of jwz's club.
Sorry for the crass reply to myself, but I forgot to relay my latest anecdote. I started a new job a few weeks back. First day on the job, I notice a lot of wanky shit happening on a development machine. Took a closer look, and the machine had been rootkitted. Took a closer closer look, and EVERY machine had been rootkitted. They were all default RH 6.2 "Server" installations, and they had all been rooted through a bind hole. Slackware, of course, doesn't start bind unless you specifically add it to the init procedure. Solution: replace r00t hat boxes with Slackware boxes. No more worries :)
Actually, they will not be back for 7.2. David Cantrell said in this post that floppy installs are now gone. Also, if you look at -current, there are several packages which are too large for floppies. a1/modules.tgz is 5MB. n1/samba.tgz is 6MB.
Is it possible to install Red Hat without installing X? I tried once, on a Multia, but gave up after 30 minutes of trying. It seems like enabling any package brought in a dependency on X (and/or tcl/tk, WTF?)
Slackware no longer has the floppy-sized directories. Not even for the A series.
Slackware is also a handy base to start a new ditribution from. At my employers, I simply make new tag files, burn CDs, and I have automatic slack installers. At home, I have created an LDAP-authenticated distribution off Slackware. Again, no headaches, no unstable libraries, no balky compilers.
Yabbut, VA Linux is working on new machines using two AMD CPUs and the AMD 760MP chipset. The news has been on several hardware sites and VA employees have been posting to linux-kernel their patches to make the AMD 760 MP work well in Linux.
Good thing these defenders of peace and freedom require cookies before you can use their site. Otherwise, some hippie with cookies turned off might get to read the secret documents!
Slackware-current will work in that setup.
As you note, there were several problems. The original design was weak. Then the builder unilaterally decided to build the box beams the way they did. They also did not want to thread the entire length of the rod, so they changed the design to two rods. The hotel's prime contractor would not allow the engineering firm to be represented on site, for cost reasons. All of this added up to the disaster. The hotel was even fucked up before it was complete: 2000 square feet of roof collaped during construction. One of my old professors put up a page about it with lots of picures. Check out this picture of the distressed box beam from the walkway that didn't collapse.
errno.h was needed to declare errno. Otherwise, gcc won't build without warnings. If I were to just declare extern int errno, I might be stepping on an implementation that uses macros for errno.
I don't think that's really a bug, because if stdout is not valid, rc will be less than zero and errno will be set to EBADF. If stdout was a pipe that was closed, the program will receive SIGPIPE, which is not handled and thus the program will exit via the default handler.
That was a famous accident. The hotel was in kansas city, IIRC. The design of the original structure was sound: a long rod suspended from the roof supported two catwalks, by supporting them both from underneath. Thus, each catwalk support had to hold the load of a fraction of one catwalk. As the drawing passed from the chief engineer down to the detail draftsman, the design of one long rod was changed to two shorter rods. So the builder suspended the upper platform from the roof, and suspended the lower platform from the upper one. The supports for the upper catwalk were loaded with twice the load they were designed for, and the offset of the lower rods caused a torque unanticipated by the designer.
Maybe this is the ultimate version of hello world:
#include <stdio.h>
#include <errno.h>
#include <stdlib.h>
int main(void)
{
int rc;
rc = printf("Hello, World!\n");
if (rc < 0)
ex it(errno);
exit(0);
}
I love my TiBook, but it is not gaming machine. The Rage 128 is slow, slow, slow no matter if Steve Jobs gets up on stage and says its faster than any video card available for PCs.
I hope that it is replaced in the next year or two by a more sane directory structure. If I am trying to find a web page for a business, I imagine looking up the entry for Businesses/ACME Tools (of Hayward, California, USA), not www.acmetools.com, or maybe acme-tools.com, or haywardacme.com, or even getsometools.com! I can imagine looking up the entry for Publications/The Onion: America's Finest News Source.
If a system suh as this existed with 1) a defined network protocol, 2) an easy way to add and change entries, and 3) a widely-accepted algorithm for solving naming conflicts, I think it would handily replace the DNS as the primary lookup system. Of course DNS would still be used, for namenumber translation and whatnot.
You still didn't answer my question. What part of this has anything to do with the kernel? The kernel is process agnostic. You could build a system on top of the kernel that doesn't even use usernames and passwords.
What the hell are you talking about with number 5? The kernel doesn't give a rat fuck about console logins or any other kind of login. It just starts itself, and hands some filehandles off to an initial process. The kernel doesn't care what happens from there on.
Datapoints: PacBell service to my home in San Francisco reliably runs at 1.5 mpbs for $40/month. PacBell DSL to my former workplace routinely ran at 4 mbps for $200/month. Concentric DSL at my current workplace runs at a very bursty 100 kbps-ish.
The solution to this problem is very simple for cities. The local government, either the city or the county, needs to own the physical infrastructure. They need to run the wires or fibers into every building in town, and run the other end into large, empty, central offices. Then the building owner or whoever is at the end of the wire gets to decide what to hook up to his wire in the central office. If he chooses an Internet service provider, that ISP has to lease space in the publically owned central office and install its own equipment. There would not be any exclusion of anyone from central office space, as long as they could pay the rent and someone wanted their services.
Actually the particular rootikit in question doesn't replace pstools. I found a trojaned stock RH 6.2 machine at work, and the worm was trying to replicate itself. It was running "hack.sh" and "scan.sh". A little after that I found the rootkit in /dev/.lib
Hey get over yourself already. LAN parties are a lot more fun than just sitting in your study alone playing games. Capture the flag games are vastly more interesting when each team is in a room with each other, communicating efficiently, and everyone has a 1ms ping. LAN parties are certainly a big improvement over the stlye of party that seems to engage most 20-30 year-old Americans: getting together to drink and make vapid conversation, then having the least drunk draggin the most drunk back to their homes.