Processed: Re: Bug#512679: initramfs-tools: 'more' pager is broken in initramfs shell
Processing commands for cont...@bugs.debian.org: > reassign 512679 busybox Bug#512679: initramfs-tools: 'more' pager is broken in initramfs shell Bug reassigned from package `initramfs-tools' to `busybox'. > stop 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
Re: Pre-bug-raising questions
On Mon, Jan 19, 2009 at 8:36 PM, Ian Campbell wrote: > On Mon, 2009-01-19 at 19:46 +, Mike Grice wrote: >> On Mon, Jan 19, 2009 at 4:57 PM, Ian Campbell wrote: >> > On Mon, 2009-01-19 at 16:43 +, Mike Grice wrote: >> >> 2009/1/19 Mike Grice : >> >> > On Mon, Jan 19, 2009 at 4:10 PM, Ian Campbell >> >> > wrote: >> >> >> On Mon, 2009-01-19 at 14:12 +, Mike Grice wrote: >> >> >>> >> >> >>> Select a language: English >> >> >>> Choose Language: default >> >> >>> Detect Network Hardware: >> >> >>> "No Ethernet card was detected. If you know the name of the driver >> >> >>> │ >> >> >>> │ needed by your Ethernet card, you can select it from the list." >> >> >> >> >> >> Do you have something akin to /sys/bus/sunv/devices/blah? With modalias >> >> >> entries here and in the module the installer should be able to make the >> >> >> connection between one and the other. For example for Xen virtual >> >> >> devices we have: >> >> >>di32:~# cat /sys/bus/xen/devices/vif-0/modalias >> >> >>xen:vif >> >> >>di32:~# modinfo xen-netfront >> >> >>filename: >> >> >> /lib/modules/2.6.26-1-686-bigmem/kernel/drivers/net/xen-netfront.ko >> >> >>alias: xennet >> >> >>alias: xen:vif >> >> >>license:GPL >> >> >>description:Xen virtual network device frontend >> >> >>depends: >> >> >>vermagic: 2.6.26-1-686-bigmem SMP mod_unload modversions >> >> >>686 >> >> >> >> >> >> So the xen:vif modalias ties into the alias on the module. > >> The main concern I have is the autodetection of the hardware... I >> don't know how the installer works enough to see what bit isn't >> working there, so I'll have to do some digging :-( > > That's what the module alias stuff I describe above is all about, if > this is correct then the installer should Do The Right Thing. Having had a hunt around the net, and looking at how Ubuntu deal with things, they seem to have a patched udev and then some udev magic to pick these devices up (via VIO). Apparently they are on a list of things that are 'not modalias compatible' so need special treatment (though I lost that page on my hunt). There is some stuff exposed through 'vio' though. hostname:~# modinfo sunvdc filename: /lib/modules/2.6.26-1-sparc64-smp/kernel/drivers/block/sunvdc.ko version:1.0 license:GPL description:Sun LDOM virtual disk client driver author: David S. Miller (da...@davemloft.net) srcversion: DA09013600C87C20DCD182A alias: vio:Tvdc-portS* depends: vermagic: 2.6.26-1-sparc64-smp SMP mod_unload modversions hostname:~# modinfo sunvnet filename: /lib/modules/2.6.26-1-sparc64-smp/kernel/drivers/net/sunvnet.ko version:1.0 license:GPL description:Sun LDOM virtual network driver author: David S. Miller (da...@davemloft.net) srcversion: FCB2B4E588A5F07F25D52B5 alias: vio:Tvnet-portS* depends: vermagic: 2.6.26-1-sparc64-smp SMP mod_unload modversions (I don't understand the vio stuff either...) Using this VIO and udev they load a special udev rules file (see attached) that seems to pick these things up. Dont know how that would work in the installer though. I've hit another bug (to do with disk labels, #512740) which I've raised (its fixed in Ubuntu so I provided a patch) but we are getting there. I can work around most of these things now via Preseeding and some early_command / late_command trickery. Of course I'll help any way I can, I'm not a package maintainer or DD (though its something I've had on my todo list for a long time) so if its just some legwork I will see what I can do. Cheers Mike 90-modprobe.rules Description: Binary data
Processing of debian-installer_20090123_amd64.changes
debian-installer_20090123_amd64.changes uploaded successfully to localhost along with the files: debian-installer_20090123.dsc debian-installer_20090123.tar.gz debian-installer_20090123_amd64.deb debian-installer-images_20090123_amd64.tar.gz Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
debian-installer_20090123_amd64.changes ACCEPTED
Accepted: debian-installer-images_20090123_amd64.tar.gz byhand debian-installer_20090123.dsc to pool/main/d/debian-installer/debian-installer_20090123.dsc debian-installer_20090123.tar.gz to pool/main/d/debian-installer/debian-installer_20090123.tar.gz debian-installer_20090123_amd64.deb to pool/main/d/debian-installer/debian-installer_20090123_amd64.deb Changes: debian-installer (20090123) unstable; urgency=low . [ Frans Pop ] * Add build dependency on docbook-xml, needed for D-I internals. Override entries for your package: debian-installer_20090123.dsc - source devel debian-installer_20090123_amd64.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
cdebconf 0.138lenny2 MIGRATED to testing
FYI: The status of the cdebconf source package in Debian's testing distribution has changed. Previous version: 0.138lenny1 Current version: 0.138lenny2 -- This email is automatically generated; the Debian Release Team is responsible. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512794: installation-reports
Package: installation-reports Boot method: CD, expert mode no gui. Image version: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-kde-CD-1.iso (weekly-build image = first week of January, 2009) Date: Machine: HP Compaq dx2450 Microtower PC Processor: AMD Athlon 1640B Memory: 2GB Partitions: df -Tl: S.ficherosTipo Bloques de 1K UsadoDispon Uso% Montado en /dev/sda1 ext396124904445672 90796280 1% / tmpfstmpfs 972592 0972592 0% /lib/init/rw udev tmpfs 1024096 10144 1% /dev tmpfstmpfs 972592 0972592 0% /dev/shm /dev/sda7 ext3 180811976 27987228 143639988 17% /home /dev/sda8 ext3 9606084152712 8965400 2% /tmp /dev/sda6 ext396124904 2954204 88287748 4% /usr /dev/sda5 ext396124904 1427328 89814624 2% /var Output of lspci -knn: 00:00.0 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03ea] (rev a1) 00:01.0 ISA bridge [0601]: nVidia Corporation MCP61 LPC Bridge [10de:03e0] (rev a2) 00:01.1 SMBus [0c05]: nVidia Corporation MCP61 SMBus [10de:03eb] (rev a2) Kernel driver in use: nForce2_smbus Kernel modules: i2c-nforce2 00:01.2 RAM memory [0500]: nVidia Corporation MCP61 Memory Controller [10de:03f5] (rev a2) 00:02.0 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f1] (rev a3) Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:02.1 USB Controller [0c03]: nVidia Corporation MCP61 USB Controller [10de:03f2] (rev a3) Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:04.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI bridge [10de:03f3] (rev a1) 00:05.0 Audio device [0403]: nVidia Corporation MCP61 High Definition Audio [10de:03f0] (rev a2) Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel 00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2) Kernel driver in use: forcedeth Kernel modules: forcedeth 00:08.0 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller [10de:03f6] (rev a2) Kernel driver in use: sata_nv Kernel modules: sata_nv 00:08.1 IDE interface [0101]: nVidia Corporation MCP61 SATA Controller [10de:03f6] (rev a2) Kernel driver in use: sata_nv Kernel modules: sata_nv 00:09.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e8] (rev a2) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:0b.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e9] (rev a2) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:0c.0 PCI bridge [0604]: nVidia Corporation MCP61 PCI Express bridge [10de:03e9] (rev a2) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:0d.0 VGA compatible controller [0300]: nVidia Corporation GeForce 6150SE nForce 430 [10de:03d0] (rev a2) Kernel driver in use: nvidia Kernel modules: nvidiafb, nvidia 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control [1022:1103] Kernel driver in use: k8temp Kernel modules: k8temp 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: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: I've had to install nVidia binary kernel module (173.14.09+3) after installation and fine tune monitor, an HP w2228h, 1680x1050 screen size. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509855: marked as done ("flat" mirror type)
Your message dated Fri, 23 Jan 2009 23:43:03 +0100
with message-id <20090123224303.ga32...@thorin>
and subject line Re: Bug#509855: "flat" mirror type
has caused the Debian Bug report #509855,
regarding "flat" mirror type
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
509855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.10
Severity: wishlist
Tags: patch
This patch implements the "flat" mirror type, a trivial archive made by
running dpkg-scanpackages on a single directory.
This is very useful when bootstrapping new ports, at the stage in which a
proper archive is not setup and one wants to build a base system out of
a set of hand-built debs.
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.18-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debootstrap depends on:
ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii wget1.11.4-2 retrieves files from the web
debootstrap recommends no packages.
debootstrap suggests no packages.
-- no debconf information
diff -ur debootstrap-1.0.10/functions debootstrap-1.0.10.new/functions
--- debootstrap-1.0.10/functions 2008-12-27 00:50:04.810414076 +
+++ debootstrap-1.0.10.new/functions 2008-12-27 00:50:24.834985012 +
@@ -226,6 +226,10 @@
DOWNLOAD_INDICES=download_main_indices
DOWNLOAD_DEBS=download_main
;;
+ flat)
+ DOWNLOAD_INDICES=download_flat_indices
+ DOWNLOAD_DEBS=download_main
+ ;;
*)
error 1 BADMIRROR "unknown mirror style"
;;
@@ -674,6 +678,28 @@
progress 100 100 DOWNMAINPKGS "Downloading Packages file"
}
+download_flat_indices () {
+ local m1="${MIRRORS%% *}"
+ progress 0 100 DOWNMAINPKGS "Downloading Packages file"
+ progress_next 100
+ COMPONENTS=main
+ export COMPONENTS
+ for m in $MIRRORS; do
+ for c in $COMPONENTS; do
+ local m_path="Packages"
+ local path="dists/$SUITE/$c/binary-$ARCH/Packages"
+ local pkgdest="$TARGET/$($DLDEST pkg "$SUITE" "$c" "$ARCH" "$m" "$path")"
+ if [ -x /bin/gunzip ] && get "$m/${m_path}.gz" "${pkgdest}.gz"; then
+ rm -f "$pkgdest"
+ gunzip "$pkgdest.gz"
+ elif get "$m/$m_path" "$pkgdest"; then
+ true
+ fi
+ done
+ done
+ progress 100 100 DOWNMAINPKGS "Downloading Packages file"
+}
+
download_main () {
local m1="${MIRRORS%% *}"
--- End Message ---
--- Begin Message ---
On Sat, Dec 27, 2008 at 12:57:51AM +, Robert Millan wrote:
> Package: debootstrap
> Version: 1.0.10
> Severity: wishlist
> Tags: patch
>
> This patch implements the "flat" mirror type, a trivial archive made by
> running dpkg-scanpackages on a single directory.
>
> This is very useful when bootstrapping new ports, at the stage in which a
> proper archive is not setup and one wants to build a base system out of
> a set of hand-built debs.
I realized that creating a "proper" mirror structure that debootstrap will
process is not such a big deal, even if you have to do it by hand. I think
my patch is not really that useful.
--
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."
--- End Message ---
initrd woes
Greetings,
I hope this is the correct place to post my question. Please let me know
if there is a more appropriate place, as I have not posted to debian
before and wasn't sure what list to use. I am attempting to boot over
the network (Debian Lenny Linux version 2.6.26), using nfs or the root
directory. The kernel boots up fine, but then fails during initrd with
the following message:
run-init: /sbin/init: No such file or directory
I have stuck some debugging statements in my initrd, and have determined
the following:
This is the exact command that is failing:
exec run-init ${rootmnt} ${init} "$@" <${rootmnt}/dev/console
>${rootmnt}/dev/console
which translates to:
exec run-init /root /sbin/init /root/dev/console
I stuck in some echo statements and verified that /root/sbin/init and
/root/dev/console both exist, and if I change the options of exec
run-init I can get it to complain about incorrect syntax, so it seems to
be able to find the command okay. Furthermore, if I change the above
command to
exec run-init ${rootmnt} ${rootmnt}${init} "$@" <${rootmnt}/dev/console
>${rootmnt}/dev/console
it also fails, stating that /root/sbin/init does not exist, however on
the line just before I can print out ls -l /root/sbin/init and I get this:
-rwxr-xr-x 1 00 37384 Aug 12 14:20 /root/sbin/init
So I have no idea why I am getting the message that init does not exist.
Can anyone give me any advice on how to proceed with troubleshooting?
thanks,
maria
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
console-setup fetching data from xkb-data?
Hello, Is there a reason for console-data to contain a duplicate of the xkb-data content? Couldn't it just build-depend on xkb-data and fetch data from /usr/share/X11/xkb? That way, updating it would just need a binNMU. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: console-setup fetching data from xkb-data?
Samuel Thibault, le Sat 24 Jan 2009 01:16:34 +0100, a écrit : > Is there a reason for console-data to contain a duplicate of the > xkb-data content? Ah, I've found http://lists.debian.org/debian-boot/2007/04/msg00925.html bummer. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: console-setup fetching data from xkb-data?
Samuel Thibault, le Sat 24 Jan 2009 02:17:50 +0100, a écrit : > Samuel Thibault, le Sat 24 Jan 2009 01:16:34 +0100, a écrit : > > Is there a reason for console-data to contain a duplicate of the > > xkb-data content? > > Ah, I've found > http://lists.debian.org/debian-boot/2007/04/msg00925.html > bummer. Mmm, that being said, really comparing the files only shows minor differences in the ro layout which should probably be merged upstream, so I guess my question now holds nowadays. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Console-Setup switch
Change in the wiki, by Samuel: >* Include kbd-udeb to the initrd images > - * (to be detailed) get rid of console-data (From Anton: "The most > difficult part inside console-setup is to make the model/layout strings > translatable. The X upstream provides translations in a xml file but I have > no idea how to use them.) > + * (to be detailed) get rid of console-data (From Anton: "The most > difficult part inside console-setup is to make the model/layout strings > translatable. The X upstream provides translations in a xml file but I have > no idea how to use them. ST: translations are not in the xml file, they are > in mere .po files in po/ of xkeyboard-config (or .mo in the .deb), ideally we > could just give their path to po2debconf) > + * parse base.xml to generate locale/country -> layout/variant default > choice (ask ST, some bugs are being fixed in xkeyboard-config). > + * parse base.xml to get e.g; compose:caps) default_compose='Caps Lock';; > (ask ST) (translations are also available in the po/ directory of > xkeyboard-config) >* (optional?) use the Ubuntu way to set the keymap? If I understand well, the strings used by console-setup for keymap names are indeed used from an XML file...that's built by xkeyboard-config, where these strings are translatable through PO files. If that's right, it means that a main blocker for the swith to console-setup does not really exist and we could re-consider this more carefully. Am I right? (Samuel, CC'ing you to get attention, only. I know you're subscribed to -boot) signature.asc Description: Digital signature
