Bug#82018: udma66 boot floppies should use current 2.2.1?-ide kernel

2001-01-14 Thread Karl Hammar


Actually, since I have not tested them myself, I cannot make such a
statement.

Regards,
/Karl

---
Karl HammarAsp Data   [EMAIL PROTECTED]
Lilla Asp 2340 +46  173 140 57Networks
S-742 94 sthammar +46  70 511 97 84  Computers
Sweden   Consulting
---


From: Adam Di Carlo [EMAIL PROTECTED]
Subject: Bug#82018: udma66 boot floppies should use current 2.2.1?-ide kernel
Date: 12 Jan 2001 19:11:11 -0500

 
 You're not exactly clear.  The remedy for this bug (and the others
 mentioned) is simply to use the kernel-image-2.2.18-ide package rather
 than kernel-image-2.2.18pre21-ide ?
 
 -- 
 .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Debian Boot CVS: aph

2001-01-14 Thread Debian Boot CVS Master

CVSROOT:/cvs/debian-boot
Module name:boot-floppies
Changes by: aph 01/01/14 10:48:30

Modified files:
documentation/pt: rescue-boot.sgml 

Log message:
fix tagging error


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Bug#81685: kernel doesn't have serial console

2001-01-14 Thread Adam Di Carlo

"Eray Ozkural (exa)" [EMAIL PROTECTED] writes:

 I don't detect a bug about DHCP/BOOTP,

What bug are you referring to?  I use DHCP with the boot-floppies all
the time, and it works fine for me.

 and it seems they are not
 present in the default configuration in kernel-source... package.
 Is it the case with kernel-image?

Well, I don't know exactly which config option you are looking for,
but you can look in the various 'kernel-config' files in the
boot-floppies area of the archive.

-- 
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Preloading add-on drivers from an extra floppy?

2001-01-14 Thread Adam Di Carlo

Marcin Owsiany [EMAIL PROTECTED] writes:

 How does one use that feature? dbootstrap's messages do not
 explain clearly the expected directory structures.

Yes, they wanna be in /lib/modules/section (just remove the
kernel-version part).

This is mentioned in the documentation at least.  perhaps it should be
mentioned in the actual dialogs in dbootstrap if someone wants to fix
that.

-- 
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Processed: base bug maint

2001-01-14 Thread Debian Bug Tracking System

Processing commands for [EMAIL PROTECTED]:

 reassign 81524 bootparamd
Bug#81524: base: bootparamd package can not remove
Bug reassigned from package `base' to `bootparamd'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Darren Benham
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: ltmodem.o fixes Re: Winmodem test disk

2001-01-14 Thread Adam Di Carlo

Marvin Stodolsky [EMAIL PROTECTED] writes:

 Marco, Mark and I will surely be interested in your 2.2.18 patch. 
 Please send it to us.

Yes.  You might want to consider also providing a URL where people can
get the module, based on the stock Debian kernels, if not perhaps file
a bug requestion on the deiban images that these patches be applied.

Regarding the shipping of a separate module, it is now possible to
have an "extra" disk which provides kernel modules which will be
added, which is precisely for these cases of proprietary of whatever
hardware where hte stock kernels can't or don't provide support.

Anyhow, if we wanted to provide that, I could put a link off
http://www.d.o/releases/potato/ .  Let me know.

-- 
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Debian Boot CVS: aph

2001-01-14 Thread Debian Boot CVS Master

CVSROOT:/cvs/debian-boot
Module name:boot-floppies
Changes by: aph 01/01/14 14:59:47

Modified files:
documentation  : install.sgml 

Log message:
update copyright notice


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Bug#81685: kernel doesn't have serial console

2001-01-14 Thread exa

On Sun, Jan 14, 2001 at 01:57:31PM -0500, Adam Di Carlo wrote:
 "Eray Ozkural (exa)" [EMAIL PROTECTED] writes:
 
  I don't detect a bug about DHCP/BOOTP,
 
 What bug are you referring to?  I use DHCP with the boot-floppies all
 the time, and it works fine for me.

