Re: live-cd preseeding, sudo, sources.list
schoappied wrote: Hi, I have made an custom Debian live-cd, it has d-i included. Now I want to customize the d-i process a bit. 1) enable sudo (disable root) 2) add a custom sources.list I've read a bit about preseeding, but where should I put the file on the live-cd? Should I do it before or after building that live-cd? I've taken the example file from the manual as example. Do I get it right that if I comment out the lines, the default d-i option is used? To enable sudo I have this in the file: ### Account setup # Skip creation of a root account (normal user account will be able to # use sudo). d-i passwd/root-login boolean false # Alternatively, to skip creation of a normal user account. #d-i passwd/make-user boolean false To enable a custom sources.list I have: # Additional repositories, local[0-9] available d-i apt-setup/local0/repository string \ # http://local.server/debian stable main ftp://ftp.debian.us/debian/ testing main contrib non-free http://www.debian-multimedia.org/ testing main http://ftp.us.debian.org/debian/ unstable main contrib non-free http://ftp.uni-kl.de/debian-multimedia/ unstable main #d-i apt-setup/local0/comment string local server # Enable deb-src lines d-i apt-setup/local0/source boolean true # URL to the public key of the local repository; you must provide a key or # apt will complain about the unauthenticated repository and so the # sources.list line will be left commented out #d-i apt-setup/local0/key string http://local.server/key # By default the installer requires that repositories be authenticated # using a known gpg key. This setting can be used to disable that # authentication. Warning: Insecure, not recommended. d-i debian-installer/allow_unauthenticated string true ( I've the keys already on the live-cd..) Advise is welcome here! Thanks in advance, ~d I tried to preseed, but I think it fails... I've this in the binary file in the build environment of the live-cd: # $LH_DEBIAN_INSTALLER_PRESEEDFILE: set debian-installer preseed filename/url # (Default: ) LH_DEBIAN_INSTALLER_PRESEEDFILE=/home/d/debianlive/preseed.cfg This are the options specified in the preseed.cfg to enable sudo and have a custom sources.list: ### Account setup # Skip creation of a root account (normal user account will be able to # use sudo). d-i passwd/root-login boolean false # Alternatively, to skip creation of a normal user account. #d-i passwd/make-user boolean false # Root password, either in clear text #d-i passwd/root-password password r00tme #d-i passwd/root-password-again password r00tme # or encrypted using an MD5 hash. #d-i passwd/root-password-crypted password [MD5 hash] # To create a normal user account. #d-i passwd/user-fullname string Debian User #d-i passwd/username string debian # Normal user's password, either in clear text #d-i passwd/user-password password insecure #d-i passwd/user-password-again password insecure # or encrypted using an MD5 hash. #d-i passwd/user-password-crypted password [MD5 hash] # Create the first user with the specified UID instead of the default. #d-i passwd/user-uid string 1010 # The user account will be added to some standard initial groups. To # override that, use this. #d-i passwd/user-default-groups string audio cdrom video ### Apt setup # You can choose to install non-free and contrib software. #d-i apt-setup/non-free boolean true #d-i apt-setup/contrib boolean true # Uncomment this if you don't want to use a network mirror. d-i apt-setup/use_mirror boolean false # Select which update services to use; define the mirrors to be used. # Values shown below are the normal defaults. #d-i apt-setup/services-select multiselect security, volatile #d-i apt-setup/security_host string security.debian.org #d-i apt-setup/volatile_host string volatile.debian.org # Additional repositories, local[0-9] available d-i apt-setup/local0/repository string \ # http://local.server/debian stable main ftp://ftp.debian.us/debian/ testing main contrib non-free d-i apt-setup/local1/repository string \ http://www.debian-multimedia.org/ testing main d-i apt-setup/local2/repository string \ http://ftp.us.debian.org/debian/ unstable main contrib non-free d-i apt-setup/local3/repository string \ http://ftp.uni-kl.de/debian-multimedia/ unstable main d-i apt-setup/local4/repository string \ http://security.debian.org lenny/updates main contrib non-free #d-i apt-setup/local0/comment string local server # Enable deb-src lines d-i apt-setup/local0/source boolean true # URL to the public key of the local repository; you must provide a key or # apt will complain about the unauthenticated repository and so the # sources.list line will be left commented out #d-i apt-setup/local0/key string http://local.server/key # By default the installer requires that repositories be authenticated # using a known gpg key. This setting can be used to disable that # authentication. Warning: Insecure, not recommended. d-i
Re: r57367 - trunk/packages/cdebconf-terminal/debian
On Tuesday 20 January 2009, Frans Pop wrote: --- trunk/packages/cdebconf-terminal/debian/control (original) +++ trunk/packages/cdebconf-terminal/debian/control Mon Jan 19 23:36:21 2009 @@ -11,7 +11,7 @@ -Provides: cdebconf-entropy +Provides: cdebconf-terminal I wonder if that will cause problems for Lenny installs. It is quite likely that it has escaped testing efforts if it does... Looks like it is harmless. signature.asc Description: This is a digitally signed message part.
Bug#512398: debian-installer: Debian Install CD should have an skip CD-boot option as for example in SuSE
Package: debian-installer Version: 20081029 and others Severity: wishlist Hi debian-installer Maintainers, It would be great to have an option to skip the CD boot integrated - `Boot from hard disk` As working for an ISP I often have to go down to the BIOS and change the boot order with an Debian GNU/Linux CD in drive in a Lights Out Environment. I'm unsure if a 60 sec timeout to boot from harddisk as in SuSE may be cool, but at least an option to do this would be a great comfort. Best regards, Jan Rasche -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (900, 'unstable'), (600, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
* Rick Thomas rbthoma...@pobox.com [2009-01-13 10:05]: Sorry, I was wrong here. Yeah, this sounds like an interesting approach. I don't think regenerating the image should be necessary. If --payload Yes, as I said, I was wrong. You can just specify --payload with an existing image when uploading to the NSLU2. can be used along with the image you provide, then there could be code in the image that looks to see if the payload area has something that looks like a preseed (maybe a magic number or checksum or timestamp or something else to be reasonably sure we're not being fooled by random data or by stuff left-over from the last d-i.) If there is, it can use it, if not, it can ignore it. Or am I missing something? I don't know much about the internals of the upslug2 process, so I'm sure there's plenty I could be missing. Is there documentation beyond the upslug2 man page I could look at? In particular, I gather that the program on the slug end of the upslug2 process is called redboot -- is that correct? Is there a Linksys manual or technical paper describing redboot? The boot loader on the NSLU2 is RedBoot, but I don't think this payload has anything to do with RedBoot per se. I think the payload features simply writes the data to a location in flash that isn't used for anything. But I don't know any details myself about this feature. I've copied Rod Whitby who should be able to point to more documentation (if it exists) or give us more information. I should mention again, though, that while this feature might be nice to have, I'm personally not interested in working on it (because there are so many other things on my TODO list from which more people will benefit than from this feature). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506252: marked as done (success: d-i lenny rc1 on nslu2 armel)
Your message dated Tue, 20 Jan 2009 15:46:46 +0100 with message-id 20090120144646.gt...@deprecation.cyrius.com and subject line Re: Bug#506252: success: d-i lenny rc1 on nslu2 armel has caused the Debian Bug report #506252, regarding success: d-i lenny rc1 on nslu2 armel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 506252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: normal -- Package-specific info: Boot method: network (upslug2) Image version: Unofficial nslu2 image (stock lenny image plus onboard ethernet microcode), http://www.slug-firmware.net/d-dls.php Date: Date and time of the install Machine: Linksys NSLU2 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [E] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Timezone setup was fine, but the system RTC does not appear to be running, so attempts to write to the hardware clock (which require an RTC poll) failed, causing a brief (but properly detected by the installer) hang. Installed files were timestamped correctly, but on post-install reboot the clock was wrong (also if the clock isn't running the hwclock access on boot will stall, taking hours for the first boot, but I'd disabled that before the reboot.) I let tasksel proceed with the default Standard system task, which was a mistake -- it took over an hour to install those packages, most of which I then had to remove manually. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=5.0 (lenny) - installer build 20081029 X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == umame -a: Linux slug 2.6.26-1-ixp4xx #1 Fri Oct 10 02:29:27 UTC 2008 armv5tel unknown lspci -knn: 00:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) lspci -knn: Kernel driver in use: ehci_hcd lsmod: Module Size Used by lsmod: jfs 166636 0 lsmod: reiserfs 245524 0 lsmod: dm_mod 56268 0 lsmod: ext3 123304 1 lsmod: jbd45396 1 ext3 lsmod: vfat9952 0 lsmod: fat48156 1 vfat lsmod: nls_base7168 3 jfs,vfat,fat lsmod: ext2 63496 0 lsmod: mbcache 7872 2 ext3,ext2 lsmod: sd_mod 22736 3 lsmod: usb_storage82375 2 lsmod: scsi_mod 111076 2 sd_mod,usb_storage lsmod: evdev 8608 0 lsmod: ohci_hcd 18212 0 lsmod: ehci_hcd 35148 0 lsmod: ixp4xx_eth 12216 0 lsmod: ixp4xx_npe 7936 2 ixp4xx_eth lsmod: ixp4xx_beeper 2720 0 lsmod: firmware_class 7552 1 ixp4xx_npe lsmod: ixp4xx_qmgr 5336 6 ixp4xx_eth lsmod: usbcore 128252 4 usb_storage,ohci_hcd,ehci_hcd df: Filesystem 1k-blocks Used Available Use% Mounted on df: tmpfs1476824 14744 0% /dev df: /dev/sda2 7223032620492 6235628 9% /target df: /dev/sda2 7223032620492 6235628 9% /dev/.static/dev df: tmpfs1476824 14744 0% /target/dev df: tmpfs1476824 14744 0% /target/dev free: total used free
Bug#512398: debian-installer: Debian Install CD should have an skip CD-boot option as for example in SuSE
reassign 512398 debian-cd thanks On Tuesday 20 January 2009, xcomm wrote: It would be great to have an option to skip the CD boot integrated - `Boot from hard disk` As working for an ISP I often have to go down to the BIOS and change the boot order with an Debian GNU/Linux CD in drive in a Lights Out Environment. I'm not sure if this is something that would need to be implemented in the program that generates CD images (genisoimage) or in the bootloader (isolinux). I would guess the first. Reassigning to the debian-cd team as they may know and it's more appropriate there anyway. Maybe it's already possible even? I know Windows CDs will prompt to press any key to boot from CD during 5 seconds or so _if_ there is an alternative bootable device. There is at least one disadvantage to changing this: it makes booting the installer a bit more awkward for visually handicapped users. I'm unsure if a 60 sec timeout to boot from harddisk as in SuSE may be cool, but at least an option to do this would be a great comfort. It would be great if you could find out how they have implemented that and add that info to this bug report. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#512398: debian-installer: Debian Install CD should have an skip CD-boot option as for example in SuSE
Processing commands for cont...@bugs.debian.org: reassign 512398 debian-cd Bug#512398: debian-installer: Debian Install CD should have an skip CD-boot option as for example in SuSE Bug reassigned from package `debian-installer' to `debian-cd'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: On installation media and firmware [Re: New section for firmware]
On Tue, 13 Jan 2009, Frans Pop wrote: On Tuesday 13 January 2009, Don Armstrong wrote: Sure it does; it's a set of the initial media which contains the non-free firmware in *addition* to the normal stuff contained on the fully DFSG-free media. [You'd just need this for CD1, the netinst, business card and cd images, and perhaps the m-a DVD.] The only additional user-facing complexity is the additional media and the need for users to be able to differentiate between the media types. I cannot make it more clear than this: the debian-boot and debian-cd teams are against any such solution. That's all fine and good, but why? Don Armstrong -- No matter how many instances of white swans we may have observed, this does not justify the conclusion that all swans are white. -- Sir Karl Popper _Logic of Scientific Discovery_ http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: D-I build
Christian Perrier bubu...@debian.org writes: (again sorry for appearing to push hard, here) Now that all unblocks were requested (as I tried to track on LennyRC2Prep), I suppose the next step is to build and upload D-I, right? I have a pending commit in webwml for the errata and home pages, just tell me when to commit it. A last time upload of win32-loader that is suitable for Lenny has been done and I'm waiting for it to upload debian-installer source package. It looks it is going today and then we'll be able to upload later today or tomorrow. :-) -- O T A V I OS A L V A D O R - E-mail: ota...@debian.org UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [RFC] New installer-settings component - please test and comment!
Below a reply to a very old post from Joey [1] to which I should have replied then, but never got around to. I've quoted his mail in full for context. [1] http://lists.debian.org/debian-boot/2008/05/msg00345.html On Thursday 08 May 2008, Joey Hess wrote: A long, long time ago I proposed changing the main menu into a kind of list of settings like this. Language: English Location: United States Network: autoconfigure Disk: autopartition entire disk (hda1) Users: root, joey Software: desktop, print-server Grub: install to MBR, no other OS Finish installation I get the idea, but I don't really see the implementation. For a lot of components I just don't see how you could usefully translate them into a value and there's also the problem of limited line length. Select a menu item to configure it, thereby running the menu item at medium priority, or skip over it if the default setting looks good (and skipped over menu items would run noninteractively at high[1] priority as needed to satisfy dependencies). Once you have such a menu, it's easy to add things to it, without them getting in the way unduely. As long as there arn't *too* many. Language: English Location: United States Mouse: PS/2 Theme: foo Network: autoconfigure Disk: hda1, autopartition entire disk Users: root, joey Software: desktop Grub: no other OS Finish installation Expert mode: disabled Rescue mode: disabled Of course, submenus could also conceivably branch off of this. installer-settings essentially implements a submenu. I also feel that the implementation I have now is one that does not get in the way, especially since it is only really used if the user selects expert mode, so basically he gets what he asks for. For the graphical installer it would be great if an alternative menu bar kind of interface could be implemented. Frans Pop wrote: Overview of potential settings -- * General - show expert questions (in early) - debconf priority (in menu) - rescue mode (in early/additional) - frontend theme - mouse support (device/protocol/left-handed) (in early/menu) Having these things in a submenu makes sense, I think, both in the current installer, and in the context of the above wild idea. * Hardware support - SATA RAID - multipath - PCMCIA support (could help avoid asking multiple times!) * Networking - PPPoE support (in early) - type of configuration (none/static/dhcp) - allow unauthenticated (?) * Installed system - use SUDO instead of root account - create first user * Debian settings (or Package management) - use security (?) - use volatile (?) - use contrib (?) - use non-free (?) * Advanced - keep regular virtual consoles (sercon installs) - eject CD - halt/poweroff system instead of reboot I'm not convinced that it makes sense to have a menu with these things on it, rather than just asking the questions at relevant times with appropriate priorities. For a number of them I'm inclined to agree. We will have to be very careful about which we do and which we don't select. But I also feel quite strongly about keeping the number of times to hit enter for a full install as low as possible. And there are some options that IMO really should be more easily accessible to users, *without* forcing them to go through _all_ possible dialogs and permutations. One example is the eject CD option. This really does cause problems sometimes, but not enough to warrant an extra dialog during finish-install warning that the CD is about to be ejected. Currently the only way to prevent CD ejection is using a boot option, which most users don't know about and which you have to remember at a time that your mind just isn't on that stage of the installation. Having it as a setting Eject CD at end of install means that users will both have an easy way to change it _and_ have a visual reminder. To what extent are the problems this is trying to solve due to us having gotten into the bad habit of adding debconf settings but never actually displaying a question for them? AFAIK we've only done that for functionality that is still experimental. It's always been the intention to make them properly accessible, or to support them by default, once better implemented. ATM both dmraid and multipath still rely on very crude bootloader installer support. More general, for support of things like PPPoE, dmraid and multipath the installer can IMO go two ways: 1) support by default, which means additional memory usage and potential failure modes; 2) offer it as optional functionality. Given that all three are only relevant for a fairly small subset of users, I feel that the second option is quite realistic. But neither forcing those users to the current expert mode
kernel-wedge 2.53 MIGRATED to testing
FYI: The status of the kernel-wedge source package in Debian's testing distribution has changed. Previous version: 2.52 Current version: 2.53 -- This email is automatically generated; the Debian Release Team debian-rele...@lists.debian.org is responsible. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
win32-loader 0.6.10 MIGRATED to testing
FYI: The status of the win32-loader source package in Debian's testing distribution has changed. Previous version: 0.6.9 Current version: 0.6.10 -- This email is automatically generated; the Debian Release Team debian-rele...@lists.debian.org is responsible. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Making commits by l10n-sync no longer silent?
Currently, the regular commits done by l10n-sync are silent, which means they are not sent to debian-installer_...@qa.debian.org like othere commits. I'm considering to drop this as this is exactly what made us fail to notice the problem happening with the packages/po/sublevel4/da.po file. Are there any objections? It means that people who receive commits will receive more mails as, each time a translation is updated and each time a package's templates are modified, the subsequent l10n-sync run will include commit to one or more files. An intermediate solution would of course be tagging them with a specific marker (this is indeed how the commits are silenced right now, by using [SILENT_COMMIT]). -- signature.asc Description: Digital signature
Re: D-I in Release Notes update
Quoting Christian Perrier (bubu...@debian.org): Quoting W. Martin Borgert (deba...@debian.org): I can commit what I have right now. That will anyway be bette rthan what we have now. OK, go ahead. It has been committed. Given that D-I release is very near now, I think that a call for translation updates should be sent ASAP A paragraph is very unclear: para The languages that can only be selected using this installer as their character sets cannot be presented in a non-graphical environment are: Amharic, Bengali, Dzongkha, Gujarati, Hindi, Georgian, Khmer, Malayalam, Marathi, Nepali, Punjabi, Tamil and Thai. /para I'm afraid this just means nothing...:-( So, I'll need to rewrite it. We're also missing a long description of SATA RAID as I mentioned already, but here I'm less comfortable to write it. -- signature.asc Description: Digital signature
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
* Rick Thomas rbthoma...@pobox.com [2009-01-13 10:39]: I think explicitly mentioning domain as well as hostname and IP- address should be all that's required. The hostname was mentioned already. I've added a reference to domain now too. Thanks. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#512261: Bug 512261 Update - Resolution
Package: installation-reports Installation was able to complete without errors when the following iso file was used. http://cdimage.debian.org/cdimage/lenny_di_rc1/amd64/iso- cd/debian-testing-amd64-netinst.iso 05-Nov-2008 The only inconvenience was that GRUB 2 did not automatically detect an MS-DOS partition. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#512427: installation-reports: investigating mini-i386.iso menu functionality - installation on a SATA bios raid0 stripe
Package: installation-reports Severity: normal Machine: generic D865PERLK P4 3GHz 512 L2, 1GB pc3200, onboard GB-lan, audio, Winfast Gforce-256 32MB ddr, Winfast 2000tv, Istor SATA RAID, 2 - Western Digital 120GB ATA/100, NEC 16x DVD-RW, SONY 16x DVD-RW -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash sfdisk -l Disk /dev/sda: 14593 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/sda1 * 0+ 30 31-248976 83 Linux /dev/sda2 31 67 37 297202+ 83 Linux /dev/sda3 68 110 43 345397+ 83 Linux /dev/sda4111 29185 29075 233544937+ 5 Extended Disk /dev/sdb: 14593 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-1: 29186 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/dm-1p1 * 0+ 30 31-248976 83 Linux /dev/dm-1p2 31 67 37 297202+ 83 Linux /dev/dm-1p3 68 110 43 345397+ 83 Linux /dev/dm-1p4111 29185 29075 233544937+ 5 Extended /dev/dm-1p5111+ 15691459- 11719386 83 Linux /dev/dm-1p6 1570+ 43652796- 22458838+ 83 Linux /dev/dm-1p7 4366+ 71612796- 22458838+ 83 Linux /dev/dm-1p8 7162+ 99572796- 22458838+ 83 Linux /dev/dm-1p9 9958+ 127532796- 22458838+ 83 Linux /dev/dm-1p10 12754+ 155492796- 22458838+ 83 Linux /dev/dm-1p11 15550+ 183452796- 22458838+ 83 Linux /dev/dm-1p12 18346+ 211412796- 22458838+ 83 Linux /dev/dm-1p13 21142+ 251534012- 32226358+ 83 Linux /dev/dm-1p14 25154+ 290433890- 31246393+ 83 Linux /dev/dm-1p15 29044+ 29185 142- 1140583+ 82 Linux swap / Solaris Disk /dev/dm-0: 30 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-2: 37 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-3: 43 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-4: 1458 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-5: 2795 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-6: 2795 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-7: 2795 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-8: 2795 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-10: 2795 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-9: 2795 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-11: 2795 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-12: 4011 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-13: 3889 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-14: 141 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-15: 14593 cylinders, 255 heads, 63 sectors/track Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/dm-15p1 * 0+ 30 31-248976 83 Linux /dev/dm-15p2 31 67 37 297202+ 83 Linux /dev/dm-15p3 68 110 43 345397+ 83 Linux /dev/dm-15p4111 29185 29075 233544937+ 5 Extended Disk /dev/dm-16: 14593 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-17: 30 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-18: 37 cylinders, 255 heads, 63 sectors/track Disk /dev/dm-19: 43 cylinders, 255 heads, 63 sectors/track df -hlT FilesystemTypeSize Used Avail Use% Mounted on /dev/mapper/isw_cabeaigada_isto5 xfs 12G 3.0G 8.3G 27% / tmpfstmpfs505M 0 505M 0% /lib/init/rw udev tmpfs 10M 176K 9.9M 2% /dev tmpfstmpfs505M 0 505M 0% /dev/shm /dev/mapper/isw_cabeaigada_isto1 ext3236M 22M 202M 10% /boot Initially I started the installer in expert mode priority low and dmraid true. IIRC the main menu didn't show up until after partman when I switched to multipath support. I used guided partitioning with LVM. I was in new territory both with the installer in expert mode and finding the right settings to get the installer to work with me. The finished installation didn't boot- grub error 2. I reboot in rescue mode 3 times in all finally finishing the installation in rescue mode.I took a look around the filesystem and chroot(ed) in rescue mode. I got stuck with libc6 - finally erasing the partition and continuing. I rebooted again in rescue mode but didn't offer the dmraid option. So I rebooted in rescue mode again using the dmraid option. The installer kept trying to mount /dev/sda1 on /target when entering rescue? from the main menu and failing, obviously
Bug#511177: Bug 511177 Update 2 - Possible Resolution
Package: installation-reports The image file below may solve the reported problems. This was not tried because Etch installed successfully and an upgrade is possible from that. This image, however, is the one recommended when all others fail installation. The amd64 version of this image installed successfully on an Athlon 64 x2 machine on which the reported image failed. http://cdimage.debian.org/cdimage/lenny_di_rc1/i386/iso- cd/debian-testing-i386-netinst.iso 05-Nov-2008 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Making commits by l10n-sync no longer silent?
On Tuesday 20 January 2009, Christian Perrier wrote: Are there any objections? IMO it is useless to send them to everybody. An intermediate solution would of course be tagging them with a specific marker (this is indeed how the commits are silenced right now, by using [SILENT_COMMIT]). And send them only to yourself (and maybe one backup person)? I also still feel that having daily syncs is way too much and leads to way too many commits which have the side effect of obscuring other changes. I can see some point in having daily sync runs after a call for translation updates when a release is being prepared, but at other times I feel that e.g. 3 times per week would be more than enough. signature.asc Description: This is a digitally signed message part.
Bug#489544: installation-reports
Hi Jérémy, sorry to have taken so long to get back! I had to give my brother the flash drive, and only recently got another one to test with. I tried this installation again with a daily build: == Daily build #3 for i386, using installer build from sid == This build finished at Sat Jan 17 15:10:11 UTC 2009. The problem still stands -- /scripts/local-top/cryptroot does not wait for its cryptsource, and reaches here: message cryptsetup: source device $cryptsource not found return 1 I guess the assumption is that udev_settle would find the device, but it seems not to -- udev_settle considers itself finished *before* all the USB devices have been detected, so udev_settle isn't doing what we expect in this case. As requested, here are the versions: ii cryptsetup2:1.0.6-7 ii initramfs-tools 0.92o Cheers, David On Wed 30 Jul 2008 2:21 am, Jérémy Bobbio wrote: On Wed, Jul 30, 2008 at 12:47:02AM -0700, David L. Emerson wrote: I've just finished a similar installation with the Lenny beta 2 installer (encrypted lvm on bootable usb flash drive) Thanks. I would have been more happy if you would have used a daily build, but it's great nevertheless. re Problem 3: STILL A BIG PROBLEM. Here are the boot messages: Uncompressing Linux... Ok, booting the kernel. Loading, please wait... Volume group socrates not found Setting up cryptographic volume sda2_crypt (based on /dev/sda2) cryptsetup: Source device /dev/sda2 not found [... wait about 5 seconds ...] sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Assuming drive cache: write through [... forehead - desk ...] [... wait about a minute, then it drops to busybox because the /dev/mapper/socrates-root_vol does not exist ...] so, it looks like I will have to manually reroll the initramfs again. If you want me to test again with a later version, I'll try and figure out a way to do that :) Could you give me the installed version of the initramfs-tools and cryptsetup packages? I have seen similar issues being fixed in recent version of those packages, and I am not sure if they have migrated to Lenny yet. (The development version of debian-installer installs testing by default.) Cheers, -- Jérémy Bobbio.''`. lu...@debian.org: :Ⓐ : # apt-get install anarchism `. `'` `- -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: D-I in Release Notes update
Hi, [I already reported this to debacle, I have no info if there was a reaction already. Then I read the mail on debian-boot, that Christian found an error in the release notes.] On Tue, 20 Jan 2009 18:56:55 +0100 Christian Perrier wrote: A paragraph is very unclear: [...] I'm afraid this just means nothing...:-( So, I'll need to rewrite it. I found some more: # type: Content of: chaptersectionpara #: en/installing.dbk:34 msgid There has been a lot of development on the Debian Installer since its first official release with oldreleasename; resulting in both improved hardware support and some exciting new features. msgstr Es wurde am Debian-Installer viel entwickelt seit seinem ersten offiziellen Erscheinen mit oldreleasename;, was zu verbesserter Hardware-Unterstützung, sowie einigen neuen Funktionen führt. This comes to: ... since its first official release with Etch resulting ... but this is not correct, the Debian Installer came up with Sarge the first time. Write Sarge without any entity? Or: What is this chapter about? Development since Etch, right? So change to: There has been a lot of development on the Debian Installer since the release of oldreleasename; resulting in ... # type: Content of: chaptersectionsectionvariablelistvarlistentrylistitempara #: en/installing.dbk:78 msgid When used with a functional network access, the installer will upgrade all packages that were updated since the initial release of releasename;. This upgrade happens during the installation step, before the installed system is booted dot is missing at the end. Greetings Holger -- == Created with Sylpheed 2.3.0 under DEBIAN GNU/LINUX 4.0 Etch http://counter.li.org/, Registered LinuxUser #311290 = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510271: installation-report: Lenny on a Slug - eventual success after a few tries and some fixups
Martin Michlmayr wrote: * Rick Thomas rbthoma...@pobox.com [2009-01-13 10:05]: Sorry, I was wrong here. Yeah, this sounds like an interesting approach. I don't think regenerating the image should be necessary. If --payload Yes, as I said, I was wrong. You can just specify --payload with an existing image when uploading to the NSLU2. can be used along with the image you provide, then there could be code in the image that looks to see if the payload area has something that looks like a preseed (maybe a magic number or checksum or timestamp or something else to be reasonably sure we're not being fooled by random data or by stuff left-over from the last d-i.) If there is, it can use it, if not, it can ignore it. Or am I missing something? I don't know much about the internals of the upslug2 process, so I'm sure there's plenty I could be missing. Is there documentation beyond the upslug2 man page I could look at? In particular, I gather that the program on the slug end of the upslug2 process is called redboot -- is that correct? Is there a Linksys manual or technical paper describing redboot? The boot loader on the NSLU2 is RedBoot, but I don't think this payload has anything to do with RedBoot per se. I think the payload features simply writes the data to a location in flash that isn't used for anything. But I don't know any details myself about this feature. I've copied Rod Whitby who should be able to point to more documentation (if it exists) or give us more information. Source code for the upgrade protocol in the Linksys (written by SerComm) version of RedBoot is available. The --payload switch to upslug2 is probably not used by anyone in the world at the moment (we certainly haven't used it in the nslu2-linux project, nor in the NSLU2 Debian work). All it does is overwrite an area in the FIS directory partition when uploading an image. It's exactly equivalent to overwriting the bytes in the image before calling upslug2 - there is no special upgrade protocol support used or required. So nothing uses that area today (we were considering using it for IXP microcode storage, but decided to put it in the rootfs instead), and no Linksys software touches that area (which is why we originally thought of using it, and added support for that in the tools). However, it will be overwritten by each flash of the NSLU2, so is different from the SysConf area (which is currently used for preseeding network settings) in that respect. -- Rod -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#512457: console-setup: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: console-setup Tags: l10n patch Severity: wishlist Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards, - -- Flamarion Jorge -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl2Se8ACgkQ0SDRnmynUOH79gCeK5hH2AGDZ6sU/+QZS5FPI3BB nzEAnA4tpEMpqv4LTzbUV/O+js8HN4qW =ueje -END PGP SIGNATURE- # Portuguese/Brazil translation of console-setup. # Copyright (C) 2009 THE console-setup'S COPYRIGHT HOLDER # This file is distributed under the same license as the console-setup package. # Flamarion Jorge jorge.flamar...@gmail.com, 2009. # msgid msgstr pt_BR utf-8\n Project-Id-Version: console-setup 1.28\n Report-Msgid-Bugs-To: console-se...@packages.debian.org\n POT-Creation-Date: 2008-07-11 20:12+0200\n PO-Revision-Date: 2009-01-08 03:48-0200\n Last-Translator: Flamarion Jorge jorge.flamar...@gmail.com\n Language-Team: Brazilian Portuguese debian-l10n-portugu...@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit #. Type: text #. Description #. Main menu item. Please keep below 55 columns #: ../console-setup.templates:1001 msgid Configure the keyboard msgstr Configurar o teclado #. Type: select #. Choices #: ../console-setup.templates:2001 msgid . Arabic msgstr . Ãrabe #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Armenian msgstr # Armênio #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Cyrillic - KOI8-R and KOI8-U msgstr # CirÃlico - KOI8-R e KOI8-U #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Cyrillic - non-Slavic languages msgstr # CirÃlico - lÃnguas não-eslavas #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Cyrillic - Slavic languages (also Bosnian and Serbian Latino) msgstr # CirÃlico - LÃnguas eslavas (também bósnio e sérvio latim) #. Type: select #. Choices #: ../console-setup.templates:2001 msgid . Ethiopic msgstr . EtÃope #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Georgian msgstr # Georgiano #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Greek msgstr # Grego #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Hebrew msgstr # Hebraico #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Lao msgstr # Laociano #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Latino1 and Latin5 - western Europe and Turkic languages msgstr # Latino1 e Latin5 - Europa Ocidental e lÃnguas Turcas #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Latino2 - central Europe and Romanian msgstr # Latino2 - Europa Central e Romeno #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Latino3 and Latin8 - Chichewa; Esperanto; Irish; Maltese and Welsh msgstr # Latino3 e Latin8 - Chichewa; Esperanto; Irlandês; Maltês e Galês #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Latino7 - Lithuanian; Latvian; Maori and Marshallese msgstr # Latino7 - Lituano; Letão; Maori e Marshallese #. Type: select #. Choices #: ../console-setup.templates:2001 msgid . Latino - Vietnamese msgstr . Latino - Vietnamita #. Type: select #. Choices #: ../console-setup.templates:2001 msgid # Thai msgstr # Tailandês #. Type: select #. Choices #: ../console-setup.templates:2001 msgid . Combined - Latino; Slavic Cyrillic; Hebrew; basic Arabic msgstr . Combinado - Latino; Eslavo CirÃlico; Hebraico; Ãrabe básico #. Type: select #. Choices #: ../console-setup.templates:2001 msgid . Combined - Latino; Slavic Cyrillic; Greek msgstr . Combinado - Latino; Eslavo CirÃlico; Grego #. Type: select #. Choices #: ../console-setup.templates:2001 msgid . Combined - Latino; Slavic and non-Slavic Cyrillic msgstr . Combinado - Latino; Eslavo e não-Eslavo CirÃlico #. Type: select #. Description #: ../console-setup.templates:2002 msgid Set of characters that should be supported by the console font: msgstr Escolha os caracteres que são suportados pela fonte do console: #. Type: select #. Description #: ../console-setup.templates:2002 msgid If you don't use a framebuffer, the choices that start with \.\ will reduce the number of available colors on the console. msgstr Se você não usa um framebuffer, as escolhas que começam com \.\ reduzirão o número de cores disponÃveis no console. #. Type: select #. Description #: ../console-setup.templates:3001 msgid Keyboard model: msgstr Modelo do teclado: #. Type: select #. Description #: ../console-setup.templates:4001 msgid Origin of the keyboard: msgstr Origem do teclado: #. Type: select #. Description #: ../console-setup.templates:5001 msgid Keyboard layout: msgstr Layout do teclado: #.
