2015-01-03 9:23 GMT+01:00 Blackcrack <[email protected]>: > Hi, > > can we add in urpmi the switch --install-system for tell urpmi, which drive > have urpmi to use for installing an basesystem and others task-XXXXX, > what we want, for an easy possible to install an system, the > Drakliveinstaller > can we use therefore as fronted .. to have with "urpmi --install-system" > something like in Win or dos the order "sys C:\" or an other drive . > With this have we the possible to install an system on prompt/console > so have we the possible easy via urpmi + swich like > "urpmi --install-system /mnt/sda1 basesystem task-bash task-apache > task-php task-sshd drakconf task-grub2 " > easy install an web-server without X or something.. or an easy possible > creating to > have an rpm-releated installer behind mkfs.ext4 ;) > > this make the live really easyer also with an liveiso, > easy urpmi --install-system $installsystem > if setting up before "formated rootsystem = $installsystem" ;) you see ;) > > easy add an switch on urpmi and most problems be solved :) > because if we have an running livesystem and can install > on usb an livesystem + urpmi can we gormating any hdd\sdd or how ever > and can use this as installsystem . > > so that's why " urpmi --install-system" switch to have an possible for > installing rpm's on an other harddisk/USB or maybe an iso /creating an iso > .. : > > urpmi --install-system basesystem task-bash icewm > --install-system-makeiso livesystem.iso > > urpmi --install-system basesystem task-bash icewm --install-system-base > $installsystem > or > urpmi --install-system basesystem task-bash icewm --install-system-base > /mnt/sdd3 > the possible for install system without grub, because an other disc have > include grub and > this installed system it is managed by the other system > > urpmi --install-system basesystem task-bash icewm --install-system-base > /mnt/sdd3 > > > --install-system (installing the listed rpm's and task's who be needed and > listed.. and solving the dependencies) > > --install-system-base (use the filesystem from mounted device a.e: > /mnt/sdd2 or /dev/sdd2 ) > or > --install-system-makeiso ( use mkiso add syslinux and create an bootable > kernel +systemd +tty a.e: livesystem.iso ) > > --install-system-rootpw (ask password of root without this string whant > set the passwort to no pw) > --install-system-user ( ask to adding users and start "adduser" without > this string it is only root existent) > > > for this we need 2 basesystems > 1. normal install as running system, normal install grub2.rpm+systemd.rpm > bash.rpm > > 2. livesystem who adjusting the kernel+systemd+bash+tty + syslinux who > boot only > the compatible grub2 for efi & normal System without efi for booting in > each case from an livesystem. > > one for IBM-compatieble i586 and one for ARM > because i586 works in both systems and make it possible for detecting the > x86_64 extension > > for this : > --install-system-IBM > or > --install-system-ARM > > and (aarch64 armv7hl armv7l i386 i586 x86_64) > --install-system-IBM (with the switch "auto" or "onlyi586" or onlyx86_64 > or nothing, -> auto) > --install-system-ARM (with the switch "auto" or aarch64, armv7hl, armv7l > or nothing -> error message) > working on, will hopefully have "perfect" integration of installation into chroots of others architectures using static qemu user & binfmt, where it should also provide this without any issues warned about (ie. such as complaints about unknown uid/gid). For those running arm port on real arm hardware, I should have in place automatic platform detection such as on x86 soon, eliminating the need for /etc/rpm/platform.
> > if i had anything forgotten, can you make more complete :) > > this about urpmi as install-system in prompt :) > > more easy can you it not make, and urpmi make it also use with with small > QT lib's as GUI . > isn't it so ? > > happy programming :) > Well, I'm working on functionality like this especially for arm port, where the packaging and dependency solving will take care of all the aspects that can be made non-interactive, ie. as rpm works in batch mode, and one dosen't want to overextend a tool with functionality that's not really within in it's areas of responsibilities/purposes of use. So what I'll most likely go at is that the distro gets installed with a default configuration (each "vendor" or whatever or whoever otherwise for that matter), with several defaults to choose from as people might provide them (ie. omv,mdk & rosa). For further customization and especially for those not involved in packaging, I will most likely integrate it in the python-drakx scripts (which ATM. only consists of classic iso generator) as some tool that allows for what level of customization that you request. :) -- Regards, Per Øyvind
_______________________________________________ OM-Cooker mailing list [email protected] http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
