from:"Mario"



On 03/30/2016 09:53 AM, Lennart Sorensen wrote:
> On Wed, Mar 30, 2016 at 09:26:11AM -0500, Mario Limonciello wrote:
>> As Jared was mentioning to me the other day, there is unfortunately a
>> mentality in the server world of not installing the OS in UEFI yet and
>> leave the CSM enabled.  The best way to allow for that mentality to
>> break is to allow an easy way for an admin to switch to UEFI mode
>> without re-installation.
> Or perhaps you could have a dialog box telling the user:
>
> You booted in legacy mode.  It is recommended to boot in UEFI mode if
> posible to gain some benefits:
> - list of benefits
>
> That seems like a lot less trouble.
I think this is a great first step out of this thread.  The challenge I
see with this is how you identify a machine that happens to be running a
BIOS that actually supports running in a UEFI mode.

If the system supports SMBIOS 2.3 or later, then the BIOS
characteristics extension byte 2 bit 3 should indicate that UEFI is
supported.

Where in the installer would this dialog land?  Somewhere early on in
d-i I'd think after you picked your language but before you've gotten to
partitioning.
>
>> Yes, this will only help people wiling to reformat their disk.  I think
>> if Debian can lead the way in switching to GPT by default it can be a
>> role model for other distributions to make this change as well. 
> Again, if you want to lead that, then tell people to switch their system
> to UEFI before installing.  Don't do it by making a hack job install
> that can cause lots of problems later.
>
>> To me this is an acceptable compromise. 
>>
>> IIRC there is a debconf question about installing to the removable path
>> when you install EFI GRUB2.  What are the defaults for this? 
>> Would you consider making the default yes if you identify they are
>> running in legacy mode when you install the EFI GRUB2 (to do this
>> bootloader switch).
> That could be a useful feature.
>
> A simple tool to change a disk from MBR to GPT without changing the
> placement of partitions could also be handy.  That could REALLY help
> people to move to GPT.  You would have to find a way to make room for
> the ESP or BIOS Boot Partition though.
>
I'm assuming simple is a relative term.  You would have to be able to
resize a filesystem in order to make another partition for the ESP. 
Then you also could run into a situation of a system that wouldn't like
an ESP that it finds later in the disk.  I don't know how common this
problem is.

Re: Simultaneous EFI and Legacy bootloader installation



On 03/30/2016 09:48 AM, Lennart Sorensen wrote:
> On Wed, Mar 30, 2016 at 09:16:35AM -0500, Mario Limonciello wrote:
>> Can you comment what version of Windows you had noticed this behavior? 
>> We actually factory install as old as Windows 7 with GPT disks in legacy
>> mode at Dell.  We don't factory install Windows 8 or Windows 10 in
>> legacy mode.
> Well certainly with Windows 7 and Windows 10, if you boot legacy mode,
> you don't get an option to use GPT.  And everything I have ever read
> says you can't do that with Windows because Microsoft says so.
> Certainly the hybrid partition table option is a problem since Linux
> and BSD prioritize GPT while windows prioritizes MBR.
>
> Every answer I can find to how to boot windows on GPT with legacy involves
> using an MBR USB key or a floppy as the boot media with the main install
> on GPT (but in that case it is in fact NOT booting from GPT).
In the public consumer facing installer it sounds like this option
doesn't populate automatically.  We don't use the same installer for
factory install in Dell.  We also only do GPT disks with Win7 legacy
when circumstances require it (large disks).

> I can't find anything anywhere that says you can boot on a legacy system
> from GPT with Windows 7, 8, 8.1 or 10.  I can only find lots of people
> asking how to do it and being told you can't without a separate boot
> device that isn't GPT.
The way to do it is to boot a USB disk with WinPE manually and format
the disk with diskpart ahead of time.  You might also be able to
accomplish this with the advanced options that can get you to the
diskpart tool before you actually select the partitioning page.

Windows should happily install onto the existing partitioning then.
>> Shouldn't it be possible to install GRUB into the partition boot record
>> (PBR) of the ESP?
> Certainly when I have used grub to run legacy systems with GPT due to
> large disks, I have used the BIOS Boot partition and grub has been happy,
> while without it you need to use the block map mode that grub highly
> discourages because it is as fragile as lilo always was.  The BIOS Boot
> partition contains the stage2 of grub raw, it does not have a filesystem
> unlike the ESP.  To put stage2 on the ESP you would have to then use
> the block map mode which defeats the purpose of using it and you might
> as well just block map the file in /boot.  Since you don't want to use
> the block map mode, the BIOS Boot Partition is the better option when
> you want grub on a legacy system with GPT.
>
> The < 500 bytes in the PBR is way too small for stage2 of grub and no
> better than using the MBR area (which works for a GPT disk too).
> It could only hold stage1.
Thanks for explaining, this makes sense to me now.
>
>> Yes, this scenario is why I was recommending in legacy mode to install
>> the removable path bootloader (\efi\boot\boot$ARCH.efi) by default.

Re: Simultaneous EFI and Legacy bootloader installation

Thanks for the comments.

On 03/30/2016 06:11 AM, Colin Watson wrote:
> On Tue, Mar 29, 2016 at 07:50:27PM -0500, mario_limoncie...@dell.com wrote:
>> I was briefly discussing this with Steve McIntyre and wanted to bring
>> it to a wider discussion.  Currently users need to make a selection at
>> installation time whether to install in UEFI mode or in Legacy mode.
> In fact pre-installation, because it depends on how they told the
> firmware to boot the installer.  I'd expect modern systems to have
> defaults that lead to UEFI mode, and for this to predominantly be an
> issue on older systems, which means that we need to give more weight to
> considerations that apply to older systems.
As Jared was mentioning to me the other day, there is unfortunately a
mentality in the server world of not installing the OS in UEFI yet and
leave the CSM enabled.  The best way to allow for that mentality to
break is to allow an easy way for an admin to switch to UEFI mode
without re-installation.
 
>> If they installed in legacy mode and later discovered that their
>> system supported extra features in UEFI mode (For example firmware
>> updates) they are penalized and need to redo the installation in order
>> to switch modes.
>>
>> I'd like to propose changing this and by default install both legacy
>> and UEFI bootloaders on architectures that support both regardless of
>> which mode the system is running in at installation.
> I'm pretty wary about this because it seems likely to exacerbate the
> already far too common problems where people end up booting from a GRUB
> installation they don't realise they're booting from, and then at some
> point in the future something changes so that some subset of the
> installed GRUB instances don't get updated properly and then everything
> explodes mysteriously.  (Usually I find out about this when I upload
> GRUB and then get dozens of bug reports that are in fact due to some bug
> in the installer from years back that's now next to impossible to track
> down.)  Being able to say that UEFI installations just don't need to
> worry about this class of problems is a significant benefit.
>
>> Making this change has a few obvious implications:
>> * The installation disk would always be formatted GPT.
> On the whole I think this is a good direction to go as it's a much
> better partition table type, but a lot of BIOSes object to this in
> practice unless the disk is very specifically and delicately formatted.
>
> parted allows setting the necessary flag ("pmbr_boot"), but I don't
> believe that partman has support for it as yet, and it violates the UEFI
> specification so it's possible that doing this unconditionally would
> cause problems later.
>
>> * An ESP would always be created.
> And, I think, also a BIOS Boot Partition, which starts feeling like a
> lot of overhead on modern systems.
>
>> * If the user is in legacy at installation time, it's not possible to
>> create an EFI boot entry since EFI runtime services aren't present.
>> The removable media fallback path (\efi\boot\boot$ARCH.efi) will need
>> to be used to boot the system at this point and at some point create a
>> "debian" NVRAM boot entry
> Indeed, and this is exactly the scenario you specifically mentioned
> being interested in.  But this is another way that the system can work
> after the initial installation but then be broken by later updates
> because we change the boot path, which to my mind is much worse than not
> working after the initial installation because the user has put more
> effort into their system by that point.
>
>> I'm not aware of any modern systems that are unable to boot a GPT
>> partitioned disk.  If there are systems like this in the wild, it
>> would be worthwhile to leave support to install in MBR mode when doing
>> an expert install so that people can still use them.
> Remember that very many Debian installations happen on systems that are
> already partitioned and frequently already have other operating systems
> on them.  In those cases we're stuck with the partition table type
> that's already in use.
Yes, this will only help people wiling to reformat their disk.  I think
if Debian can lead the way in switching to GPT by default it can be a
role model for other distributions to make this change as well. 
>
> So, I'm very unconvinced about the plan to have more than one boot
> loader instance think that it's responsible for booting the computer.  I
> think that's likely to lead to difficult-to-diagnose problems down the
> line.  How about a compromise?  If we could at least get to the point
> where we install systems with GPT and an ESP where we can even if we
> aren't going to install grub-efi-amd64, then it would at least be
> reasonably straightforward to switch mode by just installing
> grub-efi-amd64 and removing grub-pc; you wouldn't need to redo the
> installation.
>
> That would give most of the benefits you're looking for, albeit at the
> cost of a bit of documentation, without

