What is lzip? Glad you asked. Lzip is an advanced file compression utility that generates smaller file sizes than either gzip or bzip2, and does so much faster. Lzip can achieve these goals because it it based on a so-called "lossy" compression scheme (most other utilties make use of slower, less efficient "lossless" compression). For more information, you can consult the Frequently Asked Questions list. Or, you can dive right in, grab the 1.0 tarball and start reducing your bloated files down to 10%, 15%, in some cases 0% of their original size!
This may sound like a plug for the RHN Enterprise service, because it is. I got in this morning at around 7:50, checked the status of all of my Red Hat servers through the web page and saw that there was an urgent update available for OpenSSL. I clicked 3 times and all of them were scheduled to get the update the next time they checked in.
It's now 9:44 and all of my servers are patched. It took me 5 seconds to schedule it, and just drank coffee and read/. as it happened.
It's well worth it. We're all sold on it, and the Novell guys are envious.
> This means you can install stuff from the > source, or even just copy files from a > friends computer without worrying about your > package manager database getting out of synch.
So say I copy package A from another machine. I then install package B, which requires something that package A has. Your script just sees that it exists and continues on with the install. Then I uninstall package A. Without a database to keep track of dependencies, how do you know what will break by doing an uninstall?
I'm curious, what exactly can't you do yourself on a Red Hat box?
Just because they include some tools to try and be helpful to regular users doesn't mean that you have to take advantage of them. I can configure my install to do just what I want. If I'm setting up a server, it gets no X at all. No fluff. There is no problem in hand editing any configuration files. No problem installing anything out there. You're not restricted in any way that I can see.
You made the statement, so please tell me, what task does Red Hat force you to use their tools to accomplish it rather than doing it yourself?
Don't make things easy so people are forced to learn how to do things on their own in order to use their computer? That's insane.
Where do you draw the line? Maybe I think you're an idiot because you don't do everything in binary. Yeah, that's it. You've just had it too cushy with your fancy assembly language.
Let's force people to interact via a series of switches mounted on the front of their box. That way we'll be sure that they really understand exactly what is going on. If you don't want to exert the effort required to master such a system, screw you. You're not worthy anyway. No great loss.
Maybe I'm being a bit harsh, but does this make sense?
Use the palm of your hand under the pinky to hit the control key without ever moving from the home keys. This works great, but it's even better if you build up the height of the front of the control key with a bit of electrical tape.
I use vi for just about everything and use the CTRL-[ keystroke instead of having to constantly reach up for the ESC key. Using your hand to hit CTRL rather than a finger becomes second nature pretty quickly.
Apparently the corporation you admin for isn't very big. In almost any organization that depends on it's computer resources, a fee per server wouldn't even raise a question. Would I pay for UL when I could get Red Hat for free? Only if there was some credible reason to do so. But I assure you, If UL was more stable, or robust, or whatever, I would be the first in line to pay for. Most professional sysadmins would.
When I worked for small businesses, I ran Linux on their servers to save money. Now that I'm no longer in that situation and have a little money to spread around, I still choose to run Linux because it's the best tool for the job.
How about a lifelike 3d holographic image of delicious looking food sitting in the fridge. You reach for it and, of course, your hand passes right through it. Then the fridge cheerfully informs you that he can arrange to have the real thing delivered in a couple of hours.
Doesn't BIOS stand for Basic Input Output System? A network (corporate intranet, Internet, etc) today is arguably a Basic means of I/O. I assume it will be even moreso in the future.
I can invision buying a pc at Wal*Mart with no OS installed, getting home, plugging in, turning it on... it connects to a website where I'm asked what OS I want to install. Or better yet, what OS I want to run remotely *for this session*. All or most of my data is stored in a high security SAN somewhere and by its nature, is editable equally by any competitors application. I can choose to save things locally if I want. It would be my choice.
Maybe we just need to expand our definition and understand that we don't need to limit Basic I/O to local peripherals any more.
Can we fully utilize (or visualize) it's potential now? Maybe not, but this one of many baby steps to the standard PC in the future. I don't think they really expect you to do your daily browsing with this thing. It's the bigger picture.
These shots are very nice, but the window close buttons in the top right hand corner illustrate a personal frustration of mine. I like my close button to be all the way in the corner of the window, up to the last pixel, so when I have a window maximized and decide I want to close it I can move the mouse to the top right edge of the screen and click without looking at it. Why would I want to aim at a little round button? I know I could use the keyboard shortcuts, and I do, but sometimes I've got that mouse in hand and...
Yeah, well I had SFD 1000's (1 meg 5 1/4") daisy chained to offer more storage than just about any C64 BBS around. I then moved to a Lt. Kernel! This was a 10Meg hard drive that connected to the 64 via the cartridge slot. $1500! Pretty expensive for a high school kid. I ran and contributed a bit to C-Net, of course.
Speaking of drives on the 64, I also had an Indus GT. Sleek little black 5 1/4". It worked for about 3 months until it needed a head alignment. Guess it was too many runs with Error 29 Maker or 4 minute backup.
Ah, oh well, back to work... I never thought I'd be getting paid to do what I did back then for free.;) We're pretty lucky.
Sorry if I wasn't clear. I was saying the problem was with PC hardware (usually containing an Intel CPU, or at least something compatible). Even at the high end, "server class" PC kit just isn't generally the same quality as other options.
It amazes me that someone would moderate this up when you consider that in order to get moderator points you have had to have been around here for awhile and the moderator should know that a) this kind of thing gets posted all the time and b) this is answered in the FAQ.
Geez. If you don't want to moderate correctly, opt out.
Yeah, like having to change out all the fans on the pc's because they were defective? Amidst all the talk about how great Linux was doing for them, that was priceless. I have only a bit of experience on SGI machines, but I'm pretty sure that you wouldn't get a shipment of them with broken fans on every unit. Is the "tel" portion of "Lintel" really the part that isn't ready for the enterprise?
Of course, with the money they are saving, changing a few fans and having a few hot spare workstations in a closet may be very well worth it.
So who gets the money during pledge weeks? Seriously. I'd like to know how they handle that. Even if they don't have the local people begging, most of the shows talk about it and certainly alter their programming to allow time for it.
Yeah, I listen to way too much public radio. But that's not a bad thing...
This is very true. I had a really nice radio installed in my Miata... Almost the whole front was a blue LCD. It looked cool in the store.
Talk about horrid! At night it lit up the entire interior of that little car with a bright blue glow. On trips outside of city lights I had a bandana that I would use to cover it up because it was so distracting.
Now I've got a bigger car, a I guess a little better sense. You just don't think about things like that when you're in the store.
(good) Radio is not always available. I would have been the first in line to get one of these if my job hadn't changed. I spent many many hours driving betweeen rural remote sites where you couldn't get anything on the radio except preachers and country music for 6 hours each way.
Music is fine, and I do have a couple of options for listening to mp3's in my car, but when you spend more hours on the road than you do at the client's site 5 or 6 days a week, music gets kind of boring.
Getting Linux into people's hands this way sounds like a good idea, until he tries to install the other software he bought along with the computer. We don't want to force Linux on anyone. People need to make an educated decision to try it out. They need to be aware of not only the advantages, but some of the caveats. Otherwise, they will get a really bad first impression of Linux that may last a long time.
"Yeah, my machine had that linux thing on it when I bought it and it wouldn't even install Quicken. Fortunately my neighbor's kid was able to come right over and install Windows from his CD."
You could even change your password with this scheme. Give the lawyer "A53vP" and give the other half to a coworker, or several even, each time you change it.
Each month we had a meeting that brought together our company's Sr. SysAdmins from all of the remote locations so we could discuss plans in person (but mainly as an excuse for a day to relax). We would always joke about what a mess the company would be in if the van we packed into after each meeting to go get Chinese were to plummet off of a bridge.
Fortunately, it never happened to us, but I'm sure it's happened somewhere.
Like George from Seinfeld saying that we were due for a whole baseball team to be killed in a plane crash.
I'd be afraid (or happy, actually) that I would outlive the service. At $29.95 a year I'd rather just print out all this information, put it a safety deposit box, and give a key to someone I could trust.
Slashdot Mirror
From the site:
What is lzip?
Glad you asked. Lzip is an advanced file compression utility that generates smaller file sizes than either gzip or bzip2, and does so much faster. Lzip can achieve these goals because it it based on a so-called "lossy" compression scheme (most other utilties make use of slower, less efficient "lossless" compression). For more information, you can consult the Frequently Asked Questions list. Or, you can dive right in, grab the 1.0 tarball and start reducing your bloated files down to 10%, 15%, in some cases 0% of their original size!
Did you check out their sizing guide? For some reason that disturbed me. I had to switch to 1600x1200 before I felt better about myself.
This may sound like a plug for the RHN Enterprise service, because it is. I got in this morning at around 7:50, checked the status of all of my Red Hat servers through the web page and saw that there was an urgent update available for OpenSSL. I clicked 3 times and all of them were scheduled to get the update the next time they checked in.
/. as it happened.
It's now 9:44 and all of my servers are patched. It took me 5 seconds to schedule it, and just drank coffee and read
It's well worth it. We're all sold on it, and the Novell guys are envious.
> This means you can install stuff from the
> source, or even just copy files from a
> friends computer without worrying about your
> package manager database getting out of synch.
So say I copy package A from another machine. I then install package B, which requires something that package A has. Your script just sees that it exists and continues on with the install. Then I uninstall package A. Without a database to keep track of dependencies, how do you know what will break by doing an uninstall?
I'm curious, what exactly can't you do yourself on a Red Hat box?
Just because they include some tools to try and be helpful to regular users doesn't mean that you have to take advantage of them. I can configure my install to do just what I want. If I'm setting up a server, it gets no X at all. No fluff. There is no problem in hand editing any configuration files. No problem installing anything out there. You're not restricted in any way that I can see.
You made the statement, so please tell me, what task does Red Hat force you to use their tools to accomplish it rather than doing it yourself?
Don't make things easy so people are forced to learn how to do things on their own in order to use their computer? That's insane.
Where do you draw the line? Maybe I think you're an idiot because you don't do everything in binary. Yeah, that's it. You've just had it too cushy with your fancy assembly language.
Let's force people to interact via a series of switches mounted on the front of their box. That way we'll be sure that they really understand exactly what is going on. If you don't want to exert the effort required to master such a system, screw you. You're not worthy anyway. No great loss.
Maybe I'm being a bit harsh, but does this make sense?
So who wins when it's another car that gets in the way?
Do you have a model number or something on the keyboard with the eraser mouse? I'd really like to get one of these.
Use the palm of your hand under the pinky to hit the control key without ever moving from the home keys. This works great, but it's even better if you build up the height of the front of the control key with a bit of electrical tape.
I use vi for just about everything and use the CTRL-[ keystroke instead of having to constantly reach up for the ESC key. Using your hand to hit CTRL rather than a finger becomes second nature pretty quickly.
Apparently the corporation you admin for isn't very big. In almost any organization that depends on it's computer resources, a fee per server wouldn't even raise a question. Would I pay for UL when I could get Red Hat for free? Only if there was some credible reason to do so. But I assure you, If UL was more stable, or robust, or whatever, I would be the first in line to pay for. Most professional sysadmins would.
When I worked for small businesses, I ran Linux on their servers to save money. Now that I'm no longer in that situation and have a little money to spread around, I still choose to run Linux because it's the best tool for the job.
How about a lifelike 3d holographic image of delicious looking food sitting in the fridge. You reach for it and, of course, your hand passes right through it. Then the fridge cheerfully informs you that he can arrange to have the real thing delivered in a couple of hours.
Doesn't BIOS stand for Basic Input Output System? A network (corporate intranet, Internet, etc) today is arguably a Basic means of I/O. I assume it will be even moreso in the future.
I can invision buying a pc at Wal*Mart with no OS installed, getting home, plugging in, turning it on... it connects to a website where I'm asked what OS I want to install. Or better yet, what OS I want to run remotely *for this session*. All or most of my data is stored in a high security SAN somewhere and by its nature, is editable equally by any competitors application. I can choose to save things locally if I want. It would be my choice.
Maybe we just need to expand our definition and understand that we don't need to limit Basic I/O to local peripherals any more.
Can we fully utilize (or visualize) it's potential now? Maybe not, but this one of many baby steps to the standard PC in the future. I don't think they really expect you to do your daily browsing with this thing. It's the bigger picture.
These shots are very nice, but the window close buttons in the top right hand corner illustrate a personal frustration of mine. I like my close button to be all the way in the corner of the window, up to the last pixel, so when I have a window maximized and decide I want to close it I can move the mouse to the top right edge of the screen and click without looking at it. Why would I want to aim at a little round button? I know I could use the keyboard shortcuts, and I do, but sometimes I've got that mouse in hand and...
Yeah, well I had SFD 1000's (1 meg 5 1/4") daisy chained to offer more storage than just about any C64 BBS around. I then moved to a Lt. Kernel! This was a 10Meg hard drive that connected to the 64 via the cartridge slot. $1500! Pretty expensive for a high school kid. I ran and contributed a bit to C-Net, of course.
;) We're pretty lucky.
Speaking of drives on the 64, I also had an Indus GT. Sleek little black 5 1/4". It worked for about 3 months until it needed a head alignment. Guess it was too many runs with Error 29 Maker or 4 minute backup.
Ah, oh well, back to work... I never thought I'd be getting paid to do what I did back then for free.
Didn't SAM stand for Software Automated Mouth or something like that? Good times. SAM, elephant disks, and my koalapad!
Sorry if I wasn't clear. I was saying the problem was with PC hardware (usually containing an Intel CPU, or at least something compatible). Even at the high end, "server class" PC kit just isn't generally the same quality as other options.
It amazes me that someone would moderate this up when you consider that in order to get moderator points you have had to have been around here for awhile and the moderator should know that a) this kind of thing gets posted all the time and b) this is answered in the FAQ.
Geez. If you don't want to moderate correctly, opt out.
Yeah, like having to change out all the fans on the pc's because they were defective? Amidst all the talk about how great Linux was doing for them, that was priceless. I have only a bit of experience on SGI machines, but I'm pretty sure that you wouldn't get a shipment of them with broken fans on every unit. Is the "tel" portion of "Lintel" really the part that isn't ready for the enterprise?
Of course, with the money they are saving, changing a few fans and having a few hot spare workstations in a closet may be very well worth it.
So who gets the money during pledge weeks? Seriously. I'd like to know how they handle that. Even if they don't have the local people begging, most of the shows talk about it and certainly alter their programming to allow time for it.
Yeah, I listen to way too much public radio. But that's not a bad thing...
This is very true. I had a really nice radio installed in my Miata... Almost the whole front was a blue LCD. It looked cool in the store.
Talk about horrid! At night it lit up the entire interior of that little car with a bright blue glow. On trips outside of city lights I had a bandana that I would use to cover it up because it was so distracting.
Now I've got a bigger car, a I guess a little better sense. You just don't think about things like that when you're in the store.
.
(good) Radio is not always available. I would have been the first in line to get one of these if my job hadn't changed. I spent many many hours driving betweeen rural remote sites where you couldn't get anything on the radio except preachers and country music for 6 hours each way.
Music is fine, and I do have a couple of options for listening to mp3's in my car, but when you spend more hours on the road than you do at the client's site 5 or 6 days a week, music gets kind of boring.
.
Getting Linux into people's hands this way sounds like a good idea, until he tries to install the other software he bought along with the computer. We don't want to force Linux on anyone. People need to make an educated decision to try it out. They need to be aware of not only the advantages, but some of the caveats. Otherwise, they will get a really bad first impression of Linux that may last a long time.
"Yeah, my machine had that linux thing on it when I bought it and it wouldn't even install Quicken. Fortunately my neighbor's kid was able to come right over and install Windows from his CD."
You could even change your password with this scheme. Give the lawyer "A53vP" and give the other half to a coworker, or several even, each time you change it.
vmFJ3A53vp
3jadmA53vp
erMIeA53vp
MMKkeA53vp
Each month we had a meeting that brought together our company's Sr. SysAdmins from all of the remote locations so we could discuss plans in person (but mainly as an excuse for a day to relax). We would always joke about what a mess the company would be in if the van we packed into after each meeting to go get Chinese were to plummet off of a bridge.
Fortunately, it never happened to us, but I'm sure it's happened somewhere.
Like George from Seinfeld saying that we were due for a whole baseball team to be killed in a plane crash.
I'd be afraid (or happy, actually) that I would outlive the service. At $29.95 a year I'd rather just print out all this information, put it a safety deposit box, and give a key to someone I could trust.