Re: wpasupplicant udeb

[Jérémy Bobbio]

On Fri, May 23, 2008 at 04:09:48PM +0800, Glenn wrote:
> It will still build the deb and clients at the moment, which as stated
> earlier, some sort of seperate config needs to be made for the udeb.

If you can provide a patch doing so for review, it would be great.

You might want to have a look at busybox which also use a "config" file
for its build system and have several different configuration for its
binary packages.

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Re: question about d-i preseed

[Jérémy Bobbio]

On Fri, May 23, 2008 at 12:29:28PM +0200, Anthony wrote:
> i would like to know if it is possible to configure a package after 
> installation with pressed file.

Look at the appendix B of the installation manual [1], and specifically
the section about running custom commands [2] by preseeding
"preseed/early_command" and "preseed/late_command".

The later will allow you to run custom shell scripts that should fit the
example you described.

[1] http://www.debian.org/releases/stable/i386/apb.html.en
[2] http://www.debian.org/releases/stable/i386/apbs05.html.en#preseed-hooks
  
Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Re: wpasupplicant udeb

[Glenn]

Jérémy Bobbio wrote:
> On Fri, May 23, 2008 at 04:09:48PM +0800, Glenn wrote:
>   
>> It will still build the deb and clients at the moment, which as stated
>> earlier, some sort of seperate config needs to be made for the udeb.
>> 
>
> If you can provide a patch doing so for review, it would be great.
>
> You might want to have a look at busybox which also use a "config" file
> for its build system and have several different configuration for its
> binary packages.
>
> Cheers,
>   
I'll fire off an email to the wpasupplicant list before I start doing
patches for the package. This patch was meant just for testing purposes,
which is what I thought Frans wanted. I'll get back with any questions
or concerns that may arise from this.

Cheers

Glenn


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#482675: Kernel oops on amd64 quad core 9850

[Marcus Carlson]

Package: installation-reports

Boot method: netboot
Image version: 
http://people.debian.org/~aba/d-i/images/daily/netboot/netboot.tar.gz
Date: 2008-05-24

Machine: Homemade monster
Processor: AMD Quad Core 9850
Memory: 8 GB
Partitions: 50 GB / ext3, 8 GB swap, 500 GB /home ext3

Output of lspci -nn and lspci -vnn:
see attached files.

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:  [E]
Install base system:[E]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:
This is a brand new machine, also the harddrive is a new 1 TB sata (tried the 
same on an old 200 GB sata, but same problem).
Everyting goes well until its formatting the second partition to ext3. It will 
hang in installation and the console gives me an oops.

Unable to handle kernel paging request at 
Process seems to be sh

Also tried not formatting the second partition and then installation begins but hangs at installing python, same oops message. 
Process: update-alternative 


I've done memtests with no errors.

Ubuntu live CD works fine, but installation dies at the same place when 
formatting partition. (Could not see the oops)

Also tried ubuntu netboot and hang at installing of kernel package. 


Attached lspci output and dmesg output.

I've also run memtests but no errors.

TIA,
Marcus

00:00.0 Host bridge [0600]: ATI Technologies Inc RD790 Northbridge only dual 
slot PCI-e_GFX and HT3 K8 part [1002:5956]
00:02.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge 
(external gfx0 port A) [1002:5978]
00:06.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
express gpp port C) [1002:597c]
00:07.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
express gpp port D) [1002:597d]
00:09.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
express gpp port E) [1002:597e]
00:0a.0 PCI bridge [0604]: ATI Technologies Inc RD790 PCI to PCI bridge (PCI 
express gpp port F) [1002:597f]
00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA 
[1002:4380]
00:13.0 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI0) 
[1002:4387]
00:13.1 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI1) 
[1002:4388]
00:13.2 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI2) 
[1002:4389]
00:13.3 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI3) 
[1002:438a]
00:13.4 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI4) 
[1002:438b]
00:13.5 USB Controller [0c03]: ATI Technologies Inc SB600 USB Controller (EHCI) 
[1002:4386]
00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] 
(rev 14)
00:14.1 IDE interface [0101]: ATI Technologies Inc SB600 IDE [1002:438c]
00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia [1002:4383]
00:14.3 ISA bridge [0601]: ATI Technologies Inc SB600 PCI to LPC Bridge 
[1002:438d]
00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge 
[1002:4384]
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] HyperTransport Configuration [1022:1200]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] Address Map [1022:1201]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] DRAM Controller [1022:1202]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] Miscellaneous Control [1022:1203]
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h [Opteron, 
Athlon64, Sempron] Link Control [1022:1204]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3870 
[1002:9501]
01:00.1 Audio device [0403]: ATI Technologies Inc Radeon HD 3870 Audio device 
[1002:aa18]
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
04:00.0 SATA controller [0106]: JMicron Technologies, Inc. JMicron 20360/20363 
AHCI Controller [197b:2363] (rev 02)
04:00.1 IDE interface [0101]: JMicron Technologies, Inc. JMicron 20360/20363 
AHCI Controller [197b:2363] (rev 02)
05:00.0 SATA controller [0106]: JMicron Technologies, Inc. JMicron 20360/20363 
AHCI Controller [197b:2363] (rev 02)
05:00.1 IDE interface [0101]: JMicron Technologies, Inc. JMicron 20360/20363 
AHCI Controller [197b:2363] (rev 02)
06:0e.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB23 
IEEE-1394a-2000 Controller (PHY/Link) [104c:8

Re: [PATCH] Enable partman-crypto to work with keys on removable devices

[Max Vozeler]

Hi David,

On Tue, May 13, 2008 at 08:02:28PM +0200, David Härdeman wrote:
> In the "setup encrypted volumes" stage of partman, the user will be 
> given a list of partitions known to partman and after selecting one, a 
> path must be entered. If that file already exists on the device, it will 
> be used as the keyfile, otherwise a new keyfile will be created.

Nice work. This will allow us to close #381894.

> I've done a test install using qemu (with a secondary qemu harddisk as 
> the removable device) and a SVN version of cryptsetup (which has the 
> necessary "mountdev" keyscript). Also, due to a bug in klibc, only ext3 
> is supported for now (bug reported, will be fixed before the next upload 
> of cryptsetup which will allow any common fs to be used).

Sounds like we should hold off until cryptsetup is ready.

> My d-i knowledge is rusty so a review of the patch would be much 
> appreciated. (I've also been out of the loop wrt. d-i development, 
> deadlines for the next release, etc...so I have no idea how suitable 
> this patch is right now in the bigger picture)

Otavio, could you advise? Is it okay to commit such new
features to trunk soon and then upload after beta2?

> I'm also planning to use some of the infrastructure of the patch to add 
> support for two-factor keys (ask a passphrase, hash it, get a keyfile 
> from usb stick, xor the two together, use that as the key) and 
> smartcards (I've already ordered the hardware, dunno when I'll get it).

Great. Looking forward to it :-)

> +Template: partman-crypto/removable-source-path
> +Template: partman-crypto/removable-source-partition
> +Template: partman-crypto/removable-confirm-create
> +Template: partman-crypto/removable-bad-keyfile

The names of those *removable* templates confused me a bit 
when I was reading the code. Perhaps we could find more
specific and self-descriptive names?

Hm. This is what I came up with. Not sure I acutally like
them better, but they are more specific:

   removabledev-partition
   removabledev-key-path
   removabledev-key-confirm-create
   removabledev-key-badformat

> +Template: partman-crypto/removable-confirm-create
> +Type: boolean
> +Default: false
> +# :sl3:
> +_Description: Create new key?
> + No key was found on ${DEVICE} at path ${PATH}, do you wish to create
> + a new key?

s/at path/in path/ ?

> +Template: partman-crypto/removable-bad-keyfile
> +Type: error
> +# :sl3:
> +_Description: Invalid encryption key
> + You have selected a pre-existing key file which is not suitable as a
> + crypto key as it is not large enough. Please try using a different
> + key file.

Terminology - "key" vs. "crypto key" vs "encryption key". 

We should use one term consistently. Personally, I think 
I'd go for "encryption key".

> Index: finish.d/crypto_config
> ===
> --- finish.d/crypto_config(revision 53290) > +++ finish.d/crypto_config   
> (working copy)
> @@ -96,6 +96,27 @@
>   keyfile="/dev/urandom"
>   elif [ $keytype = passphrase ]; then
>   keyfile="none"
> + elif [ $keytype = removabledev ]; then
> + local keydev keypath udevlinks tmp
> + keypath=$(cat $realdevdir/keypath)
> + keydev=$(cat $realdevdir/keydev)
> +
> + # We need to use stable device names as using e.g. /dev/hda2
> + # will break the boot if a second USB key is present.
> + udevlinks=""
> + for tmp in by-id by-uuid by-label by-path; do
> + if [ -d "/dev/disk/$tmp" ]; then
> + udevlinks="$udevlinks /dev/disk/$tmp/*"
> + fi
> + done
> + for tmp in $udevlinks; do
> + if [ "$(readlink -f "$tmp")" = "$keydev" ]; then
> + keydev="$tmp"
> + break;
> + fi
> + done

I think this should be broken out into a generic 
persistent_device_name() in partman-base.

Such a function for mapping devices to persistent names 
will be useful when we start using persistent device
names in other parts of partman.

Once that happens, we might also want to make all the 
persistent device names use the same mechanism (e.g. by-id).
Last I remember the discussion was still undecided about
which mechanism was most suitable.

> Index: blockdev-keygen
> ===
> --- blockdev-keygen   (revision 53290)
> +++ blockdev-keygen   (working copy)
> @@ -192,6 +192,110 @@
>   return 0
>  }

The below would rather fit into crypto-base.sh than
blockdev-keygen IMO. 

 - It creates files in the device directory.

 - The debconf interaction is about getting the right
   removable device and the final path to store the key.
   No reason blockdev-keygen should care about those.

> +# Create or load an already created keyfile on a user-specified device

Processed: Re: Bug#482675: Kernel oops on amd64 quad core 9850

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 482675 linux-2.6 2.6.24-6
Bug#482675: Kernel oops on amd64 quad core 9850
Bug reassigned from package `installation-reports' to `linux-2.6'.

> 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#482675: Kernel oops on amd64 quad core 9850

[Frans Pop]

reassign 482675 linux-2.6 2.6.24-6
thanks

On Saturday 24 May 2008, Marcus Carlson wrote:
> Comments/Problems:
> This is a brand new machine, also the harddrive is a new 1 TB sata (tried
> the same on an old 200 GB sata, but same problem). Everyting goes well
> until its formatting the second partition to ext3. It will hang in
> installation and the console gives me an oops.

The oops is an indication of a kernel problem. Therefore reassigning to the 
kernel team.

Cheers,
FJP



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Debian Installer Lenny Beta3 plans [was Re: [PATCH] Enable partman-crypto to work with keys on removable devices

[Otavio Salvador]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Max Vozeler <[EMAIL PROTECTED]> writes:

>> My d-i knowledge is rusty so a review of the patch would be much 
>> appreciated. (I've also been out of the loop wrt. d-i development, 
>> deadlines for the next release, etc...so I have no idea how suitable 
>> this patch is right now in the bigger picture)
>
> Otavio, could you advise? Is it okay to commit such new
> features to trunk soon and then upload after beta2?

Sure.

Well basically beta2 is "almost there" and I think we could start to
work in beta3 features/fixes. However I think beta3 needs to be faster
then beta2 was.

The current list of things that should happen on Beta3 is:

 - kernel update to 2.6.25
 - parted update to 1.8
 - fixes

All new features now need to be careful check before commiting. Mostly
because we need to be ready to release at any time. So all features
need to offer testing images for review and we'd decide case by case
depending on how deeply are the changes if it'll be accepted or not.

About this patch specifically, it doesn't look too risky and I think
we could try to make it happen in time for Beta3. Let's do our best to
properly test it.

Cheers,

- -- 
O T A V I OS A L V A D O R
- -
 E-mail: [EMAIL PROTECTED]  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."
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ 

iD8DBQFIOCjHLqiZQEml+FURAlY2AJ9u/sPMHKA62vrJWUPHV/RNAfJLjQCeN6uu
RBnhqv6in09UWJYNPh3aUPk=
=oKIP
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian Installer Lenny Beta3 plans

[Jérémy Bobbio]

On Sat, May 24, 2008 at 11:40:08AM -0300, Otavio Salvador wrote:
> The current list of things that should happen on Beta3 is:
> 
>  - kernel update to 2.6.25
>  - parted update to 1.8
>  - fixes
> 
> All new features now need to be careful check before commiting. Mostly
> because we need to be ready to release at any time. So all features
> need to offer testing images for review and we'd decide case by case
> depending on how deeply are the changes if it'll be accepted or not.

I would like to work on two things for beta3 though:
 - use of aligned columns in partman,
 - integration of a terminal in the graphical installer through VTE.

I have started to work on both a while ago.  The first would be, IMHO, a
great improvement to the graphical installer usuability and I'd like to
focus on this in the following weeks.

The changes required are touching essential parts of partman [1] and
will require testing though.

[1] http://lists.debian.org/debian-boot/2008/03/msg01250.html

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Processed: tagging 481169

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.10.20~bpo40+1
> tags 481169 moreinfo
Bug#481169: installation-reports
There were no tags set.
Tags added: moreinfo

>
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]