Re: Simultaneous EFI and Legacy bootloader installation



On 03/30/2016 09:11 AM, Lennart Sorensen wrote:
> On Tue, Mar 29, 2016 at 07:50:27PM -0500, mario_limoncie...@dell.com wrote:
> Certainly windows can NOT boot GPT disks if booted in legacy mode,
> and can only boot GPT disks in UEFI mode.
>
> So you sure can't choose GPT always if there is any other OS ever going
> on the machine because it won't be able to boot in legacy mode.
Can you comment what version of Windows you had noticed this behavior? 
We actually factory install as old as Windows 7 with GPT disks in legacy
mode at Dell.  We don't factory install Windows 8 or Windows 10 in
legacy mode.

> It is possible with grub to mix things although it isn't usually done.
> Booting legacy mode from a GPT disk requires an extra BIOS Boot partition
> to be created to install grub while booting in UEFI mode requires that
> there be a system partition for the boot loader.  So quite different.
Shouldn't it be possible to install GRUB into the partition boot record
(PBR) of the ESP?
> Both could in theory coexist, although you have to have booted in UEFI
> mode to update the NVRAM settings to even add Debian (or anything else)
> to the UEFI boot settings, so it can't be done while in legacy mode.
Yes, this scenario is why I was recommending in legacy mode to install
the removable path bootloader (\efi\boot\boot$ARCH.efi) by default. 
> So sure GPT is nice and all as a default if you only ever want to install
> Linux (and Linux that knows how to boot legacy mode on GPT) and never
> anything else.  Is that really a nice default to force on users?  I would
> think it isn't.
>

Re: Simultaneous EFI and Legacy bootloader installation

2016-03-29 Thread Mario Limonciello


On 03/29/2016 07:50 PM, Limonciello, Mario wrote:
> Hi,
>
> I was briefly discussing this with Steve McIntyre and wanted to bring it to a 
> wider discussion.  Currently users need to make a selection at installation 
> time whether to install in UEFI mode or in Legacy mode.  If they installed in 
> legacy mode and later discovered that their system supported extra features 
> in UEFI mode (For example firmware updates) they are penalized and need to 
> redo the installation in order to switch modes.
>
> I'd like to propose changing this and by default install both legacy and UEFI 
> bootloaders on architectures that support both regardless of which mode the 
> system is running in at installation. Making this change has a few obvious 
> implications:
> * The installation disk would always be formatted GPT.
> * An ESP would always be created.
> * If the user is in legacy at installation time, it's not possible to create 
> an EFI boot entry since EFI runtime services aren't present.  The removable 
> media fallback path (\efi\boot\boot$ARCH.efi) will need to be used to boot 
> the system at this point and at some point create a "debian" NVRAM boot entry
>
> I'm not aware of any modern systems that are unable to boot a GPT partitioned 
> disk.  If there are systems like this in the wild, it would be worthwhile to 
> leave support to install in MBR mode when doing an expert install so that 
> people can still use them.
>
> Thoughts?
>
> Thanks,
Add debian-efi mailing list as well for awareness and to include in
discussion.

Bug#799119: Regression in NVMe support caused by 7046795cdd0e9ca11789ffe0f5cedaa42217f6e0

2015-09-15 Thread Mario Limonciello

package: grub-installer
version: 1.122

I've been trying to debug some problems related to installation on an
NVMe drive and found that 7046795cdd0e9ca11789ffe0f5cedaa42217f6e0
introduced a regression that is causing grub-installer to fail.

This commit was supposed to introduce support for multi-digit X and Y
values of /dev/nvmeXnY but instead causes it to not match on systems
with drives that are not multi-digit.  The [0-9][0-9] syntax is looking
for drives that have multi digits explicitly.

On my system I see nodes for:

/dev/nvme0n1 which will not match in this syntax.

Dropping the second [0-9] from the introduced areas resolves the problem
for me.

Thanks,



signature.asc
Description: OpenPGP digital signature

Bug#799117: NVMe devices are not offered by list-devices

2015-09-15 Thread Mario Limonciello

Package: debian-installer-utils
Version: 1.110

I've found that when using iso-scan to pick up devices, it's not finding
any NVMe devices.  This is because 'list-devices disk' doesn't recognize
NVMe.

This can be fixed with a trivial patch:

# diff --git a/list-devices-linux b/list-devices-linux
index 34ba684..9eb3c71 100755
--- a/list-devices-linux
+++ b/list-devices-linux
@@ -137,7 +137,7 @@ for x in $syspaths; do
fi
if ! $match && [ "$TYPE" = disk ]; then
case $devpath in
-  
/block/cciss\!*|/block/ida\!*|/block/rd\!*|/block/mmcblk*|/block/vd[a-z]*|/block/xvd[a-z]*)
+  
/block/cciss\!*|/block/ida\!*|/block/rd\!*|/block/nvme*|/block/mmcblk*|/block/vd[a-z]*|/block/xvd[a-z]*)
match=:
;;
/block/dm-*)

Here is the udevadm information for a situation where NVMe disk is on
the system (and not otherwise picked up).

P: /devices/pci:00/:00:1b.0/:02:00.0
E: DEVPATH=/devices/pci:00/:00:1b.0/:02:00.0
E: DRIVER=nvme
E: MODALIAS=pci:v144DdA802sv144DsdA801bc01sc08i02
E: PCI_CLASS=10802
E: PCI_ID=144D:A802
E: PCI_SLOT_NAME=:02:00.0
E: PCI_SUBSYS_ID=144D:A801
E: SUBSYSTEM=pci

P: /devices/pci:00/:00:1b.0/:02:00.0/block/nvme0n1
N: nvme0n1
E: DEVNAME=/dev/nvme0n1
E: DEVPATH=/devices/pci:00/:00:1b.0/:02:00.0/block/nvme0n1
E: DEVTYPE=disk
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=2507fc37-a8e6-4344-af2e-8db46d99f5c3
E: MAJOR=259
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=1054

P: /devices/pci:00/:00:1b.0/:02:00.0/block/nvme0n1/nvme0n1p1
N: nvme0n1p1
S: disk/by-partlabel/EFI\x20System\x20Partition
S: disk/by-partuuid/4570c6a5-9fcd-4e1e-9dc2-d470db69f4da
S: disk/by-uuid/D1A6-3882
E: DEVLINKS=/dev/disk/by-partlabel/EFI\x20System\x20Partition
/dev/disk/by-partuuid/4570c6a5-9fcd-4e1e-9dc2-d470db69f4da
/dev/disk/by-uuid/D1A6-3882
E: DEVNAME=/dev/nvme0n1p1
E:
DEVPATH=/devices/pci:00/:00:1b.0/:02:00.0/block/nvme0n1/nvme0n1p1
E: DEVTYPE=partition
E: ID_FS_TYPE=vfat
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=D1A6-3882
E: ID_FS_UUID_ENC=D1A6-3882
E: ID_FS_VERSION=FAT16
E: ID_PART_ENTRY_DISK=259:0
E: ID_PART_ENTRY_NAME=EFI\x20System\x20Partition
E: ID_PART_ENTRY_NUMBER=1
E: ID_PART_ENTRY_OFFSET=4096
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_SIZE=999424
E: ID_PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
E: ID_PART_ENTRY_UUID=4570c6a5-9fcd-4e1e-9dc2-d470db69f4da
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=2507fc37-a8e6-4344-af2e-8db46d99f5c3
E: MAJOR=259
E: MINOR=1
E: SUBSYSTEM=block
E: USEC_INITIALIZED=1117

P: /devices/pci:00/:00:1b.0/:02:00.0/block/nvme0n1/nvme0n1p2
N: nvme0n1p2
S: disk/by-partlabel/OS
S: disk/by-partuuid/f241d95a-42ca-49c2-930a-11f4ed31864c
S: disk/by-uuid/D1A6-40C6
E: DEVLINKS=/dev/disk/by-partlabel/OS
/dev/disk/by-partuuid/f241d95a-42ca-49c2-930a-11f4ed31864c
/dev/disk/by-uuid/D1A6-40C6
E: DEVNAME=/dev/nvme0n1p2
E:
DEVPATH=/devices/pci:00/:00:1b.0/:02:00.0/block/nvme0n1/nvme0n1p2
E: DEVTYPE=partition
E: ID_FS_TYPE=vfat
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=D1A6-40C6
E: ID_FS_UUID_ENC=D1A6-40C6
E: ID_FS_VERSION=FAT32
E: ID_PART_ENTRY_DISK=259:0
E: ID_PART_ENTRY_NAME=OS
E: ID_PART_ENTRY_NUMBER=2
E: ID_PART_ENTRY_OFFSET=1003520
E: ID_PART_ENTRY_SCHEME=gpt
E: ID_PART_ENTRY_SIZE=9766912
E: ID_PART_ENTRY_TYPE=ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
E: ID_PART_ENTRY_UUID=f241d95a-42ca-49c2-930a-11f4ed31864c
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=2507fc37-a8e6-4344-af2e-8db46d99f5c3
E: MAJOR=259
E: MINOR=2
E: SUBSYSTEM=block
E: USEC_INITIALIZED=1167

P: /devices/pci:00/:00:1b.0/:02:00.0/misc/nvme0
N: nvme0
E: DEVNAME=/dev/nvme0
E: DEVPATH=/devices/pci:00/:00:1b.0/:02:00.0/misc/nvme0
E: MAJOR=10
E: MINOR=58
E: SUBSYSTEM=misc



signature.asc
Description: OpenPGP digital signature

Re: Installing Debian remotely in an unmanaged VPS


I see.

I have noticed that there's a preseeding parameter 
network-console/authorized_keys_url, which may point to an URL. Is 
there a way I can *embed* my SSH public key in the initrd and then use 
file:/// or similar and likewise embed the public key to be used by the 
server?