I must have looked in the wrong place.

Thanks.

-- 
Eray (exa) Ozkural
Comp. Sci. Dept., Bilkent University, Ankara
e-mail: [EMAIL PROTECTED]
www: http://www.cs.bilkent.edu.tr/~erayo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Bug#80325: Installer misreports partition numbers

2001-01-14 Thread Christoph Paul

   Still kernels should have BSD disklable support as well i think
Its neccessary for Solaris.
  I would be more comfortable if you checked it against the kernel (or
  fdisk, I guess) sources.
 extended partition will always follow primary partitions, following this
 will be BSD or solaris on a first come first serve basis.
 The previous patch i did always put BSD before SOLARIS which is wrong
But not quite- its ok with BSD 
But look at this dmesg output:
Partition check:
 hda: hda1 hda2! hda3 solaris: [s0] hda5 [s1] hda6 [s2] hda7 [s7] hda8  hda4  hda9 
hda10 hda11 hda12 hda13   hda14 hda15 hda16 hda17   

I means what you see: BSD slices at the end, sol. after partition. 
fdisk calls it /dev/hda7, mount /dev/hda11. 
But Extended hda4 is hda4...
and this large swap partition gets "mkswapped" more than once (but not by debian 
linux):
/dev/hda3   *   783  1566   6288408   82  Linux (Auslagerung) 
thats how a solaris partition with slices inside looks to linux.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Debian Boot CVS: aph

2001-01-14 Thread Debian Boot CVS Master

CVSROOT:/cvs/debian-boot
Module name:boot-floppies
Changes by: aph 01/01/14 15:52:26

Modified files:
documentation/en: dbootstrap.sgml 

Log message:
change title of sect "base-config-shadow" -- god, I hate the word "support"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Debian Boot CVS: aph

2001-01-14 Thread Debian Boot CVS Master

CVSROOT:/cvs/debian-boot
Module name:boot-floppies
Changes by: aph 01/01/14 15:55:40

Modified files:
debian : changelog 

Log message:
recent doc changes


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Bug#70798: UDMA66 boot problem/HPT370

2001-01-14 Thread Glenn McGrath

Adam Di Carlo wrote:
 
 Glenn McGrath [EMAIL PROTECTED] writes:
 
  Adam Di Carlo wrote:
  
   Glenn McGrath [EMAIL PROTECTED] writes:
  
I just tested the 2.2.17-ide and 2.2.18-ide kernels and they both detect
a HPT370 chip
  
   Where does this lead us?  Are you saying the HPT370 problems should be
   fixed as of 2.2.18-ide (as opposed to 2.2.18pre21-ide which we are
   using now)?
 
  Well, i just tried the 2.2.18-ide kernel and detects the HPT370 chip as
  well, so i guess we should look elsewhere for the casue of failure.
 
 I don't see how that follows, since the latest release version of
 boot-floppies uses the 2.2.18pre21-ide kernel.  Can you try with that
 kernel and see if it also detects the controller?
 

Soryy, i should read my email before i send it, the first time i tried
it with 2.2.17-ide and 2.2.18-ide, both worked, then i went back and
tried 2.2.18pre21-ide and that also detected the HPT370.

Glenn


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Bug#80325: Installer misreports partition numbers

2001-01-14 Thread Adam Di Carlo

Christoph Paul [EMAIL PROTECTED] writes:

Still kernels should have BSD disklable support as well i think
 Its neccessary for Solaris.
   I would be more comfortable if you checked it against the kernel (or
   fdisk, I guess) sources.
  extended partition will always follow primary partitions, following this
  will be BSD or solaris on a first come first serve basis.
  The previous patch i did always put BSD before SOLARIS which is wrong
 But not quite- its ok with BSD 
 But look at this dmesg output:
 Partition check:
  hda: hda1 hda2! hda3 solaris: [s0] hda5 [s1] hda6 [s2] hda7 [s7] hda8  hda4  
