PMAC boot after install
hello, i have a Apple G3/266 with internal ide drives. i partitioned a drive as so: hdc1 partition map hdc2 Apple_Bootstrap 800k hdc3 LinuxSwap 200MB hdc4 LinuxRoot 2GB i then booted off the latest Debian2.2r3 CD for PMAC and followed all the steps, mounting hdc4 as root /. when the base install is finished the install script says "reboot mac" it then reboots but i just get a blinking disk image. why is the debian installer not able to make the root partition bootable ? ben_g -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
init fails to boot from loop-aes encrypted raid root fs due: "/dev/md1: no such file"
Hello guys! I have a problem where I reach the end of my linux competences. ~~~ This is what I try to accomplish: Install Debian 5.0.3/AMD64 on a blank system with 3 SATA IDEs Fully encrypted using loop-aes (mandatory). System should be able to start with 1 failed/missing disk Partition scheme (identical on all 3 discs): 256MB /boot, ext3 / RAID1 , plain 4 GB /, ext3 / RAID5 , loop-aes (key) 512MBswap , loop-aes (tmp) 1,5TB /srv , ext3 / RAID5 , loop-aes (key) /bootattached via /dev/md0 /, /srv attached via loop0,1 ontop of /dev/md1,2 ~~~ installation process: I was very pleased to see loop-aes supported in the expert installater at all! My first attemp to install from a USB stick failed as the installer itself already loads the loop device without loop-aes support code. So I grabbed a DVD drive and now I'm working with the debian-503-amd64-xfce+lxde-CD-1.iso ~~~ problem: The system fails to boot and repetingly writes: "/dev/md1: No such file or directory" (/). As far as I understand, the init script tries to mount /dev/md1 to / but the RAID5 has yet not been started prior to mounting the root fs. During startup I see sth like: < sda found > < sdb found > < sdc found > done. Begin: Mounting root file system /scripts-localtop What I miss there is the output which says that a RAID has been detected and initialized (superblocks are all fine). The installer offered to use a "custom initrd". I tried to reinstall and use the "generic initrd" without any luck, either. I tried to inspect the initrd with my limited capabilities and it contains the gpg key for the root fs and a few init scripts. So this seems to went fine. I thought maybe I need to include some missing modules but I have no clue how I would have to rebuild the initrd without the system being up and running. First of all I have no idea what to change at all :-) Any hints how I get this system bootable? I will dowloaded Knoppix to get somehow access at least to the initrd. Thank you very much for your time and support! - Ben -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: initchroot feature?
On Fri, Jun 09, 2000 at 12:19:14AM -0600, Erik Andersen wrote: > On Thu Jun 08, 2000 at 11:15:11PM -0400, Ben Collins wrote: > > On Thu, Jun 08, 2000 at 04:51:03PM -0700, Christoph Lameter wrote: > > > I see that dbootstrap supports the "initchroot" feature of some kernel to > > > start the new system without rebooting... But I cannot find that in any > > > kernel source? > > > > > > > It was a patch distributed on l-k some time back. I tried to get it > > working, but it had issues with NFS roots, so I put it on the backburner > > until woody/2.4.x (which includes the feature). > > Since Woody will be using the 2.4 kernel, we will be able to use the new "pivot > root" feature to do this, whic does essentially the same thing, but does it > much cleaner. The current "initchroot" stuff in dbootstrap and in busybox init > will be replaced with new stuff to do the "pivot root" thing. But this is > definately Woddy stuff. Yeah, pivot root is the final state of the initchroot patch I was using. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[PROBLEM] in 2.2.15 busybox tar
I've discovered a problem in the tar in busybox with boot-floppies 2.2.15. I tested with busybox-tar and GNU tar, and it is defenitely in busybox. For some reason it is making ./ mode 644 (even though in the base2_2.tgz tarball it is 755). This basically means that users are getting a / with 644 (-x) perms. I've only seen this on sparc, but the fact that is in busybox leads me to believe it is not sparc specific. Concerns me that it is not being seen elsewhere. I'll look and see where this is coming from though, unless some others can check into it. Ben -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PROBLEM] in 2.2.15 busybox tar
On Fri, Jun 09, 2000 at 01:52:43PM -0400, Ben Collins wrote:
> I've discovered a problem in the tar in busybox with boot-floppies 2.2.15.
> I tested with busybox-tar and GNU tar, and it is defenitely in busybox.
> For some reason it is making ./ mode 644 (even though in the base2_2.tgz
> tarball it is 755). This basically means that users are getting a / with
> 644 (-x) perms. I've only seen this on sparc, but the fact that is in
> busybox leads me to believe it is not sparc specific. Concerns me that it
> is not being seen elsewhere.
>
> I'll look and see where this is coming from though, unless some others can
> check into it.
Ok, I put some printf() statements in tar.c to see what was going on. It
looks like there is a more serious issue involved, and sparc is just
triggering it in a way that shows. The printf's I added were right before
all the calls to chmod(). I had it do this:
printf("1 changing mode for %s to %o\n", outName, mode);
(the starting number varied so I could trace which call was printing). I
got some odd output from one of the calls, that look like this:
4 changing mode for order hosts,bind
multi on
to 100644
error in chmod()
Some others were there with lots more garbage data (the chmod() error check
was added later to confirm). This looks like something is not pointing to
the right part of the header. There looks like there was even some
legitimate chmod()'s that resulted in errors:
4 changing mode for ./etc/chatscripts/ to 100755
error in chmod()
Now, this "#4" call was in this code, starting at around line 710 of the
tar.c file:
/*
* Check if we are done writing to the file now.
*/
if (dataCc <= 0 && tostdoutFlag == FALSE) {
struct utimbuf utb;
if (close(outFd))
perror(outName);
/* Set the file time */
utb.actime = mtime;
utb.modtime = mtime;
utime(outName, &utb);
/* Set the file permissions */
chown(outName, uid, gid);
printf("4 changing mode for %s to %o\n", outName, mode);
if (chmod(outName, mode))
printf("error in chmod()\n");
outFd = -1;
}
I'm not sure where outName is getting mangled, but it is, and it is
causing problems. On sparc, the current base2_2.tgz is showing it is /
ending up being mode 644, on other archs it could means that things are
not getting the right perms. I'm still tracking the problem though.
--
---===-=-==-=---==-=--
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PROBLEM] in 2.2.15 busybox tar
> > I am pretty close to making the BusyBox 0.44 release at the moment. > What about boot-floppies? -- ---===-=-==-=---==-=------ / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PROBLEM] in 2.2.15 busybox tar
> /*
> * Check if we are done writing to the file now.
> */
> if (dataCc <= 0 && tostdoutFlag == FALSE) {
> struct utimbuf utb;
>
> if (close(outFd))
> perror(outName);
>
> /* Set the file time */
> utb.actime = mtime;
> utb.modtime = mtime;
> utime(outName, &utb);
> /* Set the file permissions */
> chown(outName, uid, gid);
> chmod(outName, mode);
>
> outFd = -1;
> }
I just commited a fix that gets rid of the utime(), chown(), and chmod()
calls from this part of tar.c. From what I showed, the utime, mode, and
ownership is already set once prior to this being called. Doing so again
is pointless.
Ben
--
-------===-=-==-=---==-=--
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#65429: boot-floppies installation stopped by tetex-bin bug
On Fri, Jun 09, 2000 at 03:40:41PM -0400, Robert J. Chassell wrote: > Package: boot-floppies > Version: 2.2.15 > > Linux megalith 2.2.12 #1 Thu Oct 14 09:29:24 EST 1999 i686 unknown > /lib/libc.so.6 -> libc-2.1.3.so Wouldn't tetex-bin be the right place to file this bug? How can a package be held accountable for bugs on the packages it depends on? Ben -- ---===-=-==-=---=--------=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PROBLEM] in 2.2.15 busybox tar
On Fri, Jun 09, 2000 at 02:23:55PM -0600, Erik Andersen wrote: > Quoting Ben Collins <[EMAIL PROTECTED]>: > > > > > > I am pretty close to making the BusyBox 0.44 release at the moment. > > > > > > > What about boot-floppies? > > Depends on the consensus of the boot floppies developers. > > If folks want my latest and greatest in the boot floppies, then > I will be glad to merge it in. I think the easiest solution > for the future (and very possibly the present) is for me to > create a busybox.deb that conflicts with just about everything, > and that can be unpacked into the boot floppies the same way > the ash.deb is unpacked. That would be ideal for woody. For now, are there any known issues with the current busybox in boot-floppies that need to be resolved now? -- -------===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#65429: boot-floppies installation stopped by tetex-bin bug
On Fri, Jun 09, 2000 at 09:26:14PM -0400, Robert J. Chassell wrote: >> Also, I thought that the problems with boot-floppies were holding back >> this release: they are critical. > >come one. I've build 2.2.15 in a chroot and installed those packages wia apt >and it worked OK. > > How did you do that? I cannot. > >> I will remind the tetex-bin maintainers that the bug is holding back >> boot-floppies. > >no, it's not. > > Yes, it is holding boot-floppies back: take a look at my error > messages. I am running a properly upgraded frozen and boot-floppies > are not installing on account of the bug in tetex-bin. > > There is some difference between your system and mine that is not > being handled, so boot-floppies are failing. This is a bug, since > boot-floppies should be installing. If you want to build boot-floppies, you have to install tetex. If you cannot install tetex, that is a bug in tetex, not boot-floppies. Plain and simple. Although there is no way it is holding up boot-floppies considering *every* (and that means all 6) one of the archs releasing with potato have built boot-floppies 2.2.15. They are in the archive, go check. So, it is not holding up anything. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#65429: boot-floppies installation stopped by tetex-bin bug
>... Although there is no way it is holding up boot-floppies >considering *every* (and that means all 6) one of the archs releasing with >potato have built boot-floppies 2.2.15. They are in the archive, go check. >So, it is not holding up anything. > > This is false. I cannot install tetex-bin and I cannot install > boot-floppies using No, this is true. Look on the mirrors. You will see 2.2.15 boot-floppies for all archs under potato. I didn't say you. > > So this is a bug. I should be able to install boot-floppies using > apt-get in these circumstances. (If tetex is required for > boot-floppies, then it has to install sucessfully also.) > Yes you should, and you can't because of tetex, which is a bug in tetext!. If you filed a bug on every package that could not be installed because another package could not be installed we would have a sphaghetti of inter-dependent bug reports. This isn't the case. Put blame where blame lies, on tetex. -- ---===-=-==-=====---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[REASSIGNED] Re: Bug#65429: boot-floppies installation stopped by tetex-bin bug
On Sun, Jun 11, 2000 at 09:38:42AM -0400, Robert J. Chassell wrote: >Yes you should, and you can't because of tetex, which is a bug in tetext!. >If you filed a bug on every package that could not be installed because >another package could not be installed we would have a sphaghetti of >inter-dependent bug reports. > > Right. But in this case, the bug that prevents me from installing > boot-floppies is a bug (among others) that is preventing the release > of Debian 2.3. It is `release critical'. a) potato is Debian 2.2. Debian 2.3 (woody) will not be releasing for quite a few months. So if you are working with woody, then get over it because we are only worried about potato until the day it releases. This is not holding up release, all of the boot-floppies builds for potato worked, and every HAD to have tetex-bin installed to do it. b) I'll say it again, it is not the responsibility of the boot-floppies maintainers to make sure that other packages needed for it are installable. That is left up to the respective package maintainers. > I don't know whether the person maintaining tetex-bin knows that. I > would hope he would be more likely to fix the bug if you said to him: > `a bug in tetex-bin is holding up the release; please help!' Again, this is something you have to communicate to the tetex-bin maintainer. As the bug reporter, YOU have the responsibility to relay that information. > It is fine to offload blame, but boot-floppies needs to install and > right now it does not. > > apt-get install boot-floppies > > is broken. Yes, you can put the blame on tetex-bin, but the > responsibility, willy-nilly, is yours! No, "installing tetex-bin" is broken. If you simply did "apt-get install tetex-bin" you would see the same problem. BOOT-FLOPPIES MAINTAINERS CANNOT FIX A BUG IN TETEX!. Plain and simple. Only the tetex-bin maintainer can fix the problem. I have reassigned this bug to tetex-bin, please let this discussion die. Saying that boot-floppies is responsible for a broken tetex-bin install is like saying it is a bug in GCC that "non_existant_func(blah)" wont compile. It is just not the case. When reporting bugs, and placing "blame" as you like to call it, we are very specific technically about where that "blame" lies. The fact is that it lies in tetex-bin, and no where else. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PROBLEM] in 2.2.15 busybox tar
On Tue, Jun 13, 2000 at 01:16:32AM -0400, Adam Di Carlo wrote: > Erik Andersen <[EMAIL PROTECTED]> writes: > > > What bugs in the current boot-floppies BusyBox need to be fixed? > > > Probably just the tar bug. Other things, such as Bug #64576 > > are not really critical. > > I agree with that. I mean, the busybox changelog you offered the link > to does look really good, but then again, it's much to late to > introduce heavy changes. > > So -- who is handling fixing the tar bug? It's done and in CVS. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [PROBLEM] in 2.2.15 busybox tar
> > Did this fix the problem you were seeing then? > Yes, thanks. -- ---===-=-==-=---==-=------ / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [dbootstrap] `newt' and `boxes.c', `bogl' and `bowl'[, `???' and `boxeX.c'?]
[EMAIL PROTECTED] (Karl M. Hegbloom) writes: > I'll try to keep in mind that there needs to be a generic interface > that can be implemented by other GUI frontends, in the way that > `boxes.c' and `bowl' do it now. I'm going to break things on purpose > though, just for the freedom of it. I'll do a newt interface, if I > can, and not worry too much about `bogl' for now. Worrying about BOGL is probably a waste of time. AFAIK no work has been done on it in a long time. I agree that your approach is probably the best. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [woody,debinst] (Was: Re: [dbootstrap] `newt' and `boxes.c', `bogl' and `bowl'[, `???' and `boxeX.c'?])
On Fri, Jun 16, 2000 at 09:44:31PM -0600, Erik Andersen wrote: > On Sat Jun 17, 2000 at 01:29:43PM +1000, bug1 wrote: > > > Red Hat's `libfdisk' contains a partition editor with a `newt' > > > interface. It might be possible to port it to our system and hook > > > that into our Woody `debinst' `dbootstrap'. > > > > > What about parted, it doesnt have much a of a GUI, but it wouldnt be > > hard to do i dont think. > > I think the ability to resize existing partitions (non destructivve > > install) is one most users would really like. > > Agreed re parted. I think a cool project would be hacking a GUI similar to > cfdisk into parted... Better get parted to support more than just msdos partitions before we even thing of using it in boot-floppies :) Also, I'm looking into a program on freshmeat called genext2fs that can create ext2 images from a directory (and using an optional device list for devices) as non-root. Would be very nice for woody boot-floppies, IMO. It's a single .c, so could go into utilities if it doesn't get packaged. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [woody,debinst] (Was: Re: [dbootstrap] `newt' and `boxes.c', `bogl' and `bowl'[, `???' and `boxeX.c'?])
On Sat, Jun 17, 2000 at 02:22:10PM +1000, bug1 wrote: > Ben Collins wrote: > > > > > Also, I'm looking into a program on freshmeat called genext2fs that can > > create ext2 images from a directory (and using an optional device list for > > devices) as non-root. Would be very nice for woody boot-floppies, IMO. > > It's a single .c, so could go into utilities if it doesn't get packaged. > > > > Im a bit slow sometimes, how would it be used by boot-floppies? To create rescue.bin and root.bin without being root (IOW, without mounting a loop filesystem, etc...). Basically you copy all the files to a directory, and run the program, and it will create an image that mirrors that directory (and it creates everything as root.root, no matter what the perms are in the dir). -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [woody,debinst] `genext2fs', loop-dev and fakeroot?
On Sat, Jun 17, 2000 at 02:30:39AM -0700, Karl M. Hegbloom wrote: > >>>>> "Ben" == Ben Collins <[EMAIL PROTECTED]> writes: > > Ben> On Sat, Jun 17, 2000 at 02:22:10PM +1000, bug1 wrote: > >> Ben Collins wrote: > >> > >> > > >> > Also, I'm looking into a program on freshmeat called genext2fs that can > >> > create ext2 images from a directory (and using an optional device list for > >> > devices) as non-root. Would be very nice for woody boot-floppies, IMO. > >> > It's a single .c, so could go into utilities if it doesn't get packaged. > >> > > >> > >> Im a bit slow sometimes, how would it be used by boot-floppies? > > Ben> To create rescue.bin and root.bin without being root (IOW, without > Ben> mounting a loop filesystem, etc...). Basically you copy all the files to a > Ben> directory, and run the program, and it will create an image that mirrors > Ben> that directory (and it creates everything as root.root, no matter what the > Ben> perms are in the dir). > > If it could be made to work together with `fakeroot'... > > What if a loop filesystem could be set up to be `fakeroot' to a user? > Can a good kernel hacker make us one like that? Why hack the kernel when this program already does what we want in userspace? -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [woody,debinst] (Was: Re: [dbootstrap] `newt' and `boxes.c', `bogl' and `bowl'[, `???' and `boxeX.c'?])
On Fri, Jun 16, 2000 at 10:44:13PM -0600, Erik Andersen wrote: > On Sat Jun 17, 2000 at 12:02:51AM -0400, Ben Collins wrote: > > On Fri, Jun 16, 2000 at 09:44:31PM -0600, Erik Andersen wrote: > > > On Sat Jun 17, 2000 at 01:29:43PM +1000, bug1 wrote: > > > > > Red Hat's `libfdisk' contains a partition editor with a `newt' > > > > > interface. It might be possible to port it to our system and hook > > > > > that into our Woody `debinst' `dbootstrap'. > > > > > > > > > What about parted, it doesnt have much a of a GUI, but it wouldnt be > > > > hard to do i dont think. > > > > I think the ability to resize existing partitions (non destructivve > > > > install) is one most users would really like. > > > > > > Agreed re parted. I think a cool project would be hacking a GUI similar to > > > cfdisk into parted... > > > > Better get parted to support more than just msdos partitions before we > > even thing of using it in boot-floppies :) > > ??? > Parted supports ext2. > http://freshmeat.net/appindex/1999/09/19/937790960.html ext2 is a filesystem, I mean partition tables. Like Sun, Amiga, Apple (check libfdisk). Until parted can deal with those types of partition tables, it is useless on anything but i386, and some alphas. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: b-f and 2.2.16
On Mon, Jun 19, 2000 at 07:03:14PM +0200, Petr Cech wrote: > Hi, > there s 2.2.16 kenel in Incoming. Will we go with this one or will we stay at > 2.2.15+patch? Does the 2.2.16 source in incoming have Alan's errata patch included? -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: b-f and 2.2.16
On Tue, Jun 20, 2000 at 12:59:47AM +0200, Petr Cech wrote: > On Mon, Jun 19, 2000 at 03:05:02PM -0400 , Ben Collins wrote: > > On Mon, Jun 19, 2000 at 07:03:14PM +0200, Petr Cech wrote: > > > Hi, > > > there s 2.2.16 kenel in Incoming. Will we go with this one or will we stay at > > > 2.2.15+patch? > > > > Does the 2.2.16 source in incoming have Alan's errata patch included? > > doesn't seem so :( Actually it does appear to have that errata (changelog doesn't say so, but the .diff.gz has it in there). -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [m68k] boot-floppies for test cycle
> > I am only waiting for an updated m68k CD image so that I can burn it. Not > excatly sure, if any of the previous potato/m68k images has been burned and > tested, I think we all did only visual inspection... > Unfortunately debian-cd got borked, so I haven't made the image yet. It will be coming soon (after dinstall run today). -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FWD: Report: 2.2.16 i386 build available for testing
On Thu, Jun 29, 2000 at 04:17:35PM -0700, Joey Hess wrote: > Ok, this is the 3rd time I've seen the problem with it being unable to > load the kaymap. The other two were with boot-floppies I built with a > patched kernel, not the 2.2.16 test build, and so I disregared them > until now. > > But it looks like a real, general problem. When I saw it, I had picked the > defaults when setting up the keyboard, and it gave the error he > mentioned. VT 3 said it was not a valid keymap file. > I then went to the shell, found the keymap tarball, unpacked it, and > verified the file it was trying to load existed and was nonzero. I > didn't get any further though. I changed the logic for this somewhat to fix a sparc keymaps problem. I'll check it shortly. Ben -- ---===-=-==-=====---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: busybox_0.45-1_i386.changes REJECTED
On Sat, Jul 01, 2000 at 10:24:53AM -0600, Erik Andersen wrote: > On Sat Jul 01, 2000 at 11:27:31AM -0400, Antti-Juhani Kaijanaho wrote: > > This package violates policy in several ways: > > - first of all, the busybox binary package does not include > > a copyright file, a changelog file or - indeed - a > > /usr/[share/]doc/ directory! > > > > - second of all, > > E: busybox: symlink-should-be-relative bin/head /bin/busybox > > [...] > > > > - third of all, I am not sure if it is a good idea to > > include a package in the distribution that cannot be > > installed into a system without breaking that system > > (this package conflicts with many essential packages) > > You should definitely bring this issue up on -devel or > > -policy before reuploading (btw, I cannot find an ITP > > for this package...) I don't think he undertstands that this "package" was previously an integral part of the boot-floppies package and has since been split out for easier maintainence. He needs to revert that decision. Erik, it might have been a good idea to include this info in the package upload so there was no misunderstanding :) Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: busybox_0.45-1_i386.changes REJECTED
On Sat, Jul 01, 2000 at 07:58:39PM +0300, Antti-Juhani Kaijanaho wrote: > On Sat, Jul 01, 2000 at 12:40:55PM -0400, Ben Collins wrote: > > I don't think he undertstands that this "package" was previously an > > integral part of the boot-floppies package and has since been split out > > for easier maintainence. > > "Easy maintenance" is not a valid reason to include noninstallable > packages in the distribution and thus irritate the users. > > BTW, I am perfectly aware of what busybox is. > > > He needs to revert that decision. > > Why is it that everyone seems to be against discussing this matter > in a proper forum? (I'd prefer that Erik or someone else from -boot > initiated this discussion so that the list gets a clean propsal that > can be discussed.) No one is against discussing it. It was already discussed with the people that matter. If it can't be installed, and it is documented as such in the package description, then I see nothing of how it affects the distribution as a whole. The only other alternative is to provide a source .deb instead of a binary package. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: busybox_0.45-1_i386.changes REJECTED
> > The only other alternative is to provide a source .deb instead > > of a binary package. > > Why does it *have* to be a .deb? Quite possibly because you can't upload source only and all uploads have to include a .deb? Atleast last I checked that was the case. -- ---===-=-==-=---=--------=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SparcStation
On Fri, Jul 07, 2000 at 01:44:19PM +0300, [EMAIL PROTECTED] wrote: > > Hi, > > I have a Sun SparcStation 5 and I would like to use Linux on it. Is Debian > compatible with SparcStation5? Yes. You would be better off directing sparc specific questions to [EMAIL PROTECTED] Use the sun4cdm images under disks-sparc on the ftp archive. Ben -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#67082: "Choose debian archive" box confusing
Package: boot-floppies Version: 2.2.15 When installing the base system from NFS, I first get asked for a server and mount point, and then for a directory within that mount that holds the Debian archive, with the default being "/instmnt". My immediate response was to replace this with "/debian", since that was the correct directory name in the mounted filesystem. When I did this, I found that pressing return had no effect. I had to use the shell on tty2 to discover that I should have typed "/instmnt/debian". Either the box should automatically prepend "/instmnt" to the supplied path, or it should explain what /instmnt is. Error messages when an invalid path is supplied would be nice, too. -- Ben Harris Unix Support, University of Cambridge Computing Service. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel dev patches
> The reason for not just using the normal /proc is that it enlarges the > kernel by about 67KB in 2.[34].x which is about 5% of our space on the > initial boot floppy. By using a few dev modules we could (if we choose) > avoid having to use a kernel with /proc support compiled in. I Don't think we will ever be able to reasonably support using a kernel without /proc on boot-floppies, or any other system. There are quite a few things that are needed in /proc besides partitions and filesystems (among them are cpuinfo). Replacing all of them with some sort of device or ioctl type thing, isn't feasible I think. Ben -- ---===-=-==-=---=--------=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel dev patches
On Wed, Jul 19, 2000 at 04:44:11PM +1000, bug1 wrote: > Daniel Jacobowitz wrote: > > > > On Wed, Jul 19, 2000 at 12:02:30AM -0400, Ben Collins wrote: > > > > The reason for not just using the normal /proc is that it enlarges the > > > > kernel by about 67KB in 2.[34].x which is about 5% of our space on the > > > > initial boot floppy. By using a few dev modules we could (if we choose) > > > > avoid having to use a kernel with /proc support compiled in. > > > > > > I Don't think we will ever be able to reasonably support using a kernel > > > without /proc on boot-floppies, or any other system. There are quite a few > > > things that are needed in /proc besides partitions and filesystems (among > > > them are cpuinfo). Replacing all of them with some sort of device or ioctl > > > type thing, isn't feasible I think. > > > > Not to mention that it makes it nearly impossible to use the installer > > to rescue a system - I always begin by chrooting and mounting proc > > inside the chroot! > > > > Dan > > Fair enough, still its unfortunate that proc wasts a lot of space, i > guess its just unavoidable then. > > I might continue with it anyway just for personal interest and to help > me in understanding how the kernel works. If you are really interesed in writing some code, I'de like to see a smallish library that interprets things in /dev of a devfs mounted filesystem. query things like drives, partitions, devices, etc.. Devfs is definitely going to be the way to go in woody. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#68016: tftp and floppy install broken on sun4m
On Mon, Jul 31, 2000 at 03:20:10PM +0200, Christian Meder wrote: > Package: boot-floppies > Version: 2.2.16-2000-07-14; > Severity: important > > The kernel boots ok but when init starts busybox things fall apart: > > init started: BusyBox 0.43 (2000.07.06-13.xxx) multi-call binary > E: /proc does not appear to be mounted (No such file or directory) > E: /proc does not appear to be mounted (No such file or directory) > E: /proc does not appear to be mounted (No such file or directory) > E: /proc does not appear to be mounted (No such file or directory) > E: /proc does not appear to be mounted (No such file or directory) I've heard several reports about this, and it seems that busybox (or something it executes) is getting a sigsegv. This only happens on sun4m (and I suspect only on LX's), and all attempts to track it down have failed. I suspect the kernel, but I'm just not sure enough about where it comes from (coupled with the fact that I don't have a sun4m locally to test). Let me know if you are able to track it down. Ben -- ---===-=-======-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#68016: tftp and floppy install broken on sun4m
> > So what's the moral of the story: a (normal) bug report against gcc 2.95 > because it seems to misoptimise jobs.c for sparc (although it works on > sparc64), an (important) bug report against ash to get it recompiled for > sparc potato (either disable -O2 for jobs.c or use gcc2.7.2.3) which is > needed to get proper boot floppies for sparc32 and a clarification to the > boot floppies and busybox people which are not responsible for this bug. > > I'll keep the boot floppies bug open anyway until we got new sparc boot > floppies with a fixed ash. Thanks Christian, I've been hoping someone with the hardware would track this down, and you did an excellent job of doing just that. I'll recompile ash (binary only, w/o optimizations) and rebuild boot-floppies in time for potato release. Ben -- ---===-=-==-=====---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#68016: tftp and floppy install broken on sun4m
> > After recompiling new boot floppies could you put them up somewhere. > Recompiling boot floppies on our small sparc 10/20 and Ultra I is a pain. > Done. Please try these: http://auric.debian.org/~bcollins/disks-sparc/2.2.16-2000-08-03/ You should only need to get the root.bin to make sure it works for you (that's the only thing that should be different). These should be installed on the archive today, and show up in mirrors by this evening. > BTW thanks for all the potato work on the sparc port, Ben. My pleasure. Ben -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't network install with 3c905TX???
Valentijn Sessink <[EMAIL PROTECTED]> writes: > Tried to install potato, and as we're running a local Office-wide ;) > Debian-mirror, I thought it would be easiest to install by NFS. Well, I > could not even try it, as the boot/root floppies refuse to let me insert > the proper NIC module. You need to use the `compact' boot disk and driver disks, which have NIC drivers compiled in. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /boot nonexistant on sun4cdm install disk set
On Sun, Aug 13, 2000 at 06:08:02PM -0400, Adam Di Carlo wrote: > William Cordis <[EMAIL PROTECTED]> writes: > > > I have a SPARCstation 5 that I'm trying to install debian on. I downloaded > > the 2.2.16-2000-07-14 disks from /debian/dists/potato/main/disks-sparc/sun4cdm > > and the root.bin that I used came from > > debian/dists/potato/main/disks-sparc/images-1.44 > > > > All went fine until I tried to download the driver.tgz from http.us.debian.org > > Since I was using DHCP to configure the machine I checked /etc/resolve.conf. > > It was empty so I put our DNS server in there and was able to ping > > http.us.debian.org. Unfortunately the perl method didn't notice the change > > and still reported the name as unable to resolve. Putting in the ip worked > > and nothing else went wrong until I tried to install SILO. It failed so I > > ran it manually from the console. It reported that it couldn't load the > > second stage boot-loader /boot/second.b. A quick survey showed no /boot at all. > > Did I download a bad image for my root.bin?? > > Try the newer 3 August versions, I think. > > If that fails, please submit a bug against boot-floppies. No, there should be no /boot in the root.bin. The /boot that silo uses is /target/boot. Silo us run as "silo -r /target" so that it will chroot to the new installed filesystem. Try running that and see if there is an error. I'm wondering what happened to make you think it failed. Was there an error message? If so, what was it? Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /boot nonexistant on sun4cdm install disk set
> 1. DHCP doesn't work correctly, all the information is recieved, the > interface goes up, the route's are correct, but no DNS. No matter what > I do. I checked /etc/resolv.conf, nothing there. The information is in > /tmp/resolv.conf but even if I manually set up the device afterward it doesn't > work. It works fine if I set it up manually the first time with the same info > as it recieves from the DHCP server. That's a general problem then, I suspect. > > Is there something I'm missing in the install guide > Yeah, don't make a seperate /boot partition. SILO is not like LILO. It actually reads the ext2 filesystem directly. This is something I could not solve in the boot-floppies easily, so you have to work around it. I don't think you'll lose much by not having /boot on its own partition. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: DHCP and /boot
> > Hrm.. Ok. I somehow got the wrong message and thought I needed to keep > > the kernel below some cylinder number. I'll try that. Thanks. > > Ah, no, that is i386 BIOS hackery only. Actually some older sparc PROM's cannot handle this either (1024 cyl. limit). But I've never come up against it. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cant start X
> > > > rm -f /dev/gpmdata > > Is this in Installation Instructions or Release Notes somewhere? > Can we get this inode removed from the sparc image build? Am cc'ing > d-boot and d-doc. > It needs to be part of the errata. The logic of the patch that causes this problem is that if gpm is not installed (more specifically not running), then opening the device will fail. Problem is, it's not a device, nor a socket, it's a FIFO. So opening it succeeds no matter what. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Booting Sparc Station 1/2
On Tue, Aug 22, 2000 at 09:46:54PM -0400, Adam Di Carlo wrote: > Mathias Wiklander <[EMAIL PROTECTED]> writes: > > > I have problem booting a SS1 and a SS2 with the Debain 2.2 Sparc CD. It > > boots and when it want to start init it says that "Default console not > > found" or something like that. > > I'm not sure. I've CC'd the sparc user base. Please let us know if > this is a problem which can be fixed in the boot-floppies by opening a > bug against boot-floppies. I've already replied. This *was* an issue with the first set of sparc ISO's. It has since been resolved and new ISO's are available under 2.2_rev0_CDa/ directories, where they have been mirrored. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
> > We really need a hardware detection library that is modularized or can > be modularized. There is no need to have code in the installer to detect > your sound card. And if you're installing from a floppy and the network, > you need NIC detection code, but code to detect a CD drive is > unnecessary bloat. > > Also, we have to keep in mind that hardware detection is a two-edged > sword. It's great until it probes somewhere it shouldn't and crashes > your system. Strictly passive hardware detectors avoid this of course, > but they detect less hardware too (no ISA cards, probably). > > Would some interested people like to get together and do some thurough > research of the available hardware detection software, and present a > report w/reccomendation to this list? Speak up if you're interested. The good thing about PCI hardware detection is that there is no probing, and the PCI layer/driver handles allocation an IRQ and I/O. So basically the gist is, atleast include PCI detection, which maps PCI device ID's to modules, and can prompt for which ones to load. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
On Tue, Sep 12, 2000 at 06:46:44PM -0700, Joey Hess wrote: > Ben Collins wrote: > > The good thing about PCI hardware detection is that there is no probing, > > and the PCI layer/driver handles allocation an IRQ and I/O. So basically > > the gist is, atleast include PCI detection, which maps PCI device ID's to > > modules, and can prompt for which ones to load. > > Right. We already do PCI hardware detection, after all, for video card > setup with anXious. > > Maybe that's all the hardware detection we should bother with. Is there > really any point in worrying about making life easier for owners of ISA > hardware these days? IMO, we shouldn't. Trying to autodetect ISA is probably more harm than good anyway. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
On Tue, Sep 12, 2000 at 07:57:23PM -0700, Joey Hess wrote: > Dan Helfman wrote: > > Not to mention confidence in x86 hardware.. > > Well that made me realize the big thing we've missed in this hardware > detection discussion so far: what about other architectures? > > (I'm not a multi-arch kind of guy, so I occasinally need to be reminded > to consider them..) > > Is hardware detection needed much in other architectures? None of them > have the same proliferation of crappy hardware as the x86 world. I guess > everything we've discussed about PCI hardware applies to alphas too. > Anything else on other architectures that needs to be detected? Most everything under UltraSPARC is either PCI, or it's built into the kernel (standard hardware). In fact, 90% of UltraSPARC installs do not need to load a single module to get enough functionality for an install. This includes all supported SCSI, ethernet and IDE drivers. As for SPARC, it doesn't have PCI, but again the standard hardware is built into the kernel, so no need for hardware detection here. There are so few needed drivers for SPARC/UltraSPARC (no wacked out "only-one-person-owns-it" type of hardware), that it was possible to compile most of them into the kernel directly and still fit on the rescue disk. -- -------===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
On Tue, Sep 12, 2000 at 07:18:23PM -0700, Joey Hess wrote: > Glenn McGrath wrote: > > The 2.4 kernel can handle isa-pnp, so there shouldnt be problems with > > assigning irq and io value for isa-pnp network or sound cards which > > there are probably a fair few of. > > Two problems there: > > 1) I have a box that pnpdump locks solid. Ok, I haven't tried the new >kernel's detection, but I have my doubts. > 2) It's outside the domain of the installer to set up your sound card. >The only hardware the installer should care about is the hard drive, >whatever hardware is being used to install from (cd, ethernet), and >possibly CPU and memory. If we want a sound card detection thing, >someone can write it as a normal debian package that's not part of >the installer. The thing is, most of these autodetection libraries just do "detection, suggest module". They don't care whether it is an ethernet card or video frame grabber. There's no need to duplicate this just for sound (or whatever), and IMO it doesn't hurt to do it all at once. Makes the installer look more complete, as opposed to "Hey, it didn't detect my 'foo' card, why not?". There is no overhead in this, since it is just a matter of PCI ID's and module mappings. The PCI_ID->module mapping is already done for all modules. Not using it, doesn't save anything. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
On Tue, Sep 12, 2000 at 09:01:53PM -0700, Michael S. Fischer wrote: > On Tue, Sep 12, 2000 at 08:23:16PM -0700, Joey Hess wrote: > > > If the choice is between one floppy with minimal detection and two floppies > > with detection of everything, I want one floppy, every day. > > I'm with Joey on that. Still, though. After the main install is done, and the reboot complete, setting up the rest of the autodetection should be done in base-config, even if it simply calls dpkg-reconfigure or something. Let's plan for this from the installer, even if it isn't done till after install. Detecting hardware (all kinds, if possible) is part of the install process after all. -- ---===-=-==-=-------==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
On Wed, Sep 13, 2000 at 08:15:51PM -0700, Joey Hess wrote: > Adam Di Carlo wrote: > > That's true, but a more generalized point is that more and more > > hardware (sparc, ultrasparc, powerpc, dunno about the rest) support > > openfirmware or openboot, and it's possible to traverse the > > openfirmware device tree with pretty damn good results. > > I don't think libdetect knows anything about openfirmware. Do you know > of any hw detection code that does? Nope, but it would be nice to see such code. On the downside, most non-standard hardware supported by UltraSPARC Linux, doesn't have, nor need OpenPROM. If only Sun didn't require license/money/other crap for vendors to support their PROM :/ -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
On Thu, Sep 14, 2000 at 10:08:07AM -0400, Adam Di Carlo wrote: > Ben Collins <[EMAIL PROTECTED]> writes: > > > On Wed, Sep 13, 2000 at 08:15:51PM -0700, Joey Hess wrote: > > > Adam Di Carlo wrote: > > > > That's true, but a more generalized point is that more and more > > > > hardware (sparc, ultrasparc, powerpc, dunno about the rest) support > > > > openfirmware or openboot, and it's possible to traverse the > > > > openfirmware device tree with pretty damn good results. > > > > > > I don't think libdetect knows anything about openfirmware. Do you know > > > of any hw detection code that does? > > > > Nope, but it would be nice to see such code. On the downside, most > > non-standard hardware supported by UltraSPARC Linux, doesn't have, nor > > need OpenPROM. If only Sun didn't require license/money/other crap for > > vendors to support their PROM :/ > > Sure, although any bootable device by definition will support it. > > Sparcs and powerpc also have PCI support for the most part -- maybe > the focus should be just on PCI support. Then we could look at SBUS > on older sparcs as a sideline? Concentratin on PCI is the goal, IMO. SBUS device detection is overkill. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: redesigning the debian installer
Massimo Dal Zotto <[EMAIL PROTECTED]> writes: > > Massimo Dal Zotto wrote: > > > But if you want for example to install many similar machine from a cdrom > > > how can you specify which machine (hostname, ip, etc.) you are installing > > > without any prompting? > > > > DHCP > > This works if you have a network and a DHCP server. What if you have > only the cdrom? Home users usually don't have a server machine. Home users usually don't want to install many similar machines from a CD-ROM. -- "MONO - Monochrome Emulation This field is used to store your favorite bit." --FreeVGA Attribute Controller Reference -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: zen and debconf
> A couple of hours ago it hit me, we shouldnt be trying to invent the > wheel, we can use a web browser as the defualt user interface and a web > server as the backend (e.g. the kernel web server). Using html should > have a number of advantages in the tools available to use such as web > servers, proxies, remote backends, remote UI, debconf package scripts > developed as html. Debconf already supports a web interface, with it's own HTML generation and minimum server. IOW, debconf wont need apache, khttpd or any other web server, since it's all built-in (correct me if I misunderstand joey). -- ---===-=-==-=---======-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: zen and debconf
> If we are going to do anything fancy in our UI we could allow packages > to use there own html code to present there questions rather than > building a web page for them, this would add a large degree of > flexibility which i think is needed. The whole idea of debconf is to disconnect packages from the configuration frontend details. If we start asking them to produce HTML, we might as well ditch debconf and let them handle everything internally. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: zen and debconf
On Wed, Sep 20, 2000 at 02:53:28PM +1100, Glenn McGrath wrote: > Ben Collins wrote: > > > > > If we are going to do anything fancy in our UI we could allow packages > > > to use there own html code to present there questions rather than > > > building a web page for them, this would add a large degree of > > > flexibility which i think is needed. > > > > The whole idea of debconf is to disconnect packages from the configuration > > frontend details. If we start asking them to produce HTML, we might as > > well ditch debconf and let them handle everything internally. > > > > We shouldnt force them to use html, we could do the same thing the > current debconf does when it target a web browser (i have to confess i > havent tried it though) Check it out, it does have flexibility. You can group several questions together in a block, which can all be presented to the user on a single webpage. The block is set by the package, and is transparent to the UI being used (I think the GTK frontend also used to use it). I think joey says it needs work, but needing "work" is better then needing "development". An interface is there, it just needs to be used and tweaked. BTW, I like your idea, but I'm just afraid if we aren't careful, it will lead to a ggi type conundrum, where we have layers and layers of frontends all implementing each other. I want to avoid that by design. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which task package installs gpm?
>>>>> "Karl" == Karl M Hegbloom <[EMAIL PROTECTED]> writes: Karl> It would be good to check and see how powerful and loaded Karl> the machine is, and not start too much going at once if it's Karl> not that powerful. But if it can deal with it, we ought to, Karl> by default, start up `gkrellm', `xmms', and run a `gmix' to Karl> set some reasonable mixer defaults alsa. There ought to be Karl> an *.ogg in the XMMS when it's first time launched with a Karl> message from us. (Perhaps singing "(Join us now and) Free Karl> the Software" as a chorus? I believe we have a few Karl> musicians amoung our ranks.) If this is done, it might be nice to have XMMS default to using the esound output plugin; otherwise it takes control of the sound card and doesn't play well at all with GNOME. Ben -- Brought to you by the letters E and L and the number 8. "Tahiti is not in Europe." Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies 2.2.17 req'd packages
On Thu, Oct 05, 2000 at 07:36:30PM -0400, Adam Di Carlo wrote: > > Here's the list of pkgs from potato-porposed-updates which I used for > boot-floppies 2.2.17: > > base-config_0.33_i386.deb > debconf-tiny_0.2.80.17_all.deb > libc6_2.1.3-13_i386.deb > locales_2.1.3-13_i386.deb > makedev_2.3.1-46_all.deb > task-x-window-system-core_1.2_i386.deb > > Porters, please try to replicate this list. > > Porters, is anyone working on boot-floppies 2.2.17 for non-i386 ? I'll get sparc in the morning. I need to build new 2.2.17 kernel images too. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Priorities
> > Now, there are some related problems happening. One big one is the > fact that "Recommends" and "Suggests" have lost their usefulness > since apt-get came on the scene. I venture to suggest that several of > the inappropriate task-* packages exist purely to remedy this. If, > e.g., the Roxen maintainer could add appropriate recommendations and > suggestions, and feel that people would actually see them, he might > not have been inspired to build a task-webserver-roxen package. > I think the task-* packages can be solved pretty easily with some guidelines like: Task packages can define different levels of installation. The tasksel program will follow these rules for each case: - Minimum, installs everything that the task-* package Depends on - Standard, installs everything in Minimum, plus packages that it Recommends - Complete, installs all of the above plus packages that it Suggests Then a package such as task-ldap (since I know how LDAP might look) could do: Package: task-ldap Depends: ldap-utils Recommends: ldap-gateways, slapd Suggests: libnss-ldap, libpam-ldap Then in tasksel you choose minimum, standard or complete... Ben -- ---===-=-==-=========---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Priorities
On Mon, Oct 23, 2000 at 10:34:54AM -0400, Robert Funnell wrote: > On Mon, 23 Oct 2000, Ben Collins wrote: > > > ... > > Task packages can define different levels of installation. The > > tasksel program will follow these rules for each case: > > > > - Minimum, installs everything that the task-* package Depends on > > - Standard, installs everything in Minimum, plus packages that it > > Recommends > > - Complete, installs all of the above plus packages that it > > Suggests > > ... > > I've seen at least one package (I forget which) that recommended or > suggested alternate packages, from which one would normally choose one > only. Perhaps they could even be mutually incompatible. How would your > model handle this? I don't see how that is supposed to work. We have this syntax for such things: Depends: foo | bar | crap If things are really that similar and can replace each other, chances are there is a virtual package for it, or there should be. That also handles the case. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with libc6-pic
> /usr/bin/ld: /tmp/,mklibs.4082/lib-so: undefined versioned symbol name > [EMAIL PROTECTED] > /usr/bin/ld: failed to set dynamic section sizes: Bad value > collect2: ld returned 1 exit status > /usr/sbin/mklibs.sh: install-small-lib: gcc or objcopy failed. Oof, we saw this before, and I can't remember what the problem was. Can you check the archives for debian-boot and see if you can find it (Dec-1999, Jan-2000, Feb-2000, IIRC). Ben -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Patch: mklibs.sh for glibc 2.1.94
On Wed, Nov 08, 2000 at 02:38:45PM -0500, Jeff Licquia wrote: > I've been working on a project that requires building stripped-down > libraries, and was frustrated to discover the bug in mklibs.sh from > the current boot-floppies didn't work with the new glibc. Not wanting > to use potato for this task, I figured out and fixed the bug. > > (I realize that glibc has moved on since then; I'm sure it should be > obvious what I did, though, and updating it to reflect the current > situation should be a cinch.) > > I wasn't sure who to send the patch to, so I'm sending it here, in > hopes that it will make its way wherever it needs to go. Actually I'de like to see mklibs.sh rewritten to not need all this hardcoded version. For one, 2.1.94 is not even in Debian anymore (2.1.97 is the latest now), and 2.2.0 is coming very soon. To avoid all of this hardcoding for all possible versions, how about match things like 2.0.* 2.1.* and 2.2.*, or ever remove that all together? Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: OT: install from a live! cdrom
On Tue, Nov 28, 2000 at 09:38:59PM +0800, zhaoway wrote: > There're already 2-3 versions of modified Debian system runs directly > on CDROMs, i.e. Live! CDROMs. ;-) AFAIK, one is Gibraltar, a firewall > project, a read-only system is interesting in this place; the other is > DemoLinux, as the name suggests; the third maybe is from bootcd Debian > package, which copies a normal Debian system to the CDROM, and runs > there. > > Will the debian-installer be capable of installing from a Live! CDROM > system to the harddisk. i.e. not copying from .debs but copying from a > running system. And the result be the same as install the normal way > to the user. (Forgive my English.) The SPARC/UltraSPARC CD's boot from a live iso9660 filesystem. Although it is still limited to the mini-tools found on the root disk of a normal install. Joey, are there plans to support a broader range of tools on a live CD image with the new project? I never thought about it during all the discussion, but it would be nice to have a CD image that uses normal .deb tools (fileutils, vim, emacs for the insane, perhaps a compiler, a larger set of recovery tools, etc..). Ben -- ---===-=-==-=====---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dbootstrap: understanding is_cdrom_image
> The problem here is that when the user select "install XXX from
> CD-ROM", I want an accurate test of whether or not this is an official
> CD-ROM or not. Which *doesn't* rely on the bootargs to be set
> correctly.
That's not what I wrote the function for. So if you need that, use
something else, or add another return value. I say this because certain
things in debian-cd rely on this working properly, so I hope that nothing
will be messed with, since it may unknowingly affect debian-cd.
> Apparently non-zero return values means its some sort of CD-ROM
> ismage. I would presume that '2' represents booting from a CD-image
> (thus we have /dists). What I need is something like:
>
> if (NAME_ISREG("/cdrom_image",&statbuf) || bootargs.cdrom) {
> if (NAME_ISDIR("/dists",&statbuf))
> return 2;
> else
> return 1;
> } elsif (NAME_ISREG("/instmnt/.disks/info") {
> return 1;
> } else
> return 0;
>
> Does this seem correct?
You are missing the point of my function. It is meant to test if we are
booting from a cdrom. Your check is something completely different. Might
be better to make a new test just for your purposes, rather than risk
messing up the current function.
Ben
--
---===-=-==-=---==-=--
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dbootstrap: understanding is_cdrom_image
On Mon, Dec 04, 2000 at 04:01:15PM -0500, Adam Di Carlo wrote: > Ben Collins <[EMAIL PROTECTED]> writes: > > > You are missing the point of my function. It is meant to test if we are > > booting from a cdrom. Your check is something completely different. Might > > be better to make a new test just for your purposes, rather than risk > > messing up the current function. > > Ok, ok. No need to get annoyed -- a little nominal documentation or > comments would help. Sorry, didn't mean to be harsh. > Then please explain what the return values 1 and 2 are supposed to > represent? 1 means "we booted off of a debian CD using a floppy image style bootup. so we need to mount a cdrom for the install source", which is the way i386 and similar boot. 2 means "we booted off of a Debian CD with the actual CD as the filesystem, so we don't need to mount anything, we just use the files right off the root filesystem under /dists". This is the way sparc cd images are. With this method, there are no questions about the source of the packages, because the installer just knows where to get them, and does it without question (unless you have the verbose boot option set). Maybe I can use some #defines for constants to make this easier to understand. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#79004: SPARC/Potato] 'Wrong disk' message even though correct disk in drive
> - s n i p - > Wrong disk! > This is disk 1 of 2 in the drv14-sun4cdm series of 27-Nov-2000 13:18 EST. > Wrong disk. This is from series drv14-sun4cdm. You need disk 1 of series > the driver series. > - s n i p - > > The machine is a SPARC station 1+ (a sun4c arch). I'm fairly certain this is not a sparc issue, or atleast that it has nothing to do with anything I changed. For the latest set, I just used a newer kernel, and the latest boot-floppies source. Ben -- ---===-=-==-=---======-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#79004: SPARC/Potato] 'Wrong disk' message even though correct disk in drive
On Fri, Dec 08, 2000 at 03:57:40PM +0100, Turbo Fredriksson wrote: > Quoting Adam Di Carlo <[EMAIL PROTECTED]>: > > > You said the message was: > > > > > > > > > > Wrong disk! > > > > > This is disk 1 of 2 in the drv14-sun4cdm series of 27-Nov-2000 13:18 EST. > > > > > Wrong disk. This is from series drv14-sun4cdm. You need disk 1 of series > > > > > the driver series. > > > > However, that's not possible that that was the message, looking at the > > code. I need the literal message that was printed. The output should > > also be in /var/log/messages, if you are able to cat that to a floppy > > and copy it over. > > Well, that IS the (exact!) literal message that I got. I tripple checked it... > > The 'drv14-sun4cdm' and the '27-Nov-2000 13:18 EST' it gets from the disk. But > where it gets 'series the driver series' from I have no idea.. Adam, could this have to do with the fact that sparc only has one driver image, and not multiple? -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: doc/ISSUES - possible fix for ramdisk issue
On Tue, Dec 19, 2000 at 09:34:14AM +0100, Tollef Fog Heen wrote: > > However, I'm just curious about what happens when the ramdisk grows to > over free ram size.. > A quick look at the ramfs source (only one file) shows that it will return ENOSPC on a full fs. I'm not sure how much free ram it will take up trying to get full. Also, ramfs is a 2.4.x only feature. Hopefully we are releasing with 2.4.x anyway. -- ---===-=-==-=---=--------=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: BOGL based frontend for cdebconf
Daniel Jacobowitz <[EMAIL PROTECTED]> writes: > I've begun designing a BOGL based frontend for cdebconf. I've not actually > got anything useful yet, but I plan to take the project home with me over > break; I'll see how it goes. > > In order to do this, though, I need to separate BOGL out from boot-floppies. > Ben, would you mind if I packaged it for the main archive? Go ahead, be my guest. I haven't had time to work on BOGL or boot-floppies in over a year. I'd be happy to have someone use the code. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#79004: SPARC/Potato] 'Wrong disk' message even though correct disk in drive
On Wed, Jan 03, 2001 at 03:05:28AM -0800, rick wrote: > > Note that this is only a workaround. The real fix is to have the > "dbootstrap" program > accept a platform-specific qualifier (e.g, the "-sun4cdm") in the floppy > series name. > This qualifier would have to come from a command-line argument specified > in a > platform-specific "/etc/inittab". Or, if the goal is to maintain a > single root floppy for > all platforms, from the platform-specific kernel (e.g, via the "/proc" Well, it used to, so something broke since the last time I built the images. Thanks for the workaround. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FW: Right SPARC 2.2.20 floppies on the Debian web site?
On Thu, Jan 04, 2001 at 01:10:59PM -0800, McClanahan, David K wrote: > > P.P.S. When Linux starts up, at the boot prompt, SILO reports that this > floppy contains the 2.2.18pre21 kernel, which does not match the 2.2.20 > the download said it was. > 2.2.20 is the version of the boot-floppies, 2.2.18pre21 is the version of the kernel. > -Original Message- > From: McClanahan, David K > Sent: Tuesday, January 02, 2001 5:34 PM > To: '[EMAIL PROTECTED]' > Subject: RE: Right SPARC 2.2.20 floppies on the Debian web site? > Importance: High > > > P.S. I have re-downloaded the 2.2.20 (potato) floppies from the Debian FTP > site and have found the following situation. > > When I boot with the floppies I created from the rescue.bin and root.bin > image file, the install procedure asks for the "driver disk 1", after the > disk partitioning, to install software. When I put in the disk made from > the driver-1.bin image I get: > > "This is disk 1 of 2 in the drv14-sun4cdm series of > 27-Nov-2000 13:18 EST. > Wrong disk. This is from series drv14-sun4cdm. > You need disk 1 of series the driver series. ". > > Where upon it once again asks me to insert "driver disk 1". > > Are the right floppy images loaded on the FTP site? This is a bug in the dboostrap program. I am going to fix it this evening and get a new set of boot-floppies uploaded. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#81343: libc thread code problem in Debian Linux 2.2.17, i686
On Fri, Jan 05, 2001 at 04:12:58PM -0700, Gerry Wiener wrote: > Package: base > > Linux amber 2.2.17 #1 SMP Thu Sep 7 11:35:24 MDT 2000 i686 unknown > > I initially reported the bug below to the Python 2.0 bug list. The > author of Python responded by mentioning that he thinks it is a > problem with the libc thread code. I wanted to make sure the bug was > reported. I just ran your test program on sparc and i386 (bothing running unstable, both also using 2.4.0-test/2.4.0 kernels) and this was the output: %./testsys.py testing system hello there hello there hello there hello there hello there hello there hello there hello there hello there hello there ret is 0 I then went back and tested with a glibc 2.1.3 system (sparc and i386) and saw your error results. So, the problem is resolved with the latest glibc 2.2. -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FW: Right SPARC 2.2.20 floppies on the Debian web site?
On Sun, Jan 07, 2001 at 10:51:41PM -0500, Adam Di Carlo wrote: > Ben Collins <[EMAIL PROTECTED]> writes: > > > This is a bug in the dboostrap program. I am going to fix it this > > evening and get a new set of boot-floppies uploaded. > > Hmm, ok, well, if you wanna release and upload sources for 2.2.21 > that's alright with me. My personal testing indicates that version is > ok. I have a few more things I wanna fix for i386, however, before I > do a release I didn't want to risk adding new stuff, so I just made the changes, commited it to CVS (one-liner), and compiled a new set, in incoming now. -- ---===-=-==-=====---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: breaking up base-config
On Tue, Jan 09, 2001 at 06:46:38PM -0800, Joey Hess wrote: > > I would actually like to start with moving the password/new > user/shadow/md5 stuff out into passwd or some other appropriate package, > if Ben is willing. After that I'd be happy to unload the apt setup > stuff, and the rest of the list. > I'll get working on this between now and next week. -- ---===-=-==-=---======-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: breaking up base-config
On Tue, Jan 09, 2001 at 09:51:50PM -0800, Joey Hess wrote: > Ben Collins wrote: > > On Tue, Jan 09, 2001 at 06:46:38PM -0800, Joey Hess wrote: > > > > > > I would actually like to start with moving the password/new > > > user/shadow/md5 stuff out into passwd or some other appropriate package, > > > if Ben is willing. After that I'd be happy to unload the apt setup > > > stuff, and the rest of the list. > > > > > > > I'll get working on this between now and next week. > > I can send you the templates (including translations) base-config uses > now, and I could even rip out the relevant code and give you a .config > script that might sorta work if that would help. > > The annoying thing about the password prompting is that if you do it > cleanly and prompt for the passwords in the config script, then set them > in the postinst, there is a window where debconf writes them to disk. So > base-config does it all in the config script, and makes sure they are > never written out. Which is ugly. I don't know how you want to handle > that. Another option would be to prompt for the passwords in the > postinst. Sure, send them over. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: busybox insmod
On Thu, Jan 25, 2001 at 08:54:04PM -0700, Randolph Chung wrote: > > I'd love to. There is one little problem. Or rather, there are several > > little problems, specifically, alpha, hppa, m68k, mips, ppc, and sparc. > > Busybox insmod requires a little bit of arch specific code for each > > arch. So far, only x86, arm, and sh are supported. So if I turn it on, > > I will get nasty emails from the autobuilders saying: > > #error Sorry, but insmod.c does not yet support this architecture... > > is this arch-specific code we can "borrow" from some place? modutils. I really hope no one tries to reproduce insmod in busy box. The code for the 32bit/64bit support in one binary is hellish enough to keep working in one modutils package, let alone trying to ensure it works in busybox too. How about just make modutils create a udeb? -- ---===-=-======-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: busybox insmod
On Thu, Jan 25, 2001 at 08:45:03PM -0800, David Whedon wrote: > I'll start making a udeb of modutils, since that looks like where this is > heading, okay? How about filing a bug on modutils to do this? I'm sure wichert would be happy to add the udeb support in the main modutils package, where it would be much easier to maintain. Plus it means main modutils stays in sync with udeb insmod. -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
what is the whole purpose of kernel-image-di?
I'm sitting here looking at an obvious build failure for kernel-image-di on the sparc buildd, and I'm wondering what the heck this package is for anyway. I mean, is this thing supposed to be portable? If it is, it sucks at doing so, and if it's not, then is it the intention that non-i386 is left out of this loop? Are the debinst folks not even considering non-i386 ports during this development process? Am I going to have to go through all of the installer and hack it to bits to make it work on sparc, just as I had to do with boot-floppies, or is debian-installer being developed so that all I have to do is create a boot-block installer, and a set of kernel-image*.udeb packages to get it working on sparc? I'm very concerned that portability is becoming an afterthought. -- ---===-=-==-=---=----=-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what is the whole purpose of kernel-image-di?
On Wed, Feb 07, 2001 at 02:12:43PM +1100, Glenn McGrath wrote: > Ben Collins wrote: > > > > I'm sitting here looking at an obvious build failure for > > kernel-image-di on the sparc buildd, and I'm wondering what the heck > > this package is for anyway. I mean, is this thing supposed to be > > portable? If it is, it sucks at doing so, and if it's not, then is it > > the intention that non-i386 is left out of this loop? > > > > Are the debinst folks not even considering non-i386 ports during > > this development process? Am I going to have to go through all of the > > installer and hack it to bits to make it work on sparc, just as I had to > > do with boot-floppies, or is debian-installer being developed so that > > all I have to do is create a boot-block installer, and a set of > > kernel-image*.udeb packages to get it working on sparc? I'm very > > concerned that portability is becoming an afterthought. > > > > Network install to a i386 was/is the initial focus of development, but > the modular nature of d-i should make it easy(or easier) to overcome any > difficulties with a specific architecture, or even a different type of > kernel (native Hurd install). I can understand it being the first milestone, but it seems to be the only focus, and nothing is being considered as to how it affects other ports. > Probably a lot of people (me included) arent aware of the difficulties > of specific architectures, can you go into a bit of detail about what > kernel config doesnt work for sparc ? For sparc, there has to be atleast two different boot kernels. One for sun4cdm (32bit CPU), and one for sun4u (64bit CPU). SPARC also supports native netbooting (via RARP/TFTP). My main concern is whether or not it is being documented as to how other ports need to handle getting the installer working for it. Is there a checklist of what a port needs in order to have support in the installer, such as a minimum of required packages (boot loader setup, kernel-images, etc.)? Note, every arch is different, which was the main reason for so much speciality and hacking in the boot-floppies. It's held together by ducktape and string. Have the issues involved in the boot-floppies struggle with multi-platform support been brought into consideration of the debinst design? > To answer your last question specifically, portability isnt an > afterthought, its part of the design due to modularity. Sorry, but modularity does not beget portability. This assumption will end up biting us in the ass later, if it is the only premise for "portability". -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what is the whole purpose of kernel-image-di?
On Wed, Feb 07, 2001 at 06:34:59AM +0200, Eray Ozkural (exa) wrote: > Ben Collins wrote: > > > > For sparc, there has to be atleast two different boot kernels. One for > > sun4cdm (32bit CPU), and one for sun4u (64bit CPU). SPARC also supports > > native netbooting (via RARP/TFTP). My main concern is whether or not it > ^ > > One of the things we should be working out. I sweated for quite a few hours > to get my second i386 box netboot. It would be great if we could > have the system use netboot on platforms where it's possible. The installer does not need to directly support net booting, atleast not on sparc. All it needs is for the rootfs image, and a kernel image. Then it boots the same as if it were an initrd. However, creating this needs to be done somehow, and done from a scripted setup (IOW, in a reproducable way). -- ---===-=-==-=========---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian-installer status report
> But there has been only some activity on sparc, mipsel, alpha, m69k > (amiga), and s390; and little or progress on hppa, arm, various m68k > subarches, and many less common powerpc subarches; and many of these > architectures are nowhere near working. FYI, after I fix some SILO issues this weekend, I am going to finish the work on debian-installer for sparc. My biggest problem has been the size of recent kernels causing SILO to choke (an old legacy 3.5Meg limit on uncompressed kernel sizes). Once that's resolved, it will make sense for me to get working images out. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#154064: (no subject)
I'm seeing this same problem on an Axil 235 (sun4m). Nothing happens when I hit Return after the "Insert root floppy disk..." message. Booting "linux debug" doesn't show anything useful. Net-boot installation works, though. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: help with modulils for sparc64 debian-installer
On Sun, Feb 08, 2004 at 06:35:21PM -0800, Blars Blarson wrote: > I'm trying to figure out why depmod, insmod, and modprobe are give the > error that the sparc64 kernel modules are not for this architecture on > my latest d-i boot cds. I'm using the ones in the modutils-full udeb, > uname -m reports sparc64, and they match the kernel version. (The > busybox version is known not to work for sparc64.) > > I tried setting the enviornment UNAME_MACHINE to sparc64 and that > didn't help. No idea. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: help with modulils for sparc64 debian-installer
On Mon, Feb 09, 2004 at 10:48:42PM -0800, Blars Blarson wrote: > On Sun, Feb 08, 2004 at 06:35:21PM -0800, Blars Blarson wrote: > > I'm trying to figure out why depmod, insmod, and modprobe are give the > > error that the sparc64 kernel modules are not for this architecture on > > my latest d-i boot cds. I'm using the ones in the modutils-full udeb, > > uname -m reports sparc64, and they match the kernel version. (The > > busybox version is known not to work for sparc64.) > > It wound up busybox was insisting on using it's internal versions > despite the corrent binaries being in /sbin. I'm rebuilding busybox > now with modutils disabled. > > > I tried setting the enviornment UNAME_MACHINE to sparc64 and that > > didn't help. > > Further examination and experimentation showed the (undocumented?) > UNAME_MACHINE feature of modutils is broken as well. sparc64 depmod The sparc64 command will for uname=sparc64. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sparc d-i status
On Tue, Feb 24, 2004 at 08:21:18AM -0800, Jeff Bailey wrote: > On Tue, Feb 24, 2004 at 04:22:34PM +0100, Thomas Poindessous wrote: > > > > I also remember (was it Thomas? Blars? hmmm...) mentioning that the > > > fdisk udeb wasn't getting loaded for some reason. I'm hoping that the > > > whole partman thing will make this silently go away before we get there. > > > > in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is > > no support for sparc in partitioner ( bug #228518). > > Lovely! I've applied the patch in 228518 to CVS and marked it pending. > (It obviously still needs fdisk-udeb). > > Hmm... Why don't we just use parted for now, until a better solution > comes around? It's in the archive, and AFAICT supports Sparc. (ia64 > uses it right now, too) I know it supports sparc. I worked a long time ago to get the sun partition support into that. > > we also need a silo-installer > > Right. Any takers? =) Obviously, that's a "me" :) -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sparc d-i status
On Tue, Feb 24, 2004 at 07:14:50PM +0100, Sven Luther wrote: > On Tue, Feb 24, 2004 at 11:26:06AM -0500, Ben Collins wrote: > > On Tue, Feb 24, 2004 at 08:21:18AM -0800, Jeff Bailey wrote: > > > On Tue, Feb 24, 2004 at 04:22:34PM +0100, Thomas Poindessous wrote: > > > > > > > > I also remember (was it Thomas? Blars? hmmm...) mentioning that the > > > > > fdisk udeb wasn't getting loaded for some reason. I'm hoping that the > > > > > whole partman thing will make this silently go away before we get there. > > > > > > > > in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is > > > > no support for sparc in partitioner ( bug #228518). > > > > > > Lovely! I've applied the patch in 228518 to CVS and marked it pending. > > > (It obviously still needs fdisk-udeb). > > > > > > Hmm... Why don't we just use parted for now, until a better solution > > > comes around? It's in the archive, and AFAICT supports Sparc. (ia64 > > > uses it right now, too) > > > > I know it supports sparc. I worked a long time ago to get the sun > > partition support into that. > > Oh, you did write that ? I inspired myself from it when doing the amiga > partition table support. Thanks then, altough it was mostly casuality > which made me print the disk_sun.c file instead of another one. Well, I copied it from some other file, so the benefits are just being passed around :) -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sparc d-i status
On Wed, Feb 25, 2004 at 12:23:34AM -0500, Jeff Bailey wrote: > On Tue, 2004-02-24 at 11:26, Ben Collins wrote: > > > > Hmm... Why don't we just use parted for now, until a better solution > > > comes around? It's in the archive, and AFAICT supports Sparc. (ia64 > > > uses it right now, too) > > > I know it supports sparc. I worked a long time ago to get the sun > > partition support into that. > > Nice! > > > > > we also need a silo-installer > > > > > > Right. Any takers? =) > > > > Obviously, that's a "me" :) > > Actually, I had been hoping that since we have grub-installer to model > after, this should be in the category "things anyone who cares about > Sparc" can do, as opposed to the "benc and davem are the only ones with > a clue how to fix this" category... =) Your call, though. Not sure what this has to do with Dave, but it's in the category of "I'm the silo maintainer, let me handle it, rather than letting someone else do it and end up asking me tons of questions or not getting it right the first time". -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Minor update to 5.2, Choosing the Right Installation Set
http://www.debian.org/releases/stable/i386/ch-install-methods.en.html: "The `vanilla' flavor includes one Rescue Floppy, one root and three Driver Floppies." At least as of 2.2r5, the vanilla set include four driver floppies (at 1.44MB each), not three. Regards, Ben Ostrowsky -- "The Sumerians wrote by pressing the tip of a hollow reed into wet clay tablets which were then preserved by baking. Masses of these survive from those remote days. Computer punchcards from the Sixties largely do not." -- Kaplan, _The Nothing That Is_ (NYT Acrostic, 3/25/2001) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#131709: chroot segfaults
On Thu, Jan 31, 2002 at 10:09:13AM -0500, Rich Johnson wrote:
> package: boot-floppies
> version: 3.0.18
> architecture: powerpc
> model: Mac 8500 /132 ("old world" firmware)
> memory: 32M
> scsi: on-board
> cd-rom:apple, scsi interface
>
> Manually invoking root.bin's "/usr/sbin/chroot /target " from the
> installer's shell always segfaults.
>
> Perhaps this explains the "Failure trying to run : chroot /target dpkg"
> encountered while installing the base system.
Does it segv before or after it chroots? It may be that that it is
trying to execute is segv'ing, and that would be an important bit of
information.
Ben
--
.--===-=-==-=---==-=-.
/ Ben Collins--Debian GNU/Linux--WatchGuard.com \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: initrd extends beyond end of memory
On Thu, Jan 31, 2002 at 02:43:53PM -0300, [EMAIL PROTECTED] wrote: > ¡Hola! > > I'm having problems trying to install debian in my notebook. It has no > cdrom, no bootable floppy drive. So i'm using the booting from DOS > approach. > > When it boots it displays: > > initrd extends beyond end of memory (0xc1d8 > 0xc1d0) > disabling initrd > > What can i do ? How much memory do you have? -- .--===-=-==-=====---==-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: initrd extends beyond end of memory
On Thu, Jan 31, 2002 at 03:07:02PM -0300, [EMAIL PROTECTED] wrote: > ¡Hola! > > > > I'm having problems trying to install debian in my notebook. It has no > > > cdrom, no bootable floppy drive. So i'm using the booting from DOS > > > approach. > > > > When it boots it displays: > > > > initrd extends beyond end of memory (0xc1d8 > 0xc1d0) > > > disabling initrd > > > > What can i do ? > > > How much memory do you have? > > 32Mb (i've installed earlier versions of debian in this box) Check the syslinux script on the DOS disk, and see what it passes to lilo for ramdisk= Ben -- .--===-=-==-=---==-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: initrd extends beyond end of memory
On Thu, Jan 31, 2002 at 03:19:23PM -0300, [EMAIL PROTECTED] wrote: > ¡Hola! > > > > > > So i'm using the booting from DOS > > > > > approach. > > > > > > initrd extends beyond end of memory (0xc1d8 > 0xc1d0) > > > > > disabling initrd > > > > > > What can i do ? > > > > How much memory do you have? > > > 32Mb (i've installed earlier versions of debian in this box) > > > Check the syslinux script on the DOS disk, and see what it passes to > > lilo for ramdisk= > > I'm using: > > loadlin linux root=/dev/ram initrd=root.bin Isn't there a batch script that passes all the commands? (been awhile since I DOS booted a PC, so remind me :) You could try adding "ramdisk=8000" to that. Ben -- .--===-=-==-=---==-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#131709: [rjohnson@dogstar-interactive.com: Re: Bug#131709: chroot segfaults]
- Forwarded message from Rich Johnson <[EMAIL PROTECTED]> -
X-Virus-Scanner: McAfee Virus Engine
X-Spam-Status: Scanner Called
X-Sent: 2 Feb 2002 15:14:43 GMT
From: Rich Johnson <[EMAIL PROTECTED]>
To: Ben Collins <[EMAIL PROTECTED]>
Subject: Re: Bug#131709: chroot segfaults
X-Spam-Status: No, hits=0.0 required=6.5 tests= version=2.1
Rich Johnson wrote:
> I poked around a bit more. I've distilled some of the results below/
>
> The machine state is the result of:
> 1) booted from floppies (mac_hfs_boot, root.bin)
> 2) downloaded kernel & drivers from ftp.us.debian.org
> 3) downloaded base .debs from ftp.us.debian.org
> 4) extracted base .debs from ftp.us.debian.org
> 5) installation of base .debs failed with "Failure trying to run : chroot
> /target dpkg"
>
Ben--
I did still more digging--i.e. lots of reboots and manual invocations of .
Here's a report to pass on to the appropriate folks--perhaps it's a or
issue?
a) runs fine intslling the first few 's
b) start's failing with
c) the system would also hang--such that does't work; sometimes even
didn't work.
d) fsck after a forced reboot invariably showed several cross-linked files--almost
always in /usr/share/zoneinfo.
This indicates that the 3000 or so files indicated by "$(debfor required)" overstresses
. Hanging also indicates falling into an infinite loop somewhere; perhaps a
corrupted linked list or hash table?
I was able to install all the packages by rewriting install_subs() to "unwind" the
installation such that was invoked on a _single_ packages at a time. Experience
with cross-linked files also caused me to defensively put a after every .
The modified script ran to completion. This supports the hypothesis of an overstressed
.
I replaced the two lines with loops. Running each loop once left nothing
more to do. The seemed superfluous, but I may be missing some subtleties .
Here's the modified fragment (sorry, no diff's yet--I'm still configuring the system):
<...snip...>
for rdeb in ${required}; do
in_target dpkg --force-depends --unpack $(debfor $rdeb)
sync
sleep 3; #--throttle to give time to scan results.
done
<...snip...>
for bdeb in ${base}; do
in_target dpkg --force-auto-select --force-overwrite --force-confold
--skip-same-version --install $(debfor $bdeb)
sync
sleep 3#--throttle to give time to scan results.
done
in_target dpkg --configure --pending --force-config-any --force-depends
#--walk through
That's all for now...on to XBoot and finishing my configuration
--rich
- End forwarded message -
--
.--===-=-==-=---==-=-.
/ Ben Collins--Debian GNU/Linux--WatchGuard.com \
` [EMAIL PROTECTED] -- [EMAIL PROTECTED] '
`---=--===-=-=-=-===-==---=--=---'
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: e2fsprogs 1.26
On Mon, Feb 04, 2002 at 10:39:25AM +0100, Yann Dirson wrote: > e2fsprogs 1.26 is out, including fixes for one but tagged important, > ext3-related fixes, reiserfs support in fsck, and more complete > support for filesystems in >2GB files. > > I suppose it is too late to get this one in base, so I can package it > in an e2fsprogs-1.26 package if needed. However, it would probably be > better if it could go in base... What do boot-floppies and release > manager think ? > > Full list of changes at > http://sourceforge.net/project/shownotes.php?release_id=73260 If it is really that important, raise the severity of the bug, and we will certainly have to fix it for release. -- .--===-=-==-=---======-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: e2fsprogs 1.26
On Mon, Feb 04, 2002 at 05:41:11PM +0100, Yann Dirson wrote: > On Tue, Feb 05, 2002 at 02:07:43AM +1000, Anthony Towns wrote: > > On Mon, Feb 04, 2002 at 10:39:25AM +0100, Yann Dirson wrote: > > > e2fsprogs 1.26 is out, including fixes for one but tagged important, > > > ext3-related fixes, reiserfs support in fsck, and more complete > > > support for filesystems in >2GB files. > > > > > > I suppose it is too late to get this one in base, so I can package it > > > in an e2fsprogs-1.26 package if needed. However, it would probably be > > > better if it could go in base... What do boot-floppies and release > > > manager think ? > > > > Am I correct in thinking that e2fsprogs doesn't provide any shared > > libraries > > wrong - packages depending on the libs, from memory: dump, mc, some > undeletion progs, maybe other things. > > > Assuming that's the case... > > So I suppose it won't be OK, then... better provide an alternative > package ? Better to not provide an alternative. It would be useless. Fsck is run from automated scripts, so no-one would get the fixes without a lot of mucking around. Ben -- .--===-=-==-=---==-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: e2fsprogs 1.26
On Mon, Feb 04, 2002 at 06:11:27PM +0100, Yann Dirson wrote: > On Mon, Feb 04, 2002 at 12:01:12PM -0500, Ben Collins wrote: > > > So I suppose it won't be OK, then... better provide an alternative > > > package ? > > > > Better to not provide an alternative. > > Woops, wrong wording :) Sure ! > Replaces/Conflicts/Provides /broken versioned deps on lib packages/ Seems it would just break things, more than solve them. -- .--===-=-==-=---==-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re-runnability of operations modifying ram rootfs
Please CC me on replies, as I am not on this list.
To what extent is it a goal to make the installation steps
rerunnable?
I have noted while testing the woody boot floppies that some
steps that intuitively one would not think need repeating
actually do. Namely, the install OS & drivers step. Since
boot-floppies/scripts/drivers/install.sh creates five symlinks
in the ramfs, it makes it necessary to reinstall the drivers
if the install is interrupted for any reason and restarted
from the beginning. As a naive user, I expected that all that
installing the OS & drivers did was to populate /target. Not
so. When I examined the drivers script, I found this:
test -f /bin/sed || ln -sf `pwd`/bin/sed /bin/sed
test -f /usr/bin/whiptail || ln -sf `pwd`/usr/bin/whiptail /usr/bin/whiptail
if [ -e ${FLOPPY}/pcmcia.tgz ]; then
zcat ${FLOPPY}/pcmcia.tgz | tar -x
ln -sf `pwd`/sbin/ifport /sbin/ifport
ln -sf `pwd`/sbin/ifuser /sbin/ifuser
ln -sf `pwd`/sbin/cardmgr /sbin/cardmgr
fi
So if I start the install, encounter a problem, then restart
it, I know I need to:
- reset the keyboard map
- turn swap back on
- remount the root partition
- reset the host name
- reconfigure PCMCIA
- reconfigure the network ...
But in the last couple of steps, I start getting errors (logged on vt3)
because, for instance, cardmgr isn't found. The problem here is I never
expected I'd have to repeat the (lengthy) reinstall of the rescue and
drivers disks upon restarting the install. I figured they were there
on my hdd already, so I needn't bother doing it over again.
What if these symlinks were saved as they were performed via a small
helper script:
save ln -sf `pwd`/sbin/ifport /sbin/ifport
etc.
'save' would perform the command immediately but also append the
command to /target/tmp/save.sh
Then, in the event that the install is interrupted and restarted from
the beginning, upon remounting /target, /target/tmp/save.sh could be
executed to redo these saved steps.
Each step written to save.sh should be idempotent. If someone
installs the drivers multiple times, it should not matter that
multiple ln -sf's are appended to save.sh.
If something like this is not done, at the very least the user should
be notified that they need to rerun a step before they can proceed.
As it is, the user is left in the dark.
Ben
--
nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED]
Debian http://www.debian.org [EMAIL PROTECTED]
[ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ]
[ gpg key fingerprint = 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alpha and sparc boot-floppies
> > Be aware that if alpha and sparc boot-floppies aren't uploaded in a timely > fashion (and 3.0.19 hasn't been), then any bugfixes y'all may need before > release just plain won't be happening. > Will do for sparc tonight. -- .--===-=-==-=---======-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#132671: sparc disks outdated
On Sat, Mar 02, 2002 at 11:59:24PM +0100, Eduard Bloch wrote: > #include > Phil Blundell wrote on Thu Feb 14, 2002 um 02:22:27PM: > > The latest sparc boot-floppies in woody are 3.0.16 from back in October. > > Bug 132671 looks like it might be fixed by just building against a new > > kernel image. > > > > Is anyone on the list in a position to build a new set of disks? > > Okay, did anyone try to reproduce this problem with a fresh build from > CVS? > > If nobody wants to build BFs for Sparc, we should just downgrade > severities of their bug reports. > Uh, someone is building boot-floppies for sparc, we've just been waiting for a decent kernel to use. -- .--===-=-======-=---==-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#132671: sparc disks outdated
severity 132671 serious thanks > thanks > > #include > Ben Collins [DPL] wrote on Sat Mar 02, 2002 um 08:06:36PM: > > > > If nobody wants to build BFs for Sparc, we should just downgrade > > > severities of their bug reports. > > > > > > > Uh, someone is building boot-floppies for sparc, we've just been > > waiting for a decent kernel to use. > > Since you are waiting for months, we define the issue is not important > enough for beeing RC. Since you don't maintain the sparc boot disks, I suggest you leave it alone. -- .------===-=-==-=---==-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3.0.20 is in build
On Sun, Mar 03, 2002 at 07:33:04PM -0500, Adam Di Carlo wrote: > > Boot-floppies 3.0.20 is in the process of being built. Thanks to > everyone that has been working on this, and that does *not* include > me, unfortunately. However, my time is easing a little bit now so I > should be able to get back and help coordinate the final woody > boot-floppies Excellent. I'll start my new builds using this version (for sparc) -- .--===-=-==-=---=--------=-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies 3.0.21 for testing
On Thu, Mar 14, 2002 at 04:58:11PM -0500, Dave Baker wrote: > On Thu, Mar 14, 2002 at 01:50:56PM -0800, Joshua Uziel wrote: > > * Dave Baker <[EMAIL PROTECTED]> [020314 13:42]: > > > The sun4u kernel-config is missing CONFIG_ROOT_NFS and CONFIG_NFSD_TCP, > > > both of which are present in sun4cdm. I believe this omission causes a > > > network install to be impossible on a sun4u machine (though if I'm > > > mistaken I'd be very happy to hear what I'm doing wrong). > > > > Well, it'll break an NFS install, sure... but a network install works > > fine. I did one on an AX1105 just a little while ago (UltraSPARC-IIe). > > > > I chose my words poorly. My machines generally don't have floppy or cdrom > installed, so my network install is network (bootp, tftp, nfs) from start > to end. Why both with nfs when the tftpboot.img has all you need? Just required tftp+rarp. As for the nfs options, I'll get them fixed in the next kernel upload. -- .--===-=-==-=---==-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Processed: reassign 138715 kernel-image-2.4.16-sun4u
On Sun, Mar 17, 2002 at 06:03:12AM -0600, Debian Bug Tracking System wrote: > Processing commands for [EMAIL PROTECTED]: > > > reassign 138715 kernel-image-2.4.16-sun4u > Bug#138715: [b-f sparc] sun4u floppies freeze at boot > Bug reassigned from package `boot-floppies' to `kernel-image-2.4.16-sun4u'. Fixed in 2.4.18 images. -- .--===-=-==-=---=--------=-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Processed: reassign 138542 kernel-image-2.4.16-sun4u
On Sun, Mar 17, 2002 at 06:03:14AM -0600, Debian Bug Tracking System wrote: > Processing commands for [EMAIL PROTECTED]: > > > reassign 138542 kernel-image-2.4.16-sun4u > Bug#138542: Sparc boot-floppies: TFTP boot failure > Bug reassigned from package `boot-floppies' to `kernel-image-2.4.16-sun4u'. Fixed in 2.4.18 images. -- .--===-=-==-=---=--------=-=-. / Ben Collins--Debian GNU/Linux--WatchGuard.com \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Processed: re: [b-f sparc] enable fs other than ext2
reassign 139418 boot-floppies thanks On Fri, Mar 22, 2002 at 12:33:07AM -0600, Debian Bug Tracking System wrote: > Processing commands for [EMAIL PROTECTED]: > > > reassign 139418 kernel-image-sparc-2.4 > Bug#139418: Fwd: Re: heavy problems installing woody on a brand new iBook > Bug reassigned from package `boot-floppies' to `kernel-image-sparc-2.4'. > I have no idea what you are attempting to do, but that does an iBook install problem have to do with sparc kernel images? -- .--==-====----=-=-. / Ben Collins--Debian GNU/Linux \ ` [EMAIL PROTECTED] ' `---=-----==-===---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Processed: re: [b-f sparc] enable fs other than ext2
On Fri, Mar 22, 2002 at 09:40:54AM +0100, Eduard Bloch wrote: > Package: kernel-image-sparc-2.4 > Severity: wishlist > > #include > Ben Collins [DPL] wrote on Fri Mar 22, 2002 um 01:45:00AM: > > > I have no idea what you are attempting to do, but that does an iBook > > install problem have to do with sparc kernel images? > > I guess you have the same problem - no Ext3 support built-in. Wrongo. And please do not quote me as "DPL" when I am not speaking in that capacity. -- .--==-=====-=-. / Ben Collins--Debian GNU/Linux \ ` [EMAIL PROTECTED] ' `---=-----==-===---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