Will it matter which keyboard layout I set in d-i keymap select 
LAYOUT (since it's going to be installed and then managed through SSH)?


Regards and thanks a lot.

P.S: The tutorial in
http://www.papegaaiduiker.be/index.php/local-or-remote-ubuntu-debian-re-installers 
involves downloading an ISO from that user's server, and at any rate it 
seems like the ISO image has to be keep in a partition. I will follow 
the procedure of making a custom net boot image with preseeding.



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/544d694d.4010...@yandex.com

Re: Installing Debian remotely in an unmanaged VPS

I have followed https://wiki.debian.org/DebianInstaller/Remote. It 
almost worked. The problem is that the built image still prompts for a 
keyboard layout locally, and so the image don't meets it purpose for 
local installation. My preseed.cfg is this:


d-i debian-installer/localestring en_US
d-i keymap select us
d-i keyboard-configuration/toggle  select No toggling
d-i debconf/priority   select critical
d-i auto-install/enabled   boolean true
d-i netcfg/choose_interfaceselect eth0
d-i netcfg/get_hostnamestring server
d-i netcfg/get_domain  string server.none
d-i network-console/password   password OMITTED
d-i network-console/password-again password OMITTED

I have trouble finding documentation related to debian-installer and 
presiding. What should I do to preseed the keyboard layout?.


Regards and thanks.


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/544d7cfd.7070...@yandex.com

Fwd: Re: Installing Debian remotely in an unmanaged VPS


Thanks for your help, but I have already included the part of the
example that relates to keyboard configuration and it doesn't work.


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/544d83f1.6000...@yandex.com

Re: Installing Debian remotely in an unmanaged VPS


I achieved success with this preseed:

d-i debian-installer/localestring en_US
d-i console-setup/ask_detect   boolean false
d-i console-setup/layoutcode   select us
d-i keyboard-configuration/xkb-keymap  select us
d-i keyboard-configuration/toggle  select No toggling
d-i debconf/priority   select critical
d-i auto-install/enabled   boolean true
d-i netcfg/choose_interfaceselect eth0
d-i netcfg/get_hostnamestring server
d-i netcfg/get_domain  string server.none
d-i network-console/password   password OMITTED
d-i network-console/password-again password OMITTED

Now what it remains is to configure GRUB using grub-reboot to boot the 
image once and if booted again, fall back to the existing installation 
so as to lower the risk of rending the system effectively unbootable.




--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/544d8c84.7020...@yandex.com

Installing Debian remotely in an unmanaged VPS

2014-10-25 Thread Mario Castelán Castro


Hello.

I'd like to install Debian in an unmanaged VPS which has Debian 
installed already. This is so that I can customize the installation by 
using LVM for instance. I'm following 
https://wiki.debian.org/DebianInstaller/Remote but it seems like I'd 
have to keep an ISO image in the hard disk to do a HD-based installation 
if I can't use a virtualized CD and hence would need to keep at least 
one partition intact. Is there a way to avoid this?.


I suppose that it's possible—at least in principle—to build an ISO image 
which is scripted to copy itself to a tmpfs and then debian-installer 
can continue reading it from there rather than from the hard disk 
directly (So that the hard disk can be modified without the constrain of 
keeping the ISO). Are there instructions on how to do this?.


Otherwise, is it possible to cram a complete Debian installer into a 
initrd?.


Please point me in the right direction.

I found http://www.centosx.com/install-centos-remotely-through-vnc/ 
for CentOS. Apparently there are install images expressly configured for 
remote installation for Red Hat based distributions. Is there something 
similar for Debian?. If not, please consider my suggestion to include 
this feature in a future release.


Regards and thanks.


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/544c3d45.2040...@yandex.com

Bug#729326: partman-auto: Installer doesn't reuse EFI system partitions when specified by recipe

2013-11-11 Thread Mario Limonciello

Package: partman-auto
Version: 114
Severity: normal

Dear Maintainer,

During 4df358695167c0b6e2af5816f364d8a9a734ec05 some support for UEFI installs 
was added.
Within there was some support for reusing EFI system partitions, but the code 
was not
complete.

When preseeded with a recipe set to reuse the existing EFI system partition the 
installer
fails claiming it couldn't find an EFI system partition.  Examining closer it's 
apparent
that the EFI system partiiton was marked as to be formatted rather than reused.

Most of this code came from Ubuntu and this has already been fixed in Ubuntu's 
partman-auto
package.  I've pulled out the two relevant patches that will fix this problem.

I've also applied them to an install of my own and validated that they actually 
do fix the 
behavior.

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-proposed'), (500, 
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-53-generic (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
From 3f84296e7db2a5fe12bcfe57d797f2fefbac58fe Mon Sep 17 00:00:00 2001
From: Mario Limonciello mario_limoncie...@dell.com
Date: Mon, 4 Nov 2013 18:22:35 -0600
Subject: [PATCH] Add the rest of the support necessary to allow reusing EFI
 partitions.

In 4df358695167c0b6e2af5816f364d8a9a734ec05 Steve McIntyre added
initial support for UEFI leveraging a lot of code from Ubuntu.

The modifications made in lib/auto-shared.sh from Ubuntu are also
necessary however for the installer to allow the EFI System Partition
to be reused.
---
 lib/auto-shared.sh |   22 +-
 1 file changed, 21 insertions(+), 1 deletion(-)

diff --git a/lib/auto-shared.sh b/lib/auto-shared.sh
index 2b9c42a..4302738 100644
--- a/lib/auto-shared.sh
+++ b/lib/auto-shared.sh
@@ -92,9 +92,29 @@ ensure_primary() {
 	)
 }
 
-create_primary_partitions() {
+reuse_partitions() {
 	cd $dev
+	local scheme
+
+	scheme=$scheme_reused
+	foreach_partition '
+		id=$(echo  $* | sed -n '\''s/.* \$reuse{ \([^}]*\) }.*/\1/p'\'')
+		if [ -z $id ]; then
+			db_progress STOP
+			autopartitioning_failed
+		fi
+		setup_partition $id $*
+		# Hack to stop EFI partitions showing up as formatted when
+		# they will actually not be.  We do not have a good
+		# interface for this yet.
+		if [ -f $id/method ]  [ $(cat $id/method) = efi ]  \
+		   [ -f $id/detected_filesystem ]; then
+			rm -f $id/format
+		fi'
+}
 
+create_primary_partitions() {
+	cd $dev
 	while [ $free_type = pri/log ]  \
 	  echo $scheme | grep -q '\$primary{'; do
 		pull_primary
-- 
1.7.9.5

[PATCH] Add the rest of the support necessary to allow reusing EFI partitions

2013-11-05 Thread Mario Limonciello

From 3f84296e7db2a5fe12bcfe57d797f2fefbac58fe Mon Sep 17 00:00:00 2001
From: Mario Limonciello supe...@ubuntu.com
Date: Mon, 4 Nov 2013 18:22:35 -0600
Subject: [PATCH] Add the rest of the support necessary to allow reusing EFI
 partitions.

In 4df358695167c0b6e2af5816f364d8a9a734ec05 Steve McIntyre added
initial support for UEFI leveraging a lot of code from Ubuntu.

The modifications made in lib/auto-shared.sh from Ubuntu are also
necessary however for the installer to allow the EFI System Partition
to be reused.
---
 lib/auto-shared.sh |   22 +-
 1 file changed, 21 insertions(+), 1 deletion(-)

diff --git a/lib/auto-shared.sh b/lib/auto-shared.sh
index 2b9c42a..4302738 100644
--- a/lib/auto-shared.sh
+++ b/lib/auto-shared.sh
@@ -92,9 +92,29 @@ ensure_primary() {
  )
 }

-create_primary_partitions() {
+reuse_partitions() {
  cd $dev
+ local scheme
+
+ scheme=$scheme_reused
+ foreach_partition '
+ id=$(echo  $* | sed -n '\''s/.* \$reuse{ \([^}]*\) }.*/\1/p'\'')
+ if [ -z $id ]; then
+ db_progress STOP
+ autopartitioning_failed
+ fi
+ setup_partition $id $*
+ # Hack to stop EFI partitions showing up as formatted when
+ # they will actually not be.  We do not have a good
+ # interface for this yet.
+ if [ -f $id/method ]  [ $(cat $id/method) = efi ]  \
+   [ -f $id/detected_filesystem ]; then
+ rm -f $id/format
+ fi'
+}

+create_primary_partitions() {
+ cd $dev
  while [ $free_type = pri/log ]  \
   echo $scheme | grep -q '\$primary{'; do
  pull_primary


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CA+EcB1M5_w=fda5xvgjtukyonmvmwp4-1j8r_88pwvrcxyj...@mail.gmail.com

Bug#665638: prevent debootstrap vom needing SHA256sums

2012-03-31 Thread Mario Koppensteiner



On Sat, Mar 24, 2012 at 05:35:36PM -0400, Joey Hess wrote:
  Mario Koppensteiner wrote:
 Am I correct in deducing that this mirror is one that was actually
 generated with apt-move, and that's why it's missing the SHA256 fields?

Yes, you are correct.

  Can somebody please implement a parameter which tells debootstrap not
  to relly on SHA256sums and use MD5sums instead?
 
 Well, that would be insecure. Better to fix the mirror?

Yes, I tried to fix the mirror but I don't unterstand the awk script
included in apt-move. See bug [1]. Maybe someone of the Debian Installer
Team can help and fix the awk script?

Related to bug [1], I got a reply there asking if the md5sums are still
neded somewhere in the debian mirror. On the official Debian Mirror I can
still see MD5sum. Can someone of the Debian Installer Team reply to the
post on bug [1] please?

Links:
[1] http://bugs.debian.org/662003

sincerely yours

Mario



signature.asc
Description: Digital signature

Bug#665638: prevent debootstrap vom needing SHA256sums

2012-03-31 Thread Mario Koppensteiner

Hi

I created a patch for apt-move to solve the SHA256 issue. After I
applied my patch to apt-move, debootstrap accepts the local mirror as
expected.

For reference please have a look at the bug [1].


Links:
[1] http://bugs.debian.org/662003


sincerely yours

Mario



signature.asc
Description: Digital signature

Bug#665638: prevent debootstrap vom needing SHA256sums

2012-03-24 Thread Mario Koppensteiner

Package: debootstrap
Version: 1.0.37
Severity: important

Hello,

I have an issue with debootstrap. I debugged the issue and I found the
following:

The Problem is in the file /usr/share/debootstrap/functions line 634

Here is the code of the line 628 to 634
$PKGDETAILS PKGS $m $pkgdest $@ | (
leftover=  
while read p ver arc mdup fil checksum size; do
 if [ $ver = - ]; then
leftover=$leftover $p
else
progress_next $(($dloaddebs + $size))

checksum should contain the SHA256sum and size should contain the size.

But if the Packages.gz file does not contain any SHA256sums, then the
checksum variable contains the size and the size variable is empty.
If that happens then the line 634 executes 0 +

I used the following command:
root# debootstrap --no-check-gpg --verbose squeeze /path/chrootsystem/
ftp://ftp.domain.tld/pub/debian/squeeze
...
I: Found additional base dependencies: libnfnetlink0 libsqlite3-0 
I: Checking component main on ftp://ftp.domain.tld/pub/debian/squeeze...
root#

Note that there is no useful error message at the console. A message
which tells the user to look at debootstrap.log would be nice.

And the file /path/chrootsystem/debootstrap/debootstrap.log conains:
/usr/sbin/debootstrap: 634: /usr/sbin/debootstrap: arithmetic
expression: expecting primary: 0 + 

Can somebody please implement a parameter which tells debootstrap not
to relly on SHA256sums and use MD5sums instead?

About my issue with no SHA256Sums in Packages.gz I already opend
another bug [1].


Links:
[1] http://bugs.debian.org/662003


sincerely yours

Mario Koppensteiner



signature.asc
Description: Digital signature

Re: Problems with d-i on self-made (debian-cd/easy-build.sh) Debian images

2011-11-11 Thread Mario Fux

Am Dienstag 25 Oktober 2011, 14.04:04 schrieb Gaudenz Steinlin:
 Hi Mario

Morning Gaudenz
 
 On Mon, 24 Oct 2011 19:27:48 +0200, Mario Fux debian...@unormal.org wrote:
  Morning again
  
  So no progress. Tried to freshly install debian-cd with new config files
  and without custom packages. Build an ISO image with easy-build.sh DVD
  and got one.
  
  I got some warnings about some GPG stuff which afaik shouldn't be a
  problem.
 
 Hard to tell without any further information...

Yeah, right. Sorry. Will post it next time if it makes sense.

  Doesn't anybody of you is able to build wheezy images which install
  without the kernel module mismatch error? Or is this the wrong mailing
  list and is there a debian-cd one?
 
 Is your local mirror up to date? Where did yout get the debian installer
 image from? If you are building with the debian-installer image from the
 archive this is probably expected, as this package was not updated
 recently.
 
 You have to build your debian-cd image with a daily built installer
 image from http://d-i.debian.org/daily-images/. See README.easy-build
 for instructions on how to build with a custom d-i image.

That was the problem. I thought that the d-i in testing was uptodate. That 
fixed the problem. Thxè!

[snip]
Mario


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111746.29908.debian...@unormal.org

Re: Problems with d-i on self-made (debian-cd/easy-build.sh) Debian images

2011-10-24 Thread Mario Fux

Morning again

So no progress. Tried to freshly install debian-cd with new config files and 
without custom packages. Build an ISO image with easy-build.sh DVD and got 
one.

I got some warnings about some GPG stuff which afaik shouldn't be a problem.

Doesn't anybody of you is able to build wheezy images which install without 
the kernel module mismatch error? Or is this the wrong mailing list and is 
there a debian-cd one?

Btw I tested the image in virtualbox, qemu and with a usb stick on a real 
device. Always the same problem.

Thx for any hint
Mario


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201110241927.48699.debian...@unormal.org

Re: Problems with d-i on self-made (debian-cd/easy-build.sh) Debian images

2011-10-14 Thread Mario Fux

Am Freitag 14 Oktober 2011, 10.07:27 schrieb Gaudenz Steinlin:
 Hi Mario

Morning Gaudenz

 On Thu, 13 Oct 2011 11:45:36 +0200, Mario Fux debian...@unormal.org
 wrote: Non-text part: Multipart/Mixed
 
  Good morning
  
  And then trying to install I got the following error message in qemu and
  virtualbox:
  Error message:
  
  Error: Load installer components from CD:
  No kernel modules were found. This probably is due to a mismatch between
  the kernel used
  by this version of the installer and the kernel version available in the
  archive.
 
 As the error message says (unless there is a bug in d-i itself), the
 version of the kernel you are booting from your CD is not the same as in
 the archive. Which suite (stable, testing, unstable) are you tring to
 install? Did you somhow customize your installer kernel? These versions
 have to match exactly (including ABI version).

No. In the first attempts I used the same version (suite) for the installer 
images as for the rest of the distribution. Afterwards I tried other 
combination: d-i from sid and rest from wheezy. Didn't really help.

 The most likely cause is that the kernel got updated in between the
 moment you built your image and the installation.

Ok. Will try it again in the next days with an uptodate mirror and will come 
back if it doesn't help.

thx
Mario


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201110141940.55941.debian...@unormal.org

Problems with d-i on self-made (debian-cd/easy-build.sh) Debian images

2011-10-13 Thread Mario Fux

Good morning

As I still play with self-made and preseeded Debian images I've some new 
problem where I hope you can help me or give me the right hint. Of course 
before I wrote this email I googled (the error message), read the debian-cd 
documentation and READMEs and tried several updates of my local debian mirror.

My goals was it to add some additional packages which are not (yet) in proper 
Debian. They are finally on the images but as the installer doesn't really 
work (see error message below). I even tried to use other d-is than the wheezy 
one (configurations in the attached files CONF.sh and easy-build.sh).

I used to following command to generate the images.
./easy-build.sh DVD

And then trying to install I got the following error message in qemu and 
virtualbox:
Error message:

Error: Load installer components from CD:
No kernel modules were found. This probably is due to a mismatch between the 
kernel used 
by this version of the installer and the kernel version available in the 
archive.

If you're installing from a mirror, you can work around this problem by 
choosing to
install a different version of Debian. The install will probably fail to work 
if you
continue without kernel modules.

Continue to install without loading kernel modules?
Go back   Yes
No


Do you have any hint or idea what could be wrong?

TIA
Mario


CONF.sh
Description: application/shellscript


easy-build.sh
Description: application/shellscript

Re: Preseeding: No questions in Virtualbox, one on a real computer

2011-07-13 Thread Mario Fux

Morning guys

Nobody an idea or hint? I should know which question is apparently not 
preseeded when I install the image on a real computer but is preseeded in a 
Virtualbox installation.

I don't see any corresponding data or question neither on Alt-F4 nor in 
templates.dat or questions.dat.

The mentioned files are huge and when I just look at the end of the files when 
the question waits for an answer I don't see anything helpful there.

thx
Mario


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107131036.21941.debian...@unormal.org

Re: Preseeding: No questions in Virtualbox, one on a real computer

2011-07-13 Thread Mario Fux

Am Mittwoch 13 Juli 2011, 10.36:21 schrieb Mario Fux:
 Morning guys

Morging ;-)

 Nobody an idea or hint? I should know which question is apparently not
 preseeded when I install the image on a real computer but is preseeded in a
 Virtualbox installation.
 
 I don't see any corresponding data or question neither on Alt-F4 nor in
 templates.dat or questions.dat.
 
 The mentioned files are huge and when I just look at the end of the files
 when the question waits for an answer I don't see anything helpful there.

Now I found the solution myself and wanted to write it down for other people.

The problem or differnce was that virtualbox has just one harddisc but my 
computer two of them. The following line solved the problem and preseeded the 
question:
d-i partman-auto/disk string /dev/sda

thx
Mario


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201107131844.39314.debian...@unormal.org

Preseeding: No questions in Virtualbox, one on a real computer

2011-07-12 Thread Mario Fux

Morning guys

As you helped my last time (problem with not booting ISO images = solution: 
isohybrid) so kindly I thought I ask you again. Of course, after a lot of 
attempts and reading documentation and this kind of trials.

I've a preseeding file (see attached, although the same happens with my other 
preseeding file) based on the documentation [1] and use this with the current 
testing weekly kde cd1 [2].

The problem is that it doesn't ask any question on a virtualbox trial but one 
question on a real computer's installation.

The asked question is about partitioning and to select a method:
* Guided (whole disk)
* Guided ()
* Guided ()
* Manually

(I don't remember the exact wording as I used the german translation.)

And I've no idea why it asks this question as after choosing the first entry 
it uses my preseeded recipe. Do you have any idea? I works perfectly (except 
of a grub problem at the end but that's not the topic here) on Virtualbox. No 
questions at all.

I tried the hints in [1] but did not find anything useful in templates.dat or 
questions.dat in a useful time. Oh and btw is it normal the the preseeding 
lines in the debconf-get-selections --installer output are jumbled up and not 
really in the installation order?

Hope you can give me again some hints and tia
Mario

[1] http://www.debian.org/releases/stable/i386/apbs03.html.en
[2] http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-
testing-i386-kde-CD-1.iso
 Contents of the preconfiguration file (for squeeze)
### Localization
# Preseeding only locale sets language, country and locale.
d-i debian-installer/locale string de_CH

# The values can also be preseeded individually for greater flexibility.
#d-i debian-installer/language string en
#d-i debian-installer/country string NL
#d-i debian-installer/locale string en_GB.UTF-8
# Optionally specify additional locales to be generated.
#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8

# Keyboard selection.
#d-i console-tools/archs select at
d-i console-keymaps-at/keymap select sg-latin1
d-i keyboard-configuration/xkb-keymap select de_CH
# Example for a different keyboard architecture
#d-i console-keymaps-usb/keymap select mac-usb-us

### Network configuration
# Disable network configuration entirely. This is useful for cdrom
# installations on non-networked devices where the network questions,
# warning and long timeouts are a nuisance.
#d-i netcfg/enable boolean false

# netcfg will choose an interface that has link if possible. This makes it
# skip displaying a list if there is more than one interface.
d-i netcfg/choose_interface select auto

# To pick a particular interface instead:
#d-i netcfg/choose_interface select eth1

# If you have a slow dhcp server and the installer times out waiting for
# it, this might be useful.
#d-i netcfg/dhcp_timeout string 60

# If you prefer to configure the network manually, uncomment this line and
# the static network configuration below.
#d-i netcfg/disable_dhcp boolean true

# If you want the preconfiguration file to work on systems both with and
# without a dhcp server, uncomment these lines and the static network
# configuration below.
#d-i netcfg/dhcp_failed note
#d-i netcfg/dhcp_options select Configure network manually

# Static network configuration.
#d-i netcfg/get_nameservers string 192.168.1.1
#d-i netcfg/get_ipaddress string 192.168.1.42
#d-i netcfg/get_netmask string 255.255.255.0
#d-i netcfg/get_gateway string 192.168.1.1
#d-i netcfg/confirm_static boolean true

# Any hostname and domain names assigned from dhcp take precedence over
# values set here. However, setting the values still prevents the questions
# from being shown, even if values come from dhcp.
d-i netcfg/get_hostname string jupiter2
d-i netcfg/get_domain string 

# Disable that annoying WEP key dialog.
#d-i netcfg/wireless_wep string
# The wacky dhcp hostname that some ISPs use as a password of sorts.
#d-i netcfg/dhcp_hostname string radish

# If non-free firmware is needed for the network or other hardware, you can
# configure the installer to always try to load it, without prompting. Or
# change to false to disable asking.
#d-i hw-detect/load_firmware boolean true

### Network console
# Use the following settings if you wish to make use of the network-console
# component for remote installation over SSH. This only makes sense if you
# intend to perform the remainder of the installation manually.
#d-i anna/choose_modules string network-console
#d-i network-console/password password r00tme
#d-i network-console/password-again password r00tme

### Mirror settings
# If you select ftp, the mirror/country string does not need to be set.
#d-i mirror/protocol string ftp
d-i mirror/country string manual
d-i mirror/http/hostname string http.ch.debian.org
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string

# Suite to install.
#d-i mirror/suite string testing
# Suite to use for loading installer components (optional).
#d-i

Re: Preseeded d-i image doesn't boot from USB anymore

2011-05-07 Thread Mario Fux

Am Freitag 06 Mai 2011, 23.07:32 schrieb Philip Hands:
 Hi Mario,

Morning Phil

[snip: Detailed description]

Thx a lot for this. Will try it and work with it in the next hours and days.
Mario


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201105071132.52303.debian...@unormal.org

Preseeded d-i image doesn't boot from USB anymore

2011-05-06 Thread Mario Fux

Morning d-iers

First and foremost thanks a lot for your amazing work on d-i! I use Debian 
since years and the installation is always fantastically easy.

A few weeks ago I started to work with d-i's preseedeing capabilities and 
after finding a nice way (or better a description in the debian wiki [1]) to 
regenerate the debian ISO image with the new preseeded installer a problem 
appeared for me which I couldn't solve. Neither by finding a solution in the 
debian wiki, with Google or nor by reading the debian installation manual.

To regenerate the debian ISO I use the attached script (modified from [1]) and 
here is a short extract of the included commands:

###
mkdir /tmp/loop
mount -o loop $1 /tmp/loop
mkdir /tmp/cd
rsync -a -H --exclude=TRANS.TBL /tmp/loop/ /tmp/cd/
umount /tmp/loop

mkdir irmod
cd irmod
gzip -d  /tmp/cd/install.386/initrd.gz | cpio --extract --verbose --make-
directories --no-absolute-filenames
cp $2 preseed.cfg

find . | cpio -H newc --create --verbose | gzip -9  
/tmp/cd/install.386/initrd.gz
cd ../
rm -rf /tmp/irmod

genisoimage -o test.iso -r -J -no-emul-boot -boot-load-size 4 -boot-info-table 
-b isolinux/isolinux.bin -c isolinux/boot.cat .
###

$1 is the used Debian testing ISO and $2 the preseeding file.

When I test this generated image in Virtual box it works flawlessly. But when 
I copy the image to a USB stick (with every of the 3 in the installation 
manual described methods) it doesn't boot on any PC I've tried (at least three 
different).

When I copy the unmodified Debian image to a USB stick it works.

So where is the problem? I'm thankful for every hint.

Thx a lot for any help
Mario

[1] http://wiki.debian.org/DebianInstaller/Preseed/EditIso


makepreiso.sh
Description: application/shellscript

Bug#619711: console-setup: breaks copying keymap to initramfs

2011-03-26 Thread Mario 'BitKoenig' Holbe

Package: console-setup   
Version: 1.71
Severity: grave

Hello,

if a system's keymap needs to be loaded during the initramfs stage,
initramfs-tools' /usr/share/initramfs-tools/hooks/keymap looks for 
/etc/console-setup/cached.kmap.gz
and copies it to the initramfs.

console-setup 1.71 changed the name of this file to
/etc/console-setup/cached_${CHARMAP}_$backspace$VARIANT.kmap.gz
i.e. something like
/etc/console-setup/cached_ISO-8859-15_del.kmap.gz

Hence, /etc/console-setup/cached.kmap.gz doesn't exist anymore on fresh
installed systems and is thus not copied to the initramfs anymore.
This renders systems unbootable because, for example, passphrases cannot
be entered.
This bug hides well on upgraded systems, because console-setup doesn't
remove the old /etc/console-setup/cached.kmap.gz.

There are several alternatives to fix this bug like
* symlinking the new name to the old
* moving the keymap-copying from initramfs-tools to console-setup
* updating initramfs-tools to honor the new keymap name
Most of those alternatives need to be negotiated with initramfs-tools
and probably other initramfs-creators as well.
However, at the current stage console-setup should break on
packages that depend on the old naming scheme.


Thanks for your work  regards
   Mario
-- 
We know that communication is a problem, but the company is not going to
discuss it with the employees.
   -- Switching supervisor, ATT Long Lines Division


signature.asc
Description: Digital signature

Bug#613277: anna: [DACA] popen+fclose should be popen+pclose

2011-02-13 Thread Mario Lang

Package: anna
Version 1.39
Severity: minor
Tag: patch

DACA reports a mismatching allocation and deallocation in util.c:

  http://qa.debian.org/daca/cppcheck/sid/anna_1.39.html

Right, popen should be used together with pclose.

Patch attached.

--- anna-1.39/util.c.orig	2009-07-23 19:43:25.0 +0200
+++ anna-1.39/util.c	2011-02-13 21:35:34.548412831 +0100
@@ -208,13 +208,13 @@
 	if (fp == NULL)
 		return 0;
 	if (fgets(line, sizeof(line), fp) != NULL) {
-		fclose(fp);
+		pclose(fp);
 		if (strlen(line)  32)
 			return 0;
 		line[32] = '\0';
 		return !strcmp(line, sum);
 	}
-	fclose(fp);
+	pclose(fp);
 	return 0;
 }
 

-- 
CYa,
  ⡍⠁⠗⠊⠕

Re: Preseed and crypto

2010-11-12 Thread Mario Kleinsasser

Well, have not need it until today but I will take a look on it in the next
few days.

Have you done any research until today on it?

Mario

On Thu, Nov 11, 2010 at 9:42 PM, Diego Woitasen di...@woitasen.com.arwrote:

 Hi,
  Is there any documentation about preseed and crypto? I haven't found
 anything, no docs, no examples, nothing.

  I want to preseed a simple instalation with /boot, swap and / (using
 the entire disk). The last two encrypted with dm-crypt.

 Any example is welcome.

 Regards,
  Diego

 --
 Diego Woitasen


 --
 To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/aanlktikwppz31gx42brysjt2jdvobfdxx=bzawwah...@mail.gmail.com




-- 
http://www.n0r1sk.com

Re: preseed software raid, one device with many partitions?

2010-10-29 Thread Mario Kleinsasser

Hello,

I would love to,  but from my googling it sounds like preseeding software
 raid
 + LVM is a black art of some sorts.  Lots of chatter on google,  but not
 much
 solid info.  If anyone has any examples of this,  I'd love to see them.

 TBH,  I don't think the many raid device issue is a breaker,  it just
 looks
 messier then a nice hardware raid /dev/sda device.


We are using the following setting to preseed a LVM configuration during
netinstaller setup on multiple servers without any issues.

d-i partman-auto/method string lvm
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-lvm/confirm boolean true
d-i partman-auto/expert_recipe string \
  boot-root ::\
  150 150 150 ext3\
  $primary{ } $bootable{ }\
  method{ format } format{ }  \
  use_filesystem{ } filesystem{ ext3 }\
  mountpoint{ /boot } \
  .   \
  5120 5120 5120 ext3 \
  $primary{ } method{ format } format{ }  \
  use_filesystem{ } filesystem{ ext3 }\
  mountpoint{ / } \
  .   \
  500 1 10 ext3   \
  method{ format } format{ } $lvmok{ }\
  use_filesystem{ } filesystem{ ext3 }\
  mountpoint{ /var }   \
  .   \
  4096 4096 4096 linux-swap   \
  method{ swap } format{ } $lvmok { } \
  .
d-i partman/confirm_write_new_label boolean true
d-i partman/choose_partition \
   select Finish partitioning and write changes to disk
d-i partman/confirm boolean true

This works with the latest Debian 5.0.6. Please try this settings. I you
want I could post our whole configuration.
Be careful that you are not missing any dots in the lines!

Mario

-- 
http://www.n0r1sk.com

Re: l need help

Hello,

what networkcard is in the HP ML350? Or could you explain your problem more
exactly? Maybe some others could help you.

Mario

-- 
+
http://www.n0r1sk.com

On Tue, Oct 26, 2010 at 1:58 PM, franki asabere franki.asab...@gmail.comwrote:

 Hi Javier,

 This Frank again, the guy whom you helped to install network card firmware
 on HP ML350.
  l need your help again, could you please help me to install network card
 on debian 5.0?

 Looking forward to hearing from you
 Thank you

 --

 ~~
 Systems and Network administrator
 Mob:+233 243 804 126
 ~~

Re: l need help

On Tue, Oct 26, 2010 at 4:23 PM, Lennart Sorensen 
lsore...@csclub.uwaterloo.ca wrote:

 On Tue, Oct 26, 2010 at 02:56:15PM +0100, franki asabere wrote:
  Thank you very much for your quick response.
 
  Sorry l didt explain well.
 
  The server is Dell Optiplex 780 and the network card is on-board. The
 debian
  cant detect the network card

 What does 'lspci -n | grep 0200' show on the box?  That should get a
 list of all ethernet devices.


Are you trying to install with netinstaller iso or have you setup a system
from full media?



 If is of course very possible that the 2.6.26 kernel in Debian 5.0 does
 not support the network card if the machine is less than 2 years old.
 If so there isn't much choice other than use a newer kernel (2.6.32 is
 in backports so it would be easy to install and use).


Yes.



 --
 Len Sorensen



Mario



-- 
+
http://www.n0r1sk.com

Re: l need help

So, after a quit research with google, it seams like that Lennarts
information is correct. The e1000 driver used by the Lenny installer seams
like to old for you network card. I would suggest to build an own kernel for
the d-i. Could be little bit tricky.

For more infos read on here -
http://wiki.debian.org/DebianInstaller/Modify/CustomKernel

Mario

On Tue, Oct 26, 2010 at 5:13 PM, franki asabere franki.asab...@gmail.comwrote:

 Ok.

 l saw the card as this Intel Corporation 82567LM-3 Gigabit Network
 Connection (rev 02)



 On Tue, Oct 26, 2010 at 3:59 PM, Mario Kleinsasser 
 mario.kleinsasser+deb...@gmail.com 
 mario.kleinsasser%2bdeb...@gmail.comwrote:

 Ok. When the first screen from the netinstaller is loaded, I mean its the
 language selection, you could press ALT+F2 to change to a terminal.
 After that press enter to activate the terminal an enter lspci. Theoretic
 this should print an output like that in my screenshot that I append here.
 (Its from a virtual machine). Maybe we could see the networkcard

 Mario



 On Tue, Oct 26, 2010 at 4:49 PM, franki asabere franki.asab...@gmail.com
  wrote:

 Yes please, l m using netinst


 On Tue, Oct 26, 2010 at 3:37 PM, Mario Kleinsasser 
 mario.kleinsasser+deb...@gmail.commario.kleinsasser%2bdeb...@gmail.com
  wrote:


 On Tue, Oct 26, 2010 at 4:23 PM, Lennart Sorensen 
 lsore...@csclub.uwaterloo.ca wrote:

 On Tue, Oct 26, 2010 at 02:56:15PM +0100, franki asabere wrote:
  Thank you very much for your quick response.
 
  Sorry l didt explain well.
 
  The server is Dell Optiplex 780 and the network card is on-board. The
 debian
  cant detect the network card

 What does 'lspci -n | grep 0200' show on the box?  That should get a
 list of all ethernet devices.


 Are you trying to install with netinstaller iso or have you setup a
 system from full media?



 If is of course very possible that the 2.6.26 kernel in Debian 5.0 does
 not support the network card if the machine is less than 2 years old.
 If so there isn't much choice other than use a newer kernel (2.6.32 is
 in backports so it would be easy to install and use).


 Yes.



 --
 Len Sorensen



 Mario



 --
 +
 http://www.n0r1sk.com




 --

 ~~
 Systems and Network administrator
 Mob:+233 243 804 126
 ~~




 --
 +
 http://www.n0r1sk.com




 --

 ~~
 Systems and Network administrator
 Mob:+233 243 804 126
 ~~




