debian-installer status, thoughts
Good news! I just used netcfg-static to bring up the network on my machine after booting off the floppy. fun. Problems: 1. 3c509 modules depends on isa-pnp module. It looks like if you configure the kernel to have modular isapnp, then some of the ISA modules are configured to use that. Does that mean we need isapnp-modules*.udeb? 2. ethdetect is too big :-(, I couldn't fit it. I'll look to see if it is pulling in extra stuff. I expect it is, it shouldn't be that large. Anyway, that forced me to insmod manually. 3. modprobe isn't happy with the modules.dep that I created. depmod -n -F ksyms -a -b $(DEST)/ $(KVER) $(DEST)/lib/modules/$(KVER)/modules.dep where ksyms was created by the 'depmod/create_syms' script in modutils. 4. . . . But we're getting close, -David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Notes on dbootstrap makefile and plans [Re: Debian Boot CVS: tausq]
On Mon, Jan 29, 2001 at 03:03:51AM -0500, Adam Di Carlo wrote: What I do have a problem with right now is LANG_CHOOSER and how it was never really completed. Very frustrating. I feel like the i18n folks got us 95% there, but neglected to finish off the critical last 5%. Yes, i can feel that too :-( Unfortunately I really don't have enough time to work on it now. Maybe in the second half of February, but probably no sooner :-\ I'm sure to build multiple variants, you'd need to build the one, move the exec outta the way, make clean, build the other, etc. It's doable. but ugly :-) regards Marcin -- Marcin Owsiany [EMAIL PROTECTED] http://student.uci.agh.edu.pl/~porridge/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
No Keyboard when booting the powerPC bootdisk
Hi! Im having a "little" problem, when booting from the dick, found in /install/powermac/boot-floppy-hfs.img on the official Debian-CD. I dont have any access to my keyboards (one is connected to the ADB, the other to the USB port of my PowerMacintosh 4400). Some time ago, I downloaded an earlier version of the bootdisk, based on kernel 2.2.17 which workes fine with both ADB and USB keyboard, but I cant use this disk for setting up the modules of Debian 2.2r2. Thanks in advance for your kind help John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian-installer status report
* Joey Hess | - http retriever [Joey Hess] | Works, needs testing and proxy support. Has proxy support. Needs proxy and general testing. Will soon have ftp support. -- Tollef Fog Heen Unix _IS_ user friendly... It's just selective about who its friends are. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian installation screens (cont)
Hi all, last week I sent the following e-mail and someone replied me. I forgot the mail. It is something like get boot-floppies package and use dbootstrap. I tried to do a "make release" and the following error occurs: find . -name \*~ | xargs rm -f make resc1440.bin resc1440-s.bin 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 `/usr/src/boot-floppies' make[1]: *** No rule to make target `kernel-image-2.2.17_2.2.17-1.deb', needed by `linux'. Stop. make[1]: Leaving directory `/usr/src/boot-floppies' make: *** [build] Error 2 -- Hi all, I'm writing a Debian GNU/Linux manual and want to include some screenshots of Debian's 2.2 install. Anyone, already made them? If not, where I can find some or made some? Thanks, Paulo Henrique -- Anyone can help,Paulo Henrique TIA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian installation screens (cont)
On Mon, Jan 29, 2001 at 01:44:42PM -0200, Paulo Henrique Baptista de Oliveira wrote: I forgot the mail. It is something like get boot-floppies package and use dbootstrap. I tried to do a "make release" and the following error occurs: find . -name \*~ | xargs rm -f make resc1440.bin resc1440-s.bin find: /archive/debian/Incoming/: No such file or directory [...] Read the documentation in the root directory of boot-floppies tree - you need to edit the config file to contain a pointer to your local archive mirror. (Yeah, this is a PITA :-( ) regards Marcin -- Marcin Owsiany [EMAIL PROTECTED] http://student.uci.agh.edu.pl/~porridge/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian Boot CVS: ericvb
CVSROOT:/cvs/debian-boot Module name:boot-floppies Changes by: ericvb 01/01/29 09:52:29 Modified files: documentation : release-notes.fr.sgml Log message: Christophe Martin finished the French translation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#83608: [PATCH]: modutils-udeb for debian-installer
Previously David Whedon wrote: We're really strapped for space trying to fit all on a single floppy. We have to carefully consider the 10k that using modprobe will cost us. Is it possible for you to elaborate on why you don't want us to use insmod. We really only need it to insmod a nic module, and after that we can grab anything else that we want off the net (modprobei. for example). modprobe resolves dependencies, insmod does not. For some network modules that is really need: you can't load the wd driver for example before you load the 8130 module. modprobe will do that for, insmod does not. Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#83608: [PATCH]: modutils-udeb for debian-installer
Okay, using modprobe is a good idea. I have a new patch to modutils; it
includes modprobe and is attached.
Thanks,
-David
Mon, Jan 29, 2001 at 07:47:38PM +0100 wrote:
Previously David Whedon wrote:
We're really strapped for space trying to fit all on a single floppy. We
have to carefully consider the 10k that using modprobe will cost us. Is it
possible for you to elaborate on why you don't want us to use insmod. We
really only need it to insmod a nic module, and after that we can grab
anything else that we want off the net (modprobei. for example).
modprobe resolves dependencies, insmod does not. For some network
modules that is really need: you can't load the wd driver for example
before you load the 8130 module. modprobe will do that for, insmod does not.
Wichert.
--
/ Generally uninteresting signature - ignore at your convenience \
| [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
diff -ur orig/modutils-2.4.1/Makefile.common.in modutils-2.4.1/Makefile.common.in
--- orig/modutils-2.4.1/Makefile.common.in Thu Jan 4 17:45:19 2001
+++ modutils-2.4.1/Makefile.common.in Thu Jan 25 21:10:49 2001
@@ -9,7 +9,7 @@
AR = @AR@
ARCH = @ARCH@
CC = @CC@
-CFLAGS = @CFLAGS@
+CFLAGS = @CFLAGS@ $(UDEB_CFLAGS)
BUILDCC= @BUILDCC@
BUILDCFLAGS= @BUILDCFLAGS@
INSTALL= @INSTALL_LOCAL@
diff -ur orig/modutils-2.4.1/debian/control modutils-2.4.1/debian/control
--- orig/modutils-2.4.1/debian/control Mon Jan 29 11:30:16 2001
+++ modutils-2.4.1/debian/control Thu Jan 25 23:02:28 2001
@@ -2,6 +2,7 @@
Section: base
Priority: required
Maintainer: Wichert Akkerman [EMAIL PROTECTED]
+Build-Depends: dpkg-dev (= 1.7.0)
Standards-Version: 3.2.0
Bugs: debbugs://bugs.debian.org/
Origin: debian
@@ -15,3 +16,11 @@
These utilities are intended to make a Linux modular kernel
manageable for all users, administrators and distribution
maintainers.
+
+Package: modutils-udeb
+Section: debian-installer
+Architecture: any
+Depends: ${shlibs:Depends}
+Description: Linux module utilities for debian-installer.
+ modutils-udeb is a minimal package used by debian-installer.
+ This package contains only the binary 'insmod'.
diff -ur orig/modutils-2.4.1/debian/rules modutils-2.4.1/debian/rules
--- orig/modutils-2.4.1/debian/rulesMon Jan 29 11:30:16 2001
+++ modutils-2.4.1/debian/rules Sat Jan 27 20:44:09 2001
@@ -4,6 +4,11 @@
package:= modutils
docdir := /usr/share/doc/$(package)
tmpdir := $(shell pwd)/debian/tmp/
+udebtmpdir := $(shell pwd)/debian/modutils-udeb/
+version:=$(shell dpkg-parsechangelog | grep ^Version: | cut -d ' ' -f
+2)
+arch :=$(shell dpkg --print-architecture)
+priority :=$(shell grep ^Priority: debian/control | cut -d ' ' -f 2)
+udebfilename :=$(package)-udeb_$(version)_$(arch).udeb
stamp-config:
mkdir -p debian/build
@@ -12,20 +17,31 @@
--mandir='$${prefix}'/share/man
touch stamp-config
+stamp-config-udeb:
+ mkdir -p debian/build-udeb
+ cd debian/build-udeb ; ../../configure --disable-root-check \
+ --disable-combined --enable-combined-modprobe
+ touch stamp-config-udeb
+
stamp-build build: stamp-config
cd debian/build ; $(MAKE)
touch stamp-build
+stamp-build-udeb build-udeb: stamp-config-udeb
+ cd debian/build-udeb ; $(MAKE) UDEB_CFLAGS="-Os -fomit-frame-pointer"
+ touch stamp-build
+
clean:
test -d debian
- rm -rf debian/build debian/tmp
+ rm -rf debian/build debian/tmp debian/build-udeb debian/modutils-udeb
-rm -rf debian/files* debian/substvars
- -rm -f stamp-config stamp-build
+ -rm -f stamp-config stamp-build stamp-config-udeb \
+ stamp-build-udeb debian/files~
binary-indep:
@echo Nothing to do
-binary-arch: checkroot stamp-build
+binary-arch: checkroot stamp-build stamp-build-udeb
test -d debian
-rm -rf debian/tmp
install -d -m 755 -o root -g root debian/tmp
@@ -44,6 +60,21 @@
rm -f $(tmpdir)/usr/share/man/man8/kdstat.8
+# Install udeb binary
+ cd debian/build-udeb ; $(MAKE) exec_prefix=$(udebtmpdir) install
+
+# Remove all the udeb doesn't need
+ rm -rf $(udebtmpdir)/usr/
+ rm -f $(udebtmpdir)/sbin/depmod \
+ $(udebtmpdir)/sbin/genksyms \
+ $(udebtmpdir)/sbin/insmod_ksymoops_clean \
+ $(udebtmpdir)/sbin/kallsyms \
+ $(udebtmpdir)/sbin/kernelversion \
+ $(udebtmpdir)/sbin/ksyms \
+ $(udebtmpdir)/sbin/lsmod \
+
Re: Debian Boot CVS: aph
the apt-get way of downloading is *not* going to work for us. It refuses to download Required packages that are already installed. Feh!!! Have you tried setting Dir::State::status to point to an empty file or something? -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: busybox for b-f yet?
On Mon Jan 29, 2001 at 02:57:44AM -0500, Adam Di Carlo wrote: I note that in busybox_0.49pre-1 we still don't yet have a means of making the various symlinks to busybox stuff. Or am I just missing it? Is this forthcoming? It's starting to be a bother not to have it... Hmm. Did I forget to enable 'busybox --install'? That is what you are supposed to be using. -Erik -- Erik B. Andersen email: [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian Boot CVS: joeyh
CVSROOT:/cvs/debian-boot Module name:base-config Changes by: joeyh 01/01/29 13:48:08 Modified files: debian : changelog control rules Log message: * Built with fixed debhelper to get all the pt_BR template merged in. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[Fwd: Debian's new installer]
The following is a bit of a description about how Conectiva's installer works. You have probably picked up from the list that cdebconf and udeb packages are basically the heart of the new debian installer. cdebconf provides the user interface and installer modules are handled like regular packages that are fetchable on demand. The installer could be almost considered a mini-distribution. I didn't dive into details on how your installer works (or is going to), but I can have an idea based on s draft I read and what you told me now. Our installer works in a different way: modules are .so libraries. When it detects the presence of 2 or more modules of the same kind, it asks you which one you'd like to use (of course, you can force one in the mi.conf file or add a "detection" routine that chooses one for you according to the context). As I can see, your installer is highly based on separate tools, while ours are completely integrate, although it may not be (we don't use RPM, but librpm instead. And we're planning to write a pm_apt module, that will be a wrapper to apt-get, and this one will be able to handle both .rpm and .deb packages) hmm, that is an interesting design, is there more to one your installer modules, or is it completely contained in the .so library ? Sorry, I think I didn't understand you question, so I'll tell you something about its design: We currently have an engine, that handles the installation steps, flow control, etc, and a set of modules (one module from each set of modules): * imethod modules: knows how to retrieve a file from the distribution (these are your retriever modules), mounting the necessary support for that. Currently we only have imethod_local.so module, that knows how to access a file in a mounted directory (this is because we're still using a patched RedHat's loader, that already knows how to mount CD-ROMs, NFS, etc). This is one of the things we're going to change soon (get rid of RH crap). * target modules: knows everything about where you're going to install. Currently we only use target_hd.so (for hard disks installations), but I've implemented target_file.so, so we can be able to install inside a file, via loop devices. Also, it knows how to install a bootloader, do partitioning, auto-partitioning, etc (if appliable). There's a flaw in this design: our "package manager" (pm_* module) writes directly to disk (more on that) * pkglist modules: knows how to handle a specific package list. We use pkglist_hdlist.so, that reads the hdlist file from the distribution source (via imethod module) and understands it, creating a list with package information, so other modules can use it. Also, it selects/unselects packages. * pm modules: the package manager. We use pm_rpm.so, that knows how to install a set of RPM packages, calculate dependencies, verify disk space, and so on. Currently it ignores the target module, so it can only be used to install in a local harddisk (we need to patch librpm to use the target_* module or implement a separate installer). In a near future, we'll be able to drive the installation in one machine, but actually writing stuff to some other machine (or a lot of machines, simultaneously) via the network or some other media already supported by a target_* object. * distro modules: this module is a "writer" module. It knows how to configure your system (X, network, etc). * fe modules: the pluggable interface. An specific API used by the core and all other modules that supplies both generic methods (showMessage()) and specific methods (packagsSelection()) Im sure we could find at least some common ground. Yes! As I told you in the other email, we're redesigning MI core to be much more expandable than it is now, and we'd be very glad in sharing experience with you guys, so we can have the same installer working on RPM-based and DEB-based distros, and maybe FOO-based, BAR-based, BLAH-based, and so on... ;-) If it's Debian's interest adopting MI as it's official installer, rather than developing your own from scratch again, we can put a higher priority on this issue and develop MI's next version altogether. Although this joint development is not an official position from Conectiva, I can assure you from informal conversation that it will be gladly accepted by "my bosses". :-) I dont think the new debian-installer will be dumped, its had a lot of thought put into it, and things have been moving along fairly quickly in the last few weeks although there is still a long way to go. Yes... I feel sorry for not contacting you before... maybe if I had got known that you were working on it some time ago, we could have avoided a lot of work :-) As MI gets mature, maybe you can adopt it as a second-option installer. Btw, have you tried it already? Maybe you'd like to visit: http://www.thedukeofurl.org/reviews/misc/conectiva6/ or, more specifically:
Re: bogl forked (was Re: [patch] bogl memset_var for 32 bpp screen)
On Thu, Jan 25, 2001 at 08:54:38PM -0500, Adam Di Carlo wrote: Daniel Jacobowitz [EMAIL PROTECTED] writes: On Tue, Jan 23, 2001 at 08:27:51PM -0500, Adam Di Carlo wrote: Daniel Jacobowitz [EMAIL PROTECTED] writes: Sorry for not being clear - yes, I know that bterm has the same bug. I'd appreciate it if someone on this list would look into using the bogl and bterm in that package, so that we can scrap the one in debian-boot CVS; having both makes me nervous about lost work. I guess we'll plan on using straight bogl from woody for the woody boot floppies. I hate forking. I'm not sure why we forked it... Maybe Marcin (or was it Marcel?) can explain it? We didn't fork it for boot floppies; it was originally there. I added new bogl packages to woody for debian-installer, though, a month ago. At that point it was effectively forked - mostly my fault. Oh. Ok. So -- am I correct in concluding that boot-floppies for woody should rely on using bogl from woody (the .deb, b-f can't use udebs) and not the internal stuff? If at all possible, yes! It will take a little doing, because I removed the boxes code; that just needs to link to the provided libbogl. Then I can go through and sweep up any pending patches in the b-f bogl repository, and delete the whole directory. I don't have time to do this right now, alas :( Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
