Quoting Alon Horn (sal...@t2.technion.ac.il):
Package: debian-installer
Severity: normal
hi,
using the mini.iso to install sid, choosing expert install (KDE), when
getting to the install grub part, after refusing MBR, the examples for
(hdx,y) reflect grub legacy behavior.
following
Package: debian-installer
Version: (?) cdimage 04-Oct-2010
cdimage: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/ (CD1)
Excuse for my bad English.
The installation freeze at APT Configuration - Cdset 25%.
The system ask if I wanto to check other CD/DVD. I answer No.
Package: installation-reports
Abstract: debian-netinst/grub detects others systems but do not insert it in
grub.cfg
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
Date: 2010/09/30 11:20
Machine: PC
Hi,
it is documented on debian-installer/manual/doc/translations_po.txt
on debian-installer/manual$
./scripts/merge_xml en
./scripts/update_pot
./scripts/update_po pt
(i believe the last command must be done manually for each language)
Ter, 2010-10-05 às 05:51 +0200, Christian PERRIER
Package: installation-reports
Abstract: debian-netinst: /proc/bus/usb/devices file not found
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso
Date: 2010/09/30 11:20
Machine: PC
Processor: Intel(R)
On Mon, Oct 04, 2010 at 06:45:22AM +0200, Christian PERRIER wrote:
Quoting maximilian attems (m...@stro.at):
In squeeze it is no longer necessary or useful to generate or
to consult kernel-img.conf.
Thanks to the new bootloader policy, see:
The attached file is a patch for this bug.
--- a/installer/build/boot/x86/f6.txt 2010-10-05 20:52:51.0 +1100
+++ b/installer/build/boot/x86/f6.txt 2010-10-05 20:53:56.0 +1100
@@ -10,7 +10,7 @@ Some IBM ThinkPads
Protect I/O port regions
The code has changed slighly in svn. This patch seem to match the
previous proposal, updated and made relative to the current svn.
Index: i386.sh
===
--- i386.sh (revision 63405)
+++ i386.sh (working copy)
@@ -39,7 +39,7 @@
Package: base-installer
Version: 1.110
Severity: grave
User: debian-...@lists.debian.org
UserTags: debian-edu
I discovered this using the Debian Edu DVD and installing on a i686
kvm guest on a i686 Lenny host. The problem is that installation now
is successfull, but the installed machine
attached a screenshot.attachment: grub.png
Quoting Christian PERRIER bubu...@debian.org:
- Were you using a localized install?
no, english
- What mini.iso are you talking about? Daily build from
http://www.debian.org/devel/debian-installer?
yes, following the other images link, inside the netboot dir.
image downloaded 17.9, 8pm.
-
Package: os-prober
Version: 1.39
Severity: important
An upgrade (os-prober 1.35 - 1.39) corrupted 3.3 TB of data on our SAN.
I was upgrading the host space1 and the data corruption occurred on space2. An
install script of os-prober tried mounting as read-only a SAN volume which was
already
[Petter Reinholdtsen]
The code has changed slighly in svn. This patch seem to match the
previous proposal, updated and made relative to the current svn.
Except that it was not against the current svn. I was looking at the
wrong version. Ignore this patch and look at the one from Christian
This is the /proc/cpuinfo in the i686 kvm guest:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 2
model name : QEMU Virtual CPU version 0.10.0
stepping: 3
cpu MHz : 2999.338
cache size : 2048 KB
fdiv_bug: no
hlt_bug
Oops, attaching the missing aptitiude log and syslog of space1.
Original Text (with line-wrapping):
~~~
An upgrade (os-prober 1.35 - 1.39) corrupted 3.3 TB of data on our SAN.
I was upgrading the host space1 and the data corruption occurred on
space2. An
On Tue, Oct 5, 2010 at 18:28:43 +0200, Jürgen Leibner wrote:
I installed today the same way as Petter Reinholdtsen does, but on
virtualbox-ose version 3.2.8-dfsg-2.
uname -a on the host system gives:
Linux laptop-jl 2.6.32-5-amd64 #1 SMP Fri Sep 17 21:50:19 UTC 2010
x86_64 GNU/Linux
reassign 599162 usbview
thanks
Comments/Problems:
I install and run usbview:
apt-get install usbview
usbview
The usbview program claims that the file /proc/bus/usb/devices is not present.
Afer a look at that error over internet I add the following line in
/etc/fstab :
Processing commands for cont...@bugs.debian.org:
reassign 599162 usbview
Bug #599162 [installation-reports] installation-reports: /proc/bus/usb/devices
file not found
Bug reassigned from package 'installation-reports' to 'usbview'.
thanks
Stopping processing here.
Please contact me if you
Quoting Aleksandr Levchuk (alevc...@cs.ucr.edu):
Package: os-prober
Version: 1.39
Severity: important
An upgrade (os-prober 1.35 - 1.39) corrupted 3.3 TB of data on our SAN.
Sigh. From what I've witnessed over the years, os-prober has always
been designed as a component of Debian
Quoting Christian PERRIER (bubu...@debian.org):
Quoting Aleksandr Levchuk (alevc...@cs.ucr.edu):
Package: os-prober
Version: 1.39
Severity: important
An upgrade (os-prober 1.35 - 1.39) corrupted 3.3 TB of data on our SAN.
Sigh. From what I've witnessed over the years, os-prober
On Tue, Oct 05, 2010 at 07:08:03PM +0200, Jürgen Leibner wrote:
If there would be an addititional menu which gives one the possibility to
choose such a mixed system then I would be able to choose a mixed system.
But in this case, there is an Install, suggesting a 32-bit overall system
and on
On Tue, Oct 05, 2010 at 06:27:55PM +0200, Petter Reinholdtsen wrote:
This is the /proc/cpuinfo in the i686 kvm guest:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 2
model name : QEMU Virtual CPU version 0.10.0
stepping: 3
cpu MHz
Quoting Raseni (rasen...@gmail.com):
Package: debian-installer
Version: (?) cdimage 04-Oct-2010
cdimage: http://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/ (CD1)
Excuse for my bad English.
The installation freeze at APT Configuration - Cdset 25%.
The system ask
Package: debian-installer
Severity: normal
Tags: d-i
d-i lacks /lib/modules/2.6.32-5-amd64/kernel/drivers/net/phy/broadcom.ko, so I
cannot use network during the installation. The module is part of linux-
image-2.6.32-5-amd64, so I copied the file from another machine in the running
installer,
On Tue, Oct 05, 2010 at 08:42:18PM +0200, Jürgen Leibner wrote:
On Tuesday 05 October 2010 19:41 Lennart Sorensen wrote:
...
Most people would prefer the 64bit kernel with 32bit userspace. I
think there is an option in expert mode to select your kernel
yourself from a list, but unless
Hi!
Comparing Debian with other distros, using 2 GB of RAM and a disk with 1.00 TB,
we have this (using the default partition layout of the installers, full disk):
Debian:
7.0 GB /
6.2 GB swap
1.1 TB /home
Mandriva One 2010 Spring:
12 GB /
3.8 GB swap
1008 GB /home
Fedora 13:
500 MB /boot
Hello,
On Tue, Oct 5, 2010 at 2:53 PM, Klaus Umbach
klaus-bugs.debian@uxix.de wrote:
Package: debian-installer
Severity: normal
Tags: d-i
d-i lacks /lib/modules/2.6.32-5-amd64/kernel/drivers/net/phy/broadcom.ko, so I
cannot use network during the installation. The module is part of
Hello,
On Tue, Oct 5, 2010 at 12:52 PM, Christian PERRIER bubu...@debian.org wrote:
Were you using a language different from English during your install?
This has been fixed in last apt-setup upload but not available in
weekly builds yet.
--
Otavio Salvador O.S. Systems
On Tue, Oct 05, 2010 at 10:00:07AM +0200, Pierre Saramito wrote:
Package: installation-reports
...
Initial boot: [O]
Detect network card:[O]
Configure network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard
reassign 599115 grub-installer
thanks
sal...@t2.technion.ac.il, le Tue 05 Oct 2010 17:39:54 +0200, a écrit :
attached a screenshot.
Indeed, that comes from grub-installer, reassigning.
Samuel
attachment: grub.png
Processing commands for cont...@bugs.debian.org:
reassign 599115 grub-installer
Bug #599115 [debian-installer] debian-installer: grub's target examples still
reflect grub-legacy's behavior
Bug reassigned from package 'debian-installer' to 'grub-installer'.
thanks
Stopping processing here.
affects 599200 qemu-kvm
thanks
[Lennart Sorensen]
The 'lm' flag means this system has 64bit support. If in fact it
doesn't, then the VM is broken. The installer did the right thing
based on the CPU feature flags.
Assuming this is true, I suggest two things are done to make sure d-i
work on
Processing commands for cont...@bugs.debian.org:
affects 599200 qemu-kvm
Bug #599200 [base-installer] base-installer: Install amd64 kernel on i686 kvm
guest - and fail to boot
Added indication that 599200 affects qemu-kvm
thanks
Stopping processing here.
Please contact me if you need
Holger Wansing, le Mon 04 Oct 2010 21:55:17 +0200, a écrit :
And: at the beginning of that file (../en/install-methods/boot-usb-files.xml)
I read several times about Linux, even in the kfreebsd manual.
Could you check, if this is correct?
It is not, I've already asked BSD people to check what
On Tue, Oct 05, 2010 at 11:07:15PM +0200, Petter Reinholdtsen wrote:
affects 599200 qemu-kvm
thanks
[Lennart Sorensen]
The 'lm' flag means this system has 64bit support. If in fact it
doesn't, then the VM is broken. The installer did the right thing
based on the CPU feature flags.
[Lennart Sorensen]
I suspect if you run kvm with the -cpu option you can specify what
you desire. I believe the default is to simply match whatever the
host has, so if the host has a 64bit cpu, then the guest will too.
Well, the host is using a 32-bit kernel too, so 64-bit kvm with
hardware
Hello,
Anton Zinoviev, le Tue 14 Sep 2010 13:24:59 +0300, a écrit :
On Tue, Sep 14, 2010 at 12:18:44PM +0200, Julien Cristau wrote:
Do you think it will be useful if keyboard-configuration provides a
/etc/foo.d directory where the interested packages (console-setup, X)
can install
Hello:
I just committed revision 64907, migrating d-i's manual Spanish translation
to gettext.
Moving to other issue, some builds fail for every lang lately, I guess
it has do to with changes in the docs and that you know it.
Just felt I should mention.
Sorry if I raised an eyebrow
On Wed, Oct 06, 2010 at 12:01:45AM +0200, Petter Reinholdtsen wrote:
[Lennart Sorensen]
I suspect if you run kvm with the -cpu option you can specify what
you desire. I believe the default is to simply match whatever the
host has, so if the host has a 64bit cpu, then the guest will too.
[Lennart Sorensen]
Well try starting the kvm with '-cpu qemu32'. That should provide
the feature flags of a nice 32bit x86.
I tried this by adding
cpu match='exact'
modelqemu32/model
/cpu
to the libvirtm XML file for the virtual machine, which caused '-cpu
qemu32' to be part of the
On Tue, 2010-10-05 at 23:07 +0200, Petter Reinholdtsen wrote:
affects 599200 qemu-kvm
thanks
[Lennart Sorensen]
The 'lm' flag means this system has 64bit support. If in fact it
doesn't, then the VM is broken. The installer did the right thing
based on the CPU feature flags.
41 matches
Mail list logo
