Sunny wrote:

On 7/17/07, Hylton Conacher (ZR1HPC) wrote:

...

Hi,

I would like to reload the entire system from scratch but do not want to have to re-download all the patches I have already downloaded.

What I would like to know, is where openSUSE stores its updates and how those same updates can be used again. What would I need to do to have them stored in a different location?

I ask this as I want to add a 2ndry HDD into my system and use it as an install source. I would think that all I would need to do is copy the DVD into a partition on the new HDD and cut and paste the updates that I have already downloaded and applied.

Comments or should I raise an RFE?

Why need to reinstall if you just want to move the installation?

Put the new disk in, as well as the old one. Butt with Knoppix (or other live distro) and use either dd or partimage to move over the partitions. You can even use tar to get the partition content (it preserves the ownership) and untar on the new hard.

Cheers

If you use tar, use the -a option to preserve special devices, etc. See the man page. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tue July 17 2007 09:32, Sunny wrote:

On 7/17/07, Russell Jones wrote:

...

If you use tar, use the -a option to preserve special devices, etc. See the man page.

I do not see -a option in man tar? What do I miss?

It's an option of "cp" not of "tar". If you use tar, you should include the option -p while extracting to preserve all settings. -- Carlos FL Who is General Failure, and why is he reading my disk? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 7/17/07, G T Smith wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Sunny wrote:

...

On 7/17/07, Hylton Conacher (ZR1HPC) wrote:

...

Hi,

I would like to reload the entire system from scratch but do not want to have to re-download all the patches I have already downloaded.

I think the OP is after something slightly different, a re-install + apply changes made to original but NOT to move the current location.

- --

actually, I think what OP wants is to define an update source that utilizes the already downloaded patches/updates that have been applied to the existing system. He figures that the downloaded updates are stored *somewhere* on the drive, and would like to use THOSE as the update repo, so that he does not have to download them all again, after he re-installs. I have no idea whether it is possible, or how to do it ... and I'm interested to learn along with him the answer. Peter -- Everything is vague to a degree you do not realize till you have tried to make it precise. Bertrand Russell www.the-brights.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Van Lone wrote:

On 7/17/07, G T Smith wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Sunny wrote:

...

On 7/17/07, Hylton Conacher (ZR1HPC) wrote:

...

Hi,

I would like to reload the entire system from scratch but do not want to have to re-download all the patches I have already downloaded.

I think the OP is after something slightly different, a re-install + apply changes made to original but NOT to move the current location.

- --

actually, I think what OP wants is to define an update source that utilizes the already downloaded patches/updates that have been applied to the existing system.

Agreed, maybe I phrased it poorly but I was referring to what I inferred the final intent to be ... The dd option to my mind does not do what is required. Well I believe most (but not all) updates are deltas of the package on the system. With multiple cumulative updates probably the most effective way to restore these changes is to record the difference between the original distributed file and the current status of the file. I think but cannot be certain this is what the YaST System Backup Tool is doing (which is possibly one of the reasons it takes so long to run, it also does checksums on contents which problems does not help speed). This tool is also tied into the Auto Installation Tool technology in ways I have yet to completely figure out.

He figures that the downloaded updates are stored *somewhere* on the drive, and would like to use THOSE as the update repo, so that he does not have to download them all again, after he re-installs.

YaST does keep a record of the patches installed but I do not think it keeps a copy of the patch RPMs unless requested to (and I vaguely remember something about a bug which stops this from working anyway).

I have no idea whether it is possible, or how to do it ... and I'm interested to learn along with him the answer. Peter

- -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGnPPvasN0sSnLmgIRAmEzAKCCQxYplmZQj2k9vA80OxztviBO6QCg6eui /V9wSebUFZ1b4axNimGP4MA= =4T1U -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Peter Van Lone wrote:

On 7/17/07, G T Smith wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Sunny wrote:

...

On 7/17/07, Hylton Conacher (ZR1HPC) wrote:

...

Hi,

I would like to reload the entire system from scratch but do not want to have to re-download all the patches I have already downloaded.

I think the OP is after something slightly different, a re-install + apply changes made to original but NOT to move the current location.

- --

actually, I think what OP wants is to define an update source that utilizes the already downloaded patches/updates that have been applied to the existing system.

Peter, you got it! :)

He figures that the downloaded updates are stored *somewhere* on the drive, and would like to use THOSE as the update repo, so that he does not have to download them all again, after he re-installs.

I have no idea whether it is possible, or how to do it ... and I'm interested to learn along with him the answer. Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

G T Smith wrote:

Sunny wrote:

...

On 7/17/07, Hylton Conacher (ZR1HPC) wrote:

...

Hi,

I would like to reload the entire system from scratch but do not want to have to re-download all the patches I have already downloaded.

<snip>

I think the OP is after something slightly different, a re-install + apply changes made to original but NOT to move the current location.

Aah, someone actually read my post, almost as it was intended to sound :) To further explain: 1. Backup /home, /etc and wherever the Yast updates are stored. 2. Take the existing SATA HDD and using openSUSE 10.2 DVD, fdisk it to delete all the partitions. 3. Insert new secondary HDD on IDE into machine to act as software installation source. 4. Restart the machine and copy the DVD's to the secondary HDD. 5. Install 10.2 on the existing SATA HDD from my new HDD installation source. 6. Copy the backups of the updated packages to my HDD installation source. 7. Install all package updates from installation source. 8. Do YAST Online update and make it put any package updates onto secondary installation source before installing them. Make sense now, and is it possible, or as I said time for RFE? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

