Re: Installer components are in freeze

[Christian Perrier]

Quoting Otavio Salvador (ota...@ossystems.com.br):
> Hello,
> 
> On Fri, Aug 14, 2009 at 5:51 AM, Bernhard wrote:
> > only a question:
> > Some installer components are in freeze.
> > Example: user-setup-udeb or netcfg.
> >
> > Is this OK?
> 
> Yes, it is.
> 
> > If yes, why?
> 
> Currently the scripts responsable for the packages migration are not
> yet ready to handle udebs automatically. The udeb packages differs
> from regular packages and cannot be handled in same way.


Please also note that components such as user-setup-udeb, which are
generated from source packages that only have udebs (in short "core"
D-I packages), contrary to udeb provided by "regular" packagesneed
to be manually approved by the D-I release manager in order to avoid
breaking D-I too much, particularly when at least one version of D-I
has been released in a given release cycle (which is still not the
case for squeeze as of now).

Automated migration to testing for udeb-only packages could be OK only
when there is no released D-I yet.




signature.asc
Description: Digital signature

Re: d-i plans for the squeeze cycle

[Christian Perrier]

Quoting Marc Brockschmidt (m...@marcbrockschmidt.de):
> Heya,
> 
> As announced on dda [RT1], we want to get an impression when releasing
> Squeeze is feasible. We have proposed a (quite ambitious) freeze in December
> 2009, and some developers have noted that their planned changes wouldn't be
> possible in this time frame. So, to find out when releasing would work for
> most people, it would be great if you could answer the following questions:
> 
> Do you have any big changes planned? How much time would they take, and
> what consequences are there for the rest of the project?
> 
> How many "big" transitions will the upcoming changes cause? When should those
> happen? Can we do something to make them easier?


I think that the current answer we can give as of now is "we don't
even have released an alpha versionand we probablu can't expect
any before September (I'd say "end September").

As already said, I won't be available for a team meeting today (which
should have been the meeting day according to our schedule). Should we
plan a specific "alpha release" meeting in an attempt to hurry up a
release?





signature.asc
Description: Digital signature

Bug#541823: installation-reports: Acer Aspire 3690

[Christian Perrier]

clone 541823 -1 -2
reassign -1 installation-report
reassign -2 console-setup
reassign -3 iso-scan
retitle -1 README.Debian wrongly suggests reporting bugs to installation-report
retitle -2 settings chosen from console-setup-udeb not preserved on installed 
system
retitle -3 Consistently fails to find ISO image on first try
thanks

Quoting Celejar (cele...@gmail.com):

Thanks for your very detailed installation report. It contains much
valuable information and I'll try a first attempt to use at least part
of it


> Initial boot:   [O ]
> Detect network card:[E ]
> Configure network:  [ ]
> Detect CD:  [E ]
> Load installer modules: [E ]
> Detect hard drives: [O ]
> Partition hard drives:  [E ]
> Install base system:[O ]
> Clock/timezone setup:   [O ]
> User/password setup:[O ]
> Install tasks:  [ ]
> Install boot loader:[O ]
> Overall install:[E ]
> 
> Comments/Problems:
> 
> 1)  The installer allowed me to set a keymap and layout (us / dvorak), but 
> this
> was not preserved in the actual install, which reverted to standard us.


That's the secodn time we get such report. I'm definitely not in
position to test this, but there's something broken somewhere in console-setup

> 
> 2)  The installer consistently failed to find the installer ISO on the first
> try (I wound up running it quite a few times, due to various problems),
> although it always found it on the second.

Assigned to iso-scan. It would be very interesting if you could try
reproducing this and check what's displayed on 4th console after the
first failure.

> 
> 3)  AFAICT, the installer kernel doesn't include b43.  Why?  I understand that
> we can't ship non-free firmware, but why not include the driver for those of 
> us
> who are able and willing to provide  firmware?

This one I leave to other maintainers

> 
> 4)  I was unable to delete a LUKS encrypted disk that I had created on a
> partition.  The installer refused to delete the partition since it was used by
> the encrypted disk, but it also apparently offered no way to delete the
> encrypted disk.

That one also. Hopefully Max will look at it in details.