-- 
+
http://www.n0r1sk.com

Re: l need help

On Tue, Oct 26, 2010 at 5:33 PM, Lennart Sorensen 
lsore...@csclub.uwaterloo.ca wrote:

 On Tue, Oct 26, 2010 at 05:29:27PM +0200, Mario Kleinsasser wrote:
  So, after a quit research with google, it seams like that Lennarts
  information is correct. The e1000 driver used by the Lenny installer
 seams
  like to old for you network card. I would suggest to build an own kernel
 for
  the d-i. Could be little bit tricky.
 
  For more infos read on here -
  http://wiki.debian.org/DebianInstaller/Modify/CustomKernel

 This guy here has been maintaining Debian installers with newer kernels
 for many years:
 http://kmuto.jp/debian/d-i/


Wow, cool!


 Simpler than having to make your own.


Agreed!
That would be worth an entry on
http://wiki.debian.org/DebianInstaller/Modify, or?


 --
 Len Sorensen



Mario



-- 
+
http://www.n0r1sk.com

Re: l need help

As Lennart says, you could try a ready to use d-i iso from
http://kmuto.jp/debian/d-i/.

Download one of the custom images and try it because it would maybe the
easiest way for you.

Mario

On Tue, Oct 26, 2010 at 5:45 PM, franki asabere franki.asab...@gmail.comwrote:

 Please, help me to build the kernel since l dont have much idea as to how
 to build it


 On Tue, Oct 26, 2010 at 4:33 PM, Lennart Sorensen 
 lsore...@csclub.uwaterloo.ca wrote:

 On Tue, Oct 26, 2010 at 05:29:27PM +0200, Mario Kleinsasser wrote:
  So, after a quit research with google, it seams like that Lennarts
  information is correct. The e1000 driver used by the Lenny installer
 seams
  like to old for you network card. I would suggest to build an own kernel
 for
  the d-i. Could be little bit tricky.
 
  For more infos read on here -
  http://wiki.debian.org/DebianInstaller/Modify/CustomKernel

 This guy here has been maintaining Debian installers with newer kernels
 for many years:
 http://kmuto.jp/debian/d-i/

 Simpler than having to make your own.

 --
 Len Sorensen




 --

 ~~
 Systems and Network administrator
 Mob:+233 243 804 126
 ~~




