Propose your solution
Attachments
Duplicates
Comments
|
|
Yes, I want a;
* Recover boot sector
* Recover boot loader
Option on the Live CD.
|
|
|
|
The quick and dirty approach has always been to use a virtual installation with religious snapshot use prior to getting experimental with your hands. Yes streaming media isn't always perfect when you skimp on ram but it does have it's advantages.
|
|
jhoger
wrote on the 25 May 08 at 18:01
|
|
|
|
I'm curious does a "screwed" Ubuntu system happen a lot to non-technical users? I would think technical users can use Google/howtos and the existing LiveCD to fix this themselves, and non-technical users never see it because they don't fiddle with the system much.
|
|
Theif
wrote on the 25 May 08 at 19:09
|
|
|
> I'm curious does a "screwed" Ubuntu system happen a lot to non-technical users? I would think technical users can use Google/howtos and the existing LiveCD to fix this themselves, and non-technical users never see it because they don't fiddle with the system much.
agree
|
|
s3a
wrote on the 25 May 08 at 20:49
|
|
|
|
Who cares if there are other ways?! This sounds better! I added it in my sig in the forums to support your idea as much as I can.
|
|
|
|
Windows has this feature on their installation disk and I know it's saved me countless times.
|
|
jhoger
wrote on the 25 May 08 at 21:25
|
|
|
The idea "sounds better" but it is not clear to me what the idea is. What is "screwed?" If say the boot partition is hosed, then one would deal with grub. If the file system is damaged, one uses backup software and gparted
Under Windows you get registry issues, virus/spyware and DLL hell dependency issues. It is a common occurance for Windows users to reinstall their OS for these reasons. Ubuntu users rarely need to reinstall.
There is no Ubuntu registry. We don't have a significant spyware or malware issue.
So I can only guess the concern here is package dependencies. I've found that running aptitude is pretty good for this. But if DLL hell is the issue the system usually boots fine, you just run aptitude.
So I'm still interested in what the problem is, who it happens to, and what kind of catch-all tool you might have in mind.
|
|
jhuni
wrote on the 26 May 08 at 06:00
|
|
|
|
Ubuntu is a secure operating system primarily based on free software which is almost never malicious and it generally has few bugs. A user is obviously not likely to break their installation in fact I have never seen it happen before and I use Ubuntu every day.
|
|
Auzy
wrote on the 26 May 08 at 09:49
|
|
|
drives can get corrupted, and programs can get damaged. An archive and install system can also help assist other stuff.
+1
|
|
jhoger
wrote on the 28 May 08 at 06:21
|
|
|
Auzy, if that's the idea, then I think this idea is -1,SciFi. It might as well be "Provide a Magic Wand to fix whatever I did to screw up my system." There is no such gadget. Sure you can always re-install the system but that's just the Ubuntu install CD. And from what I've been reading, the Install CD already has a rescue mode.
Most everything else has a solution but there is no wizard that could be devised to fix arbitrary problems. Again, the Install live CD mode has the tools you typically need to repair a system.
Generally I think this idea is already "Done" as best it can be by the existing Install CD.
So I think I've decided +0, Already Implemented.
|
|
|
|
+1 for the so many problems i got these 4 years with Ubuntu with GDM and HAL...
|
|
|
In my few years of experimenting with Ubuntu, I've had quite a few opportunities to recover a system gone bad (by my own hand, of course). The fact is, from the get go, I always had my home directory on a separate "home" partition.
If things went south on me, I would just pop in the live CD, perform a clean install, but keep my home partition intact. This kept all my preferences and data as well for not only the desktop environment, but the settings for all my applications as well. No reconfiguration required.
Of course, I would have to reinstall the codecs as well as several applications, but that is simple enough. The real time consumer is the configuration process and I think that saving your home directory addresses this issue.
I think that maybe the default installation should provide a separate "home" partition and maybe even a "usr" partition as well. This would save a lot of people a ton of headache. If a recovery utility needs to be implemented, then this separate home partition would be very valuable.
I remember (back in my XP days) that I would use the automated system repair (on the XP installation disc) to recover broken systems (mostly due to infections). After cleaning the infections and performing the repair (which took as long as performing a clean installation), the OS would be up and running with all the data intact. I think that if Ubuntu were to implement an automated repair function, it would have to basically do the same thing, but yield better results because all the settings would be saved as well.
|
|
djringjr
wrote on the 31 Aug 09 at 15:22
|
|
|
@ jhoger and Thief:
>> I'm curious does a "screwed" Ubuntu system happen a lot to >> non-technical users? I would think technical users can use >> Google/howtos and the existing LiveCD to fix this
>> themselves, and non-technical users never see it because
>> they don't fiddle with the system much.
>agree
Wouldn't it be much easier for either of you to have posted the URL for the google how to about using the existing LiveCD to fix a busted system?
Busted systems sadly happen sometimes when testing Alpha and Betas.
I agree with the original poster, a easy to use "Restore Broken System" from the original LiveCD (or a new one if the Alpha has gone to RC or Release).
Remember before you knew the words and method to discover the knowledge you currently have, you were ignorant of being able to find what this person seeks.
Be INSTRUCTIVE rather than DESTRUCTIVE.
Give knowledge, not hold what you know when you could have easily helped this person and many others who might be seeking this information.
Thanks
|
|
|
|
I would love to have the knowledge to learn how to fix my busted ubuntu system. I haven't found howtos that have helped me. I'm sure there is a way to fix my issue, but I'd rather get back to work than learn it. An auto repair feature would help me. twice I've had machines locked up during a Ubuntu version update, leaving the system in a state where it didn't boot. not going to go into details about it here, but a liveCD auto-recover would easily fix the issue.
|
Post your comment
|
Blueprint recover-ubuntu-from-livecd:
