Bug#156882: boot-floppies: debootstrap; partition list; presentation order is inaccurate
Package: boot-floppies Version: N/A; reported 2002-08-16 Severity: minor I reinstalled my laptop, in order to set up a hibernation partition this time. I lied to the BIOS and told it that the drive geometry for my new 12 GB hard disk is the same as that of the original drive. I then used cfdisk via debootstrap to create four partitions... The BIOS wants the hibernation partition in slot number four, so I put partition three at the end of disk space, then filled in a gap I'd left with partition four and made that type A0, to run lphdisk on it. That all works great, and the laptop can suspend to disk now. The problem is that debootstrap, when asked to print out the partition table, will reorder the output in geometry or on disk order, rather than in partition table offset order. That is, it's sorting by where the partitions begin on disk, rather than by index into the partition table vector. You should mark this won't fix, close it, and make a note in the debian-installer someplace so that the implementors are aware of this subtlety. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux bittersweet 2.4.18.5-smp #1 SMP Wed Aug 7 12:55:10 PDT 2002 i686 Locale: LANG=C, LC_CTYPE=C -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#156882: boot-floppies: debootstrap; partition list; presentation order is inaccurate
Philip Blundell [EMAIL PROTECTED] writes: On Fri, 2002-08-16 at 08:36, Karl M. Hegbloom wrote: The problem is that debootstrap, when asked to print out the partition table, will reorder the output in geometry or on disk order, rather than in partition table offset order. That is, it's sorting by where the partitions begin on disk, rather than by index into the partition table vector. You mention debootstrap several times, but I suspect you actually mean dbootstrap. jawohl -- As any limb well and duly exercised, grows stronger, the nerves of the body are corroborated thereby. --I. Watts. .''`. Debian -- The blue collar Linux distribution. : :' : URL:http://www.debian.org/social_contract `. `' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Partition tools (Re: debian-installer status -- 2002-07-29)
[Ob-CC: Cc'd just FYI. d-i refers to the next generation Debian Installer, which you may view at http://cvs.debian.org/ and discuss in [EMAIL PROTECTED]; also archived there - http.] Matt Zimmerman [EMAIL PROTECTED] writes: I am in complete agreement that we would not want to include EVMS, XFS or similar in our default kernel unless (or until) they are part of the official kernel. However, I am willing to do some work to support EVMS in d-i, and to provide EVMS-enabled installation media for those who are interested in trying it. If I can use this experience to improve volume management support in d-i, then I would hope that my contributions would be welcome. I am also interested in an EVMS + XFS (and SMP enabled; give them a choice of kernel images!) enabled install, as well as a totally automatic (perhaps scripted) one. The automatic install should support EVMS too, ideally. Someday it WILL undoubtedly be production quality, and WE'll be the first to have a turnkey installer for a system that utilizes it, if we do this. As I recall, d-i sports a very modular design that should make it possible to give the user a choice of which partitioning tool to pull in off the CD media. They can then choose standard or EVMS, cfdisk, disk druid, or depart (good a name as any?). Yes, at this point in time, EVMS + XFS should certainly be considered experimental. (My present system deadlocks when I compile software; bugs reported to XFS and EVMS lists; I hope they can fix it soon.) It might improve the bugfix and development rate some if more people got exposed to these new features, which may certainly occur if there's an easy way for them to install it and try it on a test box. (You must admit that installing by hand is for experts only.) I wonder if there's any kind of consolidation and reconciliation possible between the EVMS C API and libparted? Both are capable of creating disk partitions... (Sight unseen I cannot say myself; it just occured to me and thus I wonder.) -- As any limb well and duly exercised, grows stronger, the nerves of the body are corroborated thereby. --I. Watts. .''`. We are deB.ORG; You will be freed. : :' : URL:http://www.debian.org/social_contract `. `' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
FYI: Installing EVMS and RAID1, URL to list archive
http://www.geocrawler.com/lists/3/SourceForge/11629/0/9171087/ -- As any limb well and duly exercised, grows stronger, the nerves of the body are corroborated thereby. --I. Watts. .''`. We are deB.ORG; You will be freed. : :' : URL:http://www.debian.org/social_contract `. `' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Partition tools (Re: debian-installer status -- 2002-07-29)
Tollef Fog Heen [EMAIL PROTECTED] writes: [...], we need some more partition tools; there has been some discussion on debian-boot regarding it but no final decision has been reached, though several solutions have been presented. I wonder if the partition tools can do EVMS, or if a plugin should be made for that? Anyone else want to use EVMS at some point? -- As any limb well and duly exercised, grows stronger, the nerves of the body are corroborated thereby. --I. Watts. .''`. We are deB.ORG; You will be freed. : :' : URL:http://www.debian.org/social_contract `. `' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hardware detection w/example code.
Any reason not to put hardware detection into the boot-floppies?
libdetect works fairly well on each of the three machines I've
tried it on.
Note that in the case of a USB keyboard and mouse, you'll want to
load the HID stuff right away, even before they try to type
anything... Right? (I've no system with USB keyboard only to try
this with.) There's a kbd-reset kernel command line option that
causes the kernel to attempt to reset a PS/2 or old style keyboard.
When the keyboard is thus found to be non-present, a message is
printed via printk. It can be gotten from dmesg or whatever...
This script segment should bring in IDE, SCSI, USB, and NIC
drivers. (WFM, YMMV)... Requires Linux 2.4 with devfs, tested with
busybox ash (this is from a /linuxrc I wrote)
8-8
disc_list()
{
if [ -d $DEV/discs ]
then
# deterministic order is important - ls will sort.
for disc in $(ls $DEV/discs)
do
echo discs/$disc
done
fi
}
cd_candidates ()
{
if [ -d $DEV/cdroms ]
then
# deterministic order is important - ls will sort.
for cd in $(ls $DEV/cdroms)
do
echo cdroms/$cd
done
fi
}
mount -n -t proc proc /proc
mount -t tmpfs tmpfs /tmp
# Since devfs might already be mounted by a kernel command line
# option or by default, send errors and output to /dev/null.
#
mount -t devfs devfs /dev /dev/null 21 || true
# Load drivers:
#
DRIVERS=$(discover --disable-all --enable=pci,pcmcia,usb,ide,scsi --module bridge ide
scsi cdrom ethernet)
for i in $DRIVERS; do
modprobe $i
done
unset DRIVERS
modprobe ide-probe-mod
IDE_MEDIA=$(
for m in $(find /proc/ide -name media -print)
do
cat $m
done
)
if echo $IDE_MEDIA | grep -q cdrom
then
modprobe ide-cd
fi
if echo $IDE_MEDIA | grep -q disk
then
modprobe ide-disk
fi
rmmodide-probe-mod
if [ -d $DEV/scsi ]
then
cdroms=$(cd_candidates)
modprobe sr_mod
# cd_candidates() MUST return them in deterministic order for this
# to work right. Otherwise, the same logical set returned in a
# different order would appear to this test as there being a new
# cdrom.
#
if [ $(cd_candidates) = $cdroms ]
then
# No new CDROM(s), so unload it.
rmmod --stacks sr_mod # XXX ? Is --stacks correct here?
fi
unset cdroms
discs=$(disc_list)
modprobe sd_mod
if [ $(disc_list) = $discs ] # ditto for disc_list() re sorting.
then
# No new disc(s), so unload it.
rmmod --stacks sd_mod # XXX ? Is --stacks correct here?
fi
unset discs
fi
8-8
--
mailto: (Karl M. Hegbloom) [EMAIL PROTECTED]
Free the Software http://www.debian.org/social_contract
http://www.microsharp.com
phone://USA/WA/360-260-2066
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: Bug #120407 : nparted: note for debian-installer
Glenn == Glenn McGrath [EMAIL PROTECTED] writes: Glenn http://www.speedblue.org/debian/nparted/ Glenn I gave it a quick try and got the error invalidate: busy buffer Glenn scrolling of the screeen, it makes it unusable for me. If you grep the kernel source for that message, you'll find it... I've seen the same message while using LVM/XFS. I don't think it's a fatal error, just a warning. We'd have to ask the kernel experts just exactly what it means. Glenn I assume its a problem upstream, im using devfs which may Glenn be the problem. I don't think it's devfs or your frame buffer. The reason it works in your xterm is that the printk messages from the kernel are not shown in the xterm, but are on the foreground vt when you are at the console, unless you suppress them. (setterm -msglevel 1 might do it.) -- mailto: (Karl M. Hegbloom) [EMAIL PROTECTED] http://www.microsharp.com phone://USA/WA/360-260-2066 jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
/dev/console, /dev/tty (Re: Bug#126370: installer issues on real terminals)
Can someone please clear up what /dev/console and /dev/tty are? I think that /dev/console is always the foreground virtual console, and that /dev/tty is always the process's controlling terminal. Is that correct? If that's the case, or if it's something like that, then these are the device names that need to be used for the base-config, right? Then the problem may arise where the user will switch virtual consoles and log in, and the program running on the first VT will refresh or redraw it's screen, and that output will appear on top of the user's current VT rather than on the first one. -- mailto: (Karl M. Hegbloom) [EMAIL PROTECTED] http://www.microsharp.com phone://USA/WA/360-260-2066 jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Documentation: from fdisk man page; Is this in the install manual?
This is important information and I wonder if it is mentioned in the installation manual (for Intel arch)? If not, it should be, IMO. quote If possible, fdisk will obtain the disk geometry automati- cally. This is not necessarily the physical disk geometry (indeed, modern disks do not really have anything like a physical geometry, certainly not something that can be described in simplistic Cylinders/Heads/Sectors form), but is the disk geometry that MS-DOS uses for the partition table. Usually all goes well by default, and there are no prob- lems if Linux is the only system on the disk. However, if the disk has to be shared with other operating systems, it is often a good idea to let an fdisk from another operat- ing system make at least one partition. When Linux boots it looks at the partition table, and tries to deduce what (fake) geometry is required for good cooperation with other systems. /quote -- fdisk man page. -- mailto: (Karl M. Hegbloom) [EMAIL PROTECTED] http://www.microsharp.com phone://USA/WA/360-260-2066 jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bug: cdimage.debian.org should warn against downloading with an ISDN connection
Richard == Richard Atterer [EMAIL PROTECTED] writes: Richard Do the woody bootfloppies support installing via ISDN? Perhaps if they do not, they should. Someone should perform that labor and make it possible. I wonder if it would require an entire new flavor of images, or if it's only a matter of inserting the correct modules? I know zilch about ISDN. -- We are deB.ORG; you will be freed. Deliverance is inevitable. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [PATCH;debian-installer/doc/README] Correct URL to upx
Eduard == Eduard Bloch [EMAIL PROTECTED] writes: Eduard Remember, the precompiled UPX stuff is non-free, since the Eduard closed source NRV lib is used for compression, and the Eduard free version 1.2 cannot be compiled. Currently, I am Eduard trying to make the CVS version compile, but there are Eduard problems. Apparently, you have succeeded? % apt-cache search upx upx-ucl - an efficient live-compressor for executables upx-nrv - an efficient live-compressor for executables % apt-cache show upx-ucl Package: upx-ucl Priority: optional Section: utils Installed-Size: 320 Maintainer: Eduard Bloch [EMAIL PROTECTED] Architecture: i386 Version: 1.07-9 Provides: upx, dh-upx Depends: libc6 (= 2.2.4-2) Filename: pool/main/u/upx-ucl/upx-ucl_1.07-9_i386.deb Size: 137170 MD5sum: e0c9dbcc55de1623aef9f0c2276f3273 Description: an efficient live-compressor for executables . UPX is an advanced executable file compressor. UPX will typically reduce the file size of programs and DLLs by around 50%-70%, thus reducing disk space, network load times, download times etc. The current version can compress executables for DOS, Linux/ELF (i386 only!) and some other files for different OS. . NOTE: This package is based on the UCL library, which is licensed under GPL. -- I was Linux when Linux wasn't cool. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PS (Re: [PATCH;debian-installer/doc/README] Correct URL to upx)
... yawn/ I should wake up before I write email. I see now. You are trying to build a newer version of it. Uhhmmm... let me guess. The kernel compression only works in the newer one? -- I was Linux when Linux wasn't cool. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[PATCH;debian-installer/doc/README] Correct URL to upx
Index: README === RCS file: /cvs/debian-boot/debian-installer/doc/README,v retrieving revision 1.7 diff -u -u -r1.7 README --- doc/README 2001/01/04 04:29:00 1.7 +++ doc/README 2001/11/23 06:43:33 @@ -12,4 +12,4 @@ Majong game at the end also. Upx can compress bzimages. They're still bootable, and up to 100k might - be saved this way. http://wildsau.idv.uni-linz.ac.at/mfx/upx.html + be saved this way. URL:http://upx.sourceforge.net/ -- I was Linux when Linux wasn't cool. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
patches - to bts from now on.
I'll send them to BTS from now on; sorry. I'm rusty. -- I was Linux when Linux wasn't cool. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Tip for install manual? (Re: [PLUG] Debian Linux on a SunBlade 100)
Adam == Adam Di Carlo [EMAIL PROTECTED] writes: Adam All this is already in the install manual, actually. Ah, ok. Good. But if it was not, you'd want to know about that. Hello, everyone. How are you all these days? I've got a job now. Working hard on getting things ready for a product release. Can't say more right now. The Woody installer works great! I've used it twice now. Great job. I'm very curious about the debian-installer and what it's status is... I'll grep the archives and look the sources over when I find some time for that. :-) -- mailto: (Karl M. Hegbloom) [EMAIL PROTECTED] http://www.microsharp.com phone://USA/WA/360-260-2066 jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Tip for install manual? (Re: [PLUG] Debian Linux on a SunBlade 100)
In [EMAIL PROTECTED]: Stafford == Stafford A Rau [EMAIL PROTECTED] writes: Paul == Paul Heinlein [EMAIL PROTECTED] had written: Paul [ re installing Debian sid on a SunBlade 100 ] Paul 3. Then there's some tricky renaming or symlinking that has to be Paul done. The Sun's PROM will request a file named after a hex version Paul of its IP address. If the SunBlade's IP address were 192.168.1.100, Paul then it would request a file named C0A80164. (Older PROM versions Paul supposedly added an architecture-specific suffix to that filename, Paul e.g., C0A80164.SUN4U, but that's not true for SunBlade.) Paul So I symlinked the tftpboot.img to a hex name: Paul # cd /tftpboot Paul # ln -s tftpboot.img C0A80164 Stafford Since I'm a lazy sort and don't often feel like doing Stafford the conversion, I've cheated by doing a tcpdump ether Stafford host [sparc ethernet addr] from the tftp server, then Stafford started a boot net on the sparc and watched to see for Stafford which file it was asking. -- mailto: (Karl M. Hegbloom) [EMAIL PROTECTED] http://www.microsharp.com phone://USA/WA/360-260-2066 jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Has the new installer been given a codename yet? (ala Woody)
If the Debian Installer has not yet been nicknamed, I would like to do so. Let's call it "Insinuating Terrapin". Think of the Tortoise and the Hare, and envision a hare wearing a very special hat we are so fond of. Now picture the hare hitching a ride on the terrapin, after seeing how well designed our installer is by comparison to their tangled skein. Sic transit. export DEBIAN_INSTALLER_CODENAME := Insinuating Terrapin export DEBIAN_INSTALLER_RELEASE_IDENTIFIER := 0.0.a1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: udeb's of dhcpcd, pump and ppp
I found that the DHCP v3 `dhclient' works much better than the `dhcpcd' does. There's a package in "project/experimental" that I've been using. I bet it will be ready for the main distro by release day anyway, so why not just use it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
udma100 asus a7v not found [lhomer lhomer@teleport.com] Re: Fw: [PLUG] hopeful new Linux recruit
My small problem has been solved. Thank you for all the help and support. I am now able to install and run off a hard drive although the installation named the drive "hdg", and I can't boot from that drive just yet..I also can no longer see it in a windows directory..small matters. Apparently my board is just strange enough so that even Suse 7.0 can't recognize the drives on my board. I found a recent fix on the Suse site that worked. I would like to get back to using Debian. Do these fixes usually propagate to other installations very rapidly? Details at: http://sdb.suse.de/en/sdb/html/a7vpromise.html - Original Message - From: lhomer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 29, 2000 6:54 PM Subject: Re: Fw: [PLUG] hopeful new Linux recruit I tried the debian udma installation from rescue and root floppies with a single windows bootable hard drive (WDC AC34 300L) and it couldn't find the hard drive. I see my zip drive (hdb), my two cdroms (hdc,hdd), hda is identified with ide0 and ide0 with irq 14, but no named drives or ide controllers associated with ide0. In Windows the "Win95-98 Promise Ultra100 IDE controller (PDC20265)" is assigned irq 10. My suse installation identifies irq 10 with an unknown mass storage device, but also claims I have no hard drive. Thanks for the advice and interest. - Original Message - From: David Bridges [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, November 29, 2000 10:23 AM Subject: Re: Fw: [PLUG] hopeful new Linux recruit Don Buchholz wrote: Do you see all devices listed in the POST messages when the system boots? The ASUS CUBX motherboard has 2 IDE controllers, and 4 IDE connectors. To enable the 3rd, 4th connectors you must enable the on-board 'SCSI' controller. (Yes, it says SCSI in the BIOS setup, but it's really IDE. Thank you to the ENU tech. who told me that "SCSI" means "2nd IDE controller" in ASUS/CUBX lingo. :-) Actually my cdrom drive and my cdrw show up during the initial post and the hard disk shows up whenever the Promise controller scans for devices. When the hard disk is hooked up to the ATA100 controller the disk does not show up in the BIOS. Here is the links to boot and root floppies that you can download and see if the disk is recognized. They are for Debian and you would need other disks or cdroms to actually install. Booting with them would let you see if it an UDMA issue. ftp://ftp.debian.org/debian/dists/potato/main/disks-i386/current/images-1.44 /udma66/rescue.bin (boot) ftp://ftp.debian.org/debian/dists/potato/main/disks-i386/current/images-1.44 /udma66/root.bin (root) Hope this helps David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: the next step
"Erik" == Erik Andersen [EMAIL PROTECTED] writes: Erik On Fri Oct 20, 2000 at 05:02:48PM -0700, Karl M. Hegbloom wrote: Ok, cool. Do you have a patch queue for us? Erik My mailbox. I can also give folks write access... Ok; I'll just email anything I get time for. Erik The syscall layer is in a state of flux at the moment -- starting late last Erik night I began converting from asm syscall invocations to c ones, which makes Erik my life a lot easier and makes it much easier to port to new architectures. With any luck I'll understand the code well enough to help enough to impress someone into hiring me. Erik Don't you have a few years of school left? Getting anxious already? Erik ;-) Yes, a few more. -- We should not penalize the conscientious to coddle those who run brain-dead software. I am karlheg, of deB.ORG. You will be freed. Resistance is useful. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) http://www.debian.org/~karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Shared calendar software for the `debian-boot' team?
What exists in the way of shared calendars we can utilize to help co-ordinate our efforts? Work schedules, IRC meetings, video phone conferences, whatever we decide? There's a nice one for Gnome getting written, isn't there? Let's use it. It would be cool to all meet in one place for a week or two also for a mind meld. I'm up for it... Let me settle my living situation and we can start planning when and where. -- We should not penalize the conscientious to coddle those who run brain-dead software. I am karlheg, of deB.ORG. You will be freed. Resistance is useful. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) http://www.debian.org/~karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Co-maintainership of base packages by the debian-boot team?
"Adam" == Adam Di Carlo [EMAIL PROTECTED] writes: Adam Joey Hess [EMAIL PROTECTED] writes: [ ... ] all the disgusting stuff basedisks.sh has to do in the boot-floppies to create a debian base system. A lot of packages need to be cleaned up before we can just dpkg -i `cat base-debs` and have it work. I'd prefer to go with something that already works here to save time on the first cut. Adam Yes. More care should be given to the base set. We need to file bugs Adam now, and agressively, against them. I have a better idea. Let's take out the "middle man" somewhat... Adam A lot of people blame bf for delaying release but in fact we spent Adam much of our time waiting for fixes in base or kernels. Why wait around for someone else, who may be busy with something in their own immediate surroundings? I think we should *negotiate* to become co-maintainer's of those packages. Perhaps we should institute this in Policy? That the `debian-boot' team is the co-maintainer of each base package, giving us rights to make uploads, etc??? Should I attempt to draft a proposal? That would make each of the maintainers of base packages a member of our team. Each would retain main control over their package perhaps? [potential other thread here] ... those packages ought to be CVS tracked where we can all get at them also. Vendor tracked. Strict rules about how CVS is to be used, akin to what the DRI people use, perhaps? http://dri.sourceforge.net/cvspolicy.txt ... that and a tagging scheme something like how `cvs-buildpackage' is supposed to work? What do yous think? To keep control over the package in the hands of the maintainer (perhaps not necessary in all cases, but is in some), we could create a patch queue mailing list for each one. Each team member keeps an anoncvs checkout of them. When you modify something, you create a patch and ChangeLog, and mail it to the patch queue for that package, for the maintainer to review, reject or approve, apply, and commit. (This is how the XEmacs team handles it.) This model might work well for the entire Debian distribution, in fact. Not all packages need be vendor tracked, perhaps? Some are already in CVS and the maintainers are in close cahoots with the "upstream" maintainers. How can we make this work, so that we get along with the coopetition? Will `subversions' support this model? We need a shared calendar too... another thread... started. ... and webcams w/voice -- We should not penalize the conscientious to coddle those who run brain-dead software. I am karlheg, of deB.ORG. You will be freed. Resistance is useful. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) http://www.debian.org/~karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Red Hat installer via CVS ?
"Erik" == Erik Andersen [EMAIL PROTECTED] writes: Erik It will fit. Oh, yes. It will. ;-) Erik I'm sure it can be done. Though we may need to switch to libc5 or uclibc or Erik something more exotic (like the thin syscall wrapper libc thing on the RedHat Erik installer). Does Red Hat have anonymous CVS of their installer available? What about other distributions, such as Caldera? It would be good to have a spy line on their codes. -- We should not penalize the conscientious to coddle those who run brain-dead software. I am karlheg, of deB.ORG. You will be freed. Resistance is useful. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) http://www.debian.org/~karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: the next step
"Erik" == Erik Andersen [EMAIL PROTECTED] writes: Erik At Lineo (where I work) we have a tool called "Lipo" (written in perl) that Erik does the library reduction thing, and we have it working quite nicely on a Erik number of platforms. Can we use it? Erik I don't think uclibc is quite ready for use by the boot floppies -- but I think Erik it will be ready before the woody release. One thing that may need some Erik attention is arch support (such as Alpha or UltraSparc). Is it in CVS where we can pull it out as an included module or a side tree? Can you create a patch-queue like I mentioned previously? -- We should not penalize the conscientious to coddle those who run brain-dead software. I am karlheg, of deB.ORG. You will be freed. Resistance is useful. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) http://www.debian.org/~karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FALSE == 1
"Nick" == Nick Holgate [EMAIL PROTECTED] writes: Nick I have just spent couple of hours tracking down a problem with a minor patch Nick I made to the boot-floppies sources. It turns out that I made the assumption Nick that the macro FALSE would be defined as 0, when in fact dbootstrap.h Nick defines it as ((int) 1) and the corresponding TRUE definition as ((int) 0). Nick I have not checked, but could other boot-floppies hackers have also made the Nick same invalid assumption. I think this was done deliberately. It's using shell semantics, not C semantics for TRUE and FALSE. TRUE is 0 + No error has occured. FALSE is != 0 + the number indicates an error code. Otherwise, perhaps there has to be an error code global variable? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Red Hat installer via CVS ?
"Erik" == Erik Andersen [EMAIL PROTECTED] writes: Erik Re Caldera, I just asked Tim Riker (who quit from there a couple Erik of weeks ago and now sits in a cubicle next to mine). He says the Erik latest and greatest is not available via CVS, but the latest released Erik version can be grabbed from http://openlinux.org/lizard/ Looks like they've got CVS after all. -- We should not penalize the conscientious to coddle those who run brain-dead software. I am karlheg, of deB.ORG. You will be freed. Resistance is useful. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) http://www.debian.org/~karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FALSE == 1
"Erik" == Erik Andersen [EMAIL PROTECTED] writes: Erik Arguably, I should have fixed up the sash code to use C semantics before Erik including it. But then hindsight is 20/20, No, it's catch-22-22. -- We should not penalize the conscientious to coddle those who run brain-dead software. I am karlheg, of deB.ORG. You will be freed. Resistance is useful. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) http://www.debian.org/~karlheg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [debian-installer] Build setup?
"Joey" == Joey Hess [EMAIL PROTECTED] writes: Joey Martin Keegan wrote: I found the toplevel Makefile pretty annoying last time I was building boot-floppies; it called itself recursively with a separate make process, which tended to make make -n and make -j unusable. Is Joey Hess' new installer system doing to do away with the current source tree in its entirety? Joey That's really up to the folks who maintain the modules. It should be Joey possible for someone to maintain a module themselves if they want, in Joey which case the "build system" will be a simple debian/rules plus perhaps Joey a makefile -- not unlike any other package. Please read "Recursive Make Considered Harmful" URL:http://www.canb.auug.org.au/~millerp/rmch/recu-make-cons-harm.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[debian-installer] /etc/lilo.conf
For the new installer, I think that "/etc/lilo.conf" should be pulled out into a conffile, with the `lilo' package, and configured from there, so that upgrading `lilo' will upgrade that also. This way, for instance, folks upgrading `slink' to `potato' would have had an upgraded `lilo.conf' with the `lba32' switch in it, etc. Yes, I am aware that we may well switch to GRUB. That's almost a whole 'nother thing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[debian-installer] Build setup?
How should we design the `debian-installer' build system? I think that it ought to be very granular, with a complex dependancy structure, so that changing one thing doesn't involve a long rebuild cycle before a testable image is generated. Makeing it work with the `-j' switch would be a Good Thing, and should also be a goal. Perhaps a non-recursive project Makefile(s) structure should be cooked up as well. (Have yous read "Recursive Make Considered Harmful"?) Therefore, it ought to be implemented mostly in GNU Make. We can of course construct complex commands using shell and/or perl scripts, and call those from the Makefile's, but the scripts should not build more than one target each, so that our Makefile's prerequisites structure can hold the necessary information to restart a mostly built run. It will save us lots of time during development. Nothing will be rebuilt unnecessarily. (of course that will cut down on our IRC time, but it's not a bad tradeoff really. I'm boring in IRC, remember? It will spare you all!) Some folks will call it very obfusciated... but surely they have never looked at a `configure' script or the m4 macros that create it... Speaking of which; I imagine we may need to use `autoconf' so our system will build more easily on Hurd? (YTMAWBK) It ought to take advantage of GNU Make's `include' directive, and be quite modular. This way, each architecture's archdep stuff can be sepped out into a module. Each logical stage of the build ought to have its own module. I began doing that on that side branch I created in the `boot-floppies' repository. Maybe some of that is useable, if for nothing but an example. We can finally do away with that `release.sh' crock, and have the build setup put the files into the right place in a staging directory to begin with. For complex dependancies, I wonder about the following... will this work? I've not researched it yet. (and I must remind; I'll not have time to work much on this until next Summer, unless I cut back on school hours over Winter and Spring... I might just do that.) I don't know how to implement it yet. Details. We build the base system by opening the .deb's into a chroot. What if we use the *.list files on the LHS of autogen Make targets, and the *.deb they came from on the RHS? Then, rather than erase all of the chroot between builds, we leave it intact. If a new version of a *.deb arrives at the developer's mirror, only that particular *.deb needs to be re-unpacked and configured, letting Make handle the dependancy. A similar setup can be used for the other diskette images... the main idea being to minimize the amount of image rebuilding needing to be done when a small change is made to part of the system by a developer. Of course, a `make distclean' and total from-scratch rebuild will need to be done prior to releases being made, just to ensure that the system will work correctly on any arbitrary hacker's machine when they "apt-get source debian-installer". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
"Torsten" == Torsten Landschoff [EMAIL PROTECTED] writes: Torsten On Tue, Sep 19, 2000 at 10:47:20AM +0200, Sebastien Chaumat wrote: Let me explain replicator's point of view. We assume that we want to install 99% identical contents on all of our computers (classrooms, desktops computers in our lab). So we use rsync to speed things up and, at the end of the install we do the 1% leaving job. Torsten You need a decent network for that. That's not always available. It is Torsten nice if you have it though. Have yous read the "Remote Boot mini-HOWTO"? Have a look. It's in `doc-linux-html' IIRC. They describe a setup used for school computer labs where they can boot any OS, and boot from an image kept on a central server. Maybe someone could package it up? We recommend cfengine in post-installation (as a front end to apt if we want to deal with packages). Torsten I have to say that I partly hate and partly love cfengine. We are configuring Torsten our systems using it but I am looking for an alternative. Some utility that Torsten is better suited for editing config files... Isn't `debconf' supposed to take on some of that all? With off-box config databases, pre-configuration, etc? It's a lot (really) faster than unpacking packages. Torsten Depends on the network ;) Unpacking is quite fast on our systems here but Torsten configuring takes a lot of time... `debconf's answer to `kickstart' again; set up one box, enter stuff for the differing info on the other ones, and set the thing off to install them all??? Will such a thing exist someday? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: thinkpad 240
"Sid" == Sid Bertheaud [EMAIL PROTECTED] writes: Sid trying a floppy install. hangs up on 2 disk the root.bin. gives i/o message Sid and I have tried 4 disks. Sid Goes like this. Sid ramdisk0 floppy=thinkpad Try once without the floppy=thinkpad and see if it works. Sid evedrying appears okay and then load disk two and it bugs out. Sid Any special things i should know about thinkpad 240? Perhaps if you ask IBM, they can help. They are a Linux friendly company, afaik. Sid Until then my computers a paperweight. Not for long, we hope. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which task package installs gpm?
"Ben" == Ben Gertzfield [EMAIL PROTECTED] writes: "Karl" == Karl M Hegbloom [EMAIL PROTECTED] writes: Karl It would be good to check and see how powerful and loaded Karl the machine is, and not start too much going at once if it's Karl not that powerful. But if it can deal with it, we ought to, Karl by default, start up `gkrellm', `xmms', and run a `gmix' to Karl set some reasonable mixer defaults alsa. There ought to be Karl an *.ogg in the XMMS when it's first time launched with a Karl message from us. (Perhaps singing "(Join us now and) Free Karl the Software" as a chorus? I believe we have a few Karl musicians amoung our ranks.) Ben If this is done, it might be nice to have XMMS default to using Ben the esound output plugin; otherwise it takes control of the Ben sound card and doesn't play well at all with GNOME. Agreed. And we should ship the xiph.org Ogg Vorbis output driver also... that is, if it really can replace the Mp3 format. I tried it and it works pretty good. Their current CVS didn't build the other day, but I imagine it will again soon. There is debian/* stuff already in the CVS too. :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which task package installs gpm?
"Michael" == Michael S Fischer [EMAIL PROTECTED] writes: Michael On Thu, Sep 21, 2000 at 12:23:19AM -0800, Ethan Benson wrote: IMO debian already has a system pretty darn close to kickstart, with the above commands i can clone a system at *any* time, not just when installing. with kickstart you can only create the kickstart file at install time (AFAIK anyway) and redhat installers are notorious for ignoring your package selections and installing whatever it feels like. so your still stuck going through packages and removing crap anyway. Michael I strongly disagree with this assertion. You may clone a system's Michael package inventory this way, but in doing so you will not clone the Michael actual system configuration. Right. Michael In addition, this process requires manual user intervention. Show me Michael a process that approaches the speed of kickstart (which to me is the Michael most important factor of all) and then we can talk. It would need at least some manual setup; preconfiguration, no matter what, right? this a way to export debconf answers and your pretty much set. (i don't know what kickstart does about things like networking) Michael I think that relying on debconf as a catch-all tool for system Michael configuration is a bad idea. The realm of configuration possibilities Michael is just too large for us to rely on package maintainers to make an Michael absolutely perfect configuration tool in every single package. It would be a major project to write `debconf' support for even just the core packages, I guess. It would be neat if all software had a common interface for configuration. If it was all consolidated into one database; or a distributed database as for the `debconf' proposal... and an "API" defined for accessing it. All of the daemons and everything would need to be patched to take advantage of it. This would be a Linux community wide project, not just a Debian one. Like a `registry' for Linux, but improve on Microsoft's design, I suppose. Would it work well using LDAP, an SQL server, or would writing its own database setup be best? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I'm back on list...
I'm back, folks. Hello, everyone. I will not have much time for development work until next summer. Perhaps then I can assist more... but I for sure want to be involved in the discussion. I stand to learn a lot from being involved with this project. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Boot Problem
"Adam" == Adam Di Carlo [EMAIL PROTECTED] writes: Adam Sorry we haven't been able to help you here. Adam The only time I've heard of another reporting this problem, it was bad Adam memory in the machine. You might try a memory scrubber. Adam This is a hardware/kernel problem -- not much we can do about it in Adam this group. Why was I CC'd? I did not see the conversation; I've been off-list because of time constraints. Is it sig 11 (segv) problems? That's most often the CPU overheating. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bf-utf, gnewt
"Taketoshi" == Taketoshi Sano [EMAIL PROTECTED] writes: Taketoshi [EMAIL PROTECTED] (Karl M. Hegbloom) writes: I started trying to port the patches I found in the bf-utf repository over to the `slang' Newt (snewt) in the `gnewt' module. Taketoshi Thanks for working on bf-utf. Are those changes backwards compatible? I know nothing about that. Note that there is a `minislang' in `gnewt' that I think we can use... I did not apply any patches to it. Taketoshi What do you mean with "backward compatible" ? I think the back-porting Taketoshi of the patch (created with slang 1.4.0) for older 1.3 series is really Taketoshi hard because of many difference between 1.3 and 1.4, but you can try it Taketoshi anyway. If you get success, then we can use it happily. I'm concerned with whether, after patching it to work with utf8 wide characters, it will still function as before, with standard ascii? Will I be able to use it still, or will it only work for asian text, after the patches? Taketoshi Do you think that `minislang' is usable for us in bf-utf for potato ? I hope so. The patches from the other libslang will need to be ported to it. Again, will that be compatible with standard ASCII still?? If it's backwards compatible, we should switch to the `gnewt' tree rather than the `bf-utf' one for Newt and Slang. Taketoshi I will checkout that gnewt modules from cvs.debian.org. Ok, good. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [woody,debinst] (Was: Re: [dbootstrap] `newt' and `boxes.c', `bogl' and `bowl'[, `???' and `boxeX.c'?])
"Erik" == Erik Andersen [EMAIL PROTECTED] writes: Erik Agreed re parted. I think a cool project would be hacking a GUI similar to Erik cfdisk into parted... Yes, that would be a good thing to do. If we used Newt for the interface, we'd have X for free, with `gnewt'. Erik Using compressed ext2 could also work. Works just like regular ext2 until you Erik chattr files, at which point they are transparently compressed/uncompressed. Does that already just work, or does it require patches to the kernel? It tried the `chattr' command, and it didn't appear to do anything. How do I know the file is really compressed? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[woody,debinst] (Was: Re: [dbootstrap] `newt' and `boxes.c', `bogl' and `bowl'[, `???' and `boxeX.c'?])
"Bruce" == Bruce Sass [EMAIL PROTECTED] writes:
Bruce Hello Karl,
Bruce I was gonna send this to the list, then noticed the subject was
Bruce [dbootstrap], not [woody]... maybe you will find it interesting.
I posted to the list, since that's where the other team members will
be. The more the merrier. Hope you don't mind, Bruce.
Karl I discovered today that the `boot-floppies' "root.bin" has the entire
Karl libnewt.so on it, rather than a subset as I had assumed previously.
Karl I somehow never noted that there's a libslang.pic, but not a
Karl libnewt.pic.
Bruce I hadn't got as far as looking at what is available yet, it's a variable
Bruce anyways ;). Has anyone created a map of the structure yet (how the
Bruce installation will be modularized, etc.)?
Yes. Joey Hess has started a `debinst' repository on kitenet.net.
URL:http://kitenet.net/cgi-bin/cvsweb/joey-cvs/public/packages/debinst
(Joey? Please let me know if that's not meant for public
consumption. If that's the case, can you please move it to c.d.o?)
Karl Given that the full functionality of Newt is at our disposal, I think
Karl we ought to put some work into the GUI, and utilize things like
Karl newtGrid's and whatnot. I'm going to start learning Newt, and see
Karl what I can come up with.
Karl I'll try to keep in mind that there needs to be a generic interface
Karl that can be implemented by other GUI frontends, in the way that
Karl `boxes.c' and `bowl' do it now. I'm going to break things on purpose
Karl though, just for the freedom of it. I'll do a newt interface, if I
Karl can, and not worry too much about `bogl' for now.
Bruce What does debconf support...
The Woody `debconf' uses Perl and a really neat toolkit written by
Joey Hess called `libterm-stool-perl', which in turn uses
`libterm-slang-perl'. Perl is way to large for the boot floppy, at
least for the first stage.
Karl Any ideas as to what it should look like and how it ought to look? I
Karl took a hike up the hill today and thought about it some. For one
Karl thing, the partition / format / fstab stuff ought not be serial; it
Karl ought to be one or two screens of setup, then it runs all the
Karl commands to partition, format and mount.
Bruce I've been thinking about this off'n'on since slink's bf (or was it
Bruce debian-admin when debconf started(?); ya, I'm a floater :).
Bruce Mmm, I really should have a look at debconf, shrug later.
Bruce One should be able to have generic frontends for text, newt, GUI, ...;
Bruce and installers for each item needing attention. The installation
Bruce scripts for each resource would drive the frontend (or is it the
Bruce reverse?) in whatever manner was appropriate for the UI (linear, menu,
Bruce etc.), maybe it can be prototyped by creating package files in the
Bruce dpkg DB (for the sake of discussion, dev-device.debs).
Yes, that's essentially how it works, as I understand it. I've
honestly only given it a cursory once over, and pushed it back in my
queue of things to learn about in the future.
Related to this all are things like the Gnome library for a
"registry" like configuration database, and stuff similar to Red
Hat's `kickstart'.
It would be good to have a shared library for reading configuration
data with, and to have the multi-host database thing for any
arbitrary program (bind, smtp-server, init.d, backup set definitions,
etc.). There ought to be a site-wide one for more global data, and a
per-host one for more local data, with the site-wide one supporting
centralized configureation data for satellite systems if
desired. (clusters, thin clients, student workstations) I could be
`dhcp' / `ldap' like, I guess. There's a book out, iirc from
O'Reilly, on "directory servers" or somesuch. It would be worth a
read during thourough research prior to attempting a solution.
(let's kill `linuxconf' once and for all)
Bruce e.g., create a package for each harddrive, supply {post,pre}.{inst,rm}
Bruce scripts that install and configure a harddrive; an initial installation
Bruce could do "dpkg --install dev-hda.deb", a running system would use "dpkg
Bruce --configure dev-hda" whenever bits need to be fiddled with.
Hmmm. Sort of like a shell script you'd hook into the rc.S script
that would use `sfdisk' and `mkfs', etc. to auto-install when you
know the drive is factory fresh or burnable... but done up right
with a tool made for the purpose. I imagine that the folks at VA
Linux have already put quite a lot of thought into this problem.
(perhaps when I get some more college out of the way they'd like to
teach me to help them with it)
Bruce Dbootstrap would need to: set up a minimal dpkg system (just the guts,
Bruce flag the packages involved as `reinstall required'), "scan"[1] the setup
Bruce to create an initial set of
Re: Initial problem
"rslittle" == rslittle [EMAIL PROTECTED] writes: rslittle I am using a 486 with a cd player, floppy drive and win95. I want to rslittle make boot floppies. CD is not bootable. There is no true dos capability rslittle to boot into in order to run rawrite. Any suggestions? Care to send a rslittle file with everything zipped so I can make a dos boot floppy and launch rslittle rawrite from the HD? Why can't you just download that stuff? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [dbootstrap] Resume from http-fetch not working right.
"Karl" == Karl M Hegbloom [EMAIL PROTECTED] writes: Karl If I use net-fetch to get base2_2.tgz, and stop it in the middle, Karl then attempt to resume it, the zcat | tar command fails. Fixed in CVS. Please check my work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#64179: Testers needed: This bug might still be present.
"Karl" == Karl M Hegbloom [EMAIL PROTECTED] writes: Karl I spoke too soon... This bug might still be present. Karl It does stop if you push Enter while a transfer is running. But Karl perhaps if the transfer hangs, there's a point where it cannot be Karl interrupted currently. Karl Will someone please lend a hand and check for this? Look up the bug Karl in BTS. I may have fixed this last night. There was a `usleep(25)' in there that I commented off... that might have been our hang. Perhaps it's a debugging artifact??? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to set up an install server ?
"Michael" == Michael Agbaglo [EMAIL PROTECTED] writes: Michael Under solaris thing are quite simple: You can set thing up that Michael partition your HD as you like install the OS and myabe other software... Michael I haven't seen thing like this under solaris especially Debian. I can't Michael imagine why the install/rescue disk isn't capable of booting from net... Imagine sitting down and writing the code that makes it do that! Go for it, Michael. If it works, it can become part of Debian. Joey Hess has started a design document for the Woody installation system. Look in the archives for it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#64179: stop button while downloading over http does nothing
"Marcel" == Marcel Harkema [EMAIL PROTECTED] writes: Marcel On Tue, May 16, 2000 at 21:50 +0200, Marcel Harkema wrote: On Mon, May 15, 2000 at 22:32 -0700, Randolph Chung wrote: When you're downloading the base system via dbootstrap and realize the connection was lost (even though dbootstrap didn't notice), trying to press enter to make it stop doesn't work. You have to kill dbootstrap by hand to make it restart and try again (with no resume at all :( ) marcel: any ideas? i'll take a look at this tomorrow i guess can also try to work http reget in. randolph No ideas yet. I plan to look at the code on wednesday night. Embedding a full http client is still a good idea imho, since the current code is only a hack. Unfortunately the 'snarf' stuff was never finished. Marcel Ack, I thought you were mailing about the 'powerpc http' bug... I really Marcel should read all of the mail before I reply. I do have an idea what is Marcel wrong here. Anyway, will also look at this bug tomorrow night. This is fixed in 2.2.15 - I just tested it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[dbootstrap] Ctrl-C will break out of several places now.
I just commited changes to `dbootstrap' that make it so you can push `Ctrl-C' to break out of a failing DNS lookup and the subsequent `connect()' in "http-fetch.c", and from an attempting NFS mount in "choose_medium.c". Yes, I'm an escapist. ;-) -- A few months in the laboratory often saves several hours at the library. mailto:[EMAIL PROTECTED] (Karl M. Hegbloom) irc: nick karlheg on irc.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