hda9 hda10 hda11 hda12 hda13   hda14 hda15 hda16 hda17 
  
 I means what you see: BSD slices at the end, sol. after partition. 

Um, hum. According to the Linux+FreeBSD HOWTO, the slices and such are
numbered according to the order in which the primary partition that
holds them occurs.

Thus if you are on i386 and your DOS extended partitions are off hda4,
but you had *BSD partitons off hda3, then it would look something
like:

  ... hda3  hda5 hda6 hda7  hda4 hda8 hda9 hda10
 ^^ ^^^
 *BSD partititions extended partitions

 fdisk calls it /dev/hda7, mount /dev/hda11. 

Yah, not much I can do about that.  We've documented it at least.

So long as the kernel and dbootstrap agree, I'm happy.

-- 
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: boot problems

2001-01-14 Thread Adam Di Carlo


Sorry my reply has take so long.

Scott Kersey [EMAIL PROTECTED] writes:

   I am trying to install Debian GNU/Linux 2.2r2 (3 disks) on a Dell laptop.
   I ran through the initial installation off the CD using the default
   options.  After that, I am not able to boot off the rescue CD, 
   hard drive, or rescue floppy.  Any help would be greatly appreciated!  
   Here are the specifics:
 
   My machine is a:
  Dell Inspiron 8000 Notebook, 15" SXVGA (1400x1050), PIII 700MHz,
  32MB ATI range mobility chip set graphics card, 20GB HD, 192MB RAM,
  PICMIA ethernet card, Psion Gold card PICMIA modem,
  external mouse, 
  dual partition with Windows ME (the disk was partitioned using
  Partition magic: 15GB for Linux with 800MB swap space)
 
   When Booting Off the rescue CD:
 I type "rescue root = /dev/hda6" at the "boot:" prompt.

Why are you typing this?  this is completely contrary to the
installation Manual and the documentation.  There is some danish
tutorial floating around that instructs to do this, but it doesn't
make sense.

The command line you gave means "use the kernel on this floppy, but
mount root off an existing linux root partition, hda6".  Based on what
you said you are doing, that doesn't make any sense -- you don't have
anything on /dev/hda* at all yet.

Don't type *anything* -- just hit return and you will boot off the
floppy, CD, or whatever.

Whoever told you otherwise, please hit them with a very very large
clue bat.  Repeatedly.


 The last error message I get before hanging up is:
   "Kernel panic: VFS: Unable to mount root fs on 01:00".

Not a bug -- this is the kind of errors that occur if you give the
wrong arguments.

-- 
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: boot-floppies on Toshiba Tecra 8100

2001-01-14 Thread Adam Di Carlo

[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] writes:

 Hii everyone, happy new year !
 
 I've just installed Debian on my new Toshiba Tecra 8100 laptop and it wasn't easy 
hehe but I finally got it running.
 
 My main concern is : the laptop doesn't want to boot from the debian
 cd's (cd1 or cd2 from 2.2r0).
 
 2 points :
 1) I can boot other laptops with these cd's thus they aren't broken.
 2) I can boot the Tecra with other cd-roms.
 
 I've tried it with both home burnt and commercial cd's.
 
 Adam, is this a know problem ? Searching the mailing lis archive
 doesn't return anything related.

No, it's not a known problem.  

It's either a BIOS config issue, a hardware issue, or a syslinux
issue.  I suggest you pursue those avenues.  There's not much we can
do here on boot-floppies except try to be sure that syslinux issues,
when found, are filed properly as bugs against syslinux.


-- 
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: regarding potato images

2001-01-14 Thread Adam Di Carlo

Jim Westveer [EMAIL PROTECTED] writes:

 Good idea!
 
 Disk #4 will now have the udma66 kernel loaded onto it.
 (debian-cd CVS has been updated)
 
 So for i386/potato/woody the boot kernels are:
 
 CD#1: default kernel from boot-disks(i386)
 CD#2: compact
 CD#3: idepc
 CD#4: udma66
 CD#n: default kernel from boot-disks(i386)

