ral

Don't have the information on the breakddown in sales. Willing ot be the corporate sales were mainly servers.

Thanks aru, am there now. In general though, I don't want to give viewers too much history. Frankly, I think what they really want to know is it free, is it easy to use, can I do my work on it, were can I get it...etc. It is likely that people will think GNU/Linux and Linux are different things. After reading the fact, I realize that the GNU Project may not have gotten the credit they deserve, but it may be too late to remedy that now. Maybe I could put a development history section. I know this may not want to be politically correct but... I want to keep things really simple. ----- 3lade I still use Windows myself (98SE dual boot)...for my games and Quicktime :) No I don't intend to place any anti MS stuff...but referrences to Apple and MS will probobly necessary. If you tell someone Linux is an OS... the nest question is "What is an OS?" --- "Err like Windows?". A know a fair number of people who cannot even distinguish Windows from MS Office. ------ tyme I plan to take the Linux works, is compatible and is free or cheaper :) I don't have to tell an MS user that Windows is not stable. But I should tell him that Linux is. I should also inform them about Linux's (and Linux apps) weaknesses so that they don't get shocked when they use it. ----- counterspy Thanks counterspy. ---- By the way, I use RH8...so the examples and the screens are going to come from a default RH8 install.

Yes, I think your right Counterspy.

Oh oh, I don't even know what K3B is But I plan to do a "shallow" simple site and let it grow as I grow. Well, maybe I can look around this post for volunteers too...

I found a beta drivers for the Intel 536ep modem here: http://honestarchina.www80.cn4e.com/englis...ICE/driver.html and here: http://linmodems.technion.ac.il/packages/Intel/ On the second link there is a driver called: Intel-536ep-453-M90.tgz I think this is probably the Mandrake 9 driver, but am not sure. Here is the readme says it supports Mandrake, but the readme appears ot be a generic one (for RH. ML and SuSE) and does not specifically mention ML9.

http://www.newsfactor.com/perl/story/20404.html Going after the enterprise market is good. 93% of of RedHat sales is to this sector.

Sorry about the misquote coverup. "1. I used to have the entry MAILTO=root in the crontab file, so cron could email root about the status of tasks it performed. 2. lpd sometimes emails root, eg, about dequeued jobs." I don't understand all this yet... but I will keep them both off for now and if I encounter any problems will turn postfix back on again.

Thanks aru. That kind of feedback is what I am hoping for. Please suggest a revised desicription. Soulse. This is the intro part. I will build a section which shows in detail the Linux Window managers and apps and subliminaly show why Linux is better. :) I got my software in 1999 and have been using it since. I was planning to upgrade last June 2002 (Windows XP, Office XP, Norton System Works 2002). Klez hit me so I decided to try Linux. It saved me a bunch of cash. Now I can still use my older software (Win98) for games and have updated software for everything else (by doing everything on Linux except play games a view quicktime). I think showing people what a Linux distro is and hitting on stability and security from viruses will win a few converts. It will mainly be a show and tell site. As for advice help and the like I intend to send them here (and the Mandrake Experience, LinuxISO ... etc.). :) :) :)

This seems to be a common problem: http://www.redhat.com/bugzilla/long_list.c...i?buglist=54905 Try the solutions near the bottom of the linked page. Goodluck.

I found a page with Linux modem drivers for your modem. I hope this helps. http://www.intel.com/design/modems/support...ivers_linux.htm

Whats interesting is that it is based on Konqueror and not Mozilla. Apple helping with Konqueror development will make the browser market very interesting indeed.

Oh my... Mandrake 9.1 = Microsoft Linux XP Professional. Seriously, I second the request for some links please.