> 
> 5)  The showstopper:  I installed the entire system (except for /boot) onto 
> LVM
> volumes in a vg on top of a LUKS volume created out of a primary partition.
> When I rebooted, the system wouldn't bring up the LUKS volume.  The eventual
> fix that worked is to add this line to /boot/grub/menu.lst:
> 
> # kopt=cryptopts=target=hda4_crypt,source=/dev/hda4,lvm=lizzie-root 
> root=/dev/mapper/lizzie-root ro
> 
> This is:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492790
> 
> and
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522041
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507721
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503062
> 
> 6)  Should installation reports be filed against 'installation-report' or
> 'installation-reports'?  The README from the installation-report package says
> 'report', but most reports seem to be filed against 'reports'.


Apparently this error is there for ages..:-). Reported against i-r



signature.asc
Description: Digital signature

Processed (with 2 errors): Re: Bug#541823: installation-reports: Acer Aspire 3690

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 541823 -1 -2
Bug#541823: installation-reports: Acer Aspire 3690
Bug 541823 cloned as bugs 542002-542003.

> reassign -1 installation-report
Bug #542002 [installation-reports] installation-reports: Acer Aspire 3690
Bug reassigned from package 'installation-reports' to 'installation-report'.
> reassign -2 console-setup
Bug #542003 [installation-reports] installation-reports: Acer Aspire 3690
Bug reassigned from package 'installation-reports' to 'console-setup'.
> reassign -3 iso-scan
Failed to clear fixed versions and reopen on -3: The 'bug' parameter ("-3") to 
Debbugs::Control::set_package did not pass regex check


> retitle -1 README.Debian wrongly suggests reporting bugs to 
> installation-report
Bug #542002 [installation-report] installation-reports: Acer Aspire 3690
Changed Bug title to 'README.Debian wrongly suggests reporting bugs to 
installation-report' from 'installation-reports: Acer Aspire 3690'
> retitle -2 settings chosen from console-setup-udeb not preserved on installed 
> system
Bug #542003 [console-setup] installation-reports: Acer Aspire 3690
Changed Bug title to 'settings chosen from console-setup-udeb not preserved on 
installed system' from 'installation-reports: Acer Aspire 3690'
> retitle -3 Consistently fails to find ISO image on first try
Failed to set the title of -3: The 'bug' parameter ("-3") to 
Debbugs::Control::set_title did not pass regex check


> 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

[REMINDER] Installer Team meeting today 20:00 UTC

[Max Vozeler]

Hello everyone,

On Mon, Aug 10, 2009 at 09:23:54AM +0200, Christian Perrier wrote:
> Given our current schedule, a team meetign hould happen on August 17th.
[...]
> If there are enough people around, it would be good to have a meeting,
> still, as many things happened since the last one (live at Debconf).

Indeed, lots of stuff happened!

Five people have indicated that they would be around. I think 
thats fine for (at least a short) meeting.

Time/place, just as reminder:

  ***Today***, August 17th, 20:00 UTC 
  #debian-boot (irc.debian.org (oftc))

@Otavio: Couldnt find you on IRC. Time OK for you?

See you tonight,

Max


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

bugs with business-card

[Joseph Vidal-Rosset]

Hello,

I've tried several times to install a Debian testing on my new Dell PC with
a business card. Each time it did not work. I am unable to send an
installation report, but here are the bugs I met:

-at the end of the installation, the X work, but the file xorg.conf does not
exist and the azerty configuration of the keyboard is not effective. Result:
impossible for me to get in my Desktop.
- using the rescue mode, the command dpkg-reconfigure xserver-xorg does not
work.

A

Bug#542025: installer hangs

[António dos Anjos]

Package: installation-reports

Boot method: 
Image version: 
Date: 

Machine: Dell D630
Processor: T7300
Memory: 4GB
Partitions: N/A

Not installable!


Comments/Problems:
During boot of the installer, it hangs  when showing:
usb 7-1.2: O2Micro CCID SC Reader
usb 7-1.2: Manufacturer: O2
usb 7-1.2: configuration #1 chosen from 1 choice

I am using the netinstall amd64. I tried the 2009/08/16 and 2009/08/17
installers. They both hand there.

Bug#542030: installation-reports: Forgets keyboard layout in X11

[Sam Morris]

Package: installation-reports
Severity: important