Bug#481169: installation-reports

[Jérémy Bobbio]

On Wed, May 14, 2008 at 11:31:15AM +0200, michel levy wrote:
> Machine : toshiba 310CDT
> Processor : Pentium 200Mhz with MMX support
> Memory : 94MB
> […]
> Initial boot:   [E]
> The machine stops with
> code : bad EIP value
> debian kernel panic not syncing  : attempt to kill init

It looks like an hardware problem.  It might be triggered only with the
newer version of the kernel though.

Could you please ensure that your memory is fine (memtest86 should help)
and look for a possible BIOS upgrade?

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Re: Memtest

[Jérémy Bobbio]

On Sat, May 17, 2008 at 12:11:23PM +0430, Armin ranjbar wrote:
> Does DI support memtest? is there any plan to support this in future?

Could you describe exactly the kind of memtest "support" you are
thinking about?

Debian already has a "memtest86+" package [1] that can easily create
floppies that will boot memtest86+.

[1] http://packages.debian.org/memtest86%2b

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Processed: Re: Bug#481687: Install report

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 481687 + moreinfo
Bug#481687: Install report
There were no tags set.
Tags added: moreinfo

> 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#481687: Install report

[Jérémy Bobbio]

tag 481687 + moreinfo
thanks

On Sat, May 17, 2008 at 03:07:08PM -0700, Avery Fay wrote:
> 1.) The installer repeatedly asks me if I want to start pccard
> services. I realize I'm doing an expert install, but I can't see a
> situation where I would change my mind and therefore would want to be
> asked again.

Imagine that you have a PC Card NIC. The drivers for the PC Card
controller are in a udeb on an IDE CD-ROM drive.  You would not enable
the PC Card service during the first question, but you would the second
time.

> 2.) Guided partitioning does not ask at all about swap. It gave me a
> 10 or 12 GB swap partition which is pretty ridiculous for my needs. A
> simple question like "How large do you want your swap partition to be
> (in multiples of main memory)?" would be fine. Again, this is an
> expert install. I'd like to be asked about this stuff.

Already known issue. See #346589.

> 3.) GB != GB in manual LVM setup. Space available on a volume group is
> reported as 299GB and yet making a logical volume of 295GB fails
> because there isn't enough space. I don't really care whether the
> installer uses traditional mega-, giga- or "hard drive manufacturer"
> mega-, giga-, BUT it should be consistent. As it is, manual
> partitioning is guess and check.

Already known issue. See #411943.

> 4.) The gui installer crashed when I tried to manually partition.
> Given some of the recent reports on debian-boot, I decided not to
> investigate this further, but if there are no known crashes (was
> gdk-something) I can try to get it to happen again.

I had no report of such issue.  You would be welcome if you could
provide us a procedure on how to reproduce the crashes you have
experienced.