S Glasoe wrote:

On Wednesday July 18 2007 6:57:07 am Hylton Conacher (ZR1HPC) wrote:

...

G T Smith wrote:

...

Sunny wrote:

...

On 7/17/07, Hylton Conacher (ZR1HPC) wrote:

...

Hi,

I would like to reload the entire system from scratch but do not want to have to re-download all the patches I have already downloaded. <snip> <snip>

That's all possible. What I'd suggest though is an external USB/Firewire/SATA hard drive instead of going internal. That way its portable to friends, neighbors, relatives, can grab it when running from the burning building, etc.

I use an external USB HDD for my backups already and in case of burning buildings.

Have you searched opensuse.org for building YaST patch/update repositories, installing from external USB disks, etc?

No I haven't but hoped someone already had and could point me to a HOWTO. Failing this I will hit Google and search the Google/Linux and opensuse site site. I am really hoping though someone else has done this and followed a HOWTO :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 S Glasoe wrote:

On Wednesday July 18 2007 8:14:27 am Hylton Conacher (ZR1HPC) wrote:

...

S Glasoe wrote:

...

On Wednesday July 18 2007 6:57:07 am Hylton Conacher (ZR1HPC) wrote:

...

G T Smith wrote:

...

Sunny wrote:

...

On 7/17/07, Hylton Conacher (ZR1HPC) wrote: > Hi, > > I would like to reload the entire system from scratch but do not want > to have to re-download all the patches I have already downloaded. <snip> <snip>

...

That's all possible. What I'd suggest though is an external USB/Firewire/SATA hard drive instead of going internal. That way its portable to friends, neighbors, relatives, can grab it when running from the burning building, etc. I use an external USB HDD for my backups already and in case of burning buildings.

...

Have you searched opensuse.org for building YaST patch/update repositories, installing from external USB disks, etc? No I haven't but hoped someone already had and could point me to a HOWTO. Failing this I will hit Google and search the Google/Linux and opensuse site site.

I am really hoping though someone else has done this and followed a HOWTO :)

That was my point: Go search on opensuse.org. There is a ton of information and HOWTOs there relating to all of this. The organization is getting better and better all the time. The search function is very powerful. I don't have direct links but I used this in the last few days looking for HOWTOs on booting USB sticks, etc.

There are three related components in YaST involved in this (YaST Autoinstallation, System Backup and System Restore) and to be honest the relevant documentation is not complete or integrated. The most detailed documentation is for YaST auto installation, this is a very comprehensive technical description of the XML format of the configuration file and the tool but there are a couple of weaknesses in the document. e.g. There is a description of a file to specify the package selection but I have yet to find the reference to how this can be incorporated into the installation (I will keep looking, there is a see above comment but it is not clear what it referring to). In principle it should be easy to generate this file from the current installed configuration, it then becomes a matter of figuring out where (or how) to plug it in, The YaST Backup System tool is described in a half finished Howto but I have yet to find any reference to what the YasT Restore System Tool actually does (apart from Restore that is). Unfortunately, I have so far found no information on whether the YaST restore process will prompt for missing RPMs on the target system (and how it will handle non-SuSE RPMs). If it does, it will do the job required if not... well... I have a sneaking suspicion very few people have needed to use, or tried the Restore Tool hence the lack of info... (You can incorporate the Backup Archive into an Autoinstallation configuration which probably covers the patch installation side for Autoinstall). Personally before I put my trust in a backup and restore process of any kind I like to verify it. Data is usually straight forward. When one is doing this with a system configuration, a unverified restore (or rebuild) process is quite likely to produce the result you want to use it to protect against if you verify against the system one wishes to protect. (A bit of a catch 22 situation :-) ) Some non destructive verification utility might be useful.... (Maybe part of slowness of the System Backup Tool is that it performs such verification checks). Once it is verified, I also like to have a couple of spare copies (and if possible an alternative restore route). There seems to be interesting variant of sods law which roughly goes along the lines of 'Things always break when you really need them'. I have been bitten by this a little too often.. BTW The latter is one of the reasons I am not an enthusiast for the disk image on a usb drive approach, for an organisation that can afford to maintain a couple of spare drives, the original image system drive and possibly a couple spare images on a server it is a usable approach. For home user with a single drive a phrase involving eggs and baskets comes to mind,,,, - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGnztTasN0sSnLmgIRAim4AJ9watGEtq4R2kKC8TgDeJuG8G+V1gCgpTi8 6P/3V6bnXacFxvcBgKs9eGQ= =eWrb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

The Tuesday 2007-07-17 at 16:12 +0200, Hylton Conacher (ZR1HPC) wrote:

...

I would like to reload the entire system from scratch but do not want to have to re-download all the patches I have already downloaded.

...

What I would like to know, is where openSUSE stores its updates and how those same updates can be used again. What would I need to do to have them stored in a different location?

Nowhere. They are not stored and you need to re-download them every single time.

https://bugzilla.novell.com/show_bug.cgi?id=191021

The bug is marked as duplicate of bug 188543, which gives "access denied". Please add your vote to the first one. Perhaps reopen it.

:-/

Assigned my vote to it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org