[yast-devel] YaST: 10.3 installation testing
Hi, who never needs to test the first stage installation workflow, can safely delete this mail. :-) Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.: install=ftp://server1/pub/cd1?instsys=my_fancy_instsys [using ftp://server1/pub/cd1/my_fancy_instsys] or even install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys The 'instsys' URL does _NOT_ point to a repository but directly to the instsys image (or directory). The old method of implicitly using a 'boot/<arch>/inst-sys' directory if one exists, is no longer supported. BTW, before someone asks: the linuxrc docs on opensuse.org have been updated. :-) BTW2, as of beta1 linuxrc checks the signatures of all files it downloads. Use 'insecure=1' to turn it off. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Steffen Winterfeldt wrote / napísal(a):
Hi,
who never needs to test the first stage installation workflow, can safely delete this mail. :-)
Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.:
install=ftp://server1/pub/cd1?instsys=my_fancy_instsys
[using ftp://server1/pub/cd1/my_fancy_instsys]
Can I use instsys via another protocol on other location? Example: install=ftp://server1/pub/cd1?instsys=http://server2/my_customized_root Michal
or even
install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys
The 'instsys' URL does _NOT_ point to a repository but directly to the instsys image (or directory).
The old method of implicitly using a 'boot/<arch>/inst-sys' directory if one exists, is no longer supported.
BTW, before someone asks: the linuxrc docs on opensuse.org have been updated. :-)
BTW2, as of beta1 linuxrc checks the signatures of all files it downloads. Use 'insecure=1' to turn it off.
Steffen
-- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec@suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Tue, 7 Aug 2007, Michal Zugec wrote:
Steffen Winterfeldt wrote / napísal(a):
Hi,
who never needs to test the first stage installation workflow, can safely delete this mail. :-)
Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.:
install=ftp://server1/pub/cd1?instsys=my_fancy_instsys
[using ftp://server1/pub/cd1/my_fancy_instsys]
Can I use instsys via another protocol on other location? Example:
install=ftp://server1/pub/cd1?instsys=http://server2/my_customized_root
Sure. Cf. this example from may mail:
install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys
Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 07-Aug-07, Steffen Winterfeldt wrote:
Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.:
install=ftp://server1/pub/cd1?instsys=my_fancy_instsys
[using ftp://server1/pub/cd1/my_fancy_instsys]
or even
install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys
The 'instsys' URL does _NOT_ point to a repository but directly to the instsys image (or directory).
The old method of implicitly using a 'boot/<arch>/inst-sys' directory if one exists, is no longer supported.
ARGH! Well, for testing I will have to use install=ftp://server1/pub/cd1?instsys=inst-sys then.
BTW, before someone asks: the linuxrc docs on opensuse.org have been updated. :-)
Nice. ^^
BTW2, as of beta1 linuxrc checks the signatures of all files it downloads. Use 'insecure=1' to turn it off.
Ok... Any docs on how to generate your own signature and where to put the key? Or better, a script for that? Regards, -- Olaf Dabrunz (od/odabrunz), SUSE Linux Products GmbH, Nürnberg -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Tue, 7 Aug 2007, Olaf Dabrunz wrote:
On 07-Aug-07, Steffen Winterfeldt wrote:
BTW2, as of beta1 linuxrc checks the signatures of all files it downloads. Use 'insecure=1' to turn it off.
Ok... Any docs on how to generate your own signature and where to put the key? Or better, a script for that?
man gpg, I'd say. And add it here: # mnt boot/i386/loader/initrd # file /mnt/installkey.gpg /mnt/installkey.gpg: GPG key public ring Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Steffen Winterfeldt wrote:
Hi,
who never needs to test the first stage installation workflow, can safely delete this mail. :-)
Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.:
install=ftp://server1/pub/cd1?instsys=my_fancy_instsys
[using ftp://server1/pub/cd1/my_fancy_instsys]
or even
install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys
I've also found that 'root' (inst-sys) is no more 'cramfs' but newly 'squashfs'. If you want to decompile the 'root' file you will need a kernel module 'modprobe squashfs' (which is in squashfs-kmp-default.rpm, or squashfs-kmp-xen.rpm, or ...). Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic
On Wed, 8 Aug 2007, Lukas Ocilka wrote:
Steffen Winterfeldt wrote:
who never needs to test the first stage installation workflow, can safely delete this mail. :-)
Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.:
install=ftp://server1/pub/cd1?instsys=my_fancy_instsys
[using ftp://server1/pub/cd1/my_fancy_instsys]
or even
install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys
I've also found that 'root' (inst-sys) is no more 'cramfs' but newly 'squashfs'.
If you want to decompile the 'root' file you will need a kernel module 'modprobe squashfs' (which is in squashfs-kmp-default.rpm, or squashfs-kmp-xen.rpm, or ...).
Ehm, yes. That was coolo's special wish. It compresses better and the 1-CD people wanted the additional space. It's a bit of a PITA, though, as our fs tools more or less ignore it. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Steffen Winterfeldt <snwint@suse.de> writes:
On Wed, 8 Aug 2007, Lukas Ocilka wrote:
Steffen Winterfeldt wrote:
who never needs to test the first stage installation workflow, can safely delete this mail. :-)
Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.:
install=ftp://server1/pub/cd1?instsys=my_fancy_instsys
[using ftp://server1/pub/cd1/my_fancy_instsys]
or even
install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys
I've also found that 'root' (inst-sys) is no more 'cramfs' but newly 'squashfs'.
If you want to decompile the 'root' file you will need a kernel module 'modprobe squashfs' (which is in squashfs-kmp-default.rpm, or squashfs-kmp-xen.rpm, or ...).
Ehm, yes. That was coolo's special wish. It compresses better and the 1-CD people wanted the additional space.
It's a bit of a PITA, though, as our fs tools more or less ignore it.
Could you file bugs against our fs tools, please? Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Steffen Winterfeldt wrote / napísal(a):
Hi,
who never needs to test the first stage installation workflow, can safely delete this mail. :-)
Starting with beta1, a shiny new linuxrc is used. In particular, you can specify an inst-sys independently of the repository. Like, e.g.:
install=ftp://server1/pub/cd1?instsys=my_fancy_instsys
[using ftp://server1/pub/cd1/my_fancy_instsys]
or even
install=ftp://server1/pub/cd1?instsys=nfs://server2/my/fancy_instsys
The 'instsys' URL does _NOT_ point to a repository but directly to the instsys image (or directory).
The old method of implicitly using a 'boot/<arch>/inst-sys' directory if one exists, is no longer supported.
BTW, before someone asks: the linuxrc docs on opensuse.org have been updated. :-)
BTW2, as of beta1 linuxrc checks the signatures of all files it downloads. Use 'insecure=1' to turn it off.
Steffen
It doesn't works for me in 10.3RC1. It seems that when I use instsys parameter it tries to use that url as repository (url mount: nfs:/my_repository_url fauled no openSUSE repository found) Steffen, did you change something? M. -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec@suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Mon, 24 Sep 2007, Michal Zugec wrote:
It doesn't works for me in 10.3RC1. It seems that when I use instsys parameter it tries to use that url as repository (url mount: nfs:/my_repository_url fauled no openSUSE repository found) Steffen, did you change something?
Works fine for me. If not, boot with 'linuxrcdebug=1 linuxrclog=/foo' and send me the log. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (5)
-
Andreas Jaeger -
Lukas Ocilka -
Michal Zugec -
Olaf Dabrunz -
Steffen Winterfeldt