Re: [PATCH] support live image installing mode selection
Christian Perrier wrote: > _Description: Installation mode: > Please select the installation mode to be used. > . > By choosing 'normal', the installed system will be a regular system > running from disk while 'live' will continue by running a system > without any physical installation on disk. How about something like this? _Description: Installation mode: Please select the installation mode to be used. . By choosing 'normal', the installed system will installed as a regular system while choosing 'live', the system will continue to act as a live system with the only difference that it is directly launched from the harddisk instead of an external/another/boot/$whatever medium. (the 'external/another/boot/$whatever' is not ment literally, don't know which one is the best to choose). -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#469650: console-setup: [INTL:eu] debconf templates Basque translation
Package: console-setup Severity: wishlist Tags: patch l10n d-i Hi Attached console-setup debconf templates basque translation, please commit it. thx -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=eu_ES.UTF-8, LC_CTYPE=eu_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-setup depends on: pn console-terminus (no description available) ii debconf [debconf-2. 1.5.19 Debian configuration management sy ii xkb-data1.1~cvs.20080104.1-1 X Keyboard Extension (XKB) configu Versions of packages console-setup recommends: ii console-tools 1:0.2.3dbs-65 Linux console and font utilities # translation of eu.po to Euskara # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER # This file is distributed under the same license as the PACKAGE package. # # Piarres Beobide <[EMAIL PROTECTED]>, 2008. msgid "" msgstr "" "Project-Id-Version: eu\n" "Report-Msgid-Bugs-To: [EMAIL PROTECTED]" "POT-Creation-Date: 2008-01-05 10:30+0100\n" "PO-Revision-Date: 2008-03-06 11:51+0100\n" "Last-Translator: Piarres Beobide <[EMAIL PROTECTED]>\n" "Language-Team: Euskara <[EMAIL PROTECTED]>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.11.4\n" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid ". Arabic" msgstr ". Arabiarra" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Armenian" msgstr "# Armeniarra" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Cyrillic - KOI8-R and KOI8-U" msgstr "# Zirilikoa - KOI8-R eta KOI8-U" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Cyrillic - non-Slavic languages" msgstr "# Zirilikoa - hizkuntza ez-eslaviarrak" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Cyrillic - Slavic languages (also Bosnian and Serbian Latin)" msgstr "# Zirilikoa - Hizkuntza eslaviarrak (Bosnia eta Serbiar Latina barne)" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid ". Ethiopic" msgstr ". Etiopiarra" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Georgian" msgstr "# Georgiarra" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Greek" msgstr "# Grekoa" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Hebrew" msgstr "# Hebreera" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Lao" msgstr "# Laosera" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Latin1 and Latin5 - western Europe and Turkic languages" msgstr "# Latin1 eta Latin5 - mendebaldeko europa eta turkiar hizkuntza" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Latin2 - central Europe and Romanian" msgstr "# Latin2 - erdiko europa eta errumaniera" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Latin3 and Latin8 - Chichewa; Esperanto; Irish; Maltese and Welsh" msgstr "# Latin3 eta Latin8 - Chichewa Esperantoa Irlandako gaelikoa Maltera eta Gaelikoa" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Latin7 - Lithuanian; Latvian; Maori and Marshallese" msgstr "# Latin7 - Lituaniera, Letoniera, Maoriera eta Marshallera" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid ". Latin - Vietnamese" msgstr ". Latina - Vietnamera" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid "# Thai" msgstr "# Thailandiarra" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid ". Combined - Latin; Slavic Cyrillic; Hebrew; basic Arabic" msgstr ". Nahasia - Latina; Eslaviar Zirilikoa; Hebreera; Arabiera soila" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid ". Combined - Latin; Slavic Cyrillic; Greek" msgstr ". Nahasia - Latina; Eslaviar zirilikoa; Grekoa" #. Type: select #. Choices #: ../console-setup.templates:1001 msgid ". Combined - Latin; Slavic and non-Slavic Cyrillic" msgstr ". Nahasia - Latina; Eslaviar eta ez-eslaviar Zirilikoa" #. Type: select #. Description #: ../console-setup.templates:1002 msgid "Set of characters that should be supported by the console font:" msgstr "Kontsola letra-tipoak onartu behar dituen karaktere jokoak:" #. Type: select #. Description #: ../console-setup.templates:1002 msgid "" "If you don't use framebuffer the choices that start with dot will reduce the " "number of the available colors on the console." msgstr "" "Frambuffer erabiltzen ez baduzu puntu batez hasten diren aukerak kontsolan " "erabilgarri diren kolore kopurua gutxiagotuko dute." #. Type: select #. Description #: ../console-setup.templates:2001 msgid "Keyboard model:" msgstr "Teklatua modeloa:" #. Type: select #. Description #
cdebconf-entropy plugin: usage, templates and strings
Hi!
One of the initial goal of the work done on improving the GTK+ frontend
code was to make it provide a simple API for plugins. This work has
been completed and integrated in the current cdebconf version, but
useful plugins as yet to be written.
The first plugin to be written, obviously, is the graphical sibling to
the plugin gathering entropy, used in partman-crypto. The code for this
plugin was actually written while working on the rest of the GTK+
frontend [1] but as yet to be integrated properly.
[1] http://people.debian.org/~lunar/fe_gtk-plugin-entropy.c
I have taken another look at this, and I stumbled on a few issues on
which I would welcome advices…
The cdebconf-entropy source packages currently build a plugin named
"newt/plugin-entropy-text.so" which will introduces a new question type,
"entropy-text".
This question type is only used currently in partman-crypto by the
following template:
Template: partman-crypto/entropy-text
Type: entropy-text
_Description: Enter random characters
The encryption key for ${DEVICE} is now being created.
.
You can help speed up the process by entering random characters on
the keyboard, or just wait until enough keydata has been collected.
(NOTE: this can take a long time)
The straightforward way to add an entropy gathering plugin would be to
add another question type, for example "entropy-gui", add another
template in partman-crypto, duplicate all code checking for the plugin
and be done with it.
But I think this would be sub-obtimal. :)
I think it would make more sense to make a single question type, for
both frontend, named "entropy", and to have a single question template
in partman-crypto and a single code path handling both frontends.
But the strings displayed to the user becomes problematic: we need to
ask for random characters on the keyboard for the newt frontend, but it
would be a shame not to mention random mouse movements for the GTK+
frontend.
In the previous template, two strings are not actually relevant to the
question asked, but to the frontend asking it:
frontend specific
vvv
_Description: Enter random characters
The encryption key for ${DEVICE} is now being created.
.
> You can help speed up the process by entering random
same > characters on the keyboard, or just wait until enough
here > keydata has been collected. (NOTE: this can take a long
> time)
I thought about using the newly introduced debconf directives, but I
might just wanna play with a new toy here. So I really want to know
other advices before hacking… Here is the proposed implementation,
though:
Using directives would make the previous template look like:
_Description: ${!ENTROPY_SHORT_TITLE}
The encryption key for ${DEVICE} is now being created.
.
${!ENTROPY_GENERATE_MORE}
A new text template would be introduced in each plugin built by
cdebconf-entropy. Its short description would be used for
ENTROPY_SHORT_TITLE and ENTROPY_GENERATE_MORE would be its extended
description.
I'm not totally happy with this approach. If anyone can think about
anything (and I'm sure you can! ;)), please speak up. :)
Cheers,
--
Jérémy Bobbio.''`.
[EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism
`. `'`
`-
signature.asc
Description: Digital signature
Re: [RFC] Column alignment in debconf {multi,}selects, take 2
On Thu, Mar 06, 2008 at 03:33:23AM +0100, Frans Pop wrote:
> > At some point, I was wondering if it would not be better just to drop
> > the whole directive idea and push '\t' forward again, but I have
> > actually an use-case for another directive related to "align" support:
> > ${!RIGHT_ALIGN}. As you can see on the attached screenshot, partman's
> > choose_partition would be a little bit better if partition sizes were
> > right aligned. Work stills need to be done, though.
>
> I guess that screenshot is with columns implemented, but not yet with the
> right alignment, right?
Sorry if that was not clear enough. So the screenshot is the screenshot
of a handmade revised version of the partman/choose_partition template,
available in cdebconf/src/test/align.templates.
After creating this template to see how it could look like, I have
noticed the alignment issue. IMHO, having right alignment support is a
minor improvement over no alignment support, so I would prefer to get
alignment support in-tree first.
> One thing to keep in mind for implementing columns in partman's main screen
> is that currently the content of columns may differ for different types of
> partition tables. I noticed that myself on my sparc box when I had one disk
> with msdos disklabel and another with sparc disklabel. May even still have
> a screenshot of that around somewhere.
> They can also differ (I think) for things like LVM and RAID.
> Life is never easy :-/
Well… while trying to figure out where to put the needed ${!TAB} in
partman code I have discovered several things:
- My previous implementation of directives would not work, as
debconf_select currently relies on getting exactly one of the choice
it had put in ${CHOICES} as the result. Previously, I was expanding
directives everywhere which would not have worked well with that.
- debconf_select and ask_user do use several splitting tricks that
could probably be removed in favor of using Choices-C instead. The
code would be *a lot* simplier and faster as well.
- Putting columns properly will require quite a lot of work. :D
But anyway, I am not pushing changes in partman yet. I do think there is
a little bit of restructuring needed first.
> Something to keep in mind for right aligning a column is to preserve correct
> support for RTL scripts (e.g. Hebrew).
Thanks for reminding. :)
> Take the localechooser patch:
> $translation = $name .
> (" " x (22 - length($name))).
> - "- $translation";
> + "\${!TAB}- $translation";
>
> What you do here is to keep the old spaces based alignment and add the tab
> separator.
Indeed! :)
> IMO for really consistent tabs support this should be changed
> to:
> $translation = $name .
> -(" " x (22 - length($name))).
> - "- $translation";
> + "\${!TAB}- $translation";
> or even:
> - $translation = $name .
> -(" " x (22 - length($name))).
> - "- $translation";
> + $translation = $name\${!TAB}-\${!TAB}$translation";
Ok, local tree updated with your second proposal. Here are screenshots
of the newt [1] and GTK+ [2] frontends.
I wonder if we should just not drop the dash completely: it just looks
like an inverted column separator, now that alignment is done
correctly. [3,4]
[1] http://people.debian.org/~lunar/localechooser-aligned-newt.png
[2] http://people.debian.org/~lunar/localechooser-aligned-gtk.png
[3] http://people.debian.org/~lunar/localechooser-aligned-no-dash-newt.png
[4] http://people.debian.org/~lunar/localechooser-aligned-no-dash-gtk.png
> In the current implementation adding a tab for the column for these
> frontends is probably even wrong because you also leave the spaces: the tab
> adds extra space.
> Also, tabs are possibly not the best option for alignment as their effect
> very much depends on the starting column. I would think that padding with
> spaces would be easier to implement.
I think you overlooked how the implementation works in the text or newt
frontend: the proposed patch is not using actually sending '\t' to any
terminals. It is just using the character internally as the delimiter
for columns, like the GTK+ needs. These delimiters are replaced by the
correct amount of spaces by strutl.c:stralign().
Cheers,
--
Jérémy Bobbio.''`.
[EMAIL PROTECTED]: :Ⓐ : # apt-get install anarchism
`. `'`
`-
signature.asc
Description: Digital signature
Bug#469670: not run early enough when in expert mode
Package: localechooser Version: 1.46 Severity: normal When in expert mode, localechooser is not run early enough, causing the first menu option to be displayed (global menu) not to be localised, even if locale was being preseeded. The typical situation in which this happens is when using win32-loader: - User selects a language other than English (win32-loader needs to ask this as its first question, and afterwards preseeds the reply). - User selects expert mode. - win32-loader boots D-I with priority=low and locale=something. -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#469670: not run early enough when in expert mode
Processing commands for [EMAIL PROTECTED]: > tags 469670 wontfix Bug#469670: not run early enough when in expert mode There were no tags set. Tags added: wontfix > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#469670: not run early enough when in expert mode
tags 469670 wontfix thanks On Thursday 06 March 2008, Robert Millan wrote: > When in expert mode, localechooser is not run early enough, causing the > first menu option to be displayed (global menu) not to be localised, even > if locale was being preseeded. As the main menu is the thing that _drives_ all other components, there is not really any way this can be fixed other than hardcoding localechooser as some kind of exception in main-menu to be run before the menu is displayed. Given that localechooser is not included in all D-I initrds and given that this would go against the general philosophy of the installer and given that this could hinder debugging of localechooser, I don't think we want to do this. Therefore tagging wontfix. Unless others disagree with this, this report can closed at some point in the future. Cheers, FJP signature.asc Description: This is a digitally signed message part.
Bug#469680: localechooser: Current preseeding does not support some language/country options
Package: localechooser Version: 1.37 Currently language and country can only be preseeded through the locale debconf template. Although this works well for most situations, there are a few that are not supported by this system. Example is language Traditional Chinese (zh_TW) + country Hong Kong (HK). Selecting that manually will result in language=zh_TW:zh; locale=zh_HK.UTF-8 and country=HK. Preseeding 'locale=zh_HK' will result in language=zh_CN (wrong) and a prompt for the country (with default not equal to HK). Preseeding 'locale=zh_TW debian-installer/country=HK' does not improve things (the country basically gets ignored). For such cases, it should be possible to preseed locale, language and country separately. signature.asc Description: This is a digitally signed message part.
Re: Bug#469030: debian ppc64 not booting after install
I installed debian 40r3 on a IBM Power 620 (7025-f0) from CD (debian-40r3-powerpc-netinst.iso). The install was successful, but the system did not boot from the scsi disc, with the output shown below. Boot messages: Welcome to yaboot version 1.3.13 Enter "help" to get some basic usage information boot: Linux old boot: Linux Please wait, loading kernel... Elf32 kernel loaded... Loading ramdisk... ramdisk loaded at 0220, size: 5264 Kbytes OF stdout device is: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] command line: root=/dev/sda4 ro console=ttyS0 memory layout at init: alloc_bottom : 02724000 alloc_top: alloc_top_hi : rmo_top : ram_top : Looking for displays alloc_down() called with mem not initialized EXIT called ok 0 > I booted with the rescue option 'rescue64 conlose=ttyS0), booting into a chroot of the installed environment. Frans Pop suggested rebuilding the rebuild the initrd (using update-initramfs -u), but that did not work. He also suggested looking at what kernel was installed. Here is what I see when I look in the boot directory: sh-3.1# ls -la /boot total 10550 drwxr-xr-x 3 root root1024 Mar 6 15:27 . drwxr-xr-x 22 root root4096 Mar 2 17:47 .. -rw-r--r-- 1 root root 745419 Feb 12 05:05 System.map-2.6.18-6-powerpc-smp -rw-r--r-- 1 root root 57120 Feb 11 11:14 config-2.6.18-6-powerpc-smp lrwxrwxrwx 1 root root 31 Mar 2 17:48 initrd.img -> initrd.img-2.6.18-6-powerpc-smp -rw-r--r-- 1 root root 5384155 Mar 6 15:27 initrd.img-2.6.18-6-powerpc-smp drwx-- 2 root root 12288 Mar 2 17:42 lost+found lrwxrwxrwx 1 root root 28 Mar 2 17:48 vmlinux -> vmlinux-2.6.18-6-powerpc-smp -rw-r--r-- 1 root root 4551303 Feb 12 05:04 vmlinux-2.6.18-6-powerpc-smp Should the kernel not have a 64 somewhere in the name. Steve Luther suggested looking at '/proc/cmdline' to see which console the system has. I was using 'conlose=ttyS0'. In the rescue system the whole /proc is empty. This seems very odd, am I doing something wrong here? Can you please suggest how I can get the booting to work. What I have found is that the SMS menu does not list a disk if partitioned with the normal debian install tool, even with a prep partition in the beginning. I tried openSuse, and it seems to do the petitioning correctly. Any suggestions welcome, and thanks for those who have already given me some pointers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
live rescue install backup
Hello, debian-installer is very modular by design. The modular concept allows the d-i code to be (re)used as a -installer -live system -rescue system -backup and restore system The thing I didn't see yet, is a modular way to start d-i for the non installer functions like "live", "rescue" and "backup & restore". What I have see it the functions have all the own way to come alive. Would it make sense to have something like Template: d-i/function Type: string Default: installer Description: Which function should be preformed. Enter the function that should be preformed. Default is an installer. For rescue, type 'rescue' And having directories /lib/$function.d as the rescue udeb allready has? >From the README of rescue: | Rescue operation scripts | | | After asking for the root filesystem, rescue-mode displays a menu of various | operations that can be performed on this filesystem. Some of these | operations are provided by rescue-mode, while others may be provided by | separate udebs (such as bootloader reinstallation). | | Any udeb may install an executable script in /lib/rescue.d/; the name of | this script should begin with two digits, which provide a consistent menu | order, and the name may not contain "." or ":". It must provide a debconf | template of type text called "rescue/menu/" where is the name | of the script with the sequence number removed; the description of this | template will be used to construct the rescue menu. It may also provide a | debconf template of type text called "rescue//intro", which will be | displayed before running the script. Feedback is appriciated. Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: For now let's treat this as an installation issue.
Processing commands for [EMAIL PROTECTED]: > reassign 469030 installation-reports Bug#469030: debian ppc64 not booting after install Bug reassigned from package `linux-2.6' to `installation-reports'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#469030: debian ppc64 not booting after install
Hi On Thu, Mar 06, 2008 at 04:19:29PM +0200, Ulrich Enslin wrote: > > I installed debian 40r3 on a IBM Power 620 (7025-f0) from CD > (debian-40r3-powerpc-netinst.iso). The install was successful, but the > system did not boot from the scsi disc, with the output shown below. > > Boot messages: > > Welcome to yaboot version 1.3.13 > Enter "help" to get some basic usage information > boot: > Linux old > boot: Linux > Please wait, loading kernel... > Elf32 kernel loaded... > Loading ramdisk... > ramdisk loaded at 0220, size: 5264 Kbytes > OF stdout device is: /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] > command line: root=/dev/sda4 ro console=ttyS0 > memory layout at init: > alloc_bottom : 02724000 > alloc_top: > alloc_top_hi : > rmo_top : > ram_top : > Looking for displays > alloc_down() called with mem not initialized > EXIT called ok > 0 > This looks like the kernel dies very early during the boot. > > I booted with the rescue option 'rescue64 conlose=ttyS0), booting into a > chroot of the installed environment. > > Frans Pop suggested rebuilding the rebuild the initrd (using update-initramfs > -u), but that did not work. He also suggested looking at what kernel was > installed. Here is what I see when I look in the boot directory: > > sh-3.1# ls -la /boot > total 10550 > drwxr-xr-x 3 root root1024 Mar 6 15:27 . > drwxr-xr-x 22 root root4096 Mar 2 17:47 .. > -rw-r--r-- 1 root root 745419 Feb 12 05:05 System.map-2.6.18-6-powerpc-smp > -rw-r--r-- 1 root root 57120 Feb 11 11:14 config-2.6.18-6-powerpc-smp > lrwxrwxrwx 1 root root 31 Mar 2 17:48 initrd.img -> > initrd.img-2.6.18-6-powerpc-smp > -rw-r--r-- 1 root root 5384155 Mar 6 15:27 initrd.img-2.6.18-6-powerpc-smp > drwx-- 2 root root 12288 Mar 2 17:42 lost+found > lrwxrwxrwx 1 root root 28 Mar 2 17:48 vmlinux -> > vmlinux-2.6.18-6-powerpc-smp > -rw-r--r-- 1 root root 4551303 Feb 12 05:04 vmlinux-2.6.18-6-powerpc-smp > > Should the kernel not have a 64 somewhere in the name. Yes I think you have the wrong kernel installed. Try to install linux-image-2.6-powerpc64. Try "aptitude install linux-image-2.6-powerpc64" after booting into rescue mode and mounting /proc and /sys (see below). > > Steve Luther suggested looking at '/proc/cmdline' to see which console > the system has. I was using 'conlose=ttyS0'. In the rescue system the > whole /proc is empty. This seems very odd, am I doing something wrong > here? The proc filesystem is not mounted inside the rescue chroot. You can mount it with "mount -t proc none /proc". You probably also need to mount sysfs before installing the kernel (mount -t sysfs none /sys). Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#469030: debian ppc64 not booting after install
On Thursday 06 March 2008, Gaudenz Steinlin wrote: > > Should the kernel not have a 64 somewhere in the name. > > Yes I think you have the wrong kernel installed. Try to install > linux-image-2.6-powerpc64. Try "aptitude install > linux-image-2.6-powerpc64" after booting into rescue mode and mounting > /proc and /sys (see below). Could you please send us the syslog (gzipped!) for the installation so we can check what exactly happened during kernel selection? It should be in /var/log/installer/ on the installed system. TIA, FJP (Please keep both the bug report and the d-powerpc list in the address list) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#469650: console-setup: [INTL:eu] debconf templates Basque translation
Quoting Piarres Beobide ([EMAIL PROTECTED]): > Package: console-setup > Severity: wishlist > Tags: patch l10n d-i > > Hi > > Attached console-setup debconf templates basque translation, please commit it. You can:-) console-setup is maintained by the D-I team and lies in packages/console-setup in D-I SVN. Its PO file is currently not aggregated in the D-I master files because console-setup is not used in D-I, so translators have to work on it separatelybut still can commit updates themselves. PS: don't forget updating debian/changelog as well (including the needed "Closes" statement for this bug report) signature.asc Description: Digital signature
Re: [PATCH] support live image installing mode selection
Quoting Daniel Baumann ([EMAIL PROTECTED]): > _Description: Installation mode: > Please select the installation mode to be used. > . > By choosing 'normal', the installed system will installed as a regular > system while choosing 'live', the system will continue to act as a live > system with the only difference that it is directly launched from the > harddisk instead of an external/another/boot/$whatever medium. > > (the 'external/another/boot/$whatever' is not ment literally, don't know > which one is the best to choose). I'd say 'another'. Your proposal is fine by me. -- signature.asc Description: Digital signature
kernel version in boot files
Is there any good reason for this? [EMAIL PROTECTED]:~/ftp/dists/unstable/main/installer-mips/current/images>find |grep 2.6.22 ./sb1-bcm91250a/netboot/vmlinux-2.6.22-3-sb1-bcm91250a ./qemu/netboot/vmlinux-2.6.22-3-qemu ./sb1a-bcm91480b/netboot/vmlinux-2.6.22-3-sb1a-bcm91480b Needing to follow these versions is constantly breaking digress, and I imagine is also annoying if trying to maintain a netboot server. Other d-i images that include the kernel version number: ./installer-arm/20080227/images/iop32x/netboot/vmlinuz-2.6.22-3-iop32x ./installer-arm/20080227/images/ixp4xx/netboot/vmlinuz-2.6.22-3-ixp4xx ./installer-hppa/20080227/images/cdrom/2.6/vmlinux-2.6.22-3-parisc64 ./installer-hppa/20080227/images/cdrom/2.6/vmlinux-2.6.22-3-parisc ./installer-sparc/20080227/images/cdrom/vmlinuz-2.6.22-3-sparc64 -- see shy jo signature.asc Description: Digital signature
Re: cannot set a size to lvm partition (size 0 is invalid)
On Wed, Mar 5, 2008 at 11:21 PM, Frans Pop <[EMAIL PROTECTED]> wrote: > On Tuesday 04 March 2008, Lukasz Szybalski wrote: > > I set the raid 5 partition as a lvm group and not I am trying to > > create lvm partition for my home at 1450GB. I keep getting the error > > that partition size 0 cannot be created. > > Could you please file a bug report against partman-lvm for this issue? > > > > Here is a syslog. > > I don't know why but when I want to create lvm volume: > > 1497303MB is my initial setting. > > I can just hit enter to 1497303MB and it will take it. > > > > But if I pick 1457303MB I get an error. > > That's certainly strange. Could possibly have to do with rounding functions. > > > > What is going on with these numbers. syslog tells me that 1.36 TB is > > only available? Shouldn't that be 1.4xx TB? > > There is some confusion inside partman and between partman and other tools > about how disk sizes are presented. Disk capacity is usually given as a > power of 10, while other sizes are in multiples of bytes (power of 2). > So 40MB can be either 40.000.000 bytes or 41.943.040 (40*1024*1024). > You are correct on this one. Finally after 4h of reserach I realized that 500Gb drive is in reality 465GiB. So 1.3Tb 465*3 is about right. So there seem to be a miss match of what is displayed and what it is in reality. In real world the drive is 465Gib and that is what I should see. The partition screen shows the lvm group partition as 1.5TB, but when you go into add first partition it wants the actual GiB size (max 1.5Tb =max 1.3Tb). Not sure why it let me put into 1497303MB (all space) but not 1497000Mb etc. If you recalculate by hand how much space you have in GiB then its easy from there. Confusion introduced by 500Gb =465Gib has everybody confused I guess. It would be much easier if everything was in GiB So final setting was to make one partition 1.1Tb and rest with rest of space. So I guess the partition screen should either show you (1500GB / 1395 GiB ) or it should pick one(GiB preffered). My guess would to be make Gib a default since that is the size I will see when I do 'df -h' when its all said and done. I guess at Tera size the Gib vs GB measurement is huge! > > > Can somebody explain why I cannot create my 1.45 tb and rest as swap > > partitions? > > A solution could be to create the swap first at the required size. > > > > Also why sys log tells me I have 1.36 even do other > > screens tell me that my lvm group holds 1.5tb? > > See above. > > > > I tried both. installgui and install when setting these up. > > That should not make any difference. > > > Could you run a new installation and, before partman is started, add a > line 'set -x' near the top of /lib/partman/definitions.sh? > That will give a huge amount of debugging output in the syslog, but should > tell us exactly where the error comes from when you reproduce it. > > Please attach the syslog (gzipped) to your bug report. > I'm sorry I won't be able to provide any more logs. I have installed debian already and both raid 1 and raid 5 are setup. The computer will go into production soon. I will report the bug and provide logs I had. Lucas -- Vehicle Information Number. Check for Authentic VIN http://lucasmanual.com/vin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#468779: installation-reports: Install failed to recognize Intel Nineveh 82566DM adapter network on Econel 100 S2
Hi Today I followed the instructions given in my former mail. On a well configured machine it will take 20 minutes (all included) to make the new driver module. It worked for me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: r51742 - trunk/packages/partman/partman-partitioning/debian
Frans Pop wrote: > On Thursday 06 March 2008, Joey Hess wrote: > >* Add missing sourcing of debconf confmodule in init.d/unsupported. > > In my tests, this broke installation on mips in qemu when using a > > blank disk image. > > Sorry about that one. > I think this is one of the first real issues from the restructuring I did. > Still not bad :-P I've verified that partman-partitioning 57 fixes the problem, and I recommend including this in the beta. -- see shy jo signature.asc Description: Digital signature
Processing of libdebian-installer_0.56_i386.changes
libdebian-installer_0.56_i386.changes uploaded successfully to localhost along with the files: libdebian-installer_0.56.dsc libdebian-installer_0.56.tar.gz libdebian-installer4_0.56_i386.deb libdebian-installer4-dev_0.56_i386.deb libdebian-installer4-udeb_0.56_i386.udeb libdebian-installer-extra4_0.56_i386.deb libdebian-installer-extra4-udeb_0.56_i386.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
win32-loader 0.6.3 MIGRATED to testing
FYI: The status of the win32-loader source package in Debian's testing distribution has changed. Previous version: 0.6.0 Current version: 0.6.3 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libdebian-installer_0.56_i386.changes ACCEPTED
Accepted: libdebian-installer-extra4-udeb_0.56_i386.udeb to pool/main/libd/libdebian-installer/libdebian-installer-extra4-udeb_0.56_i386.udeb libdebian-installer-extra4_0.56_i386.deb to pool/main/libd/libdebian-installer/libdebian-installer-extra4_0.56_i386.deb libdebian-installer4-dev_0.56_i386.deb to pool/main/libd/libdebian-installer/libdebian-installer4-dev_0.56_i386.deb libdebian-installer4-udeb_0.56_i386.udeb to pool/main/libd/libdebian-installer/libdebian-installer4-udeb_0.56_i386.udeb libdebian-installer4_0.56_i386.deb to pool/main/libd/libdebian-installer/libdebian-installer4_0.56_i386.deb libdebian-installer_0.56.dsc to pool/main/libd/libdebian-installer/libdebian-installer_0.56.dsc libdebian-installer_0.56.tar.gz to pool/main/libd/libdebian-installer/libdebian-installer_0.56.tar.gz Override entries for your package: libdebian-installer-extra4-udeb_0.56_i386.udeb - optional debian-installer libdebian-installer-extra4_0.56_i386.deb - optional libs libdebian-installer4-dev_0.56_i386.deb - optional libdevel libdebian-installer4-udeb_0.56_i386.udeb - optional debian-installer libdebian-installer4_0.56_i386.deb - optional libs libdebian-installer_0.56.dsc - source libs Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[D-I Manual] Build log for en (06 Mar 2008)
A build of the Debian Installer Manual was triggered by an update to SVN.
There were no errors during the build process.
The new version of the manual has been uploaded successfully.
A log of the build is available at:
- http://d-i.alioth.debian.org/manual/logs/en.log
===
It is possible to use RSS to track changes to the manual.
For more information, see:
http://d-i.alioth.debian.org/manual/translators.html
===
Note: PDF output is not yet supported for some languages; help
with this would be appreciated.
===
If you have any questions about the build or this message, feel
free to contact me at .
===
Updated files ('svn up')
Uen/using-d-i/modules/apt-setup.xml
Uen/boot-installer/x86.xml
Updated to revision 51764.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Patch to tidy up wget use, and add return=4 when 404's are seen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frans Pop wrote: > Or maybe use a switch to toggle between "continuation" and "full" retries. > Continuation retries probably make sense for larger files (Packages comes > to mind) for which the integrity can be checked (md5sum). > Given the caveats in the wget manpage for -c, it may be safer to not do > continuation retries at all, but just do a full retry in other cases (like > fetching preseed files). OK, I've done -c as an option to fetch-url that adds a -c option to wget for the 3 retries that it tries if the initial wget fails. I've also made preseed_fetch accept options and pass them onto fetch-url, so you can use -c in preseed scripts (for downloading udebs or debs, say) Here's the patch, split in two as you suggested so that the first half is just the moving of fetch-url into di-utils: http://hands.com/~phil/d-i/fetch-url.diff and the second bit is the wget404 stuff: http://hands.com/~phil/d-i/wget404.diff Cheers, Phil. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH0LUGYgOKS92bmRARAut1AJ4ktLRzGfrD/tedw2WW/RxFUZcqawCgoos7 MzezfQDVP8qA0lUu8/sivCQ= =9/yT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
testing: issue with mips images
The mips netboot images fail to boot in qemu as follows: VFS: Mounted root (cramfs filesystem) readonly. Freeing unused kernel memory: 136k freed cramfs: bad compressed blocksize 29091 cramfs: bad compressed blocksize 12209 request_module: runaway loop modprobe binfmt- request_module: runaway loop modprobe binfmt- request_module: runaway loop modprobe binfmt- request_module: runaway loop modprobe binfmt- request_module: runaway loop modprobe binfmt- Looks like a somehow corrupt cramfs image. The mipsel images do not have this problem. I see tbm reported a similar problem on debian-mips[1], and it seems to affect real hardware. -- see shy jo [1] http://lists.debian.org/debian-mips/2008/02/msg00056.html signature.asc Description: Digital signature
Re: testing: issue with mips images
* Joey Hess <[EMAIL PROTECTED]> [2008-03-07 00:32]: > Looks like a somehow corrupt cramfs image. > > The mipsel images do not have this problem. I see tbm reported a > similar problem on debian-mips[1], and it seems to affect real hardware. Looks like the same issue indeed. It's good to know that this also happens in qemu since I wasn't sure whether it was specific to SGI. Anyway, I mostly care about mipsel these days (which works), so maybe someone else can take a look. And someone should put in the errata that mips d-i beta1 is broken. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