Part of the intro to Linux: "What is Linux? Linux is a Unix-type operating system originally created by Linus Torvalds with the assistance of developers around the world. Various companies and groups have developed their own versions of Linux. Why use Linux? Well for one, there are several versions of Linux which are available for free. These free versions of Linux are not crippled versions of the operating system but are powerful fully functional versions which can operate as a workstation, email server, web server, FTP server, file sharing server and print server. Most operating systems are released with a basic edition and a professional version. The Linux operating systems available on the net for free are equivalent to professional edition operating systems. In the same way that the software can be obtained freely, updates to the software are also available for free. Linux operating systems are known for being very stable platforms. They can run for as long as a year without hanging or crashing. They are also resistant to viruses. With over 70,000 viruses and other malicious software in existence, Linux users surf the web and go about their business without using virus scanners. For Linux, viruses are non-issue. Finally, support. Linux distributions are supported by the companies that make them and by the various communities of users through email, messageboards, IRC and other intenret media. Request for support are typically answered in a few hours or a day or two, and can be had for free. It just a matter of knowing where to go. What is a Linux distribution? Most operating systems today, like Microsoft Windows XP Home and Professional Editions and Apples Mac OS X, are bundled with additional applications like a web browser, email client, a basic text editor, image viewer and editor, and other applications. However, the included applications are not sufficient for serious work and hence you have to add an office suit, like Microsoft Office, if you intend to use your computer to create text documents, spreadsheets and presentations. If you intend to do graphics work you need to add a graphic editor like Adobe's Photoshop. Linux operating systems are released as "Distributions." A Linux distribution does not only comes pack with a web browser, email client and the basic applications found in other applications, but also include a powerful office suit capable of creating complex documents, spreadsheets and presentations. Should you need to do graphics work a Linux distribution also includes a very powerful graphics editor capable of creating very complex images." I would appreicate any comments, advice or flames :)

Pardon my ignorance, but when does an email client "send messages to root" and why?

http://firstmonday.org/issues/issue8_1/nic...hols/index.html

Thanks. Postfix and sendmail disabled. :)

Are there any instructions for configuring it to work it OpenOffice. The manuak at the site uses StarOffice as an example. Pretty similar but somewhere along the way I messed up.

