Re: partman-auto: preseeding a multiboot install
Quoting John Morris (j...@zultron.com): > It is painful to overcome the learning curve of d-i, debconf and > partman, and just about any alternate means of achieving one's goals > should be considered. If hacking partman-auto and partman-auto-lvm is > really the only solution, here's what I did, in broad strokes: You know, a discussion I was having with Joey Hess at DebConf 13 had one of its conclusion as this: it is very sad that partman has indeed no more "real" maintainer. The framework is indeed fairly well robust as it is in this state for several years and, still, things are mostly working (except when I break everything by committing an unchecked patch)and even allowed some people to plumb in their own pet filesystem. But, still, the overall code is mostly unchanged and we have tons of interesting suggestions piling up in the BTS.but remaining as they are: interesting suggestions...:-) We would definitely welcome someone ready to invest some time (preferrably in the long term) to enhance the parts that could be enchanced. Really. But, at the moment, there is nobody who stepped in for this There is some learning curve as you mentioned but, after all, it is not that huge and all this requires some good understanding of shell-script programming (and everything related to partitions and filesystems of course). signature.asc Description: Digital signature
Re: Bug#721013: installation-reports : elilo is missing in /target/usr/sbin
Control: reassign -1 installation-reports On Ma, 27 aug 13, 16:54:17, ohata.hide...@zf.mitsubishielectric.co.jp wrote: > Package: d-i ia64 Reassigning to correct "package". Andrei > Boot method: netboot > Image version: Debian version: 7 (wheezy) Installer build: 20130613 > Date: 2013-Aug-19 > > Machine: hp rx2800i2 AH395A > Processor: Itanium(R) Processor 9340 (1.6 GHz, 20 MB) > Memory: 12179 MB (11.89 GB) > Partition: > root@rx28db:~# mount > sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) > proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) > udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=384648,mode=755) > devpts on /dev/pts type devpts > (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) > tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1232800k,mode=755) > /dev/sdb2 on / type ext4 > (rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered) > tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) > tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=4809280k) > /dev/sdb1 on /boot/efi type vfat > (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro) > rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) > > (parted) print > Model: HP LOGICAL VOLUME (scsi) > Disk /dev/sdb: 73.4GB > Sector size (logical/physical): 512B/512B > Partition Table: gpt > > Number Start End SizeFile system Name Flags > 1 1049kB 99.6MB 98.6MB fat16 boot > 2 99.6MB 60.1GB 60.0GB ext4 > 3 60.1GB 72.1GB 12.0GB linux-swap(v1) > > Comments/Problems: > elilo is not installed to /target/usr/sbin/ at installation phase. > > > root@rx28db:~# ls /usr/sbin/e* > /usr/sbin/e2freefrag/usr/sbin/exim_convert4r4 /usr/sbin/exinext > /usr/sbin/e4defrag /usr/sbin/exim_dbmbuild/usr/sbin/exipick > /usr/sbin/exicyclog /usr/sbin/exim_dumpdb /usr/sbin/exiqgrep > /usr/sbin/exigrep /usr/sbin/exim_fixdb /usr/sbin/exiqsumm > /usr/sbin/exim /usr/sbin/exim_lock/usr/sbin/exiwhat > /usr/sbin/exim4 /usr/sbin/exim_tidydb > /usr/sbin/exim_checkaccess /usr/sbin/eximstats > > here the installer/syslog related to elilo ; > . > Aug 26 10:23:49 in-target: The following extra packages will be installed: > Aug 26 10:23:49 in-target: libuuid-perl linux-base > linux-image-3.2.0-4-mckinley > Aug 26 10:23:49 in-target: Suggested packages: > Aug 26 10:23:49 in-target: linux-doc-3.2 debian-kernel-handbook fdutils > elilo > Aug 26 10:23:49 in-target: Recommended packages: > Aug 26 10:23:49 in-target: firmware-linux-free > Aug 26 10:23:49 in-target: The following NEW packages will be installed: > Aug 26 10:23:49 in-target: libuuid-perl linux-base > linux-image-3.2.0-4-mckinley linux-image-mckinley > Aug 26 10:23:49 in-target: 0 upgraded, 4 newly installed, 0 to remove and 0 > not upgra > . > Aug 26 10:48:55 main-menu[459]: INFO: Menu item 'elilo-installer' selected > Aug 26 10:48:55 main-menu[459]: INFO: Falling back to the package description > for fat-modules-3.2.0-4-itanium-di > Aug 26 10:48:55 main-menu[459]: INFO: Falling back to the package description > for fat-modules-3.2.0-4-itanium-di > > Aug 26 10:49:17 main-menu[459]: (process:8600): Error: Both the primary and > backup GP > T tables are corrupt. Try making a fresh table, and using Parted's rescue > feature to > recover partitions. > Aug 26 10:49:17 main-menu[459]: (process:8600): A bug has been detected in > GNU Parted > . Refer to the web site of parted > http://www.gnu.org/software/parted/parted.html for > more information of what could be useful for bug submitting! Please email a > bug > Aug 26 10:49:17 main-menu[459]: (process:8600): Aborted > Aug 26 10:49:17 main-menu[459]: WARNING **: Configuring 'elilo-installer' > failed with error code 1 > Aug 26 10:49:17 main-menu[459]: WARNING **: Menu item 'elilo-installer' > failed. > Aug 26 10:49:19 main-menu[459]: DEBUG: resolver (libunwind7): package doesn't > exist (ignored) > > here the installer/syslog related to partman, > Aug 26 10:09:08 anna[1729]: DEBUG: retrieving partconf-find-partitions 1.40 > Aug 26 10:09:08 anna[1729]: DEBUG: retrieving libparted0-udeb 2.3-12 > Aug 26 10:09:09 anna[1729]: DEBUG: retrieving parted-udeb 2.3-12 > Aug 26 10:09:10 anna[1729]: DEBUG: retrieving partman-auto 106 > Aug 26 10:09:11 anna[1729]: DEBUG: retrieving partman-auto-raid 21 > Aug 26 10:09:11 anna[1729]: DEBUG: retrieving partman-base 165 > Aug 26 10:09:13 anna[1729]: DEBUG: retrieving partman-utils 165 > Aug 26 10:09:13 anna[1729]: DEBUG: retrieving partman-basicfilesystems 77 > Aug 26 10:09:14 anna[1729]: DEBUG: retrieving partman-basicmethods 52 > Aug 26 10:09:15 anna[1729]: DEBUG: retrieving partman-btrfs 10 > Aug 26 10:09:16 anna[1729]: DEBUG: retrieving partman-efi 36 > Aug 26 10:09:20 anna[1729]: DEBUG: retrieving partman
Processed: Re: Bug#721013: installation-reports : elilo is missing in /target/usr/sbin
Processing control commands: > reassign -1 installation-reports Bug #721013 [d-i ia64] installation-reports : elilo is missing in /target/usr/sbin Warning: Unknown package 'd-i' Warning: Unknown package 'ia64' Bug reassigned from package 'd-i ia64' to 'installation-reports'. Ignoring request to alter found versions of bug #721013 to the same values previously set Ignoring request to alter fixed versions of bug #721013 to the same values previously set -- 721013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b721013.137759478122902.transcr...@bugs.debian.org
Re: partman-auto: preseeding a multiboot install
Hi Christian,
On 08/27/2013 12:11 AM, Christian PERRIER wrote:
> Quoting John Morris (j...@zultron.com):
>
>> It is painful to overcome the learning curve of d-i, debconf and
>> partman, and just about any alternate means of achieving one's goals
>> should be considered. If hacking partman-auto and partman-auto-lvm is
>> really the only solution, here's what I did, in broad strokes:
>
>
> You know, a discussion I was having with Joey Hess at DebConf 13 had
> one of its conclusion as this: it is very sad that partman has indeed
> no more "real" maintainer.
Ah ha! An orphaned package would explain why the original question
about 'reusing' partitions or LVs has been asked many times in the past,
but never been answered.
> The framework is indeed fairly well robust
> as it is in this state for several years and, still, things are mostly
> working (except when I break everything by committing an unchecked
> patch)and even allowed some people to plumb in their own pet
> filesystem.
As already described, partman-auto and partman-auto-lvm leave something
to be desired.
On the other hand, partman's underlying infrastructure looks quite
solid. As you say, someone with enough dedication can make interesting
customizations without requiring major, widespread changes.
In fact, it would be fairly easy to generalize the 'multiboot' work and
undo those assumptions in partman-auto-lvm, even while preserving the
current behavior as default. Nearly all changes would be localized
within the partman-auto-lvm package, possibly with a minor change to
partman-lvm.
> But, still, the overall code is mostly unchanged and we have tons of
> interesting suggestions piling up in the BTS.but remaining as they
> are: interesting suggestions...:-)
Yes, I understand very well how that happens.
> We would definitely welcome someone ready to invest some time
> (preferrably in the long term) to enhance the parts that could be
> enchanced. Really. But, at the moment, there is nobody who stepped in
> for this
On the technical side, I'm well-qualified to work on partman.
Unfortunately there are other aspects that would make it hard for me to
jump in. For one, I'm already a Fedora developer with way too many
packages, ha! Also, I'm not a Debian developer. Fedora's process to
become a developer requires a LOT of busy work, most of which I managed
to circumvent by demonstrating experience. Debian's process is probably
similar. I've written and currently support .debs (for the LinuxCNC
community), including a few very challenging ones, but I've only been
involved with Debian over the last year, and couldn't demonstrate enough
contributions to the community to qualify for shortcuts. :) Also, I
see a *lot* of bugs against e.g. partman-lvm in the BTS. Agreeing to
fix all those would be quite a commitment on top of the developer
hurdle-jumping process.
> There is some learning curve as you mentioned but, after all, it is
> not that huge and all this requires some good understanding of
> shell-script programming (and everything related to partitions and
> filesystems of course).
It took about 4-5 days of solid work, including rebooting about 200
times! But you're right, really not too bad, and most of it was spent
reverse-engineering partman and understanding debconf and d-i.
Some things that could have made the work easier:
- sshd: Editing scripts remotely, such as over sshfs or emacs' tramp,
would have made life easier. Also, connecting to the installer through
an emacs inferior shell or one's favorite editor, one would have more
powerful command-line editing facilities than ash provides. Maybe sshd
is available in d-i somewhere, but from the moment I started, I kept
thinking the job wouldn't take much longer, so I never looked. :)
- debconf/frontend doesn't steal stdio: In 'confmodule', there's a
comment saying a socket for debconf communication would be ideal. True!
The ability to '. /usr/share/debconf/confmodule' and then run db_*()
from the shell would be handy.
- documentation! Of course the source is the ultimate documentation,
but a basic 'principles of operations' ('POOPS', in IBM slang) document
would have been very valuable.
John
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/521cdede.4010...@zultron.com
Re: partman-auto: preseeding a multiboot install
Quoting John Morris (j...@zultron.com): > On the technical side, I'm well-qualified to work on partman. > Unfortunately there are other aspects that would make it hard for me to > jump in. For one, I'm already a Fedora developer with way too many > packages, ha! Also, I'm not a Debian developer. Fedora's process to > become a developer requires a LOT of busy work, most of which I managed > to circumvent by demonstrating experience. Debian's process is probably > similar. I've written and currently support .debs (for the LinuxCNC > community), including a few very challenging ones, but I've only been > involved with Debian over the last year, and couldn't demonstrate enough > contributions to the community to qualify for shortcuts. :) Also, I > see a *lot* of bugs against e.g. partman-lvm in the BTS. Agreeing to > fix all those would be quite a commitment on top of the developer > hurdle-jumping process. Indeed, there is no strict need to be an official Debian developer in order to contribute to D-I packages. We have several DDs in what remains of the D-I team in order to do the build/check/upload step of the work (ahem"check" as much as possible, which sometimes sums up to "well, let's be confident in that change because I have confidence in that guy"). And commit access to the D-I git repo doesn't require to be an official DD, just having an account on Alioth. signature.asc Description: Digital signature
Bug#721093: debootstrap: possibly add clarifying comment about $SECOND_STAGE_ONLY
Package: debootstrap Version: 1.0.53 Severity: wishlist Hi, turns out that I used debootstrap (via debirf) in a completely wrong manner: I used a subsequent manual debootstrap invocation with --second-stage, but I failed to realize at that time that this should likely be done *within-target* (chroot) rather than from the outside, in order to be able to successfully locate suite and arch files within the correct $DEBOOTSTRAP_DIR. Thus it would be useful to have comment if [ "$SECOND_STAGE_ONLY" = "true" ]; then # Within-target handling - read existing content # established there by a prior complete run: SUITE=$(cat $DEBOOTSTRAP_DIR/suite) ARCH=$(cat $DEBOOTSTRAP_DIR/arch) added to debootstrap script. Yeah, I know: docs do contain hints at this handling - but who reads docs anyway? ;) Thanks for a very useful package and an impressively clean script, Andreas Mohr -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130827212446.ga12...@rhlx01.hs-esslingen.de
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 Aug 28 00:03 buildd@barber build_cdrom_isolinux http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log * FAILED BUILD: amd64 Aug 28 00:03 buildd@barber build_cdrom_gtk http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log * FAILED BUILD: amd64 Aug 28 00:03 buildd@barber build_cdrom-xen http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log * FAILED BUILD: amd64 Aug 28 00:05 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log * FAILED BUILD: amd64 Aug 28 00:05 buildd@barber build_netboot-xen http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log * FAILED BUILD: amd64 Aug 28 00:05 buildd@barber build_hd-media http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log * FAILED BUILD: amd64 Aug 28 00:06 buildd@barber build_hd-media_gtk http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log * FAILED BUILD: armel Aug 27 08:36 buildd@ancina build_kirkwood_netboot-gtk http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log * OLD BUILD:armhf Aug 21 23:08 buildd@hasse build_mx5_netboot http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot.log * OLD BUILD:armhf Aug 22 03:20 buildd@hasse build_mx5_network-console http://d-i.debian.org/daily-images/armhf/daily/build_mx5_network-console.log * OLD BUILD:armhf Aug 22 09:27 buildd@hasse build_mx5_netboot-gtk http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot-gtk.log * OLD BUILD:armhf Aug 22 14:33 buildd@hasse build_vexpress_netboot http://d-i.debian.org/daily-images/armhf/daily/build_vexpress_netboot.log * FAILED BUILD: i386 Aug 28 00:02 buildd@biber build_cdrom_isolinux http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log * FAILED BUILD: i386 Aug 28 00:03 buildd@biber build_cdrom_gtk http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log * FAILED BUILD: i386 Aug 28 00:03 buildd@biber build_cdrom-xen http://d-i.debian.org/daily-images/i386/daily/build_cdrom-xen.log * FAILED BUILD: i386 Aug 28 00:04 buildd@biber build_netboot-gtk http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log * FAILED BUILD: i386 Aug 28 00:05 buildd@biber build_netboot-xen http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log * FAILED BUILD: i386 Aug 28 00:05 buildd@biber build_hd-media http://d-i.debian.org/daily-images/i386/daily/build_hd-media.log * FAILED BUILD: i386 Aug 28 00:05 buildd@biber build_hd-media_gtk http://d-i.debian.org/daily-images/i386/daily/build_hd-media_gtk.log * OLD BUILD:ia64 May 26 00:12 buildd@alkman build_cdrom http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log * OLD BUILD:ia64 May 26 00:16 buildd@alkman build_netboot http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log * OLD BUILD:amd64 Aug 12 09:17 debian-cd@pettersson 4sidmipsel http://cdbuilder.debian.org/cdimage-log/4sidmipsel * OLD BUILD:amd64 Aug 19 09:33 debian-cd@pettersson 4sidmipsel http://cdbuilder.debian.org/cdimage-log/4sidmipsel * OLD BUILD:amd64 Aug 19 11:40 debian-cd@pettersson 4sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/4sidkfreebsd-amd64 * OLD BUILD:amd64 Aug 19 12:12 debian-cd@pettersson Asidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/Asidkfreebsd-i386 * OLD BUILD:amd64 Aug 19 12:12 debian-cd@pettersson 4sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/4sidkfreebsd-i386 * FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson 5sidi386 http://cdbuilder.debian.org/cdimage-log/5sidi386 * FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson Asidi386 http://cdbuilder.debian.org/cdimage-log/Asidi386 * FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson 4sidi386 http://cdbuilder.debian.org/cdimage-log/4sidi386 * FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson Dsidi386 http://cdbuilder.debian.org/cdimage-log/Dsidi386 * FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson sidi386 http://cdbuilder.debian.org/cdimage-log/sidi386 * FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson 9sidi386 http://cdbuilder.debian.org/cdimage-log/9sidi386 * FAILED BUILD: amd64 Aug 26 04:08 debian-cd@pettersson 3sidi386 http://cdbuilder.debian.org/cdimage-log/3sidi386 * FAILED BUILD: amd64
