Re: r56925 - in trunk/win32-loader: debian l10n/po
Quoting Frans Pop (elen...@planet.nl): > On Monday 22 December 2008, Christian Perrier wrote: > > Author: bubulle > > > - * Romanian (ro.po) by Eddy Petri?or > > + * Romanian (ro.po) by Eddy Petri?or > > This is really getting ridiculous... Thanks you for kindly pointing it. I'll correct the error. I now try to avoid using xemacs for changelog editing but, as it is the default editor on my system, some occurrences still slip through. (and, to answer very probable followups, I tried to switch to regular emacs twice during the last months but the weird handling of emacsclient and the lack of "-unmapped" made me switch back to my good old editor) -- signature.asc Description: Digital signature
Bug#509400: installation-reports: optical drive not detected (Lite-On 20X LightScribe)
* Christian Perrier (bubu...@debian.org) wrote: |> Quoting Jim McCloskey (mccl...@ucsc.edu): |> > Package: installation-reports |> > |> > Boot method: CD |> > Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso |> > |> > Date: Dec 20th--21st |> This is probably the following problem, listed in the errata file: |> |> Due to a pata_marwell module not begin properly autoloaded |> on i386 and amd64 media, |> peripherals driven by Marvell disk controllers are not detected. If |> IDE is used in legacy mode with these controllers, switch to |> console 2 when the installer boots (Alt+F2) and |> run 'modprobe -r ahci; modprobe pata_marvel; modprobe ahci' before |> continuing. |> |> |> Could you do two tests ? |> |> 1) try with the same image, then follow the above instructions (switch |> to VT2 when the installer boots and run the magic commands) and |> check if the CD is detected later on. This did indeed fix the problem. Thank you. |> 2) download the *netboot* image of the daily builds. I really mean |> *netboot*. Not netinst. This is a very small ISO image (8MB). With |> that image, which has the latest kernel package from unstable, that |> problem should not happen I will try this when the current install finishes (I want to re-do the partition scheme in any case). Thanks very much to all who helped (the installation has now completed without problem), Jim -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509238: panic backtrace
Quoting The Eclectic One (eclec...@sdf.lonestar.org): > First thought: race condition (the panic message contained a backtrace > of different threads), so then I tried multiple times with only one > change at at time: expert mode, regular mode, ethdetect -x, vga=771, > vga normal. It turns out that the culprit was the vga option. With > vga=771, I get no crash/panic in either expert or regular mode, with So, in short, in regular mode, it crashes (always at the same place) but in vga=771 mode, it doesn't, right? signature.asc Description: Digital signature
partman (etch)
Hi,
I'm trying to preseed a machine and am getting stuck on the partitioning.
This email is to ask people to search their memory to see if they recall
a similar problem.
The preseed files I am using work perfectly well with another machine,
that has a smaller hard disk (20Gb vs 40Gb).
I can also preseed the problematic machine with a different preseed
file, that has slightly different partitioning.
What happens is the following:
clean the hard disk with
dd if=/dev/zero of=/dev/hda bs=512
(in the installer)
netboot the installer (version: 20070308etch2)
partman creates /dev/hda1 and /dev/hda5,
The latter partition is set up as an LVM PV.
(fdisk -l & pvscan confirm this)
it then stops and complains that there is no swap space set up.
I tried an alternative procedure and got a different result.
deleted the partitions in partition with e.g. knoppix disk.
and empty msdos partition table remains.
netboot the installer (version: 20070308etch2)
partman creates /dev/hda1 and /dev/hda5,
The latter partition is set up as an LVM PV.
(fdisk -l & pvscan confirm this)
It then stops with a red-screen error, complaining that the
"volume group name is already in use".
In both cases the VG name is set to the hostname, as expected.
The mystifying thing is that it works with a very similar preseed.
The partitioning preseeding commands I am using are below.
d-i partman-auto/disk string /dev/discs/disc0/disc
d-i partman-auto/methodstring lvm
d-i partman-auto/purge_lvm_from_device boolean true
d-i partman-auto-lvm/no_boot boolean true
d-i partman-lvm/confirmboolean true
d-i partman/confirm_write_new_labelboolean true
d-i partman/choose_partition select Finish partitioning and write
changes to disk
d-i partman/confirmboolean true
d-i partman-auto/expert_recipe string ATNF_laptop : \
512 2000 1024 ext3 \
$primary{ }\
$bootable{ } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext3 } \
label{ root } \
mountpoint{ / }\
. \
512 2000 300% linux-swap \
$lvmok{ } \
method{ swap } \
format{ } \
. \
5120 1000 5120 ext3\
$lvmok{ } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext3 } \
mountpoint{ /usr } \
. \
5120 1000 5120 ext3\
$lvmok{ } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext3 } \
mountpoint{ /usr/local } \
. \
2048 1000 2048 ext3\
$lvmok{ } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext3 } \
mountpoint{ /var } \
. \
2048 1000 2048 ext3\
$lvmok{ } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext3 } \
mountpoint{ /tmp } \
. \
1024 1000 2048 ext3\
$lvmok{ } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext3 } \
mountpoint{ /local } \
. \
256 500 10240 ext3\
$lvmok{ } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext3 } \
mountpoint{ /home }\
.
10240 500 10 ext3 \
$lvmok{ } \
method{ format } \
format{ } \
use_filesystem{ } \
filesystem{ ext3 } \
mountpoint{ /data }\
.
-
The differences from the partitioning that works are
the /usr/local and the /home chunks,
and the first field of the /data chunk (10240 vs 1024).
Thoughts?
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: installation-report: sparc on Sun Fire V880 fails due to unaligned access
Processing commands for cont...@bugs.debian.org: > reassign 509202 installation-reports Bug#509202: installation-report: sparc on Sun Fire V880 fails due to unaligned access Bug reassigned from package `installation-report' to `installation-reports'. > severity 509202 normal Bug#509202: installation-report: sparc on Sun Fire V880 fails due to unaligned access Severity set to `normal' from `grave' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509238: panic backtrace
Quoting Christian Perrier >> Ok, tried a few more times. I usually get the same kernel panic screen, >Did you try in expert mode, ie choosing it from the "Advanced options" >in the boot menu. Yes, I tried expert as well as regular. >In expert mode, when you reach the HW detection step, you'll get a >question about PCMCIA options. They're not necessarily relevant but >checking if the crash happens before or after it would help No question about PCMCIA before getting to the network detection screen/status bar. > ... >Some drivers in 2.6.18 provided firmware blobs that have been >extracted from the source and are now provided as separate udebs: >r...@mykerinos:~> apt-cache search firmware 2100 >firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915 That explains the missing firmware. >If that firmware is needed for ipw2100, you'll be prompted about >thisbut you're not, which means the crash happens before..:-) Correct. >> Anything else I can do? More tests? >Before the network devices screen (for instance, when prompted for >language), could you switch to VT2 (Alt+F2) and, from there edit >/bin/ethdetect.sh >Add "-x" to the first line: >#!/bin/sh -x >Then go back to VT1, continue to the step where the crash happens and >sitch to VT4 before it happens. As ethdetect.sh will be in debug mode, >we'll see all its output and could narrow down the exact line where >the crash happens. Ok, did that and also vga=771. I was hoping to get a smaller font to see more of the backtrace. This is what I got: [ output of ethdetect -x - lsifaces (3 lines) sed (4), grep (4) and sed (3) ] Dec 22 15:42:48 main-menu[1328]: (process:9628) + ip link set eth0 up Dec 22 15:42:48 main-menu[1328]: (process:9628) + ip link set eth0 down Dec 22 15:42:48 main-menu[1328]: (process:9628) + ip link set eth1 up Dec 22 15:42:48 main-menu[1328]: (process:9628) + ip link set eth1 down Dec 22 15:42:48 main-menu[1328]: (process:9628) + check-missing-firmware Dec 22 15:42:48 main-menu[1328]: (process:9628) + sysfs-update-devnames Dec 22 15:42:48 main-menu[1328]: (process:9628) + cleanup Dec 22 15:42:48 main-menu[1328]: (process:9628) + rm -f /tmp/devnames-static.txt Dec 22 15:42:48 main-menu[1328]: DEBUG: resolver (libslang2-udeb): package doesn't exist (ignored) It didn't crash! After that I proceeded to console 1 and did see the screen explaining that I needed the missing firmware - ipw2100-1.3.fw. As I had thought, even with the missing firmware, the culprit wasn't the wireless device. First thought: race condition (the panic message contained a backtrace of different threads), so then I tried multiple times with only one change at at time: expert mode, regular mode, ethdetect -x, vga=771, vga normal. It turns out that the culprit was the vga option. With vga=771, I get no crash/panic in either expert or regular mode, with sh -x in ethdetect or not. It might still be a race condition but if so it seems to be triggered by something related to the display. Very strange. The display works fine (with a big font) in normal mode. In 771 mode, the font is smaller and the curses windows sharper. Even though I now have a work-around, I'm willing to keep debugging if if would be useful. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: r56925 - in trunk/win32-loader: debian l10n/po
On Monday 22 December 2008, Christian Perrier wrote: > Author: bubulle > - * Romanian (ro.po) by Eddy Petrișor > + * Romanian (ro.po) by Eddy Petri?or This is really getting ridiculous... signature.asc Description: This is a digitally signed message part.
Bug#268495: renaming a partition on ia64 to no name makes partman hang
tags 268495 patch
user ubuntu-de...@lists.ubuntu.com
usertags 268495 ubuntu-patch jaunty
thanks
On Thu, Oct 28, 2004 at 08:28:20PM +0100, Colin Watson wrote:
> It's still possible to hang parted_server by entering an empty name,
> which is a separate problem: the implementation of the SET_NAME command
> uses fscanf(" %a[^\n]"), which never returns if you only send
> whitespace.
Here's a patch which I think fixes this. I've only tested this in a test
harness, not yet in a full installation, but I think it's right.
--
Colin Watson [cjwat...@ubuntu.com]
Index: parted_server.c
===
--- parted_server.c (revision 56922)
+++ parted_server.c (working copy)
@@ -118,7 +118,38 @@
the function `scanf' */
#define iscanf(...) fscanf(infifo,__VA_ARGS__)
+/* Read the remainder of this line from the input FIFO, skipping leading
+ * whitespace. Sets *str to NULL if there was no data left in the FIFO (as
+ * opposed to merely optional leading whitespace followed by a newline,
+ * indicating an empty argument following the whitespace; in that case, set
+ * *str to the empty string). Caller is expected to free *str.
+ */
void
+iscan_line(char **str)
+{
+int c;
+
+*str = NULL;
+
+c = fgetc(infifo);
+if (c == EOF)
+return;
+while (c != EOF && c != '\n') {
+if (isspace((unsigned char) c))
+c = fgetc(infifo);
+else {
+ungetc(c, infifo);
+break;
+}
+}
+
+if (c == EOF || c == '\n')
+*str = calloc(1, 1);
+else
+iscanf("%a[^\n]", str);
+}
+
+void
synchronise_with_client()
{
char *str;
@@ -287,7 +318,8 @@
oprintf("\n");
if (timer_was_started)
start_timer();
-if (1 != iscanf(" %a[^\n]", &str))
+iscan_line(&str);
+if (!str)
critical_error("No data in infifo.");
if (!strcmp(str, "unhandled")) {
log("User canceled exception handler");
@@ -1471,7 +1503,8 @@
for (flag = first; flag <= last; flag++)
states[flag - first] = false;
while (1) {
-if (1 != iscanf(" %a[^\n]", &str))
+iscan_line(&str);
+if (!str)
critical_error("No data in infifo!");
if (!strcmp(str, "NO_MORE"))
break;
@@ -1530,7 +1563,8 @@
if (part == NULL || !ped_partition_is_active(part))
critical_error("No such active partition: %s", id);
log("Partition found (%s)", id);
-if (1 != iscanf(" %a[^\n]", &name))
+iscan_line(&name);
+if (!name)
critical_error("No data in infifo!");
log("Changing name to %s", name);
open_out();
Processed: Re: Bug#268495: renaming a partition on ia64 to no name makes partman hang
Processing commands for cont...@bugs.debian.org: > tags 268495 patch Bug#268495: renaming a partition on ia64 to no name makes partman hang There were no tags set. Tags added: patch > user ubuntu-de...@lists.ubuntu.com Setting user to ubuntu-de...@lists.ubuntu.com (was cjwat...@ubuntu.com). > usertags 268495 ubuntu-patch jaunty Bug#268495: renaming a partition on ia64 to no name makes partman hang There were no usertags set. Usertags are now: ubuntu-patch jaunty. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509378: should use labels for all partitions in fstab
On Sun, Dec 21, 2008 at 08:15:55PM +, Daniel Pocock wrote: > I believe it would be much safer to use labels for partitions rather > than using the device nodes. Automatically assigning labels is a really, really bad idea. Red Hat tried this and the result was that if you did two Red Hat installations on the same machine then they would get terribly confused on boot as there would be two filesystems with LABEL=root. I spoke to the Anaconda developers about this in person some time back, and they agreed that this was a mistake (I think UUIDs may have been unavailable at the time). Of course you could try to generate universally unique labels, but this is a bit silly when we already have UUIDs. Labels should be reserved for assignment by the system administrator. I absolutely think that we should be using UUIDs by default for devices where there isn't some other stable naming, as Ubuntu does. Note that pretty much every naming system has its downsides: * Traditional device names Fail when devices are enumerated in a different order at boot, or when the kernel changes device naming (e.g. IDE -> libata). * Labels Good when assigned manually by the system administrator, but assigning automatically is fraught with problems. Bit-for-bit filesystem copies will preserve the label, which is fine for backup and restore but can have surprising results. If you have to reconstruct a filesystem during disaster recovery you need to remember to reset the label too (or adjust /etc/fstab). * UUIDs Every filesystem already has one so they can be used automatically. Long and difficult to remember. Bit-for-bit filesystem copies will preserve the UUID, which is fine for backup and restore but can have surprising results. If you have to reconstruct a filesystem during disaster recovery you need to remember to reset the UUID too (or adjust /etc/fstab). * /dev/disk/by-id/ If your disk fails and you have to plug in a new one with a different serial number, you have to remember to adjust /etc/fstab. * /dev/disk/by-path/ If you have to move a disk to a different hardware location, you have to remember to adjust /etc/fstab. IMO the best answer is to use UUIDs by default, but use labels if they are manually set during installation. This way people who don't care can have it just work, and people who care can set labels. In Ubuntu we put a comment above the UUID in /etc/fstab with the original traditional device name for the device in question, which is often a useful aide-memoire. > The only solution I can see is for d-i to enforce the use of labels for > /boot and other non-LVM filesystems. Using the labels with LVM > filesystems would be nice but not essential. I think it's best to use the LVM names for LVM filesystems, since they already form a stable naming scheme. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 509299
Processing commands for cont...@bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26etch1 > tags 509299 pending Bug#509299: installation: Error in Windows-Based Debial Installation There were no tags set. Tags added: pending > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509299: installation: Error in Windows-Based Debial Installation
On Sat, Dec 20, 2008 at 05:06:54PM -0700, Mike Armstrong wrote: > Package: installation > Severity: important > Justification: fails to build from source > > >Windows identifies two partitions (drives) involved in the boot > process - the boot drive and the system drive. The boot drive is > the active partition and the system drive is the drive containing > the Windows kernel (ntoskrnl.exe) >The Windows-Based Install for Debian assumes that the Windows > boot drive and system drive are the same. The install uses > the value in %SystemDrive% to identify where to install the grub > bootloader stuff (g2ldr, g2ldr.mbr, grub.conf) and the \debian > directory. This is AOK for most Windows installations. >However the root drive and system drive can be different (e.g. > I have a small boot partition that will boot either Vista or > XP both of which are located in a separate partition). In this case > the Debian boot-install will not boot. >The temporary fix is to reboot into Windows and copy/move > \g2ldr, \g2ldr.mbr, \grub.conf and \debian into the boot drive. > Then reboot and do the install. >The Debian install should check to see if the file "\ntldr" (for > Windows NT, 2000, server 2000. XP, server 2003) or "\bootmgr" (for > Vista and Server 2008) exists in %SystemDrive%. If neither doesn't > exist then Debian should (a) search for them or (b) ask the user > where the initial boot program is located. Identifying the active > partition may not be sufficient as the user may be using a non- > Windows bootloader that doesn't rely on the active partition to boot. >I hope this helps to improve the install process. Thanks. I know about System Drive vs Boot Drive, but it seems win32-loader's use of it wasn't really consistent. I think I fixed this now. Please could you test latest SVN? If you don't know how to build from source, let me know and I'll provide a binary for you. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
A sua c?pia do windows ? genu?na? - Campanha de Natal - infomail e-Mail4Business
Se n?o visualizar correctamente esta mensagem por favor v? a: http://www.e-mail4business.com/newsletters/20081218/getgk/getgkweb.html Se desejar receber mais informa??o sobre este producto, por favor v? a: http://www.e-mail4business.com/newsletters/20081218/getgk/getgk_form.php Para Encomendar, por favor v? a: http://www.jrpi.pt/component/page,shop.product_details/flypage,shop.flypage/product_id,10/category_id,8/manufacturer_id,0/option,com_virtuemart/Itemid,6/ A sua c?pia do windows ? genu?na? A Microsoft lan?ou recentemente o "Get Genuine Kit para o Windows XP Profissional", este Kit foi concebido para ser usado num PC onde foi pr?-instalada uma vers?o do Windows XP Profissional n?o-genu?no. Aproveite esta iniciativa da Microsoft para legalizar a sua c?pia do Windows XP Profissional. 177.00 ? (*) (*) Campanha de Natal V?lida at? 2008/12/30 Para verificar se a sua c?pia do Windows ? legal, , por favor v? a: http://www.microsoft.com/resources/howtotell/pt/default.mspx Para verificar as ofertas existentes para utilizadores dos Sistemas Operativos Windows XP Genu?nos, por favor v? a: http://www.microsoft.com/genuine/offers/default.aspx?displaylang=pt-pt Get Genuine Kit para o Windows XP Profissional JR PI - Programa??o Inform?tica, Lda. http://www.jrpi.pt ++ Mensagem enviada por e-Mail4Business infomail O seu email: debian-boot@lists.debian.org Para Remover o seu e-Mail, visite o seguinte link: http://infomail.e-mail4business.com/unsubscribe.php?CampaignID=97&Demo=0&EncryptedMemberID=MTEzNzEy&email=debian-b...@lists.debian.org O presente email destina-se ?nica e exclusivamente a informar potenciais clientes e n?o pode ser considerado SPAM. Caso n?o pretenda receber informa??es clique no link "Remova o seu email" existente nesta mensagem. Ao abrigo do decreto lei 67/98 de 26 de Outubro, de regula??o do tratamento automatizado de dados de car?cter pessoal, o utilizador poder? cancelar os mesmos, conforme o disposto nos artigos 10? e 11?. Qualquer solicita??o nesse sentido dever? ser feita para o endere?o do remetente. De salientar que se pretender anular o seu email deve efectuar essa anula??o pelo endere?o de email que se encontra na nossa base de dados, de outra forma ficaremos impossibilitados de o eliminar. Gratos pela aten??o, pedimos desde j? que aceite as nossas desculpas pelo inc?modo causado. ++
Bug#509378: should use labels for all partitions in fstab
Christian Perrier wrote: Quoting Daniel Pocock (dan...@pocock.com.au): Package: debian-installer I believe it would be much safer to use labels for partitions rather than using the device nodes. Reassigning to the correct package. We might even have an already existing bug report about this but I can't check right now. As most wishlist features, this is of course something we can do in the queeze release cycleand, as always, it will not happen by magic: it needs someone to do it, and given the current state of the d-i resourcesdon't expect too muchunless you're ready to do the work..:-) This one could be quite disruptive for some users installing for the first time, so hopefully it will be given consideration. Here are some more specific ideas for implementation, if an approach is agreed on, I might code something: - it needs to be automatic - therefore, the filesystems need to be named automatically, perhaps use the convention HOSTNAME_PATH for top level filesystems, and HOSTNAME_001/002, etc for filesystems with deeper mount points. E.g. if hostname=host1, / would be host1_root, /usr would be host1_usr - if using labels, the filesystem definition window should not allow the user to proceed if the label is missing - as an alternative to the above, use the UUID instead - this is always present, and it doesn't have the length issues - maybe put a comment in /etc/fstab to show where the filesystem was found (device node) during install, particularly important for UUID, e.g.: # /boot was on /dev/sdb1 during install LABEL=myhost_boot /boot ext3 defaults 0 0 or # /boot was on /dev/sdb1 during install UUID=558e4695-e2c8-4e79-93cb-8b89313dce6a /boot ext3 defaults 0 0 - if using pre-formatted filesystems, must check that the label and/or UUID is present before writing fstab, and either instruct the user to label their filesystems manually, or even better, prompt them to enter labels and do it for them - in the case of existing filesystems, an automatic approach should be able to use either UUID or label, if one and not the other is present - must also check that each label and UUID is unique within the host, display an error and refuse to create fstab if not the case -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#502821: Enhances oldsys-preseed patch for the DNS-323
Copying Matt: * Laurie Bradshaw [2008-12-22 09:33]: > I've been playing around with this, and it's not quite working, > functions are good (thanks :) ), but the case for dns323 should go > more like: > > elif echo "$machine" | grep -q "^D-Link DNS-323"; then > INTERFACE="eth0" > check_file /proc/mtd > rootfs=$(get_mtdblock "MTD1") > if [ -n "$rootfs" ]; then > path=/tmp/oldsys-preseed > mkdir -p $path/rootfs > mount -t minix -o ro /dev/$rootfs $path/rootfs > parse_sib_conf "$path/rootfs/sib.conf" > umount $path/rootfs > else > log "Can't find rootfs MTD partition" > NET_CONFIG=dhcp > fi > sanity_check_static_config > if [ "$NET_CONFIG" != "static" ]; then > IPADDRESS=192.168.0.32 > NETMASK=255.255.255.0 > GATEWAY=192.168.0.1 > [ -z "$NAMESERVERS" ] && NAMESERVERS=192.168.0.1 > dhcp_fallback $FILE > fi > > so that it can fall back to dhcp in the event of failing to read > settings, and also fallback to the static address if no dhcp server is > available. I've tested the above code with and without a dhcp server > available, both with static and dhcp configuration in sib.conf, and > even with MTD1 renamed so it can't be found - it gets the network up > one way or another for all cases. :) > -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#509400: installation-reports: optical drive not detected (Lite-On 20X LightScribe)
* Jonathan Quick (j...@hartrao.ac.za) wrote: |> There is problem with support for Marvell SATA IDE controllers in legacy |> mode as included in the 2.6.26-11 kernel image used for that daily image. Oh, I see. It didn't occur to me that the problem might be with the disk controller, rather than with the optical drive itself. Thank you very much indeed for this. I'll try the workaround first and report back. I appreciate your help very much, Jim -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#509378: should use labels for all partitions in fstab
Processing commands for cont...@bugs.debian.org: > reassign 509378 partman-base Bug#509378: should use labels for all partitions in fstab Bug reassigned from package `partman-base' to `partman-base'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: (forw) Re: Bug#509378: should use labels for all partitions in fstab
Processing commands for cont...@bugs.debian.org: > reassign 509378 partman-base Bug#509378: should use labels for all partitions in fstab Bug reassigned from package `debian-installer' to `partman-base'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509378: should use labels for all partitions in fstab
reassign 509378 partman-base thanks Quoting Daniel Pocock (dan...@pocock.com.au): > Package: debian-installer > > > I believe it would be much safer to use labels for partitions rather > than using the device nodes. Reassigning to the correct package. We might even have an already existing bug report about this but I can't check right now. As most wishlist features, this is of course something we can do in the queeze release cycleand, as always, it will not happen by magic: it needs someone to do it, and given the current state of the d-i resourcesdon't expect too muchunless you're ready to do the work..:-) signature.asc Description: Digital signature
Re: Bug#509400: installation-reports: optical drive not detected (Lite-On 20X LightScribe)
In-Reply-To: <1229903525.14242.43.ca...@lapdog2> Hi Jim Jim McCloskey wrote: >03:00.0 IDE interface [0101]: Marvell Technology Group Ltd. 88SE6121 SATA II Controller [11ab:6121] (rev b2) > Kernel driver in use: ahci > Kernel modules: ahci, pata_marvell There is problem with support for Marvell SATA IDE controllers in legacy mode as included in the 2.6.26-11 kernel image used for that daily image. There is a newer 2.6.26-12 kernel image due to hit the dailies shortly which should fix the issue. See: http://packages.qa.debian.org/l/linux-2.6/news/20081215T163248Z.html Alternatively you can try the work-around mentioned in the list posting: http://lists.debian.org/debian-boot/2008/12/msg00058.html which seems to have worked around the problem for the the user who first identified this issue. Note that the released Lenny RC1 images are actually missing the 'pata_marvell' module completely as documented in: http://www.debian.org/devel/debian-installer/errata Regards Jon -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
