Bug#484115: Partitioning forgets root partition
Package: debian-installer Version: daily netinst 2008.06.02 Severity: normal Hi, I'm just installing the daily netinst and found a glitch when partitioning. I've create a raid1 (md0) for / and a second raid1 (md1) for LVM. I've then configured the / first and then went on to configure LVM. Coming back from that the md0 was no longer marked as / and finishing partitioning compained about having no root partition. Configuring md0 as / again fixes the problem but that shouldn't be required. MfG Goswin -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.2-mrvn Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#373704: Wrong patch
Package: busybox
Version: 1:1.1.3-3
Followup-For: Bug #373704
Sorry, I send the wrong patch last night.
MfG
Goswin
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-frosties
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages busybox depends on:
ii libc62.3.6.ds1-9 GNU C Library: Shared libraries
busybox recommends no packages.
-- no debconf information
diff -u busybox-1.1.3/debian/changelog busybox-1.1.3/debian/changelog
--- busybox-1.1.3/debian/changelog
+++ busybox-1.1.3/debian/changelog
@@ -1,3 +1,15 @@
+busybox (1:1.1.3-3a0.mrvn.2) unstable; urgency=low
+
+ * fix more sort
+
+ -- Goswin von Brederlow [EMAIL PROTECTED] Mon, 15 Jan 2007 00:03:02 +0100
+
+busybox (1:1.1.3-3a0.mrvn.1) unstable; urgency=low
+
+ * Fix sort issues to behave like coreutils sort.
+
+ -- Goswin von Brederlow [EMAIL PROTECTED] Sat, 13 Jan 2007 18:26:58 +0100
+
busybox (1:1.1.3-3) unstable; urgency=low
* debian/control:
diff -u busybox-1.1.3/coreutils/sort.c busybox-1.1.3/coreutils/sort.c
--- busybox-1.1.3/coreutils/sort.c
+++ busybox-1.1.3/coreutils/sort.c
@@ -58,50 +58,60 @@
static char *get_key(char *str, struct sort_key *key, int flags)
{
- int start=0,end,len,i,j;
-
+ int start=0,end,len,i,j,r3=0;
/* Special case whole string, so we don't have to make a copy */
if(key-range[0]==1 !key-range[1] !key-range[2] !key-range[3]
- !(flags(FLAG_bFLAG_dFLAG_fFLAG_iFLAG_bb))) return str;
+ !(flags(FLAG_b|FLAG_d|FLAG_f|FLAG_i|FLAG_bb))) return str;
/* Find start of key on first pass, end on second pass*/
len=strlen(str);
+ /* key-range[3] == 0 means before the next key starts */
+ if (!key-range[3]) r3=1;
+
+ /* Find start of key */
for(j=0;j2;j++) {
if(!key-range[2*j]) end=len;
/* Loop through fields */
else {
end=0;
- for(i=1;ikey-range[2*j]+j;i++) {
-/* Skip leading blanks or first separator */
-if(str[end]) {
- if(!key_separator isspace(str[end]))
- while(isspace(str[end])) end++;
-}
-/* Skip body of key */
-for(;str[end];end++) {
+ for(i=1;ikey-range[2*j]+j*r3;i++) {
+/* Skip leading blanks */
+if(str[end] !key_separator)
+while(isspace(str[end])) end++;
+/* Skip body of key and separator */
+while(str[end]) {
if(key_separator) {
- if(str[end]==key_separator) break;
- } else if(isspace(str[end])) break;
+ if(str[end++]==key_separator) break;
+ } else {
+ if(isspace(str[end])) break;
+ end++;
+ }
}
}
}
if(!j) start=end;
}
- /* Key with explicit separator starts after separator */
- if(key_separator str[start]==key_separator) start++;
+ /* key-range[3] == 0 means before the next key starts */
+ /* rewind the separator */
+ if(key_separator !key-range[3] str[end]) end--;
/* Strip leading whitespace if necessary */
- if(flagsFLAG_b) while(isspace(str[start])) start++;
- /* Strip trailing whitespace if necessary */
- if(flagsFLAG_bb) while(endstart isspace(str[end-1])) end--;
+ if(flagsFLAG_b) {
+ while(isspace(str[start])) start++;
+ /* key end with offset also strips leading spaces */
+ if(key-range[3]) while(isspace(str[end])) end++;
+ }
/* Handle offsets on start and end */
if(key-range[3]) {
- end+=key-range[3]-1;
+ end+=key-range[3];
if(endlen) end=len;
}
if(key-range[1]) {
start+=key-range[1]-1;
if(startlen) start=len;
}
+ /* Strip trailing whitespace if necessary */
+ /* FIXME: not sure about this one. Needs testing with -kx,y.z */
+ if(flagsFLAG_bb) while(endstart isspace(str[end-1])) end--;
/* Make the copy */
if(endstart) end=start;
str=bb_xstrndup(str+start,end-start);
Bug#373704: Updated patch
Package: busybox
Version: 1:1.1.3-3
Followup-For: Bug #373704
Hi,
attached an updated patch for busybox that includes the fix for
#406785 sort: incorrect result when sorting on subfields
or does not break it if you will.
MfG
Goswin
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-frosties
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages busybox depends on:
ii libc62.3.6.ds1-9 GNU C Library: Shared libraries
busybox recommends no packages.
-- no debconf information
diff -u busybox-1.1.3/coreutils/sort.c busybox-1.1.3/coreutils/sort.c
--- busybox-1.1.3/coreutils/sort.c
+++ busybox-1.1.3/coreutils/sort.c
@@ -62,7 +62,7 @@
/* Special case whole string, so we don't have to make a copy */
if(key-range[0]==1 !key-range[1] !key-range[2] !key-range[3]
- !(flags(FLAG_bFLAG_dFLAG_fFLAG_iFLAG_bb))) return str;
+ !(flags(FLAG_b|FLAG_d|FLAG_f|FLAG_i|FLAG_bb))) return str;
/* Find start of key on first pass, end on second pass*/
len=strlen(str);
@@ -72,23 +72,24 @@
else {
end=0;
for(i=1;ikey-range[2*j]+j;i++) {
-/* Skip leading blanks or first separator */
-if(str[end]) {
- if(!key_separator isspace(str[end]))
- while(isspace(str[end])) end++;
-}
-/* Skip body of key */
-for(;str[end];end++) {
+/* Skip leading blanks */
+if(str[end] !key_separator)
+while(isspace(str[end])) end++;
+/* Skip body of key and one blank or seperator */
+while(str[end]) {
if(key_separator) {
- if(str[end]==key_separator) break;
- } else if(isspace(str[end])) break;
+ if(str[end++]==key_separator) break;
+ } else {
+ if(isspace(str[end])) break;
+ end++;
+ }
}
}
}
if(!j) start=end;
}
- /* Key with explicit separator starts after separator */
- if(key_separator str[start]==key_separator) start++;
+ /* Don't include the last whitespace or separator */
+ if (str[end]) end--;
/* Strip leading whitespace if necessary */
if(flagsFLAG_b) while(isspace(str[start])) start++;
/* Strip trailing whitespace if necessary */
Bug#373704: Another patch update
Package: busybox
Version: 1:1.1.3-3
Followup-For: Bug #373704
Hi,
Frans Pop noticed a mistake in the latest patch. The last fix (-2)
changed the way 'end' turns up at the end of the loop for no separator
but still removed one from it. Sort did then crop the end of key by
one without separator.
Patch 3 attached.
MfG
Goswin
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-frosties
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages busybox depends on:
ii libc62.3.6.ds1-9 GNU C Library: Shared libraries
busybox recommends no packages.
-- no debconf information
diff -u busybox-1.1.3/coreutils/sort.c busybox-1.1.3/coreutils/sort.c
--- busybox-1.1.3/coreutils/sort.c
+++ busybox-1.1.3/coreutils/sort.c
@@ -62,7 +62,7 @@
/* Special case whole string, so we don't have to make a copy */
if(key-range[0]==1 !key-range[1] !key-range[2] !key-range[3]
- !(flags(FLAG_bFLAG_dFLAG_fFLAG_iFLAG_bb))) return str;
+ !(flags(FLAG_b|FLAG_d|FLAG_f|FLAG_i|FLAG_bb))) return str;
/* Find start of key on first pass, end on second pass*/
len=strlen(str);
@@ -72,23 +72,24 @@
else {
end=0;
for(i=1;ikey-range[2*j]+j;i++) {
-/* Skip leading blanks or first separator */
-if(str[end]) {
- if(!key_separator isspace(str[end]))
- while(isspace(str[end])) end++;
-}
-/* Skip body of key */
-for(;str[end];end++) {
+/* Skip leading blanks */
+if(str[end] !key_separator)
+while(isspace(str[end])) end++;
+/* Skip body of key and one blank or seperator */
+while(str[end]) {
if(key_separator) {
- if(str[end]==key_separator) break;
- } else if(isspace(str[end])) break;
+ if(str[end++]==key_separator) break;
+ } else {
+ if(isspace(str[end])) break;
+ end++;
+ }
}
}
}
if(!j) start=end;
}
- /* Key with explicit separator starts after separator */
- if(key_separator str[start]==key_separator) start++;
+ /* Don't include the last separator */
+ if (key_separator str[end]) end--;
/* Strip leading whitespace if necessary */
if(flagsFLAG_b) while(isspace(str[start])) start++;
/* Strip trailing whitespace if necessary */
Bug#373704: Once more with feeling
Package: busybox
Version: 1:1.1.3-3
Followup-For: Bug #373704
And once more another patch.
sort -kx,y.z caused busybox to find the end of key y without trailing
separator and then add z-1. And leading whitespaces didn't get
ignored.
I changed the code now to the following:
-kx,y[.0] find start of key y+1 and rewind the separator
-kx,y.z find start of key y, skip leading spaces if needed, add z
I'm not sure about removing trailing whitespaces. I moved it to after
adjusting end by the offset. Makes no sense to remove trailing
whitespaces when end still points to the start of y. Someone has to
create a few testcases for this and tell me if it differs from
coreutils sort in any way. FLAG_bb gets set with -b and -k1,2b.
MfG
Goswin
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-frosties
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages busybox depends on:
ii libc62.3.6.ds1-9 GNU C Library: Shared libraries
busybox recommends no packages.
-- no debconf information
diff -u busybox-1.1.3/debian/changelog busybox-1.1.3/debian/changelog
--- busybox-1.1.3/debian/changelog
+++ busybox-1.1.3/debian/changelog
@@ -1,3 +1,15 @@
+busybox (1:1.1.3-3a0.mrvn.2) unstable; urgency=low
+
+ * fix more sort
+
+ -- Goswin von Brederlow [EMAIL PROTECTED] Mon, 15 Jan 2007 00:03:02 +0100
+
+busybox (1:1.1.3-3a0.mrvn.1) unstable; urgency=low
+
+ * Fix sort issues to behave like coreutils sort.
+
+ -- Goswin von Brederlow [EMAIL PROTECTED] Sat, 13 Jan 2007 18:26:58 +0100
+
busybox (1:1.1.3-3) unstable; urgency=low
* debian/control:
diff -u busybox-1.1.3/coreutils/sort.c busybox-1.1.3/coreutils/sort.c
--- busybox-1.1.3/coreutils/sort.c
+++ busybox-1.1.3/coreutils/sort.c
@@ -59,49 +59,59 @@
static char *get_key(char *str, struct sort_key *key, int flags)
{
int start=0,end,len,i,j;
-
/* Special case whole string, so we don't have to make a copy */
if(key-range[0]==1 !key-range[1] !key-range[2] !key-range[3]
- !(flags(FLAG_bFLAG_dFLAG_fFLAG_iFLAG_bb))) return str;
+ !(flags(FLAG_b|FLAG_d|FLAG_f|FLAG_i|FLAG_bb))) return str;
/* Find start of key on first pass, end on second pass*/
len=strlen(str);
+ /* key-range[3] == 0 means before the next key starts */
+ if (!key-range[3]) key-range[2]++;
+
+ /* Find start of key */
for(j=0;j2;j++) {
if(!key-range[2*j]) end=len;
/* Loop through fields */
else {
end=0;
- for(i=1;ikey-range[2*j]+j;i++) {
-/* Skip leading blanks or first separator */
-if(str[end]) {
- if(!key_separator isspace(str[end]))
- while(isspace(str[end])) end++;
-}
-/* Skip body of key */
-for(;str[end];end++) {
+ for(i=1;ikey-range[2*j];i++) {
+/* Skip leading blanks */
+if(str[end] !key_separator)
+while(isspace(str[end])) end++;
+/* Skip body of key and separator */
+while(str[end]) {
if(key_separator) {
- if(str[end]==key_separator) break;
- } else if(isspace(str[end])) break;
+ if(str[end++]==key_separator) break;
+ } else {
+ if(isspace(str[end])) break;
+ end++;
+ }
}
}
}
if(!j) start=end;
}
- /* Key with explicit separator starts after separator */
- if(key_separator str[start]==key_separator) start++;
+ /* key-range[3] == 0 means before the next key starts */
+ /* rewind the separator */
+ if(key_separator !key-range[3] str[end]) end--;
/* Strip leading whitespace if necessary */
- if(flagsFLAG_b) while(isspace(str[start])) start++;
- /* Strip trailing whitespace if necessary */
- if(flagsFLAG_bb) while(endstart isspace(str[end-1])) end--;
+ if(flagsFLAG_b) {
+ while(isspace(str[start])) start++;
+ /* key end with offset also strips leading spaces */
+ if(key-range[3]) while(isspace(str[end])) end++;
+ }
/* Handle offsets on start and end */
if(key-range[3]) {
- end+=key-range[3]-1;
+ end+=key-range[3];
if(endlen) end=len;
}
if(key-range[1]) {
start+=key-range[1]-1;
if(startlen) start=len;
}
+ /* Strip trailing whitespace if necessary */
+ /* FIXME: not sure about this one. Needs testing with -kx,y.z */
+ if(flagsFLAG_bb) while(endstart isspace(str[end-1])) end--;
/* Make the copy */
if(endstart) end=start;
str=bb_xstrndup(str+start,end-start);
Bug#373704: Patch for sort issues
Package: busybox
Version: 1:1.1.3-3
Followup-For: Bug #373704
Attached is a patch for the sort issues. A few have croped up while
testing this. Hopefully busybox sort now behaves like coreutils sort.
About the patch (line numbers of result):
Line 65 : Fix -b -f -i -d and trailing spaces.
Try any of those flags on its own.
Line 75 : Seperators are not skipped (never where)
Line 76-77: Collaps lines:
- the while checks for isspace() already
- combine str[end] and !key_separator
No code change, just correcting the comment and simplifying.
Line 78-82: Move 'end++' into the loop into the tests
for becomes while
The loop in line 74 is supposed to count 'key-range[2*j]+j'
seperators or whitespaces. The old code would advance end up to the
first seperator and then no more. The same seperator got counted again
and again. Only -k1 and -k2 worked. Moving the 'end++' inside the loop
into the test cases causes them to advance past the seperator so the
next loop starts fresh on the next key again.
,x,,,a gets split into '','x','','','a' now, into 5 key positions.
Line 88 + : The fix in 78-82 included the last whitespace or
separator, remove it here.
Without this sort -k2,2 -t, and this input
x,a,a
x,a
would use the following strings for comparisons:
a,
a
Line 88 - : Don't skip the first seperator if a key starts with
seperators.
Frankly that line didn't make any sense. Consider sort -k2 -t,
,a
,b
,,a
,,b
,,,a
,,,b
That gets split into
a
b
,a
,b
,,a
,,b
And then one leading , got ignored giving
a
b
a
b
,a
,b
and last sorted into
,,,a
,,,b
,,a
,a
,,b
,b
It should either ignore all leading seperators or none, not
one. Coreutils ignores none so I removed that line completly.
MfG
Goswin
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-frosties
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages busybox depends on:
ii libc62.3.6.ds1-9 GNU C Library: Shared libraries
busybox recommends no packages.
-- no debconf information
diff -u busybox-1.1.3/coreutils/sort.c busybox-1.1.3/coreutils/sort.c
--- busybox-1.1.3/coreutils/sort.c
+++ busybox-1.1.3/coreutils/sort.c
@@ -62,7 +62,7 @@
/* Special case whole string, so we don't have to make a copy */
if(key-range[0]==1 !key-range[1] !key-range[2] !key-range[3]
- !(flags(FLAG_bFLAG_dFLAG_fFLAG_iFLAG_bb))) return str;
+ !(flags(FLAG_b|FLAG_d|FLAG_f|FLAG_i|FLAG_bb))) return str;
/* Find start of key on first pass, end on second pass*/
len=strlen(str);
@@ -72,23 +72,21 @@
else {
end=0;
for(i=1;ikey-range[2*j]+j;i++) {
-/* Skip leading blanks or first separator */
-if(str[end]) {
- if(!key_separator isspace(str[end]))
- while(isspace(str[end])) end++;
-}
-/* Skip body of key */
-for(;str[end];end++) {
+/* Skip leading blanks */
+if(str[end] !key_separator)
+while(isspace(str[end])) end++;
+/* Skip body of key and one blank or seperator */
+while(str[end]) {
if(key_separator) {
- if(str[end]==key_separator) break;
- } else if(isspace(str[end])) break;
+ if(str[end++]==key_separator) break;
+ } else if(isspace(str[end++])) break;
}
}
}
if(!j) start=end;
}
- /* Key with explicit separator starts after separator */
- if(key_separator str[start]==key_separator) start++;
+ /* Don't include the last whitespace or separator */
+ if (str[end]) end--;
/* Strip leading whitespace if necessary */
if(flagsFLAG_b) while(isspace(str[start])) start++;
/* Strip trailing whitespace if necessary */
Bug#401876: Missing proper dictionary for selected language
Package: debian-installer Version: etch RC1 Severity: wishlist Hi, in D-I the user selects his language and everything is nice and localized during install. But then dictionaries-common pops up and asks what wordlist dictionary to use and the only choice is american (American English). Please add the proper dictionary for the selected language to the list of packages d-i installs after base. MfG Goswin -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-frosties Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#371166: FTBFS: cp: cannot stat `/usr/share/terminfo/b/bterm': No such file or directory
Package: di-utils Version: 1.23 Severity: important Justification: fails to build from source When trying to build di-utils in etch I get: make[1]: Leaving directory `/home/mrvn/01-di-utils/debian-installer-utils-1.23' touch build-stamp fakeroot debian/rules binary dh_testdir dh_testroot dh_clean -k dh_installdebconf -i dh_compress -i dh_fixperms -i for file in /usr/share/terminfo/a/ansi /usr/share/terminfo/l/linux \ /usr/share/terminfo/v/vt102 /usr/share/terminfo/b/bterm; do \ mkdir -p debian/di-utils-terminfo/`dirname $file`; \ cp -pL $file debian/di-utils-terminfo/$file; \ done cp: cannot stat `/usr/share/terminfo/b/bterm': No such file or directory make: *** [binary-indep] Error 1 debuild: fatal error at line 1219: fakeroot debian/rules binary failed MfG Goswin -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.16-rc4-xen Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#271782: (no subject)
Joey Hess [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: Some more udeb sources missing in sarge: rootskel cdrom-checker anna ddetect debian-installer-utils lowmemcheck main-menu No udeb sources are in sarge, but I am not seeing these build-depends on them that you speak of. -- see shy jo They are not listed as Build-Depends since udebs are not installed on the build system as such. They are downloaded and unpacked to create the initrds instead. That's why I quoted build-depends. They need to be in the udebs Packages file. As you say there are no udeb sources in sarge (unless it is a regular source also building udebs). Apart from meaning that amd64 doesn't get udeb automatically it is also a GPL violation not to have the sources on the same medium as the udebs. Having the source on alioth isn't enough. For both those reasons I think it would be good to make a new D-I rc release during/after the debcamp and get that one moved to sarge with sources. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#235068: FTBFS: should unpack latest kernel-source during build
Package: modconf
Version: 0.2.45.1
Severity: normal
Followup-For: Bug #235068
Hi,
modconf should not require human intervention to unpack the kernel
source proided by a kernel-source package. The attached patch uses the
@sources array of available kernel sources to unpack them and test for
Makefile them starting with the last one. Hopefully the last one is
also the highest version.
You should also consider adding a 'real | virtual' Build-Depends for
kernel-source because apt-get build-dep fails without it and lintian
warns (in the next release). Maybe the soon to come kernel-tree or
kernel-tree-2.4|2.6 meta-package is a more suitable Build-Depends.
MfG
Goswin
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.5-amd64
Locale: LANG=C, LC_CTYPE=de_DE
Versions of packages modconf depends on:
ii modutils 2.4.26-1 Linux module utilities
ii whiptail [whiptail-provider] 0.51.4-23 Displays user-friendly dialog boxe
-- no debconf information
diff -Nurd modconf-0.2.45.1.deb/debian/changelog modconf-0.2.45.1/debian/changelog
--- modconf-0.2.45.1.deb/debian/changelog 2004-03-20 22:05:39.0 +
+++ modconf-0.2.45.1/debian/changelog 2004-06-22 00:33:06.0 +
@@ -1,3 +1,9 @@
+modconf (0.2.45.1-0.0.0.1.pure64) unstable; urgency=low
+
+ * Unpack kernel-source during build
+
+ -- Goswin von Brederlow [EMAIL PROTECTED] Tue, 22 Jun 2004 02:23:32 +0200
+
modconf (0.2.45.1) unstable; urgency=low
* NMU
diff -Nurd modconf-0.2.45.1.deb/debian/mkkerneldesc.pl
modconf-0.2.45.1/debian/mkkerneldesc.pl
--- modconf-0.2.45.1.deb/debian/mkkerneldesc.pl 2004-03-20 22:06:33.0 +
+++ modconf-0.2.45.1/debian/mkkerneldesc.pl 2004-06-22 00:51:58.0 +
@@ -9,19 +9,23 @@
# Enable/Disable debugging here
my $opt_d = 0;
+my @sources = glob (/usr/src/kernel-source-*.tar.bz2);
+die You need to install a kernel-source package!\n if (scalar(@sources) == 0 );
+
my $linux = '';
-my @linux = glob (/usr/src/kernel-source-*/);
[EMAIL PROTECTED] = (/usr/src/kernel-source/, /usr/src/linux/, @linux);
-my $dir;
-foreach $dir (@linux) {
- if (-f ${dir}Makefile) {
+my $file = '';
+mkdir(linux);
+foreach $file (reverse @sources) {
+ warn I: Unpacking kernel source from \.$file.\\n;
+ system(tar -C linux -x --bzip -f .$file);
+ my $dir = glob (linux/kernel-source-*);
+ if (-f ${dir}/Makefile) {
$linux = $dir;
last;
}
}
-my @sources = glob (/usr/src/kernel-source-*tar.{bz2,gz});
-warn E: You need to install a kernel-source package and unpack the tar it
provides!\n if ( $linux eq '' scalar(@sources) 0 ) ;
-die Cannot find kernel source if ($linux eq '');
+die Unpacking kernel source failed if ($linux eq '');
+
warn I: Will parse kernel Makefiles under \$linux\.\n;
if(open(fh, $linux/Makefile) grep(/PATCHLEVEL.*=.*6/, fh)) {
warn I: Using Kernel 2.6 extraction method.\n;
diff -Nurd modconf-0.2.45.1.deb/debian/rules modconf-0.2.45.1/debian/rules
--- modconf-0.2.45.1.deb/debian/rules 2001-01-26 01:35:03.0 +
+++ modconf-0.2.45.1/debian/rules 2004-06-22 00:40:56.0 +
@@ -20,9 +20,10 @@
clean:
$(checkdir)
-make clean
- -rm -f `find . -name *~`
- -rm -rf debian/tmp debian/files* core
- -rm -f build-stamp
+ rm -f `find . -name *~`
+ rm -rf debian/tmp debian/files* core
+ rm -rf linux
+ rm -f build-stamp
binary-indep: checkroot build
$(checkdir)
Bug#249598: FTBFS: amd64 missing in Architecture list
Package: kbd-chooser
Version: 0.53
Severity: important
Tags: patch
Justification: no longer builds from source
Not sure if kdb-choose actually works on amd64 but having an udeb
means we can test it.
MfG
Goswin
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.5-amd64
Locale: LANG=C, LC_CTYPE=de_DE
diff -Nurd kbd-chooser-0.53.deb/debian/changelog kbd-chooser-0.53/debian/changelog
--- kbd-chooser-0.53.deb/debian/changelog 2004-05-15 18:08:44.0 +
+++ kbd-chooser-0.53/debian/changelog 2004-05-18 12:10:38.0 +
@@ -1,3 +1,9 @@
+kbd-chooser (0.53-0.0.0.1.pure64) unstable; urgency=low
+
+ * Added amd64 to Architecture list
+
+ -- Goswin von Brederlow [EMAIL PROTECTED] Mon, 18 May 2004 14:10:05 +0200
+
kbd-chooser (0.53) unstable; urgency=low
* Fix calculation of default keymap by locale. Closes: #245477, #247466.
diff -Nurd kbd-chooser-0.53.deb/debian/control kbd-chooser-0.53/debian/control
--- kbd-chooser-0.53.deb/debian/control 2004-05-08 07:56:18.0 +
+++ kbd-chooser-0.53/debian/control 2004-05-18 12:10:05.0 +
@@ -6,7 +6,7 @@
Build-Depends: debhelper (= 4.1.16), libdebian-installer4-dev, po-debconf (=
0.5.0), flex | flex-old , bison, libdebconfclient0-dev (= 0.49)
Package: kbd-chooser
-Architecture: i386 ia64 hppa alpha sparc mips mipsel arm m68k powerpc
+Architecture: i386 ia64 hppa alpha sparc mips mipsel arm m68k powerpc amd64
XB-Installer-Menu-Item: 12
Depends: ${shlibs:Depends}, console-keymaps, archdetect
Description: Detect a keyboard and select layout
Bug#228068: FTBFS: kernel-headers-2.4.20-386 are arch specific
Package: discover2 Version: 2.0+20031223-1 Severity: normal Followup-For: Bug #228068 Hi, dpkg-buildpackage: source package is discover2 dpkg-buildpackage: source version is 2.0+20031223-1 dpkg-buildpackage: host architecture is m68k dpkg-checkbuilddeps: Unmet build dependencies: kernel-headers-2.4.20-386 | kernel-headers autoconf libtool doxygen opensp sgml-data docbook-xml xsltproc ldp-docbook-xsl links docbook-to-man libxml2 ( 2.5.7-1) | libxml2-utils (= 2.5.7-1) dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting. dpkg-buildpackage: (Use -d flag to override.) If discover2 supports m68k at all you need to use different kernel-headers for it. Otherwise you should remove the arch. MfG Goswin -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux dual 2.4.23dual #1 SMP Sun Dec 14 13:57:16 CET 2003 i686 Locale: LANG=C, LC_CTYPE=de_DE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#221534: debian-installer: FTBFS mips (in a good way)
Package: debian-installer Version: 20031114 (not installed) Severity: important Justification: fails to build from source Hi, -- dh_gencontrol -- -Vkernel:Package='kernel-image-2.4.19-r4k-ip22' dpkg-gencontrol: error: current build architecture mips does not appear in package's list (i386 powerpc ia64) dh_gencontrol: command returned error code 65280 make: *** [binary-arch] Error 1 -- Please include arch mips. -- System Information: Debian Release: testing/unstable Architecture: mips Kernel: Linux paco 2.4.19-r4k-ip22 #1 Fri Sep 19 20:36:32 CEST 2003 mips GNU/Linux Locale: LANG=C, LC_CTYPE=de_DE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#221213: partconf: Uninstallable due to broken depends
Package: partconf
Version: 0.15 (not installed)
Severity: grave
Justification: renders package unusable
Partconf Build-Depends on libparted1.6-dev | libparted-dev and its
binary packages Depends: ${shlibs:Depends}. That results in
Depends: libc6 (= 2.3.2.ds1-4), libdebconfclient0,
libdebian-installer4 (= 0.16), libparted1.6-0 (= 1.6.0). That makes
them uninstallable.
The binary packages should depend on the respective udebs:
Package: libc-udeb
Provides: glibc-2.3.2.ds1-10
Package: libparted1.6-udeb
Provides: libparted
MfG
Goswin
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux dual 2.4.21-ac4 #1 SMP Sat Jul 5 17:53:13 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=de_DE
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#216756: busybox-cvs udeb: /linuxrc is obsolete and breaks d-i
Package: busybox-cvs Version: unavailable; reported 2003-10-20 Severity: critical Justification: breaks unrelated software /linuxrc only works in some special cases that can't be used inn all cases on all architectures and is obsolete since pivot_root was invented. Because of that the rootskel udeb of debian-install no longer provides a /linux that would override the busybox /linuxrc. In cases that do support /linuxrx that can lead to busybox being started instead of the start script for debian-installer, which in turn leads to the filesystem running out of space or being unwriteable later in the d-i process. Please do remove /linuxrc. MfG Goswin -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux dual 2.4.21-ac4 #1 SMP Sat Jul 5 17:53:13 CEST 2003 i686 Locale: LANG=C, LC_CTYPE=de_DE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#216435: busybox-cvs: ln reports wrong error
Package: busybox-cvs Version: unavailable; reported 2003-10-18 Severity: normal When linking a non existing file busybox ln will report the target missind and not the source: [EMAIL PROTECTED]:~% ln /bla/foo /foo ln: accessing `/bla/foo': No such file or directory [EMAIL PROTECTED]:~% busybox ln /bla/foo /foo ln: /foo: No such file or directory MfG Goswin -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux dual 2.4.21-ac4 #1 SMP Sat Jul 5 17:53:13 CEST 2003 i686 Locale: LANG=C, LC_CTYPE=de_DE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody can't find Adaptec 39320 SCSI card...
[EMAIL PROTECTED] writes: Hello guys, I have recently bought a fine server running 3 raid disks on an Adaptec 39320D SCSI card. This card is supported by the Linux aic79xx driver (the old one aic7xxx does not work). Thus, I need to compile a boot kernel and rdev it into a set of bf24 boot floppies. HOWEVER, this requires that you have at least ONE Debian machine already running bf24 to have a sufficiently similar kernel compilation environment. I do not. You can compile the linux kernel and modules on any linux system with sufficiently new toolchain (see kernel-source/Doc*/Changes). Some people even crosscompiled their kernel from other unix systems, AmigaOS, MacOS or even Windows (althgough thats not for the faint of heart). Also don't you have some onboard ide contrroler and a spare ide disk for an hour? Just install debian there, compile your kernel and eigther move the system over to scsi or reinstall with that kernel. Or a cdrom drive on another controler? Boot a Knoppix CD and compile your kernel there. Maybe knoppix even has support for your card so you can run debootstrap inside Knoppix to install Debian. The Posibilities are endless. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Not an ELF file?
Matt Kraai [EMAIL PROTECTED] writes: On Sun, Jul 20, 2003 at 12:56:09AM +0200, Petter Reinholdtsen wrote: What is the solution to this error, which I get when I try to build d-i floppies out of the current archive: mklibs -v -d ./tmp/cdrom/tree/lib --root=./tmp/cdrom/tree `find ./tmp/cdrom -type f -perm +0111 -o -name '*.so'` Command failed with status 1 : readelf --program-headers ./tmp/cdrom/tree/lib/debian-installer.d/S20templates With output: readelf: Error: Unable to read in 28772 bytes of section headers readelf: Error: Not an ELF file - it has the wrong magic bytes at the start This has been reported as bug #201740. Why does it happen at all? S20templates does not match -name '*.so' so it should not be passed as an argument and nothing links to it so mklibs should not pull it in eigther. I don't realy see the point in checking files not passed as argument or linked against but I haven't worked on mklibs for a long long time. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Not an ELF file?
Matt Kraai [EMAIL PROTECTED] writes: On Tue, Aug 05, 2003 at 08:49:29AM +0200, Goswin Brederlow wrote: Matt Kraai [EMAIL PROTECTED] writes: On Sun, Jul 20, 2003 at 12:56:09AM +0200, Petter Reinholdtsen wrote: What is the solution to this error, which I get when I try to build d-i floppies out of the current archive: mklibs -v -d ./tmp/cdrom/tree/lib --root=./tmp/cdrom/tree `find ./tmp/cdrom -type f -perm +0111 -o -name '*.so'` Command failed with status 1 : readelf --program-headers ./tmp/cdrom/tree/lib/debian-installer.d/S20templates With output: readelf: Error: Unable to read in 28772 bytes of section headers readelf: Error: Not an ELF file - it has the wrong magic bytes at the start This has been reported as bug #201740. Why does it happen at all? S20templates does not match -name '*.so' so it should not be passed as an argument and nothing links to it so mklibs should not pull it in eigther. I think it matches '-type f -perm +0111'. -- Matt Oh, there is an -o there, overlooked that. Do files that get sourced need to be executable? Should they be? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Ideas for d-i cdrom images
Martin Sjögren [EMAIL PROTECTED] writes: tis 2003-08-05 klockan 09.21 skrev Goswin Brederlow: 1. One can create a seemingly writeable loopback filesystem on CD. The CD holds a readonly loopback file and one can create a snapshot of that together with a ramdisk or shmfs (or on newer kernels a file on tmpfs). Any writes to the loopback file then go into the ramdisk and are lost on reboot. I have a CD image with a 100% normal woody system on it with a initrd that sets such a snapshot up. Works like a charme. This sounds really neat. Stackable file systems, yay. Stackable block devices. Its independant of the filesystem or even if there is a filesystem on it. With this instead of installing all (selected) udebs into a big ramdisk the udebs can be preinstalled into a loopback file upon cd creation and mounted this way to reduce the ram consumtion a lot. No complicated linkfarms would be neccessary. It would also instantly have all udebs unpacked already so its faster too. The Installer would then just run the postinst files when an udeb is selected. Okay, so how would it work for net installs? floppy installs? (with floppy install I mean boot from floppy, load either CD drivers or NIC drivers from floppy/floppies and then proceed with CD or net install) Floppy/Net install of cause wouldn't use this. A Floppy/CD install (where one creates floppies of the CDs boot images because the CD doesn't boot) works just like the CD version. A Floppy/NFS-root install could use this if you can have loopback files on NFS. One possibility would look like this: The Stage 1 installer would load modules for lvm, cd, nic, nfs and so on from the boot media just like now. Then one would select the live image menu option to start the snapshot and run the live filesystem with fancy X, some games, docs, irc, browser, etc depending on the size of the image. Have you looked in cvs.debian.org/debian-installer/doc/scenarios.txt? It is very important that our design fits all or at least most of the installation scenarios, I think it will be a pain to have one design for CD installs and another for net installs. Then add that we might need a separate design for a GUI installer, and we may end up juggling three or four designs... Anything that doesn't come with a big chunk of space can't realy use this. Its mainly a bonus for CD install. The beauty of the design would be that it would appear to have all the udebs on the mounted filesystem just like they would be in the net installer (that installs into ramdisk). The only difference would be that they would all already be unpackaged. Changes to skip the unpacking should be minimal. Don't get me wrong, I like the idea of reducing the ramdisk size, but I don't see how it would work for a net install... It wouldn't. But it would make no difference to the installed udebs, just the d-i core itself needs a little tweak. Another thing, I don't think it's a good idea to actually have all udebs unpacked already, because all udebs will be a lot of them... For example, on a CD install you will rarely need to configure the network, so the network udebs should not be unpacked automatically. For simple installs, there's no reason to have lvm/raid/evms unpacked automatically, it will unnecessarily clutter the menu. Correct me if I'm wrong but doesn't running the postinst add the menu entries so unless they are run no menu entries should appear. 2. The CD could contain a knoppix like live filesystem that autodetects most stuff and asks questions about the rest and thus configures itself. Then once the harddisk is partitioned and formated the running live filesystem can be transfered over to harddisk on the fly in the background and the user can just keep on working all the time and doesn't need to reboot even once. Rebootless install? Eek. I think it would be nice to be able to reboot the more specific kernel for your system than continuing to use the udeb kernel... So far the same kernel has been used for the install and later system and I wouldn't change that behaviour. You only end up with the install kernel working but the installed kernel not working. 3. When repartitioning a harddisk one has to reboot if any partition is in use to let changes take affect. Using lvm the partition can be mapped seperatly and those mappings can be changed in userspace. One can also move partitions around in the background with lvm and even have a resume feature when the system crashes inbetween (provided there is some space to store resume infos). IIRC evms has some of those features already. But how often will a partition be in use when you partition it from an installer? I don't understand your point, but then, I don't know anything about lvm. .oO( Your low on ram, you setup swap and activate it using the textmode. Than you switch to graphical
Re: Cross-install howto
Eduard Bloch [EMAIL PROTECTED] writes: #include hallo.h Ben Bucksch wrote on Sat Jun 01, 2002 um 02:38:44PM: Does debootstrap not run the dbootstrap ncurses-bases config/install No. tool? That was probably my problem back then (not Red Hat) - I didn't know how to manually configure the network, hostnames, timezone etc. back then. You have to do manually. /etc/hostname, /etc/hosts, base-config. /etc/network/interfaces debbostrap is ment primary for changeroots where such stuff is usually not needed. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Cross-install howto
Ben Bucksch [EMAIL PROTECTED] writes: None of my machines have floppy drives and most of them have no removable media at all, not even CD-ROM drives. Until recently, I had no CD burner either. So, I had (and still have) the problem of installing Debian only with the harddisk and my existing OSes. mrvn@dual:~% apt-cache show debootstrap Package: debootstrap Priority: extra Section: admin Installed-Size: 176 Maintainer: Anthony Towns [EMAIL PROTECTED] Architecture: i386 Version: 0.1.17 Depends: libc6 (= 2.2.4-4), wget Filename: pool/main/d/debootstrap/debootstrap_0.1.17_i386.deb Size: 52770 MD5sum: 0d37ce6cd5b70a8372a3539f611fbb30 Description: Bootstrap a basic Debian system debootstrap is used to create a Debian base system from scratch, without requiring the availability of dpkg or apt. It does this by downloading .deb files from a mirror site, and carefully unpacking them into a directory which can eventually be chrooted into. I hope you knew this existed. Unfortunately, the install guide doesn't describe, how to do that. All of the many ways to install Debian assume some form of removable media to boot from (or a bootable network card), even if they are called net-only or hd-only. You can download the linux.bat, the kernel and rescue disk onto a fixed disk and then run that in DOS. No need for a _removable_ media, a fixed one will do. After fiddling around long (incl. building boot-floppies), I found an easy way to achieve that. It is probably obvious for people working on the boot disks, yet I didn't find it being documented anywhere. So, I wrote a guide myself and put it online. You can find it at http://www.bucksch.org/1/projects/debian/crossinst. If you want, you can integrate it (or something similar) into the Debian install manual or just link to that URL. For real cross installing bochs is also nice. I cross installed my i386 dsl router once using bochs on my Alpha (because then I had internet to download the debs meanwhile). Hope you mentioned that too. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help needed : kernel panic unable to mount root fs
Shree Raman [EMAIL PROTECTED] writes: hi all!! I am experiencing a tough time as my system had a kernel panic. it happened while I was installing openoffice. The system hunged and there was no way left other than rebooting then a kernel panic prompt. I had installed debian testing from floppies i am not having a boot disk. I tried to use mkrboot from another system but it is also not helping. Can any one tell me how to solve this problem. The panic prompt tells try using init= . but i am unable to find out a soluton. the filesystem(reiserfs) as reprted is readonly. Most likely your reiserfs ist just broken. Tough luck, don't use unstable filesystems. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#146713: language-chooser: unsorted and to small
Package: boot-floppies Version: N/A; reported 2002-05-12 Severity: minor The language chooser is 5 lines to small to show all languages. Since theres some space left on the screen it could be made to fit them all. Also the languages seems to be roughly sorted alphabetically, but just roughly (e.g. zh being second). Having them sorted would be good and also a default EN at the top would be nice, since most users will want that. As one said: You can teach a chicken to install Debian, just put some corn on the return key :). Defaulting to en would be the save option. MfG Goswin -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux dual 2.4.16 #11 SMP Sat Jan 26 23:06:31 CET 2002 i686 Locale: LANG=C, LC_CTYPE=de_DE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#136204: boot-floppies (alpha): wrong build depends output
Package: boot-floppies Version: N/A; reported 2002-02-28 Severity: normal ... dpkg-checkbuilddeps checking variable dependancies didn't find libnewt-utf8-pic didn't find slang1-utf8-pic didn't find slang1-utf8 didn't find libnewt-utf8-0 To install missing packages: apt-get install libnewt-utf8-pic slang1-utf8-pic slang1-utf8 libnewt-utf8-0 make[1]: *** [check_depends] Error 1 make[1]: Leaving directory `/usr/local/src/debian/boot-floppies-3.0.19' make: *** [build] Error 2 debuild: fatal error at line 322: dpkg-buildpackage failed! mrvn@alpha:/usr/local/src/debian/boot-floppies-3.0.19% sudo apt-get install libnewt-utf8-pic slang1-utf8-pic slang1-utf8 libnewt-utf8-0 Reading Package Lists... Done Building Dependency Tree... Done Package slang1-utf8 has no available version, but exists in the database. This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list E: Package slang1-utf8 has no installation candidate apt-get build-dep boot-floppies installs slang1-utf8-dev slang1-utf8-pic slang1a-utf8 May the Source be with you. Goswin -- System Information Debian Release: 3.0 Architecture: alpha Kernel: Linux alpha 2.4.16 #10 Tue Jan 29 14:02:46 CET 2002 alpha Locale: LANG=C, LC_CTYPE=de_DE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: initrd extends beyond end of memory
[EMAIL PROTECTED] writes: ¡Hola! I'm having problems trying to install debian in my notebook. It has no cdrom, no bootable floppy drive. So i'm using the booting from DOS approach. When it boots it displays: initrd extends beyond end of memory (0xc1d8 0xc1d0) disabling initrd What can i do ? Maybe you have a memory hole (or not) at 15MB. Might cause problems so try togling that bios option. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library reduction problems in recent rootdisk.sh
Stefan Gybas [EMAIL PROTECTED] writes: On Wed, Nov 14, 2001 at 04:09:06AM -0900, Ethan Benson wrote: its easy enough to export it if we need to, i doubt it would cause any harm. rootdisk.sh already exports ldlib (defined per arch), so we can just use this variable. mklibs.py is already used on a arch by arch basis defined in rootdisk.sh, any arch which wants to switch simply needs to add thiers to the test. I've just successfully tested mklibs.py (modified to use $ldlib) on s390, I'll commit the patch in a few hours. Ok. Do that. My sponsor is currently unavailable so I couldn't cvs commit a fix. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.4.x boot floppies, was: Vulnerable SSH versions
Ethan Benson [EMAIL PROTECTED] writes: On Wed, Nov 14, 2001 at 12:42:10PM +0100, Goswin Brederlow wrote: People with such old hardware are probably better of with bo or hamm or potato. They probably need the low-mem target too. which are not (or will not in potato's case) be supported with security updates. I ment that from a hardware requirement point of view. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library reduction problems in recent rootdisk.sh
Erik Andersen [EMAIL PROTECTED] writes: On Tue Nov 13, 2001 at 06:16:23AM -0900, Ethan Benson wrote: # Make the dynamic linker executable -ld_file = find_lib(ld-linux.so.2) +ld_file = find_lib(ld.so.1) ld_file_name = os.path.basename(ld_file) os.chmod(dest_path + / + ld_file_name, 0755) You want to use something like the following makefile snippet: SYSTEM_LDSO=$(shell for each in `$(CC) -print-search-dirs| \ grep ^libraries| sed -e 's/^libraries: //' -e 's/:/ /g'`;\ do ls $$each/ld.so.* 2/dev/null;done) a os.getenv(SYSTEM_LDSO) or whatever its called in the rootdisk.sh should do the trick. I hope it gets exported to subshells/programs. I will look into that. Important is now if there are any archs left with the atexit problem. I only saw one out of two persons, who had the problem, saying its gone now. Please say its gone or try the earlier test and send the output. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.4.x boot floppies, was: Vulnerable SSH versions
Jørgen Hermanrud Fjeld [EMAIL PROTECTED] writes: Hi. Although it might sound stupid, my question is: Will there ever come a time when making 1220 boot floppies with 2.4.x kernel will be doable? If I assume that it's the kernel size that makes it difficult, then it doesn't matter wether we use boot-floppies or debian-installer. This leads me to believe we can't ship with 2.4 kernel until we drop debian support for 1220 floppies. Is this correct? How small can you make a 2.4 kernel? Surely you can get it below 1.2 MB. The ramdisk can be split over several disks, its just ugly. If essential drivers have to be removed from the kernel they can be placed on the ramdisk or preloaded from the drivers disk set. The thing is, do we realy need those disks anymore? Is there any user out there with only such a drive, no cdrom and 12MB ram? Do 12 MB even last for a 2.4 kernel during install? People with such old hardware are probably better of with bo or hamm or potato. They probably need the low-mem target too. Maybe we should add hardware info to the popularity contest package to see how many of each hardware are out there. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library reduction problems in recent rootdisk.sh
Ethan Benson [EMAIL PROTECTED] writes:
On Mon, Nov 12, 2001 at 02:09:52PM -0500, Adam Di Carlo wrote:
Goswin Brederlow [EMAIL PROTECTED] writes:
Good that you start telling.
What do you mean by that? I reported this *months* ago, pleading that
someone fix it.
It still has the atexit problem? What libc version do you have?
I was able to fix this problem on PowerPC I think by fixing the
hardcoded ld.so bit in the script.
no that doesn't fix it. i made the same changes and it fixed nothing.
I can investigate more if needed...
I've got the DEBUG_SPAM output now and from that it should work.
I deduces that it needs atexit from the libc and tells gcc to include
that in the stripped version. But then it won't appear in the stripped
version.
It looks eigther like a gcc bug or the atexit symbol is defined in a
strange way that prevents it from resolving in the stripped version of
the libc.
Can someone with this problem try to run the library reduction on
#include stdlib.h
void bla(void) {}
int main() {
atexit(bla);
return 0;
}
and the libc with nothing else cluttering the output.
Its the same behaviour the broken libc had on i386.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library reduction problems in recent rootdisk.sh
Ethan Benson [EMAIL PROTECTED] writes:
On Tue, Nov 13, 2001 at 12:43:03PM +0100, Goswin Brederlow wrote:
It looks eigther like a gcc bug or the atexit symbol is defined in a
strange way that prevents it from resolving in the stripped version of
the libc.
Can someone with this problem try to run the library reduction on
#include stdlib.h
void bla(void) {}
int main() {
atexit(bla);
return 0;
}
and the libc with nothing else cluttering the output.
Its the same behaviour the broken libc had on i386.
i just tried both your test and a full powerpc b-f build and this time
i had no problems with mklibs.py. libc6 is 2.2.4-5
fine. So alpha, ppc, i386 and m68k work. Anyone other experiences?
we still cannot use mklibs.py until someone fixes the gratuitous
i386ism regarding what ld is called i have to use the following patch
to make it work correctly (well ignore DEBUG_SPAM):
Index: scripts/rootdisk/mklibs.py
===
RCS file: /cvs/debian-boot/boot-floppies/scripts/rootdisk/mklibs.py,v
retrieving revision 1.4
diff -u -r1.4 mklibs.py
--- scripts/rootdisk/mklibs.py 2001/08/11 06:55:18 1.4
+++ scripts/rootdisk/mklibs.py 2001/11/13 15:14:55
@@ -53,7 +53,7 @@
DEBUG_VERBOSE = 2
DEBUG_SPAM= 3
-debuglevel = DEBUG_NORMAL
+debuglevel = DEBUG_SPAM
def debug(level, *msg):
if debuglevel = level:
@@ -352,7 +352,7 @@
base_name = so_pattern.match(library).group(1)
# libc needs its soinit.o and sofini.o as well as the pic
if base_name == libc:
-extra_flags = find_lib(ld-linux.so.2)
+extra_flags = find_lib(ld.so.1)
extra_pre_obj = /usr/lib/libc_pic/soinit.o
extra_post_obj = /usr/lib/libc_pic/sofini.o
else:
@@ -396,6 +396,6 @@
os.remove(dest_path + / + lib)
# Make the dynamic linker executable
-ld_file = find_lib(ld-linux.so.2)
+ld_file = find_lib(ld.so.1)
ld_file_name = os.path.basename(ld_file)
os.chmod(dest_path + / + ld_file_name, 0755)
I have the following on my system:
mrvn@dual:~% ls -l /lib/ld*
-rwxr-xr-x1 root root94561 Oct 30 23:44 /lib/ld-2.2.4.so*
lrwxrwxrwx1 root root 18 Mar 13 2001 /lib/ld-linux.so.1 -
ld-linux.so.1.9.11*
-rwxr-xr-x1 root root24817 Mar 7 2001 /lib/ld-linux.so.1.9.11*
lrwxrwxrwx1 root root 11 Nov 4 05:54 /lib/ld-linux.so.2 -
ld-2.2.4.so*
-rwxr-xr-x2 root root99568 Mar 7 2001 /lib/ld.so*
-rwxr-xr-x2 root root99568 Mar 7 2001 /lib/ld.so.1.9.11*
2fca30cbaccb4c9eccfe46cc26d1317b /lib/ld-2.2.4.so
d4a2c961c9306a2e556aa01b9f3578a8 /lib/ld-linux.so.1.9.11
77328b80b0c4956fa82bbec45cfd8fd1 /lib/ld.so
77328b80b0c4956fa82bbec45cfd8fd1 /lib/ld.so.1.9.11
So which one should be used? Which ones don't work?
Do all archs have an /lib/ld.so and does that work for all?
I would hate to do things differently for each arch or libc version. I
thought with ld-linux.so.2 would be provided by all current glibcs.
May the Source be with you.
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: library reduction problems in recent rootdisk.sh
Ethan Benson [EMAIL PROTECTED] writes: On Mon, Nov 12, 2001 at 04:12:13PM +1300, Mark van Walraven wrote: Hi, Trying to build very-recent-CVS boot-floppies, I get: I: doing library reduction I: library reduction pass 1 531 symbols, 531 unresolved I: library reduction pass 2 607 symbols, 47 unresolved I: library reduction pass 3 607 symbols, 1 unresolved I: library reduction pass 4 607 symbols, 1 unresolved I: library reduction pass 5 607 symbols, 1 unresolved ... etc., ad infinitum. EXACTLY what i have on powerpc Setting debuglevel to DEBUG_SPAM yields: Still need: atexit ditto! Builds ok with mklibs.sh (I haven't tried a test install yet). mklibs.py is broken, but nobody knows why. Good that you start telling. It still has the atexit problem? What libc version do you have? I had the same problem with an libc update some time ago, but several older binaries had the same problem with the unreduced library. Switching back to the previous or next (fixed) libc also fixed the problem in the mklibs.py. I deduced that it was the buggy libc causing the problem so I let it rest. Can you mail me the complete output with DEBUG_SPAM for a few iterations, say 5. Same for ppc please. May the Source be with you. Goswin PS: Try do delete the downloaded libc and rebuild. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: busybox bloat
Ethan Benson [EMAIL PROTECTED] writes: The root disk is currently too bloated, on pmac and chrp its already too large to fit on a 1.44MB floppy. Did you use mklibs.sh or mklibs.py? If the former try the later. And please, if mklibs.py doesn't work send me a logfile with verry verbose output in mlibs.py. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Why msdos and not vfat?
Eduard Bloch [EMAIL PROTECTED] writes: #include hallo.h Goswin Brederlow wrote on Mon Aug 06, 2001 um 03:40:51AM: Why do most archs use msdos.o and only ia64 vfat.o? I did make a patch for this a long time ago to use vfat.o if present and fallback to msdos.o. Seems like nobody bothered to check that in. I think you mean something like the attached. I mentioned this also in another thread. No, I mean that while building the boot-floppies. The shell scripts and makefiles use fat and won't use vfat, except for ia64. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mklibs.py fails on powerpc
Adam Di Carlo [EMAIL PROTECTED] writes: We seem to have some sort of problem on PowerPC with mklibs.py: I: library reduction pass 1 526 symbols, 526 unresolved I: library reduction pass 2 561 symbols, 5 unresolved I: library reduction pass 3 561 symbols, 1 unresolved I: library reduction pass 4 561 symbols, 1 unresolved I: library reduction pass 5 561 symbols, 1 unresolved I: library reduction pass 6 561 symbols, 1 unresolved I: library reduction pass 7 ... What would this be caused by? Did that go away with the newer libc? If not, please add some debug info (look at the source for the realy verbose setting) and send me the logfile. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PLIP install (was Re: Still no base tarball)
Adam Di Carlo [EMAIL PROTECTED] writes: Nick Phillips [EMAIL PROTECTED] writes: Aside: were it not for the flexibility of the Debian installtion process, I'd probably still be using slackware right now. I had previously been put off by the fact that stable appeared to be rather out-of-date, and the err, cough, interface to ds... cough... was a little unf... cough. I was able to install onto a 486-50 laptop with 4MB RAM using 7 floppies (created on a slackware box) followed by nfs over PLIP (no Adam, no network either). None of the other major distributions would install on that box *at all*. Having installed the system, and been forced to learn a little bit about dselect, I was converted. I'm curious. Does PLIP work in the woody boot-floppies? Are there things we could do to make installation via PLIP network easier? An important thing to notice in the docs is that plip seems to need the irq _and_ io set when loading the module to work properly. I tested it with several systems and archs and it never worked completly without options (even though it said it would use correct irq and io settings after probing). The symptoms are that all seems to be correct but plip just gives timeouts. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PLIP install (was Re: Still no base tarball)
Philip Blundell [EMAIL PROTECTED] writes: An important thing to notice in the docs is that plip seems to need the irq _and_ io set when loading the module to work properly. I tested it with several systems and archs and it never worked completly without options (even though it said it would use correct irq and io settings after probing). The symptoms are that all seems to be correct but plip just gives timeouts. I don't think this is the case any more. Using `irq=auto' should be enough. p. 2.4.7 failed (plip said it wouldn't have an IRQ), 2.4.9 seems to work (it reports an irq for use). But my plip partner is off, so I can't test if it realy works. Better mention it in the docs because its hard to see the problem if the kernel reports the right irq/io settings but still fails. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Alpha boot-foppies successes and failures cvs-2001-08-03
Adam Di Carlo [EMAIL PROTECTED] writes: - Configuring modules segfaults I'm pretty sure this is fixed now. - installing base segfaults and gives return value 139 I believe this is fixed now, no? Both were ash failures. 4) When installing files via NFS it doesn't work to list possible dirs, one has to specify the correct dir manually. This might be a general problem, not an alpha problem. We should track this down or file it or something. I just tried installing from harddisk. Once it worked and found the stuff, the next reboot it didn't. Most curious. Well, it would be helpful to look at the bug already filed for this, and followup to identify exactly what circumstances causing it to fail. Also the /instmnt is still there and still confusing. I don't think it would be best to remove this. Rather there should be verbage on there explaining that the mount point for the server already mounted is /instmnt. You select server:/path/to/the/dir and that gets omited as well. That's the server name, not the mount point. Theres realy no reason for the gui to tell where the nfs is mounted temporary. We happen to disagree. I assume that poeple will be doing things in tty2, at least some of the time, and this helps with that. Furthermore, the user could make other mount points or whatever. It still makes no sense to have it in the selection. People just get confused and delete it and then nothing works. If you want mention that the nsf will be mounted at /instmnt but it just makes no sense that i can I select anything outside the nfs mounted fs in that selection. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc-2.2.4.so breaks library reduction with its atexit() bug
Ben Collins [EMAIL PROTECTED] writes: On Sat, Aug 11, 2001 at 03:51:43AM +0200, Goswin Brederlow wrote: Hi, better not use the new libc-2.2.4.so. Apart from sveral programs not running anymore the library reduction seem to go into an endless loop due to it. What programs? I'm using 2.2.4 on sparc and the library reduction worked just fine, and no programs have failed. Ben rar for example. Its the atexit problem you probably fixed in libc-2.2.3-10.0.1, haven't tested that yet. The loop also has problems with atexit. -uatexit is given as paramter to the gcc reduction call but the resulting lib doesn't contain atexit. That was the behaviour on ppc. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Library reduction on Alpha (was: Re: Alpha: aboot rescue disk)
Christopher C. Chimelis [EMAIL PROTECTED] writes: On 8 Aug 2001, Goswin Brederlow wrote: A short add on to mklibs.sh. As I see it it looks for symbols that are in two files, i.e. ash and libm, and includes all matches. It thinks that all symbols that match names will be needed in the library. Unfortunatly that will keep any and all symbols with all duplicates in the library, so instead of using libc's math funktions it keeps libcs _and_ libms. Ah, ok. So, if I understand this correctly, you want to only keep the symbols in libc/libm that are needed by the binaries on the boot floppies, correct? If so, I may have a scheme to do this, but I would have to see Yes and now. mklibs.sh keeps all symbols needed, mklibs.py keeps only one instance of each symbol needed. We want that set of instances of symbols that results in a minimum of space. Thats a NP complete problem, in general. So up to now we made a few assumptions: - the problem size is small. :) - all binaries are roughly linked against the same set of libs - duplicate symbols can savely be ignored, just pick one (thats an extension of the previous one) - versioned symbols will be ignored, or rather the version tag the scripts first (I'll check them out of CVS probably tomorrow) to make sure they don't already try that :-) mklibs.py on the other hand includes each symbol only once. Theres a small hack to prefer libc symbols (althout not realy needed since libm seems to be after libc) but otherwise its a first come first use basis. Ok...this script probably does what I'm thinking about then. Is this one working well enough or do you want to shrink it even more? If we can, sure. But the only thing that I see left si to remove versioned symbols and leave only the right version or the minimal set of version required. But does that realy help? Its probably just some stubs that get removed by that. Another idea would be to use a smaller (but slower) libc and to optimize for size. Currently the root.bin fits, so unless someone adds more the jobs done, but that just a lazy programmers attitude. :) MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: proposal: using isolinux to boot CDs...
Erik Andersen [EMAIL PROTECTED] writes: I was playing around earlier this week with making bootable CDs and discovered something I think will make the boot-floppies a lot easier for x86, perhaps allowing us to avoid building all the different kernel floppies we currently build for x86. I propose we usr the isolinux bootloader for the Debian x86 CD-ROMs. http://syslinux.zytor.com/iso.php Isolinux is a new bootloader written by hpa and included in the latest syslinux package (sharing much of the syslinux code). It is designed for use on ISO9660/El Torito CD-ROMs operating in no emulation mode, bypassing the need for limited space floppy emulation mode images... Instead, of going through Sounds nice for cdimages. Can you write up some code that generates a big image with all the basics on/in it (rescue + root + drivers basically) and generates a bootable iso with that? No base (since its not being build by the bootfloppies [yet?]) or further packages, just the minimum to get everything working and to prove it works. the pain of forcing the various kernels to the kernels fit onto a single floppy, we would just create a /isolinux directory on the CD-ROM and populate it with an initrd file (however big that needs to be) and as many kernels as we want of whatever size the kernels need to be. Then we provide a isolinux.cfg file (exactly the same syntax as the existing syslinux.cfg file) that allows people to select the kernel to boot with (with a timeout for a sane default). And if we want to be fancy, isolinux can even display a graphical spash screen... Slackware 8.0 is already using isolinux to allow people to select on boot whether they want ATA100 or the scsi kernel, or any of about 6 choices. I think this is something to seriously consider... Granted, those needing to install exclusively from floppy (as opposed to CD-ROM) could not benefit. However, for the vast majority of x86 systems, this would be a big win since it would greatly ease the pain of finding the right kernel image needed to boot and install Debian, I allways just put in the first CD or the resc1440.bin and bootet. No problems ever finding them. :) MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
(alpha) YES, we have working boot-floppies
Hi, YES, its true. The boot-floppies work. Fixing the latest ash to build on alpha solved not only the Configure Drivers problem, but also the Instaling Base failure. One now gets a completly running system. No more segfaults or error 139. I found another bug though: task-sel seems to quit emidiatly or doesn't get started. So here is a remaining TO-DO list: 1. get a fixed ash into the archive 2. resolve that e2fsprogs-bf, sysvinit, modutils problems and remove the workaround 3. milo bootdisks 4. aboot/e2bootwrite 5. task-sel 6. docs 7. more testers May the Source be with you. Goswin PS: Great work by the way. The installation is way better than potato. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Library reduction on Alpha (was: Re: Alpha: aboot rescue disk)
Falk Hueffner [EMAIL PROTECTED] writes: Christopher C. Chimelis [EMAIL PROTECTED] writes: On 7 Aug 2001, Falk Hueffner wrote: Yes, it acually doesn't seem to make any difference. With mklibs.sh: What exactly does this script do to libc (or really, what isn't it doing now)? There are some binutils issues that I'm working on that may be related... The only difference between the two scripts is how the set of symbols to be incuded is determined. mklibs.py simply adds missing symbols iteratively until everything is satisfied. mklibs.sh does something different (I just realized that it doesn't do what I thought it did... unfortunately there's no real documentation... Hm, I'm afraid somebody else will have to tell you how it works :) You can find both scripts in the boot-floppies CVS, in scripts/rootdisk. Well another difference: mklibs.py uses readelf insead of objdump, since that seemed to be slightly easier to parse. Main reason for readelf was objdump failing on some files. Can't remember which though. Falk MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Library reduction on Alpha (was: Re: Alpha: aboot rescue disk)
Falk Hueffner [EMAIL PROTECTED] writes: Christopher C. Chimelis [EMAIL PROTECTED] writes: On 7 Aug 2001, Falk Hueffner wrote: Yes, it acually doesn't seem to make any difference. With mklibs.sh: What exactly does this script do to libc (or really, what isn't it doing now)? There are some binutils issues that I'm working on that may be related... The only difference between the two scripts is how the set of symbols to be incuded is determined. mklibs.py simply adds missing symbols iteratively until everything is satisfied. mklibs.sh does something different (I just realized that it doesn't do what I thought it did... unfortunately there's no real documentation... Hm, I'm afraid somebody else will have to tell you how it works :) You can find both scripts in the boot-floppies CVS, in scripts/rootdisk. A short add on to mklibs.sh. As I see it it looks for symbols that are in two files, i.e. ash and libm, and includes all matches. It thinks that all symbols that match names will be needed in the library. Unfortunatly that will keep any and all symbols with all duplicates in the library, so instead of using libc's math funktions it keeps libcs _and_ libms. mklibs.py on the other hand includes each symbol only once. Theres a small hack to prefer libc symbols (althout not realy needed since libm seems to be after libc) but otherwise its a first come first use basis. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Alpha milo bootdisks, can we use SuSes?
A set of milo disks can be found at ftp://ftp.suse.com/pub/suse/axp/current/disks I just tested the ruffian disk and it works. The disk contains the first stage loader and the milo image and nothing else so we can just take them as they are. No changes needed. Since nobody complained about using the newer milos from SuSe I think it would be save to just take all those bootdisks instead of building our own milo disks. Should the boot-floppies script download those disks or do we just copy them into the debian mirror with a readme.txt explaining their origin? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFS Boot Disks
Constantin-Marius Moisescu [EMAIL PROTECTED] writes: Hello all, I was just wondering if there are any plans to make it possible to select XFS as a filesystem during the install of Woody. Or will it only be EXT2? Will Woody use the 2.4-series kernel during the installation? If so, it would be relatively easy to add support for XFS, ReiserFS, JFS, or any other file system (modules +initrd). reiserfs seems to be already included. i386 builds a disk set with reiser in its name. Haven't tried them yet though. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libm on root-filesystem?
Hmm, Falk says the attachment is garbled, try this: ftp://rut.informatik.uni-tuebingen.de/boot-floppies/ MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New console-data deb causes problems on ia64
Philip Blundell [EMAIL PROTECTED] writes: Are any other arch's seeing this, or is it just ia64? I see this too, on ARM. p. I see this too, on i386. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
documentation is broken in the cvs
Hi, here it comes for all the sgml experts: ** making documentation for language C make[1]: Entering directory `/usr/local/src/boot-floppies/documentation' make all KVER=2.2.19 ALTKVER= utillinux= amigafdisk= atarifdisk= macfdisk= pmacfdiskcross= make[2]: Entering directory `/usr/local/src/boot-floppies/documentation' rm -f messages.ent ln -s messages_C.ent messages.ent rm -f dynamic.ent ln -s dynamic_C_i386.ent dynamic.ent debiandoc2text -d /usr/share/sgml/debiandoc/dtd/sgml/1.0/debiandoc.dcl -l C -O install.sgml install.en.txt saspconvert: en/dbootstrap.sgml:8 (input line 4525): indentifier dbootstrap-intro is defined more than once saspconvert: en/rescue-boot.sgml:934 (input line 3833): indentifier dbootstrap-intro originally defined here saspconvert: en/dbootstrap.sgml:35 (input line 4580): indentifier dbootstrap-shell-log is defined more than once saspconvert: en/rescue-boot.sgml:966 (input line 3888): indentifier dbootstrap-shell-log originally defined here saspconvert: en/dbootstrap.sgml:65 (input line 4661): indentifier dbootstrap-welcome is defined more than once saspconvert: en/rescue-boot.sgml:997 (input line 3971): indentifier dbootstrap-welcome originally defined here saspconvert: en/dbootstrap.sgml:72 (input line 4679): indentifier dbootstrap-title is defined more than once saspconvert: en/rescue-boot.sgml:1004 (input line 3989): indentifier dbootstrap-title originally defined here make[2]: *** [install.en.txt] Error 1 make[2]: Leaving directory `/usr/local/src/boot-floppies/documentation' make[1]: *** [uni-docs] Error 2 make[1]: Leaving directory `/usr/local/src/boot-floppies/documentation' make: *** [all-lang-docs] Error 2 MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
root disks are too small on i386
Hi, I had to change the size of the root disks on i386 because the default 3200 blocks run out of space. Did anyone else experience that problem? I'm building todays CVS on yesterdays sid-i386. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New bootdisks / first install report / help needed
Falk Hueffner [EMAIL PROTECTED] writes: Adam Di Carlo [EMAIL PROTECTED] writes: Helge Kreutzmann [EMAIL PROTECTED] writes: I can try them on a ruffian which is currently out of production due to some technical difficulties and on my LX, maybe on an XP1000. Regarding my LX I cannot complete the installation due to missing network (i.e. only modem). How is a milo based system supposed to be booted ? I see special disk for nautilus and jensen but no for milo based systems. I'd have to leave that to an Alpha porter to answer. I'm afraid the documentation probably won't be much help. I know about two MILO systems: Those with AlphaBios, and the Ruffian, which has an ARCS-Bios (and I actually know only about AlphaBios first-hand). Both understand the FAT filesystem, so you need a FAT-formatted Floppy with the correct milo and linload.exe, which is a tiny program that gets started from the bios and loads the MILO. We could either provide the MILO images and instruct the users to prepare such floppies, or provide complete floppy images. The latter would be more wasteful for the mirrors since the milo only takes about 400k, so we waste about 15MB mirror space, but I'd actually prefer it, makes things easier for the installer, no problems with finding a mkfatfs, getting file names right etc. Most importantly we need docs. I tried to install suse-axp (*hide*) to write a test report on my Ruffian and couldn't get it past the bios at all. I have never been able to boot anything but the harddrive, which came preinstalled. I changed the milo and harddrive a few times, but always bootet from harddisk. The ARCS Bios is very precise in what it wants and not very helpfull in telling whats wrong. It seems the files have to be in proper subdirs even though you specify the full path in the bios. So I don't know if one can even boot from floppy or cdrom. If anyone knows about some docs for this I can try to make a floppy or cdrom boot. I wanted to hack that part anyway, OK if I give it a try? Falk Since he's practically living next door you would have two people working on it and 2 alpha archs testing it. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Why msdos and not vfat?
Hi, me again. Why do most archs use msdos.o and only ia64 vfat.o? I did make a patch for this a long time ago to use vfat.o if present and fallback to msdos.o. Seems like nobody bothered to check that in. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Alpha boot-foppies successes and failures cvs-2001-08-03
Hi,
I build a set of bootfloppies yesterday from cvs (cvs-2001-08-03) on
Alpha/sid.
I run across the already mentioned problems so I won't elaborate on them:
- sysvinit (workaround by Falk Hueffner)
- library reduction (root.bin is a bit to big)
- Configuring modules segfaults
- installing base segfaults and gives return value 139
Now, what did work and what didn't thats new:
1) The tfpboot.img is not build but is later copied
===
RCS file: /cvs/debian-boot/boot-floppies/Makefile,v
retrieving revision 1.374
diff -r1.374 Makefile
141a142
./tftpboot.sh linuxgeneric root.bin tftpboot.img
Index: common.sh
===
2) The driver disks are called driver${subarch} and not
driveralpha_${subarch} and the root is calkles root.bin and not
root.tar.gz
===
RCS file: /cvs/debian-boot/boot-floppies/release.sh,v
retrieving revision 1.111
diff -r1.111 release.sh
864c864
mv $release/driversalpha_${subarch}.tgz \
---
mv $release/drivers${subarch}.tgz \
866,867c866,867
cp linuxalpha_${subarch} $targetdir/linux
for drvdisc in $release/images-1.44/driveralpha_${subarch}-?.bin
---
cp linux${subarch} $targetdir/linux
for drvdisc in $release/images-1.44/driver${subarch}-?.bin
869c869
drv_number=`echo $drvdisc|sed s/.*driveralpha_${subarch}-\([1-9]\
).bin/\1/`
---
drv_number=`echo $drvdisc|sed s/.*driver${subarch}-\([1-9]\).bin/
\1/`
886c886
cp root.tar.gz $release/
---
cp root.bin $release/
902c902
images-1.44 linux tftpboot.img root.tar.gz *.tgz)
---
images-1.44 linux tftpboot.img root.bin *.tgz)
Index: sources.list
===
3) The milo and apb files where not downloaded. I downloaded the new
milos from SuSe and linked them accordingly. I didn't see a ldmilo.exe
and linload.exe, so I used the potato version. Not sure if that will
work. I haven't actualy tried the milos yet but used my old one.
4) When installing files via NFS it doesn't work to list possible
dirs, one has to specify the correct dir manually. Also the /instmnt
is still there and still confusing.
5) Installing base does not cope with /proc being mounted already
6) How do I format the DOS partition needed for milo?
7) I created a new DOS partition and I have one with my current milo
on it, but still the install told me that I have no DOS partiton so I
can't make the system bootable.
I have a Ruffian system and I'm one of those hit with network
problems. Does anyone know if the docs say how to cope with it? What
to try to make it work, what boot paramter to use to use de4x5 instead
of tulip? If not we should add that. I can write something up if
someone corrects the grammar and spelling.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#107377: boot-floppies: configure device driver
Carpenter, Dean [EMAIL PROTECTED] writes: On Wed, Aug 01, 2001 at 07:16:01PM -0400, Adam Di Carlo wrote: tags 107377 + moreinfo thanks You need to look in the logs and tell us what it says there. /var/log/messages has nothing unusual (shortened): kernel and modules was installed successfully moving away /lib/modules to /lib/modules.old making /lib/modules a link to /target/lib/modules but it still does not show the menue to configure device driver modules. i didn't find any other log files I tried to start modconf manually on the second console and it complained about /usr/share/something and failed directly. I linked /target/usr/share - /usr/share and then it gave the usual segfaults and crashed the console. It wasn't possible to type anything there anymore. Only ctrl-c gives you a new prompt one line down and a bit more indented. I can corroborate this with a little more information. Installing with a full diskette set works fine. rescue, root, then the 4 drivers disks does a working install, nice and clean. Did you compare the contents of the disks with the tgz? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libm on root-filesystem?
Falk Hueffner [EMAIL PROTECTED] writes: Adam Di Carlo [EMAIL PROTECTED] writes: Adam Di Carlo [EMAIL PROTECTED] writes: Thimo Neubauer [EMAIL PROTECTED] writes: On Wed, Jul 25, 2001 at 09:42:28PM -0400, Adam Di Carlo wrote: Thimo Neubauer [EMAIL PROTECTED] writes: Ouch. So its that libslang itself should be reduced, and based on that, the usage in libnewt should be reduced? Almost :) First libnewt needs to be reduced, then libslang and after that libm, so that only the really needed math-symbols get in :( I'll take a swipe at it. Ok, this is done in CVS. Can some people test this? Hm, I've not tested it, but in any case mklibs.sh seems to be getting more and more ugly. I've considered rewriting it in Python, using an iterative method where I simply add symbols until everything is satisfied. Shell is just not the language for such stuff. Does that look like a good idea? Would add another build dependency, but we have a gazillion already ;) I (nesarly) finished the python script Falk started tonight. The good news is that it sort of works, the size is a bit smaller and libm is reduced to 0 Symbols and 3K. The bad news is that even though I can chroot with those libs and run programs and all, they all segfault when done. I dunno why. I will compare the symbols included with both scripts, maybe theres something missing. I'm suspecting that its one of those special cases done for libc or some other extra case I overlooked in the mklibs.sh and thus didn't translate. Last thing to mention is the speedup. the mklibs.sh needs 6 minutes, the python variant about 30 seconds including debug output. So, who is an elf expert? What could be wrong? Anyone intrested in the code? The mklibs.py can be used instead of the mklibs.sh as it is, same arguments used. It then creates lib-so-stripped files that have to be moved to lib (or rather that what the lib link points to) manually. MfG Goswin --[[application/octet-stream; type=gzip Content-Disposition: attachment; filename=mklibs.py.gz][base64]] H4sIABTDbDsCA+1ae3PjthH/X59iS2UayRZp+zJNc7q6ic6PO098tkeyc7mxHAUiIYkxSagE aVvN5Lt3FwBfEiXdw5nOdKrMxSSw+8NiX1gAbP4F9lIZ7439aG++SGYieuHsNxpNCO8Dfyyd +aILvQhYmoiQJdyDR7aARIAbc3wFBqEf+SELYA/J98DzY+4mIl44jSaCHIn5IvanswQOXr58 CeMFnLLgHt6mfDKJeAx/hTdCPvoRvI65x+NAPCo2M7acEcc7FrupRAo/ug9ZFME/dIuTt/wQ p7PYTiPfHgt3loaOx/+JKKlEcZmEhIfzAIUlaGwGuJ75EuaxmMYsBHycxJyDFJPkkcX8FSxE Ci6LAEXyZRL74xQn6ifAIm9PxBAKz58sFBA2phHKDcmM4zBxKEFM1Mubixt4w3GKqJmrdBz4 Lpz7Lo8kJ4nm1CJnKN5YAxHLKUkxMFLAqUBklvgiegXcx/4YHngs8R1eZIMYxA6IWKG0WELC xyDmxNhGiRdAM895nTUaKCbqAVqDwGdijnOaISTO8tEPAhhzUukkDToKA6nh/dn128uba+hd fID3vX6/d3H94RVSox9hL3/gGstHA/jKd+KYRckCJ6Ag3p30j94iT+/12fnZ9QecB5yeXV+c DAZwetmHHlz1+tdnRzfnvT5c3fSvLgcnDsCAk2BcIWzQ80TZClXp8YT5gczm/gHNK1G+wIMZ e+BoZpf7D+Qq4KK7bregQmGBiKZqpkhdKPMV+BOIRNKBx9hHt8FIWbGt4i/s24GzyHU68LeX cE2eyuEqYC5adZASwjff7HfgtZAJUb7rAey/ODg4sA++2f87wM2gR7H69vI9nF3D+8v+jwM1 SxveMOUzDO2WRjGXIqApykU4FoEkVwYMsZjFPpcQcQw+8kUlq5mJ1GKe/fzupKvoMRxSl5f4 lsfJwBHgwS8BsgBzhbeoBUCnjUTEQWhHmfixTGDOpGwr9LNJBZkCI0d/5OrdQ3ZFOyVVxyKd zhRPMT0tfMjDMQr6SB6t8RIacpEB1mGs0VzI4nstbhq5ZEJJQU3pRoGQ43HmzowIi66aJ7b7 yDtHP5r4aOSWdhQcnkseJdr3CJ0ica7gpWgbVleEc2LC2BRRsNCpzYhkSBSbGn/M3PvM8RIx bzQw/ERMI4SYLT2ZvRNHNM3e0C+z9kVOIvKnaSDG+TNH2KTRcAM0FIZj0m2gCBhnExiNcDlI RqOW5MGkrdvpR6/OaOT5bgKH8PsfjZyDeZ4ixiw2/q2e4xZ77pDtoOByRYRBHcla1pgnaRyV EZwZk6N7vmgRYYES8njKDYQsASgLkrKlwwMeylapL5eNBOclME25NO8aUVAMBGyUVIaGWNWY 4fx1lfVXCnnTzdDJMGIwZwV+xNXyg5l3niZZGsMJe2k4z4zf0MpTzy3ztwM7LJ5m82/O0Sty Z+kYL3F+E37UIrIOWGC1G+XJaQqJOT7JMKVDTqIkaeVTMn2wC1/jf7s10NjebuOfYfR1m2Z5 6ge0eplZMtcVsYcs5N0Mh5/yp3nmCtRMmaTVhilG8NyBvhIPURjqP3HU1DXPRMG2CLRjmjqa K4rJz4wq5ixBsghbYu6YEGxp8kwBMg3IoTEGWrqJXOeJXIfAC2ti7YQJQQGpx5bB7sBTOyfC jKA6q86mB1HupnodJWjLiNs2nmRsoYnXOEiWEFWWx9DFHILugfUaFgB8ztEyIlJaMolrpFtl qwgvFLFFWUtIB63Bperr0Ovp6PLHdtl/mY+LsHWE9RnSq9yHsF30nl0aVdEZVz3MPdIy7mqh l9k2euIDVi/2DJcPrF8sHefV6ZbMqdHQoJazc3FycnxyPJQ7reFgt/0VOmzdxEZT1x1hW8RC /pyzfJ455pyZu7Jw7DF46maBQ8O1nhAGhwwdKaw2HB6CfdAxrEsw25WFOEpfQwRzdr4yYW4W Ks2xmhCNKSxLtfBA8tU+O7CW4r2KRkkFaYyVqKbGuXFvZJa4P8k0zS228RboGL5roxQVwzS3 ed/NxbGzM5S579X7AVVFmNzVWJ9p+IvL6w9XJ1vsvhVlcHJ0fXZ58aUwvdeDL4U4vzzqndeD bNP5UKLWUee3v/wwlHe77dYPzm77+zzys7Lxv+xSK6708bohr9qp101T1+moHKxaFwYK07xA aZHu+08eCk25bqjtdqi4/SZ6VbnW/mLrl9t9+yWzJ3e7Q7l7O328wz/OTrmxtf/03e3+d3ft 7/MhO/AiU8hzgKIrKUcaDnbIkxT6nxfLaN4vDZ//p4PCDb3d7lDeDj20bE8b18F/2FwxrEkR hEhF04y2TlTCJVwmtDmi1EHiUJWA9eLYJAMiwQpupgu98Yieu+U6rlUkE0W3C9Ye5Qkkrs0s pSkt01fqO1xlN4qJ28uSmFKMamtYq+XsqEW+5aBC2rtGA2Mm+YhqoXKhWmB0svKpbUrQA82m Nww580coiHonZj9LG0uH/ldVVCELtuzQvBxmLSmsqmcCXKvbkgqJ7hNVOgrZ/H9WrTi3P1Gx ehZmDWxZE4FVaqNZecdAH7OYFmpDvbz9sNTpdCCJcx0FnWEHwmWBon3iIXM30htEHHsL62ox uirOSnGhQX8+OOh/q87F8R++UFX97UYuQ+sqSueAaMmokiz6MeRFdd4sXEiiYuVCOvwJ9+f7 pOaaH+48cYy6HiSHG8mmvAvOXn4rALeXV7RK3DmOA7YHxyeDa6xCzk8AG4jlHbvneudNm8/s lqDYhE7UYa+mp+nlNwcKSkHQv0t1lC279Axgn8PxWR/Xp8v+hyUn7HleqS8Rmc1RAhbj3pvC
Bug#80862: boot-floppies: I can't mount an NFS share as my root fs
" " == idalton [EMAIL PROTECTED] writes: On Mon, Jan 01, 2001 at 04:03:44AM -0500, Adam Di Carlo wrote: [EMAIL PROTECTED] writes: Package: boot-floppies Version: 2.2.20.0.1 Severity: normal I'm trying to install an NFS root/diskless system. I get the network configured, then I select 'mount a previously-initialised partition', and then I select 'nfs' (which is the only option listed). And then I get dumped to the main menu without anything asking about my NFS server and path.I'm booting with the 'debug verbose' options set, and there are no messages in the log at this point. Is dbootstrap seg faulting? Init should say something. It's hard for me to test this, unfortunately. The only message that appears is the one saying there isn't a /lib/modules/foo/modules.dep, which appears on the console and gets overwritten by the dialogs. Say, might NFS support have been disabled at some point? Have a look weather the nfs.o module gets loaded and if no, if its loadable by insmod. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Boot Virus
Steve Bowman [EMAIL PROTECTED] writes: On Fri, Sep 29, 2000 at 12:40:33AM -0400, Adam Di Carlo wrote: "Christopher Dryburgh" [EMAIL PROTECTED] writes: Thankyou Macan. I will look into it. Just some extra information. I only run into the single user shell and need to use fsck when booting from the hard drive. Booting using the floppy does not cause this to happen. There is something about booting from the hard drive that corrupts the file system. Other wise I would not need to use fsck when booting from hard drive. Just turning off the switch that monitors for boot viruses would not solve the problem if there is a virus. I've run Linux since 1995 and I've never had a boot virus on a linux box. It's only single-users insecure operating systems which have this problem. The user is correct, disable the BIOS warning. that may or may not fix your problem. If not, I would look at the partition tables again and make sure they are kosher. But given the boot from floppy vs boot from hd scenario, I'm quite sure your overachieving BIOS is to blame. Furthermore, the installation instructions tell you to turn off BIOS virus protection (section 3.3.4). I assume there's a reason someone bothered to put it in the instructions. First the Virus Protection in the bios should disable any write access to the MBR and the bootblock by non authorized programms. (How should that ever work :). It also should detect any unusual mbr/bootblock on the drive and not boot it, so that when a virus is present it is recognised and not executet. The Problem is that several old bios think that Linux (lilo) is a virus and refuse to boot it or they prevent lilo from writing the mbr, so linux is not bootable. Any bootvirus present on the system will be disabled when starting linux, unless its something as complex as vmware or plex. After that lilo can overwrite the mbr and thereby delete the virus. When booting the bootdisks no virus is startet at all and any boot virus on the drive will get overwritten as well by the lilo installation. Turn the Bios off for installation and turn it on if linux still boots with it on (if you use some risky M$ OS). MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debinst: non-msdos partition table creation support
Glenn McGrath [EMAIL PROTECTED] writes: Junichi Uekawa wrote: On a PC, BIOS needs to be able to read it first, before anything else. regards, junichi Are you sure ? I can understand that this would be the case for OS's that use the boot indicator flag to work out which partition to boot from, but linux doesnt use this, and pretty much ignores the BIOS for everything. You need the MBR, everything else can be changed if your mbr handles that. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debinst: non-msdos partition table creation support
Glenn McGrath [EMAIL PROTECTED] writes: I understand how msdos partition tables work now, its just a bunch of ugly hacks to make use of legacy structures that are long obsolete. msdos partitions need to be supported for machines that need microsoft compatability (and other OS's ?), but i think that we should provided users the ability to create a non-crap partition table. You need them to boot. There are heaps of other partition tables formats around, i dont know much about any of them though, i will look into it. I think the nicest one comes form AmigaOS. No limitations and enough space for aditional infos. You can even put the filesystem to be used onto the disk for bootloader that need it (which none do because dos partitions cant). MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: busybox in main
Glenn McGrath [EMAIL PROTECTED] writes: I would like to see the busybox package in the main debian archive. Busxybox is a multicall binary that is targeted at embedded systems, it is the basis of the debian installer. Me too. I realy need it for my demofs and stealing it out of the boot-floppies sources or duplicating its source in my package is stupid and ugly. A busybox package was previously rejected because it was uninstable on an existing system. This was because busybox would break packages in base due to the many links it created (e.g. symlink from //bin/ls to busybox binary). Infact due to conflicting dependencies it wouldnt have been installable without being forced. The proposed solution was to create a seperate area in the debian archive for installer specific packages and put it in there, for whatever reason this hasnt happened, but i dont think the busybox package should be hidden away anyway. Why not make a perfectly normal package and a spezial script that will dump the neccesities into a directory (for the boot-floppies package and my demo-fs) and maybe a downsized package living in disks-arch/something (for the new installer scheme floating around)? busybox doesnt actually need symlinks to provide functionality, it can be used by calling busybox with the command as the argument, e.g. busybox ls -al. busybox isnt only usefull for debian in the installer, it could be a handy emergency utility to have hanging around on an installed system. If the busybox package was setup so that it only installed the busybox binary then it wouldnt cause any problems and it would make it more accessable to both end users and the installer. A policy compliant package would be fine for this and for building the bootfloppies or rescuedisks or a demo-fs you could provide a little script that installs the binary and (if wanted) hard/soft-links to a given directory or a script that cleansup unneccessary stuff after installation. May the Source be with you. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alternative root filesystem support
Glenn McGrath [EMAIL PROTECTED] writes: "Karl M. Hegbloom" wrote: "Goswin" == Goswin Brederlow [EMAIL PROTECTED] writes: Goswin Hartmut Koptein [EMAIL PROTECTED] writes: Let's add one more bullet point for the new installer--namely, alternative root filesystem support. I and my colleagues would just love to see ReiserFS support in woody's installer. Why reiserfs? reiserfs is the bad guy, it doesen't support other architectures then intel and only the 32 bit part. Goswin Doesn't reiser also have problems with raid and lvm? I spoke with a guy the other night who says he set up a reiserfs on a raid with lvm, iirc. I'll try and have him put in here, if I can find his email and Cc him... Hey, Anthony? What can you tell us about this? Do you really know how to set up Reiserfs on RAID with lvm? raid and lvm are different storries, although lvm can do striping. I think reiser only had problems with raid5. For the woody installer it shouldnt be too difficult to handle reiser, lvm, raid, partition resizing etc. A lot of places to change for the current dbootstrap. Trust me I hunted them all down to get devfs working. As long as we have access to the module (or package) archive prior to creating the root filesystem we download whats required to make a raid partition, or reiserfs, and run it through a debconf menu to control its functionality. One possible problem is that the modules we have the more demanding we will be on ram size as its all in ramdisk. Anyone who wants raid/lvm/other fancy stuff on his root partition should have a bit more ram than lowmem users. Also note that lvm on 7 is not possible without initrd tricks (which is rather stupid of lvm). An alternative to the everything in ramdisk idea would be to setup a loopfs somewhere on a local disk. This would complicate partitioning as we would have to check and maybe move the loop filesystem to another partition if the loopf is residing on the partition to be worked on. If all else fails, take some out of swap. Is ramfs swapable? If so, just use that. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot problems with potato and scsi
Adam Di Carlo [EMAIL PROTECTED] writes: Pierre Burri [EMAIL PROTECTED] writes: Where do I find if it as a vanilla or a compact CD? (Sorry I'm new to Debian...) In the README.txt I found: This CD-ROM is labeled Debian GNU/Linux 2.2 r0 "Potato" - Official i386 Binary-1 and I have the 3 Binary CDs. I belive compact is the 2nd CD. I wonder why people don't go ahead and try all 3 or 4 cds they get. Isn't it mentioned that all (most) of them are bootable? Never read the docs though, just grew up with it. May the Source be with you. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Initial install using apt
Chris AtLee [EMAIL PROTECTED] writes: Hey there, Is there a boot disk out there that doesn't need any of the base packages, but instead has all the necessary software to get a network connection and apt up and running so that you can install everything off the internet? It would be great to be able to carry around a bootable mini-CD (one of those business card shaped ones) with all the software on it to install a brand new debian system. Its enough to have rescue, root and drivers on the cd and install everything else via net. But since theres more space on the CD (even business card shaped once), add base and stuff needed for isdn to it and you have the perfect install CD. Alternatively wait for my Debian Demo FS, which will boot up X and lets you configure your network, irc, browse the net, play moonbuggy or install Debian in an xterm. I'm just waiting for 2.4.0 to make an initial release. May the Source be with you. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Floppy boot to Harddisk Boot
"TODD WITTER" [EMAIL PROTECTED] writes:
Hey list!
I have a question about booting into debian. During installation I
did not want to have lilo installed on the mbr. I chose to boot from
a floppy. I also run rh6.2 and win9x on this little machine. I boot
into redhat with a floppy and it goes lickity split! ("/" is mounted on
hda5). Right now "/" in debian is mounted on hda9. I used to have
stormix there but I overwrote it with debian potato. STormix, too,
booted up lickity split when I booted from a floppy. I can assume
that's because the kernel is already on the hard drive. Can I do the
same with debian? When I boot from a floppy it takes forever! I
syslinux has a slow/safe and a fast mode. The installer uses the
slow/save mode. Just run syslinux once more on the floppy, then it
should be way faster.
Another option would be:
dd if=kernel-image of=/dev/fd0
know it's actually got the kernel (of sorts) on the floppy. What can
I do to change this? Can I have it on hda9? So, if I use the rescue
disk or whatever, I can simply do something like "kernel
root=/dev/ha9" at the "boot:" prompt? Or am I kind of stuck with the
slow/unreliable boot from a floppy?
Thanks in advance, gang!
You might want to use lilo on the floppy instead of syslinux, since
lilo can boot the kernel from the harddrive. Should be the fastest way.
As to how, rtfm. :)
May the Source be with you.
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installing with 2.4.0-test8 and devfs, problem with floppy
Glenn McGrath [EMAIL PROTECTED] writes: Hi, i checked out your diff, i havent gotten very far into it yet, but see youve done some customisations to get init working with devfs. There is a simpler solution, change the following lines from ./busybox/scripts/inittab The problem is that most people have old kernels and news kernels and might or might not use devfs. So changing the inittab will break kernels without devfs. I want to be able to put a 2.2.x kernel onto the rescue disk and have it work, or a 2.4.0 without devfs or one with. So instead of having 2 different inittabs to choose from I changed init.c to cope with it. I also changed getty to cope with it (diff is send to maintainer and upstream) for after installation. May the Source be with you. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alternative root filesystem support
Hartmut Koptein [EMAIL PROTECTED] writes: Let's add one more bullet point for the new installer--namely, alternative root filesystem support. I and my colleagues would just love to see ReiserFS support in woody's installer. Why reiserfs? reiserfs is the bad guy, it doesen't support other architectures then intel and only the 32 bit part. Doesn't reiser also have problems with raid and lvm? I prefer jfs, it supports more then only intel and it is 64b clean. An alternative is xfs. Then reiserfs and then ext3fs. Will jfs be in 2.4.0 or where can I get some docs for it? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
some problems solved [Was: Re: Installing with 2.4.0-test8 and devfs, problem with floppy]
I overlooked a check for /dev/fd that now also checks for /dev/floppy/. The install didn't recognise /dev/floppy/0 as floppy and then tried to handle the floppy as mounted filesystem, which didn't quite work. So now I am able to install drivers and base, which are unpacking at the moment. Only problem left is a "ioctl fdflush failed (non fatal)". Kernel 2.4.0-test8 doesn't seem to like the fdflush. Does anyone know why that might be? May the Source be with you. Goswin PS: Make a bootfloppy remains to be adapted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installing with 2.4.0-test8 and devfs, problem with floppy
Erik Andersen [EMAIL PROTECTED] writes: On Fri Sep 22, 2000 at 02:45:52PM +0200, Petr Cech wrote: On Fri, Sep 22, 2000 at 01:32:13PM +0200 , Goswin Brederlow wrote: So instead of having 2 different inittabs to choose from I changed init.c to cope with it. I also changed getty to cope with it (diff is send to maintainer and upstream) for after installation. couldn't the rescue floppy have devfs packagem that installs the "compatibility links" in /dev, so if init discovers it's running 2.4 kernel with devfs it executes it and we have /dev/hda again. And the documentation stays the same. You'll still have /dev/hda1 and not /dev/ide/0/1 (or whatever). I like this approach much better. Or (depending on its size) we could install devfsd... Many people don't like to have jet another demon running and devfsd is only ment as a temporary fix for old software. I don't intend to use it. Using a linkfarm would of cause be possible, but then one would giveup all the advantages of devfs. Forcing devfs for the installation would probably save 1 to 2 MB of the root disk and autodetection of the cdrom drive or partitions could be greatly simplified. No more option to use the second floppy drive one doesn't have or problems that /dev/hda9 does not exist or /dev/sde-g. I also tend to disk names, partition names and ext2lables instead of device names like /dev/hda5, so root will be on /dev/drives/system/root and home on /dev/drives/raid/home and swap on /dev/drives/swap (for example). May the Source be with you. Goswin PS: lvm support will also alter the name of partitions, so hdaX will be gone soone I hope. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: installing off of serial console.
Matt Rose [EMAIL PROTECTED] writes: Is it possible to install debian through a sparc serial console? I have a sparc with no monitor or keyboard (fine, I'm just gonna use it as a server anyways) I don't have access to these things. When I boot up using the supplied tftpboot.img, it drops me into dbootstrap, and dbootstrap gives me all kinds of garbage. I was wondering if I could set the comm parameters on the serial port so that dbootstrap works, or failing that, is there a debian install system that doesn't use curses? Yes it is. But you need a vt100 capable terminal or maybe even a linux terminal. You might also have to set another boot paramter: "console=ttya" May the Source be with you. Goswin PS: Isn't there a debian-sparc mailinglist, maybe there they have more experience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Installing with 2.4.0-test8 and devfs, problem with floppy
Over the last two weeks I made extensive changes to the boot-floppies to get it to work with a 2.4.0-test kernel and devfs mounted at boot time. I now have a 37K diff with a lot of changes and can install from a mounted medium but not from floppy. When I want to install from floppy and select /dev/fd0 as medium I get two "Bad file descriptor" errors displayed and then a dialogbox telling me that the extraction failed. I did add code to test for /dev/fd0 and /dev/floppy/0 and use the right one, so the device and mounting should be fine. Also I can mount the disk by hand, so floppy works and the filesystem is right. Can anyone give me a clue as to what causes the two "Bad file descriptor" errors and whats likely to fail? Anyone willing to test can get my diff from: ftp://rut.informatik.uni-tuebingen.de/boot-floppies-mrvn.diff.bz2 But beware, its work in progress. May the Source be with you. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#70387: automatic build fails for potato
Package: boot-floppies Version: N/A; Severity: normal *** explain.txt I compiled all packages that have no "Build-Depends" in potato/main/Sources.gz. Your package failed to build together with about 1700 other packages. Since you have no "Build-Depends" you eigther forgot that your package build-depends on something (like debhelper?) or you don't know about build dependencies. The releavnt fields are descibed in: http://www.at.debian.org/doc/packaging-manuals/packaging.html/ch-relationships.html#s8.7 Please add build dependencies to your package or correct what ever else caused the package not to build. If you already did so for woody, please just close this bug report. If your Package is one of the rare cases with a Build-Depends-Indep and I overlooked it, also please just close. May the Source be with you. Goswin The compilation logfiles follows: *** boot-floppies/boot-floppies.log Reading Package Lists... Building Dependency Tree... Need to get 2666kB of source archives. Get:1 ftp://alpha potato/main boot-floppies 2.2.16 (dsc) [605B] Get:2 ftp://alpha potato/main boot-floppies 2.2.16 (tar) [2665kB] Fetched 2666kB in 2s (897kB/s) dpkg-source: extracting boot-floppies in boot-floppies-2.2.16 dpkg-source: extracting boot-floppies in boot-floppies-2.2.16 dpkg-buildpackage: source package is boot-floppies dpkg-buildpackage: source version is 2.2.16 dpkg-buildpackage: source maintainer is Adam Di Carlo [EMAIL PROTECTED] debian/rules clean DEB_BUILD_ARCH=i386 DEB_BUILD_GNU_CPU=i386 DEB_BUILD_GNU_SYSTEM=linux DEB_BUILD_GNU_TYPE=i386-linux DEB_HOST_ARCH=i386 DEB_HOST_GNU_CPU=i386 DEB_HOST_GNU_SYSTEM=linux DEB_HOST_GNU_TYPE=i386-linux test -f rootdisk.sh -a -f debian/rules make -i distclean find: /archive/debian/Incoming/: No such file or directory find: /archive/debian/local/: No such file or directory find: /archive/debian/dists/potato/main/binary-i386: No such file or directory make[1]: Entering directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16' make -C utilities distclean make[2]: Entering directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16/utilities' rm -f *.o *.bak set -e; for i in libfdisk dbootstrap busybox writemaps lowmemrd; do make -C $i clean; done make[3]: Entering directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16/utilities/libfdisk' rm -f fdisk.o partbl_msdos.o partbl_osf.o partbl_sun.o partbl_amiga.o partbl_atari.o partbl_mac.o libfdisk.a testing.o make[3]: Leaving directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16/utilities/libfdisk' make[3]: Entering directory `/mnt/raid0/builder/tmp/boot-floppies-2.2.16/utilities/dbootstrap' set -e; \ touch -a lang.h; \ echo ".depend/util : util.c" .depend/util; \ echo .depend/util; \ gcc -MM -D_GNU_SOURCE -DBUILDTIME='"2000.08.28-05:17+"' -DARCH='"i386"' -DARCHNAME='"i386"' -DKERNEL_VERSION_CODE=131584 -DKVER='""' util.c | \ sed -e 's,\(util\)\.o[ :]*,\1.o \1.test.o : ,g' | \ sed -e 's,\(util\.c\),.translated/\1,' .depend/util; \ touch -m .depend/util; set -e; \ touch -a lang.h; \ echo ".depend/tzconfig : tzconfig.c" .depend/tzconfig; \ echo .depend/tzconfig; \ gcc -MM -D_GNU_SOURCE -DBUILDTIME='"2000.08.28-05:17+"' -DARCH='"i386"' -DARCHNAME='"i386"' -DKERNEL_VERSION_CODE=131584 -DKVER='""' tzconfig.c | \ sed -e 's,\(tzconfig\)\.o[ :]*,\1.o \1.test.o : ,g' | \ sed -e 's,\(tzconfig\.c\),.translated/\1,' .depend/tzconfig; \ touch -m .depend/tzconfig; set -e; \ touch -a lang.h; \ echo ".depend/select_not_mounted : select_not_mounted.c" .depend/select_not_mounted; \ echo .depend/select_not_mounted; \ gcc -MM -D_GNU_SOURCE -DBUILDTIME='"2000.08.28-05:17+"' -DARCH='"i386"' -DARCHNAME='"i386"' -DKERNEL_VERSION_CODE=131584 -DKVER='""' select_not_mounted.c | \ sed -e 's,\(select_not_mounted\)\.o[ :]*,\1.o \1.test.o : ,g' | \ sed -e 's,\(select_not_mounted\.c\),.translated/\1,' .depend/select_not_mounted; \ touch -m .depend/select_not_mounted; set -e; \ touch -a lang.h; \ echo ".depend/release_notes : release_notes.c" .depend/release_notes; \ echo .depend/release_notes;\ gcc -MM -D_GNU_SOURCE -DBUILDTIME='"2000.08.28-05:17+"' -DARCH='"i386"' -DARCHNAME='"i386"' -DKERNEL_VERSION_CODE=131584 -DKVER='""' release_notes.c | \ sed -e 's,\(release_notes\)\.o[ :]*,\1.o \1.test.o : ,g' | \ sed -e 's,\(release_notes\.c\),.translated/\1,' .depend/release_notes; \ touch -m .depend/release_notes; set -e; \ touch -a lang.h; \ echo ".depend/reboot_system : reboot_system.c" .depend/reboot_system; \ echo
Bug#66009: 32 Mb, but Sorry, not enough memory (caused by new kernels sysinfo syscall)
" " == Erik Andersen [EMAIL PROTECTED] writes: I can implement a correct solution for the way the kernel currently changed right now (not requiring such a hack). I asked on the boot-floppies mailing list and it was agreed to _not_ do anything about this, and that 2.4.x kernels were not a potato boot-floppy target. The "correct" way to work around the change is the copy the 2.2.x and the 2.4.x sysinfo structs into the busybox source tree, giving them unique names. Then on boot, call uname to decide which struct to use, and then, if the kernel is 2.4.x also take ito account sysinfo.mem_unit. This is ugly, but workable. I thing you could initialise sysinfo.mem_unit with 1, then call sysinfo(). Since 2.2 has just padding there, sysinfo.mem_unit should remain 1 and on 2.4 it would be set to reflect the page size. That way sysinfo.mem_unit could be used in both cases. For the moment, it was agreed to _not_ fix this in the boot floppies for potato, so I am not touching it unless asked to by Adam Di Carlo (potato boot floppies team lead). May the Source be with you. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#66030: tries to read past end of driver-3.bin
Package: boot-floppies Version: N/A; Severity: normal When installing Debian, the installation of the Driver disks reads past the end of drivers-3.bin (that probably what tar/gzip allways try) Normaly that wont be a problem, since a real floppy will have some spam after the driver-3.bin, but when using the files via loopback or in an emulator that results in an IO error and you are questioned to try the disk again. An aditional few blocks should be added to the drivers-3.bin, for example by: dd if=/dev/zero bs=1k count=100 | cat driver-3.bin That resolves the problem and makes Debian installable under VMware. May the Source be with you. Goswin -- System Information Debian Release: 2.2 Architecture: i386 Kernel: Linux mose 2.4.0-test1-ac7 #20 Wed Jun 7 14:53:53 CEST 2000 i686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