-- 
+
http://www.n0r1sk.com

Re: l need help

Have made an update on http://wiki.debian.org/DebianInstaller/Modify to list
the link to http://kmuto.jp/debian/d-i/.
Could be interesting for some other people.

Mario

On Tue, Oct 26, 2010 at 5:57 PM, Lennart Sorensen 
lsore...@csclub.uwaterloo.ca wrote:

 On Tue, Oct 26, 2010 at 04:45:34PM +0100, franki asabere wrote:
  Please, help me to build the kernel since l dont have much idea as to how
 to
  build it

 I really wouldn't bother.  Making a custom installer is a lot of work
 for a one time use.  Since the guy in japan has already done that work,
 just use that.  I ahve used that in the past.

 http://kmuto.jp/debian/d-i/

 For amd64 the installer cd is:
 http://mirror.home-dn.net/d-i/2.6.32/amd64/lenny-custom-0116.iso

 For i386 the isntaller cd is:
 http://mirror.home-dn.net/d-i/2.6.32/lenny-custom-0116.iso

 They have 2.6.32 kernels at this time according to the main page.

 He has been doing this for Lenny, Etch and Sarge, so he has many years
 of experience making updated installer images.

 After installing, add backports.debian.org to your sources.list and use
 the 2.6.32 kernel from there.  backports is now an official Debian
 feature.

 --
 Len Sorensen