Chose United Keyboard layout in the installer. This choice remains in effect
during the installation and on the console after installation, but when I
log into X11 I am stuck with a US keyboard layout.

This would make it rather difficult for someone with unusual characters
in their password (such as £ or á) from logging in.

I think this happens because the xorg.conf that is created by the installer
is empty.

This is a regression from previous releases, which put the keyboard
layout chosen by the installer in xorg.conf.

-- Package-specific info:

Boot method: network
Image version: lenny i386 netboot
Date: 2009-08-14

Machine: ASUS Eee PC 904HD


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

-- 

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 20090123lenny3"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
umame -a: Linux utgard 2.6.26-2-486 #1 Sun Jun 21 04:15:19 UTC 2009 i686 unknown
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 
915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 04)
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04)
lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 04)
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller 
[8086:2668] (rev 04)
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW 
(ICH6 Family) PCI Express Port 1 [8086:2660] (rev 04)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW 
(ICH6 Family) PCI Express Port 2 [8086:2662] (rev 04)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW 
(ICH6 Family) PCI Express Port 4 [8086:2666] (rev 04)
lspci -knn: Kernel driver in use: pcieport-driver
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 04)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 04)
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: Kernel modules: uhci-hcd
lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 
82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 04)
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: Kernel modules: ehci-hcd
lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI 
Bridge [8086:2448] (rev d4)
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC 
Interface Bridge [8086:2641] (rev 04)
lspci -knn: 00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) 
SATA Controller [8086:2653] (rev 04)
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: Kernel modules: ata_piix, ahci
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 
Family) SMBus Controller [8086:266a] (rev 04)
lspci -knn: 01:00.0 Ethernet controller [0200]: Atheros Communications Inc. 
AR242x 802.11abg Wireless PCI Express Adapter [168c:001c] (rev 01)
lspci -knn: Kernel driver in use: ath5k_pci
lspci -knn: Kernel modules: ath5k
lspci -knn: 03:00.0 Ethernet controller 

Re: Success report: GRUB2, LVM, GPT, AMD64, Debian Installer

[Robert Millan]

On Fri, Aug 14, 2009 at 09:43:34AM +0200, Thomas Schwinge wrote:
> Hello!
> 
> A short success report about using GRUB2 on a LVM-only system, with GPT
> instead of the usual MBR booting, on a AMD64 system, installed with the
> 20090531-7 Debian Installer.
> 
> I had the DI create a GPT partition table, partitioned that into a small
> (1 MiB) GRUB booting partition (as suggested on
> , which I had found by pure
> chance),

Hi Thomas,

Glad everything's working fine for you.

We try our best to explain why blocklists are problematic, why embedding is
the preferred setup, and why embedding on GPT is not possible without the
BBP as a dedicated partition.

If you think this could be better explained, suggestions are welcome.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

[RFC] Bugs#503292: linux-latest-2.6: new dummy images for Samsung s3c24xx devices

[Luca Capello]

Hi there!

Starting from 2.6.31, the upstream Linux kernel contains basic Openmoko
GTA02 Neo FreeRunner support.  Unfortunately, there is still need for an
external patch which I hope will be included in the final 2.6.31:

  http://thread.gmane.org/gmane.comp.handhelds.openmoko.kernel/10089/focus=10112
  http://marc.info/?l=linux-arm-kernel&m=125020931711953&w=2

During DebConf9, there were various discussions about the kernel name
for the Samsung S3C devices, together with Gaudenz Steinlin, Riku
Voipio, Martin Michlmayr and Vincent Sanders, who suggested "s3c":

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503292#17

Another discussion took place on the debian-boot mailing list:

  http://lists.debian.org/debian-boot/2009/07/msg00853.html

Gaudenz and me tried to find a "internal" consensus about the name in
private mails and we set on "s3c24xx" for the following reasons:

-> the possible options are s3c24xx, s3c2410, s3c

-> all s3c24xx devices are currently supported by the same kernel
   subarch

 http://armlinux.simtec.co.uk/kautobuild/2.6.31-rc6/s3c2410_defconfig.html

-> not all s3c devices are supported though, see s3c6400, so s3c is
   not an appropriate name

 http://armlinux.simtec.co.uk/kautobuild/2.6.31-rc6/s3c6400_defconfig.html

-> the kernel calls the corresponding defconfig s3c2410, but this seems
   too specific, as it actually supports more than only s3c2410

 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503292#10

Is there any strong opposition to "s3c24xx"?

If no one will complain in one week from now, I will prepare a new
unofficial kernel for the pkg-fso repository, named "2.6.29-1-s3c24xx"
(this kernel version and ABI are not important ATM).

BTW, if the missing patch will be accepted in 2.6.31, Debian can build
an official kernel that can at least boot on the Openmoko GTA02, thus
debian-installer development can officially continue :-)

Thx, bye,
Gismo / Luca


pgpUkQO4BdOYu.pgp
Description: PGP signature

Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set

[Eran Guy]

on 01/08/09 20:17 Dinyar Rabady said the following:

  Hi,

On Tue, Jul 28, 2009 at 12:04 PM, Otavio
Salvador wrote:
  
  

  
  

  The second problem I encountered was that neither my user account was created
during installation nor was the root password set. This left the system fairly
unusable until I used a rescue system to mount my encrypted disk, added a user
to /etc/passwd and /etc/shadow (without a password) and subsequently added
this user to the sudoers group. In this way I could aquire root on my new
system.
  

This is confusing; maybe your media was corrupted in some way since I
don't remember of seeing this report and it is used in every
installation. Could you try to reproduce it and report back to us?


  
  
I actually tried twice, though with the same installation media. I
don't have any plans to reinstall in the near future though (at least
not until the multi-arch stuff screws up my system again.. ;) ) so
sorry about that.
  


I can confirm this- reproduced while installing with different daily
builds (from yesterday, last week & even one from May 2009) using
different media with the same result as reported above.
This might be an issue with one of the packages the installer uses,
since it's also reproduced when using a netinst CD from May 11th, 2009.


-E-





-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: [REMINDER] Installer Team meeting today 20:00 UTC

[Luca Capello]

Hi there!

On Mon, 17 Aug 2009 13:07:39 +0200, Max Vozeler wrote:
> Five people have indicated that they would be around. I think 
> thats fine for (at least a short) meeting.
>
> Time/place, just as reminder:
>
>   ***Today***, August 17th, 20:00 UTC 
>   #debian-boot (irc.debian.org (oftc))

Because of some late stuff in real life, I am not sure I could attend
this meeting, sorry.

FWIW, since I am not involved in anything vital and since Gaudenz is
doing most of the work supporting Openmoko, I do not think my absence
will be heavily noticed ;-)

Thx, bye,
Gismo / Luca


pgp0MUycr8aty.pgp
Description: PGP signature

Bug#538086: installation-reports: Installation works, but neither is user created nor a root password set

[Eran Guy]

on 01/08/09 20:17 Dinyar Rabady said the following:
> Hi,
>
> On Tue, Jul 28, 2009 at 12:04 PM, Otavio
> Salvador wrote:
>  
> 
>
>  
>>> The second problem I encountered was that neither my user account
was created
>>> during installation nor was the root password set. This left the
system fairly
>>> unusable until I used a rescue system to mount my encrypted disk,
added a user
>>> to /etc/passwd and /etc/shadow (without a password) and subsequently
added
>>> this user to the sudoers group. In this way I could aquire root on
my new
>>> system.
>>>  
>> This is confusing; maybe your media was corrupted in some way since I
>> don't remember of seeing this report and it is used in every
>> installation. Could you try to reproduce it and report back to us?
>>
>>
>
> I actually tried twice, though with the same installation media. I
> don't have any plans to reinstall in the near future though (at least
> not until the multi-arch stuff screws up my system again.. ;) ) so
> sorry about that.
>  

I can confirm this- reproduced while installing with different daily
builds (from yesterday, last week & even one from May 2009) using
different media with the same result as reported above.
This might be an issue with one of the packages the installer uses,
since it's also reproduced when using a netinst CD from May 11th, 2009.


-E-



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#396458: Demande de virement de solde sur votre comp te bancaire

[paypal]

Bonjour
 
 Dans le cadre de nos mesures de sécurité, nous contrôlons régulièrement les 
activités en cours dans le système PayPal. Nous vous avons récemment contacté à 
la suite d'un problème sur votre compte PayPal.
 
 
 Des informations vous ont été demandées pour le motif suivant :
 
 Notre système a détecté des débits inhabituels sur une carte de crédit 
associée à votre compte PayPal.
 
 Dossier nº : PP-6841-894-753
 
 Ceci est un dernier rappel vous invitant à vous connecter à PayPal dès que 
possible.
 
  Veuillez rétablir l'accès à votre compte.
 
 
 Veuillez ne pas répondre à cet email. Les emails envoyés à cette adresse ne 
peuvent pas recevoir de réponse.
 
 
­
 Copyright © 1999-2009 PayPal. Tous droits réservés.
 
 PayPal (Europe) S.à r.l. & Cie, S.C.A.
 Société en Commandite par Actions
 Siège social : 5ème étage 22-24 Boulevard Royal L-2449, Luxembourg
 RCS Luxembourg B 118 349
 
 Email PayPal n° PP834 
 

Bug#539744: Frissítse email electrСnico most Enternet

[Tisztelt Felhasználó webmail]

   -- -
  Ez egy internetes újság frissíti az e-mail fiók
  Lásd az alábbi levelezési információk
   -- -
Frissítse UNLP Küldés.

Kedves "ENTERNET e-mail" Uram, ez a ENTERNET mail szerver az összes e-mail
UNLP tulajdonosok. Mi fejlesztjük adatbázis, e-mail center. Mi törli az
összes nem használt "UNLP e-mail", hogy több helyet az új ones.To
megakadályozza a bezárást fiókja lesz, hogy ellenőrizze az alábbi, ha
tudom, hogy ez egy fiókot jelenleg használt.

Azonban "ENTERNET" a panaszok érkeztek ügyfeleink jogosulatlan használata
a ENTERNET e-mail. "Ennek eredményeképpen már a biztonsági
ellenőrzést a postafiókok ügyfeleink védelme érdekében az Ön adatait
a lopás és csalás.

Figyelem! Tulajdonos e-mailt, hogy megtagadja a frissítés e-mailjét
követő két napon belül ez az értesítés kézhezvételétől végleg
elveszti az e-mailt. Meg kell elküldeni az alábbi információkat
forverification
hatásait.

Szükséges információk
Username E-mail :..
Email Jelszó :..
Született :..
Ország vagy terület :..

Köszönjük az együttműködést.
Copyright © 2009





--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Finishing notes: MTD Embedded Onboard flash Partitioning and Installion

[Per Andersson]

Hi!

The short story:

I did not achieve my proposed goal for my Google Summer of
Cod project because of things I did not know about I wrote the
proposal. Flip-side: There is now a solid foundation for future work.

I have learned a lot, met a lot of interesting people, and will
continue my involvment with Debian.

(Read the long story!!)


The long story:

I started out with a project proposal to add support to Debian
installer (d-i) for UBI [0,1]. My original thought was that this was
possible to do entirely by packaging existing tools and adding
a mechanism for configuring UBI to d-i/partman.

By the mid-term evaluation I had a hackish showcase monolithic iso,
showing this as a proof of concept. I also realized that this might not
be enough. The thing I did not understand when I wrote my proposal
was that d-i/partman is very dependent on GNU Parted [2], and if
support for a device is not in Parted it will be very awkward to add it
to d-i/partman.

The week after mid-term (and during DebConf9) I perfomed a thorough
investigation and decided that the way to go was to add support for MTD
and UBI to GNU Parted. Wookey and I also re-evaluated the goals and
 schedule for the rest of the project. The new goal was to have at least
GNU Parted understanding MTD flash by the end of summer.

Since mid-term this is what I have been working with, the first week or
so was mainly struggling with getting it building at all. Otavio and Colin
helped out with during DebConf9, big thanks! The started out with me
researching how Parted works and an assesment of what was needed.
The remaining time I have been adding support for MTD to Parted and
tuning the same. I have pushed my work so far to Alioth. [3]

Results, outline for future work, and instructions to build are on the
Debian wiki. [4]


Best regards,
Per

[0] Unsorted Block Images
[1] http://www.linux-mtd.infradead.org/doc/ubi.html
[2] http://www.gnu.org/software/parted/index.shtml
[3] http://git.debian.org/?p=users/avtobiff-guest/parted.git;a=summary
[4] http://wiki.debian.org/DebianInstaller/MTD


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#541831: installation-reports: Sunfire T2000 success (one minor issue)

