Fixed in NMU of boot-floppies 3.0.19
tag 108477 + fixed tag 118997 + fixed tag 119825 + fixed tag 119834 + fixed tag 120386 + fixed tag 123926 + fixed tag 123948 + fixed tag 123973 + fixed tag 125646 + fixed tag 125683 + fixed tag 125999 + fixed tag 126035 + fixed tag 126205 + fixed tag 126489 + fixed tag 127370 + fixed tag 127405 + fixed tag 127413 + fixed tag 127436 + fixed tag 127521 + fixed tag 127524 + fixed tag 127550 + fixed tag 127583 + fixed tag 127955 + fixed tag 128237 + fixed tag 129037 + fixed tag 129470 + fixed tag 129837 + fixed tag 129940 + fixed tag 131121 + fixed tag 131409 + fixed tag 94435 + fixed quit This message was generated automatically in response to a non-maintainer upload. The .changes file follows. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 22 Jan 2002 13:14:24 -0500 Source: boot-floppies Binary: boot-floppies install-doc Architecture: source powerpc all Version: 3.0.19 Distribution: unstable Urgency: low Maintainer: Debian Install System Team <[EMAIL PROTECTED]> Changed-By: Adam Di Carlo <[EMAIL PROTECTED]> Description: boot-floppies - Scripts to create the Debian installation system install-doc - Documentation for Debian installation and release notes Closes: 94435 108477 118997 119825 119834 120386 123926 123948 123973 125646 125683 125999 126035 126205 126489 127370 127405 127413 127436 127521 127524 127550 127583 127955 128237 129037 129470 129837 129940 131121 131409 Changes: boot-floppies (3.0.19) unstable; urgency=low . * really notable changes: - reiserfs and udma100-ext3 flavors have been replaced with the new bf2.4 flavor (using kernel 2.4.17) - support for "new-powermac" architecture . * bugs closed by using new stuff from the archive; closes: #127524 * Matt Kraai - tell pcmcia to use dhclient, closes: #125683 - install the MBR on the first available IDE disk, closes: #119825 - configure pcmcia interface properly, closes: #118997 * Phil Blundell - fix for documentation display of non-English dbootstrap msgs - avoid comic situation at reboot time where the user is prompted to take the CD out of the drive, but the drawer is still locked - reformat French release notes for display (other languages still need checking), closes: #125646 - check that LINGUA is set to C when LC is enabled, closes: #126035 - enable Japanese on arm - try mounting floppy images with type "auto" first, closes: #94435 - add support for new arm subarch "lart"; reorganise arm build a bit - enable LC on alpha - remove Greek keymap (it breaks the build with recent console-data) - correct LANGUAGE bogosity in dbootstrap_settings, closes: #127413 * Adam Di Carlo - enable i18n for i386's reiserfs flavor, which was indicated as enabled before but really wasn't - reboot using the 'reboot' command rather than signalling PID 1, closes: #119834 - require whiptail >= 0.50.17-9, closes: #125999 - require debootstrap >= 0.1.16 * Colin Walters - support for "new-powermac" architecture. closes: #126489, #127955, #131409 - Yaboot can now boot from XFS and ext3, so allow the user to make /boot with these filesystem types - kill any DHCP daemon running if the user chooses static networking, closes: #126205 - minor rescue.sh cleanups, fixes - Add EXTRACT_LIST_powerpc_newpmac and SMALL_BASE_LIST_powerpc_newpmac - fix rootdisk.sh to install yabootwrapper for newpmac too * Eduard Bloch - when mounting DOS partitions, use vfat instead of msdos where possible, closes: #123973 - added tune2fs to the extract list, maybe needed for ext3 conversion - enable i18n for i386's udma100-ext3 flavor, was a typo in rootdisk.sh - German translation updates - additional check to make sure that ext3 is supported before choosing it - Adapted messages for choose-target dialogs when making a problem report - bf2.4 integration: README, new rules in i386.rules - mkreiserfs in all flavors. Since we do have the space, the user should be used to replace the kernel and use reiserfs with any flavor - preliminary dbootstrap support for locales preinstallation - made a workaround to store the list of loaded modules in /etc/modules - updated libc version in rootdisk.sh to 2.2.5 - dropped non-C message files from modconfs tarball (never used) * John H. Robinson, IV - when mounting partitions of type 82, test the actual filesystem type - trouble report log now gzipped - added ``livecd'' kernel and base system installation method - re-worked ``mounted'' kernel and base system installation method - Closes: #108477, #123926, #127521 * Chris Tillman: documentation updates - revise BootX instructions for OldWorld Mac booting
Fixed in NMU of boot-floppies 3.0.15
tag 105451 + fixed tag 113554 + fixed tag 113882 + fixed tag 114328 + fixed tag 114605 + fixed tag 115018 + fixed tag 115174 + fixed quit This message was generated automatically in response to a non-maintainer upload. The .changes file follows. -BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Tue, 16 Oct 2001 15:13:41 -0400 Source: boot-floppies Binary: boot-floppies install-doc Architecture: source powerpc all Version: 3.0.15 Distribution: unstable Urgency: low Maintainer: Debian Install System Team <[EMAIL PROTECTED]> Changed-By: Adam Di Carlo <[EMAIL PROTECTED]> Description: boot-floppies - Scripts to create the Debian installation system install-doc - Documentation for Debian installation and release notes Closes: 105451 113554 113882 114328 114605 115018 115174 Changes: boot-floppies (3.0.15) unstable; urgency=low . * Adam Di Carlo - document the serial port limitations on i386, ttyS0 -- ttyS3 closes: #105451 - s390 was not shipping images-1.44/drivers* for some reason, fixed - arm requires catsboot for building - dbootstrap: reword most of the main menu descriptives; stop saying the system is "experimental and untested" (not to say it's perfect!) - new upstream debootstrap fixes some things; closes: #113882 - SPARC: ethtool, used on the root disk is now in it's own package * Christian T. Steigies - add a note to m68k quickinstall guides - removed mac-de-latin1-nodeadkeys for m68k, loadkeys can not load it - rescue-boot.en.sgml: Atari can boot from the harddisk, too * David Kimdon - fix fetching *_all.deb packages from local incoming dir - add easier linting to docs, fix some lint issues - Danish translation update thanks to Claus Hindsgaul <[EMAIL PROTECTED]> - fix broken sgml (closes: #114328) - use busybox ifconfig, route, saving some space - use wget rather than our own http code (saves 1.6k) - support ftp driver and base install - remove cruft, add boxProgress() widget, make vaproblemBox() support longer messages - add cancel button to lilo install question (closes: #115174) * Chris Tillman - fix urls in pdf documentation - remove references to baseX_X.tgz (closes: #113554) - meta key on Macs is 'Option' rather than 'Command' - move around sections in all languages so they match english (dbootstrap.sgml is replaced by boot-new.sgml and kernel.sgml other fixups) - add pointers to help docs after final login * Ethan Benson - Make lilo configuration XFS aware. (thanks to Colin Walters) - Remove filesystem caveats regarding yaboot since yaboot can now read XFS. * Henning Heninold - Adding some Dokumentation for mips - mips and mipsel now using kernel 2.4.9 * Gerhard Tonn - disable temporarily some pam settings to run base-config from telnet session for s390 - drop drivers390-1.bin for s390 - add netsetup script for s390 and consider network parameters entered during initial netsetup in dbootstrap - some inittab changes for s390 - add nfs modules for s390 - consider module parameters entered during initial netsetup in dbootstrap - (initial) peer configuration for s390 - implement pointopoint setup (closes: #115018) - reboot system -> halt system for s390 - add dasdfmt for 'fresh' disks - disable make boot-floppy action for s390 - ensure that base.config is not called twice - call mke2fs -b 4096 on s390 - treat s390 console similar to serial console - add dynamic attach menu on s390 * Richard Hirst - fix delay param in elilo.conf for ia64 - call update_console_info() if serial console used on ia64 - support serial consoles up to ttyS5, needed for ia64 - rootdisk.sh tried to specify multiple exe's with ld-linux.so.2 --list, which is invalid, so library check was ineffective. Changed to use a for loop. * Ben Collins - sun4u uses 2.4.10 now - Fix subarch usage for sun4* in rescue.sh * Guido Guenther - add initrd support for mips - dboostrap: subarch is r4k-ip22 not ip22 - add mips(el) support to tftpboot.sh - compress mips kernel on rescue disc and use resc1440 instead of resc2880 - fix directory layout created by release.sh for mips - finally disable pcmcia on mips(el) * Eduard Bloch - deboostrap german po updates - routine checking for bootable CDs, helping clueless users - wget build dependancy for all archs (closes: #114605) Files: 875e62a67d6c217ec91ba1fd74068cf4 3120642 devel extra boot-floppies_3.0.15_all.deb a3fc65902b22e1c8e63b1e47e6b50cce 33217423 byhand - bf-arch_3.0.15_powerpc.tar.gz dd439181606f2fa7f2844491cc8c3166 844 byhand - bf-archive-install_3.0.15_powerpc.sh 66b310f24c24d4b14fb73d96480ea406 4143178 byhand
Fixed in NMU of boot-floppies 3.0.13
tag 108317 + fixed tag 109578 + fixed quit This message was generated automatically in response to a non-maintainer upload. The .changes file follows. -BEGIN PGP SIGNED MESSAGE- Format: 1.7 Date: Fri, 24 Aug 2001 09:01:51 -0400 Source: boot-floppies Binary: boot-floppies install-doc Architecture: source powerpc all Version: 3.0.13 Distribution: unstable Urgency: low Maintainer: Debian Install System Team <[EMAIL PROTECTED]> Changed-By: Adam Di Carlo <[EMAIL PROTECTED]> Description: install-doc - Documentation for Debian installation and release notes Closes: 108317 109578 Changes: boot-floppies (3.0.13) unstable; urgency=low . * Christian T. Steigies - m68k builds with libc 2.2.4 - include amigainstall.tgz, which somehow dropped off * Eduard Bloch: - i386 flavor shows up on rescue disk too - German dbootstrap updates - build improvements - prepatches for ext3 support - prepatches for parted support (not sure if we will neable this) * Jacobo Tarrio: Galician dbootstrap updates * Risko Gergely <[EMAIL PROTECTED]>: Hungarian updates * Erik Andersen: - support for w2k dynamic partitions * Adam Di Carlo: - fix the problem where cardmgr and such weren't on the driver disks as they should have been closes: #109578, #108317 - build improvements Files: 31f23e4f218ea1aaaf38ac13289b3730 32351467 byhand - bf-arch_3.0.13_powerpc.tar.gz b5c2fe844bc5d2d4125771adb9855668 844 byhand - bf-archive-install_3.0.13_powerpc.sh 42afbf62026e3e1ac162e67a755be8df 4082901 byhand - bf-doc_3.0.13_powerpc.tar.gz 621a0d6db58b9d976ac9fd25908e54ec 9224 byhand - bf-misc_3.0.13_powerpc.tar.gz bb5cabcb1fbcf791180fcaecd7a04fa6 4183442 doc extra install-doc_3.0.13_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iQCVAwUBO4aOko/8QF79WmfNAQEo8gP/S7pNpPnl/SE6xLaHDAGkIMbznqKF9D8e UMMDrBjMZ8iBYgjtQS1X5pPXqTy3ORp7v8VtBgHlPSFzAIbdhi/6y/aRMI4Jz5L/ h/UGAAtdWTKOsXx31Bkxy+K08oY2xH8VQpFAXTGN5HgF2iKcfyqC9yKYAYtqMyCj bwRRC00r/cM= =7Atd -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: success with cvs boot-floppies on powerpc
Ethan Benson <[EMAIL PROTECTED]> writes: > On Sun, Jun 24, 2001 at 12:26:06AM -0800, Ethan Benson wrote: > > > > the remaining problems are: > > one other thing, dhcp/bootp network configuration failed, i have only > a bootp server which works fine for netbooting this machine, and > potato boot-floppies liked it fine for network configuration (even > macos liked it). File this as a bug. Mentioned the package and version that has bootpd in it (the server side). -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install Manual Updates Phase 2
Quite honestly, there are only two cases that I see are all that valid: (a) if you're a single user, single disk workstation, just make one partition for swap, and one big one for everything else (b) if you're a server, than you bettah split out /tmp, /var, /usr, possibly /var/mail, yadda yadda sysadmin black art I don't see any benefit to a user in situation (a) in making more than one partition. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems with the IBM Power Series 400 (601e/PReP arch)
"Andreas Sliwka" <[EMAIL PROTECTED]> writes: > Hi, > I recently got the machine mentioned in the subject. I tried to install it > (currently AIX is infecting the harddrive), but failed. After doing some > deep searches on the net I found out that: > - in general IBM PReP machines /should/ work Yes. > - the build-in graphics adapter (Diamond Viper Pro with Weitek 9000 chip) > is a bitch and /not/ supported. Not supported by Linux or just by the install process we provide? If the latter, sounds like a bug should be filed against the kernel-image package you are using. > The normal (and only) behaviour of a (linux) boot try is : > - normal PowerPC screen > - a lot of reading from the boot disk. > - I change the disks and press enter > - nothing. Are you testing with woody or potato versions? > Now my question: Would it be possible to use the serial line to install > the machine? Since I cant use the screen (and maybe the keyboard) this is > the only possibility I can think of ... Yes, should be possible, see the install manual. there are specialized PREP instructions as well. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing on new iBook dual USB
Well, if you have suggestions for mac-fdisk or whatever, you should file a wishlist bug against it. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: time for boot-floppies 3.0.0
Anthony Towns <[EMAIL PROTECTED]> writes: > Personally, I'd make it 2.3.99 or something, and do 3.0.0 in a few days > or a week when (a) floppy/mounted installs of base appear in the UI and > (b) when we have pcmcia modules; but I've been known to be too obsessed > with drama in the past. Nah, 3.0.x is change is not for major update but just to sync with the Woody version number. Actually, I'm going to number it 3.0.7 (7th woody version). > Aside from (a) and (b) above, is there anything the potato boot-floppies > do particularly better than woody boot-floppies at this point that anyone > knows of? PCMCIA, badblock scan. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap-0.1.14 breaks boot-floppies
Ethan Benson <[EMAIL PROTECTED]> writes: > i commited a fix for it, powerpc should have debootstrap tomorrow now > that the buildd builds it. other archs need to catch up anyway. (who > else even has b-f working yet?) Sparc, i386; dunno about m68k testing but they have a build. So -- I need to wait for new debootstrap 0.1.15 w/o the 'seq' dependancy? Someone needs to help me so I trigger the next boot-floppies build at the right time. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian install system approach
Anthony Towns <[EMAIL PROTECTED]> writes: > Anyway, the logic isn't backwards, it's just looking more at getting > things right in the future than at the moment. In particular, for > future releases we need to get in the habit of always having working > boot-floppies, even when we're not expecting a freeze for some time yet. > The benefits of this are mainly in that it gives us more flexibility > in choosing when we freeze and when we release: we don't have to worry > about spending six months getting boot-floppies working again, and we can > change the boot-floppies development philosophy from "just hack it so > it works" to "make it pleasant and functional". Well, "boot-floppies" per se is always going to be "just hack it until it works", because that is a legacy, nasty, end-of-life piece of software. To prevent confusion, I suggest you use the term "debian install system" to mean the install system in general, which is what I think you mean here, and boot-floppies (or b-f), debian-installer (or d-i) to mean specific software. If you review the CVS changelogs for b-f, you'll see the stretch of time where things weren't really working all that well (until end of May) were caused by the changes we felt were worth making (replacing busybox with the packaged version, replacing base with debootstrap) primarily. It's pretty much true that any software the decides to make some deep changes in how it works will subsequently go though a period of instability. You seem to be wishing there was no period of instability -- I don't think that can happen. Another fact you may have overlooked was that my attention at least was still pretty fixed on the stable updates through the end of March, 2001. Work in earnest on woody began in April. >From my perspective, that's not all that bad -- functional Woody boot-floppies in less than 3 months, including adding some new ports and significant PowerPC bootconfig features. The only reason we were able to achieve that was because the woody version is an incremental update only to the Potato version. In short, I don't see how turnaround could be faster is to have completely separate teams for post-release stable updates and another team working on the next release. Luckily, we *will* have this situation in Woody/sid because Joey Hess is driving Debian-installer and I'm not involved in it (except perhaps for the installation manual). However, on the post-sid release, JoeyH will have the same problem that you're complaining about -- time I spent on post-release updates to potato boot-floppies ends up pushing back the following release. > What this means is we've got to be able to develop boot-floppies > even in spite of instabilities in the base system. So we've (I've) > got to be debootstrap so it doesn't break as readily with changes in > the base-system; and we've got to work around problems with busybox and > whatever else. > > Again, the idea is that after woody -boot will be able to continue > working on the installation system, and -testing will be able to continue > testing upgrades and new installs for the next release, even as it's > under development. Again, not splitting stable maint and unstable devel means you're going to have the same problems (eventually). > For the moment, what that means is I'm not starting the freeze until b-f's > start working with a non-frozen base. What does this mean? I don't understand it... What criteria must be met before you will freeze base? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: configuration of base packages
Ethan Benson <[EMAIL PROTECTED]> writes: > there was no MTA installed in the base system until now. i remember > because i never had to --purge exim when installing postfix on new > installs, unless i ran dselect and forgot to fix it there. No, I think you're right. In fact, http://http.us.debian.org/debian/dists/potato/main/disks-i386/current/basecont.txt> proves that you're right. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: configuration of base packages
Joey Hess <[EMAIL PROTECTED]> writes: > I'm trying to remember when exim got configured in potato installs. Was > it even installed as part of the base system back then? Could someone > with a test machine do an install and check? Yes, it would stop and ask you on postinst, IIRC. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.3.6 uploaded
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > On the other issue, building 2.3.6 in parallel, it failed now two times in a > row. First, vmelilo was not installed (need to be added in make check, > build-depends [m68k] or somewhere). Ok fixed, I hope. > But this is not true, there are 8 loop devices, only the first one was still > "in use" from the previous try. I didn't check the source, but does the > script explicitely look for loop0? That would not be so nice then. Restarted > yet another build... can't help you on this one. Maybe reboot is needed. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: configuration of base packages
Matt Kraai <[EMAIL PROTECTED]> writes: > Now, the problem. There does not appear to be any obvious time in > which the base packages are configured. For example, I am never > asked how to setup exim so that email works correctly. This needs > to be fixed before the release. Should we have base-config > dpkg-reconfigure all the base packages? It seems like it should, yes. Perhaps Joey Hess could opine on this, or else, file it as a bug on base-config. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.3.6 uploaded
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > > You say "does not fail at this place" -- where does it fail, then? > It didn't fail at all until I went home yesterday. Remember, on my home box > it built fine and even worked to some extent (I didn't try downloading all > the base stuff over my phone line, and it didn't like my partial local > mirror). > It failed when I was disconnected, but it was looking good until then. But > now with debootstrap buggy (?) I wonder if its worth the effort to try it > again... I would say you should focus your efforts on getting *some* recent version (2.3.5, 2.3.6, I don't care, just *anything*) of boot-floppies uploaded and installed into the archive. That's the first priority by far... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: more space spared in e2fsprogs-bf
Yann Dirson <[EMAIL PROTECTED]> writes: > Unless you have objections, I'll build e2fsprogs-bf with -Os. > Probably many other packages would benefit from this flag as well... Sounds good to me. Oh, I heard a rumor this package is having trouble building in non-i386 arches. Hopefully you can look at addressing that quickly, because I can't really adopt this package in boot-floppies until it's built for all arches. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dell 2500 RAID5
Shérif Hocine <[EMAIL PROTECTED]> writes: > Is it possible to patch the boot diskettes ? or is there a way to surround > (turn around, avoid ?) this problem ? I suggest following the directions very carefully at http://www.debian.org/releases/stable/i386/ch-boot-floppy-techinfo.en.html#s-rescue-replace-kernel> -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
serious problems with new debootstrap / busybox wget
I've been having some serious problems with my testing version of 3.0.0, using new deboostrap (0.1.13) and whatever the latest busybox is. Download from http.us.debian.org is hanging. I don't know if it's a network issue of if our use of 'wget -c -O ...' is causing it to tickle some sort of busybox bug. I'm going to research some more in a chroot environment with tcpdump, hopefully that will shed more light. In other news, the new debootstrap is failing with "mout -t proc proc /proc". Is it not doing this properly in the chrooted area? Again, needs more research. Just reporting it informally here for early warning. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install manual organization
"Chris Tillman" <[EMAIL PROTECTED]> writes:
> OK, perhaps you could copy me with the "Sysadmin Hints on Debian Linux", I
> wasn't around then.
Sure Attached.
> >> 9 Technical Information on the Debian Installer
> >
> > Thanks for working on this, Chris.
>
> I'm enjoying it, hope the output has value-added over the input.
Good, I'm sure it will be. Hopefully you're able to mostly just
use/reorganize existing content because rewriting is very very time
consuming and requires a lot of experience. Anyhow, I think it might
be wise to throw patches up here for comment prior to committing
them. Alternatively, I can make a CVS branch for your work and we can
merge that into mainstream when it's good enough...
--
.Adam Di [EMAIL PROTECTED]http://www.onshored.com/>
Title: Sysadmin Hints on Debian Linux
Getting Along with Debian Linux
(hints from Adam Harris
<[EMAIL PROTECTED]>)
If you're new to Debian, you might not know the following:
the pkg management system owns much of your hard drive. The
following directories should not be messed with manually unless you
really know what you are doing:
/usr (excluding /usr/local)
/var
(you could make /var/local and be safe in there)
/bin
/sbin
/lib
If you do mess around in there, you are liable to have whatever
you did be stomped by upgrading a package.
alternative versions of applications are managed by
update-alternatives, man page for which () still not
shipped as of 4 June 1998, unfortunately. Basically, say,
/usr/bin/vi -> /etc/alternatives/vi ->
{nvi, vim, whatever you like}. You can set your
preferred vi by modifying the symlinks in
/etc/alternatives/.
X configuration is a pain in the butt; but I suggest you use the
XF86Setup program (part of the xserver-vga
package). Sometimes that doesn't work, however.
Documentation to be found in /usr/doc. To submit bugs, look at
/usr/doc/debian/bug*. To read about Debian-specific
issues, look at /usr/doc//README.Debian.
The best installation method is apt. Get it from
/project/experimental/. Once you have
that, you can use it as a method from dselect; or you can use the
command line version. Look at apt-get(8). Note
apt also will let you merge, say, ftp1.debian.org
with ftp.de.debian.org in such a way as you have the
export-restricted packages (like pgp) as well as the std pkgs.
The debian way of building a kernel is also somewhat different.
Get the kernel-package pkg, get the kernel source tree
(either debian version or standard linux archive kernel will work),
install in /usr/src/linux (or symlink to that), and for any
non-std modules (i.e., pcmcia) get that source too (debian module
sources will install to /usr/src/modules). Then read
/usr/doc/kernel-packages/README.gz. This method will make
a .deb of your kernel source, and, if you have non-std
modules, make a synchronized dependant .deb of those too.
It's a better way to manage kernel images; /boot will hold
the kernel, the System.map, and a log of the active config
file for the build.
Ever said, "Damn, where the fsck is that cron job"? Ever
grepped thru /var/spool/cron/crontabs, had to
su to some wierd user, then do crontab -e? Even had
to look through all the cron jobs, thinking about whether they all
happen to fire at the same time or not?
Well, you don't have to anymore. Only personal cron jobs
should be in /var/spool/cron/crontabs on a debian server.
Any jobs under the purview of the system administrator should be in
/etc, since they are configuration files. If you have a root
cron job for daily, weekly, or nightly runs, put them in
/etc/cron.{daily,weekly,monthly}. These are invoked from
/etc/crontab, and will run in alphabetic order, which
serializes them.
On the other hand, if you have a cron job that (a) needs to run as a
special user, or (b) needs to run at a special time or frequency, you
can use either /etc/crontab, or, better yet,
/etc/cron.d/whatever. These particular files also have an
extra field that allows you to stipulate which the user under which
the cron job runs.
In either case, you just edit the files and cron will notice them
automatically. No need to run a special command.
For more information see cron(8), crontab(5), and
/usr/doc/cron/README.Debian.
Re: 2.3.6 uploaded
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > On Thu, Jun 21, 2001 at 02:44:37AM -0400, Adam Di Carlo wrote: > > > > Boot-floppies 2.3.6 for i386, powerpc, and source, has been uploaded. > How much time do we have before you upload 2.3.7? I have 2.3.5 ready for > m68k, but I can't get it through the phone line... How are you going to upload it at all if you can't get it through the phone line? I don't know when I'm going to release the next boot-floppies. The version number is going to be 3.0.0. I have to release it when it's ready. Its more important to have *some* version available for m68k than to have it be the latest. I doubt there will be all that many changes between 2.3.6 and 3.0.0, or, if there are, it will be a ways off. > One is the downloading of packages, it works for some, it doesn't work for > others, I suspect (without any proof yet) that it does work for others, only > the error message is wrong/misleading. This is from my lastest try on a > networked machine, boot-floppies-2.3.6 installed, no changes to the config > file. > > I: downloading kernel-image-2.2.19-atari > [...] > I: downloading required packages from files > /home/cts/boot-floppies/scripts/rootdisk/EXTRACT_LIST_all > /home/cts/boot-floppies/scripts/rootdisk/EXTRACT_LIST_m68k > E: Couldn't find package debootstrap > can't find package, or no such package, 'ash' > can't find package, or no such package, 'base-passwd' > can't find package, or no such package, 'busybox' > can't find package, or no such package, 'dhcp-client' > can't find package, or no such package, 'debootstrap' > can't find package, or no such package, 'e2fsprogs' > [...] > > So the kernel-image is downloaded fine, then when a bunch of packages is to > be downloaded, it fails. There is no deboostrap package in the archive for > m68k, maybe it chockes on that and (erroneously) "fails" on all the others > as well? I know that we have "ash" and many others in the archive. That's possible. You need to run the shell script with the 'verbose' environment variable turned on and examine the output. > Now that I built debootstrap and put it into /archive/debian/Incoming the > build does not fail at this place. Which I find is a pretty good proof of > the "misleading" error messages, maybe its even wrong. The error clearly is apt-get failing out, then the script is merrily running along and noticing that it cannot find any of the packages that were supposed to be downloaded. Sorta a "cascading" problem. Well, I'll look at fixing the error output... I don't really see how it's a big priority, though... If you look at the first error (from apt-get, I believe) then the cause is pretty clear You say "does not fail at this place" -- where does it fail, then? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new debootstrap in incoming
Matt Kraai <[EMAIL PROTECTED]> writes: > On Thu, Jun 21, 2001 at 11:01:34AM -0400, Adam Di Carlo wrote: > > Glad to see a new debootstrap with the fixes but the timing was just > > *awful*... > > > > /me considers build 2.3.7 right away... > > Are there 2.3.6 images available for testing anywhere? They're in unstable now... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel boot args (was Re: laoding drivers (floppy-boot))
Ethan Benson <[EMAIL PROTECTED]> writes: > so you finally got it booting via quik? what configuration did that > require? nope, not yet :) I am still booting with a miboot floppy hacked with resedit. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2.3.6 uploaded
Boot-floppies 2.3.6 for i386, powerpc, and source, has been uploaded. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.3.6 report
Anthony Towns <[EMAIL PROTECTED]> writes: > On Wed, Jun 20, 2001 at 05:07:04PM -0700, David Whedon wrote: > > All in all the errors are mostly cosmetic. I hope we move to quickly freeze > > base because boot-floppies are ready for it. > > That's not going to happen particularly quickly, because -testing *isn't* > ready for it, because they haven't had a chance to get into the swing > of things, because they haven't had boot-floppies they can try out and have > kind-of work. (2.3.5 came close, but we followed within a day or two by > groff and man-db breaking) I have to say, you're logic is rather backwards. Pretty much *every* reported problem about the installation I've seen as far back as 2.3.4 has nothing to do with boot-floppies themselves and everything to do with immaturity and instability in base and the testing distribution in general. For you to turn around and say that base isn't frozen because boot-floppies isn't ready just isn't true... We've been ready. YOu do have to expect that base change has to happen *prior* to a boot-floppies which accomodates it. And furthermore realize that there's about a 4-8 day lag on when the change occurs (for instance, new debootstrap) and when the new b-f that uses that is available. If Debian is willing to purchase for me fast machinery (i386 preferred) with fask disk and full exclusive root access, i could probably do the i386 builds myself much more quickly. Please please please --- lets get base frozen and stop pointing the finger at boot-floppies. Boot-floppies maturity has exceeded Potato already for 2 releases now. It's base and debootstrap which is still lacking maturity. And a frozen base will obviously make that maturity a little easier to achieve (less of a moving target). -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new debootstrap in incoming
Richard Hirst <[EMAIL PROTECTED]> writes: > Hi, I sent you this patch about a week ago, but it isn't in the > new source; did you not like it for some reason? I realise it wont > apply cleanly now, since you have woody.debs. Would you like me to > regenerate? I would guess you should regenerate and bump the severity of that bug to important, since it affects the releasability of an arch slated for woody. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PATCH: hppa support in boot-floppies
FYI, let me just comment that you guys (HPPA porters) seem really organized. I'm impressed. This is how things *should* be done, when a company is trying to get their hardware supported by Debian... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kernel boot args (was Re: laoding drivers (floppy-boot))
Ethan Benson <[EMAIL PROTECTED]> writes: > On Wed, Jun 13, 2001 at 10:16:07PM -0400, Adam Di Carlo wrote: > > > > Well, quik has certain boot args. I would assume yaboot would too. > > yes.. > > > Just has to be handled on a boot-loader by boot-loader basis, I guess. > > > > The option shouldn't appear if it doesn't work at all on the > > boot-loaders for a given arch, however. > > what i mean is we will have to write two different `Make System > Bootable' routines for every bootloader. or else modify the existing > ones to handle this. Yup. > yabootconfig for example will not allow you to supply additional > config information asside from bootstrap and root. however the way it > generates the config file we can simply append "\tappend=\"whatever\"" > or perhaps better would be "\tliteral=\"whatever\"" > > i think thats a tad bit gross though. Gross or not, my powerbook G3 is effectively unbootable with the vmode=atyfb... bootargs. So it kinda *has* to be done, IMHO. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#100996: boot-floppies regress. seriously
Isn't this bug a debootstrap bug? If so, can some reassign it? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: b-f build, with debootstrap-0.1.12
Richard Hirst <[EMAIL PROTECTED]> writes: > scripts/rootdisk/SMALL_BASE_LIST_all will need a new entry for woody.debs > for debootstrap-0.1.12. Havn't committed, because I don't know if all archs > have 0.1.12 in place yet. Assume yes. The only lagging arch is powerpc and I can take care of that one. Can you explain what is in this file? > It will also need an entry for sid.debs, once the bug I just submitted > against debootstrap gets actioned. > > I have some hppa changes that missed your 60 min deadline yesterday, > should I hold off now until 2.3.7, or is the deadline slipping? Deadline is slipping, had power outages last night. Will try again tonight :) -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dbootstrap_settings and proxy
Stephen R Marenka <[EMAIL PROTECTED]> writes: > Right now, dbootstrap only saves proxy settings to dbootstrap_settings > if a proxy is configured when downloading the rescue and drivers disks. > If you skip that proxy setup, but setup a proxy later for installing base, > we don't save that to dbootstrap_settings. Any reason why not, or shall > I go ahead and fix that? No good reason. > Or perhaps, would it just be better to call > write_userconfig in nf_server_select since that's where we get the proxy > info anyway? Whatever is the most robust and convenient way of fixing it technically, go for it. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
preparing 2.3.6
I'm preparing 2.3.6 now. I'm going to build that tonight if possible and if that passes some tests on i386 then release that. So please sync any changes for 2.3.6 over the next 60 minutes! -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: BF 2.3.6 install - 2 glitches
Filip Van Raemdonck <[EMAIL PROTECTED]> writes: > First, when I tried running the badblocks scan on the new created partitions, > I got the following error: > > badblocks: error while loading shared libraries: badblocks: undefined symbol: >ext2fs_sync_device > > Not really a problem (it wasn't a brand new drive, there had been windos on > it, and I checked (including surface scan) the drive before wiping) (question > is off course if I should trust scandisk ;-) Oouch. Which architecture are you on ? i386? This looks like a library reduction bug. Wierd and unusual, sicne I don't think we're reducing the ext2 libs. > Second issue, bigger problem: I needed the 3c509 module. Modconf suggested > setting io and irq parameters, so I did (had them ready anyway). This failed > with the error: "invalid parameter parm_io". > I tried a couple of variations (ioaddr, iobase, ...) but nothing worked. > I went to see in the kernel sources on another machine, and lo and behold > there was no io parameter for the 3c509 module indeed. (Granted, it was a > Z.4.5 source, but apparently 2.2 didn't have that parameter as well) > I suppose this could puzzle some other users as well, could this be fixed to > only suggesting to set irq and not io? (Probably this is a modconf bug?) Yes, file a bug on modconf, please. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic on CDROM install of potato
Nathan Crane <[EMAIL PROTECTED]> writes: > I have just recieved the following error message when installing > potato for the first time. I used the the line 'linux mem=128m' at > the boot prompt. My system is a K6-2 500 with 128m of RAM. Other > specifics cheerfully provided if it will help. This is a kernel issue. There are only a few courses open to you: - file a bug against the kernel-image you are using - surf the web and see if others have had this problem on your hardware, and found a workaround - use a different set of boot-floppies. For instance, if you were using the vanilla set (cd#1), try the idepci set. See the documentation. - try the woody version if you feel like testing whether it's fixed in a newer kernel (I think woody and Potato are pretty much using the same kernels now though) -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Patch not included in e2fsprogs 1.21.
Yann Dirson <[EMAIL PROTECTED]> writes: > As for the packaging of those libs and of the binaries that were > reduced, I'm not sure what would be best. IIRC most stuff included in > boot-floppies is taken right from real packages installed on the > machine where they are built. The e2fsprogs-bf I've built contains > stuff in e2fsprogs, so mush conflict with him to be installed, which > 1) is a pain for people building boot-floppies, No, its not a pain for us. We can build root to contain with one package, while a conflicting package is locally installed. It's no big deal for us. So I would recommend setting up conflicts/replaces as need, and letting the e2fsprogs-bf package be for root-building only. > 2) creates a package > that noone should ever installed except for building boot-floppies. Not even then :). It's a package that is just used when constructing the root disk. I dont' think that will cause problems with us. > Would it be OK to put them in some /usr/lib/boot-floppies so that they > won't interfere with what is installed ? That makes more work for us, but it's doable. I mean, don't do that as a favor to us, it's just going to make our life harder. > Or to put that in a tar.gz in the pool, where the boot-gloppies > built will know to find it ? Ew, please, no. > Or wouldn't it be best to have boot-floppies "apt-get source > e2fsprogs" and run "debian/rules build-bf" instead ? Ew, please, no. > It would require some tweeking so that the bf package does not get > built and uploaded into the dist, but it may be worth it. I don't really see the problem with having an e2fsprogs-bf package, just for root.bin, which no one should ever normally install... This can be used in debian-installer too, as David points out. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: base*.tgz is gone, and why it's gone
Jason Gunthorpe <[EMAIL PROTECTED]> writes: > I am sitting at an intel machine. Right now, I have debootstrap installed, > I can make chroots and nfsroots for i386 boxes. Yay. > > Tell me the exact command to make a chroot for an ARM from my i386. 'reportbug debootstrap' -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies 2.3.5 ready for testing (i386 and powerpc so far)
Josip Rodin <[EMAIL PROTECTED]> writes: > On Tue, Jun 12, 2001 at 10:00:17PM -0400, Adam Di Carlo wrote: > > > > we aren't even responsible for base (debootstrap is). Problems with > > > > base should be filed against debootstrap; > > > > > > Should the maintainer for the "base" pseudo-package be chaned to > > > [EMAIL PROTECTED] now? > > > > Yes, indeedy... how do we get that changed? Or are you volunteering > > to do that? > > I can't do it, but an FTP admin can -- I suggest you file a bug on > ftp.debian.org pseudo-package asking for this change to be done. Bug filed. Thanks. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: base*.tgz is gone, and why it's gone
Jason Gunthorpe <[EMAIL PROTECTED]> writes: > Debian's base*.tar is the *only* solution I know of for this that supports > the variety of platforms I am interested in, I know other people do the > same thing. This would be a very unfortunate loss to the people doing > embedded work with linux. You just need some education on what's available. You can use debootstrap to create a chroot or nfsrootable area. Go back, play with debootstrap, then formulate what it's lacking. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot disks 2.3.5
Stephen R Marenka <[EMAIL PROTECTED]> writes: > On Fri, Jun 15, 2001 at 03:27:31PM -0700, Duane Powers wrote: > > Stephen R Marenka wrote: > > > This applies to me precisely. Most of you probably saw my post earlier > > this morning, and after beating of the stupid out of myself, > > I compiled a kernel properly, and managed to get into the install > > process. However, when I try to load the operating system, I'm running > > into trouble that isn't covered at all in the above url. Questions I > > have would include, do I need to modify the root.bin disk? if so, how? > > why? how about the driver disks? Do I need to do anything other than > > modules.tgz? Do I have to install via driver disks? I can't get that > > far, I am getting an error when I try to remount the rescue disk,at the > > "install operating system kernel and modules" step, telling me Unable to > > mount the Rescue Floppy. You may have inserted the wrong floppy. Please > > try again" which I can't find any information on, at least, not yet. I > > tried donwloading, from the net, but I get a wrong rescue disk error > > there as well, so now I'm lost. I would guess that you don't have FAT support in the hand-made kernel. Thus it can't mount the rescue disk. Yes, that is documented... > I agree that the documentation isn't really suitable for newbies. On the > occassion I had to do this, I didn't need to modify the root.bin. I also > just grabbed the rescue and modules disks off the net to get through the > installation. I believe I ended up manually mounting my custom rescue > disk and copying the appropriate stuff into /boot. I also set the > /vmlinuz link manually and renamed the /lib/modules/xxx directory. The > renaming is because I was using the compact disk set which had > "flavored" kernels and my kernel was plain. Ah, yes, good point. If you modify the kernel and such, you should probably base it from the vanilla set rather than one fo the flavors. That definately should be documented. > That's not very easy. What I probably need to do is go through the whole > process again, document it, and fix the documentation. Very good idea. > Or better yet, maybe someone else will come along and clean it up > for us. :-) Not a good idea to count on that. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: base*.tgz is gone, and why it's gone
Ben Collins <[EMAIL PROTECTED]> writes: > On Fri, Jun 15, 2001 at 05:09:33PM -0600, Jason Gunthorpe wrote: > > The base tarball is *very* useful for NFS root booting other > > architectures which I do alot, particularly when the NFS serving box is > > not a debian box. It is very nice to be able to say 'fetch this tar, > > unpack it, setup NFS and boot this kernel'. > > > > I'm not sure how you can automate that process without haxoring the .debs > > since they can't really have their post insts run. It would be nice if > > there is possible solution, particularly if said solution could run on > > non-Debian unix's.. > > Maybe debootstrap could be hacked to support this? I'm not sure how you > would create a fully installed system in a chroot on a different arch > though. Honestly, the best approach here is to hack debootstrap, say, with a special arg, so that instead of building base, it constructs enough of a local mirror so that you could install base. Of course, the packages in base are going to vary from arch to arch, and most of the packages are arch-dependant Anyhow, assuming you had a subset of a debian archive, enough to get base, and you can get that via http, nfs, or ftp, if you had that, why is that less convenient to install from the actual packages rather than from a big fat tarball? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
base*.tgz is gone, and why it's gone
Dale Scheetz <[EMAIL PROTECTED]> writes: > I've been downloading these files for a test session, and I can't find the > base tarball. Where can I find this file? It is normally in the images > directories, but I can't find it. There is no base tarball anymore. The functionality has been superceeded by debootstrap (the package). FYI, what debootstrap does is simply download (or get from CD) the packages in base at runtime. Essentially, it replaces the bootdisks.sh script in boot-floppies -- we used to build the base system at boot-floppies build time. Why is this better? For one, it's going to be able to work with debian-installer, for sid release, since boot-floppies is going away in sid. For two, its better because we don't have to create another boot-floppies release to capture updates in base. We're able to turn around base fixes as easily as updating the packages in the archive. For three, it's better because it means less for the overworked debian-boot team to be directly responsible for. :) Some have asked for some way to install base via floppies -- you'll have to take it up with AJ. CVS for the debootstrap package is available in the same cvsroot as boot-floppies. I'm happy to try to accomodate this on the boot-floppies side if the support is added to debootstrap and some split images provided. However, AJ might not be willing to do this at all, since it will invalidate (for floppy install anyhow) many of the benefits above. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: E2fsprogs 1.20 released
Yann Dirson <[EMAIL PROTECTED]> writes: > On Thu, Jun 14, 2001 at 03:49:30AM -0400, Theodore Tso wrote: > > The e2fsprogs 1.21-WIP-0614 release which I just uploaded has some new > > configure options; if you compile it: > > > configure --enable-elf-shlibs --disable-swapfs --disable-imager --disable-resizer >--disable-debugfs '--with-ccopts=-O2 -fomit-frame-pointer' > > Gasp, I had not realized that, the 1st 1.21-WIP-0614 package doesn't > make use of this. > > > Would this be workable for you? > > I can have the pics libs and an e2fsck.bf binary built reduced, and > shipped in the e2fslibs-pic package with not much work. Yann, thanks for doing this. You too, Theodore. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#100749: cdrom entry in /etc/fstab points to non-existant /dev/cdrom
Matt Kraai <[EMAIL PROTECTED]> writes: > On Thu, Jun 14, 2001 at 03:33:44PM -0400, Adam Di Carlo wrote: > > No, I think we're doing the right thing. If the user doesn't install > > from CD-ROM, we don't make the link. If the user is installing from > > CD-ROM and there are more than one, we have them pick, and set > > /dev/cdrom accordingly. > > > > This bug should be closed, IMHO. It's invalid. > > I agree that the boot-floppies should install, not configure, the > system. As such, I don't think it is their place to setup > /dev/cdrom unless it is used during the install. But we shouldn't > force users to learn about unix devices and symlinks before they > can play music. Therefore, I think this should be reassigned to > base-config, and Joey can decide if it belongs there or somewhere > else (such as makedev). Agreed. Can you do that and drop it to wishlist while you're at it? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#100749: cdrom entry in /etc/fstab points to non-existant /dev/cdrom
No, I think we're doing the right thing. If the user doesn't install from CD-ROM, we don't make the link. If the user is installing from CD-ROM and there are more than one, we have them pick, and set /dev/cdrom accordingly. This bug should be closed, IMHO. It's invalid. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install manual organization
"Chris Tillman" <[EMAIL PROTECTED]> writes: > > 3 Before Installing Debian GNU/Linux > > > > 3.1 Backups > > 3.2 Information You Will Need > > (was 4.2) Planning Use of the System > > 3.3 Pre-installation Hardware and Operating System Setup > > (was 5.1) Overview of the Installation Process > > add here: Pre-Partitioning to Support Dual Booting >-- create placeholder partition for Linux which will be deleted later Yes... It would be great if we had more info for people who are installing debian but wanna retain their existing OS. I admit the boot-loader configuration stuff isn't likely to solve that (well, if we use grub on i386, that might be possible). Interestingly, the process for all arches is similar: - do your partitioning in the non-linux OS, leaving a place hold or room for Debian - do the install, changing that placeholder or free space to a linux partition, etc. - do NOT make hard disk bootable, but use other means of booting instead (rescue floppy with the 'rescue' option, the miboot floppy on powermac, booting from cd w/ rescue, whatever...) - after installation is complete, user must manually configure boot-loader for dual-booting. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap and dselect tutorial
Ok, it's there now, needs testing. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Root disk problems for i18n floppies
David Whedon <[EMAIL PROTECTED]> writes: > Too bad, but there isn't a good way around it. Has any thought gone into making > root.fr.bin, that is, a bunch of different root disks, or am I going crazy? In > principle they would be easy to make, unfortunately it would increase the size > of b-f binary uploads greatly. Yes, this is doable today. It's just too large to make part of the mainstream build process. This is what people are doing now I think. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem building b-f, need help
David Whedon <[EMAIL PROTECTED]> writes: > > Anyway the problem is still there, it fails to find the packages I've > > already downloaded. I've tried putting them in /archive/debian/local, > > /archive/debian/Incoming, and /archive/debian/download/cache/archives. > > Any ideas? In config, set offline_mode := true You should be able to put files in either the 'incoming' dir (if they have the _.deb suffix) or the local_dir dir, as configured in 'config'. We still cannot debug your problem, because you need to provide debug=true output especially for the 'make_paths" function in common.sh failing. You're contention that it's looking for pkg-foo rather than pkg_foo is simply wrong, see common.sh lines 94 and 104. > I've been putting packages in boot-floppies/updates/ nad it find them, beware, > the clean target deletes boot-floppies/updates/ Yes, that's the wrong thing to do. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#100749: cdrom entry in /etc/fstab points to non-existant /dev/cdrom
Thue <[EMAIL PROTECTED]> writes: > Package: boot-floppies > Version: N/A; reported 2001-06-13 > Severity: important > Tags: potato > > (hoping this is the correct package) Yup. > Title says it all actually. > The problem is somewhat easily located and fixed by hand, > but I really think the cdrom should work "out of the box", > hence the bug severity... Yah, well, since it can be worked around, I wonder if 'Important' is perhaps too high... But, yes, it is supposed to work... > I have installed potato on 2 computers, and in both instances > I had the problem. We'll take a look. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: laoding drivers (floppy-boot)
Ethan Benson <[EMAIL PROTECTED]> writes: > On Wed, Jun 13, 2001 at 02:44:29PM -0400, Adam Di Carlo wrote: > > > 'Edit Kernel Boot ...' will still come up as alternate to 'Configure the > > > Hostname' and 'Configure the Network' sometimes. > > > > "Edit Kernel Boot..." should be an alternative tot he "Make system > > bootable", IMHO. > > hrm, how will that become archetecture friendly? Well, quik has certain boot args. I would assume yaboot would too. Just has to be handled on a boot-loader by boot-loader basis, I guess. The option shouldn't appear if it doesn't work at all on the boot-loaders for a given arch, however. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap and dselect tutorial
David Whedon <[EMAIL PROTECTED]> writes: > Here's the play by play. > > You asked me if I could help with something here: > http://lists.debian.org/debian-boot-0106/msg00176.html > > I think a decision started to be made here: > http://lists.debian.org/debian-boot-0106/msg00164.html > > And then it looked like you were happy to do what needed to be done: > http://lists.debian.org/debian-boot-0106/msg00308.html Oh, yah, I still am. I just forgot what exactly it was. :) > Whatever, I'm now going though the list to find something to do this > evening, so feel free to re-delegate :-) Well, I was just reading over installer.log and frankly it should be a lot better. You should be able to read the log and determine that the user installed kernels and drivers from cd, installed base from the network, etc etc. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: successful installation with 2.3.5 boot-floppies
Erik Andersen <[EMAIL PROTECTED]> writes:
> On Tue Jun 12, 2001 at 08:37:21PM -0400, Adam Di Carlo wrote:
> >
> > > they're allowed to have special instructions that you have to carry out
> > > very precisely ("Switch to VC 2, type this confusing sed command... Before
> > > rebooting, switch to VC 2, and chmod these directories like so..."),
> > > all they have to do is be usable to install a functional woody system.
> >
> > Yah -- the bad bug still outstanding is the busybox tar problem, which
> > is causing a *VERY* insecure system to be produced.
>
> This is not an outstanding bug. It was fixed in busybox 1:0.51-7 which
> was uploaded on June 4th. busybox 1:0.51-8 was installed into the archive
> yesterday...
Yes, confirmed fixed.
--
.Adam Di [EMAIL PROTECTED]http://www.onshored.com/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [OT] extracting boot image from 'el torito' image
Brent Verner <[EMAIL PROTECTED]> writes: > On 13 Jun 2001 at 01:01 (-0400), Adam Di Carlo wrote: > | Brent Verner <[EMAIL PROTECTED]> writes: > | > | > Hi, > | > Sorry for the noise, but I figured this is the best list for the > | > question. > | > > | > How can I extract the boot image from a bootable ISO image? > | > > | > I've tried > | > dd if=iso.raw of=boot.img bs=2 skip=21 count=720 > | > but it doesn't give me the bootable floppy image. > | > | The disk itself is the bootable image. > > well, yes, the cdrom does contain a bootable (1.44 or 2.88) image. > I would like to see that image. I believe there is no convenient > way to do this with current tools. Sure -- find the rescue.bin file and do : dd of=/dev/fd0 if=rescue.bin bs=1024 > | There are other images provided (boot/root) if you want 1.44MB > | versions suitable for standard floppy. > > are those the /same/ as the one written to the bootable ISO images? The CD-ROM's bootability is based on the fact that it's setup to use the 2.88k sized floppy (should be there under images-2.88 somewhere) as an EL TORITO bootable image. It uses different "flavors" on different CDs, see the fine manual. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: laoding drivers (floppy-boot)
David Whedon <[EMAIL PROTECTED]> writes: > > This is very confusing... We shoudl remove this question entirely and > > replace it with an alternative selection the user could run *before* > > running "configure drivers", just like "configure pcmcia" is an > > alternative there > > > > can do, looks like we'll have 3 alternates on some archs > Next: Configure Device Driver Modules > Alternate: Configure PCMCIA Support > Alternate1: Edit Kernel Boot Parameters > Alternate2: Install Foreign Modules from Floppy > > Is that cool? why not replace 'Edit Kernel ...' with 'Install Foreign .. ' ? Yes, replace. > 'Edit Kernel Boot ...' will still come up as alternate to 'Configure the > Hostname' and 'Configure the Network' sometimes. "Edit Kernel Boot..." should be an alternative tot he "Make system bootable", IMHO. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies 2.2.25 with i386 2.2.19 upgrade
Richard Hirst <[EMAIL PROTECTED]> writes: > On Wed, Jun 13, 2001 at 12:59:22PM -0400, Adam Di Carlo wrote: > > > > It's a Symbos 53C1010, which appears to be more or less compatible with the > > > > 53C8xx chips used in the earlier tekram cards. At least, there're references > > > > to them in the 2.4 series kernels' 53c8xx driver sources, so I assume they > > > > work, but there's no mention of them in my copy of the 2.2.13 sources I have > > > > here, so you may require a 2.4 kernel to use this card. You should check > > > > the 2.2.19 sources. > > > > > OK, is there anyone building or has a set of 2.4 kernel disks? > > > > I'm confused. The potato boot floppies includes CONFIG_SCSI_SYM53C8XX > > in both the vanilla set and the compact set. > > There are quite a few specific references to 53c1010 in the 2.4.x > sym53c8xx.c driver; I don't know whether those changes are in 2.2.19. Well, I don't see the point in telling the user it doesn't work in 2.2.19 unless you can say that for sure... In essence, it's a hardware/kernel issue, and needs to be addressed at that level. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies 2.2.25 with i386 2.2.19 upgrade
Brian Schramm <[EMAIL PROTECTED]> writes: > On Mon, 14 May 2001 [EMAIL PROTECTED] wrote: > > > > LSI Logic Symbios pci scsi bios. > > > > > > I think that is what you are looking for. > > > > Not really, no. I wanted a chip number. > > > > www.tekram.com, flip, flip, flip. > > > > It's a Symbos 53C1010, which appears to be more or less compatible with the > > 53C8xx chips used in the earlier tekram cards. At least, there're references > > to them in the 2.4 series kernels' 53c8xx driver sources, so I assume they > > work, but there's no mention of them in my copy of the 2.2.13 sources I have > > here, so you may require a 2.4 kernel to use this card. You should check > > the 2.2.19 sources. > OK, is there anyone building or has a set of 2.4 kernel disks? I'm confused. The potato boot floppies includes CONFIG_SCSI_SYM53C8XX in both the vanilla set and the compact set. You have to identify what config option is required by your card, then grep in the 'kernel-config' files in the b-f area, e.g., http://http.us.debian.org/debian/dists/potato/main/disks-i386/current/> There's not really much else I can do for the user. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#96906: Debian installer 96906 is a real bug after all
Dan Shearer <[EMAIL PROTECTED]> writes: > lilo_1%3a21.7.1-4_i386.deb exists as it should in /var/cache/apt/archives > after the base system install. The file appears to be valid (I unpacked it > with ar, tar and gzip.) > > I am pretty sure the problem is simply that lilo isn't being installed. > > Let me know if there is any other info I can give you to help solve this > annoying problem. It is probably fixed in newer debootstrap. Can you retest with 2.3.5 ? If you still get it, then file a new bug under debootstrap. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: install manual todo
"Chris Tillman" <[EMAIL PROTECTED]> writes: > I'm up for getting started ... sounds like a good plan to me. Any inputs are > welcome! I'd be happy to review work that you've done, of course... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#99926: Rescue boot disk error
severity 99926 important thanks Greg Leppert <[EMAIL PROTECTED]> writes: > I did try a new floppy, several times. What I found out eventually was > that rawrite2.exe was writing bad blocks onto my floppies, and all the > data wasnt written. It also destroyed the floppy sector, making the disk > unusable for the images. I switched to the older version of rawrite, and > it worked great. Sorry about the hasty message, but I wrote it over my > 2.2r2 rescue disk, and assumed it was in good shape. Assume got me again. > Thanks for your help. Oy, ok, well, we gotta fix or find an alternative for rawrite2 I guess. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap and dselect tutorial
David Whedon <[EMAIL PROTECTED]> writes: > > [...] > > > > Lets wait until I burn 2.3.5 first. > > > > I'm sure I can add the package building stuff into debian/rules in a > > pretty damn short order. > Sounds like a good plan to me. Too aggressively snipped, David. Can you remind me what I was promising here? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem building b-f, need help
Ron Farrer <[EMAIL PROTECTED]> writes: > Christian T. Steigies ([EMAIL PROTECTED]) wrote: > > > turn on debug in common.sh? > > Interesting... it seems to be looking for "packagename-" instead of > "packagename_" Neither myself nor grep could find which script does > this.. Short of renaming all the files to "packagename-" is there > anything I can do? That's not even close to being correct. The download stuff works fine for me and lots of people on this list. Again, run it with debug settings and look for the apt-get command line. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: m68k boot-floppies for woody
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > If we could change the bf-archive install script a little, the amount of > files uploaded could be significantly reduced without loosing anything. > Currently we build [amiga|atari|mac|*vme*]install.tar.gz files so that > potential users have to download only one archive (and in earlier times the > base). However the contents of all these files is duplicated in > bf-base.tar.gz, which is an awful waste of space, and bandwidth when > uploading via a 33k6 link. Can we change the install script to unpack the > *inatt.tar.gz files and drop bf-root completely (unless there is something > in bf-root which is not in any of the other files of course)? Sure, go nuts. Just don't break any other arches... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [OT] extracting boot image from 'el torito' image
Brent Verner <[EMAIL PROTECTED]> writes: > Hi, > Sorry for the noise, but I figured this is the best list for the > question. > > How can I extract the boot image from a bootable ISO image? > > I've tried > dd if=iso.raw of=boot.img bs=2 skip=21 count=720 > but it doesn't give me the bootable floppy image. The disk itself is the bootable image. There are other images provided (boot/root) if you want 1.44MB versions suitable for standard floppy. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
install manual todo
FYI, my rough thoughts on the install manual todo: - we should merge chapters ch-inst-methods and ch-rescue-boot; don't focus on describing everything, but rather traverse it by the installation method. Basically, merge ch-inst-methods into ch-rescue-boot. - Description of Installation System Files should be moved to an appendix at the back - partitioning chapter should be questioned I guess.. shouldn't it occur as a section in the partition step of dbootstrap ? - dbootstrap stuff needs to be fully reviewed so it's up-to-date with Woody Is anyone able to take care of this? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: PATCH: hppa support in boot-floppies
Richard Hirst <[EMAIL PROTECTED]> writes: > This patch adds to the partial hppa support already in b-f. The > documentation certainly needs more work, but I do produce working > images with these patches. Very nice. I have applied these. You didn't include a debian/changelog entry so I made one for this. For this very clean patch, you deserve the dubious honor of debian-boot CVS write perms. Use my PGP key from the debian keyring to send me a username and password and I can set you up with an account if you want one. Is hppa releasing with Woody? Do you need an upload of 2.3.6 which contains these changes so you guys can upload hppa boot-floppies? Is there any official developers building this (who can upload)? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: critical problems in 2.3.5 prevent release
Ethan Benson <[EMAIL PROTECTED]> writes: > this is really not much to ask of the base system. at > the moment there is only two packages im aware of that violate these > conditions: > > powerpc-utils > quik Quik at least is fixed in incoming. I had to re-upload the .4 NMU just now due to a capitalization issue... > > Is there a way to test to see if the nvramrc patches have been applied? > > We could at least prompt the users then. > > not really, because some oldworlds always have an nvramrc. apple > apparently found some bugs in thier firmware, and rather then just fix > them they wrote nvramrc patches and burned them into the ROM. FYI, is there a URL for such patches? Even if it requires MacOS to run? /me is still wishing his wallstreet powerbook was quik bootable and wants to avoid installing MacOS to run BootX -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies 2.3.5 ready for testing (i386 and powerpc so far)
Josip Rodin <[EMAIL PROTECTED]> writes: > On Tue, Jun 12, 2001 at 12:16:49PM -0400, Adam Di Carlo wrote: > > we aren't even responsible for base (debootstrap is). Problems with base > > should be filed against debootstrap; > > Should the maintainer for the "base" pseudo-package be chaned to > [EMAIL PROTECTED] now? Yes, indeedy... how do we get that changed? Or are you volunteering to do that? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: laoding drivers (floppy-boot)
Michael Bramer <[EMAIL PROTECTED]> writes: > On Mon, Jun 11, 2001 at 03:40:22PM +0200, Juerg Oehler wrote: > > with these floppies i booted and loaded the rescue successfully into > > RAM. when i got to the menu for loading additional drivers the system > ^^ > This are for _additional_ driver. You can use a own driver-disk with > this. If you don't have one, skip this point (this is the default). Yes. This is very confusing... We shoudl remove this question entirely and replace it with an alternative selection the user could run *before* running "configure drivers", just like "configure pcmcia" is an alternative there -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bootp network configuration
Ethan Benson <[EMAIL PROTECTED]> writes: > I have seen a couple people mention that dhcp network configuration > worked for them with cvs boot-floppies. > > when i tested it failed, and now the only reason i can think of as to > why is that i have a bootp server, not a dhcp server. (only reason i > have it is to netboot this powermac which wants bootp). [...] > the man page for dhcp-client implys that it supports bootp, so whats > wrong? No idea. Do you have the same problem after installation? Might be a dhcp-client bug or interop problem... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installer online help
"Chris Tillman" <[EMAIL PROTECTED]> writes: > In my case I did end up finding a quick reference sheet on the web after my > first few weeks of trying to get Debian installed. But it didn't include > many of the commands that are available, and was bash-oriented, so it really > wasn't much help. That's a good point, but you should contribute to debian-doc about such things. You have to remember that boot-floppies is end of life. I don't wanna sink a lot of time and waste space on command-line help. I don't think it's worth it. I don't think I'm being dismissive of i18n either, because I also fear the bloat of root.bin, which i18n needs every byte... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installer online help
"Chris Tillman" <[EMAIL PROTECTED]> writes: > New users feel completely lost; even if the information is right there, they > don't know how to get at it. No, new users shouldn't have to use tty2 at all. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
verdict on Installer online help
I agree with Erik. Chris' documentation is good, but should be part of the documentation, not actually something on the root disk. /me has spoken. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
trimming fat in busybox (was Re: Installer online help)
Erik Andersen <[EMAIL PROTECTED]> writes: > Oh, thats right. > I wonder if I should trim out some of the fat in the .deb then. > For example, the .deb contains the busybox shell (lash), which > is not being used... I expect a bit of hunting could find a > fw others. Fat trimming sounds worthwhile to me... I'd hate to make the .deb less useful generally -- but I would love the space savings... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Root disk problems for i18n floppies
Marcin Owsiany <[EMAIL PROTECTED]> writes: > So what shall we do? Only support it for the 2.88 ones? If we have to... > Othewise we need to find a way to cut some 200 KB (100 + 40 for > chinese messages + who knows how much for locale definition). Oy. The size of the locale part needs to be established ASAP. Possibly hack it to get the messages file via http if possible (wget), or use english if not. That would be *something* anyway. Another possibility, which I like even worse, is to just supply the major euro lanugages, say: English French German Italian Spanish Then allow downloading of other messages catalogs... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Root disk problems for i18n floppies
David Whedon <[EMAIL PROTECTED]> writes: > One option is to make an optional i18n floppy and have a menu option: 'Load > Multiple Languages'. Then we mount the dist that contains the additional > messages and whatever else we need then install into the right locations. I > don't know much about gettext or whatever. In principle this sounds possible > but there may be issues I am unaware of. Or get it over the network... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: successful installation with 2.3.5 boot-floppies
Anthony Towns <[EMAIL PROTECTED]> writes:
> On Fri, Jun 08, 2001 at 12:04:49PM -0600, Matt Kraai wrote:
> I was under the impression the boot-floppy disks were being based on
> packages in sid (busybox, debootstrap, etc) and used to install packages
> from woody (dpkg.deb, bash.deb, libc6.deb, etc). This still seems the
> sensible thing to do, to me, but stuff I read seems to indicate the
> opposite is happening?
No, if you're reading that, who-ever wrote it is wrong.
What we do is build using sid packages, as you say, until base
freezes, and we let the testers choose which distro (stable, testing,
unstable) they want to install.
With regards to telling the testers what to do, I feel that's the
responsibility of the testing coordinator (is Dale Scheetz the
coordinator?).
If there is no testing coordinator, then that is going to be a problem
that someone shoudl do something about.
> The main goal for boot-floppies at the moment, btw, is much simpler
> than what you appear to be thinking: what we need right now are some
> boot-floppies in the archive accompanied by a list of do's, don't's and
> workarounds that can be used by competent testers to do woody
> installs.
AFAIK, unless I hear otherwise from testers, we are at that point the
second that 2.3.5 is moved from incoming into woody (or sid I guess).
> These only need to be available for i386,
They are there for i386 and powerpc at least. BenC said he'd build
sparc shortly. m68k might have to wait for 2.3.6, they seem to have a
build problem.
> they're allowed to only work for
> one method ("You can't use these floppies for CD installs, nor for
> DHCP"),
Not many such limitations but I don't have any woody CDs yet to test
with.
> they're allowed to have special instructions that you have to carry out
> very precisely ("Switch to VC 2, type this confusing sed command... Before
> rebooting, switch to VC 2, and chmod these directories like so..."),
> all they have to do is be usable to install a functional woody system.
Yah -- the bad bug still outstanding is the busybox tar problem, which
is causing a *VERY* insecure system to be produced.
> It'd be nice to start having "released" beta boot-floppies, asap. Even
> without multiple architecture support, and whatever else.
We've had "released" versions since Sun, 8 Apr 2001 03:59:31 -0400.
They just weren't working very well.
Anthony, I sense some impatience and/or hostility here. What is it
we can do to make you more happy?
I'm trying to release the code more quickly -- 6 uploads since early
april. We are averaging about 10 days between releases Do you
have some expectations beyond taht which are not being met?
I could always use more qualified hackers of course
Personally I would put a little concern in about the coordination of
the testing effort. Is that in place? I have no idea, maybe...
--
.Adam Di [EMAIL PROTECTED]http://www.onshored.com/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg and DEBIAN_FRONTEND
Stephen R Marenka <[EMAIL PROTECTED]> writes: > Wouldn't it be valuable for dpkg to check for DEBIAN_FRONTEND and if > it's Noninteractive then take defaults instead of prompting? It seems that > many install scripts aren't built for noninteractivity. I would suspect > if you ever wanted to build multiple machines from the same base (ala > kickstart), this would be all but a requirement. Personally I think all packages in base, at least, should require use of debconf for any interactive bits. This is a battle that should be taken up on debian-policy. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: should ext2 be formated to support 2.0 kernels?
I've changed the ext2 / kernel versioning stuff. Question is not a double negative anymore. Default on non-arm is 2.2 support; Default on arm is 2.0 support I am considering changing this so that it doesn't even prompt, but just goes with the defaults, unless 'verbose' is on. Thoughts? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2.2.26 (potato) tagged and building
Boot-floppies 2.2.26 update is tagged and buiding for i386 now. It had some PowerPC updates, but the main reason for this release is to get the kernel 2.2.19 4potato.2. Here are the packages I am building with from potato-proposed-updates: -rw-r--r--1 apharris staff 185934 Jun 7 01:28 e2fsprogs_1.18-3.0potato1_i386.deb -rw-r--r--1 apharris staff 1880484 Jun 8 23:35 kernel-image-2.2.19-compact_2.2.19-4potato.2_i386.deb -rw-r--r--1 apharris staff 5813322 Jun 8 23:25 kernel-image-2.2.19-ide_2.2.19-4potato.2_i386.deb -rw-r--r--1 apharris staff 1245854 Jun 8 23:16 kernel-image-2.2.19-idepci_2.2.19-4potato.2_i386.deb -rw-r--r--1 apharris staff 5661830 Jun 8 23:31 kernel-image-2.2.19_2.2.19-4potato.2_i386.deb -rw-r--r--1 apharris staff 2169530 Jun 12 08:18 libc6-dev_2.1.3-19_i386.deb -rw-r--r--1 apharris staff 670888 Jun 12 08:17 libc6-pic_2.1.3-19_i386.deb -rw-r--r--1 apharris staff 1900782 Jun 12 08:26 libc6_2.1.3-19_i386.deb -rw-r--r--1 apharris staff 2284222 Jun 12 08:20 locales_2.1.3-19_i386.deb -rw-r--r--1 apharris staff 326494 Jun 7 01:20 pcmcia-modules-2.2.19-compact_3.1.22-0.2potatok4potato.1_i386.deb -rw-r--r--1 apharris staff 344408 Jun 7 01:23 pcmcia-modules-2.2.19-ide_3.1.22-0.2potatok4potato.1_i386.deb -rw-r--r--1 apharris staff 246122 Jun 7 01:25 pcmcia-modules-2.2.19-idepci_3.1.22-0.2potatok4potato.1_i386.deb -rw-r--r--1 apharris staff 344414 Jun 7 01:19 pcmcia-modules-2.2.19_3.1.22-0.2potatok4potato.1_i386.deb -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: E2fsprogs 1.20 released
Yann Dirson <[EMAIL PROTECTED]> writes: > [CCing the boot-floppies team] > > On Thu, Jun 07, 2001 at 08:49:54AM -0400, Theodore Tso wrote: > > As long as they don't care about needing debugfs, they can probably > > save 12k, maybe as much as 15k. How desperate for space are they? 12-15k is nothing to sneeze at. We really do need the space, esp with i18n issues possibly coming in. > > Is the boot floppy also supposed to double as a rescue floppy? If so, > > removing debugfs might not be such a hot idea. > > IIRC it's the case. Um, well, not really. You *can* use the boot/root floppies as a rescue system, but it kinda sucks for that, and I always recommend people use the better, specialized uni-floppy linux distributions. > > > The other way of doing this if they're really desparate for space > > would be to make a new configure option, --enable-small-subset which > > built a version of e2fsprogs that had been cut down for use on > > installation floppies. This allows further cuts, such as not > > supporting byte-swapping filesystems (needed to convert very old > > Linux-PPC filesystems to the standard ext2 byte order; doing this > > would save approximately 3k from e2fsck and libext2fs). This would > > also not build debugfs and resize2fs, and automatically contain the > > right list of functions that could be removed from libext2fs (as well > > as using #ifdef to remove functions with .o files that can't be used). > > I could remove all use of inline functions from e2fsck, which will slow > > it down some, but make it quite a bit smaller. > > > > So if they're truly desparate for space, it may be possible to save a > > some more by making much more invasive changes to e2fsprogs. Well, Ted, I hardly want to do anything to make the source itself harder to maintain, to change, to release, or to understand. Those issues override our needs, IMHO. We do have space desperation, sure, insofar as we're trying to fit internationalized message catalogs on the damn disk not to mention the locales messages catalogs. That last one is the "low-hanging watermelon" we need to put our energy into, IMHO. I just figured the pic libraries would be a pretty easy way to save 10-20k. > > If they're in a big hurry, I'd advise doing this as a new debian > > package with a diff file that modified lib/ext2fs/Makefile.in to > > remove certain files, removed debugfs and resize2fs from the list of > > directories to be built, etc. See mumblings above about not wanting to add a maintenance burden... > Probably it can be handled in one source package, using a modified > version of DBS (the thing used to build X and such). I was looking > for an excuse to make a jam-based version of DBS, cool :) > > > If they're going to be code slipping for another six months anyway > > :-), I can look into making the mods into e2fsprogs in a "clean" way, > > i.e., using configure options to control how it's built. > > investigating... plans for base system appear to be: > > - fix release-critical bugs before July 1st > - hard freeze July 20th It's probably too tight to attempt this ... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: When to install?
Yah. Right now I would consider Woody installation system as alpha. If you're studly, you can try testing with 2.3.5 when that comes in. If you more are interested in the final user experience, wait for like 3 or 4 weeks, or until we freeze the base distribution. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
boot-floppies 2.3.5 ready for testing (i386 and powerpc so far)
Boot-floppies 2.3.5 has been released and qualifies for what I would call "alpha" status, although I can't say for sure that we won't be adding any features here and there as needed, so it's kinda a "squishy alpha". I have 2.3.5 builds for i386 and PowerPC (from Incoming) expanded for tester convenience at http://people.debian.org/~aph/debian/dists/woody/main/ These should be in the archive shortly as soon as the archive manager does that. I would like to open the door wide for testing. I apologize for the state of the boot-floppies bug tracking area -- it's a mess. We will try to clean that up. However, even so, please don't hesitate to file bugs. Alternatively, just take rough notes during installation and send those to <[EMAIL PROTECTED]>. You will be prompted for whether you wanna install stable, testing, or unstable. For i386, I suggest using testing; for powerpc, I suggest unstable (for the new yaboot). Of course, this situation will change over time and is not controlled by the debian-boot group. As experienced testers know, boot-floppies are prone to exposing plenty of bugs in other packages, particularly now that we aren't even responsible for base (debootstrap is). Problems with base should be filed against debootstrap; problems with kernels should be filed against the kernel-image packages; problems with tasksel filed against tasksel, same with base-config, yaboot, quik, etc. The debian-boot list only works on the boot-floppies. Changelog for 2.3.5 attached below. Thanks for helping get Woody released. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> boot-floppies (2.3.5) unstable; urgency=medium * The "Be Kind to Porters" release, mostly work on the non-i386 ports * Marcin Owsiany: - making sure that i18n code is included, moving over to stuff moved from CVS to their own packages * Adam Di Carlo - the logic to build a modules tarball for given root disk was a little messed up on non-i386, partly due to some schizophrenia in either rootdisk.sh or make/root issue; worked around - for sparc building, we use a single sun4cmd root.bin, because it doesn't matter which kernel we use and using none is not an option; better handling of generic rootdisk for all arches; only SPARC right now bothers to share a rootdisk for the different subarches, but I'm pretty sure other subarches which don't have kernel modules in their root filesystems should also set the 'generic_rootdisk' var in 'make/root' - remove the powerpc empty images-1.44 directory - other build fixes and cleanups - README (for developers): some updates - README (for users): rewrite the "Quick Install Instructions" part - debian/control: add dosfstools for powerpc, alpha, m68k; add linuxdoc-tools, snarf for powerpc (stuff in powerpc-specials); sync build-depends and depends - dynamically deal with READ-*.txt (internationalized top-level README); before, we weren't shipping the Galician one * Ethan Benson - todo: update status regarding PowerMac booting plans - bootprep.sh, milodisk.sh, nfsroot.sh, package-m68k.sh, release.sh, rescue.sh, tftpboot.sh: use /bin/bash as we should be - remove hfsutils and yaboot/ybin/mkofboot from the PowerPC root disk; these can be run from /target after base is installed, and frankly, we have no choice because we need the space - ybinwrapper added to root disk, sets up the environment for calling ybin from the new base system; add some symlinking into the target system as required by yaboot - Rewrite yaboot installation - vmlinu[xz] symlink fixage when /boot is a partition (run_yaboot/run_silo) - create /target/etc/kernel-img.conf when /boot is a partition so kernel-images will create symlinks that work with yaboot (run_yaboot) - More PowerMac partition checks/warning fixes, make sure they get displayed at the right times - Reworded PowerMac partition warning/info dialogs - Prevent non-ext2 /boot on PowerMac - Update Readme.yaboot - Update install-pmac.en.sgml with current info on NewWorlds - Remove obsolete instructions about manually running mkofboot on NewWorld macs from documentation/en/dbootstrap.sgml. Instead tell user to run Make System Bootable and reference yaboot.conf man page. - Add execlog_to_string function written by Colin Walters which stores a program's stdout in a variable, and sends its stderr to syslog, it also returns the program's exit code. - Reorg run_plilo_quik(), use execlog_to_string to run ofpath, cleanup/rewrite. * Stephen R. Marenka - Various and sundry updates to yaboot and quik boot configuration and partition checking. - Removed dbootstrap/powerma
Re: problem with latest boot-floppies
Matt Kraai <[EMAIL PROTECTED]> writes: > However, only the shell was executing on tty2, and it was in the > root directory. Does anyone know what might still be walking > around in /target/proc? Do ps -- it could be the man postinst... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install Pb With Raid controller
FYI, you need to be using the udma66 set (or in Woody, the ide flavor) of rescue/root/driver disks. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation of Debian on iMac DV 400Mhz
I would ask that you test with the woody version. I have images up at http://people.debian.org/~aph/debian/dists/woody/main/disks-powerpc/current -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dbootstrap_settings and proxy
Stephen R Marenka <[EMAIL PROTECTED]> writes: > Is there any reason we can't/don't save the proxy settings in > dbootstrap_settings so that we can have them in base-config? Nope, we should do this. > It'd be handy not to have to enter the info again. Yup. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Base Installation (aph 2.3.5 6/7)
Ethan Benson <[EMAIL PROTECTED]> writes: > known issue, this probably won't go away either. it happens because > man-db's postinst calls su -c 'mandb -c' and since there is no syslog > listening to /target/dev/log (where the chrooted su ran) the log entry > falls back to being spewed to the console. Hmm! I wonder if we can work around this somehow... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap and dselect tutorial
Josip Rodin <[EMAIL PROTECTED]> writes: > On Mon, Jun 11, 2001 at 06:38:50PM -0400, Adam Di Carlo wrote: > > > > if you want, you could take over the "build and release for web" > > > > stuff, that would be one less thing for me to do to keep > > > > http://www.d.o/releases/... documentation up-to-date. > > > > > > I forgot how it's done... maybe we should automate it and have it done > > > weekly from webmaster scripts. > > > > make doc-web > > make mirror-to-master > > Ah, right, I remember now. I'm now setting up a partial checkout on > www-master and a script to update it. You might get into trouble with a partial checkout. Watch out. > After this is done, can I get you removed from the debwww group, or did you > need it for anything else? If you want, you can certainly remove me. I work on the WML pages for www.debian.org in CVS -- I don't need debwww for that do I? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap and dselect tutorial
Josip Rodin <[EMAIL PROTECTED]> writes: > On Sat, Jun 09, 2001 at 02:43:31PM -0400, Adam Di Carlo wrote: > > > I have no special interest in splitting out release notes... anyway, > > > let me know if you need me to do something about this whole issue :) > > > > Nope -- if you want, you could take over the "build and release for > > web" stuff, that would be one less thing for me to do to keep > > http://www.d.o/releases/... documentation up-to-date. > > I forgot how it's done... maybe we should automate it and have it done > weekly from webmaster scripts. make doc-web make mirror-to-master > > And of course tkaing care of the woody release notes... > > I don't know if I'm going to be doing that, it's a lot of work :| Um, if you can't do it, can you find someone to take it over for you? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-checkbuilddeps
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > Who's fooling who? Or is this a special feature of the boot-floppies? > I think dpkg 1.9.8 for m68k was not built/uploaded because the i386 version > made some trouble. I guess you'll have to work around the lack of a new dpkg by either (a) replacing dpkg-checkbuilddeps with a symlink to /bin/true or hacking your local debian/control file or seomthing. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.3.5 test candidate
David Whedon <[EMAIL PROTECTED]> writes: > boot-floppies 2.3.5 is looking very good. Various cleanups that have > trickled in this weekend have given us a smooth install (at least on > i386). I have installed a couple times this weekend and have only > seen cosmetic bugs. I put a freshly built set up at: > > http://people.debian.org/~dwhedon/dists/woody/main/disks-i386/2.3.5-2001-06-10/ > > For your testing pleasure. Ok, I've retagged the sources, am building for i386 source upload. David, perhaps if you get this, could you start an i386 source / binary build as well ? Just in case you get it done faster than me. I'll try to start a powerpc build as well. I'm on #debian-boot on IRC if anyone wants me. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: m68k boot-floppies for woody
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > I built a busybox with Richards patch, rebuilt bf (well, it hangup sometime, > must be a local problem, but I got a new root.bin) and booting with the new > root.bin works fine on my amiga. I did not get far in the installation > (base.tar.gz is no more, all packages now have to be retrieved from cdrom, > net, whatever?), Yes, it pulls from a archive. I don't know if woody cdrom images are around so I always pull from http.us.debian.org or whatever. > but thats probably another local config problem (used the > wrong IP number for my NFS server). So I guess woody bf for m68k are > "working", we just need a little polishing here (fdisk manpages) and there > (documentation). Excellent to hear. Are you going to be able to do a binary upload of the built package for 2.3.5 when we release that shortly? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap and dselect tutorial
Josip Rodin <[EMAIL PROTECTED]> writes: > I have no special interest in splitting out release notes... anyway, > let me know if you need me to do something about this whole issue :) Nope -- if you want, you could take over the "build and release for web" stuff, that would be one less thing for me to do to keep http://www.d.o/releases/... documentation up-to-date. And of course tkaing care of the woody release notes... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: m68k boot-floppies for woody
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > On Fri, Jun 08, 2001 at 11:32:35AM -0400, Adam Di Carlo wrote: > > > ROOTCMD := $(shell [ d -u = 0 ] || echo sudo) > > > Guess it will fail when I build as root, and no sudo is installed. > > > > Just replace the "sudo" part by whatever you use to achieve root > > (super should work too). > I just replaced it with $ROOTCMdD seems the right way to do it. sudo was > working fine for me and I guess nobody would have ever noticed, who else > besides Richard is trying to build on m68k? Oh, yah, that's the right fix. You should commit that. I thought you were saying sudo wasn't working for you, but in fact the make rules were wrong. > > 'grab_paths m68k-vme-tftplilo' shoudl download that and return a path > > to where it was downloaded, or fail. > Where will it be downloaded to? Can try that at home. Under $ftp_archive. Apt is run, so there's a dir structure for that. > > Fine with me. I always wanted to add a quick-install section to the > > installation manual itself. The top-level README has some > > quick-install notes too, you can add m68k scribblings in there too. > No, I am not going to add things there. As much as I'd like m68k to be > documented, I do not have the time for that. If you see me adding things > there, you should disable my CVS access. Heh, well, I'll take anything I can get! No problem... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: m68k boot-floppies for woody
"Christian T. Steigies" <[EMAIL PROTECTED]> writes: > On Mon, Jun 04, 2001 at 08:23:24PM -0400, Adam Di Carlo wrote: > > > > Are you applying this patch or do you need someone to apply it? > > > > If you are sending patches to this need that need applying, please > > make it very clear, perhaps with subject of [APPLY PATCH PLS]. > I applied the subarch/system patch and the patch for the hfsutils, might > have to replace sudo by $ROOTCMD though... but does it matter?: > ROOTCMD := $(shell [ d -u = 0 ] || echo sudo) > Guess it will fail when I build as root, and no sudo is installed. Just replace the "sudo" part by whatever you use to achieve root (super should work too). > What is still missing is the location of m68k-vme-tftplilo_*.deb. Currently > it is searched in $archive/admin/m68k-vme-tftplilo_*.deb, which was working > in the potato boot-floppies. But the meaning of archive seems to have > changed a bit, for me s/"admin"/"download/archives" (off my head) and copying > the deb there worked. I don't know how to test for the deb to be there > before spending hours building and then failing here. A patch for the test > and downloading (in online mode only!) the deb to there would be more than > welcome. 'grab_paths m68k-vme-tftplilo' shoudl download that and return a path to where it was downloaded, or fail. > Besides that m68k suffers from a busybox<->linux-2.2 incompatiblity, Richard > is working on a fix. I guess I may not tell more right now ;-) Huh, well, be sure to file bugs against busybox if needed. > Oh, and I found a cosmetic problem. All the *manpage.txt files (amiga, > atarai, mac, etc) for m68k say: manpage not found. We had that earlier in > potato bf, and we had it fixed. Seems it needs to be refixed for woody. But > I'll look into that only after the busybox problem is solved. Yeah, I noticed that on powerpc as well, very annoying. > A little more than cosmetic is probably the m68k specific documentation. I > have absolutely no time to spend onto that. I propose to delete the m68k > specific quickinstall files completely, since they were not updated since > about one year. Not sure how much has changed for a woody installation, but > now is the time to get rid of that hack and integrate the m68k specifics > into the main documentation, that will save a lot of time in the long run, > or to have no m68k specific documentation at all. Fine with me. I always wanted to add a quick-install section to the installation manual itself. The top-level README has some quick-install notes too, you can add m68k scribblings in there too. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
critical problems in 2.3.5 prevent release
Well, on powerpc at least, the "configure base" step is getting
skipped by default. This leads to lack of /etc/fstab and other evil
conditions.
on booting into my new system, I didn't have the right inittab in
place; it gave me the "true" inittab instead
I have uploaded i386 and powerpc images to
http://people.debian.org/~aph/debian/dists/woody/main/disks-{i386,powerpc}/current.
Someone please test the i386 images to see if they are installable or
not. If someone coudl confirm the powerpc problems as well that
would be good.
Also, I need some poeple on the debian-boot list to file bugs as
appropriate against debootstrap and such...
* Other really annoying problems (but not blocking 2.3.5 release)
dhcp is failing after the first boot -- is debootstrap grabbing
dhcp-client when it installs base?
debootstrap is still saying: 'Failure trying to run: dpkg
--force-auto-select --force-overwrite --force'
the quik booting didn't work on this Wallstreet PowerMac, but that's
status quo, not a blocker per se. No, it's not ofpath failing, that
returns fine (ofpath /dev/hda => /pci/mac-io/ata0/ata-disk@0:). I
can't tell if that's actually used to set boot-device because the
system is going into serial console and I don't have one at the
moment.
Things working now:
- install sid works again (it is really identical to woody?)
- dhcp worked fine from dbootstrap
I'll have to retry 2.3.5 build on Monday because I'm out on a trip
until then.
Please
--
.Adam Di [EMAIL PROTECTED]http://www.onshored.com/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems with install
"Hofstede" <[EMAIL PROTECTED]> writes: > I downloaded the boot-cd image (app. 30 mb's) wich I think you call > 'Netboot cd' (?) Um, that didn't come from Debian, or not from us, at least. What was the URL? > Well, when I boot it, I get a screen full of text, and have to press > ENTER to continue. But when I press ENTER the screen goes black, and > the monitor light is orange... What could possibly be the > explanation for this? What is your architecture? i386 ? -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debootstrap and dselect tutorial
Josip Rodin <[EMAIL PROTECTED]> writes: > That would be good. Would this binary package be built from boot-floppies > source package, or do you want someone to make a whole new source package > for it? If the latter, it would be no problem for me to do so[1]. Hmm, you're the release notes maintainer. If you want to split the release notes into another package, that's certainly an option. As for the installation manual, I'm not wanting to move that to another package because there's too much stuff I grab from the 'make' command line, as well as dbootstrap messages and stuff. I probably will move it out when we shift to debian-installer, but not until then. > I suppose if it cannot be put in a dialog the base-config program can fork a > more(1) or less(1), that's usable, too. I don't think it's much of a problem -- debconf can pretty much show files, I think. Would be nice for it to be i18n sensitive as well about it... -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tail /var/log/messages spasm
Ethan Benson <[EMAIL PROTECTED]> writes: > no that won't change anything, what your seeing is no such file or > directory messages being logged. Oh, that's a possibility too. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tail /var/log/messages spasm
Stephen R Marenka <[EMAIL PROTECTED]> writes: > Intermittently during testing, I've found that the tail > /var/log/messages running on tty3 sometimes reports "no such file or > directory." I assume this is because the messages file simply doesn't > exist yet. > > Certainly one fix for this would be to touch messages in=20 > scripts/rootdisk/prototype/var/log, thus creating an empty file. Perhaps > another way is to otherwise create the file at boot time, perhaps in > inittab? > > What's the best solution? I think the idea of shipping an empty scripts/rootdisk/prototype/var/log/messages file seems fine. Someone should just add that to CVS, no code changes needed. > On another topic: currently, the default ext2 partition formatting > provides backward support for 2.0 kernels. Would anyone object if I > change the default to 2.2 (and later) kernels? I noticed that the arm > message (in utilities/dbootstrap/partition_config.c) is a bit different, > something about netwinder firmware. I won't change that entry without > explicit instructions. Yes, let's drop it except on ARM, which needs it for their bootloader. No other boot loader requires the ext2 from 2.0 and can't cope with the ext2 from 2.2 kernels (unless I'm mistaken). -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem building b-f, need help
Marcin Owsiany <[EMAIL PROTECTED]> writes: > On Thu, Jun 07, 2001 at 08:54:06AM -0700, Ron Farrer wrote: > > Does anyone know what is wrong? > > Looks like it doesn't fit. :-( Yes, jack up the size of the rootdisk. -- .Adam Di [EMAIL PROTECTED]http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