Okay, so if I understood you correctly (I use Mozilla's Messenger), I don't really need either sendmail or postfix to send and receive emails. Is it better if I just turned both of the off? Tips on how to do that would be appreciated.

I play RTCW and Quake II on Linux. Both run natively. I have and old copy of Win98 which I use to play Windows games and run an apt which is not yet Linux compatible. I forgot, I use it to run Quicktime too. I love OFP too. I don't think there is a Linux port or emulator for it right now. Not too fond of wine since games usually run slower when using wine. So if you have an old copy of Windows lying around, maybe your best off dual booting.

http://techupdate.zdnet.com/techupdate/sto...2907876,00.html Besides I MS Sysadmin abilities would be limited to the software he is working on. He cannot modify and customize MS Windows as a Linux Sysadmin could modify and customize Linux.

Good to have you both back. :D

Okay did the whole thing again: [root@localhost root]# sensors-detect This program will help you to determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have done a `make install', issued a `depmod -a' and made sure `/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate module path before you can use some functions of this utility. Read doc/modules for more information. Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files if you do not have them already. If you have patched your kernel and have some drivers built-in you can safely answer NO if asked to load some modules. In this case, things may seem a bit confusing, but they will still work. IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW! IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning the bus will break your thinkpad forever! We can start with probing for (PCI) I2C or SMBus adapters. You do not need any special privileges for this. Do you want to probe now? (YES/no): YES Probing for PCI bus adapters... Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595 Use driver `i2c-riva' for device 01:00.0: GeForce2 MX Probe succesfully concluded. We will now try to load each adapter module in turn. Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): YES /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o failed /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595 failed Loading failed ()... skipping. Load `i2c-riva' (say NO if built into your kernel)? (YES/no): YES modprobe: Can't locate module i2c-riva Loading failed ()... skipping. ** Note: i2c-riva module is available at ** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml Do you now want to be prompted for non-detectable adapters? (yes/NO): YES Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): YES /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o failed /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: insmod i2c-elektor failed Loading failed ()... skipping. Load `i2c-elv' (say NO if built into your kernel)? (YES/no): YES /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o failed /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: insmod i2c-elv failed Loading failed ()... skipping. Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): YES Module loaded succesfully. Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): YES /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o failed /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: insmod i2c-velleman failed Loading failed ()... skipping. To continue, we need module `i2c-dev' to be loaded. If it is built-in into your kernel, you can safely skip this. i2c-dev is not loaded. Do you want to load it now? (YES/no): YES Module loaded succesfully. We are now going to do the adapter probings. Some adapters may hang halfway through; we can't really help that. Also, some chips will be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. That often includes address 0x69 (clock chip). Some chips are also accessible through the ISA bus. ISA probes are typically a bit more dangerous, as we have to write to I/O ports to do this. Do you want to scan the ISA bus? (YES/no): YES Probing for `National Semiconductor LM78' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `National Semiconductor LM78-J' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `National Semiconductor LM79' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83781D' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83782D' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83627HF' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83697HF' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Silicon Integrated Systems SIS5595' Trying general detect... Success! (confidence 9, driver `sis5595') Probing for `VIA Technologies VT82C686 Integrated Sensors' Trying general detect... Failed! Probing for `ITE IT8705F / IT8712F / SiS 950' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `IPMI BMC KCS' Trying address 0x0ca0... Failed! Probing for `IPMI BMC SMIC' Trying address 0x0ca8... Failed! Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `sis5595' (should be inserted): Detects correctly: * ISA bus, undetermined address (Busdriver `i2c-isa') Chip `Silicon Integrated Systems SIS5595' (confidence: 9) I will now generate the commands needed to load the I2C modules. Sometimes, a chip is available both through the ISA bus and an I2C bus. ISA bus access is faster, but you need to load an additional driver module for it. If you have the choice, do you want to use the ISA bus or the I2C/SMBus (ISA/smbus)? ISA WARNING! If you have some things built into your kernel, the below list will contain too many modules. Skip the appropriate ones! To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers modprobe i2c-isa # I2C chip drivers modprobe sis5595 #----cut here---- To make the sensors modules behave correctly, add these lines to either /etc/modules.conf or /etc/conf.modules: #----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here---- After adding the appropriate lines and a reboot: [ral@localhost ral]$ sensors sis5595-isa-8008 Adapter: ISA adapter Algorithm: ISA algorithm VCore 1: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM VCore 2: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM +3.3V: +4.08 V (min = +4.08 V, max = +4.08 V) ALARM +5V: +6.85 V (min = +6.85 V, max = +6.85 V) ALARM fan1: 0 RPM (min = 0 RPM, div = 8) ALARM fan2: 0 RPM (min = 0 RPM, div = 8) ALARM temp: +51?C (limit = +51?C, hysteresis = +51?C) ALARM alarms: Board temperature input (usually LM75 chips) ALARM [ral@localhost ral]$ Run sensors detect again and selected SMBus: [root@localhost root]# sensors-detect This program will help you to determine which I2C/SMBus modules you need to load to use lm_sensors most effectively. You need to have done a `make install', issued a `depmod -a' and made sure `/etc/conf.modules' (or `/etc/modules.conf') contains the appropriate module path before you can use some functions of this utility. Read doc/modules for more information. Also, you need to be `root', or at least have access to the /dev/i2c[-/]* files for some things. You can use prog/mkdev/mkdev.sh to create these /dev files if you do not have them already. If you have patched your kernel and have some drivers built-in you can safely answer NO if asked to load some modules. In this case, things may seem a bit confusing, but they will still work. IF THIS IS AN IBM THINKPAD, PRESS CTRL-C NOW! IBM Thinkpads have a severely broken i2c/SMBus implementation, just scanning the bus will break your thinkpad forever! We can start with probing for (PCI) I2C or SMBus adapters. You do not need any special privileges for this. Do you want to probe now? (YES/no): YES Probing for PCI bus adapters... Use driver `i2c-sis5595' for device 00:02.0: Silicon Integrated Systems SIS5595 Use driver `i2c-riva' for device 01:00.0: GeForce2 MX Probe succesfully concluded. We will now try to load each adapter module in turn. Load `i2c-sis5595' (say NO if built into your kernel)? (YES/no): YES /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o failed /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-sis5595.o: insmod i2c-sis5595 failed Loading failed ()... skipping. Load `i2c-riva' (say NO if built into your kernel)? (YES/no): YES modprobe: Can't locate module i2c-riva Loading failed ()... skipping. ** Note: i2c-riva module is available at ** http://drama.obuda.kando.hu/~fero/cgi-bin/rivatv.shtml Do you now want to be prompted for non-detectable adapters? (yes/NO): yes Load `i2c-elektor' (say NO if built into your kernel)? (YES/no): YES /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o failed /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elektor.o: insmod i2c-elektor failed Loading failed ()... skipping. Load `i2c-elv' (say NO if built into your kernel)? (YES/no): YES /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o failed /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-elv.o: insmod i2c-elv failed Loading failed ()... skipping. Load `i2c-philips-par' (say NO if built into your kernel)? (YES/no): YES Module loaded succesfully. Load `i2c-velleman' (say NO if built into your kernel)? (YES/no): YES /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: insmod /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o failed /lib/modules/2.4.18-19.8.0/kernel/drivers/i2c/i2c-velleman.o: insmod i2c-velleman failed Loading failed ()... skipping. To continue, we need module `i2c-dev' to be loaded. If it is built-in into your kernel, you can safely skip this. i2c-dev is not loaded. Do you want to load it now? (YES/no): YES Module loaded succesfully. We are now going to do the adapter probings. Some adapters may hang halfway through; we can't really help that. Also, some chips will be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. That often includes address 0x69 (clock chip). Some chips are also accessible through the ISA bus. ISA probes are typically a bit more dangerous, as we have to write to I/O ports to do this. Do you want to scan the ISA bus? (YES/no): YES Probing for `National Semiconductor LM78' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `National Semiconductor LM78-J' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `National Semiconductor LM79' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83781D' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83782D' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83627HF' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Winbond W83697HF' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `Silicon Integrated Systems SIS5595' Trying general detect... Success! (confidence 9, driver `sis5595') Probing for `VIA Technologies VT82C686 Integrated Sensors' Trying general detect... Failed! Probing for `ITE IT8705F / IT8712F / SiS 950' Character in "C" format wrapped at /usr/sbin/sensors-detect line 963. Trying address 0x0290... Failed! Probing for `IPMI BMC KCS' Trying address 0x0ca0... Failed! Probing for `IPMI BMC SMIC' Trying address 0x0ca8... Failed! Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `sis5595' (should be inserted): Detects correctly: * ISA bus, undetermined address (Busdriver `i2c-isa') Chip `Silicon Integrated Systems SIS5595' (confidence: 9) I will now generate the commands needed to load the I2C modules. Sometimes, a chip is available both through the ISA bus and an I2C bus. ISA bus access is faster, but you need to load an additional driver module for it. If you have the choice, do you want to use the ISA bus or the I2C/SMBus (ISA/smbus)? SMBus WARNING! If you have some things built into your kernel, the below list will contain too many modules. Skip the appropriate ones! To load everything that is needed, add this to some /etc/rc* file: #----cut here---- # I2C adapter drivers modprobe i2c-isa # I2C chip drivers modprobe sis5595 #----cut here---- To make the sensors modules behave correctly, add these lines to either /etc/modules.conf or /etc/conf.modules: #----cut here---- # I2C module options alias char-major-89 i2c-dev #----cut here---- [root@localhost root]# Same results though.

Cool new look.

Thanks DOlsen. Will do.

Okay people... we may all get a bit hot under the collar sometimes becuase of the different positions we take, but after is all is said and done we should not try to take things to personally. Difficult if we al have to be too careful before write what we think. This is a Linux forum after all. "But I also bought a Playstation." Well, I still use a Windows partition to play games... I wonder what people will think about that :) Okay people... lets cool it.