[Stephen Gran]

This one time, at band camp, Frans Pop said:
> reassign 541831 finish-install 2.22
> thanks
> 
> On Sunday 16 August 2009, Stephen Gran wrote:
> > Comments/Problems:
> > The only complaint from the install is that after the install was
> > completed and the machine rebooted, there was no getty listening on
> > ttyS0.
> 
> Was the installation itself done over ttyS0? If it was, it surprises me a 
> lot that there was no inittab entry for it.
> 
> It sounds like the "rsc console" is something different, which could 
> explain what you saw. Maybe we need special handling for this case.

The rsc is much like an iLo or alom.  It's just another management
interface that offers a 'console' interface to manage the OS.  I did the
install using this interface, obtained by running 'break -c'.

> Questions:
> - What were the contents of /etc/inittab after the installation? Were
>   the entries for tty[1-6] commented out or not?

# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6

# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100

# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3

I had to uncomment T0 to get a console with 'console -f' from the rsc.

> - Can you reboot the installer, activate a debug shell and give the output
>   of:
>   - console-type

~ # console-type
serial

>   - readlink /proc/self/fd/0

~ # readlink /proc/self/fd/0
/dev/console

>   - # 'pidof debian-installer' does not work in lenny, so we need:
> ps | grep "[/]sbin/debian-installer"
> readlink /proc//fd/0

~ # pidof debian-installer
~ # ps | grep "[/]sbin/debian-installer"
  912 root  1600 S/bin/sh /sbin/debian-installer 
~ # readlink /proc/912/fd/0 
/dev/console

> - If the first is not "serial" and/or the last is not /dev/ttyS0, then
>   how could the need to set up serial console be detected?

That's a very good question.  Interestingly, I see this in dmesg:
[   32.032662] console handover: boot [earlyprom0] -> real [tty0]

So at least at that point, the kernel thinks it _is_ tty0.
Unfortunately, I don't know enough about whether there is a difference
between what you attach to with 'console -f' in the rsc and what you
attach to with 'break -c'.  I naively think that they should be the same
thing, but it is possible that they are not.

> - Does the installer work correctly and does a listener for serial console
>   get set up for the installed system if you boot D-I with console=ttyS0?

No:
steal-ctty: No such file or directory
steal-ctty: No such file or directory
steal-ctty: No such file or directory

Over and over.  So, this doesn't look like a problem the installer can
fix.  It's just odd that the OS doesn't see the serial console on the
same device as the installer does:

sg...@zee:~$ readlink /proc/self/fd/0
/dev/ttyS0

Well, I'm a bit mystified about how this could be fixed, so I don't mind
if you want to close it as unresolvable or punt it over to the sparc
porters to see if they can shed any light on it.

> If changes are needed, that would probably be in the script
> /usr/lib/finish-install.d/90console (from finish-install).

Looks like it's unlikely to need any patching.

Cheers,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :sg...@debian.org |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Bug#541115: armel affected as well

[Gaudenz Steinlin]

Hi 

Just for the record, I also ran into this bug on armel while testing the
installer on the openmoko. It's probably safe to conclude that this bug
affects all architectures.

Gaudenz

-- 
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~


signature.asc
Description: Digital signature

Re: Are you on webcam?

[ashley horny]

Im live on cam now come connect to me and chat free / live 
www.freakymatch.com/fDear debianboot! Get Yourself a cool, short @in.com Email 
ID now!

Processed: Re: Processed (with 2 errors): Re: Bug#541823: installation-reports: Acer Aspire 3690

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 541823 -1
Bug#541823: installation-reports: Acer Aspire 3690
Bug 541823 cloned as bug 542118.

> reassign -1 iso-scan
Bug #542118 [installation-reports] installation-reports: Acer Aspire 3690
Bug reassigned from package 'installation-reports' to 'iso-scan'.
> retitle -1 Consistently fails to find ISO image on first try
Bug #542118 [iso-scan] installation-reports: Acer Aspire 3690
Changed Bug title to 'Consistently fails to find ISO image on first try' from 
'installation-reports: Acer Aspire 3690'
>
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 debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

[PATCH] localechooser: ASCII only if on cons25 terminal

