-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ~ Smoking Tech Problem ~ --------------------- ~ After experiencing difficulties with his computer, a poor, incognizant ~ user called the system maker's technical support line for assistance... ~ Technician: Hello. How can I help you today? ~ Customer: There's smoke coming from the power supply on my computer... ~ Technician: Looks like you need a new power supply... ~ Customer: No, I don't! I just need to change the startup files... ~ Technician: Sir, what you described is a faulty power supply. You need ~ to replace it... ~ Customer: No way! Someone told me that I just had to change the system ~ startup files to fix the problem! All I need is for you to tell me the ~ right command... ~ For the next ten minutes, in spite of the technician's efforts to explain ~ the problem and its solution, the customer adamantly insisted that he was ~ right. So, in frustration, the technician responded... ~ Technician: I'm sorry. We don't normally tell our customers this, but ~ there's an undocumented DOS command that will fix the problem... ~ Customer: I knew it! ~ Technician: Just add the line 'LOAD NOSMOKE.COM' at the end of the ~ CONFIG.SYS file and everything should work fine. Let me know how it ~ goes... ~ About ten minutes later, the technician received a call back from ~ the customer... ~ Customer: It didn't work. The power supply is still smoking... ~ Technician: Well, what version of DOS are you using? ~ Customer: MS-DOS 6.22... ~ Technician: Well, that's your problem. That version of DOS doesn't ~ include NOSMOKE. You'll need to contact Microsoft and ask them for ~ a patch. Let me know how it all works out... ~ When nearly an hour had passed, the phone rang again... ~ Customer: I need a new power supply... ~ Technician: How did you come to that conclusion? ~ Customer: Well, I called Microsoft and told the technician what you ~ said, and he started asking me questions about the make of the power ~ supply... ~ Technician: What did he tell you? ~ Customer: He said my power supply isn't compatible with NOSMOKE... - -- "DRM.. Digitally Retarded Media. That's exactly what it is - content that cannot reach its full potential because of artificial restraints." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iEYEARECAAYFAj2eVF4ACgkQeNJ3p8sZ/uuK/ACfYhXAB0ocByGNWWMBcf2EaOLY 33kAoI0DIEZ5qhMw17EGXlaQVKiQ7MDR =QpDA -----END PGP SIGNATURE-----
Someone told me if I made a /home partition on the hard drive and install all my programs and work in the that I would not lose it if & when I upgrade the version, So far whenever I have asked anybody, I get " " for a reply.
From Eric
NO ATTACHMENT WAS SENT WITH THIS EMAIL, IF THERE IS ONE, IT IS A UNDETECTED VIRUS, PLEASE LET ME KNOW.. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.394 / Virus Database: 224 - Release Date: 10/3/02
söndagen den 6 oktober 2002 08.43 skrev Eric Richards:
Someone told me if I made a /home partition on the hard drive and install all my programs and work in the that I would not lose it if & when I upgrade the version,
If you chose not to format the /home partition when you do a new install the contents are still there. If you just do an upgrade you shouldn't lose anything. I have /home , /usrlocal and a datapartition /data on separate partitions to make installing/reinstallinf easier. I sometimes get carried away and mess things up so much it's easier to reinstall than to clean up the mess. :-) Olle -- MicroSoft Network may not carry this message without license to do so. License to carry this message requires a fee of $1000, payable within 30 days to Olle Viksten. Appearance of this message on MicroSoft Network constitutes an agreement to terms.
Olle Viksten
If you chose not to format the /home partition when you do a new install the contents are still there. If you just do an upgrade you shouldn't lose anything.
If you keep your existing /home, will a new install update, and add new, configuration ('.') files? Normally when installing or updating a package where the user has changed a 'normal' (in /etc) configuration file the new "standard" configuration file is installed with a '.rpmsave' extension and the user can (manually) merge in any changes. Or would it be better to not tell YaST about the partition containing the existing /home, allow it to set up a default set of configuration files, mount the existing /home somewhere else and manually merge the changes, and then change /etc/fstab to restore use of the existing /home?
On Sunday 06 October 2002 08:43, Eric Richards wrote: Hi, Someone told me if I made a /home partition on the hard drive and
install all my programs and work in the that I would not lose it if & when I upgrade the version,
So far whenever I have asked anybody, I get " " for a reply.
I have always made a separate partition for /home. Lately, with the price of HDs, I've actually made a separate drive/partition for /home. That way, I can do upgrades/tests and not lose my info. Also, if one drive crashes, I don't lose everything. And yes, I do have /home backed up separate from / Mike -- Powered by SuSE 8.0 Kernel 2.4.18 KDE 3.0.2 Kmail 1.4.2 For a great linux portal try http://www.freezer-burn.org For SuSE Mondo/Mindi backup support go to http://home.t-online.de/~jroark 9:58am up 3 days, 14:29, 4 users, load average: 1.50, 1.59, 1.64
On October 6, 2002 02:43 am, Eric Richards wrote:
Someone told me if I made a /home partition on the hard drive and install all my programs and work in the that I would not lose it if & when I upgrade the version,
So far whenever I have asked anybody, I get " " for a reply.
Not exactly right. You should have a separate partition for /home but that's your home. Keep things like data files not programs there. Well unless you are installing programs for your use only. Use /usr/local for programs that aren't coming from SuSE. If you do it right then you could wipe the rest of the system and upgrade without too many problem. Nick
Hi there! And the question was : "After I had to abort the 8.0 -> 8.1 upgrade process, I get 'EBDA too big' error from LILO when I reboot" I've managed to trick the system to start under Windows XP (and I mean 'trick', it's not a straight reboot - I boot on the SuSE 8.1 update CD and then go to Installation, cancel it, it then launch my OLD SuSE 8.0, goes as far as the KDE logging prompt but refuses to let me in as root. I then select, still under suSE 8.0 + KDE, shutdown->reboot->windows, gives the root password (accepted) and here it goes, away from from SuSE 8.0 to Windows XP Pro ... It might be (and surely is) a disk space trouble when upgrading that triggered this strange behaviour. I have managed now to make some space on the Win XP NTFS partitions. So I can reclaim some space for SuSE ... How can I have a plain sailing dual boot Win XP Pro / SuSE 8.1 machine again? Please ... TIA. LaoToma (Yes, I've checked Google, SuSE support database, etc ...)
participants (7)
-
Eric Richards -
Fred A. Miller -
Graham Murray -
Lao Toma -
Mike -
Nick Zentena -
Olle Viksten