-- 
http://www.n0r1sk.com

Re: unattended lenny 5.0.4 preseed option fail

2010-10-07 Thread Mario Kleinsasser

Hello,

in your preseed.cfg under the ### Package selection you have not specified
any package selections.

You have to specify a package selection like this (minimal system):

### Package selection
#tasksel tasksel/first multiselect standard
# If the desktop task is selected, install the kde and xfce desktops
# instead of the default gnome desktop.
#tasksel tasksel/desktop multiselect kde, xfce
#d-itasksel/first   multiselect
#tasksel tasksel/first  multiselect
#tasksel tasksel/tasks  multiselect
tasksel tasksel/first multiselect standard

I've commented your settings and added one line.

Regards,

Mario
http://www.n0r1sk.com


On Thu, Oct 7, 2010 at 2:40 PM, leonardo Cuyar Morales
leona...@softel.cuwrote:

  I remaster a debian lenny install iso with a preseed in order to have
  a full unattended lenny installation, but at testing fase
  (installation) there still showing me the package manager windows
  asking if I want to scan another CD. I look all the preseed examples
  files googling around but there isn't an option on this. I attach my
  preseed.cfg and the isolinux.cfg in case you find any error

 Imagination is more important than knowledge

Bug#591633: user-setup: fails to install

2010-08-04 Thread Mario 'BitKoenig' Holbe

Package: user-setup
Version: 1.32
Severity: grave

Hello,

user-setup 1.32 fails to install:

Preparing to replace user-setup 1.31 (using .../user-setup_1.32_all.deb) ...
Unpacking replacement user-setup ...
Setting up user-setup (1.32) ...
Template parse error near `description...@latin.utf-8: Dozvoliti logovanje na 
sistem kao ârootâ korisnik?', in stanza #5 of 
/var/lib/dpkg/info/user-setup.templates
dpkg: error processing user-setup (--configure):
 subprocess installed post-installation script returned error exit status 9
Errors were encountered while processing:
 user-setup

Downgrading to 1.31 works well.

Probably related packages:
ii  adduser3.112  add and remove users and groups
ii  apt0.7.25.3   Advanced front-end for dpkg
ii  debconf1.5.33 Debian configuration management system
ii  dpkg   1.15.8.3   Debian package management system
ii  passwd 1:4.1.4.2-1change and administer password and


regards
   Mario
-- 
Um mit einem Mann gluecklich zu werden, muss man ihn sehr gut
verstehen und ihn ein bisschen lieben.
Um mit einer Frau gluecklich zu werden, muss man sie sehr lieben
und darf erst gar nicht versuchen, sie zu verstehen.


signature.asc
Description: Digital signature

Bug#570273: debian-installer: netboot stops after loading pxelinux.cfg/default

2010-02-24 Thread Mario 'BitKoenig' Holbe

On Wed, Feb 24, 2010 at 06:02:44PM +0100, Frans Pop wrote:
 I've done a quick test using tftpd-hpa with the '-r tsize' option, which 
 should make it not accept that option.
 D-I still boots fine when I use the lenny or squeeze images.

Could you please try tftpd (plain, from netkit-tftp)?
I was using tftpd 0.17-16 from lenny.

 So that does seem to confirm that tsize is not the problem here. It also 
 seems more likely that it's not syslinux that's broken, but either the PXE 
 client in Mario's system(s), or his TFTP server (I'd bet on the latter).

The PXE client was from the installer tarball (I tested lenny and
squeeze), the tftp server was tftpd 0.17-16 and the dhcp server was
dhcp3-server 3.1.1-6+lenny4.

Ferenc: I did not miss your request for information, I just need some
spare time to reproduce it.


regards
   Mario
-- 
To err is human. To really foul things up requires a computer.


signature.asc
Description: Digital signature

Bug#570273: debian-installer: netboot stops after loading pxelinux.cfg/default

2010-02-18 Thread Mario 'BitKoenig' Holbe

On Thu, Feb 18, 2010 at 01:18:01AM +0100, Frans Pop wrote:
 Problem is: it works perfectly here for me using the daily image you linked 
 to on two systems: in VirtualBox and my (oldish) Toshiba laptop.

All right, I think I got it... syslinux/pxelinux.txt states, that:

PXELINUX currently requires that the boot server has a TFTP server
which supports the tsize TFTP option (RFC 1784/RFC 2349).

So, purging tftpd and installing either tftpd-hpa or atftpd does the
trick.
However, although tftpd-hpa generally works, it is horribly slow in
inetd as well as in standalone mode, i.e. it takes ages until some menu
is displayed (having a look at the network traffic going on in the
meantime shows why :/). atftpd does its job very well and quick.

I would suggest to put some notes regarding this issue in the
Installation Guide:
a) add a huge warning note about using Debian's tftpd package in
conjunction with Network boot, and
b) strongly suggest atftp to the disadvantage of tftpd-hpa.


If I got this tsize TFTP option thingy right, the tsize option needs
to be negotiated between client and server, thus pxelinux should be able
to notice that the server it talks to does not understand it (either
tsize or negotiation at all). Thus, pxelinux should be able to print
some warning or error message when it talks to a tftp server not
supporting tsize.

Depending on what you think about using this bug to modify the
Installation Guide I'll either clone or reassign it to syslinux.


Thanks for your help  regards
   Mario
-- 
jv Oh well, config
jv one actually wonders what force in the universe is holding it
jv and makes it working
Beeth chances and accidents :)


signature.asc
Description: Digital signature

Bug#570273: debian-installer: netboot stops after loading pxelinux.cfg/default

2010-02-18 Thread Mario 'BitKoenig' Holbe

On Thu, Feb 18, 2010 at 08:43:34PM +0100, Frans Pop wrote:
  a) add a huge warning note about using Debian's tftpd package in
  conjunction with Network boot, and
 
 Something like the Note here you mean?
http://www.debian.org/releases/sarge/i386/ch04s06.html.en

Uh, I was carefully reading all the stuff under 4.5.3. Enabling the
TFTP Server and found nothing :) Now, with your comment I grepped for
Note and found the other one too :)

 IIRC atftp had problems with some architectures. We mention both, but we've 
 found that across the board there are the least issues with tftpd-hpa.

Okay.


Thanks again
   Mario
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


signature.asc
Description: Digital signature

Bug#570273: debian-installer: netboot stops after loading pxelinux.cfg/default

Package: debian-installer
Version: 20100211

Hello,

the debian-installer netboot stops after the message:
Trying to load: pxelinux.cfg/default

The machine in question is an Asus P5Q-EM (Intel G45 chipset) with an
Intel Core2Duo E2200 and 4G RAM. Neither the HDMI (default) nor the VGA
output shows anything else than the message above. Ctrl-Alt-Del is not
working.

The same problem occurs on an Asus CUV4X-EA (VIA Apollo Pro133A chipset)
with an Intel P3-1GHz and 768M RAM.

It looks like switching to a graphical interface or something like that
goes wrong: when I disable the following line in pxelinux.cfg/default
default debian-installer/i386/boot-screens/vesamenu.c32
and try again, I get a
Invalid or corrupt kernel image.
message followed by a
boot:
prompt offering
install mainmenu expert rescue auto mainmenu-kde
etc. pp. items.

Booting into install or rescue then works well and I get prompted
for my language settings afterwards.

I downloaded
http://ftp.de.debian.org/debian/dists/squeeze/main/installer-i386/current/images/netboot/netboot.tar.gz
and extracted it to /srv/tftp.

# cat /srv/tftp/version.info
Debian version: 6.0 (squeeze)
Installer build: 20100211

The (somewhat newer)
http://people.debian.org/~joeyh/d-i/images/daily/netboot/netboot.tar.gz
(Installer build: 20100217-16:54) behaves identical.

The debian-installer netinst iso-image works well and seems to get the
switch to graphics right. The vesamenu.c32 on both the netboot tarball
and netinst iso is identical.

Feel free to clone or reassign this bug to syslinux if you think it's a
pxelinux issue.

Thanks for your work regards
Mario
--
Independence Day: Fortunately, the alien computer operating system works just
fine with the laptop. This proves an important point which Apple enthusiasts
have known for years. While the evil empire of Microsoft may dominate the
computers of Earth people, more advanced life forms clearly prefer Macs.

signature.asc
Description: Digital signature

Bug#570273: debian-installer: netboot stops after loading pxelinux.cfg/default

On Wed, Feb 17, 2010 at 11:09:15PM +0100, Frans Pop wrote:
 Have you tried enabling logging for your tftp server to see if there are 
 any problems serving the files needed by the installer?

There are no such errors (as btw. the rest of my mail does also prove
where I'm describing how I got the whole stuff working without that
ominous vesamenu.c32 :)).


regards
   Mario
-- 
Singing is the lowest form of communication.
 -- Homer J. Simpson


signature.asc
Description: Digital signature

Bug#570273: debian-installer: netboot stops after loading pxelinux.cfg/default

On Thu, Feb 18, 2010 at 01:18:01AM +0100, Frans Pop wrote:
 So we need to find out why it works so differently for you. I don't think 
 it's a D-I issue as nothing has changed, and I'd like to rule out that 
 it's not a local configuration issue before reassigning to syslinux.
 
 I'd really like to see the log from the tftp daemon with verbose option 
 enabled.

All right, here we go.

I attached 3 tftpd logs:
p5q.failboot with P5Q-EM and fresh squeeze netboot.tar.gz
p5q.ok  boot with P5Q-EM and vesamenu.c32 commented out
cuv4x.fail  boot with CUV4X-EA and fresh squeeze netboot.tar.gz

# md5sum /srv/tftp/pxelinux.0 /srv/tftp/pxelinux.cfg/default 
/srv/tftp/debian-installer/i386/boot-screens/vesamenu.c32
5154a8b498f13dad5a556951ab769c3c  /srv/tftp/pxelinux.0
1cd0d0cbe3ac8d0f695ac2903c8666a5  /srv/tftp/pxelinux.cfg/default
1fe1ac1555cf28b17d8c90e36c92c39a  
/srv/tftp/debian-installer/i386/boot-screens/vesamenu.c32

The pxelinux.0 md5 equals to syslinux 2:3.83+dfsg-3 pxelinux.0 md5.
The vesamenu.c32 md5 equals to debian-testing-i386-netinst.iso
vesamenu.c32 md5.

Just to be sure my tftp server cannot serve anything different:
# find / -name pxelinux.0 -print -o -name vesamenu.c32 -print
/srv/tftp/debian-installer/i386/pxelinux.0
/srv/tftp/debian-installer/i386/boot-screens/vesamenu.c32
/srv/tftp/pxelinux.0

Since you said nothing has been changed, I also tested
http://ftp.de.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/netboot.tar.gz
Same behaviour - freeze after loading vesamenu.c32. So, to some extent,
I can confirm that nothing has been changed :) Of course, pxelinux.0,
pxelinux.cfg/default and vesamenu.c32 have different md5sums.


regards
   Mario
-- 
The social dynamics of the net are a direct consequence of the fact that
nobody has yet developed a Remote Strangulation Protocol.  -- Larry Wall


signature.asc
Description: Digital signature

Bug#570273: debian-installer: netboot stops after loading pxelinux.cfg/default