How can I make deboostrap'd system use host system tar?

Asked by David Jaša

Related to bug #539814 - I'm installing lucid on etch system with 2.6.18 kernel. How can I make debootstrap use newest tar package (or the one I build manually) instead of defective one in repository?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu debootstrap Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Keith Ward (kward) said :
#1

If remember correctly when I encountered this, the way I found around the problem was either to bootstrap karmic first, and then update it to lucid once your inside it, or update to say: Lenny (which is the new debian stable), and then debootstrap lucid from there, as long as the host system has a kernel version > 2.6.22 you shouldn't encounter a problem.

HTH,

Keith

Revision history for this message
Keith Ward (kward) said :
#2

If remember correctly when I encountered this, the way I found around the problem was either to bootstrap karmic first, and then update it to lucid once your inside it, or update to say: Lenny (which is the new debian stable), and then debootstrap lucid from there, as long as the host system has a kernel version > 2.6.22 you shouldn't encounter a problem.

HTH,

Keith

Revision history for this message
Ken Sharp (kennybobs) said :
#3

Debootstrap can handle file:/ URI as source mirrors. If you don't want to untar then you could mount the tar with a FUSE tool.

However, if you already have a tar then why do you need to bootstrap?

Can you help with this problem?

Provide an answer of your own, or ask David Jaša for more information if necessary.

To post a message you must log in.