Excellent.  I've updated the Installation Manual to talk about booting
from different CDs to get different flavors, with the caveat that CDs
3 and 4 require 2.2r3 or better.

-- 
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Debian Boot CVS: aph

2001-01-14 Thread Debian Boot CVS Master

CVSROOT:/cvs/debian-boot
Module name:boot-floppies
Changes by: aph 01/01/14 16:18:25

Modified files:
documentation/en: dbootstrap.sgml 

Log message:
change the reference to *BSD stuff since it's not really i386 only


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Debian Boot CVS: zw

2001-01-14 Thread Debian Boot CVS Master

CVSROOT:/cvs/debian-boot
Module name:boot-floppies
Changes by: zw  01/01/14 16:28:36

Added files:
utilities/dbootstrap/po: zh_CN.po 

Log message:
Initial check-in for Chinese-GB2312 translation. Thanks hashao and
debian-chinese-{gb,big5}@lists.debian.org a.k.a. Debian-Zh.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Bug#61802: problems in Alpha boot-floppies documentation

2001-01-14 Thread Adam Di Carlo


Well, we have a reference to the *BSD stuff in the CVS version of the
installation manual now.

The other stuff is pretty flat-out Alpha specific and there's not much
I can do if no alpha developers volunteer to improve the alpha
installation manual.

-- 
.Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Bug#80325: Installer misreports partition numbers

2001-01-14 Thread Glenn McGrath

damnit, ive stuffed up, for the 2.2.x kernels extended partitions
(msdos, bsd, solaris) are shown as they are discovered irrespective of
there type, but for 2.4.x kernels msdos style kernels are always shown
first followed by whichever has the lowest primary partition number.

So basicaly as libfdisk isnt mainly going to used for 2.2.x my patch
will provide incorrect behaviour.

Rather than just reversing it, it would be best if i tested for versions
prior to setting the order, incase we do want to use 2.4.x

For reference in the 2.2.18 source code look at drivers/block/genhd.c
from line 650
In the 2.4.0 code look in fs/partitions/msdos.c from line 440


Sorry about that.


Glenn


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: ltmodem.o fixes Re: Winmodem test disk

2001-01-14 Thread Marvin Stodolsky

The ltmodem.o compile kits are being officially mounted at 
   http://walbran.org/sean/linux/stodolsk/.
The URL for the next upgrade which I'm 2.4.0 testing for Mark is
http://www.test.dclabs.com.au/linmodem/  the  ltmodem-5.78e2.tar.gz  
It is VERY easy to compile a ltmodem.o using the kit components and
kernel-header-packages.  There is an issue of legality about providing
compiled modules as contrasted to the compile kit. I'm excerpting here
from an email of Marco Giordani (concerning the 2.2.nn - 2.4.0-test11
patches), as I'm not erudite on these issues.
 Original Message 
Subject: Re: ltmodem works on 2.4.0test11
Date: Thu, 30 Nov 2000 15:40:06 +0100
From: Marco Giordani [EMAIL PROTECTED]
To: Pavel Machek [EMAIL PROTECTED]
CC: LinModems [EMAIL PROTECTED]
On Wed, Nov 29, 2000 at 03:41:23PM +0100, Pavel Machek wrote:

 As far as I can see, this is forbidden.
 
 You take GPL-ed serial.c, then statically link it against
 closed-source piece of software. That is violation of GPL.

I'm afraid you're wrong here.
The patch I posted was against serial.c (and it is allowed by the GPL
license). I didn't post the final object, because _that_ would have been
bad.

bye, Marco.
---
With respect to Debianizing, Mark Spieth has put commands  in the
README  for  ltmodem.tar.gz -- ltmodem.o --- ltmodem.rpm
and 
alien ltmodem.rpm
does take it to an effective
ltmodem.deb 
though a pause at
alien -g ltmodem.rpm
 is still desirable to achieve Debian standards with added