> 5.) Having a gui is a great way to make partitioning easier.
> Unfortunately, the current gui is an exact clone of the text
> interface. This does not translate well at all. I'd like to see visual
> representation of the layout as well as buttons for add/delete/modify
> next to partitions. Also, there's no need to go to a separate page
> when modifying a partition... just bring up a modal dialogue.

A specific partitioning interface for the graphical installer is in
everyone's mind for a while now.  The first step was to work on the GTK+
frontend for cdebconf to make the creation of plugins easier and this is
mostly done now.

Given the short time before the release of Lenny, we have decided to
improve the current interface (by providing properly aligned columns
instead of misrendered whitespaces) instead of working on a specific
partitioner interface.

The main issue is lack of time and interested contributors though.

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Re: DI to detect HIGHMEM

[Jérémy Bobbio]

On Wed, May 21, 2008 at 04:48:25PM +0430, Armin ranjbar wrote:
> as you know , when there is need for BIGMEM kernels , kernel prints
> warning in dmesg log :
> 
> Warning only 4GB will be used.
> Use a HIGHMEM64G enabled kernel.
> 
> as for net install , this error is not presented (while it is shown
> in installed system) , 'quite' boot options is removed but still , dmesg
> and syslog log seems incomplete , can you please assist me on this ?

The debian-installer kernel uses the -486 kernel flavour for the i386
architecture.  During the installation process, the installer detects
that the system you are installing is able to support the -686 flavour
and install a -686 kernel.

Both flavour have different built time options[1].  -484 has
CONFIG_NOHIGHMEM set, where -686 has CONFIG_HIGHMEM4G.  The kernel does
not output anything when CONFIG_NOHIGHMEM is set, which is why you don't
get any message when starting up the installer.

So, from what I can think of, you can either need to find a more
reliable way to detect the full amount of memory in the system, or build
a custom debian-installer using a -686 flavour…

Or use the amd64 architecture. :)

[1] http://merkel.debian.org/~jurij/2.6.24-5/i386/

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Bug#480937: Etch Install

[Jérémy Bobbio]

tag 480937 + moreinfo
thanks

On Mon, May 12, 2008 at 03:23:17PM -0400, Dan Collier wrote:
> Comments/Problems: It seemed to install OK & install the boot loader
> OK, but it will not boot either the Debian drive or the Windows drive.
> I don't know Linux, so I don't know what to do to fix the boot loader.
> I would appreciate any help you can offer.

As far as I understand your issue, it might be related to your BIOS
settings.

In any case, the installation CD provides a rescue mode which you can
start be typing "rescue" at the initial installation boot prompt (the
one with the Debian logo).  The rescue mode provide an option to
reinstall the boot loader.  See:
  http://www.debian.org/releases/stable/i386/ch08s07.html.en

Hope that helps,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Processed: Re: Bug#480937: Etch Install

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tag 480937 + moreinfo
Bug#480937: Etch Install
There were no tags set.
Tags added: moreinfo

> 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#481514: marked as done (Poor mouse configuration with debian-installer)

[Debian Bug Tracking System]

Your message dated Sat, 24 May 2008 23:53:26 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#481514: Poor mouse configuration with debian-installer
has caused the Debian Bug report #481514,
regarding Poor mouse configuration with debian-installer
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 [EMAIL PROTECTED]
immediately.)


-- 
481514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481514
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: installation-reports

Boot method: CD-ROM
Image version: etch 4.0r1
Date: May 3, 2008

Machine: Dell Inspiron 4400
Processor: Intel Pentium 4
Memory: 512M
Partitions: 4 (1 Windows NTFS, 1 Linux swap, 1 root
(/), 1 home (/home))

Output of lspci -nn and lspci -vnn: N/A

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] =
didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [ ]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Clock/timezone setup:   [O]
User/password setup:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

I took the default for priority (i.e. no boot
parameters) and in tasksel I selected only "standard
system" and "desktop environment".  The mouse was a
PS/2-style mouse, was detected, and was installed for
use in the X Window System.  But the X server was
configured to drive the mouse directly rather than
through the gpm daemon.  In my opinion, gpm should
have been installed automatically and the X server
should have been configured to use /dev/gpmdata as the
mouse device.  This would allow the mouse to be used
both in X and in regular virtual consoles.  This
provides maximum flexibility.