[Luca Favatella]

This patch let localechooser not to try to print non-ascii characters
on a cons25 terminal.

This should not affect d-i images not using cons25 terminal (e.g. linux-*).


Cheers,
Luca Favatella
Index: debian/changelog
===
--- debian/changelog	(revision 60241)
+++ debian/changelog	(working copy)
@@ -3,6 +3,9 @@
   * Only check for validlocale if any locales need to be generated, as
 otherwise we won't have installed the locales package (closes: #538343).
 
+  [ Aurelien Jarno ]
+  * Don't try to print non-ascii characters on a cons25 terminal.
+
  -- Colin Watson   Sat, 25 Jul 2009 11:04:09 +0100
 
 localechooser (2.13) unstable; urgency=low
Index: localechooser
===
--- localechooser	(revision 60241)
+++ localechooser	(working copy)
@@ -66,9 +66,9 @@
 		else
 			level=1
 		fi
-		# ASCII only if we are on serial console or a dumb terminal
+		# ASCII only if we are on serial console, dumb or cons25 terminal
 		# Both variables should already be set at init time
-		if [ "$TERM_TYPE" = "serial" ] || [ "$TERM" = "dumb" ]; then
+		if [ "$TERM_TYPE" = "serial" ] || [ "$TERM" = "dumb" ] || [ "$TERM" = "cons25" ] ; then
 			level=0
 		fi
 		;;

[PATCH] d-i-utils: terminfo different from cons25 on kfreebsd-*

[Luca Favatella]

This patch also ships terminfo different from cons25 on GNU/kFreeBSD.

This should not affect linux-* d-i images.


Cheers,
Luca Favatella
Index: debian/changelog
===
--- debian/changelog	(revision 60241)
+++ debian/changelog	(working copy)
@@ -2,6 +2,10 @@
 
   * Upgrade to debhelper v7.
 
+  [ Aurelien Jarno ]
+  * Also ship other terminfo on GNU/kFreeBSD, they are also used in some
+cases (e.g. installation through openssh).
+
  -- Colin Watson   Thu, 13 Aug 2009 14:52:50 +0100
 
 debian-installer-utils (1.71) unstable; urgency=low
Index: debian/rules
===
--- debian/rules	(revision 60241)
+++ debian/rules	(working copy)
@@ -2,11 +2,11 @@
 %:
 	dh $@
 
-ifeq ($(DEB_HOST_ARCH_OS),linux)
 TERMS=/usr/share/terminfo/a/ansi /usr/share/terminfo/d/dumb \
   /usr/share/terminfo/l/linux /usr/share/terminfo/v/vt102
-else ifeq ($(DEB_HOST_ARCH_OS),kfreebsd)
-TERMS=/usr/share/terminfo/c/cons25
+
+ifeq ($(DEB_HOST_ARCH_OS),kfreebsd)
+TERMS+=/usr/share/terminfo/c/cons25
 endif
 
 override_dh_auto_install:

net-install CD do not work

[Joseph Vidal-Rosset]

Hello,

I've tried several times the netinstall CD with a business card on my new
DELL. Here some bugs that I met in the testing:

(1) It was not possible to install Grub, I have had to choose Lilo.

(2) The keymap was no more configured in azerty: result no mean to get in my
desktop.

(3) The rescue mode of the CD did not success: I've tried it to test a
"dpkg-reconfigure xserver-xorg", no Terminal was done... and I gave it up.
(I have noticed also that the file xorg.conf was void.)

I regret sincerely that the installer of Debian meets again a bug (2) that I
met some years ago. I am worried also about the comparison with the Ubuntu
installer and the Debian's. Ironically the Ubuntu's is based on Debian but
works on my computer, not the Debian's. I regret it because I prefer Debian
and because a popular desktop like Ubuntu cannot live without Debian.

I hope that that these problems with the installer will disappear.

Best wishes
Jo.

please allow ltsp 5.1.81-2 into testing

[Vagrant Cascadian]

ltsp 5.1.81-2 is blocked from migrating into testing, due to the
ltsp-client-builder udeb, though this udeb is not used by debian-installer by
default, and has no changes since the previous version.

it has been in unstable for 9 days without introducing new problems.

thanks!

live well,
  vagrant


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org