Re: [sparc] new bootdisks coming soon
Eric Delaunay <[EMAIL PROTECTED]> writes: > BTW, how should I commit my patches ? Changes you want in the slink boot-floppies should be committed to a local repository which is on the "adam-boot-floppies_2-1_branch" branch. > Either I completely missed the point about getting the > "adam-boot-floppies_2-1_branch" branch or my last fixes (dated from > 99/04/13) about 2.2 kernel support were not put in the tree. I have > had to refix them in my current copy of the tree I'm not quite sure what you are saying. We have the 'trunk' which is for potato, and the 'branch' which is for slink. Committing to the branch isn't going to get your changes into the trunk unless I do a merge. Committing to the trunk won't get onto the branch, period (that's the point of the branch). > :-(( More on this > topic: how do you manage to bring some fixes from your branch to the > main trunk ? Is there any magic cvs command ? No. Just ask me to do another merge from the branch to the trunk and I'll do it. Do you want me to do that? It's not a command, it's a workflow. It's pretty tricky and I prefer to do it myself. OTOH, I am not really in a position to burn new slink boot-floppies for i386 since I don't seem to have any access to tecra kernels. Enrique, would you be able to burn a new boot-floppies? > > 2.2.5 is available AFAIK (or is that only source?). Why not just > > stick with that? > > Where can I get these kernel-images ? (I'm not connected to the net > by the time I write this email so I cannot check if it sits in > potato or not, sorry). I dunno. I guess they don't exist yet. Should I make some for 2.2.5? I think I shoud. Sure it may have problems, but it's better than 2.2.1, right? And the kernel source for slink has been updated from 2.2.1 to 2.2.5. > Oops, forgot it. > I downloaded both silo 0.8.5-4 & 0.8.6-1 from ftp.prosa.it few hours ago, but > which one should I use ? Which one will be put in 2.1r3 anyway ? I dunno -- if 0.8.5-4 fixes the nasty bug on Ultra5s and Ultra10s that hit me (Bug#34896) then I guess that one would be the one for slink. I guess it's worth a try! Then I can test it easily. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
dselect hang
I'm using the apt method in dselect, and for some reason, dselect just hangs whenever I try to update or install packages. It doesn't give me any sort of status indication, but I can see that the apt-get process is taking up a huge chunk of the CPU. Has anyone seen this before? I'm using potato with kernel 2.0.35 and dselect version 1.4.0.31 on a SS 2. Thanks, Max -- The hopeful depend on a world without end Whatever the hopeless may say Neil Peart, 1985 pgpsXXPDfv1KC.pgp Description: PGP signature
Re: [sparc] new bootdisks coming soon
Adam Di Carlo <[EMAIL PROTECTED]> writes: > Eric Delaunay <[EMAIL PROTECTED]> writes: > > > I just now need new 2.2 kernel images for sparc. > > Which one are available now ? 2.2.6 ? 2.2.7 ? > Slink proposed-updates already has 2.2.5. Let's stick with that, it's > known to be good. Do you need me to make an image? If so, I just > gotta find the kernel config files used for 2.2.1 somewhere... They should be in /boot in the respective packages - they are also in the debian dir of the source package for those kernels. It might help to make sure LEO support is enabled in the sparc32 kernel. (If there is an option in 2.2.5. Build the ultra kernel with: make-kpkg --subarch=sun4u --arch_in_name kernel_image (If you build this after the 32-bit one, make sure you remove stamp-configure first - and it wouldn't hurt to make sure include/linux/modules is empty.) Oh, and the 2.2.5 kernel _might_ not work with the 3.3.3.1 X servers (when I release them) on some machines - I'm not sure when the appropriate patches were applied. (The trouble would be with Ultra's and maybe LEO machines.) Steve [EMAIL PROTECTED]
Re: Broken loop device
Andreas Jaehnigen wrote: > Hi Eric, > > thanks for the reply... > > > sorry for the late reply, I was too busy to read all my emails last week > > :-( > > > > But you know: It's never too late! :-) > > > How many memory is installed in your SLC ? > > You've got the problem! :-) > It has only 8 megs installed - somewhat tiny, hm? :-( > In the meantime, I figured out what you've been writing and I'm trying to get > done with a (temporarily) installiation onto a local disk. Unfortunately, the > SLC hangs (again!!) during filesystem creation, seems to be tight on memory > again. > But how can this happen? I succesfully managed to create a swap partition > (about 128 megs)... Is your swap space really available ? (look at /proc/meminfo) I'm sorry but I don't have any further ideas :-( I don't promise you I will have time to work on it, but I will try to install on a low memory system (after I removed some memory banks out of one of my sparc) to see what happens exactly... Regards. -- Eric Delaunay | "La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant." Henri Jeanson (1900-1970)
Re: [sparc] new bootdisks coming soon
Adam Di Carlo wrote: > > > "Eric" == Eric Delaunay <[EMAIL PROTECTED]> writes: > > Eric> I'm pretty ready to release new bootdisks, at least for 2.1r3(?) > Eric> candidate. > > Ok, be sure to let me know when you are actually burning these, and > you should tag the source when you do that too. At that point, any > subsequent changes should be 2.1.10.1 or 2.1.11. Well, I hope I could upload it next monday... At least on my ftp site to allow some of you do a trial. BTW, how should I commit my patches ? Either I completely missed the point about getting the "adam-boot-floppies_2-1_branch" branch or my last fixes (dated from 99/04/13) about 2.2 kernel support were not put in the tree. I have had to refix them in my current copy of the tree :-(( More on this topic: how do you manage to bring some fixes from your branch to the main trunk ? Is there any magic cvs command ? > Eric> I addressed the following problems: > [list deleted] > > Did you make sure these all show up in ./debian/changelog file? If > not, you should. I will check it before uploading it. > Eric> 6. /dev/mouse -> sunmouse symlink added to the base system. > > Actually. > > Eric> I just now need new 2.2 kernel images for sparc. Which one are > Eric> available now ? 2.2.6 ? 2.2.7 ? > > 2.2.5 is available AFAIK (or is that only source?). Why not just > stick with that? Where can I get these kernel-images ? (I'm not connected to the net by the time I write this email so I cannot check if it sits in potato or not, sorry). > Eric> BTW, what is the status of the /dev/fb0 permissions troubles ? > Eric> Is it fixed in the X server or the wrapper ? > > Not that I know of. Perhaps we should try to workaround that. > It's a pretty critical/annoying sparc problem. I'm using xdm, so I don't have this problem either. Could just well documenting it in the release notes be sufficient ? > Eric, have you dealt with the attached silo issues? (Bug#34896) Oops, forgot it. I downloaded both silo 0.8.5-4 & 0.8.6-1 from ftp.prosa.it few hours ago, but which one should I use ? Which one will be put in 2.1r3 anyway ? >Davide Barbieri wrote: > I have put on ftp.prosa.it/pub/people/paci/silo > a new debian package of silo (0.8.5-4) > > there is only the binary packages, and it is there because > I don't want to upload it, until I'm confident it will work > > I have made a little hack, and it should now work on Ultra, > but I can't test because I haven't an Ultra: can you test it? -- Eric Delaunay | "La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant." Henri Jeanson (1900-1970)
Re: glibc....
On Mon, May 03, 1999 at 12:51:00PM -0400, Adam Di Carlo wrote: > Ben Collins <[EMAIL PROTECTED]> writes: > > > Also, xia01 (the Ultra donated graciously by Kachina Tech) has been > > upgraded to potato, and kernel 2.2.7, so we will start up the buildd > > again and catch up on some potato compiles and make failed build logs > > available to everyone. > > Sorry to pester again, but does xia01 enable us to add our machines to > the as a buildd to the xia01 wanna-build database? No, xia01 is just a buildd server, the main wanna-build server is where otehr systems, plus developers can interface with the packages that need building. Let me get this setup first before I start figuring out how to expand on it. > In unrelated issues, we're still lagging on potato egcs/g++, right? No, egcs 1.1.2 was uploaded and installed last week, it was used to compile the the glibc 2.1.1 in Incoming. The main compiler (the gcc package) is now egcc 1.1.2. So as far as the dev environment, we are equal (if not superior as far as backward and cross-dist compatibility) to the other archs.
Re: dbootstrap: status b
Andreas Jaehnigen <[EMAIL PROTECTED]> writes: > dbootstrap occasionally starts over here while mounting partitions over > NFS. In this case it displays (on the error console) a message: > pid exit: status = b > What does this mean? No clue. CC'ing [EMAIL PROTECTED] > Hardware: Sun Sparcstation SLC with 8 MB RAM, 128 MB Swap > Software: Debian "slink" (2.1) for Sparc -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
Re: [sparc] new bootdisks coming soon
Eric Delaunay <[EMAIL PROTECTED]> writes: > I just now need new 2.2 kernel images for sparc. > Which one are available now ? 2.2.6 ? 2.2.7 ? Slink proposed-updates already has 2.2.5. Let's stick with that, it's known to be good. Do you need me to make an image? If so, I just gotta find the kernel config files used for 2.2.1 somewhere... -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
Re: glibc....
Ben Collins <[EMAIL PROTECTED]> writes: > Also, xia01 (the Ultra donated graciously by Kachina Tech) has been > upgraded to potato, and kernel 2.2.7, so we will start up the buildd > again and catch up on some potato compiles and make failed build logs > available to everyone. Sorry to pester again, but does xia01 enable us to add our machines to the as a buildd to the xia01 wanna-build database? In unrelated issues, we're still lagging on potato egcs/g++, right? -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