Documentation/Depends/Conflicts.  We would be Delighted if someone more
Experience than (negligible) I took over the Debianizing step.
I've been spending more than an hour a day in "Fire Control" on
[EMAIL PROTECTED]

Incidentally, professionally I'm a biologist administrator with no
formal comp-sci training. I just stumbled into this because my company
laptop has an embedded Lucent modem, and decided to return help for my
early Linux years.

MarvS
===
 Adam Di Carlo wrote:
 
 Marvin Stodolsky [EMAIL PROTECTED] writes:
 
  Marco, Mark and I will surely be interested in your 2.2.18 patch.
  Please send it to us.
 
 Yes.  You might want to consider also providing a URL where people can
 get the module, based on the stock Debian kernels, if not perhaps file
 a bug requestion on the deiban images that these patches be applied.
 
 Regarding the shipping of a separate module, it is now possible to
 have an "extra" disk which provides kernel modules which will be
 added, which is precisely for these cases of proprietary of whatever
 hardware where hte stock kernels can't or don't provide support.
 
 Anyhow, if we wanted to provide that, I could put a link off
 http://www.d.o/releases/potato/ .  Let me know.
 
 --
 .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Bug#80325: Installer misreports partition numbers

2001-01-14 Thread Glenn McGrath

 there type, but for 2.4.x kernels msdos style kernels are always shown
partitions---^
 
 So basicaly as libfdisk isnt mainly going to used for 2.2.x my patch
is-^

g

Glenn


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Bug#80325: Installer misreports partition numbers

2001-01-14 Thread Glenn McGrath

Here we go again.

The attached patch reverts to the old behaviour (first in best dressed)
if the kernel version is pre 2.4.0 and if 2.4.0 or later will put
extended partitions first.

BUGS: I guess the behaviour changed somewhere in the 2.3.x series, so if
they are using a 2.3 series it may behave incorectly. It will be simple
to update it to behave correctly once we know the exact version that
this new behaviour was implemented.


Glenn

Only in boot-floppies.working/utilities/libfdisk: .depend
diff -r -U 3 boot-floppies.orig/utilities/libfdisk/partbl_msdos.c 
boot-floppies.working/utilities/libfdisk/partbl_msdos.c
--- boot-floppies.orig/utilities/libfdisk/partbl_msdos.cMon Jan 15 13:43:23 
2001
+++ boot-floppies.working/utilities/libfdisk/partbl_msdos.c Mon Jan 15 13:53:53 
+2001
@@ -12,6 +12,7 @@
 #include stdlib.h
 #include unistd.h
 #include asm/types.h
+#include sys/utsname.h
 #include "byteorder.h"
 
 #include "fdisk.h"
@@ -302,12 +303,33 @@
 }
 #endif
 
+/* this function taken from busybox/utility.c 
+ * Returns kernel version encoded as major*65536 + minor*256 + patch,  
+ * so, for example,  to check if the kernel is greater than 2.2.11: 
+ * if (get_kernel_revision() = 2*65536+2*256+11) { stuff }
+ */
+int get_kernel_revision(void)
+{
+struct utsname name;
+int major = 0, minor = 0, patch = 0;
+
+if (uname(name) == -1) {
+fprintf(stderr, "cannot get system information");  
+return (0);
+}
+major = atoi(strtok(name.release, "."));
+minor = atoi(strtok(NULL, "."));
+patch = atoi(strtok(NULL, "."));
+return major * 65536 + minor * 256 + patch;
+}
+
 int parse_msdos_partition(char *device, int fd)
 {
 int i, minor = 1;
 struct partition *p;
 unsigned char data[512];
-
+int kernel_version = get_kernel_revision();
+ 
 if (!sread( fd, 0, data ))
return -1;
 if (*(unsigned short *) (0x1fe + data) != __cpu_to_le16(MSDOS_LABEL_MAGIC))
@@ -322,26 +344,40 @@
if (is_extended_partition(p)) {
extended_partition(device, fd, START_SECT(p), NR_SECTS(p));
}
+   /* if kernel version is less than version 2.4.0 */
+   if (kernel_version  (2*65536 + 4*256)) {
+   if (SYS_IND(p) == BSD_PARTITION) {
+bsd_disklabel_partition(device, fd, START_SECT(p));
+}
+/* [EMAIL PROTECTED]: Solaris has a nasty indicator: 0x82
+ * which also means linux swap.  For that reason, all
+ * of the prints are done inside the
+ * solaris_x86_partition routine */
+if (SYS_IND(p) == SOLARIS_X86_PARTITION) {
+solaris_x86_partition(device, fd, START_SECT(p));
+}
+   }
 }
+
+/* if kernel is 2.4 or better */
+if (kernel_version = (2*65536 + 4*256)) {
 #if HAVE_BSD_DISKLABEL | HAVE_SOLARIS_X86_PARTITION
-p = (struct partition *) (0x1be + data);
-for (i=1 ; i=4 ; minor++,i++,p++) {
+p = (struct partition *) (0x1be + data);
+for (i=1 ; i=4 ; minor++,i++,p++) {
 #if HAVE_BSD_DISKLABEL
-   if (SYS_IND(p) == BSD_PARTITION) {
-   bsd_disklabel_partition(device, fd, START_SECT(p));
-   }
+   if (SYS_IND(p) == BSD_PARTITION) {
+   bsd_disklabel_partition(device, fd, START_SECT(p));
+   }
 #endif
 #if HAVE_SOLARIS_X86_PARTITION
-/* [EMAIL PROTECTED]: Solaris has a nasty indicator: 0x82
- * which also means linux swap.  For that reason, all
- * of the prints are done inside the
- * solaris_x86_partition routine */
-   if (SYS_IND(p) == SOLARIS_X86_PARTITION) {
-   solaris_x86_partition(device, fd, START_SECT(p));
-   }
+   if (SYS_IND(p) == SOLARIS_X86_PARTITION) {
+   solaris_x86_partition(device, fd, START_SECT(p));
+   }
 #endif
-}
+}
 #endif 
+}
+
 /*
  *  Check for old-style Disk Manager partition table
  */



Re: Debian bootdisk with Chinese enabled.

2001-01-14 Thread wen

adam   I am trying the compact one. When the installation goes to the
adam   step of disk partition(cfdisk) I found there is not a highlight
adam   on any partition, so we don't know which partition is being treated.
adam   I don't think this problem is related to Chinese translation but I 
adam   wonder if you have the same problem.

adam Yes, this is one of the critical problems which is preventing us from
adam using LANG_CHOOSER by default.  It's very confusing.  I suppose it's
adam related to the fact that the LANG_CHOOSER stuff uses it's own fonts,
adam and perhaps the highlit version of the character aren't available?  I
adam really have no idea.

Thanks for your reply. As I remember in the page of disk partition(cfdisk)
only English letters exist. My question is: does the problem still
exist even for English letters from a Chinese font set? 

Regards,

Wen
 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Debian Boot CVS: peterk

2001-01-14 Thread Debian Boot CVS Master

CVSROOT:/cvs/debian-boot
Module name:boot-floppies
Changes by: peterk  01/01/15 07:21:14

Modified files:
utilities/dbootstrap/po: sv.po 

Log message:
Updated Swedish translation


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: new demo system -- chrooted!

2001-01-14 Thread Randolph Chung

In reference to a message from Joey Hess, dated Jan 10:
 Anthony Towns wrote:
  The debconf frontend should really be passed through to the udeb frontend;
  the keymap should already have been determined.
 
 Right. How we do that with dpkg and random postinst scripts scribbling
 all over the display, I'm not sure. perhaps you preconfigure everything
 first (with their debconf protocol output/input just passing through to 
 the cdebconf frontend), then when you actually install the stuff you
 redirect it to tty3?

ok, pardon me for being slow.. just got back from a trip

what exactly do you mean by passing the debconf frontend to the udeb
frontend?

randolph
-- 
Debian Developer [EMAIL PROTECTED]
http://www.TauSq.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]