In my opinion, the user has everything to gain and
nothing to lose by using gpm instead of direct control
of the mouse by the X server.  Even if the user does
not ever use the mouse in a virtual console, using gpm
provides more flexibility in the X server.  For
example, when using gpm, one can unplug the mouse and
plug in a different one without restarting the X
server.  Simply restart the gpm daemon.  All the X
aplications keep running without missing a beat.

gpm should be installed by default when the user
requests a desktop environment, and the X server
should be configured to use gpm.  Indeed, one could
even make a case that gpm should be installed by
default even when the user requests only a "standard
system", if a mouse is detected.

gpm should also be on CD number 1, particularly if it
is going to be installed by default.



  


--- End Message ---
--- Begin Message ---
On Fri, May 16, 2008 at 09:07:18AM -0700, Stephen Powell wrote:
> Overall install:[O]

As the installation procedure went fine, I am closing this bug report
(no bugs). :)

> Comments/Problems:
> 
> I took the default for priority (i.e. no boot
> parameters) and in tasksel I selected only "standard
> system" and "desktop environment".  The mouse was a
> PS/2-style mouse, was detected, and was installed for
> use in the X Window System.  But the X server was
> configured to drive the mouse directly rather than
> through the gpm daemon.  In my opinion, gpm should
> have been installed automatically and the X server
> should have been configured to use /dev/gpmdata as the
> mouse device.  This would allow the mouse to be used
> both in X and in regular virtual consoles.  This
> provides maximum flexibility.

As this would require changes in various packages and requires proper
acknowledgement by the different maintainers involved, I suggest that
you raise your suggestion on the debian-devel mailling-list.
(The installer itself only installs these packages and is not directly
affected here.)

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature
--- End Message ---

Bug#481433: Installation report: minor partitioning display bug, otherwise fine (Daily i386 netboot build, 13-May-2008)

[Jérémy Bobbio]

reassign 481433 partman-base 117
retitle 481433 wrong partition numbering when confirming changes
severity 481433 minor
tag 481433 patch
thanks

On Thu, May 15, 2008 at 08:05:16PM -0400, Johnathan Mayo wrote:
> However, when I continued on and the screen came up afterwards to
> confirm it looked like the following:
> The partition tables of the following devices are changed:
> IDE1 master (hda)
> 
> The following partitions are going to be formatted:
> partition #1 of IDE1 master (hda) as ext3
> partition #1 of IDE1 master (hda) as swap

Well spotted! :)

The bug has been introduced while adding support for multipath devices.
I have just commited a fix for this issue.

Cheers,
-- 
Jérémy Bobbio.''`. 
[EMAIL PROTECTED]: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Processed: Re: Bug#481433: Installation report: minor partitioning display bug, otherwise fine (Daily i386 netboot build, 13-May-2008)

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 481433 partman-base 117
Bug#481433: Installation report: minor partitioning display bug, otherwise fine 
(Daily i386 netboot build, 13-May-2008)
Bug reassigned from package `installation-reports' to `partman-base'.

> retitle 481433 wrong partition numbering when confirming changes
Bug#481433: Installation report: minor partitioning display bug, otherwise fine 
(Daily i386 netboot build, 13-May-2008)
Changed Bug title to `wrong partition numbering when confirming changes' from 
`Installation report: minor partitioning display bug, otherwise fine (Daily 
i386 netboot build, 13-May-2008)'.

> severity 481433 minor
Bug#481433: wrong partition numbering when confirming changes
Severity set to `minor' from `normal'

> tag 481433 patch
Bug#481433: wrong partition numbering when confirming changes
There were no tags set.
Tags added: patch

> 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]

Re: Memtest

[Holger Wansing]

Hi,

On Sat, 24 May 2008 18:57:53 +0200 Jérémy Bobbio wrote:
> On Sat, May 17, 2008 at 12:11:23PM +0430, Armin ranjbar wrote:
> > Does DI support memtest? is there any plan to support this in future?
> 
> Could you describe exactly the kind of memtest "support" you are
> thinking about?

To have an option "memtest" in the installer main menu?
Several other distributions have this since a long time ...


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 [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]