There are a good couple of reasons to run Linux instead of AIX on those machines... Examples? Sure! - You run mainly Linux on your machines, but want to have that RS/6000 (my case - A SparcStation 5, a Pentium and a RS/6000 model 570) - I know that Yellow Dog doesn't run on that model, but I wish some day a flavor of Linux will... - You prefer free software to propietary solutions, even if the cost is the same (as you say, the license travels with the hardware) - You like Gnome. You like WindowMaker. You like linuxconf. You hate CDE. You hate the AIX admin utils. etc.
Wow... I am amazed to see this word - Foonly:) I didn't know a Foonly was used for Tron - But back in 1983, being seven years old, I used regularly (once a week, maybe) the Foonly where my father worked, learnt some TeX and Emacs - and had no idea that 16 years later I'd still be using them... Well, anyway, the Foonly F2 was so important for me that now I like even more Tron! Heck, if I could get hold of a Tron movie in Mexico:)
The instructions (as they appear on a previous reply to your post) are quite straightforward. Now, about recompiling - It shouldn't take that long. If you just compiled 2.2.9, then this patch will only take a few seconds to get compiled, make will automatically notice this is the only file with a modification time newer than the object (compiled) code.
Nope - that doesn't work, at least on the motherboards I have tested it. I don't know why, but I think that a braindead engineer preferred the machine not to boot at all than to boot at power up in case the button got stuck:-/
ATX has a cleaner, more logical, less crammed design than AT. The changes (at least, the ones that spring to me now) are: - The CPU is at the top, not in front of the cards. Many (most? [all?]) current processors will discourage you from using full-size cards on an AT motherboard because they are just in the middle. - RAM is in a much more convenient place than just under the power supply, it is actually possible to fill your motherboard with RAM without unmounting the power supply:) - Printer, serial, keyboard, mouse, USB, video (optional) and audio (optional) ports are soldered on the motherboard, so you won't have 5 extra cables on your case, which makes up a cleaner design, easier access and maintenance. - IDE, SCSI and floppy ports are located actually near the disks, so your cables won't run all across the place - once again, cleaner. - The boxes are a bit wider. I don't know what is that for. - The fan on the power supply doesn't suck the hot air from the case, it blows fresh air in instead. What's the effect? I don't know. - ATX motherboards can implement wake up on ring, LAN activity, keyboard activity or port activity, they are continously powered - I don't know if this can damage your computer in the long run. To keep safe, if you plan not to turn on the PC, turn off the UPS or regulator.
I tend to prefer AT because it has been the standard for many years and still works very good, and I don't think most people will need this features. However, I just bought an ATX systems (they were out of AT motherboards and I needed the machine immediately), and assembling it was much easier. Also, it's easier to spot a misconnected cable. I think I will start recomending ATX now.
Where on the Kernel compile options can you find that? Do you have to recompile, or you can use some kind of "insmod poweroff"?
Each time more people are using ATX motherboards, and I think that most of us, when typing shutdown -h now mean I want to turn off the bloody system - why is it not enabled by default?
When you power on an ATX system's power supply, you see the LEDs on your keyboard and case flash for a fraction of a second. This is enough to tell the computer "Hey, do you want to wake up?", let it check in the BIOS settings how you programmed the boot process to be, and take the right decision.
It depends on the BIOS you have - If you happened to buy an AT/ATX compliant motherboard, you may be out of luck, because they often ship with BIOSes that don't know how to handle ATX power. On ATX motherboards, I have seen that Phoenix BIOS has the easiest to understand options, in the Boot section: - Whenever power is detected, turn the system on, regardless of how it was shut down. - If power is detected and the system was not shut down by software, turn the system on. If it was shut down properly, then leave it off - Whenever power is detected, go to sleep until someone presses the power button. (this is the default setting for most ATX machines)
What I did for my servers was to set them with the first option, and disconnected the frontal power button... The rear (real) power switch is harder to press by accident - and... Well, servers are meant to stay up, am I wrong?:)
No, the SMB protocol is staying with us. It will only implement and addition to be more like Novell's NDS - the Active Directory. I have used Windows NT 5.0 (beta), and is compatible with the existing, SMB-based networks. I think (if I recall correctly, I tested this software a while ago) you will have to point your client to a directory master (something like an enhanced WINS server), which will tell him which service corresponds to each object on the tree, and where (on the net) is it to be found.
It depends where do you want to run this server on: Given your case (you use Linux), then you don't need no special software. The Linux kernel itself has a SMB client for filesystems (you use it with the command smbmount, it's usually shipped as a compiled module so you won't even have to recompile).
If you happened to use an old version of Linux with no SMB support, or if you happened to run another OS (I mean, a Unix, Mac or Amiga OS), Samba ships with smbclient, which you can use more or less as an FTP equivalent for all SMB functions - it runs pretty smoothly, although smbmount is much better.
Would be too hard to make it real - What would happen if tomorrow morning you read in Slashdot about such a benchmark? I can assure you that thousands of people would be requesting more and more info from the free server, and hundreds would be sending DoS attacks to the NT one...:)
For the Spanish-speaking slashdotters, there is a short story by (I think) Jorge Luis Borges, called Funes el Memoriado - If you have read Borges, you know anything written by him is worth it. And this is a very good piece of work, just on this thread:)
While we're at it, I'd add that 20/20 memory would mean memorizing much more sensory input than our brains are equipped to handle normally. The result: probalby something on the order of madness, paralysis, or even death the instant you tried to remember any event.
Er... Think about a stack overflow in your brain! What if you suddenly try to remember when you tried to remember something? And then you try to remember that? No, thanks, I prefer having stuff written down!:)
Re:Best of both worlds?
on
BSD vs GPL
·
· Score: 1
You have *lots* of licenses to choose from - I think you are looking for something +- like the Artistic license, under which Perl is released. And, anyway, if you don't like a license, you can always modify it for your program!:)
(hell... I hope the GPL isn't GPL'd, because that would be recursive madness:):):) )
er... You can use it already, if I understood your question: Linux can natively run binaries for other OSs without modifications. On Intel, it can run iBCS binaries (SCO, mainly). On Sparc, it runs Solaris binaries, if you install some Solaris libraries. Work is under way to run even non-UNIX programs (Windows on i386, MacOS on PPC).
This problems caused by morons - like most of us
on
IP Address Shortage
·
· Score: 1
When I set up the network for the company I worked with until about 1 month ago, I was completely unaware of the situation or of any possible workarounds. I got a class C for (then) 60 PCs. They grew up to be 150 in a bit over a year. Well, they always had Internet access, but via a proxy (bandwith is too expensive in Mexico, I had to set up Squid with 2GB in order to make it work smoother). Later, I restricted most ports to all machines except for the servers - Well, I could have done it from the beginning with a 10.x.x.x or 192.168.x.x or any other public number... But, as I did not know this beforehand (as most sysadmins don't when they start sysadmining), it would be a PITA to change it all...
Yes, IPv6 will fix a LOT of things, but the FIRST thing is - READ before you set up. Search for optimal, ecological (i.e. - don't ask for what you won't need) solutions.
I mean... Well, the people they feature are the ones that really deserve to be featured - always have deserved and always will. I hate to admit it, but this is one of the places where both Gates and Stallman fit quite nicely together... But they left out a big amount of important people: Everyone before 1975. Everyone working for bigger computers. Maybe I misunderstood something, but I didnt see anywhere specified it was about personal computer history...
I didn't go through college...M��s-����^?*���>�?��
on
Do Geeks Need College?
·
· Score: 1
Now I work as the sysadmin of a campus of Mexico's main University:)
I never needed the paper, but (as you said) I may need it later, so I'm starting to study at a distance-learning university... Maybe that will be 6 months, and I'll have my B.A.
It seems RedHat is going to include KDE... Check out the RedHat5.9 FTP site. Yes, this is not a final distribution, but it seems that after Qt was put under the QPL (open source but not free software - Eric likes it, Richard doesn't) RedHat agreed to use it...
I have had great luck with XF86Setup, maybe it should be used as default instead of Xconfigurator...BTW, has any of you used EIT's EasyLinux? Seems to have a good, easy, graphical X configuration program.
About upgrading from another RedHat version, it usually goes smoothly - If you updated everything, there may not be a great deal of stuff to do:) But it is not problematic. Just watch the.log after installing - I skipped it once, and all of my security configuration became shit, because my config files were renamed.rpmsave (or something like that) and were replaced by stock configuration files!:-/
6) Have poll show up on the right only if you've not voted in it!
What do you think about having it this way: Once you voted, instead of showing the poll, to show the statistics? Would be neat! I mean, if I'm among the first voters, maybe I'll never find out - how often do you check polls after voting?
Slashdot Mirror
There are a good couple of reasons to run Linux instead of AIX on those machines... Examples? Sure!
- You run mainly Linux on your machines, but want to have that RS/6000 (my case - A SparcStation 5, a Pentium and a RS/6000 model 570) - I know that Yellow Dog doesn't run on that model, but I wish some day a flavor of Linux will...
- You prefer free software to propietary solutions, even if the cost is the same (as you say, the license travels with the hardware)
- You like Gnome. You like WindowMaker. You like linuxconf. You hate CDE. You hate the AIX admin utils.
etc.
Wow... I am amazed to see this word - Foonly :) I didn't know a Foonly was used for Tron - But back in 1983, being seven years old, I used regularly (once a week, maybe) the Foonly where my father worked, learnt some TeX and Emacs - and had no idea that 16 years later I'd still be using them... Well, anyway, the Foonly F2 was so important for me that now I like even more Tron! Heck, if I could get hold of a Tron movie in Mexico :)
The instructions (as they appear on a previous reply to your post) are quite straightforward. Now, about recompiling - It shouldn't take that long. If you just compiled 2.2.9, then this patch will only take a few seconds to get compiled, make will automatically notice this is the only file with a modification time newer than the object (compiled) code.
Nope - that doesn't work, at least on the motherboards I have tested it. I don't know why, but I think that a braindead engineer preferred the machine not to boot at all than to boot at power up in case the button got stuck :-/
ATX has a cleaner, more logical, less crammed design than AT. The changes (at least, the ones that spring to me now) are: :)
- The CPU is at the top, not in front of the cards. Many (most? [all?]) current processors will discourage you from using full-size cards on an AT motherboard because they are just in the middle.
- RAM is in a much more convenient place than just under the power supply, it is actually possible to fill your motherboard with RAM without unmounting the power supply
- Printer, serial, keyboard, mouse, USB, video (optional) and audio (optional) ports are soldered on the motherboard, so you won't have 5 extra cables on your case, which makes up a cleaner design, easier access and maintenance.
- IDE, SCSI and floppy ports are located actually near the disks, so your cables won't run all across the place - once again, cleaner.
- The boxes are a bit wider. I don't know what is that for.
- The fan on the power supply doesn't suck the hot air from the case, it blows fresh air in instead. What's the effect? I don't know.
- ATX motherboards can implement wake up on ring, LAN activity, keyboard activity or port activity, they are continously powered - I don't know if this can damage your computer in the long run. To keep safe, if you plan not to turn on the PC, turn off the UPS or regulator.
I tend to prefer AT because it has been the standard for many years and still works very good, and I don't think most people will need this features. However, I just bought an ATX systems (they were out of AT motherboards and I needed the machine immediately), and assembling it was much easier. Also, it's easier to spot a misconnected cable. I think I will start recomending ATX now.
Where on the Kernel compile options can you find that? Do you have to recompile, or you can use some kind of "insmod poweroff"?
Each time more people are using ATX motherboards, and I think that most of us, when typing shutdown -h now mean I want to turn off the bloody system - why is it not enabled by default?
When you power on an ATX system's power supply, you see the LEDs on your keyboard and case flash for a fraction of a second. This is enough to tell the computer "Hey, do you want to wake up?", let it check in the BIOS settings how you programmed the boot process to be, and take the right decision.
It depends on the BIOS you have - If you happened to buy an AT/ATX compliant motherboard, you may be out of luck, because they often ship with BIOSes that don't know how to handle ATX power. On ATX motherboards, I have seen that Phoenix BIOS has the easiest to understand options, in the Boot section:
:)
- Whenever power is detected, turn the system on, regardless of how it was shut down.
- If power is detected and the system was not shut down by software, turn the system on. If it was shut down properly, then leave it off
- Whenever power is detected, go to sleep until someone presses the power button. (this is the default setting for most ATX machines)
What I did for my servers was to set them with the first option, and disconnected the frontal power button... The rear (real) power switch is harder to press by accident - and... Well, servers are meant to stay up, am I wrong?
No, the SMB protocol is staying with us. It will only implement and addition to be more like Novell's NDS - the Active Directory. I have used Windows NT 5.0 (beta), and is compatible with the existing, SMB-based networks. I think (if I recall correctly, I tested this software a while ago) you will have to point your client to a directory master (something like an enhanced WINS server), which will tell him which service corresponds to each object on the tree, and where (on the net) is it to be found.
It depends where do you want to run this server on: Given your case (you use Linux), then you don't need no special software. The Linux kernel itself has a SMB client for filesystems (you use it with the command smbmount, it's usually shipped as a compiled module so you won't even have to recompile).
If you happened to use an old version of Linux with no SMB support, or if you happened to run another OS (I mean, a Unix, Mac or Amiga OS), Samba ships with smbclient, which you can use more or less as an FTP equivalent for all SMB functions - it runs pretty smoothly, although smbmount is much better.
Would be too hard to make it real - What would happen if tomorrow morning you read in Slashdot about such a benchmark? I can assure you that thousands of people would be requesting more and more info from the free server, and hundreds would be sending DoS attacks to the NT one... :)
For the Spanish-speaking slashdotters, there is a short story by (I think) Jorge Luis Borges, called Funes el Memoriado - If you have read Borges, you know anything written by him is worth it. And this is a very good piece of work, just on this thread :)
Wow... If I only could have given boolean answers to my high school tests, I would have done much better! :)
While we're at it, I'd add that 20/20 memory would mean memorizing much more sensory input than our brains are equipped to handle
:)
normally. The result: probalby something on the order of madness, paralysis, or even death the instant you tried to remember any event.
Er... Think about a stack overflow in your brain! What if you suddenly try to remember when you tried to remember something? And then you try to remember that? No, thanks, I prefer having stuff written down!
You have *lots* of licenses to choose from - I think you are looking for something +- like the Artistic license, under which Perl is released. And, anyway, if you don't like a license, you can always modify it for your program! :)
:) :) :) )
(hell... I hope the GPL isn't GPL'd, because that would be recursive madness
er... You can use it already, if I understood your question: Linux can natively run binaries for other OSs without modifications. On Intel, it can run iBCS binaries (SCO, mainly). On Sparc, it runs Solaris binaries, if you install some Solaris libraries. Work is under way to run even non-UNIX programs (Windows on i386, MacOS on PPC).
When I set up the network for the company I worked with until about 1 month ago, I was completely unaware of the situation or of any possible workarounds. I got a class C for (then) 60 PCs. They grew up to be 150 in a bit over a year. Well, they always had Internet access, but via a proxy (bandwith is too expensive in Mexico, I had to set up Squid with 2GB in order to make it work smoother). Later, I restricted most ports to all machines except for the servers - Well, I could have done it from the beginning with a 10.x.x.x or 192.168.x.x or any other public number... But, as I did not know this beforehand (as most sysadmins don't when they start sysadmining), it would be a PITA to change it all...
Yes, IPv6 will fix a LOT of things, but the FIRST thing is - READ before you set up. Search for optimal, ecological (i.e. - don't ask for what you won't need) solutions.
I mean... Well, the people they feature are the ones that really deserve to be featured - always have deserved and always will. I hate to admit it, but this is one of the places where both Gates and Stallman fit quite nicely together... But they left out a big amount of important people: Everyone before 1975. Everyone working for bigger computers. Maybe I misunderstood something, but I didnt see anywhere specified it was about personal computer history...
Now I work as the sysadmin of a campus of Mexico's main University :)
I never needed the paper, but (as you said) I may need it later, so I'm starting to study at a distance-learning university... Maybe that will be 6 months, and I'll have my B.A.
the GPL was tailored a long time ago. Time for it to include all the new stuff to protect software from being non-free. I'm in! :)
Well, my computer has a K6-II and the Pentium II I also use around here are MUCH slower... I became a convinced AMD fan.
I really doubt it would get to the POST check - if it didn't make some nice sparkles, that is... The circuitry is simply non compatible.
It seems RedHat is going to include KDE... Check
out the RedHat5.9 FTP site. Yes, this is not a
final distribution, but it seems that after Qt
was put under the QPL (open source but not free
software - Eric likes it, Richard doesn't)
RedHat agreed to use it...
I have had great luck with XF86Setup, maybe it should be used as default instead of Xconfigurator...BTW, has any of you used EIT's EasyLinux? Seems to have a good, easy, graphical X configuration program.
:) But it is not problematic. Just watch the .log after installing - I skipped it once, and all of my security configuration became shit, because my config files were renamed .rpmsave (or something like that) and were replaced by stock configuration files! :-/
About upgrading from another RedHat version, it usually goes smoothly - If you updated everything, there may not be a great deal of stuff to do
6) Have poll show up on the right only if you've not voted in it!
What do you think about having it this way: Once you voted, instead of showing the poll, to show the statistics? Would be neat! I mean, if I'm among the first voters, maybe I'll never find out - how often do you check polls after voting?