Re: unbreaking LibreOffices tests on at least release architectures
On Sun, Jun 18, 2023 at 10:32:55AM +0200, Rene Engelhard wrote: >Hi, > >Am 18.06.23 um 10:19 schrieb John Paul Adrian Glaubitz: >> On Sun, 2023-06-18 at 09:31 +0200, Rene Engelhard wrote: >> > Also note I am not talking about the debian-ports architectures. Those I >> > forgot and I have no problems making them stay into "testsuite ran but >> > results ignored" set. >> Why did you send this mail exclusively to debian-ports then? > >I (obviously) wrongly assumed that this was the magic address which >duplicates to every port. > >Must have misremembered. It still does - I got this copy via the debian-arm list... -- Steve McIntyre, Cambridge, UK.st...@einval.com "This dress doesn't reverse." -- Alden Spiess
Re: debian-installer now available in Ports
On Wed, Apr 12, 2017 at 01:55:08PM +0100, Steven Chamberlain wrote: >John Paul Adrian Glaubitz wrote: >> Thus, I was wondering whether any volunteers would be willing to help >> building >> ISO images for the various architectures. > >I'm already doing this for kfreebsd-amd64, but only the jessie-kfreebsd >suite: >http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_jessie-kfreebsd/lastBuild/console >and I had to patch debian-cd before it worked. (Didn't yet find time to >file bugs or submit those patches). Please post them! >I could probably set up similar jobs for kfreebsd-* sid now. > >> It's not necessary to run debian-cd on the same architecture as the >> target architecture of the ISO images. Exactly. There are sometimes difficulties with the tools needed to set up boot files etc., but they tend to be portable. >I did not even realise that. So I will add kfreebsd-i386 next. > >I expect there might be problems trying to build linux arches from a >kfreebsd host. But we should try to find out, and then maybe fix it. We were happily building kfreebsd-* images from a Linux host, so I'd expect it to work OK. I've offered before: I don't have the time personally to work on building ports images, but I'm more than happy to help other people getting them building on our official infrastructure... -- Steve McIntyre, Cambridge, UK.st...@einval.com Who needs computer imagery when you've got Brian Blessed?
Re: Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
On Wed, Feb 10, 2016 at 07:14:07PM +0100, Christian PERRIER wrote: >Quoting John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de): >> Hi! >> >> Coming back to the discussion after having re-assigned the bug to the >> partman-ext3 package. First of all, this particular bug was reported >> in Ubuntu as well [1], so I have linked this bug report to the LP bug >> report. >> >> Secondly, I would like to discuss here what is keeping us from adding >> "-F" to the mkfs.$filesystem call in 50format_ext3. I am currently >> not seeing any obvious, but I might just be missing something here. >> >> However, since we are using "-f" (the btrfs equivalent to mkfs.ext3's >> "-F") in partman-btrfs [2], I see no apparent reason not to use it if >> it helps resolving problems people are seeing on certain architectures >> and partition setups. > >Just read the bug log and got convinced. >So the patch would actually be: > >diff --git a/commit.d/format_ext3 b/commit.d/format_ext3 >index fe84d89..d86c545 100755 >--- a/commit.d/format_ext3 >+++ b/commit.d/format_ext3 >@@ -56,7 +56,7 @@ for dev in $DEVICES/*; do >usage='' >fi >if log-output -t partman --pass-stdout \ >- mkfs.$filesystem $device $usage >/dev/null; then >+ mkfs.$filesystem -F $device $usage >/dev/null; then > sync >status=OK >else > > >Objections for me to commit? It looks like an obvious fix - go ahead! -- Steve McIntyre, Cambridge, UK.st...@einval.com Into the distance, a ribbon of black Stretched to the point of no turning back
Re: Time to change the debian-ports "list"?
On Wed, Jul 22, 2015 at 05:38:17PM +0200, Wouter Verhelst wrote: >On Fri, Jul 17, 2015 at 01:40:20PM +0100, Steve McIntyre wrote: >> On Thu, Sep 11, 2014 at 12:51:29PM +0100, Steve McIntyre wrote: >> >On Wed, Sep 10, 2014 at 07:01:00PM +, Thorsten Glaser wrote: >> >>Alexander Wirt dixit: >> >> >> >>>Could you please (technically) summarize what needs to be done from >> >>>listmaster side? >> >> >> >>1. Remove whatever debian-po...@lists.debian.org is right now >> >> >> >>2. Create a new debian-po...@lists.debian.org mailing list which >> >> works just like the other regular lists >> >> >> >>3. Announce the new debian-po...@lists.debian.org so that people >> >> can subscribe to it; document that there is no longer >> >> an address to reach *all* ports but that people should >> >> eMail the individual ports’ lists (and cross-post if >> >> needed, but only to the amount needed), and that the >> >> new debian-po...@lists.debian.org instead is a mailing list for >> >> discussion about >> >> a) debian-ports.org infrastructure >> >> b) porting Debian in general >> >> c) questions related to setting up a Debian port, >> >> including wanna-build, buildd, etc. > >That seems like a bad idea to me, tbh. There will be people who won't >notice that the meaning of debian-ports@ has changed, and who will try >to use it with its old meaning. > >If there are problems with the current meaning of debian-ports, can't we >just retire the old alias and create a list under a different name? Is there much point to that? I've not heard anybody at all speak up in favour of the existing behaviour. If anybody does use try to use it that way in future, the new list will most likely be the best place for their mail to go... -- Steve McIntyre, Cambridge, UK.st...@einval.com "I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. " -- Charlie Stross -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150722170456.gc5...@einval.com
Re: Time to change the debian-ports "list"?
On Thu, Sep 11, 2014 at 12:51:29PM +0100, Steve McIntyre wrote: >On Wed, Sep 10, 2014 at 07:01:00PM +, Thorsten Glaser wrote: >>Alexander Wirt dixit: >> >>>Could you please (technically) summarize what needs to be done from >>>listmaster side? >> >>1. Remove whatever debian-po...@lists.debian.org is right now >> >>2. Create a new debian-po...@lists.debian.org mailing list which >> works just like the other regular lists >> >>3. Announce the new debian-po...@lists.debian.org so that people >> can subscribe to it; document that there is no longer >> an address to reach *all* ports but that people should >> eMail the individual ports’ lists (and cross-post if >> needed, but only to the amount needed), and that the >> new debian-po...@lists.debian.org instead is a mailing list for >> discussion about >> a) debian-ports.org infrastructure >> b) porting Debian in general >> c) questions related to setting up a Debian port, >> including wanna-build, buildd, etc. > >That's exactly it, yes. Thanks. :-) Hi Alexander et al,, Could we make a start on this please? More discussions on the d-ports expander today have reminded me how annoying the current setup is. -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150717124020.ga13...@einval.com
Ports pages need updating on www.d.o
Hi folks, I've been trying to help out a bit with the port pages (under https://www.debian.org/ports/), starting with the ARM ports. We could really do with updating a lot of the information here - it's so old it's starting to smell bad! I've removed some of the older details (e.g. hardware support) that used to be under https://www.debian.org/ports/arm and replaced them with pointers to the wiki now. My reasoning here is that the wiki is more easily updated for more dynamic content like this, plus it's much easier for the wider community to contribute that way. I'd suggest that most of the other port pages would be better organised like this too, but that's a decision for porters to make for themselves. We also need to work on some of the other content around here. For example, the top-level ports page is still listing the ports from Wheezy rather than Jessie. Please take a look. In the webwml source, there's even a file to list maintainers for the various port pages. Until I touched it today, it hadn't been modified since 2005. It's clearly not very useful at the moment! -- Steve McIntyre, Cambridge, UK.st...@einval.com "I suspect most samba developers are already technically insane... Of course, since many of them are Australians, you can't tell." -- Linus Torvalds -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150428223702.go21...@einval.com
Re: Time to change the debian-ports "list"?
On Wed, Sep 10, 2014 at 07:01:00PM +, Thorsten Glaser wrote: >Alexander Wirt dixit: > >>Could you please (technically) summarize what needs to be done from >>listmaster side? > >1. Remove whatever debian-po...@lists.debian.org is right now > >2. Create a new debian-po...@lists.debian.org mailing list which > works just like the other regular lists > >3. Announce the new debian-po...@lists.debian.org so that people > can subscribe to it; document that there is no longer > an address to reach *all* ports but that people should > eMail the individual ports’ lists (and cross-post if > needed, but only to the amount needed), and that the > new debian-po...@lists.debian.org instead is a mailing list for > discussion about > a) debian-ports.org infrastructure > b) porting Debian in general > c) questions related to setting up a Debian port, > including wanna-build, buildd, etc. That's exactly it, yes. Thanks. :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com "I suspect most samba developers are already technically insane... Of course, since many of them are Australians, you can't tell." -- Linus Torvalds -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2014095129.gg14...@einval.com
Re: Time to change the debian-ports "list"?
On Fri, Sep 05, 2014 at 06:39:10PM +0100, Steve McIntyre wrote: >Hi folks, > >I believe the existing debian-ports setup (as an exploder pointing to >all the different port lists) is not working well at all. It's a >confusing setup to many people, which leads to lots of cross-list >noise that's probably not warranted. Some of the traffic is also >clearly meant to be discussing the debian-ports setup itself rather >than individual ports, and that's also off-topic for those ports that >are in the main archive. So, I propose: > > * Remove the confusion: turn debian-ports into a separate *normal* > mailing list, announce it and let people subscribe to it as they > see fit normally. This would be specifically for "discussions about > ports.debian.org and architectures hosted there". > > * Explicitly do *not* add another exploder to replace the old > address: instead, *if* we want something to cover this use case, > add a new list that interested people can subscribe to. Maybe > "debian-cross-ports" or "debian-architectures" or something. Please > feel free to suggest a better name! If such a list were to be set > up, we could/should encourage existing architecture porters to sign > up there too. > >Thoughts? Any dissenting opinions? Listmasters - are you happy to change things like I propose? -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with "Valor": "Centurion" represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140910150520.go24...@einval.com
Time to change the debian-ports "list"?
Hi folks, I believe the existing debian-ports setup (as an exploder pointing to all the different port lists) is not working well at all. It's a confusing setup to many people, which leads to lots of cross-list noise that's probably not warranted. Some of the traffic is also clearly meant to be discussing the debian-ports setup itself rather than individual ports, and that's also off-topic for those ports that are in the main archive. So, I propose: * Remove the confusion: turn debian-ports into a separate *normal* mailing list, announce it and let people subscribe to it as they see fit normally. This would be specifically for "discussions about ports.debian.org and architectures hosted there". * Explicitly do *not* add another exploder to replace the old address: instead, *if* we want something to cover this use case, add a new list that interested people can subscribe to. Maybe "debian-cross-ports" or "debian-architectures" or something. Please feel free to suggest a better name! If such a list were to be set up, we could/should encourage existing architecture porters to sign up there too. Thoughts? -- Steve McIntyre, Cambridge, UK.st...@einval.com Welcome my son, welcome to the machine. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905173910.gf17...@einval.com
Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
On Mon, Apr 28, 2014 at 01:20:20PM +0200, Thomas Schmitt wrote: >Hi, > >> I may provide you access to a shell account on my machines if needed. > >Yes, please. > >Plus a directory tree > ./tmp/miniiso/cd_tree >which can cause the xorriso crash. > > >> Sparc architecture is extremely picky about alignement. Bad alignement, >> yields SIGSEGV whereas intel only do it in the less efficient way. > >I would suspect the habit of my libisofs predecessor developer >to use structs as access frame for byte arrays read from file. > >But why then was it possible to produce > debian-7.4.0-sparc-netinst.iso >by xorriso-1.2.6 as can be read from its "Preparer Id": > XORRISO-1.2.6 2013.01.08.103001, LIBISOBURN-1.2.6, LIBISOFS-1.2.6, > LIBBURN-1.2.6 >Does debian-cd pull "sparc" trees onto a non-sparc machine ? Yes. We build all the release images on an amd64 machine, pettersson.d.o -- Steve McIntyre, Cambridge, UK.st...@einval.com "The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary." -- James D. Nicoll -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140428113544.ga30...@einval.com
Re: Results of the porter roll call (Was: Roll call for porters of architectures in sid and testing)
On Wed, Oct 02, 2013 at 04:07:25PM +0100, Wookey wrote: >+++ Niels Thykier [2013-10-02 09:45 +0200]: >> Hi, >> >> The final results are in: >> >> Summary table: >> Arch || DDs || NMs/DMs || Other || Total >> ---++-++-++---++-- >> armel || 3 || 0 || 1 ||4 >> armhf || 3 || 1 || 2 ||6 > >> armel: Wookey (DD), Gatis Visnevskis (!DD), Nobuhiro Iwamatsu (DD), Steve >> McIntyre (DD) >> armhf: Jeremiah Foster (!DD, but NM?), Wookey (DD), Justus Winter (!DD), >> Lennart Sorensen (!DD), Nobuhiro Iwamatsu (DD), Steve McIntyre (DD) > >I am surprised not to see Riku Voipio and Hector Oron on this list as >I know they help manage the buildds and Riku signs uploads. I don't >know if they are trying to escape, or just being too slack to send >mail :-) > >> arm64: Wookey (DD), Steve McInture (DD) > >There are other DDs working on this too (Doko and Riku >particularly), but again they are probably trying to avoid getting >any more formal responsibilities. :-) *grin* I guess so... -- Steve McIntyre, Cambridge, UK.st...@einval.com You raise the blade, you make the change... You re-arrange me 'til I'm sane... -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131002151044.gk14...@einval.com
Help with Wheezy CD testing on Saturday
Hi folks, As we're expecting to release this Saturday (4th May) and I'm going to be preparing the CDs and DVDs to go with the release, it would be lovely if we have some volunteers to help test the images. We have been doing testing of the daily, weekly and Release Candidate images as they're produced, but it would be nice to get more coverage in the testing, especially: * non-PC architectures * more obscure combinations of options like partitioning, filesystems etc. * different desktops with differing package sets I've started a wiki page at https://wiki.debian.org/Teams/DebianCD/ReleaseTesting/Wheezy and I'll be filling in more details there in the next couple of days, including some specific configurations that I'd like to see tested. If you can help us test on Saturday, please take a look and join me in #debian-cd where we'll be coordinating. Cheers, -- Steve McIntyre, Cambridge, UK.st...@einval.com "Managing a volunteer open source project is a lot like herding kittens, except the kittens randomly appear and disappear because they have day jobs." -- Matt Mackall -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130502012910.gb28...@einval.com
Re: install net drivers
Dave Miller wrote: >From: Jurij Smakov >Date: Mon, 21 Mar 2011 09:26:10 + > >> On Sun, Mar 20, 2011 at 10:05:11PM -0700, David Miller wrote: >>> >>> Please add CONFIG_NIU to the network drivers provided on the network >>> install image. >>> >>> Installations on several Niagara variants is not possible without >>> this. >> >> This was reported as http://bugs.debian.org/608516, and is fixed in >> 6.0.1 images (I've just verified that netinst image contains >> >> /lib/modules/2.6.32-5-sparc64/kernel/drivers/net/niu.ko >> >> in the nic-modules-2.6.32-5-sparc64-di_1.64+squeeze1_sparc.udeb). > >That's great. > >I must have had a 6.0 image. There was also a bug in the script generating the small CDs (such as the netinst) for 6.0.1, meaning you might have seen this problem in a 6.0.1 image. After that was fixed, rebuilt 6.0.1a images have been produced and distributed as replacements. -- Steve McIntyre, Cambridge, UK.st...@einval.com There's no sensation to compare with this Suspended animation, A state of bliss -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q1d5b-et...@jack.mossbank.org.uk
DPL teams review 2008
k all of your tasks in order of importance? f. Finally, are you having fun working on Debian? Why/why not? 2. Teams you're in -- (please answer this section multiple times where appropriate, once per team, but *excluding* teams for maintenance of individual packages) a. What teams do you work on? Are you an "official" member of those teams? b. How well do you think those teams are performing, in terms of getting things done? How are daily/regular tasks dealt with? And how about less common, one-off things? c. How do members of your teams communicate with each other about what they're working on? And how do they (as individuals or as a team) communicate with people outside of the team? Do you feel they coordinate well? d. Are there enough resources for your teams to do their jobs well? If not, what's missing? e. Anything else you'd like to mention? 3. Other teams -- a. What contact, if any, do you (as an individual) have with other teams? How well does that contact work? b. How well do your team(s) interact with other teams? c. If you have any issues in (a) or (b), how would you suggest to fix them? d. Any other observations about the various teams in Debian? === Other stuff === That's the list of things I'm hoping to learn more about from this review of teams. Of course, I'm sure there are many other things in Debian that you'd like to ask or tell me about. By all means, talk to me about them - I see it as part of my job to listen and do what I can to help. But please keep those separate from this survey - it'll help me to avoid my head exploding in all directions... :-) -- Steve McIntyre, Debian Project Leader <[EMAIL PROTECTED]> signature.asc Description: Digital signature
Re: Account on sparc machine(s) wanted
In article <[EMAIL PROTECTED]> you write: > >I am a member of Debian kernel team, working (to the extent of my >abilities) on sparc-specific bugs. Recently I have moved and thus was >forced to get rid of all my sparc hardware which I used for d-i testing >and kernel work. The plans to get some new machines are on the way (Blars >Blarson has a sparc32 box waiting for me and Andres Salomon is planning to >ship an Ultra 5 my way), but it will take at least a few more weeks before >I can lay my hands on them. In the meantime I can't even do test kernel >builds or any basic testing/porting. If you have a possibility to open >an account for me on a sparc box for this purpose, I would really >appreciate it. If the box can be rebooted remotely or accessed via the >serial console, that would be a huge plus. I have an Ultra 30 available - mail me a (PGP-signed) ssh key and I'll set you up. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Welcome my son, welcome to the machine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Envctrl support for E450
David Johnson wrote: >On Friday 13 May 2005 23:32, Jeff Adams wrote: >> It's an e450 (of course), 3GB RAM, (3) 4.5 GB drives, (8) 36GB drives >> (2) 400 Mhz procs (I think), 3 power supplies, dual backplanes, dual >> controllers, fast ethernet card, and a sun gigabit over fiber network >> card. We can provide the rackmount sliding tray as well. >> > >Well I contacted the hardware donations person at Debian and they haven't >replied, so I can only presume that they don't want it (!), so I don't know >what to suggest if you can't find a developer who wants it. Maybe the Gentoo >SPARC people...? > >Failing that, just put it on eBay ;-) Apologies for the lack of response from the hw donations guy - Rob's a student about to hit exams in the next couple of weeks, and so he's a little bit occupied... :-) Re: envctrl support, I have an E450 sat at the end of my desk at work right now. It's currently installed with Solaris 8, but I dare say I could get Sarge onto another disk quite easily and have a play... -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] We don't need no education. We don't need no thought control. signature.asc Description: Digital signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 02:56:43PM -0500, Ben Collins wrote: >> Thanks very much for the support, Ben. I've been working hard trying >> to get some sparc CDs created, and I didn't think asking for some help >> to get this job done was particularly out of order. Apparently I was >> wrong. I hope you have time to get the installer and CDs ready for the >> sarge release... > >No, you didn't ask, you bitched and moaned and got pretty damn rude >about it. Just asking would have gotten you a nice reply with >explanation, and help avoiding the problem. Apparently you don't know >how to ask nicely and would rather be an ass about it. To top it off, >it's your own damn fault and you felt like pointing fingers. Yes, I did. Sorry, it's been a _very_ long couple of days, without much sleep in the middle and I've been getting defensive and rude when I shouldn't have been. Apologies. It gets very frustrating in these situations when a long task that normally works with minimal intervention suddenly needs a lot of attention. Things seem a lot more under control now, and I'm slowly working my way through the rest of the arches to help Phil. This shouldn't have turned into a flaming match - again, I'm sorry. I don't want to fall out over this... Can I ask one favour for in future, though - if any more changes are made in future to core tools like silo, mkisofs etc. that will affect CD/DVD image generation, can you please give us just a little bit of warning? At the moment, without the information about the new isofs.b you gave me a way back up this messy thread, we wouldn't be able to make working (bootable) sparc images for sarge or sid. On that front, how is the sparc end of the debian-installer work going? Thanks, -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I... signature.asc Description: Digital signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 12:51:52PM -0500, Ben Collins wrote:
>On Tue, Dec 02, 2003 at 03:57:46PM +0000, Steve McIntyre wrote:
>> On Tue, Dec 02, 2003 at 10:26:54AM -0500, Ben Collins wrote:
>> >> For now I'm going to leave the sparc images as they are. If there's no
>> >> way to test, then I'm going to wait until the boot-sparc script is
>> >> known to work. I'll work on the easier architectures first.
>> >
>> >I know they wont work, because isofs.b doesn't work like cd.b did, and
>> >you used a mkisofs that that was expecting that.
>>
>> No, I didn't, In the end I've used a woody mkisofs and the woody
>> silo. If _they_ don't work together, then things are screwed
>> altogether. That's how the r0 and r1 images are made, as far as I
>> know. Yes or no?
>
>If you used woody silo and woody mkisofs, then you are good to go.
Thank you. That's the information I was hoping to get out of you
several mails ago.
>> A mirror is a mirror. It's getting ludicrous to expect people
>> to set up a completely separate woody-only mirror to build CDs. All
>> the other architectures work fine in this scenario.
>
>How the hell do you expect to build woody CD's if you are using shit
>from unstable to build it? It's even more ludicrous for you to expect
>that to work. Woody CD's should build from woody. How can you expect
>that things don't change across over a year of development?
Some consistency of the changes might not hurt. The fact that the
debian-cd code in both woody _and_ unstable still depends on very
specific behaviour of old versions of silo and mkisofs is a bit of a
problem here:
> silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
> # put the relevant parts of SILO boot loader
> (ar p $silo_deb data.tar.gz | \
> tar zxf - -C $inst/ ./boot/{cd,second}.b)
>I'm not taking any blame or guilt from your problems. You caused your
>own headache.
Thanks very much for the support, Ben. I've been working hard trying
to get some sparc CDs created, and I didn't think asking for some help
to get this job done was particularly out of order. Apparently I was
wrong. I hope you have time to get the installer and CDs ready for the
sarge release...
--
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
Welcome my son, welcome to the machine.
signature.asc
Description: Digital signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 10:26:54AM -0500, Ben Collins wrote: >> For now I'm going to leave the sparc images as they are. If there's no >> way to test, then I'm going to wait until the boot-sparc script is >> known to work. I'll work on the easier architectures first. > >I know they wont work, because isofs.b doesn't work like cd.b did, and >you used a mkisofs that that was expecting that. No, I didn't, In the end I've used a woody mkisofs and the woody silo. If _they_ don't work together, then things are screwed altogether. That's how the r0 and r1 images are made, as far as I know. Yes or no? >So you are telling me that the problem is that you are pulling stuff >from unstable, and using unstable to build, and things are failing >because of that? If so, then that's your mistake, not mine. Build on >woody, and point to a woody mirror, not unstable. I can imagine the >amount of problems you would have building that way. A mirror is a mirror. It's getting ludicrous to expect people to set up a completely separate woody-only mirror to build CDs. All the other architectures work fine in this scenario. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] You lock the door And throw away the key There's someone in my head but it's not me pgpuLOjbsMZKl.pgp Description: PGP signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 09:52:41AM -0500, Ben Collins wrote: >> >The path to isofs.b needs to be absolute on the build machine (not >> >relative to the CD root). The "..." is literal, it means use isofs.b to >> >boot any sort of sparc (sun4c,sun4m,sun4d,sun4u). >> >> Some warning of these changes would have been useful. Does this mean >> that the set of images I've just produced are now useless? > >I had forgotten that I had put silo 1.3.x into stable. Wasn't >intentional. I didn't realize that mkisofs had changed in woody. That's >pretty broken in itself (or maybe you are running testing/unstable to do >the CD builds, which is probably not a good idea either). No, silo 1.2.x is still in woody. The mkisofs and silo versions I'm now using are the woody ones, by dint of forcing things in the build script. My development machine (the one with the mirror attached) is running unstable, but the silo problem would have shown up there anyway - the script to make Sparc bootable CDs grabs the latest one directly out of the mirror. And can you please work out your differences with Joerg and/or the mkisofs maintainer so we can get these going again? >The images you produced are broken, I'm sure. My mistake on the silo >problem, but you could calm down a bit. Things happen. Is there any easy way to check them? It would be nice not to have to start _again_. It's becoming impractical already to make CDs for woody due to the mixture of breakages and the sheer length of time taken to build them; I shudder to think what sarge is going to be like at this rate. For now I'm going to leave the sparc images as they are. If there's no way to test, then I'm going to wait until the boot-sparc script is known to work. I'll work on the easier architectures first. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] You raise the blade, you make the change... You re-arrange me 'til I'm sane... pgp1Fh0iqGq57.pgp Description: PGP signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 08:14:13AM -0500, Ben Collins wrote:
>On Tue, Dec 02, 2003 at 01:31:26AM +0000, Steve McIntyre wrote:
>>
>>
>> We're late getting the r2 images created, and changes to the packages
>> that we need to use don't help. The script to make sparc CDs bootable
>> contains the following:
>>
>> silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
>> # put the relevant parts of SILO boot loader
>> (ar p $silo_deb data.tar.gz | \
>> tar zxf - -C $inst/ ./boot/{cd,second}.b)
>>
>> This currently picks up silo_1.3.1-2_sparc.deb, which doesn't contain
>> a cd.b file at all, so the sparc build fails. Generally after an hour
>> of frantic disk-thrashing. I don't know if the change to silo is
>> deliberate or not, but for now I'm patching the script to use the bits
>> out of silo_1.2.5-2_sparc.deb instead, as that seems to have what we
>> need. If this is wrong, please shout!
>
>The silo cd boot step changed. You'll need isofs.b and second.b, and
>you'll need to move silo.conf to /boot on the CD. Then change the
>mkisofs incantation to include these bootable options:
>
> -r -G /boot/isofs.b -B ...
>
>The path to isofs.b needs to be absolute on the build machine (not
>relative to the CD root). The "..." is literal, it means use isofs.b to
>boot any sort of sparc (sun4c,sun4m,sun4d,sun4u).
Some warning of these changes would have been useful. Does this mean
that the set of images I've just produced are now useless?
--
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/
pgpoRrnJAn24o.pgp
Description: PGP signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 01:50:17AM -0800, David S. Miller wrote: >On Tue, 2 Dec 2003 02:33:56 +0000 >Steve McIntyre <[EMAIL PROTECTED]> wrote: > >> If this next attempted build fails, I'm going to abandon the sparc >> images altogether, and recommend that woody r2 does not include sparc >> CDs. Does anybody actually care in the SLIGHTEST about supporting >> sparc CDs? It certainly doesn't look that way. It's now 2.30am here, >> and I'm going to bed. I'll check in the morning if the CDs built, but >> as it stands right now I'd be quite surprised... > >Why don't you wait a bit for Ben Collins to wake up and read >his email so that he can help you with these problems? > >I fully recognize the amount of time and effort you are putting >into trying to get these CDs built, but posting as if an immediate >response is required and throwing a tantrum won't fix the problem. > >Let's wait for what Ben has to say about this ok? I think a lot of >people would like to have Sparc CD images if possible. The build appears to have worked, FWIW. I've checked that the jigdo files are valid by rebuilding images from them, and I'm uploading the jigdo bits (slowly) now to cdimage. I wasn't especially expecting an immediate response last night, but it does get really annoying when there are multiple mails every day now, pestering for the new r2 images, and the toolchain needed to build them has just been allowed to rot by the architecture maintainers. Apologies for the tantrum, but _please_ can we get architecture folks to put some effort into the CD creation process...? -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] "It's actually quite entertaining to watch ag129 prop his foot up on the desk so he can get a better aim." [ seen in ucam.chat ] pgpW1ynFz1D6A.pgp Description: PGP signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 01:31:26AM +, Steve McIntyre wrote:
>
>
>We're late getting the r2 images created, and changes to the packages
>that we need to use don't help. The script to make sparc CDs bootable
>contains the following:
>
>silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
># put the relevant parts of SILO boot loader
>(ar p $silo_deb data.tar.gz | \
>tar zxf - -C $inst/ ./boot/{cd,second}.b)
>
>This currently picks up silo_1.3.1-2_sparc.deb, which doesn't contain
>a cd.b file at all, so the sparc build fails. Generally after an hour
>of frantic disk-thrashing. I don't know if the change to silo is
>deliberate or not, but for now I'm patching the script to use the bits
>out of silo_1.2.5-2_sparc.deb instead, as that seems to have what we
>need. If this is wrong, please shout!
Christ. This gets even better. Two more runs, and things are failing
further down the line. mkisofs now complains:
/usr/bin/mkisofs: No such file or directory. Invalid node - boot/second.b
I go looking for the reason, and I can't find one - the directory
boot1 is included in the command line, and that's where boot/second.b
lives. Why is it failing. Oh, I see - the options passed in
-silo-boot boot/second.b -s /boot/silo.conf -S boot/cd.b boot1
aren't being parsed properly. It seems that recent versions of mkisofs
don't support the -silo-boot option. And nobody has flagged this as a
problem AT ALL. I'm now trying again, hacking around this by using an
old woody version of mkisofs. FFS, this should not be necessary.
If this next attempted build fails, I'm going to abandon the sparc
images altogether, and recommend that woody r2 does not include sparc
CDs. Does anybody actually care in the SLIGHTEST about supporting
sparc CDs? It certainly doesn't look that way. It's now 2.30am here,
and I'm going to bed. I'll check in the morning if the CDs built, but
as it stands right now I'd be quite surprised...
--
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
Is there anybody out there?
signature.asc
Description: Digital signature
Silo breakage creating woody r2 CDs for sparc
We're late getting the r2 images created, and changes to the packages
that we need to use don't help. The script to make sparc CDs bootable
contains the following:
silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
# put the relevant parts of SILO boot loader
(ar p $silo_deb data.tar.gz | \
tar zxf - -C $inst/ ./boot/{cd,second}.b)
This currently picks up silo_1.3.1-2_sparc.deb, which doesn't contain
a cd.b file at all, so the sparc build fails. Generally after an hour
of frantic disk-thrashing. I don't know if the change to silo is
deliberate or not, but for now I'm patching the script to use the bits
out of silo_1.2.5-2_sparc.deb instead, as that seems to have what we
need. If this is wrong, please shout!
--
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
We don't need no education.
We don't need no thought control.
signature.asc
Description: Digital signature
Re: Bug#104313: ytalk segfaults under sparc
On Wed, Jul 11, 2001 at 05:31:25PM +0200, Marcus Crafter wrote: >ffzj0ia9[/home/crafterm]:73>gdb ytalk >GNU gdb 2001-07-05-cvs (MI_OUT) >Copyright 2001 Free Software Foundation, Inc. >GDB is free software, covered by the GNU General Public License, and you are >welcome to change it and/or distribute copies of it under certain conditions. >Type "show copying" to see the conditions. >There is absolutely no warranty for GDB. Type "show warranty" for details. >This GDB was configured as "sparc-unknown-linux-gnu"... >(no debugging symbols found)... >(gdb) run >Starting program: /usr/bin/ytalk >(no debugging symbols found)...(no debugging symbols found)... >(no debugging symbols found)...(no debugging symbols found)... >(no debugging symbols found)... >Program received signal SIGSEGV, Segmentation fault. >0x in ?? () >(gdb) where >#0 0x in ?? () >#1 0x700ddfdc in _init () from /usr/X11R6/lib/libX11.so.6 >#2 0x700ddf8c in _init () from /usr/X11R6/lib/libX11.so.6 >#3 0x7000dec8 in call_init (l=0x7001a880, argc=1, argv=0xe5a4, >env=0xe5ac) at dl-init.c:70 >#4 0x7000e060 in _dl_init () at dl-init.c:87 >#5 0x70002f94 in _dl_start_user () at rtld.c:141 >(gdb) Hmmm. None of the symbols mentioned show up in ytalk at all; this would seem to be a bug somewhere else, at a guess the X libs. Does anybody on the sparc list have any idea about this? I'm a little lost... -- Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED] "It's actually quite entertaining to watch ag129 prop his foot up on the desk so he can get a better aim." [ seen in ucam.chat ] Finger for PGP key
Autobuilders - do we need more?
I've got a full mirror sat around at home at the moment, and a cable modem sat idle for significant amounts of time. I know the m68k buildds are struggling to keep up at the moment; are any of the other arches in a similar position? I'd love to be able to help here. I've even been offered a reasonably-specced Amiga 1200 to help with builds, if that will help. I don't know enough about m68k hardware to say for sure myself. I'm hoping to get hold of some other hardware soon, including a Sparc Ultra 5 and maybe an Arm of some description. Let me know how I can help... -- Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED] Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
Re: slink Packages file empty for sparc...
On Tue, 6 Jul 1999, Steve McIntyre wrote: >On 6 Jul 1999, James Troup wrote: > >>Richard Braakman <[EMAIL PROTECTED]> writes: >>> Hmm, this is due to three broken symlinks to sid: >>> >>> find: binary-sparc/admin/libnfslock_0.1-6.deb: No such file or directory >>> find: binary-sparc/admin/open_1.4-10.deb: No such file or directory >>> find: binary-sparc/sound/cdparanoia_3a9-1.deb: No such file or directory >> >>Woops, sorry. I've put these files back. > >OK, thanks. All seems to be going OK now. OK, cdimage now has two shiny new sparc 2.1r2 images that appear to be OK by inspection... Woo! -- Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/comp/>My PC page "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: slink Packages file empty for sparc...
On 6 Jul 1999, James Troup wrote: >Richard Braakman <[EMAIL PROTECTED]> writes: >> Hmm, this is due to three broken symlinks to sid: >> >> find: binary-sparc/admin/libnfslock_0.1-6.deb: No such file or directory >> find: binary-sparc/admin/open_1.4-10.deb: No such file or directory >> find: binary-sparc/sound/cdparanoia_3a9-1.deb: No such file or directory > >Woops, sorry. I've put these files back. OK, thanks. All seems to be going OK now. -- Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/>My home page "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: slink Packages file empty for sparc...
On Tue, 6 Jul 1999, Richard Braakman wrote: >Hmm, this is due to three broken symlinks to sid: > >find: binary-sparc/admin/libnfslock_0.1-6.deb: No such file or directory >find: binary-sparc/admin/open_1.4-10.deb: No such file or directory >find: binary-sparc/sound/cdparanoia_3a9-1.deb: No such file or directory > >I'm trying to locate these files. Do you have archives? Apologies, no... -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Oh My God! They Killed init! You Bastards! "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
slink Packages file empty for sparc...
I was just about to try to create some new sparc CD images and the run has failed again, this time because the Packages file for the main section on sparc is empty. I've checked and this is the case on master, not just on the mirror I'm using. Could somebody investigate please? -- Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~damerell/CUWoCS/CUWoCS.html>CUWoCS home page Cthulhu - Why vote for the Lesser Evil? "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Sparc problem - any answers???
I said earlier in the week: >> I've just started doing a new set of official sparc images on >> cdimage.debian.org and things are failing all over the place. I've checked >> up and the binary-sparc directories are full of sym-links to sid. Can >> somebody please explain this? At the moment this makes it impossible to >> make CDs... As a clarification, this means that the _released_ sparc _slink_ distribution is unstable. I'd be very surprised to hear that this is the case deliberately, and if so I'd love to hear the reasoning for it. That aside, I believe we need to fix this and soon. Comments? -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Oh My God! They Killed init! You Bastards! "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Re: MAJOR PROBLEM WITH SPARC CDS
[ftpmaster cc:ed] On Tue, 29 Jun 1999, Steve Dunham wrote: >Steve McIntyre <[EMAIL PROTECTED]> writes: > >> I've just started doing a new set of official sparc images on >> cdimage.debian.org and things are failing all over the place. I've checked >> up and the binary-sparc directories are full of sym-links to sid. Can >> somebody please explain this? At the moment this makes it impossible to >> make CDs... > >Talk to the ftp guys. I complained about this weeks before the >release of slink. This is a mess. And it means the sparc CDs we gave away at the Linux99 event last weekend are potentially badly broken. Is there any reason for the stable release tp have sym-links into unstable at all??? -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/comp/>My PC page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
MAJOR PROBLEM WITH SPARC CDS
I've just started doing a new set of official sparc images on cdimage.debian.org and things are failing all over the place. I've checked up and the binary-sparc directories are full of sym-links to sid. Can somebody please explain this? At the moment this makes it impossible to make CDs... -- Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/>My home page "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: 2.1_r0 install experience
On 10 Mar 1999, Mark W. Eichin wrote: >> Hmmm. If that's correct then it's a bug - the comment should say to run >> _dselect_ with the last binary CD in the drive, not to boot that way... > >Indeed, I misremembered. The comment was really from README.multicd, >and it very clearly says *after* you've done the install, etc. Sorry >about that... _Mark_ OK, thanks. You had me very worried for a minute then... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
Re: 2.1_r0 install experience
Mark Eichin writes: >another minor nit: one of the install docs suggests that one should >boot off of the last binary cd in your set - so disk 1/1, 2/2, or 2/4 >(in the set that is 2 bin + 2 src.) binary-sparc-2 doesn't appear to >be bootable, though - or at least, it has no /boot and no >disks-sparc. (As mentioned earlier I can't boot ISO disks on my >machine anyway.) Probably the doc should be changed, though there's >plenty of room on b-s-2 if we wanted to make it bootable as well... Hmmm. If that's correct then it's a bug - the comment should say to run _dselect_ with the last binary CD in the drive, not to boot that way... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/comp/>My PC page "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: E450 supported?
3c875-1: on-chip RAM at 0x1ff80011000 ncr53c875-1: restart (scsi reset). ncr53c875-1: Downloading SCSI SCRIPTS. scsi0 : ncr53c8xx - revision 3.1f scsi1 : ncr53c8xx - revision 3.1f scsi : 2 hosts. Vendor: TOSHIBA Model: XM5701TASUN12XCD Rev: 0997 Type: CD-ROM ANSI SCSI revision: 02 Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0 Vendor: IBM Model: DDRS34560SUN4.2G Rev: S98E Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi1, channel 0, id 0, lun 0 Vendor: SEAGATE Model: ST34371W SUN4.2G Rev: 7462 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdb at scsi1, channel 0, id 1, lun 0 Vendor: SEAGATE Model: ST34371W SUN4.2G Rev: 7462 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdc at scsi1, channel 0, id 2, lun 0 ncr53c875-1-<0,0>: tagged command queue depth set to 8 ncr53c875-1-<1,0>: tagged command queue depth set to 8 ncr53c875-1-<2,0>: tagged command queue depth set to 8 scsi : detected 1 SCSI cdrom 3 SCSI disks total. ncr53c875-0-<6,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 8) Uniform CDROM driver Revision: 2.52 ncr53c875-1-<0,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 15) SCSI device sda: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB] [4.1 GB] ncr53c875-1-<1,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 15) SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB] [4.1 GB] ncr53c875-1-<2,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 15) SCSI device sdc: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB] [4.1 GB] sunhme.c:v1.10 27/Jan/99 David S. Miller ([EMAIL PROTECTED]) eth0: HAPPY MEAL (PCI/CheerIO) 10/100BaseT Ethernet 08:00:20:90:cb:59 Partition check: sda: sda1 sda2 sda3 sda4 sda6 sda7 sda8 sdb: sdb2 sdb3 sdb7 sdc: sdc1 sdc2 sdc3 sdc4 sdc6 sdc7 sdc8 You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|44bsd|old|next|openstep >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old ufs_read_super: bad magic number Kernel panic: VFS: Unable to mount root fs on 01:00 Press L1-A to return to the boot prom -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
E450 supported?
I've just tried a newly-written 2.1 sparc boot CD on our twin-CPU Enterprise 450 at work, mainly as a test of the intelsilo stuff Steve Dunham gave me. It seemed to work quite well, then failed. Some of the boot messages below, ask if you need to see more. Is this a real problem with the CD, with Linux sparc support, or something else? ncr53c875-1: rev=0x03, base=0x1ff8001, io_port=0xf9fe02010400, irq=3,7e0 ncr53c875-1: NCR clock is 40218KHz, 40218KHz ncr53c875-1: ID 7, Fast-20, Parity Checking ncr53c875-1: on-chip RAM at 0x1ff80011000 ncr53c875-1: restart (scsi reset). ncr53c875-1: Downloading SCSI SCRIPTS. scsi0 : ncr53c8xx - revision 3.1f scsi1 : ncr53c8xx - revision 3.1f scsi : 2 hosts. Vendor: TOSHIBA Model: XM5701TASUN12XCD Rev: 0997 Type: CD-ROM ANSI SCSI revision: 02 Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0 Vendor: IBM Model: DDRS34560SUN4.2G Rev: S98E Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi1, channel 0, id 0, lun 0 Vendor: SEAGATE Model: ST34371W SUN4.2G Rev: 7462 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdb at scsi1, channel 0, id 1, lun 0 Vendor: SEAGATE Model: ST34371W SUN4.2G Rev: 7462 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sdc at scsi1, channel 0, id 2, lun 0 ncr53c875-1-<0,0>: tagged command queue depth set to 8 ncr53c875-1-<1,0>: tagged command queue depth set to 8 ncr53c875-1-<2,0>: tagged command queue depth set to 8 scsi : detected 1 SCSI cdrom 3 SCSI disks total. ncr53c875-0-<6,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 8) Uniform CDROM driver Revision: 2.52 ncr53c875-1-<0,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 15) SCSI device sda: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB] [4.1 GB] ncr53c875-1-<1,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 15) SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB] [4.1 GB] ncr53c875-1-<2,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 15) SCSI device sdc: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB] [4.1 GB] sunhme.c:v1.10 27/Jan/99 David S. Miller ([EMAIL PROTECTED]) eth0: HAPPY MEAL (PCI/CheerIO) 10/100BaseT Ethernet 08:00:20:90:cb:59 Partition check: sda: sda1 sda2 sda3 sda4 sda6 sda7 sda8 sdb: sdb2 sdb3 sdb7 sdc: sdc1 sdc2 sdc3 sdc4 sdc6 sdc7 sdc8 You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|44bsd|old|next|openstep >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old ufs_read_super: bad magic number Kernel panic: VFS: Unable to mount root fs on 01:00 Press L1-A to return to the boot prom -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.rpg-soc.ucam.org/curs/>CURS home page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Re: Sparc status and Re: Sparc progress
On Mon, 8 Mar 1999, Christian Meder wrote: >sorry for my absence during the past week. My girlfriend and I got a >small baby boy on Wednesday which mixed up my timetable. I guess >that's a usual feature of children that they mix up your life ;-) :-) Congratulations on becoming a dad. -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.rpg-soc.ucam.org/curs/>CURS home page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
slink CDs
i386 and m68k are done on cdimage, ready to go. Steve Dunham is rsyncing the sparc images onto there right now. Loic, are you doing the alpha images? Hopefully we're going to be sorted now and out on Tuesday. I'd suggest a party but all I want now is sleep... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] Also available from [EMAIL PROTECTED] "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: Releasing Slink
On 7 Mar 1999, Steve Dunham wrote: >Steve McIntyre <[EMAIL PROTECTED]> writes: > >> Steve Dunham writes: > >> >So, when do you want a CD image. Assuming the other archs have >> >stopped uploading new stuff, the last thing we _need_ for sparc is for >> >console-tools to be installed from incoming into the distribution. > >> Ick... > >It made it into the dist yesterday. OK, good. >> >Now depending on how rushed we are for time, I can merge this into my >> >mirror manually and generate the CD images, or I can wait till it is >> >installed on master and then rsync and generate the CD images. >> >(Assuming that dinstall picks it up today, it will be 1800 EST or >> >later - dinstall runs at 1500 EST and "masterfiles", a long process, >> >runs after dinstall is done.) > >> Hmmm. That's probably a bit late. I'd like to have all the images done and >> on cdimage by the end of today (Sunday) GMT to give the mirrors Monday to >> get the images. If you can do it by hand, then I guess... > >Those times were on saturday. I'm running md5list right now, and just >finished blanking the CDRW. The image I prepared last night didn't >work because the silo stuff is broken in slink_cd 1.10 and 1.11, it >mounted the old image and installed silo on the new one. I'll mail >you a patch for all of the silo woe as soon as this new image is built >and burned. OK, thanks. And if it's not imposing too much, have you made any progree on non-sparc silo? >I don't have a cdimage account. For the pre1 images I just gave Phil >Hands a rsync address and password. Whoever transfers these new >images to cdimage, should copy the old ones into the place for the new >one and then do an rsync with a large block size. OK... Or alternatively - do you want an open account? While Phil is away, Glen is in charge and can do these things... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] Use Debian GNU/Linux - upgrade your Windoze box today! http://www.debian.org/ "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Sparc progress
I'm still seeing the following package errors on a CD build run. Do we pull them? virgo:~/debian/slink_cd/slink_cd-1.11$ ./pkg-order --check-recommends --nocheck-conflicts --nooutput-order /debian/local/slinkcd-sparc/Packages-all == Failed: Package: dia libglib1.1(>= 1.1.3-2.1) Package: ivtools-dev ivtools(= 0.6.7-7) Package: libcompface1 libc5(>= 5.4.0.0) Package: libdl1-altdev libc5-altdev(>= 5.4.0-0) Package: libwcsmbs libc6(<< 2.0.8) == == Unknown: Package: dialdcost diald Package: econfigedit libgtk-imlib-perl(>= 0.3-3) Package: felt-doc felt Package: gstep-base-examples gstep-base-dev(= 0.5.0.981229-1) Package: iceconf libgtk-perl Package: libdb1-dev libc5-dev Package: palm-doctoolkit palmpython(>= 0.5.2) Package: pilot-manager pilot-link-perl Package: python-history python-numeric python-pdb Package: wml eperl(>= 2.2.14-0.1) == 16 Critical errors encountered. Exiting. -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Also available from [EMAIL PROTECTED] "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Re: Documentation issues in disks-2.1.8.1
Steve Dunham writes: >FYI, I've created an arch-specific README.1ST for the sparc, modeled >after the i386 one: > >README for Debian 2.1 CD installation. >== [snip] Great... -- Steve McIntyre, [EMAIL PROTECTED] The Unix world's best mod player http://www.chiark.greenend.org.uk/~stevem/mikmod/>MikMod "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: Releasing Slink
Steve Dunham writes: >Steve McIntyre <[EMAIL PROTECTED]> writes: > >> The slink release has been a mess, culminating in a last-minute "sorry, we >> missed it again" announcement. If we're going to release properly next >> Tuesday at 00:00 GMT, then we need a schedule like the following: > >> 1. Fixes needed for each set allowed in Tue, Wed, Thu and then _no more >>uploads_ for any reason. At all. None. > >Sparc is slightly broken. A new console-tools was uploaded Wednesday, >dinstall, as usual, deleted the old binary-all "console-tools-data" >package, breaking console-tools on the sparc. I didn't notice this >until I ran slink_cd late friday night. > >I've uploaded a sparc binary for the console-tools that is currently >in slink (for all of the other architectures.) > >So, when do you want a CD image. Assuming the other archs have >stopped uploading new stuff, the last thing we _need_ for sparc is for >console-tools to be installed from incoming into the distribution. Ick... >Now depending on how rushed we are for time, I can merge this into my >mirror manually and generate the CD images, or I can wait till it is >installed on master and then rsync and generate the CD images. >(Assuming that dinstall picks it up today, it will be 1800 EST or >later - dinstall runs at 1500 EST and "masterfiles", a long process, >runs after dinstall is done.) Hmmm. That's probably a bit late. I'd like to have all the images done and on cdimage by the end of today (Sunday) GMT to give the mirrors Monday to get the images. If you can do it by hand, then I guess... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~damerell/CUWoCS/CUWoCS.html>CUWoCS home page Cthulhu - Why vote for the Lesser Evil? "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
slink_cd 1.11
On chiark... slink-cd (1.11) unstable; urgency=low * Mainly last-minute cleanups for final CD builds. * slink_cd changes: * Changed boot target slightly, less warnings on non-i386. * Now using new isomarkboot, new options. * others: * Added sysutils and dpkg-perl to list of requirements in README. * Added exclude details to README. * boot-alpha changes from Loic. * moved some i386-specific boot stuff to boot-i386. * Fixed several small bugs/typos in boot-m68k. * Added amiga .info files in boot-m68k, and tar file from Christian. * Updated master file. * Exclude support in mklist. * Added exclude-$ARCH files. * Fixed mklist bug - check right location for newer files. * -- Steve McIntyre <[EMAIL PROTECTED]> Sun, 07 Mar 1999 00:40:33 - -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/comp/>My PC page "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: CDs
On 6 Mar 1999, Steve Dunham wrote: >Steve McIntyre <[EMAIL PROTECTED]> writes: > >> On Sat, 6 Mar 1999, Steve Dunham wrote: > >> >Steve McIntyre <[EMAIL PROTECTED]> writes: > >> >> So, where are we up to for sparc/alpha. The m68k stuff is sorted now, as >> >> is the i386. Where have we got to on fixing the last few dependencies? >> >> I've added "exclude" support to slink_cd as a last-miute hack to allow us >> >> to simply lose any final problem packages, I'll be sending this out >> >later. >> >> I'm going to be building the m68k, i386 and source CD images overnight on >> >> cdimage.debian.org ready for people to test them... > >> >How exactly does "exclude" work? Does it rebuild all of the Packages >> >files or just the master ones for the CD? > >> Just the ones for the CD. It works as a modifier in the genlist stage - >> where it used to check for which of the first 2 CDs a main package should >> go on, there's now a third option EXCLUDED where the package will simply >> be ignored. The syntax is simple - exclude-$ARCH should list package >> names. > >Ok. When does the CD need to be ready? There is one last binary >sparc package in incoming, to sync up with the versions in other >architectures. I can manually merge it into my local archive and >generate the CDs now, or I can wait until dinstall and generate the >CDs late tonight (circa 1800 EST). It's probably better to wait... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] "It's actually quite entertaining to watch ag129 prop his foot up on the desk so he can get a better aim." [ seen in ucam.chat ] Finger for PGP key
Re: CDs
On Sat, 6 Mar 1999, Steve Dunham wrote: >Steve McIntyre <[EMAIL PROTECTED]> writes: > >> So, where are we up to for sparc/alpha. The m68k stuff is sorted now, as >> is the i386. Where have we got to on fixing the last few dependencies? >> I've added "exclude" support to slink_cd as a last-miute hack to allow us >> to simply lose any final problem packages, I'll be sending this out >later. >> I'm going to be building the m68k, i386 and source CD images overnight on >> cdimage.debian.org ready for people to test them... > >How exactly does "exclude" work? Does it rebuild all of the Packages >files or just the master ones for the CD? Just the ones for the CD. It works as a modifier in the genlist stage - where it used to check for which of the first 2 CDs a main package should go on, there's now a third option EXCLUDED where the package will simply be ignored. The syntax is simple - exclude-$ARCH should list package names. -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/comp/>My PC page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
CDs
So, where are we up to for sparc/alpha. The m68k stuff is sorted now, as is the i386. Where have we got to on fixing the last few dependencies? I've added "exclude" support to slink_cd as a last-miute hack to allow us to simply lose any final problem packages, I'll be sending this out later. I'm going to be building the m68k, i386 and source CD images overnight on cdimage.debian.org ready for people to test them... -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Oh My God! They Killed init! You Bastards! "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
CDs: where are we up to?
I previously said: >The slink release has been a mess, culminating in a last-minute "sorry, >we missed it again" announcement. If we're going to release properly next >Tuesday at 00:00 GMT, then we need a schedule like the following: > >1. Fixes needed for each set allowed in Tue, Wed, Thu and then _no more > uploads_ for any reason. At all. None. We've had some fixes going in; we need to decide on actions for the remaining missing/broken packages that have been flagged. Where are we on each platform right now? >2. Starting _now_ we have people building CD images for each platform. > These will need to be re-done again later as uploads are made, but we > need feedback _now_ if there are any missing packages or other CD image > problems. I've seen some feedback here, but not very much... >3. On Friday final images are made for each of the release architectures. > I can do i386 and source, we need volunteers for m68k, alpha and sparc. > Let us know ASAP if you can help.. Steve, you willing to do sparc still? > In theory, one person could do all of them, but in practice this just > does not work. And these need to be sanity checked before we pronounce > them ready to go. OK, I'll have i386 and source covered. Steve Dunham has sparc covered (thanks!). M68k/alpha? Anybody? If it comes to the crunch I can _possibly_ do these, but I will have no way to test them. And these are still to come. >4. The 4 image maintainers(?) mail me Friday/Saturday to report progress, > let me know when we have images ready to go. At that point I get them > onto cdimage.debian.org so they can be mirrored worldwide ready for the > end of Monday - this takes a _long_ time for ~7GB of image files. > >5. At 00:00 GMT on Tuesday the 9th March we announce release to the world; > images are already on mirrors ready to be downloaded and those of us > selling CDs will have copies ready to go in the mail. -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/comp/>My PC page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Missing from sparc
Just run slink_cd and these errors came out: virgo:~/slink_cd-1.09$ echo $TDIR; echo $ARCH ; ./pkg-order --nocheck-conflicts --nooutput-order $TDIR/Packages-all /debian/local/slinkcd-sparc sparc == Failed: Package: dia libglib1.1(>= 1.1.3-2.1) Package: ivtools-dev ivtools(= 0.6.7-7) Package: libcompface1 libc5(>= 5.4.0.0) Package: libdl1-altdev libc5-altdev(>= 5.4.0-0) Package: libwcsmbs libc6(<< 2.0.8) == == Unknown: Package: dialdcost diald Package: econfigedit libgtk-imlib-perl(>= 0.3-3) Package: felt-doc felt Package: gstep-base-examples gstep-base-dev(= 0.5.0.981229-1) Package: iceconf libgtk-perl Package: libdb1-dev libc5-dev Package: palm-doctoolkit palmpython(>= 0.5.2) Package: pilot-manager pilot-link-perl Package: python-history python-numeric python-pdb Package: wine-doc wine Package: wml eperl(>= 2.2.14-0.1) == 17 Critical errors encountered. Exiting. wine/wine-doc is a known pain that I'm ignoring for now. Others? -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
Releasing Slink (was Re: Please add new version of Release-Notes)
On Tue, 2 Mar 1999, Johnie Ingram wrote: >"Adam" == Adam Di Carlo <[EMAIL PROTECTED]> writes: > >Steve> If we have another week, then I'd say pull the images for now >Steve> while we re-think things. > >Adam> Why wait? I'm a little nervous by how little testing the CDs >Adam> have gotten compared to hamm. I know you guys have done a great >Adam> job but my sense was that with phil's efforts for slink, the If we leave the images around now, people like CD vendors will end up using them by mistake, and then we end up with inconsistent stuff out there. And there has been a lot of testing, just not so much in the way of testing "official" images as last time. >I'm going to set up a US mirror of the images again, so that should >provide more testers for this final week. Cheers. >Incidentially I can't build the images here -- I get 2 "critical >errors" that pppconfig and alsa-modules (iirc) depend on whiptail >which is on disc #2. OK, I'm checking into this. [ Not aimed at netgod, but you're here... :-) ] The slink release has been a mess, culminating in a last-minute "sorry, we missed it again" announcement. If we're going to release properly next Tuesday at 00:00 GMT, then we need a schedule like the following: 1. Fixes needed for each set allowed in Tue, Wed, Thu and then _no more uploads_ for any reason. At all. None. 2. Starting _now_ we have people building CD images for each platform. These will need to be re-done again later as uploads are made, but we need feedback _now_ if there are any missing packages or other CD image problems. 3. On Friday final images are made for each of the release architectures. I can do i386 and source, we need volunteers for m68k, alpha and sparc. Let us know ASAP if you can help. Steve, you willing to do sparc still? In theory, one person could do all of them, but in practice this just does not work. And these need to be sanity checked before we pronounce them ready to go. 4. The 4 image maintainers(?) mail me Friday/Saturday to report progress, let me know when we have images ready to go. At that point I get them onto cdimage.debian.org so they can be mirrored worldwide ready for the end of Monday - this takes a _long_ time for ~7GB of image files. 5. At 00:00 GMT on Tuesday the 9th March we announce release to the world; images are already on mirrors ready to be downloaded and those of us selling CDs will have copies ready to go in the mail. Comments? We _can_ do this, but we need to be organised. I'll be sending out a separate mail later listing the problems I've seen us have this release, and ways that can we can improve for in future. The key thing here will be to keep producing the install/release stuff all the way through potato, and not just in the last couple of weeks... Talk to me... -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.rpg-soc.ucam.org/curs/>CURS home page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
CD images for release
Hopefully the mirrors are in sync and we're ready to go tonight. i386 images are easy - Phil, can you sort those please? And the source images are probably easiest for you, too. And if you can sort out making copies of the other images, cdimage.debian.org would be the best place to advertise I guess... Steve Dunham has sparc images sorted, yes? If not, we may be able to help in Cambridge. And m68k/alpha people - who wants to do the images for those? In theory both can be done on an i386, unless I'm missing something. But it's probably worth doing last-minute sanity checks on them. Let's put this thing to bed. I won't be able to join the IRC party, I'm afraid, but I hope the rest of you that do have a good time...! Yours, a very tired Steve. -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Also available from [EMAIL PROTECTED] "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Re: Silo
On Sun, 28 Feb 1999, Steve Dunham wrote: >> Hmmm, OK... That does sound weird. If it makes life easier I can easily >> change that upstream too... > >The error, from dpkg-deb, was something along the lines of "Can't make >temporary file: invalid filename". Hmmm. I've changed upstream to match your change. >Ok, with "master" installed I'm getting: > > Total extents scheduled to be written = 280038 > >That's 547MB. >The second disk is 394MB. OK, that looks a lot better for CD 1. But CD 2 is still small, unless you're missing chunks of contrib. >(BTW, CDRW is a life-saver for testing these things.) *grin* Yes... >I'm going to move the image over to an intel machine and test >intelsilo on it. Great. Let me know how you get on... -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Also available from [EMAIL PROTECTED] "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Re: Intel silo (Re: Silo)
On Sun, 28 Feb 1999, Steve Dunham wrote: >> Hmmm. Any idea where to look? I had a quick look using Altavista, and it >> just bounced me to the redhat sparc mailing list archives, which didn't >> appear to be of much use. > >It builds out of the box, but there is a slight catch. It must be >built in a tree that has already been built on a sparc. > >I put a package up at "http://www.cse.msu.edu/~dunham/debian/silo/";. >To build the source package, you must do: > > dpkg-buildpackage -rfakeroot -m"your email" > >on a sparc, and then > > rm build > dpkg-buildpackage -B -nc -rfakeroot -m"your email" > >on the intel box (in the same tree). > >I will coordinate with the silo maintainer to get these changes into >potato. OK, good. >Note that before anyone starts handing out CDs made with intelsilo, we >must test it first (e.g. make a CD on an intel box and boot it on a >sparc). I'm hoping we can do that very soon... >To use it with slink_cd, you need BOOTDIR=/usr/lib/silo, and you need >the following patch to slink_cd: > >--- slink_cdSat Feb 27 20:22:12 1999 >+++ slink_cd.newSun Feb 28 11:46:57 1999 >@@ -1153,7 +1153,7 @@ >if [ "$EXECARCH"x = "sparc"x ]; then >siloprog=silo >elif [ "$EXECARCH"x = "i386"x ]; then >- siloprog=$BASEDIR/intelsilo >+ siloprog=intelsilo >fi >if [ -n "$siloprog" ]; then >cd1=/boot/debian.txt OK, done for 1.09. -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/>My home page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Re: Silo
On Sun, 28 Feb 1999, Steve Dunham wrote: >> Hmmm. Any idea where to look? I had a quick look using Altavista, and it >> just bounced me to the redhat sparc mailing list archives, which didn't >> appear to be of much use. > >There is a binary on Jakub's site (ultra.linux.cz). I could try >making one from the latest version of silo... That would be useful, thanks. >> >I'm now set up to generate CD Images. I mirrored master today, and >> >generated a set of CD images. The file sizes are: > >> >slink1.raw 309188608 >> >slink2.raw 676298752 >> >slink5.raw 391374848 > >> >I'm going to tweak the slink1.useful list to push the bulk of the main >> >packages onto the first CD. (I'm not sure why so few packages are >> >going onto the first CD...) > >> I'm curious, too - can you send me your lists? > >Turns out that /archive/tmp/slink1.needed is empty. After looking at >the slink_cd script, I realized that the file "master" was missing... Ah! OK, that was the last file that I missed out of the .deb. From now on I'm not going to list files explicitly - the .deb will get *. >Also, I was having some weird problems because I was setting the >TMPDIR environment variable. Apparently this causes "dpkg-deb" to >break. (This could be a libc6_2.1 issue.) I changed the variable >name to TDIR in my copy of slink_cd. Hmmm, OK... That does sound weird. If it makes life easier I can easily change that upstream too... -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.rpg-soc.ucam.org/curs/>CURS home page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
slink_cd about ready to go
OK, we should now be able to produce working installable CDs for all 4 arches, assuming the mirrors are up to date and the last few missing packages are compiled up. Woo! I've got install stuff from all the boot-floppy teams. Thanks for all the hard work guys... Just a last couple of things to make this look really good for release: I've got README.1ST files for m68k and i386 - _small_ text files giving people a quick start, or a pointer to longer docs. I've attached them here for reference. Can somebody from each of sparc and alpha please give me similar ones for those? Is there any way of getting silo to work on platforms other than sparc? Otherwise the images will always have to be made on sparcs. And similarly for alpha - I have an i386-specific version of isomarkboot, but no source or binaries for other platforms. And I believe that's it. I'll have slink_cd 1.09 out later today. And then I'm going to go to bed. For a week. I'm hitting a tight deadline at work this week (which is why I'm in at the weekend), on top of the slink release. Argh! -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Also available from [EMAIL PROTECTED] "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..." README for Debian 2.1 CD installation. == If you have a BVME 4000 or 6000, you can boot the installation system from CD. You will need to insert CD#1 in your CD-ROM drive and reboot. If your system will not boot from CD, you should run the appropriate installation program for your system. They are in subdirectories of install for each platform (amiga, atari, mac, vme). See \install\install.txt for more information. Some more detailed notes about this CD set are in \README.m68k. Also check \README.multicd for last-minute information about the multi-cd installation method. Chris Lawrence <[EMAIL PROTECTED]> 12 Feb 1999 README for Debian 2.1 CD installation. == To boot the installation system from CD, you will need to insert either CD#1 or CD#2 in your CD-ROM drive and reboot. CD#1 contains a normal kernel that should work for most people and contains many drivers. CD#2 is a smaller system based on the "tecra" kernel - this is smaller because it has fewer drivers compiled in to avoid a known problem with large kernels on laptops, especially the Toshiba Tecra series. If your system will not boot from CD, there are other options: 1.Boot a DOS system with CD drivers, then run boot.bat from the \install direcory on the first CD. 2.Make boot floppies from the images on the first CD, in the directory \dists\stable\main\disks-i386\current. The program rawrite2.exe in that directory will write the floppy images under DOS. e.g. d: (change to the CD drive) cd \dists\stable\main\disks-i386\current rawrite2 -f resc1440.bin -d a: (a: is the 1.44 MB floppy drive) See \install\install.txt for more information, and \README.multicd for last-minute information about the multi-cd installation method. Steve McIntyre <[EMAIL PROTECTED]> 15 Feb 1999
Re: Silo
On Sun, 28 Feb 1999, Steve Dunham wrote: >> I honestly don't know myself. Anybody? > >You can't build silo on i386. There is a program somewhere called >"intelsilo", but it's not in debian, and it might need tweaking to >work. Also, you must use the "second.b" file from the silo in >incoming, or the CD will fail to boot on a large subset of machines. Hmmm. Any idea where to look? I had a quick look using Altavista, and it just bounced me to the redhat sparc mailing list archives, which didn't appear to be of much use. >I'm now set up to generate CD Images. I mirrored master today, and >generated a set of CD images. The file sizes are: > >slink1.raw 309188608 >slink2.raw 676298752 >slink5.raw 391374848 > >I'm going to tweak the slink1.useful list to push the bulk of the main >packages onto the first CD. (I'm not sure why so few packages are >going onto the first CD...) I'm curious, too - can you send me your lists? >I still want the packages in incoming (kernel-* and silo-*) to make it >into the archive before making the final images, and Eric said he was >going to do a final run of boot floppies on Monday. Cool. -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/comp/>My PC page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Re: slink_cd - progress
On 27 Feb 1999, Steve Dunham wrote: >Steve McIntyre <[EMAIL PROTECTED]> writes: > >> or lack of it, even. My mirror is currently broken because of the removal >> of the hamm sym-links, so I'm struggling to make any progress at all - >> it's a bit difficult to test things when the files underneath me are still >> moving... > >> Hopefully the i386 and sparc things will all >> work, but I'm going to be pushed to get my stuff working for the m68k and >> alpha ports by Tuesday, let alone get images built in time for people to >> mirror them. > >I'm currently doing a mirror of all of the sparc stuff off of master >on the assumtion that I have to do the sparc CD images - is this true? You don't _have _ to, but it would be great if you can, yes. >If so, I need to know which images are needed (e.g. just the two >binary disks or a complete set?), where I should put them, and when >are they needed? Just the two binary ones, I think - the common source ones we can cope with, and the layout of them is not quite so crucial... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~damerell/CUWoCS/CUWoCS.html>CUWoCS home page Cthulhu - Why vote for the Lesser Evil? "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: Silo
On Sat, 27 Feb 1999, M.C. Vernon wrote: > I need this to make sparc images, but it doesn't seem to be >available for the i386 architecture. Is it worth grabbing it and building >it; or will it not work at all? I honestly don't know myself. Anybody? -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] "Whenever you eat, chew" "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: missing/back revved unstable packages
Stephen Zander writes:
>Does someone have a stash of packages for unstable just lying around
>waiting for the Official Release before uploading, or should I just
>start filling in the gaps as I run into them?
>
>I seem to recall Steve {Dunham,McIntyre} mentioning that they hadf
>done a dbuild session but can't seem to find any mention of it now...
I haven't done a dbuild run, but I have had notice of a CD build run fail
with the following:
> Package: ivtools-dev
> ivtools(= 0.6.7-7)
> Package: debiandoc-sgml
> sp
> Package: dialdcost
> diald
> Package: docbook-stylesheets
> jade
> Package: dome
> libg++2.8.2
> Package: emacs20-el
> emacs20(= 20.3-7)
> Package: emacspeak
> emacs20
> tclx76
> tclx75
> tclx74
> tclx
> Package: felt-doc
> felt
> Package: gnome-admin
> gnome-core(>= 0.30-0)
> Package: gnome-games
> gnome-core(>= 0.30-0)
> Package: gnome-gxsnmp
> gnome-core(>= 0.30-0)
> Package: gnome-media
> gnome-core(>= 0.30-2)
> Package: jadetex
> jade(>= 1.2-1)
> Package: python-elisp
> emacs20
> xemacs19
> xemacs20-bin
> Package: r-cran
> r-base(>= 0.62.2)
> Package: sgml-tools
> sp(>= 1.1.1-3)
> Package: w3-el-e20
> emacs20(<= 20.3-100)
>23 Critical errors encountered. Exiting.
--
Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED]
http://www.rpg-soc.ucam.org/curs/>CURS home page
"Can't keep my eyes from the circling sky, +--
"Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: One more slink_cd patch for the sparc
On Fri, 26 Feb 1999, Steve McIntyre wrote: >Hmmm. I have that already: > ># put the relevant parts of SILO boot loader >mkdir -p boot1/boot >cp -p $BOOTDIR/cd.b $BOOTDIR/second.b boot1/boot >cat - > boot1/boot/silo.conf << __EOF__ >message=!cd1 >timeout=300 >root=/dev/ram >image[sun4c,sun4d,sun4m]=!cd2 > label=linux > initrd=!cd5 >image[sun4u]=!cd4 > label=linux > initrd=!cd5 >image[sun4c,sun4d,sun4m]=!cd3 > label=linux-2.2 > initrd=!cd5 >image[sun4u]=!cd4 > label=linux-2.2 > initrd=!cd5 >__EOF__ or is your patch reversed? -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.rpg-soc.ucam.org/curs/>CURS home page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
Re: One more slink_cd patch for the sparc
On Fri, 26 Feb 1999, Steve Dunham wrote: >One final patch needed for the sparc: > >--- slink_cd.oldFri Feb 26 00:52:01 1999 >+++ slink_cdFri Feb 26 00:52:54 1999 >@@ -1028,6 +1028,7 @@ >cat - > boot1/boot/silo.conf << __EOF__ > message=!cd1 > timeout=300 >+root=/dev/ram > image[sun4c,sun4d,sun4m]=!cd2 >label=linux >initrd=!cd5 Hmmm. I have that already: # put the relevant parts of SILO boot loader mkdir -p boot1/boot cp -p $BOOTDIR/cd.b $BOOTDIR/second.b boot1/boot cat - > boot1/boot/silo.conf << __EOF__ message=!cd1 timeout=300 root=/dev/ram image[sun4c,sun4d,sun4m]=!cd2 label=linux initrd=!cd5 image[sun4u]=!cd4 label=linux initrd=!cd5 image[sun4c,sun4d,sun4m]=!cd3 label=linux-2.2 initrd=!cd5 image[sun4u]=!cd4 label=linux-2.2 initrd=!cd5 __EOF__ -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Also available from [EMAIL PROTECTED] "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
slink_cd: still waiting on final boot/install setup
[ Apologies again for the major cross-post; things are getting tight and we're still missing bits. ] STATUS == Slink_cd 1.07 is out as of last night; I've made tiny changes that can become 1.08 very soon. The state of play for release is: We have working beta i386 CD images available (thanks Phil). These have been tested already, check cdimage.debian.org for more info and mirror locations. The sparc boot/install stuff is apprently sorted now, and the work needed for this went into slink_cd yesterday. Thanks Steve, Eric and others. Can somebody write a README.1ST.sparc on similar lines to the i386/m68k versions please? I've been sent docs and I know there are sets of boot disks with the m68k people, but there's still no slink_cd support for them yet. On the alpha front, I've seen/heard _nothing_ about boot/install stuff. Is anything happening out there? If we're going to get a chance to get this stuff done we need it _now_. LAYOUTS === The official CD layouts will be quite simple: CD 1: main binary section 1, bootable where possible . Will work standalone, dependencies are being checked to make sure of this. CD 2: main binary section 2, bootable where possible. Also contains contrib section (binary and source). These 2 discs should work as they are, no unmet dependencies for main section, maybe some contrib -> non-free. Non-US is _not_ going on the official disks. CD 3: main source section 1, arch-independent CD 4: main source section 2, arch-independent The official CD set should contain all of the above. Complete binary sets for each architecture will work, using CDs 1 and 2. And single disk versions may be made, using just CD 1. The multicd method will cope with these without complaint, using a simple hack in slink_cd: the Packages.cd files on each CD will only know about the packages on itself and any prior CDs: CD 1 is standalone CD 2 knows about CD 1, CD 2. (optional, non-official non-free) CD 5 will know about CD 1, CD 2, CD 5. The end user just needs to be told to insert the _last_ binary CD first when running dselect update. I can see we'll need 2 binary CDs for each of 4 arches, plus 2 source CDs, making 10 images in total. As the images are ~550-650 MB each, I'd guesstimate we need approx. 6 GB of archive space for them all on mirrors. The option of having a single CD that will install and work alone is IMHO quite important - it can make life easier/cheaper for distributors, and for us at shows when we give them out etc... TODO slink_cd 1.08 is ready to go as a final version; I just need some instructions/patches/docs from certain groups, especially the alpha team. I'm hoping to get slink_cd itself into the archive in time to make the slink release - it's all architecture-independent and is already tested, so there should be no problems there I hope. But of course, it'll have to be in contrib as always because it depends on unzip/lha etc... -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/comp/>My PC page "Can't keep my eyes from the circling sky, "Tongue-tied & twisted, Just an earth-bound misfit, I..."
slink_cd v 1.07 out
At the usual place: http://www.chiark.greenend.org.uk/~stevem/DebianCD/ Changes from 1.06: slink-cd (1.07) unstable; urgency=low * slink_cd changes: * Build slink1.needed from "master" file from boot-floppies. * Now uses pkg-order to check dependencies - check CD 1 doesn't depend on any others, then check ALL Depends: and Recommends: . Fail if CD 1 fails, if the whole set fails then either a) give a warning about this if we haven't included non-free or non-US (it's reasonable - contrib depends on non-free) b) fail if we have. * Added work-around for broken metro-motif-man package for the pkg-order step. * Added upgrade-2.0-i386 and upgrade-older-i386 links at top-level. * Removed upgrade-i386 at top level. * Added latest sparc patch from Steve Dunham <[EMAIL PROTECTED]> * others: * Added README.1ST.m68k from Chris Lawrence <[EMAIL PROTECTED]>. * Removed slink1.needed from package, replaced with master. * Added more upgrade stuff to slink1.list. -- Steve McIntyre <[EMAIL PROTECTED]> Mon, 22 Feb 1999 18:38:50 - -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] http://www.chiark.greenend.org.uk/~stevem/>My home page "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Re: Gnome-apt for sparc (Re: slink release (and status discussion))
Steve Dunham writes: > >Oh yeah, and back on topic: I have a patch for slink_cd, but I want to >upgrade to the latest version of slick_cd and test it before I hand >out patches. I'll have it tested by the end of the week. (After >Anders' X packages make it into the archive, I'll make some test >images available.) Please, if you have patches for slink_cd pass them along and I'll help you with them and get them in more quickly... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] http://www.rpg-soc.ucam.org/curs/>CURS home page "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
slink_cd v 1.06 released
As usual, at http://www.chiark.greenend.org.uk/~stevem/DebianCD/ Please give feedback; hopefully we're about there for release, but I still need instructions on how to create useable CDs for all arches, and we will need these testing too... Changes from 1.05: slink-cd (1.06) unstable; urgency=low * slink_cd changes: * handle non-US links better * Copy Release Notes onto all CDs * Create README.1ST - lists slink_cd version, creation date, disk label (from .disk/info) and gives simple instructions on what to do to run the installation system. * Copy the full set of files for the installation manual to /install. * Add sym-links for the installation manual into /doc. * Added hfs.map stuff for Apple people. * Added $MKISOFS_OPTS_DISC support, makes life easier for special mkhybrid requirements for different arches. * others: * Changed the default volid for each disk to be "Debian-ARCH 2.1 Disc " * Created README.1ST.i386 - template for README.1ST above. * Removed test genlinks option from arch. * Added hfs.map for Apple people * Added mkisofsrc to packaging. -- Steve McIntyre <[EMAIL PROTECTED]> Thu, 11 Feb 1999 16:35:01 - -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] I sent ten dollars to death.net and all I got was... well, nothing. "Can't keep my eyes from the circling sky, +-- "Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
Slink release - what's left?
[ Apologies for the major cross-post - I need input from lots of you... ] Consensus on -testing appears to be that we're about ready to ship the i386 release. I'm adding the final touches to the slink-cd script (v 1.06) right now. Changes from slink-cd v 1.05 up to now are: slink-cd (1.06) unstable; urgency=low * slink_cd changes: * handle non-US links better * Copy Release Notes onto all CDs * Create README.1ST - lists slink_cd version, creation date, disk label (from .disk/info) and gives simple instructions on what to do to run the installation system. * Copy the full set of files for the installation manual to /install. * Add sym-links for the installation manual into /doc. * others: * Created README.1ST.i386 - template for README.1ST above. * Removed test genlinks option from arch. * Added hfs.map for Apple people - not sure what to do with it yet. * Added mkisofsrc to packaging. -- Steve McIntyre <[EMAIL PROTECTED]> Thu, 11 Feb 1999 11:47:53 - Where are we up to on non-i386 boot/installation? If we're going to release together, which I assume is still the plan, then we need to get this sorted _soon_. I know someone (Eric? Stephane?) is working on the sparc disks and I have some support for them now. I've seen work ongoing on the m68k disks, too. I've not seen much for Alpha yet, but that may be my fault. Also, this is the contents of the README.1ST.i386 file I've written, which will hopefully be the first thing people will look at if they need help on getting the installation system up. Comments/changes are welcome. And similar information for other arches would also help a lot. README for Debian 2.1 CD installation. == To boot the installation system from CD, you will need to insert either CD#1 or CD#2 in your CD-ROM drive and reboot. CD#1 contains a normal kernel that should work for most people and contains many drivers. CD#2 is a smaller system based on the "tecra" kernel - this is smaller because it has fewer drivers compiled in to avoid a known problem with large kernels on laptops, especially the Toshiba Tecra series. If your system will not boot from CD, there are other options: Boot a DOS system with CD drivers, then run /install/boot.bat from the first CD. Make boot floppies from the images on the first CD, in the directory /dists/stable/main/disks-i386/current. The program rawrite2.exe in that directory will write the floppy images under DOS. See /install/install.txt for more information. Steve McIntyre <[EMAIL PROTECTED]> 10 Feb 1999 Prepended to this file automatically will be This Debian installation CD was created by slink_cd version $VER on $DATE It is labelled $LABEL Anything else? -- Steve McIntyre, Allstor Software [EMAIL PROTECTED] Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
Re: NEWS for debian-boot
On 17 Jan 1999, Adam Di Carlo wrote: >We're preparing for the 2.1.5 release of the boot-floppies package, >which will re-introduce the tecra kernels for x86 (aw!). Also, the >package pre-selections mechanism has been made >cross-architecture-aware, and we have patched in m68k fixes. Ok, good. The tecra reintroduction is not good news, but is not a problem - I'll change the CD scripts back to using it on disc 2 for release. >There is still much work to be done on the Install Manual, so there >will be at least one release after 2.1.6 before freeze (if only to get >the new set of documentation). Since the non-x86 boot-floppies are >rather lagging here, I'm sure there will be more than one, but I don't >speak for Enrique. > >There are two main areas of concern for me with slink, aside from the >obvious stuff that has to be done. The first is that I don't see >visible signs that the alpha and sparc people are working on the >boot-floppies or the CD set. (I could also use heavy documentation >help from these camps). I hope I'm overlooking actual activity, but I >doubt it. If we're going to release for all the arches (I've already been told by Joel Klecker that powerpc is not being frozen this time) then I need help (and preferably patches) to make install/boot CDs on m68k/atari m68k/mac alpha i386 is covered and I have numerous success reports for this, including my own testing. sparc should be covered for boot at least - Eric Delaunay <[EMAIL PROTECTED]> sent me patches that I trust will work. I can't check this myself unfortunately, due to lack of non-i386 hardware. And Chris Lawrence <[EMAIL PROTECTED]> has promised m68/amiga patches soon. >The second major issue I see, which I hope we will resolve soon, is a >lack of coordination between the CD team, the boot floppies, the >Debian archive maintainers, Bob Hillard (doing the upgrade notes), and >the Debian webmaster. An argument, I think, for an ecumenical Release >Tiger Team or some such? Sounds good to me. There are a couple of things that would help right now and in future: a) the list of pre-selected packages used in the installation can be used by slink_cd to generate the list of packages it will push onto disc 1. Is this posted on the debian-boot list, or if not can it be mailed to me when it's updated please? b) some of the ports still appear to be (or at least were when I checked on Friday) quite a way behind on the recompile front, particularly on non-free and non-US. I know we have limited cycles available for this work - are many packages still being updated for i386? If so, we need to go completely frozen apart from critical bug fixes NOW. Until things are more consistent, it's difficult to say whether or not the non-i386 images I'm producing are any use at all. For the general issues, is it maybe time for a new debian-release mailing list? Or should we flood debian-devel and hope to get more interest from the other developers? And is much thought being put into bo->slink upgrades? I tried one on one of my machines a few weeks back and struggled a lot. In the end I did bo->hamm->slink. Can somebody update the upgrade script so it will cope bo->slink? At the moment, lots of the packages it lists have hardcoded versions that match hamm. I would offer, but I've barely found time for slink_cd lately and I don't want to take on more than I can handle right now - work is getting very busy... -- Steve McIntyre, CURS CCE, Cambridge, UK. [EMAIL PROTECTED] Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoer
