Re: Getting d-i to find firmware on the CD generated by debian-cd

[Goswin von Brederlow]

Steve McIntyre  writes:

> On Thu, May 27, 2010 at 03:17:08PM +0100, Steve McIntyre wrote:
>>On Sat, May 22, 2010 at 06:58:52PM +0200, Petter Reinholdtsen wrote:
>>
>>I've added code into debian-cd to generate images with firmware on the
>>first CD. Add "FORCE_FIRMWARE=1" in CONF.sh. I've also tweaked the
>>build scripts so that we'll start generating them. I can see that I've
>>got all the firmware debs in /firmware in the ISO, but I don't see any
>>feedback to suggest that the installer is picking up on them. Test
>>images available at

I haven't tested it but just from this short text you seem to be doing
it wrong.

>From memory you should add the debs to the normal repository structure
on the CD under non-free and in the Release file specify that the CD
carries main and non-free. Iirc you also need to list non-free in the DI
info file but I'm not sure. Last time I did this was by hand and when
lenny was frozen.

DI then sees that you have both main and non-free on the CD and reads
main/binary-arch/Packages and non-free/binary-arch/Packages and sees all
the firmware debs (same for udebs).

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874ogteuh0@frosties.localdomain

Re: Multi-arch netinst getting too big

[Goswin von Brederlow]

Steve McIntyre  writes:

> On Tue, Jun 15, 2010 at 03:06:14PM +0100, Ian Campbell wrote:
>>On Tue, 2010-06-15 at 14:30 +0100, Steve McIntyre wrote:
>>> For the last few builds, the i386/amd64/powerpc sid netinst image has
>>> become too big to fit on one CD any more. The following packages are
>>> falling off onto a second disk now:
>>> 
>>> i386:main:linux-image-2.6.32-5-686-bigmem:27213342
>>> i386:main:linux-image-2.6-686-bigmem:3036
>>> i386:main:linux-headers-2.6.32-5-686-bigmem:516338
>>> i386:main:linux-headers-2.6-686-bigmem:2930
>>
>>The linux-image ones were added to support installation into a Xen PV
>>domain and were added to this image precisely because it was one of the
>>few images which was considered to have room -- it would be a shame to
>>have to drop them.
>
> Hmmm, OK.
>
>>> http://cdimage.debian.org/cdimage/daily-builds/sid_d-i/20100615-5/multi-arch/list-cd/debian-testing-amd64-i386-powerpc-netinst.list.gz
>>> 
>>> in case anybody wants to take a look and suggest things...
>>
>>I'm afraid I don't have any good ideas. Is this particular image
>>supposed to contain a complete base system or just enough to fetch the
>>remainder of the base system from the net?
>
> The netinsts are meant to have the base system, yes. I can't see
> anything obvious myself that we can drop. Maybe time to give up on
> powerpc on that image, like we've done on the m-a DVD. Shame, but
> there's only so much stuff we can accommodate here. Anybody else have
> an opinion here? Frans/Joey?

Just a crcy idea: Could the plain i386 kernel be droped instead? That
would loose support for i486 and i586 cpus on the m-a CD. But is that
needed there?

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87zkyldfr8@frosties.localdomain

Re: MBF alert: packages with very long source / .deb filenames

[Goswin von Brederlow]

Joey Hess  writes:

> Steve McIntyre wrote:
>> There are uses I've heard about, including (apparently quite common)
>> using CDs and DVDs to seed a mirror on a Windows server.
>
> If I had to chose between that working, and not needing to worry about
> filename lengths, I'd choose the latter.
>
>> >Is it possible to provide Joliet filenames for only a subset of files?
>> 
>> It is, yes. But not something I'd like to do if we can avoid it.
>
> One approach then would be to omit joliet filenames for the few long
> packages. This would not even impact your use case above much, since
> any mirror seeded from files from CDs needs a further sync step.

And how would users then get those files? If you have a kernel without
udf filesystem support then apt/aptitude/... would suddenly fail to find
some files. Same if udf isn't the default filesystem for cds.

The files could be renamed and the new name be used in Packages/Sources
files on the CD. But then the dsc files are broken. And they are signed
so they can't be edited without loosing the signature.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87fwq7is3k.fsf@frosties.localnet

Re: MBF alert: packages with very long source / .deb filenames

[Goswin von Brederlow]

Andreas Metzler  writes:

> In gmane.linux.debian.devel.general Joey Hess  wrote:
>> Steve McIntyre wrote:
>>> There are uses I've heard about, including (apparently quite common)
>>> using CDs and DVDs to seed a mirror on a Windows server.
>
>> If I had to chose between that working, and not needing to worry about
>> filename lengths, I'd choose the latter.
>
>>> >Is it possible to provide Joliet filenames for only a subset of files?
>
>>> It is, yes. But not something I'd like to do if we can avoid it.
>
>> One approach then would be to omit joliet filenames for the few long
>> packages. This would not even impact your use case above much, since
>> any mirror seeded from files from CDs needs a further sync step.
>
> Hello,
> An alternative approach would be to use a different *filename* while
> keeping the package name unchanged (This could be done on both mirrors
> and CD.) Iirc apt/dpkg have absolutely no problem with "foo.deb"
> containing version 1:3.2.1-11+squeeze2 of the 
> openoffice.org-report-builder-bin i386 package. I do not know about
> dak, though.
>
> cu andreas

Doesn't work for sources as the dsc files are signed and therefore
unalterable. Unless you want to teach dpkg about the renaming rules too.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87y63xxbl1.fsf@frosties.localnet

Re: MBF alert: packages with very long source / .deb filenames

[Goswin von Brederlow]

Philipp Kern  writes:

> On 2011-04-03, Wouter Verhelst  wrote:
>> OTOH, do you really want to type
>> "apt-get install package-with-policy-compliant-utterly-long-silly-name"?
>> There's a point when package name lengths become problematic, and that
>> isn't just true for ISO images.
>
> That's why $DEITY invented tab completion.  (And yes, that really
> auto-completes on a stock Squeeze install.)
>
> Kind regards
> Philipp Kern

Also those long names are usualy installed as part of dependencies so
you never type them.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87lizravcd.fsf@frosties.localnet

Bug#658352: 4k Advanced format

[Goswin von Brederlow]

shirish शिरीष  writes:

> at bottom :-
>
> On Thu, Feb 2, 2012 at 19:04, Thomas Schmitt  wrote:
>> Hi,
>
> 
>
> Getting a little sideways here :-
>
>> I am clueless enough to look into wikipedia about GUID Partition Table.
>> The is room for a "Protective MBR" of 512 bytes.
>> So somebody would need to teach me how to announce the range of the
>> ISO image and the range of the FAT partition in a GPT.
>>
>> Further one would have to discuss with Vladimir Serbinenko at grub-devel
>> about the layout of the first 32 kB of the ISO image, where MBR, GPT,
>> and GRUB2 code have to reside side-by-side.
>
> I am curious to know how easy it is (or not) to have the newish
> Advanced format [1] support in Debian-installer [2], as well as the
> ext* filesystems [3]. I remember a story about it which came in
> osnews[4] long-time back (around 1.5 years +) but do not really know
> how relevant they are or not atm. I am asking as from what i read
> alongwith the above at the very least the perception is most of the
> changes being done are to take care of growth for the next 20 + years.
>  I also saw discussions on the linux kernel page [5] but that wiki
> page is not current with the linux 3.x kernels. I did however spot an
> article on lwn.net [6] .
>
> Sadly there is no wiki entry about 'Advanced Format' on the Debian
> wiki. It would be nice if somebody has some updated instructions for
> it somewhere.

I think that should plain just work right[tm].

I recently bought a 3TB disk with advanced format and parted correctly
detected 512 byte logical blocksize and 4096 byte physical blocksize
(that is the advanced format part) and defaulted to aligning the
partitions to 1MB.

And since DI uses libparted that should just work there too.


As for ext* filesystems you just have to make sure to use 4k block size
there, which is the default for large enough filesystems.

MfG
Goswin



--
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/877gzwqfv7.fsf@frosties.localnet

Re: Planning for final lenny point release (5.0.10)

[Goswin von Brederlow]

"Adam D. Barratt"  writes:

> On Mon, 2011-12-12 at 23:05 +, Adam D. Barratt wrote:
>> Working on the four-monthly schedule for oldstable, the next lenny point
>> release would be due in early February.
>> 
>> As the security team have recently confirmed that security support for
>> lenny will end on February 6th (a year after the release of squeeze) it
>> makes sense to schedule 5.0.10 to be after that date and make it the
>> final roll-up point release for lenny.
>
> So, security EOL for lenny has now passed.  We're in sync with the
> security archive and the only missing packages are
> openjdk-6/{alpha,ia64} and opie/{arm,armel}.  AIUI the chances of those
> ever building are remote but, given that we've nothing to lose we might
> as well go ahead and accept them in to o-p-u and see what happens[tm].
>
> I can't see any outstanding o-p-u package bugs in the BTS.  If there's
> any I missed on the list, please yell.
>
> -kernel, -boot - were there any plans for a final kernel and/or d-i
> upload for lenny?  If so we need to get those sorted asap.
>
> In terms of scheduling for the point release itself, the current
> suggestions are:
>
> 25-26/2 - Steve's not available for CDs
>
> 3-4/3 - Cambridge BSP.  Should be do-able as long as I can get decent
> connectivity at the right time. :-)
>
> 10-11/3 - Joerg mentioned he's not available on the Sunday, but that's
> only really an issue if stuff breaks and it then transpires that Mark's
> also unavailable to help fix the world.
>
> Thoughts / preferences / anything I missed?
>
> Cheers,
>
> Adam

Should ia32-libs be updated?

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87haysth07.fsf@frosties.localnet

Re: Missing Packages.gz file in debian-6.0.7-amd64-DVD-8.iso image

[Goswin von Brederlow]

On Thu, Mar 14, 2013 at 04:25:43PM +, Steve McIntyre wrote:
> On Thu, Mar 14, 2013 at 04:54:20PM +0100, Franco Martelli wrote:
> >Hi,
> >
> >In debian-6.0.0-amd64-DVD-8.iso image the file Packages.gz exist but
> >in debian-6.0.7-amd64-DVD-8.iso it doesn't!
> >This cause an "apt-get update" error. I don't know which package
> >affect this bug...
> 
> Hi Franco,
> 
> This is not a bug at all, I'm afraid. There are no packages from
> contrib on DVD#8 in 6.0.7, so there is no Packages.gz file needed
> there.

Now the question becomes: What error does apt give and why?

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130318101854.GB27927@frosties

Re: DOUBTS installing home-server through the Internet

[Goswin von Brederlow]

"Pablo J." <[EMAIL PROTECTED]> writes:

> I want to use CD-minimun to install through the Internet but...
> 
> if a want to create a poor P-II server... 
> 
> What flavor can I use ? 
> 
> What .iso file download for burning the CD instaler ? 
> 
> And which mirror download from ??
> 
> Pablo J. [EMAIL PROTECTED]
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

http://cdimages.debian.org/

And use images for woody sinc hyare known to work. You can upgrade
later at any time if you feel like you need to.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: businesscard iso

[Goswin von Brederlow]

"Dave Henderson" <[EMAIL PROTECTED]> writes:

> Debian Team,
> 
>  
> 
>  I am working on a project where space is at a premium so I started to
> look over the Debian web site for smaller packages than the base install from
> a regular install CD.  I noticed that there is one called a businesscard iso,
> but it is for unofficial releases.  One of the main reasons I like Debian, is
> because when you guys release something as "official" it is a good release.  I
> was wondering why there isn't an official release of this iso AND what is left
> out (so to speak) from this iso that wouldn't be included from a base install
> from the regular Debian cd.  I appreciate your time in this matter and look
> forward to hearing from you.

At the time woody was released there were yet no widespread netinstall
isos or mini install isos in use. Now there are several smaller images
referenced on the debian webpages that can be considered semi
official ranging from 10 to 300 MB.

I think the only reason that Debian has no official small images is
that noone bothered to change the cd creation scripts to also build a
small image. Given the popularity the next releas will probably have
such images with official label.

But you will allways get the base install. I don't think there is
anyone working on a even smallerimage. But an image for an base
install is about 30MB and fits on a small CD.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Network Install

[Goswin von Brederlow]

"Ian" <[EMAIL PROTECTED]> writes:

> Will the network install of debian work if your connected to a router via 
> wireless with WEP enabled or would I have to use the full CD set in that 
> case?
> 
> Ian Balls.

That depends on _the_ network install.

Not sure which or if any of the unofficial images contain WEP support
but I guess the 300MB ones have it.

You can also use the ~30 MB ones and copy the extra packages for WEP
manually via floppy or add them to the CD.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DOUBTS installing home-server through the Internet

[Goswin von Brederlow]

Goswin von Brederlow <[EMAIL PROTECTED]> writes:

> http://cdimages.debian.org/
> 
> And use images for woody sinc hyare known to work. You can upgrade
> later at any time if you feel like you need to.

And use images for woody since they are known to work. You can upgrade
later at any time if you feel like you need to.

Sorry, typing too fast for the laag.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: free cd burning programs

[Goswin von Brederlow]

"henny" <[EMAIL PROTECTED]> writes:

> hi
> 
> i wont take up much of ur time. Can u recommend a free cd burning
> software program that i can download on to my hard?
> 
> thanks
> 
>  

http://packages.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?

[Goswin von Brederlow]

[EMAIL PROTECTED] writes:

> Hello Raphael
> 
> > Hello everyone,
> > 
> > I finally uploaded debian-cd 2.2.16 to unstable. But I've been way too
> > long in doing that and that reminds me that I really should find some
> > co-maintainers in order to avoid such delays in the future.
> > 
> > So, are there any volunteers ?
> 
> What exactly are the tasks of a co-maintainer and how much time will this
> consume ?
>  
> > The package is not in a bad shape (there's only one wishlist bug open)
> > but from time to time it requires immediate attention to adapt it to a
> > new set of files provided by the debian-boot team for example... 

Is there any debian-installer support yet?

Did you notice me developing and packaging debix and as a sub package
debix-imager.  Debix-imager handles the part of boot-floppy and
ramdisk creation that needs root. I intend to do build D-I CDs with
debix as one option which might mean forking debian-cd or copying the
support for it from debian-cd.

> Hmm, so maintaining debian-cd will require in-depth knowledge about
> debian-boot for all 16 (17) architectures ?

Which noone has. Its more likely adding patches from various people
doing work on different archs and from debian-boot. Or even more
likely pestering debian- so someone volunteres to test and fix
problems that arise.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

debian-cd questions [Was: Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?]

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Le Thu, Aug 21, 2003 at 12:05:16PM +0200, Goswin von Brederlow écrivait:
> > > > The package is not in a bad shape (there's only one wishlist bug open)
> > > > but from time to time it requires immediate attention to adapt it to a
> > > > new set of files provided by the debian-boot team for example... 
> > 
> > Is there any debian-installer support yet?
> 
> Sure there is ! How do you think we build the d-i test images ?

By hand last I heard, which was for the LinuxTag. Buts that was probably
D-I's fault and not debian-cd's.

> > Did you notice me developing and packaging debix and as a sub
> > package debix-imager.  Debix-imager handles the part of
> > boot-floppy and ramdisk creation that needs root. I intend to do
> > build D-I CDs with debix as one option which might mean forking
> > debian-cd or copying the support for it from debian-cd.
> 
> What about depending on it and using it ? debian-cd is modular
> enough to be able to do whatever you need provided that you write
> some intelligent hooks ...

I need different kernel images (building them atm), different
ramdisks (those debix will build via debix-imager), and the normal
ramdisk or a full live filesystem as loopback file on the CD.

I hope I can use debian-cd to create the actual CDs and make them
bootabel. I would hate to do the bootloader stuff for alpha, mips,
 all over again.

Is there some documentation about intelligent hooks in the cvs?

By the way, does debian-cd need root to build the ramdisk or is that
provided as image by boot-floppies/D-I? Can't rememer.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: debian-cd questions [Was: Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?]

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Le Fri, Aug 22, 2003 at 03:12:50AM +0200, Goswin von Brederlow écrivait:
> > I need different kernel images (building them atm), different
> > ramdisks (those debix will build via debix-imager), and the normal
> > ramdisk or a full live filesystem as loopback file on the CD.
> > 
> > I hope I can use debian-cd to create the actual CDs and make them
> > bootabel. I would hate to do the bootloader stuff for alpha, mips,
> >  all over again.
> 
> Sure, beware however that not all arch are able to provide a choice for
> the kernel to use at boot time ...

I won't. It will be hard enough to build one kernel for most archs.

> > Is there some documentation about intelligent hooks in the cvs?
> 
> Not really, the only doc available is what's in README (and README.devel).
> It's rather terse about the hooks but well UTSL. :-)
> 
> > By the way, does debian-cd need root to build the ramdisk or is that
> > provided as image by boot-floppies/D-I? Can't rememer.
> 
> Provided by d-i. I always tried to avoid root requirement. It may be
> that sparc building needs root right (in order loop-munt a file and edit
> it IIRC).

debix-imager doesn't allow to loop-mount a given image for security
reasons. Maybe d-i can be convinced to do the edit or provide a tar
file instead.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: A simple question about downloading debian-30r1-i386-binary-x.iso's

[Goswin von Brederlow]

Richard Atterer <[EMAIL PROTECTED]> writes:

> On Mon, Aug 25, 2003 at 10:16:24AM +, john smith wrote:
> > A simple question about downloading debian-30r1-i386-binary-x.iso's
> > 
> > Im currently wishing to download Linux, and was just wondering if i had to 
> > download all of the ISO's on this page 
> > "ftp://gd.tuwien.ac.at/opsys/linux/debian-cd/images/3.0_r1/i386/";
> > 
> > Or wether i just have to download one.?
> 
> See :
> 
>   Which of the numerous CD images should I download? Do I need all of them?
>   
>   No, you only need the CD images for your computer's architecture. The 
>   architecture is the type of hardware your computer uses. By far the most 
>   popular one is the Intel architecture, so most people will only want to 
>   get the images for "i386".
>   
>   Furthermore, in most cases it is not necessary to download all of the 
>   images for your architecture. The packages on the CDs are sorted by 
>   popularity: CD 1 contains the installation system and the most popular 
>   packages. CD 2 contains slightly less popular ones, CD 3 even less 
>   popular ones, etc. You will probably not need CD 3 and higher unless you 
>   have very special requirements. (And in case you happen to need a package 
>   later on which is not on one of the CDs you downloaded, you can always 
>   install that package directly from the Internet.)
>   
>   Finally, for each architecture there are two versions of the first CD, 
>   the normal and the non-US version. You only need one of these! See below 
>   for details.

This should be updated for the netinstall CDs. I hope sarge will get
official ones.

The minimum CD is 10 MB for setups with a already working router.
~30 MB for systems that needs ppp/dsl/(isdn?) for install.
~300 MB for useable system with or without internet.

The cdimages webpage has links to semi official images. Unless you
want to produce CDs you should never download the Debian CD set. Go to
the next shop and buy one. The media costs more.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Jigdo Automation

[Goswin von Brederlow]

Roger Guenter Trott <[EMAIL PROTECTED]> writes:

> Hello everybody,
> 
> i would like to use jigdo to keep my SID cd rom images up to date.
> 
> My problem is as follows: I want to do this automatically at night
> (means no user interaction :-))
> 
> It is no problem to get 11 loop mounts, but i can't figure out how to
> use something like
> 
> 
> for I in *.iso do ; jigdo . done ;
> 
> question: is this possible ?

rsync the images.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Making unofficial extension CDs

[Goswin von Brederlow]

Terry Hancock <[EMAIL PROTECTED]> writes:

> Is there an online reference that describes how the Debian 
> archives are constructed?  Such as how "Packages.gz" gets 
> built, etc?

man dpkg-scanpackages
man dpkg-scansources

As to the Release files there is some docs in apt but I think its
mostly look at existing once and do the same.

> I need to create a CD set based on a set of extra, 
> unofficial Debian packages.  My understanding is that if 
> this is done right, it will be possible to combine such a 
> CD with an official distribution set to make an extended 
> set, with local packages, unofficial deb packages, etc, 
> that can be installed and maintained more-or-less just like 
> you would a standard system.
> 
> The debian-cd instructions state that you need a "Local 
> Debian Mirror", but don't describe how you create it, 
> especially if you *aren't* just copying the official 
> archives.

apt-cache show debmirror (for the official archives)

Otherwise (untested) I think you just dump your debs into a directory
and point debian-cd to it. It should generate the neccessary
Packages/Sources and Release files itself.

> I really feel like this has to be a FAQ, but I haven't been 
> able to find it with Google or the search engine on the 
> Debian site.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: installatin

[Goswin von Brederlow]

"Matthias Tepe" <[EMAIL PROTECTED]> writes:

> da mein cd laufwerk nicht von der demian cd booted, boote ich mit einer win 98
> cd, wechsel dann die
> 
> cd und starte auf der demian cd im ordner install die boot datei.
> 
> ich verstehe zwar nicht warum die demian cd nicht automatisch booted und die
> win98 cd woll.

Alle Debian binary CDs sind bootbar. Auf der 1. CD ist ein multiboot
menu drauf das einem eine Auswahl verschiedener Kernel
ermoeglicht. Das funktioniert leider nicht ueberall.

Statt der Auswahl kann man aber auch CD 2-6 nehmen auf denen jeweils
ein anderer kernel drauf ist. Irgendwo steht auch was auf was ist,
weiss das nciht auswendig. Probier einfach mal von einer anderen zu
booten.

> auf jedenfall beginnt da auch eine installation die dann aber abgebrochen wird
> und ich weiß nicht warum.
> 
> ich habe auch nicht die gewalltige ahnung , aufjedenfall mache ich etwas
> falsch und ich weiß nicht was
> 
> kernel panic: vfs: unable to mount root fs on 01:00

Er sollte die ramdisk mit der Installationsroutine mounten. Von der
Ausgabe her wuerd ich sagen das die .bat datei Fehlerhaft ist und die
Falschen parameter uebergibt.

> was muß ich anders machen damit ich demian auf meinen laptop insallieren
> kann??

Wenn keine der CDs bootet haeng doch mal bitte die .bat datei an die
du zum starten benutzt hast. Vieleicht ist da nur nen simpler
tippfehler drinn.

Ansonsten kanst du auch bootfloppies (wie in der Dokumentation
beschrieben) erstellen, Floppylaufwerk vorrausgesetzt natuerlich.

Als wirklich allerletzten Ausweg gaebs dann noch Platte ausbauen und
woanders installieren.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: custom cd

[Goswin von Brederlow]

"St Francis Team" <[EMAIL PROTECTED]> writes:

> Sir,
> 
> 
> We tried to prepare bootable cd using knoppix remastering howto steps . 
> However the cd did not boot. Are there some steps to load boot.img boot.cat? 
> We had just  copied them from knoppix 3.2 cd using "cp" command.
> 
> Please help.

Knoppix is not quite Debian so your on the wrong list for that. Better
contact Knoppix itself for this.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Mattias Wadenstein <[EMAIL PROTECTED]> writes:

> I suspect I'm not the only one that thinks that this might be a good idea.
> I'm actually planning on offering this, what I'd like feedback on is how
> official it should be.

mldonkey urls should also be provided. Thats even easier than
bittorrent since its just an url containing a checksum.

> Should I (or whoever is doing them) place the .torrents in the debian-cd
> directory on cdimage.debian.org so that they are mirrored all over the
> place and look official or should I place them in some unofficial/test-
> directory?
> 
> When it comes to tracker I'm planning on using a dedicated dns name with a
> short ttl so we can repoint it at need if the machine can't handle it (I
> should be able to find a fast one though).

It would be good if debian had an official tracker (doesn't need to
have the image but it would be good).

The debian-installer group is currently struggling to get
autobuildable images. I guess it might be good to add the creation of
a torrent and donkey file there too so every arch will autobuild those
files too.

I'm all for it. Bittorrent is still one of the best.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

jason andrade <[EMAIL PROTECTED]> writes:

> On Mon, 5 Oct 2003, Goswin von Brederlow wrote:
> 
> > It would be good if debian had an official tracker (doesn't need to
> > have the image but it would be good).
> 
> [...]
> 
> > I'm all for it. Bittorrent is still one of the best.
> 
> i've heard a fair amount of discussion about BT but still haven't
> figured out how we can also use a P2P app in a S2C (server2client)
> manner.  how can mirror sites also make available the ISO images
> (and other files) available via the concept of a BT 'server' which
> doesn't have to download anything but can be pointed at a file
> or number of files which are then accessible via BT clients ?
> 
> and please don't say "just download the ISO and leave it running"
> as that isn't a viable idea from a server POV.

With bittorrent you have to have a running tracker. You also need
clients connected to the tracker that feed the data. That means each
mirror would have to run a bittorrent client on their local image.

Doogie was thinking about extending bittorrent to also download files
via http so normal http mirrors could be utilized too. Don't think
that will be ready for sarge though.


I don't think it would be too hard to get a group to mirror the debian
CD images with bittorrent to their servers and leave the clients
running for the first weak or so till the big rush is over. If Debian
says they will only do jidgo and bittorrent the first week that should
give enough incentive.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Patrick Strasser <[EMAIL PROTECTED]> writes:

> Mattias Wadenstein wrote:
> 
> [about offering Debian CD-images via BitTorrent]
> > I suspect I'm not the only one that thinks that this might be a good idea.
> > I'm actually planning on offering this, what I'd like feedback on is how
> > official it should be.
> 
> I know that people like BitTorrent, and it that it is a nice P2P-System.
> But what is the point of a second distribution system besides a
> perfectly working distribution system that uses already existing
> staging points?
> 
> 
> I don't see an advantage in BitTorrent. It needs new software, users
> to spread data, extra administration, support. Moreover jigdo is IMO
> the best way to spread Debian CDs, thanks to the nature of ISO9660.

Jigdo produces a good initial template image that often needs further
repairs by rsync.

Bittorrent on the other hand is self repairing (like rsync).
Also bittorrent utilizes the leechers upstream bandwith to share data
and reduce the traffic on the mirror.


A mixture of rsync, bittorrent and jigdo would be best.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Dedication to 'Espy' still on CDs?

[Goswin von Brederlow]

Frank Bauer <[EMAIL PROTECTED]> writes:

> Hi.
> 
> I', testing sarge netinst iso and I've noticed, that there are
> still those files about dedication to Joel 'Espy' Klecker,
> which were introduced for _potato_ and were also on _woody_ discs.
> 
> With all respect to him, isn't time to remove those files from
> CDs?

Are they in /doc/? /doc/ is taken from woody at the moment.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Steve McIntyre <[EMAIL PROTECTED]> writes:

> On Sun, Oct 12, 2003 at 02:05:58PM +0200, Goswin von Brederlow wrote:
> >
> >Jigdo produces a good initial template image that often needs further
> >repairs by rsync.
> 
> ??? What makes you say this? I've never had to repair images after
> jigdo has run successfully...

Never had jigdo fail to download some file for some reason or another?

Or a bittoggler that goes undetected by the TCP checksums.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Sarge-Installation: dpkg: error processing

[Goswin von Brederlow]

Martin Sjögren <[EMAIL PROTECTED]> writes:

> I bet, udebs (like udpkg, rootskel,...) aren't meant to be installed on
> a normal Debian system.
> 
> > rootskel template parse error: Template #7 in /tmp/template.2.7.910 doesn't cont 
> > in a 'Template:' line
> > dpkg: error processing
> > Errors were encountered while processing:
> > /cdrom//pool/main/c/cdebconf/cdebconf_udeb_0.41_i386.udeb (e.g.)
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > Some errors occured while unpacking.
> > Only errors above this message are important.
> > Please fix them and run Install (dselect) again.
> 
> It seems to me like apt-cdrom interacts really badly with a CD that has
> both debs and udebs on it... Does anybody have an idea how to fix this?

Am I right to assume anna and libdebian-installer will ignore pining?
Then it should be easy to add a pin of <100 to the udebs keeping them
from ever being installed automatically.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Christian Leber <[EMAIL PROTECTED]> writes:

> On Sun, Oct 12, 2003 at 03:10:29PM +0200, Goswin von Brederlow wrote:
> 
> > Or a bittoggler that goes undetected by the TCP checksums.
> 
> It's very unlikely because the jigdo files have md5
> checksum's for every file and i think they are used.

And if they detect an error?

What if your local mirror has a broken deb on it?

You need rsync to correct that then unless you want to fiddle around
till you find a working file.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Christian Leber <[EMAIL PROTECTED]> writes:

> On Sun, Oct 12, 2003 at 04:22:49PM +0200, Goswin von Brederlow wrote:
> 
> > And if they detect an error?
> 
> I would rerun jigdo, i think it would download the file again.
> If this would fail I would report this to the mirror maintainer and use
> another mirror.
> 
> > What if your local mirror has a broken deb on it?
> 
> I would fix it.

Without a valid source it can't.

> > You need rsync to correct that then unless you want to fiddle around
> > till you find a working file.
> 
> And if the iso on the rsync server is brocken?

Then the md5sums of the official images will be bogus as well and all
hell breaks loose.

> I really like rsync and use it for my daily backup, but i don't see a
> reason to use it together with jigdo.

Your choice. Seen enough people on irc saying the md5sum differs after
jigdo had been run.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [joeyh@debian.org: Bug#215469: don't include unnecessary udebs on the cd]

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Hello,
> 
> I just got this bug. It looks like we aren't smart enough about the
> selection of udebs to include on the CD ...
> 
> The initial idea was to include them all so that all install scenario
> can happen but it looks like there are udebs which are useless since
> they are simple "file repositories" for d-i.
> 
> And the list is getting so big, that it doesn't make sense to include
> everything for netinst & business card CD.

My new D-I build script builds 20MB businescard cds compared to the
48MB? debian-cd images. There is more to save on docs, keyring,
indices, Contents files,... than on the udebs.

> I think we need to update the script that generates the task files which
> lists udebs. Santiago ? 
> 
> The first step is probably just to have exclusion list/pattern used by
> tools/generate_di_list and/or tools/generate_di+k_list ...
> 
> Cheers,
> -- 
> Raphaël Hertzog -+- http://www.ouaza.com
> Formation Linux et logiciel libre : http://www.logidee.com
> Earn money with free software: http://www.geniustrader.org
> From: Joey Hess <[EMAIL PROTECTED]>
> Subject: Bug#215469: don't include unnecessary udebs on the cd
> To: Debian Bug Tracking System <[EMAIL PROTECTED]>
> Date: Sun, 12 Oct 2003 19:48:01 -0400
> Reply-To: Joey Hess <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Resent-From: Joey Hess <[EMAIL PROTECTED]>
> 
> Package: debian-cd
> Severity: normal
> 
> The businesscard and netinst cd images at
> http://gluck.debian.org/cdimage/testing/netinst/i386/ are bigger than
> they need to be. partly because they include such useless things as
> this:
> 
> ./pool/main/k/kernel-image-2.4.20-1-i386-udeb/kernel-image-2.4.20-1-386-udeb_2.4.20-8_i386.udeb
> 
> This contains only a kernel, in a form users cannot use, and that the
> installer will only waste a lot of memory loading into its initrd after
> it has already booted.
> 
> ./pool/main/b/busybox-cvs/busybox-cvs-udeb_20030926-1_i386.udeb
> ./pool/main/b/busybox/busybox-udeb_0.60.5-2_i386.udeb
> 
> All d-i images already come with the appropriate busybox udeb installed
> on the image.
> 
> ./pool/main/c/cdrom-detect/cdrom-detect_0.31_all.udeb
> ./pool/main/c/cdrom-retriever/cdrom-retriever_0.08_all.udeb
> 
> If the installer can find these on the CD, it does not need them.
> 
> ./pool/main/c/cdebconf/cdebconf-gtk-udeb_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-newt-udeb_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-priority_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-slang-udeb_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-text-udeb_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-udeb_0.46_i386.udeb
> 
> These are probably useless, d-i boot images include at least one
> cdebconf frontend.
> 
> Etc. I'm sure you could save a *lot* of space by working with the d-i
> team to whittle down the udebs on the cd images to a set that is
> appropriate for the purpose of the CD. As it is these images are getting
> too big to be useful.

I'm working on getting propper lists what udebs will be always on the
boot media, what should be on CD and what is just leftovers or
unsuported (like the gtk frontend). Thanks for the hint about
retrievers and cdebconf.

After that d-i will generate partial Packages files containing just
the right files for each part. Those will be used by debmirror for
d-i developer to keep a partial mirror. They will work just as well
for debian-cd.


I'm not yet quite sure on how to get debian-cd to put the right stuff
on the right type of CD, or more concrete how to get it not to put some
stuff on it. A lot of stuff is just hardcoded in, like wgeting the
daily build d-i images of the net. Ideas are welcome there.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Packaging debian-installer images for upload and to where?

[Goswin von Brederlow]

Hi,

debian-installer has two problems that need a decision soon:

1. Where will debian-installer images be placed?
   We have floppy, cdrom, netboot and hd-install images ranging from
   1.4 MB floppies, 5-20MB netboot/hd-install images and 5/20/50MB
   cdrom isos. Total 100-150 MB per arch.

   Images should be build regulary or even daily and stored for a few
   days to allow for testing and savekeeping of tested and working
   images.

   Would ftp://ftp.debian.org/debian/dists/sid/main/disks-/ be
   reasonable? Or should they be put on cdimage.debian.org (even the
   floppy, net and hd images)?

2. How do we package up the images for upload?



Debian installer has to few developers with to few architectures to
manually compile and upload images for every arch. During the
Debian-installer Debcamp in Oldenburg we discussed using the
autobuilders to build the images. We would create a source package and
upload that. The autobuilder pick it up along with normal sources and
build it.

Now the problem begins:

- The build needs to download udebs. Currently that means access to
any rsync mirror (ftp or any apt/sources.list could be aranged). This
should be easy to arrange. We just try and contact the buildd
maintainer if it fails.

- The build produces some floppy images, some cdrom.iso, some tftp
images and some tar.gz archives. What to do with them.
It has been suggested to build debs or udebs containing these files
but thats an ugly solution. I would be nice if the files could be
added as such to the changes file, uploaded in the normal queue and
put into dists/sid/main/disks-// by the ftp scripts.

E.g: (only important entries of the changes file)
Architecture: i386
Version: 20031018
Maintainer: Debian Install System Team <[EMAIL PROTECTED]>
Files: 
 bd065541fe35d5af69a016352a8c84b6 3334144 disks-i386 standard cdrom-boot.iso
 90f048938e12e5f3c6d10344b07db63b 1474560 disks-i386 standard floppy-boot.img


Currently pretty much all the porting to different architectures is at
a standstill because the people with the hardware have no clue how to
build images and the people with the knowledge to build and fix bugs
have no hardware. I and some others feel that use of the autobuilders
to compile and build images is essential to getting porting underway
again even if they throw the build images away instead of uploading
them.

Objections, comments, suggestions?

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Installations-Images

[Goswin von Brederlow]

Jürgen Siepmann <[EMAIL PROTECTED]> writes:

> Hallo,
> 
> mir ist unklar, weshalb auf
> 
> http://www.debian.org/CD/netinst/
> 
> Inoffizielle Netz-Installations-Images für das "stable" Release
> und
> Offizielle Netz-Installations-Images für das "testing" Release
> 
> angeboten werden.
> 
> Gibt es keine
> 
> Offiziellen Netz-Installations-Images für das "stable" Release?

Du hast es erfasst.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cds

[Goswin von Brederlow]

"JeffMacko" <[EMAIL PROTECTED]> writes:

> Debian:
> 
> I can't seem to find anyone to tell me the diff. from scsi and regular
> burning[writing]. Is there an accuracy diff. why pay so much more for scsi. I
> want to buy an 8cd burner but I don't want drop out or anything half way
> thru. Is scsi more faultless.or even 100%?
> 
> Looking forward to your reply, Ive searched for months.
> 
> Thanks Alot
> 
> Jeff&[EMAIL PROTECTED]

This is rather offtopic but here we go:

Until recently ide burners would work through a scsi emulation layer
(ide-scsi) so that they would appear as scsi burners to the
software. But nowadays burning directly to ATAPI is also possible.

As to the difference, scsi is of cause the better system and the firms
let you bleed for it. Ide has drawbacks when using multiple drives at
once (like harddisk and burner together) but nothing severe for a home
system. A firm wouldn't want its database server to go to half speed
just because the backup system is burning a cdrom.

>From time to time ide gets errors where scsi would corret the
error. But even if its as much as 1 cd in 100 that fails due to ide
(and I'm not saying its anywhere that much) just think about how many
cds you have to burn before you recoverd the extra price for scsi.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: apt-get

[Goswin von Brederlow]

"Mathieu R." <[EMAIL PROTECTED]> writes:

> HI
> is the function "apt-get update/upgrade" available with the DOWNLOADED
> version of debian 30r1 ?

There is Debian, the whole of Debian and only Debian.

Doesn't matter where you get it from, apt-get is apt-get.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Usage of isolinux on the beta CDs

[Goswin von Brederlow]

Santiago Garcia Mantinan <[EMAIL PROTECTED]> writes:

> Umm, seems like we go again for the same discusion, ok, I've been gathering
> some old links to try to shorten this.
> 
> The isolinux / multiboot / boot floppy emulation (syslinux) decision was
> already discussed for woody, at that time I was building unofficial images
> for all woody's arches, and I also partitipated on this discusion, I dislike
> isolinux because of the problems they give in old machines, but I also see
> its good side letting us have bigger and different initrds and kernels.

But we don't have that for the netinstall and businesscard CDs.

> > > it seems that we are locking out people from testing by using isolinux
> > > on our netinst/businesscard CDs, see #220139 and #220139.
> > > 
> > > Since we do not need any of isolinux's features I propose to use
> > > syslinux on the CDs.
> 
> We are using these features, current isolinux setup allows the user to
> select to boot the "net" initrd or the "cdrom" initrd. I don't know if this
> is wanted, this must be decided by the debian-installer guys, if we want to
> offer just the posibility to boot the cdrom image we can just boot
> cdrom.img, I have just tried it and it works, even though the setup for
> syslinux should be changed a bit to include the help screens and all that,
> this should be done in debian-installer, as it is d-i who makes that image.

I've been working on the new build scripts for d-i to build more
functional images directly. They generate 3 different CD images each
suited specifically to one task and one task only:

5MB bootcd - just boots but is like netboot or floppy boot in all
other respects

20MB d-i cd - image with tons of udebs to get your network up and
running and disk partitions so you can install base over net.

60MB base cd - image with udebs and all the debs needed to install
base. Everything needed till the first reboot (and a little more
e.g. for dsl). You have a fully functional Debian without any net
access but nothing in the way of apps.



Given those three types its a bit pointless to have multiple initrds
on the cdrom. People who want less than is on the cdrom should have
downloaded the smaller cd in the first place. I know the beta1 scripts
don't build a pure bootcd image but thats coming now that beta1 is out.

In cases were you end up with an old cd and would like to not use
the outdated (u)debs on the cdrom I say tough luck. People should live
with the old udebs or rsync a fresh image. Its only 5 or 20MB. Not
supporting a lot of older hardware just to be able to choose a
different behaviour not intended by the cd is not worth it.

> > Maybe we could put isolinux on the *second* CD, with eventually an
> > initrd that supports SCSI cdroms.
> 
> That sounds fine with me if it is ok to drop the net initrd from the booting
> options of the cds.

What second cd? Only the full set has multiple cds.

For a cd with isolinux we should probably build a huge initrd with all
the ide/scsi/cd modules preinstalled. We are not bound by the 2.88MB
limit there, right?

> Well, I don't know  what else to say, in the full cd set we really can have
> different booting methods, one on each cd, the important thing is to decide
> what do we put on the netinst/bussinesscard cds and also how do we order the
> methods in the full cd set.
> 
> If something I said needs farther explanation (I know my english sucks) just
> ask for it.

As a conclusion: My opinion is that the boot/netinst/bussinesscard
images are small enough to force people to download the right one in
favour of supporting all cdrom bootable i386 hardware. That means a
2.88MB floppy image with syslinux.

For the full set smae as with previous releases: cd 1 multiboot and cd
2 - X different single boot flavours.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

List of udebs to be included on the CDs

[Goswin von Brederlow]

Hi,

as promised I cleaned up the list of udebs that should be present on
the CDs:

The lists are in
http://cvs.debian.org/debian-installer/build/pkg-lists/mirror_udeb/

The lists contain all udebs that aren't obsolete (like the out-of-date
gtk udebs) and aren't already on the cdroms initrd. That means all
udebs that could possibly be loaded from cdrom.

The lists still contain all versions of kernel-image and modules but
debian-installer normaly only uses only one (but not on all
archs). That might be cleaned up in the near future.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problems with Sarge netinst and Yaboot

[Goswin von Brederlow]

<[EMAIL PROTECTED]> writes:

> Hi, I've just bought a PowerBook G4 12".
> 
> I have downloaded the Beta1 of Sarge NetInst for PowerPC (November 9th)
> and I have got a problem at the beginning of the installation.
> 
> I enter Open Firmware, and then boot with:
> boot cd:\\yaboot
> 
> And then I get:
> /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
> PROTECTED]:0,yaboot.conf: Unknown or
> corrupt filesystem
> Can't open config file
> Welcome to yaboot version 1.3.10
> Enter "help" to get some basic usage information
> boot: 
> Please wait, loading kernel...
> :0,/vmlinux: Unable to open file, Invalid device
> 
> The ISO image is correct (I have checked the MD5sum) and I've burned it a
> couple of times with the same results.
> 
> After trying some things (it was the first time I used yaboot) I've got it
> working with:
> boot: cd:0,/install/powermac/vmlinux initrd=/install/powermac/root.bin
> ramdisk_size=8192 init=/linuxrc
> 
> Well, it is not working yet, now it boots the kernel but it can't mount
> the root partition or initrd, it says (after detecting mouse, pci devices,
> etc ...):
> VFS: Cannot open root device "" or 16:01
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 16:01
>  <0>Rebooting in 180 seconds..
> 
> If I specify root=/dev/ram0 then it says (earlier than without specifying
> it):
> cramfs: wrong magic
> Kernel panic: VFS: Unable to mount root fs on 01:00
> ...
> 
> I've tried several combinations of these options without any good result.
> 
> Thanks for your help (please, keep me in CC because I'm not subscribed to
> the lists)

My branch of d-i has the following yaboot.conf:

debian-installer/build% cat boot/powerpc/yaboot.conf
## This yaboot.conf is for CD booting only, do not use as reference.
## Debian GNU/Linux PowerPC (woody)

# It is important not to have a comma after cd:
device=cd:
default=install
timeout=100

# FIXME: will this be the correct path?
message=/install/powermac/boot.msg

image=/install/powermac/linux
label=install
initrd=/install/powermac/root.bin
append="devfs=mount,dall"
initrd-size=8192
read-only

# some machines have wonky framebuffer support
image=/install/powermac/linux
label=install-safe
initrd=/install/powermac/root.bin
initrd-size=8192
append="video=ofonly devfs=mount,dall"
read-only

You might or might nor need root=/dev/ram. The beta-1 images are done
by debian-cd so the yaboot.conf and actual image names and locations
might differ but you should be able to compare them.

MfG
Goswin

PS: bugs in the beta-1 yaboot.conf should be filed against debian-cd, not much 
debian-boot can do about it


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Some observations about Debian installation

[Goswin von Brederlow]

[EMAIL PROTECTED] (Otto Wyss) writes:

> I'm just gone through a new Debian installation process and think I know
> a little bit what's wrong.
> 
> 1. The current stable release (3.0r1) is just outdated.
> 2. There are way too many show stoppers in the testing release (3.1)
> installation
> 
> 1. takes care that (almost) nobody uses Debian/stable for new systems.
> 2. takes care that (almost) everybody takes out his old Woody CD and
> does a dist-upgrade or similar. Therefore none of the installation
> problems gets mentioned and solved, at least not within a wish able time
> frame. And if someone still is determined and goes through the process
> and mentioning any problems he gets either no answer (see
> "http://lists.debian.org/debian-boot/2003/debian-boot-200311/msg01073.ht
> ml") or just some not very helpful (see

Discussed, explained and mostly fixed on the ML and cvs.

> "http://lists.debian.org/debian-devel/2003/debian-devel-200311/msg01248.
> html").

Installing kernel-image-2.4.22

What has that got to do with installing sarge?
 
> The problems I've mention are show stoppers for any user not as much
> accustomed to Debian as I. And they have to be fixed in one or the other
> way. Else Debian still keeps its image as a hacker distribution.
> Regardless how good or bad Debian is and regardless how many RC bugs
> exists, if a user encounters a show stopper during installation this
> user is lost. Gurus might find a solution but casual users simply switch
> to another distribution. Therefore the installation process has to be
> foolproof to a certain degree.

You are welcome to help.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: System Question

[Goswin von Brederlow]

"Mauricio" <[EMAIL PROTECTED]> writes:

> Hello,
> 
> I'm going to download de Debian CD Images for my computer. It's an AMD Athlon XP 
> 1700+. Wich version I must download? the Intel-Compatible or other one?
> 
> Other question I want to do: is there a new stable version near from now to be 
> completed? because I don't have an ADSL/Cable-modem and I need to pay for the ISO-CD 
> download. If a new version is going to be released, I want to wait this little time 
> to download it.
> 
> Sorry if my words/english are not very clearly.
> 
> Thanks for your answer.
> Regards,
> 
> Mauricio Ibáñez
> Montevideo, Uruguay.

Don't download isos. 80% of the stuff you don't need or want.

Download a netinstall cd with base (those 30-100MB isos), install
base, configure your modem and then install directly off the net.

That way you only have to download the programs you actually are going
to install. As an added bonus the new stable revision 3.0R2 has been
pushed to the debian mirrors but the CDs are not yet available.
Installing over the net you will get newer packages and don't have to
upgrade next week.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: broken link

[Goswin von Brederlow]

Josef Frühwirth <[EMAIL PROTECTED]> writes:

> Hello!
> I hope i`m sending this to the right adress.
> 
> On  page
> 
> http://www.debian.org/CD/netinst/
> 
> the link
> 
> Official "testing" images 
> 
> leads to an access error!
> 
> May be this is a feature of that page but in my opinion its a bug.
> Therefore i`m telling you:-)

Most likely caused by the compromised servers not being fully
reactivated yet and nothing can be changed till the logins are enabled
again.

By the way, the non daily build images are in the ftp archive if you
want to test them out.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: dependency problem

[Goswin von Brederlow]

tej trivedi <[EMAIL PROTECTED]> writes:

> hi!
> 
>  
> 
> i am a new user to knoppix.i wanted to know whether there is any command by
> which i can find the list of packages that i can safely remove while
> remastering knoppix cd. i haved made 2 remastered knoppix CDs, but the problem
> is that one of them does not boot at all ,and the second does not go to
> GUI. so if some of you know any command to get the list of packages that can
> be safely removed, then it would be of great help to me.
> 
> waiting for reply

Repeat after me:

KNOPPIX IS NOT DEBIAN!
KNOPPIX IS NOT DEBIAN!
KNOPPIX IS NOT DEBIAN!

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Not usefull kernel images take all first Debian sarge CD :(

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Quoting Adam Majer:
> > I agree. This is crazzy. But how the heck do you get this?
> > 
> > > kernel-image-2.4.22-xfs   - ~22 Mb
> > > kernel-image-2.4.22-i386  - ~78 Mb
> > 
> [...]
> > So even if you had 8 kernels, that would be 80M. To occupy most of the 
> > disk, I think you'll need more than 25 kernels..
> 
> We have many kernels, here's the list that I excluded yesterday evening:
> kernel-image-2.6.0-test11-1-386
> kernel-image-2.6.0-test9-1-386

Test and pre kernels could be kept in sid exclusively.

> kernel-image-2.4.20-3-386
> kernel-image-2.4.20-3-586tsc
> kernel-image-2.4.20-3-686
> kernel-image-2.4.20-3-686-smp
> kernel-image-2.4.20-3-k6
> kernel-image-2.4.20-3-k7
> kernel-image-2.4.20-3-k7-smp

kernel-source-2.4.20 is needed for m68k, keep that on some cd.
And e.g. kernel-image-2.4.20-amiga.

For non i386 the list of kernels differs widely between archs.

> kernel-image-2.4.21-5-386
> kernel-image-2.4.21-5-586tsc
> kernel-image-2.4.21-5-686
> kernel-image-2.4.21-5-686-smp
> kernel-image-2.4.21-5-k6
> kernel-image-2.4.21-5-k7
> kernel-image-2.4.21-5-k7-smp
> kernel-image-2.4.22-1-386
> kernel-image-2.4.22-1-586tsc
> kernel-image-2.4.22-1-686
> kernel-image-2.4.22-1-686-smp
> kernel-image-2.4.22-1-k6
> kernel-image-2.4.22-1-k7
> kernel-image-2.4.22-1-k7-smp
> kernel-image-2.4.23-1-386
> kernel-image-2.4.23-1-586tsc
> kernel-image-2.4.23-1-686
> kernel-image-2.4.23-1-686-smp
> kernel-image-2.4.23-1-k6
> kernel-image-2.4.23-1-k7
> kernel-image-2.4.23-1-k7-smp
> 
> That makes ~30 kernels. I kept 2.4.24* and 2.6.0-1*.
> 
> > Anyway, the number of kernel on the CDs should be reduced anyway.
> > We should only have the i386 version and let people build their
> > own variants if they choose to (or DL from mirrors).
> 
> No, IIRC debian-installer installs the good one depending on /proc/cpu.  So
> we'd better keep all the variants on the first CD. But we should definitely
> stick to one version of the kernel.
> 
> Cheers,

The first CD should have only one version, the one used in D-I, but as
many flavours as possible without overcrowding. All other versions
could be on later CDs. People might want a 2.2.x kernel or need a
2.6.0 kernel for their hardware.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Not usefull kernel images take all first Debian sarge CD :(

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> [ removing debian-devel which is not really necessary but added
>   debian-boot ]
> 
> Quoting Goswin von Brederlow:
> > Test and pre kernels could be kept in sid exclusively.
> 
> They could, but for the moment they aren't and I have to live up with
> that. :)
> 
> > For non i386 the list of kernels differs widely between archs.
> 
> Yes I address the problem only for i386. But I bet the problem is less
> serious for other arches because they don't have so frequent uploads of
> kernels, aren't they ?

None have that many flavours and fewer versions too.
 
> > The first CD should have only one version, the one used in D-I, but as
> > many flavours as possible without overcrowding. All other versions
> > could be on later CDs. People might want a 2.2.x kernel or need a
> > 2.6.0 kernel for their hardware.
> 
> debian-installer doesn't use 2.4.24 yet, does that mean that I broke
> d-i by excluding the other kernels from the CDs ? Is that's true,
> couldn't d-i be a bit more clueful and install the latest
> kernel-image-2.4.x package that it finds ?
> 
> Cheers,
> -- 
> Raphaël Hertzog -+- http://www.ouaza.com
> Formation Linux et logiciel libre : http://www.logidee.com
> Earn money with free software: http://www.geniustrader.org

D-I should preferably install the kernel image its booted with. We
know that one works. I think its looking at uname to figure out the
version to look for at runtime.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Debian DVD

[Goswin von Brederlow]

"Marco Terzuoli" <[EMAIL PROTECTED]> writes:

> Hi
> 
> I am due to download the latest Debian release but, before doing so, would
> like to know if there is, in addition to the 7 CD version, a DVD version,
> which would be more comfortable. If not, is there any plan to make a DVD
> version of Debian in the future?
> 
> Thank you
> 
> Marco

Unless you want to produce CDs for sale or give-away or have to
install a system without network access you should never download the
ISOs. And even then you might start with the first 1-3 CDs and see
whats missing and get those manually. Downloading all CDs wastes a lot
of bandwith on things you don't need.

If you just want to install a Debian system on a coputer with network
access just download the first CD, burn it, install it. After the
initial setup debian can download the specific software you need
directly without the need of burning CDs. Using the network is
probably the most prefered method under Debian.

MfG
Goswin

PS: There are also small netinstall images for stable ranging from 30
to 300Mb in size. I suggest trying out one of those.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: m68k daily cd patch

[Goswin von Brederlow]

Stephen R Marenka <[EMAIL PROTECTED]> writes:

> Would someone please apply the following patches? m68k needs these for
> daily sarge cds to be useful.
>
> The first is due to a kernel build-dep problem and keeps an install from
> completing. The second is some cleanup.
>
> Thanks,
>
> Stephen
>
>
> diff -ru setup/debian-cd/tasks/base-sarge debian-cd/tasks/base-sarge
> --- setup/debian-cd/tasks/base-sarge  Thu Jan 29 12:16:47 2004
> +++ debian-cd/tasks/base-sargeMon Apr  5 11:29:33 2004
> @@ -680,6 +680,7 @@
>  setserial
>  vmelilo
>  ipchains
> +filesutils

filesutils? Not fileutils?

>  #endif
>  
>  #ifdef ARCH_powerpc
> diff -ru setup/debian-cd/tools/boot/sarge/boot-m68k 
> debian-cd/tools/boot/sarge/boot-m68k
> --- setup/debian-cd/tools/boot/sarge/boot-m68kSat Mar 27 14:34:13 2004
> +++ debian-cd/tools/boot/sarge/boot-m68k  Mon Apr  5 11:30:08 2004
> @@ -34,6 +34,9 @@
>  
>  install_languages $CDDIR
>  
> +# remove i386 stuff
> +rm -rf $CDDIR/tools
> +

Thats the cleanup.

>  cd $INSTALLDIR
>  # create directories for different sub-archs
>  mkdir {amiga,atari,bvme6000,mac,mvme147,mvme16x}
> @@ -60,5 +63,7 @@
>  # Amiboot needs to be executable
>  chmod a+x amiga/amiboot-5.6
>  
> +# Need a .info file for the install directory (AmigaOS) (icon?)
> +cp amiga/amiga.info  $CDDIR/install.info

That the icon for the 'install' directory so people can click at it to
pop up the contents and click at the right install script in turn.

Now you are only missing the icon for the CD itself. Its a different
icon (icon type disk instead of icontype drawer) so you can't just
rename the amiga.info to disk.info.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: boot-cd

[Goswin von Brederlow]

<[EMAIL PROTECTED]> writes:

> Hello,
>
> I have an easy question.
>
> Which CD-Image is for booting?
>
> I have download "sarge-i386-1.iso" but when I boot from it the programm it stops.
>
> I see only the starting screen where you can select F1 or BOOT, then it break off.
>
> Send me a link or a filename for downloading, please.
>
> MfG
> Frank

You have the right CD. In fact all debian CDs can boot. The first CD
contains multiple kernels and you can pick one of them (read the help
and docs on the CD). All other CDs contain just one of the flavours
present on the first CD in a different way and are for cases where the
first CD doesn't boot.

Since you see the info screen the CD aparently boots so thats not the
problem. Try typing bf2.4 at the prompt.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#208736: corrupt file in Debian

[Goswin von Brederlow]

Mejo <[EMAIL PROTECTED]> writes:

> Steve Powell wrote:
>
>> I've downloaded the disk 1 iso for Debian 3.0r2 from two different places
>> and burnt CD's 3 different times and I always get that same error during
>> install --
>> file: /instmnt/pool/main/b/bash/bash_2.05a-11_i386.deb was corrupt
>
> Did u check the md5sum?
>
> if you are on a linux machine, type - md5sum filename.iso and check
> the output with that's on the debian website.

And in case of differences use rsync to correct errors instead of
downloading it all again.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: m68k daily cd patch

[Goswin von Brederlow]

Stephen R Marenka <[EMAIL PROTECTED]> writes:

> On Wed, Apr 14, 2004 at 03:53:40PM +0200, Goswin von Brederlow wrote:
>> Stephen R Marenka <[EMAIL PROTECTED]> writes:
>
>> > +filesutils
>> 
>> filesutils? Not fileutils?
>
> Fortunately, it's spelled correctly in cvs.
>
>> > +# Need a .info file for the install directory (AmigaOS) (icon?)
>> > +cp amiga/amiga.info  $CDDIR/install.info
>> 
>> That the icon for the 'install' directory so people can click at it to
>> pop up the contents and click at the right install script in turn.
>> 
>> Now you are only missing the icon for the CD itself. Its a different
>> icon (icon type disk instead of icontype drawer) so you can't just
>> rename the amiga.info to disk.info.
>
> Please tell me what I need to do. I really don't know much about amiga.

Look at the woody debian CD. There should be a file called disk.info
on it. Copy that file. I don't see the file on the ftp in
woody/main/disks-m68k but I know the woody CD had an icon when I
tested it for the last release.

> Thanks,
>
> Stephen

MfG
Goswin

PS: I don't have a woody m68k cd here or I would look myself, sorry.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Grub boot floppy on D-I i386 CD images

[Goswin von Brederlow]

Hi,

would it be possible to include a grub boot floppy image on the i386
CDs and add it to the multiboot menu (and/or put it on one of the
other CDs). For cases where the grub-installer doesn't work people
could then boot grub and install directly form the grub shell.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mipsel cd images available for testing

[Goswin von Brederlow]

Santiago Garcia Mantinan <[EMAIL PROTECTED]> writes:

> Hi!
>
> Today we have produced our first set of mipsel cd images of testing, they
> have not yet been tested, so we need people with cd equiped mipsel machines
> to test the new images, they are available at the usual place, which for
> mipsel is: 

Hi,

What kernel images do you have on it?

Can one export the CD via tftp/nfs for netbooting systems?

This would require the CD to have the same layout a debian mirror
would have (should be already) and it would need the netinstall images
on it.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Fulfilling our source obligation

[Goswin von Brederlow]

Petter Reinholdtsen <[EMAIL PROTECTED]> writes:

> [Matt Taggart]
>> In the process of giving out all these CDs it occurred to me that
>> Debian could make it easier for people giving out CDs to fulfill
>> their source obligation(required by some licenses like the GPL) by
>> creating an ISO image that also contained it's own source.
>
> As far as I know the GPL only require the source to be available on
> request.

Where where you during the Task&Skill checks?

GPL requires that the source accompanies the binary directly or a
written offer to deliver the source on demand (directly or passed on
from where you got the binary).

So actually handing out just binary CD1 is a violation of the GPL
since neither source nor a written offer is there.


You (Matt) can build a source CD for binary CD1 and have them ready
for anyone that wants it. If people don't take/buy both its their own
fault (like when they only download the binary from an url). That way
you usualy get away with 0 source CDs, or with burning one or two.


> But I welcome the idea for other reasons.  It would increase the
> amount of offline backup media for the source, and also make it easier
> to send "modifiable" CDs to countries with very bad Internet
> connections.
>
>> What do people think? Is this a reasonable idea? Should I start
>> looking in to what it would take to make the current processes do
>> this? (or does someone who's already doing it want to save me the
>> trouble? I'm not above bribery, name your price)
>
> Sounds good to me.  I'm aware of two CD building tools at the moment.
> debian-cd and picax.  There are probably more options available.
> debian-cd is the one we use at the moment, but it is getting harder
> and harder to maintain.

Does debian-cd organize the source CDs to correlate to the binary CDs
in any way?

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: A few problems with incuding local packages

[Goswin von Brederlow]

Colin Watson <[EMAIL PROTECTED]> writes:

> On Thu, Jul 08, 2004 at 05:35:48PM +0900, Horms wrote:
>> 2. The $PREFIX.generate-binary-debian-installer file created for
>>a local instance of the debian installer is bogus as it lacks
>>the FileList line.
>> 
>>This means that the resulting packages file will be empty
>>and as a result local .udebs will be not be able to be found
>>by debian-installer, even though they are present on the CD.
>> 
>>The attached patch, debian-cd-scanpackages_local.patch,
>>resolves this problem.
>
> Even if you do this, udpkg is not capable of merging two Packages files,
> so it won't actually work properly. I had to hack tools/scanpackages to
> append all the files listed in the local section to the main filelist
> instead, thus effectively merging the Packages files. This works but is
> hacky.
>
> -- 
> Colin Watson  [EMAIL PROTECTED]

The CD should be small enough to just scan all debs/udebs on it and
create a full Packages file for it. No mergeing, just recreate.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: AMD64 CDs

[Goswin von Brederlow]

Steve McIntyre <[EMAIL PROTECTED]> writes:

> On Sun, Dec 05, 2004 at 03:23:14AM +0100, Kurt Roeckx wrote:
>>Did I miss anything about this?  I would like to add those
>>netinst images to my daily builds for ages but I never was able
>>to make it build properly.
>
> I've not really looked into the netinst changes yet. I've written and
> tested regular AMD64 CDs and DVDs, and they seem to work OK at this
> point.
>
>>I also mailed you my old patches and never heard anything about
>>it anymore.
>
> Sorry, that was me being crap. They were a good start - thanks! I'm
> planning to get some of the changes into CVS tonight.

That is good to hear.

Something someone else said had me thinking about mixed CDs.
Amd64/Em64t is fully capable of running 32 and 64 bit at the same
time. It should be possible to boot the 64bit kernel, run the 32bit
debian-installer and install either 32bit or 64bit debian.

So what I'm thinking of is adding the 64bit kernel to D-I and patch in
a question "Install 32 bit (default) / Install 64 bit (experimental)"
question if a 64bit kernel is running.


As for debian-cd: What do you think about adding an option to use
different archs for the debs and udebs on a cd? Or including both
sets?

MfG
Goswin

PS: If you already have that option excuse me, it's been a while since
I build woody CDs with debian-cd.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: AMD64 CDs

[Goswin von Brederlow]

Steve McIntyre <[EMAIL PROTECTED]> writes:

> On Wed, Dec 08, 2004 at 05:45:18PM +0100, Goswin von Brederlow wrote:
>>Steve McIntyre <[EMAIL PROTECTED]> writes:
>>As for debian-cd: What do you think about adding an option to use
>>different archs for the debs and udebs on a cd? Or including both
>>sets?
>
> I'm happy to see that kind of thing suggested, although I'm a little
> short on time to do it myself right now. What I'd _love_ to do is try
> and create an all-in-one CD or DVD which will boot and install on
> several architectures. AMD64/i386/ppc should definitely be possible,
> and I'm hoping to be able to fit several more. Watch this space...

Amd64 and i386 booth use the same boot code so they are fine.

M68k (amiga) uses icons on the CD and can be added too.

Alpha hacks into the first block on the CD (aboot) and uses milo
otherwise. Not sure if aboot interferes with isolinux, I didn't need
it.

A while back I mixed myself an universal rescue CD for those three
and that came in handy a few times. It's nice to have one for all.


But one doesn't have to restrict oneself to one CD/DVD. If one needs a
full set for multiple archs it could be a good idea to place a
different archs boot code and installer on each CD/DVD, arch:all
packages only once on one CD and arch: on others. It would mean
you would always have to change the cd/dvd between arch and all but
with ~6G of arch:all packages having them once per arch is wastefull.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: businesscard iso

[Goswin von Brederlow]

"Dave Henderson" <[EMAIL PROTECTED]> writes:

> Debian Team,
> 
>  
> 
>  I am working on a project where space is at a premium so I started to
> look over the Debian web site for smaller packages than the base install from
> a regular install CD.  I noticed that there is one called a businesscard iso,
> but it is for unofficial releases.  One of the main reasons I like Debian, is
> because when you guys release something as "official" it is a good release.  I
> was wondering why there isn't an official release of this iso AND what is left
> out (so to speak) from this iso that wouldn't be included from a base install
> from the regular Debian cd.  I appreciate your time in this matter and look
> forward to hearing from you.

At the time woody was released there were yet no widespread netinstall
isos or mini install isos in use. Now there are several smaller images
referenced on the debian webpages that can be considered semi
official ranging from 10 to 300 MB.

I think the only reason that Debian has no official small images is
that noone bothered to change the cd creation scripts to also build a
small image. Given the popularity the next releas will probably have
such images with official label.

But you will allways get the base install. I don't think there is
anyone working on a even smallerimage. But an image for an base
install is about 30MB and fits on a small CD.

MfG
Goswin

Re: Network Install

[Goswin von Brederlow]

"Ian" <[EMAIL PROTECTED]> writes:

> Will the network install of debian work if your connected to a router via 
> wireless with WEP enabled or would I have to use the full CD set in that 
> case?
> 
> Ian Balls.

That depends on _the_ network install.

Not sure which or if any of the unofficial images contain WEP support
but I guess the 300MB ones have it.

You can also use the ~30 MB ones and copy the extra packages for WEP
manually via floppy or add them to the CD.

MfG
Goswin

Re: DOUBTS installing home-server through the Internet

[Goswin von Brederlow]

"Pablo J." <[EMAIL PROTECTED]> writes:

> I want to use CD-minimun to install through the Internet but...
> 
> if a want to create a poor P-II server... 
> 
> What flavor can I use ? 
> 
> What .iso file download for burning the CD instaler ? 
> 
> And which mirror download from ??
> 
> Pablo J. [EMAIL PROTECTED]
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

http://cdimages.debian.org/

And use images for woody sinc hyare known to work. You can upgrade
later at any time if you feel like you need to.

MfG
Goswin

Re: DOUBTS installing home-server through the Internet

[Goswin von Brederlow]

Goswin von Brederlow <[EMAIL PROTECTED]> writes:

> http://cdimages.debian.org/
> 
> And use images for woody sinc hyare known to work. You can upgrade
> later at any time if you feel like you need to.

And use images for woody since they are known to work. You can upgrade
later at any time if you feel like you need to.

Sorry, typing too fast for the laag.

MfG
Goswin

Re: free cd burning programs

[Goswin von Brederlow]

"henny" <[EMAIL PROTECTED]> writes:

> hi
> 
> i wont take up much of ur time. Can u recommend a free cd burning
> software program that i can download on to my hard?
> 
> thanks
> 
>  

http://packages.debian.org/

Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?

[Goswin von Brederlow]

[EMAIL PROTECTED] writes:

> Hello Raphael
> 
> > Hello everyone,
> > 
> > I finally uploaded debian-cd 2.2.16 to unstable. But I've been way too
> > long in doing that and that reminds me that I really should find some
> > co-maintainers in order to avoid such delays in the future.
> > 
> > So, are there any volunteers ?
> 
> What exactly are the tasks of a co-maintainer and how much time will this
> consume ?
>  
> > The package is not in a bad shape (there's only one wishlist bug open)
> > but from time to time it requires immediate attention to adapt it to a
> > new set of files provided by the debian-boot team for example... 

Is there any debian-installer support yet?

Did you notice me developing and packaging debix and as a sub package
debix-imager.  Debix-imager handles the part of boot-floppy and
ramdisk creation that needs root. I intend to do build D-I CDs with
debix as one option which might mean forking debian-cd or copying the
support for it from debian-cd.

> Hmm, so maintaining debian-cd will require in-depth knowledge about
> debian-boot for all 16 (17) architectures ?

Which noone has. Its more likely adding patches from various people
doing work on different archs and from debian-boot. Or even more
likely pestering debian- so someone volunteres to test and fix
problems that arise.

MfG
Goswin

debian-cd questions [Was: Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?]

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Le Thu, Aug 21, 2003 at 12:05:16PM +0200, Goswin von Brederlow écrivait:
> > > > The package is not in a bad shape (there's only one wishlist bug open)
> > > > but from time to time it requires immediate attention to adapt it to a
> > > > new set of files provided by the debian-boot team for example... 
> > 
> > Is there any debian-installer support yet?
> 
> Sure there is ! How do you think we build the d-i test images ?

By hand last I heard, which was for the LinuxTag. Buts that was probably
D-I's fault and not debian-cd's.

> > Did you notice me developing and packaging debix and as a sub
> > package debix-imager.  Debix-imager handles the part of
> > boot-floppy and ramdisk creation that needs root. I intend to do
> > build D-I CDs with debix as one option which might mean forking
> > debian-cd or copying the support for it from debian-cd.
> 
> What about depending on it and using it ? debian-cd is modular
> enough to be able to do whatever you need provided that you write
> some intelligent hooks ...

I need different kernel images (building them atm), different
ramdisks (those debix will build via debix-imager), and the normal
ramdisk or a full live filesystem as loopback file on the CD.

I hope I can use debian-cd to create the actual CDs and make them
bootabel. I would hate to do the bootloader stuff for alpha, mips,
 all over again.

Is there some documentation about intelligent hooks in the cvs?

By the way, does debian-cd need root to build the ramdisk or is that
provided as image by boot-floppies/D-I? Can't rememer.

MfG
Goswin

Re: debian-cd questions [Was: Re: Debian-cd 2.2.16 uploaded, any co-maintainers ?]

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Le Fri, Aug 22, 2003 at 03:12:50AM +0200, Goswin von Brederlow écrivait:
> > I need different kernel images (building them atm), different
> > ramdisks (those debix will build via debix-imager), and the normal
> > ramdisk or a full live filesystem as loopback file on the CD.
> > 
> > I hope I can use debian-cd to create the actual CDs and make them
> > bootabel. I would hate to do the bootloader stuff for alpha, mips,
> >  all over again.
> 
> Sure, beware however that not all arch are able to provide a choice for
> the kernel to use at boot time ...

I won't. It will be hard enough to build one kernel for most archs.

> > Is there some documentation about intelligent hooks in the cvs?
> 
> Not really, the only doc available is what's in README (and README.devel).
> It's rather terse about the hooks but well UTSL. :-)
> 
> > By the way, does debian-cd need root to build the ramdisk or is that
> > provided as image by boot-floppies/D-I? Can't rememer.
> 
> Provided by d-i. I always tried to avoid root requirement. It may be
> that sparc building needs root right (in order loop-munt a file and edit
> it IIRC).

debix-imager doesn't allow to loop-mount a given image for security
reasons. Maybe d-i can be convinced to do the edit or provide a tar
file instead.

MfG
Goswin

Re: A simple question about downloading debian-30r1-i386-binary-x.iso's

[Goswin von Brederlow]

Richard Atterer <[EMAIL PROTECTED]> writes:

> On Mon, Aug 25, 2003 at 10:16:24AM +, john smith wrote:
> > A simple question about downloading debian-30r1-i386-binary-x.iso's
> > 
> > Im currently wishing to download Linux, and was just wondering if i had to 
> > download all of the ISO's on this page 
> > "ftp://gd.tuwien.ac.at/opsys/linux/debian-cd/images/3.0_r1/i386/";
> > 
> > Or wether i just have to download one.?
> 
> See :
> 
>   Which of the numerous CD images should I download? Do I need all of them?
>   
>   No, you only need the CD images for your computer's architecture. The 
>   architecture is the type of hardware your computer uses. By far the most 
>   popular one is the Intel architecture, so most people will only want to 
>   get the images for "i386".
>   
>   Furthermore, in most cases it is not necessary to download all of the 
>   images for your architecture. The packages on the CDs are sorted by 
>   popularity: CD 1 contains the installation system and the most popular 
>   packages. CD 2 contains slightly less popular ones, CD 3 even less 
>   popular ones, etc. You will probably not need CD 3 and higher unless you 
>   have very special requirements. (And in case you happen to need a package 
>   later on which is not on one of the CDs you downloaded, you can always 
>   install that package directly from the Internet.)
>   
>   Finally, for each architecture there are two versions of the first CD, 
>   the normal and the non-US version. You only need one of these! See below 
>   for details.

This should be updated for the netinstall CDs. I hope sarge will get
official ones.

The minimum CD is 10 MB for setups with a already working router.
~30 MB for systems that needs ppp/dsl/(isdn?) for install.
~300 MB for useable system with or without internet.

The cdimages webpage has links to semi official images. Unless you
want to produce CDs you should never download the Debian CD set. Go to
the next shop and buy one. The media costs more.

MfG
Goswin

Re: Jigdo Automation

[Goswin von Brederlow]

Roger Guenter Trott <[EMAIL PROTECTED]> writes:

> Hello everybody,
> 
> i would like to use jigdo to keep my SID cd rom images up to date.
> 
> My problem is as follows: I want to do this automatically at night
> (means no user interaction :-))
> 
> It is no problem to get 11 loop mounts, but i can't figure out how to
> use something like
> 
> 
> for I in *.iso do ; jigdo . done ;
> 
> question: is this possible ?

rsync the images.

MfG
Goswin

Re: Making unofficial extension CDs

[Goswin von Brederlow]

Terry Hancock <[EMAIL PROTECTED]> writes:

> Is there an online reference that describes how the Debian 
> archives are constructed?  Such as how "Packages.gz" gets 
> built, etc?

man dpkg-scanpackages
man dpkg-scansources

As to the Release files there is some docs in apt but I think its
mostly look at existing once and do the same.

> I need to create a CD set based on a set of extra, 
> unofficial Debian packages.  My understanding is that if 
> this is done right, it will be possible to combine such a 
> CD with an official distribution set to make an extended 
> set, with local packages, unofficial deb packages, etc, 
> that can be installed and maintained more-or-less just like 
> you would a standard system.
> 
> The debian-cd instructions state that you need a "Local 
> Debian Mirror", but don't describe how you create it, 
> especially if you *aren't* just copying the official 
> archives.

apt-cache show debmirror (for the official archives)

Otherwise (untested) I think you just dump your debs into a directory
and point debian-cd to it. It should generate the neccessary
Packages/Sources and Release files itself.

> I really feel like this has to be a FAQ, but I haven't been 
> able to find it with Google or the search engine on the 
> Debian site.

MfG
Goswin

Re: installatin

[Goswin von Brederlow]

"Matthias Tepe" <[EMAIL PROTECTED]> writes:

> da mein cd laufwerk nicht von der demian cd booted, boote ich mit einer win 98
> cd, wechsel dann die
> 
> cd und starte auf der demian cd im ordner install die boot datei.
> 
> ich verstehe zwar nicht warum die demian cd nicht automatisch booted und die
> win98 cd woll.

Alle Debian binary CDs sind bootbar. Auf der 1. CD ist ein multiboot
menu drauf das einem eine Auswahl verschiedener Kernel
ermoeglicht. Das funktioniert leider nicht ueberall.

Statt der Auswahl kann man aber auch CD 2-6 nehmen auf denen jeweils
ein anderer kernel drauf ist. Irgendwo steht auch was auf was ist,
weiss das nciht auswendig. Probier einfach mal von einer anderen zu
booten.

> auf jedenfall beginnt da auch eine installation die dann aber abgebrochen wird
> und ich weiß nicht warum.
> 
> ich habe auch nicht die gewalltige ahnung , aufjedenfall mache ich etwas
> falsch und ich weiß nicht was
> 
> kernel panic: vfs: unable to mount root fs on 01:00

Er sollte die ramdisk mit der Installationsroutine mounten. Von der
Ausgabe her wuerd ich sagen das die .bat datei Fehlerhaft ist und die
Falschen parameter uebergibt.

> was muß ich anders machen damit ich demian auf meinen laptop insallieren
> kann??

Wenn keine der CDs bootet haeng doch mal bitte die .bat datei an die
du zum starten benutzt hast. Vieleicht ist da nur nen simpler
tippfehler drinn.

Ansonsten kanst du auch bootfloppies (wie in der Dokumentation
beschrieben) erstellen, Floppylaufwerk vorrausgesetzt natuerlich.

Als wirklich allerletzten Ausweg gaebs dann noch Platte ausbauen und
woanders installieren.

MfG
Goswin

Re: custom cd

[Goswin von Brederlow]

"St Francis Team" <[EMAIL PROTECTED]> writes:

> Sir,
> 
> 
> We tried to prepare bootable cd using knoppix remastering howto steps . 
> However the cd did not boot. Are there some steps to load boot.img boot.cat? 
> We had just  copied them from knoppix 3.2 cd using "cp" command.
> 
> Please help.

Knoppix is not quite Debian so your on the wrong list for that. Better
contact Knoppix itself for this.

MfG
Goswin

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Mattias Wadenstein <[EMAIL PROTECTED]> writes:

> I suspect I'm not the only one that thinks that this might be a good idea.
> I'm actually planning on offering this, what I'd like feedback on is how
> official it should be.

mldonkey urls should also be provided. Thats even easier than
bittorrent since its just an url containing a checksum.

> Should I (or whoever is doing them) place the .torrents in the debian-cd
> directory on cdimage.debian.org so that they are mirrored all over the
> place and look official or should I place them in some unofficial/test-
> directory?
> 
> When it comes to tracker I'm planning on using a dedicated dns name with a
> short ttl so we can repoint it at need if the machine can't handle it (I
> should be able to find a fast one though).

It would be good if debian had an official tracker (doesn't need to
have the image but it would be good).

The debian-installer group is currently struggling to get
autobuildable images. I guess it might be good to add the creation of
a torrent and donkey file there too so every arch will autobuild those
files too.

I'm all for it. Bittorrent is still one of the best.

MfG
Goswin

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

jason andrade <[EMAIL PROTECTED]> writes:

> On Mon, 5 Oct 2003, Goswin von Brederlow wrote:
> 
> > It would be good if debian had an official tracker (doesn't need to
> > have the image but it would be good).
> 
> [...]
> 
> > I'm all for it. Bittorrent is still one of the best.
> 
> i've heard a fair amount of discussion about BT but still haven't
> figured out how we can also use a P2P app in a S2C (server2client)
> manner.  how can mirror sites also make available the ISO images
> (and other files) available via the concept of a BT 'server' which
> doesn't have to download anything but can be pointed at a file
> or number of files which are then accessible via BT clients ?
> 
> and please don't say "just download the ISO and leave it running"
> as that isn't a viable idea from a server POV.

With bittorrent you have to have a running tracker. You also need
clients connected to the tracker that feed the data. That means each
mirror would have to run a bittorrent client on their local image.

Doogie was thinking about extending bittorrent to also download files
via http so normal http mirrors could be utilized too. Don't think
that will be ready for sarge though.


I don't think it would be too hard to get a group to mirror the debian
CD images with bittorrent to their servers and leave the clients
running for the first weak or so till the big rush is over. If Debian
says they will only do jidgo and bittorrent the first week that should
give enough incentive.

MfG
Goswin

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Patrick Strasser <[EMAIL PROTECTED]> writes:

> Mattias Wadenstein wrote:
> 
> [about offering Debian CD-images via BitTorrent]
> > I suspect I'm not the only one that thinks that this might be a good idea.
> > I'm actually planning on offering this, what I'd like feedback on is how
> > official it should be.
> 
> I know that people like BitTorrent, and it that it is a nice P2P-System.
> But what is the point of a second distribution system besides a
> perfectly working distribution system that uses already existing
> staging points?
> 
> 
> I don't see an advantage in BitTorrent. It needs new software, users
> to spread data, extra administration, support. Moreover jigdo is IMO
> the best way to spread Debian CDs, thanks to the nature of ISO9660.

Jigdo produces a good initial template image that often needs further
repairs by rsync.

Bittorrent on the other hand is self repairing (like rsync).
Also bittorrent utilizes the leechers upstream bandwith to share data
and reduce the traffic on the mirror.


A mixture of rsync, bittorrent and jigdo would be best.

MfG
Goswin

Re: Dedication to 'Espy' still on CDs?

[Goswin von Brederlow]

Frank Bauer <[EMAIL PROTECTED]> writes:

> Hi.
> 
> I', testing sarge netinst iso and I've noticed, that there are
> still those files about dedication to Joel 'Espy' Klecker,
> which were introduced for _potato_ and were also on _woody_ discs.
> 
> With all respect to him, isn't time to remove those files from
> CDs?

Are they in /doc/? /doc/ is taken from woody at the moment.

MfG
Goswin

Re: Sarge-Installation: dpkg: error processing

[Goswin von Brederlow]

Martin Sjögren <[EMAIL PROTECTED]> writes:

> I bet, udebs (like udpkg, rootskel,...) aren't meant to be installed on
> a normal Debian system.
> 
> > rootskel template parse error: Template #7 in /tmp/template.2.7.910 doesn't 
> > cont 
> > in a 'Template:' line
> > dpkg: error processing
> > Errors were encountered while processing:
> > /cdrom//pool/main/c/cdebconf/cdebconf_udeb_0.41_i386.udeb (e.g.)
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > Some errors occured while unpacking.
> > Only errors above this message are important.
> > Please fix them and run Install (dselect) again.
> 
> It seems to me like apt-cdrom interacts really badly with a CD that has
> both debs and udebs on it... Does anybody have an idea how to fix this?

Am I right to assume anna and libdebian-installer will ignore pining?
Then it should be easy to add a pin of <100 to the udebs keeping them
from ever being installed automatically.

MfG
Goswin

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Steve McIntyre <[EMAIL PROTECTED]> writes:

> On Sun, Oct 12, 2003 at 02:05:58PM +0200, Goswin von Brederlow wrote:
> >
> >Jigdo produces a good initial template image that often needs further
> >repairs by rsync.
> 
> ??? What makes you say this? I've never had to repair images after
> jigdo has run successfully...

Never had jigdo fail to download some file for some reason or another?

Or a bittoggler that goes undetected by the TCP checksums.

MfG
Goswin

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Christian Leber <[EMAIL PROTECTED]> writes:

> On Sun, Oct 12, 2003 at 03:10:29PM +0200, Goswin von Brederlow wrote:
> 
> > Or a bittoggler that goes undetected by the TCP checksums.
> 
> It's very unlikely because the jigdo files have md5
> checksum's for every file and i think they are used.

And if they detect an error?

What if your local mirror has a broken deb on it?

You need rsync to correct that then unless you want to fiddle around
till you find a working file.

MfG
Goswin

Re: Bittorrent distribution of cdimages

[Goswin von Brederlow]

Christian Leber <[EMAIL PROTECTED]> writes:

> On Sun, Oct 12, 2003 at 04:22:49PM +0200, Goswin von Brederlow wrote:
> 
> > And if they detect an error?
> 
> I would rerun jigdo, i think it would download the file again.
> If this would fail I would report this to the mirror maintainer and use
> another mirror.
> 
> > What if your local mirror has a broken deb on it?
> 
> I would fix it.

Without a valid source it can't.

> > You need rsync to correct that then unless you want to fiddle around
> > till you find a working file.
> 
> And if the iso on the rsync server is brocken?

Then the md5sums of the official images will be bogus as well and all
hell breaks loose.

> I really like rsync and use it for my daily backup, but i don't see a
> reason to use it together with jigdo.

Your choice. Seen enough people on irc saying the md5sum differs after
jigdo had been run.

MfG
Goswin

Re: [joeyh@debian.org: Bug#215469: don't include unnecessary udebs on the cd]

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Hello,
> 
> I just got this bug. It looks like we aren't smart enough about the
> selection of udebs to include on the CD ...
> 
> The initial idea was to include them all so that all install scenario
> can happen but it looks like there are udebs which are useless since
> they are simple "file repositories" for d-i.
> 
> And the list is getting so big, that it doesn't make sense to include
> everything for netinst & business card CD.

My new D-I build script builds 20MB businescard cds compared to the
48MB? debian-cd images. There is more to save on docs, keyring,
indices, Contents files,... than on the udebs.

> I think we need to update the script that generates the task files which
> lists udebs. Santiago ? 
> 
> The first step is probably just to have exclusion list/pattern used by
> tools/generate_di_list and/or tools/generate_di+k_list ...
> 
> Cheers,
> -- 
> Raphaël Hertzog -+- http://www.ouaza.com
> Formation Linux et logiciel libre : http://www.logidee.com
> Earn money with free software: http://www.geniustrader.org
> From: Joey Hess <[EMAIL PROTECTED]>
> Subject: Bug#215469: don't include unnecessary udebs on the cd
> To: Debian Bug Tracking System <[EMAIL PROTECTED]>
> Date: Sun, 12 Oct 2003 19:48:01 -0400
> Reply-To: Joey Hess <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Resent-From: Joey Hess <[EMAIL PROTECTED]>
> 
> Package: debian-cd
> Severity: normal
> 
> The businesscard and netinst cd images at
> http://gluck.debian.org/cdimage/testing/netinst/i386/ are bigger than
> they need to be. partly because they include such useless things as
> this:
> 
> ./pool/main/k/kernel-image-2.4.20-1-i386-udeb/kernel-image-2.4.20-1-386-udeb_2.4.20-8_i386.udeb
> 
> This contains only a kernel, in a form users cannot use, and that the
> installer will only waste a lot of memory loading into its initrd after
> it has already booted.
> 
> ./pool/main/b/busybox-cvs/busybox-cvs-udeb_20030926-1_i386.udeb
> ./pool/main/b/busybox/busybox-udeb_0.60.5-2_i386.udeb
> 
> All d-i images already come with the appropriate busybox udeb installed
> on the image.
> 
> ./pool/main/c/cdrom-detect/cdrom-detect_0.31_all.udeb
> ./pool/main/c/cdrom-retriever/cdrom-retriever_0.08_all.udeb
> 
> If the installer can find these on the CD, it does not need them.
> 
> ./pool/main/c/cdebconf/cdebconf-gtk-udeb_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-newt-udeb_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-priority_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-slang-udeb_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-text-udeb_0.46_i386.udeb
> ./pool/main/c/cdebconf/cdebconf-udeb_0.46_i386.udeb
> 
> These are probably useless, d-i boot images include at least one
> cdebconf frontend.
> 
> Etc. I'm sure you could save a *lot* of space by working with the d-i
> team to whittle down the udebs on the cd images to a set that is
> appropriate for the purpose of the CD. As it is these images are getting
> too big to be useful.

I'm working on getting propper lists what udebs will be always on the
boot media, what should be on CD and what is just leftovers or
unsuported (like the gtk frontend). Thanks for the hint about
retrievers and cdebconf.

After that d-i will generate partial Packages files containing just
the right files for each part. Those will be used by debmirror for
d-i developer to keep a partial mirror. They will work just as well
for debian-cd.


I'm not yet quite sure on how to get debian-cd to put the right stuff
on the right type of CD, or more concrete how to get it not to put some
stuff on it. A lot of stuff is just hardcoded in, like wgeting the
daily build d-i images of the net. Ideas are welcome there.

MfG
Goswin

Packaging debian-installer images for upload and to where?

[Goswin von Brederlow]

Hi,

debian-installer has two problems that need a decision soon:

1. Where will debian-installer images be placed?
   We have floppy, cdrom, netboot and hd-install images ranging from
   1.4 MB floppies, 5-20MB netboot/hd-install images and 5/20/50MB
   cdrom isos. Total 100-150 MB per arch.

   Images should be build regulary or even daily and stored for a few
   days to allow for testing and savekeeping of tested and working
   images.

   Would ftp://ftp.debian.org/debian/dists/sid/main/disks-/ be
   reasonable? Or should they be put on cdimage.debian.org (even the
   floppy, net and hd images)?

2. How do we package up the images for upload?



Debian installer has to few developers with to few architectures to
manually compile and upload images for every arch. During the
Debian-installer Debcamp in Oldenburg we discussed using the
autobuilders to build the images. We would create a source package and
upload that. The autobuilder pick it up along with normal sources and
build it.

Now the problem begins:

- The build needs to download udebs. Currently that means access to
any rsync mirror (ftp or any apt/sources.list could be aranged). This
should be easy to arrange. We just try and contact the buildd
maintainer if it fails.

- The build produces some floppy images, some cdrom.iso, some tftp
images and some tar.gz archives. What to do with them.
It has been suggested to build debs or udebs containing these files
but thats an ugly solution. I would be nice if the files could be
added as such to the changes file, uploaded in the normal queue and
put into dists/sid/main/disks-// by the ftp scripts.

E.g: (only important entries of the changes file)
Architecture: i386
Version: 20031018
Maintainer: Debian Install System Team 
Files: 
 bd065541fe35d5af69a016352a8c84b6 3334144 disks-i386 standard cdrom-boot.iso
 90f048938e12e5f3c6d10344b07db63b 1474560 disks-i386 standard floppy-boot.img


Currently pretty much all the porting to different architectures is at
a standstill because the people with the hardware have no clue how to
build images and the people with the knowledge to build and fix bugs
have no hardware. I and some others feel that use of the autobuilders
to compile and build images is essential to getting porting underway
again even if they throw the build images away instead of uploading
them.

Objections, comments, suggestions?

MfG
Goswin

Re: Installations-Images

[Goswin von Brederlow]

Jürgen Siepmann <[EMAIL PROTECTED]> writes:

> Hallo,
> 
> mir ist unklar, weshalb auf
> 
> http://www.debian.org/CD/netinst/
> 
> Inoffizielle Netz-Installations-Images für das "stable" Release
> und
> Offizielle Netz-Installations-Images für das "testing" Release
> 
> angeboten werden.
> 
> Gibt es keine
> 
> Offiziellen Netz-Installations-Images für das "stable" Release?

Du hast es erfasst.

MfG
Goswin

Re: cds

[Goswin von Brederlow]

"JeffMacko" <[EMAIL PROTECTED]> writes:

> Debian:
> 
> I can't seem to find anyone to tell me the diff. from scsi and regular
> burning[writing]. Is there an accuracy diff. why pay so much more for scsi. I
> want to buy an 8cd burner but I don't want drop out or anything half way
> thru. Is scsi more faultless.or even 100%?
> 
> Looking forward to your reply, Ive searched for months.
> 
> Thanks Alot
> 
> Jeff&[EMAIL PROTECTED]

This is rather offtopic but here we go:

Until recently ide burners would work through a scsi emulation layer
(ide-scsi) so that they would appear as scsi burners to the
software. But nowadays burning directly to ATAPI is also possible.

As to the difference, scsi is of cause the better system and the firms
let you bleed for it. Ide has drawbacks when using multiple drives at
once (like harddisk and burner together) but nothing severe for a home
system. A firm wouldn't want its database server to go to half speed
just because the backup system is burning a cdrom.

>From time to time ide gets errors where scsi would corret the
error. But even if its as much as 1 cd in 100 that fails due to ide
(and I'm not saying its anywhere that much) just think about how many
cds you have to burn before you recoverd the extra price for scsi.

MfG
Goswin

Re: apt-get

[Goswin von Brederlow]

"Mathieu R." <[EMAIL PROTECTED]> writes:

> HI
> is the function "apt-get update/upgrade" available with the DOWNLOADED
> version of debian 30r1 ?

There is Debian, the whole of Debian and only Debian.

Doesn't matter where you get it from, apt-get is apt-get.

MfG
Goswin

Re: Usage of isolinux on the beta CDs

[Goswin von Brederlow]

Santiago Garcia Mantinan <[EMAIL PROTECTED]> writes:

> Umm, seems like we go again for the same discusion, ok, I've been gathering
> some old links to try to shorten this.
> 
> The isolinux / multiboot / boot floppy emulation (syslinux) decision was
> already discussed for woody, at that time I was building unofficial images
> for all woody's arches, and I also partitipated on this discusion, I dislike
> isolinux because of the problems they give in old machines, but I also see
> its good side letting us have bigger and different initrds and kernels.

But we don't have that for the netinstall and businesscard CDs.

> > > it seems that we are locking out people from testing by using isolinux
> > > on our netinst/businesscard CDs, see #220139 and #220139.
> > > 
> > > Since we do not need any of isolinux's features I propose to use
> > > syslinux on the CDs.
> 
> We are using these features, current isolinux setup allows the user to
> select to boot the "net" initrd or the "cdrom" initrd. I don't know if this
> is wanted, this must be decided by the debian-installer guys, if we want to
> offer just the posibility to boot the cdrom image we can just boot
> cdrom.img, I have just tried it and it works, even though the setup for
> syslinux should be changed a bit to include the help screens and all that,
> this should be done in debian-installer, as it is d-i who makes that image.

I've been working on the new build scripts for d-i to build more
functional images directly. They generate 3 different CD images each
suited specifically to one task and one task only:

5MB bootcd - just boots but is like netboot or floppy boot in all
other respects

20MB d-i cd - image with tons of udebs to get your network up and
running and disk partitions so you can install base over net.

60MB base cd - image with udebs and all the debs needed to install
base. Everything needed till the first reboot (and a little more
e.g. for dsl). You have a fully functional Debian without any net
access but nothing in the way of apps.



Given those three types its a bit pointless to have multiple initrds
on the cdrom. People who want less than is on the cdrom should have
downloaded the smaller cd in the first place. I know the beta1 scripts
don't build a pure bootcd image but thats coming now that beta1 is out.

In cases were you end up with an old cd and would like to not use
the outdated (u)debs on the cdrom I say tough luck. People should live
with the old udebs or rsync a fresh image. Its only 5 or 20MB. Not
supporting a lot of older hardware just to be able to choose a
different behaviour not intended by the cd is not worth it.

> > Maybe we could put isolinux on the *second* CD, with eventually an
> > initrd that supports SCSI cdroms.
> 
> That sounds fine with me if it is ok to drop the net initrd from the booting
> options of the cds.

What second cd? Only the full set has multiple cds.

For a cd with isolinux we should probably build a huge initrd with all
the ide/scsi/cd modules preinstalled. We are not bound by the 2.88MB
limit there, right?

> Well, I don't know  what else to say, in the full cd set we really can have
> different booting methods, one on each cd, the important thing is to decide
> what do we put on the netinst/bussinesscard cds and also how do we order the
> methods in the full cd set.
> 
> If something I said needs farther explanation (I know my english sucks) just
> ask for it.

As a conclusion: My opinion is that the boot/netinst/bussinesscard
images are small enough to force people to download the right one in
favour of supporting all cdrom bootable i386 hardware. That means a
2.88MB floppy image with syslinux.

For the full set smae as with previous releases: cd 1 multiboot and cd
2 - X different single boot flavours.

MfG
Goswin

List of udebs to be included on the CDs

[Goswin von Brederlow]

Hi,

as promised I cleaned up the list of udebs that should be present on
the CDs:

The lists are in
http://cvs.debian.org/debian-installer/build/pkg-lists/mirror_udeb/

The lists contain all udebs that aren't obsolete (like the out-of-date
gtk udebs) and aren't already on the cdroms initrd. That means all
udebs that could possibly be loaded from cdrom.

The lists still contain all versions of kernel-image and modules but
debian-installer normaly only uses only one (but not on all
archs). That might be cleaned up in the near future.

MfG
Goswin

Re: Problems with Sarge netinst and Yaboot

[Goswin von Brederlow]

<[EMAIL PROTECTED]> writes:

> Hi, I've just bought a PowerBook G4 12".
> 
> I have downloaded the Beta1 of Sarge NetInst for PowerPC (November 9th)
> and I have got a problem at the beginning of the installation.
> 
> I enter Open Firmware, and then boot with:
> boot cd:\\yaboot
> 
> And then I get:
> /[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL 
> PROTECTED]:0,yaboot.conf: Unknown or
> corrupt filesystem
> Can't open config file
> Welcome to yaboot version 1.3.10
> Enter "help" to get some basic usage information
> boot: 
> Please wait, loading kernel...
> :0,/vmlinux: Unable to open file, Invalid device
> 
> The ISO image is correct (I have checked the MD5sum) and I've burned it a
> couple of times with the same results.
> 
> After trying some things (it was the first time I used yaboot) I've got it
> working with:
> boot: cd:0,/install/powermac/vmlinux initrd=/install/powermac/root.bin
> ramdisk_size=8192 init=/linuxrc
> 
> Well, it is not working yet, now it boots the kernel but it can't mount
> the root partition or initrd, it says (after detecting mouse, pci devices,
> etc ...):
> VFS: Cannot open root device "" or 16:01
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 16:01
>  <0>Rebooting in 180 seconds..
> 
> If I specify root=/dev/ram0 then it says (earlier than without specifying
> it):
> cramfs: wrong magic
> Kernel panic: VFS: Unable to mount root fs on 01:00
> ...
> 
> I've tried several combinations of these options without any good result.
> 
> Thanks for your help (please, keep me in CC because I'm not subscribed to
> the lists)

My branch of d-i has the following yaboot.conf:

debian-installer/build% cat boot/powerpc/yaboot.conf
## This yaboot.conf is for CD booting only, do not use as reference.
## Debian GNU/Linux PowerPC (woody)

# It is important not to have a comma after cd:
device=cd:
default=install
timeout=100

# FIXME: will this be the correct path?
message=/install/powermac/boot.msg

image=/install/powermac/linux
label=install
initrd=/install/powermac/root.bin
append="devfs=mount,dall"
initrd-size=8192
read-only

# some machines have wonky framebuffer support
image=/install/powermac/linux
label=install-safe
initrd=/install/powermac/root.bin
initrd-size=8192
append="video=ofonly devfs=mount,dall"
read-only

You might or might nor need root=/dev/ram. The beta-1 images are done
by debian-cd so the yaboot.conf and actual image names and locations
might differ but you should be able to compare them.

MfG
Goswin

PS: bugs in the beta-1 yaboot.conf should be filed against debian-cd, not much 
debian-boot can do about it

Re: Some observations about Debian installation

[Goswin von Brederlow]

[EMAIL PROTECTED] (Otto Wyss) writes:

> I'm just gone through a new Debian installation process and think I know
> a little bit what's wrong.
> 
> 1. The current stable release (3.0r1) is just outdated.
> 2. There are way too many show stoppers in the testing release (3.1)
> installation
> 
> 1. takes care that (almost) nobody uses Debian/stable for new systems.
> 2. takes care that (almost) everybody takes out his old Woody CD and
> does a dist-upgrade or similar. Therefore none of the installation
> problems gets mentioned and solved, at least not within a wish able time
> frame. And if someone still is determined and goes through the process
> and mentioning any problems he gets either no answer (see
> "http://lists.debian.org/debian-boot/2003/debian-boot-200311/msg01073.ht
> ml") or just some not very helpful (see

Discussed, explained and mostly fixed on the ML and cvs.

> "http://lists.debian.org/debian-devel/2003/debian-devel-200311/msg01248.
> html").

Installing kernel-image-2.4.22

What has that got to do with installing sarge?
 
> The problems I've mention are show stoppers for any user not as much
> accustomed to Debian as I. And they have to be fixed in one or the other
> way. Else Debian still keeps its image as a hacker distribution.
> Regardless how good or bad Debian is and regardless how many RC bugs
> exists, if a user encounters a show stopper during installation this
> user is lost. Gurus might find a solution but casual users simply switch
> to another distribution. Therefore the installation process has to be
> foolproof to a certain degree.

You are welcome to help.

MfG
Goswin

Re: System Question

[Goswin von Brederlow]

"Mauricio" <[EMAIL PROTECTED]> writes:

> Hello,
> 
> I'm going to download de Debian CD Images for my computer. It's an AMD Athlon 
> XP 1700+. Wich version I must download? the Intel-Compatible or other one?
> 
> Other question I want to do: is there a new stable version near from now to 
> be completed? because I don't have an ADSL/Cable-modem and I need to pay for 
> the ISO-CD download. If a new version is going to be released, I want to wait 
> this little time to download it.
> 
> Sorry if my words/english are not very clearly.
> 
> Thanks for your answer.
> Regards,
> 
> Mauricio Ibáñez
> Montevideo, Uruguay.

Don't download isos. 80% of the stuff you don't need or want.

Download a netinstall cd with base (those 30-100MB isos), install
base, configure your modem and then install directly off the net.

That way you only have to download the programs you actually are going
to install. As an added bonus the new stable revision 3.0R2 has been
pushed to the debian mirrors but the CDs are not yet available.
Installing over the net you will get newer packages and don't have to
upgrade next week.

MfG
Goswin

Re: broken link

[Goswin von Brederlow]

Josef Frühwirth <[EMAIL PROTECTED]> writes:

> Hello!
> I hope i`m sending this to the right adress.
> 
> On  page
> 
> http://www.debian.org/CD/netinst/
> 
> the link
> 
> Official "testing" images 
> 
> leads to an access error!
> 
> May be this is a feature of that page but in my opinion its a bug.
> Therefore i`m telling you:-)

Most likely caused by the compromised servers not being fully
reactivated yet and nothing can be changed till the logins are enabled
again.

By the way, the non daily build images are in the ftp archive if you
want to test them out.

MfG
Goswin

Re: dependency problem

[Goswin von Brederlow]

tej trivedi <[EMAIL PROTECTED]> writes:

> hi!
> 
>  
> 
> i am a new user to knoppix.i wanted to know whether there is any command by
> which i can find the list of packages that i can safely remove while
> remastering knoppix cd. i haved made 2 remastered knoppix CDs, but the problem
> is that one of them does not boot at all ,and the second does not go to
> GUI. so if some of you know any command to get the list of packages that can
> be safely removed, then it would be of great help to me.
> 
> waiting for reply

Repeat after me:

KNOPPIX IS NOT DEBIAN!
KNOPPIX IS NOT DEBIAN!
KNOPPIX IS NOT DEBIAN!

MfG
Goswin

Re: Not usefull kernel images take all first Debian sarge CD :(

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> Quoting Adam Majer:
> > I agree. This is crazzy. But how the heck do you get this?
> > 
> > > kernel-image-2.4.22-xfs   - ~22 Mb
> > > kernel-image-2.4.22-i386  - ~78 Mb
> > 
> [...]
> > So even if you had 8 kernels, that would be 80M. To occupy most of the 
> > disk, I think you'll need more than 25 kernels..
> 
> We have many kernels, here's the list that I excluded yesterday evening:
> kernel-image-2.6.0-test11-1-386
> kernel-image-2.6.0-test9-1-386

Test and pre kernels could be kept in sid exclusively.

> kernel-image-2.4.20-3-386
> kernel-image-2.4.20-3-586tsc
> kernel-image-2.4.20-3-686
> kernel-image-2.4.20-3-686-smp
> kernel-image-2.4.20-3-k6
> kernel-image-2.4.20-3-k7
> kernel-image-2.4.20-3-k7-smp

kernel-source-2.4.20 is needed for m68k, keep that on some cd.
And e.g. kernel-image-2.4.20-amiga.

For non i386 the list of kernels differs widely between archs.

> kernel-image-2.4.21-5-386
> kernel-image-2.4.21-5-586tsc
> kernel-image-2.4.21-5-686
> kernel-image-2.4.21-5-686-smp
> kernel-image-2.4.21-5-k6
> kernel-image-2.4.21-5-k7
> kernel-image-2.4.21-5-k7-smp
> kernel-image-2.4.22-1-386
> kernel-image-2.4.22-1-586tsc
> kernel-image-2.4.22-1-686
> kernel-image-2.4.22-1-686-smp
> kernel-image-2.4.22-1-k6
> kernel-image-2.4.22-1-k7
> kernel-image-2.4.22-1-k7-smp
> kernel-image-2.4.23-1-386
> kernel-image-2.4.23-1-586tsc
> kernel-image-2.4.23-1-686
> kernel-image-2.4.23-1-686-smp
> kernel-image-2.4.23-1-k6
> kernel-image-2.4.23-1-k7
> kernel-image-2.4.23-1-k7-smp
> 
> That makes ~30 kernels. I kept 2.4.24* and 2.6.0-1*.
> 
> > Anyway, the number of kernel on the CDs should be reduced anyway.
> > We should only have the i386 version and let people build their
> > own variants if they choose to (or DL from mirrors).
> 
> No, IIRC debian-installer installs the good one depending on /proc/cpu.  So
> we'd better keep all the variants on the first CD. But we should definitely
> stick to one version of the kernel.
> 
> Cheers,

The first CD should have only one version, the one used in D-I, but as
many flavours as possible without overcrowding. All other versions
could be on later CDs. People might want a 2.2.x kernel or need a
2.6.0 kernel for their hardware.

MfG
Goswin

Re: Not usefull kernel images take all first Debian sarge CD :(

[Goswin von Brederlow]

Raphael Hertzog <[EMAIL PROTECTED]> writes:

> [ removing debian-devel which is not really necessary but added
>   debian-boot ]
> 
> Quoting Goswin von Brederlow:
> > Test and pre kernels could be kept in sid exclusively.
> 
> They could, but for the moment they aren't and I have to live up with
> that. :)
> 
> > For non i386 the list of kernels differs widely between archs.
> 
> Yes I address the problem only for i386. But I bet the problem is less
> serious for other arches because they don't have so frequent uploads of
> kernels, aren't they ?

None have that many flavours and fewer versions too.
 
> > The first CD should have only one version, the one used in D-I, but as
> > many flavours as possible without overcrowding. All other versions
> > could be on later CDs. People might want a 2.2.x kernel or need a
> > 2.6.0 kernel for their hardware.
> 
> debian-installer doesn't use 2.4.24 yet, does that mean that I broke
> d-i by excluding the other kernels from the CDs ? Is that's true,
> couldn't d-i be a bit more clueful and install the latest
> kernel-image-2.4.x package that it finds ?
> 
> Cheers,
> -- 
> Raphaël Hertzog -+- http://www.ouaza.com
> Formation Linux et logiciel libre : http://www.logidee.com
> Earn money with free software: http://www.geniustrader.org

D-I should preferably install the kernel image its booted with. We
know that one works. I think its looking at uname to figure out the
version to look for at runtime.

MfG
Goswin

Re: debmirror can't download some boot system's files

[Goswin von Brederlow]

Alexander Golovin <[EMAIL PROTECTED]> writes:

>  I had downloaded my local Debian Etch mirror with debmirror, then I was
> trying to create my dvd's. Now all is ok, except one: for create first
> bootable dvd "debian-40r3-i386-DVD-1.iso" I need some files which hadn't
> downloaded with debmirror:
>
> debian/dists/etch/main/installer-i386/20070308etch2/images/floppy/boot.img
> debian/dists/etch/main/installer-i386/20070308etch2/images/cdrom/initrd.gz
> debian/dists/etch/main/installer-i386/20070308etch2/images/cdrom/gtk/initrd.gz
> debian/dists/etch/main/installer-i386/20070308etch2/images/floppy/cd-drivers.img
> debian/dists/etch/main/installer-i386/20070308etch2/images/cdrom/gtk/vmlinuz
> debian/dists/etch/main/installer-i386/20070308etch2/images/floppy/root.img
>
>  I had downloaded all this files with wget and copied to my local
> mirror, before that debian-40r3-i386-DVD-1.iso was created successfully.
>
>  I had used debmirror with that options:
> debmirror debian --nosource --host=ftp.fi.debian.org --method=http --progress 
> --dist=etch --section=main,contrib,non-free,main/debian-installer --arch=i386 
> --ignore-release-gpg
>
>  What's wrong with that, had I missed some debmirror options?

debmirror only downloads files indexed in Packages and Sources. The
installer images are not among them.

In the past debian-cd would fetch those images itself so that never
was a pressing problem.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: On installation media and firmware [Re: New section for firmware]

[Goswin von Brederlow]

Frans Pop  writes:

> On Wednesday 24 December 2008, Don Armstrong wrote:
>> It would be nice if you (or someone else) would then explain[1] why
>> having a limited set of d-i images + cd images which contained the
>> non-free firmware necessary for certain hardware to boot would be an
>> intractable solution. From where I sit, the major issues with it would
>> be:
>
> The major issue is that it does not solve all use-cases where firmware is 
> needed. It does not solve the problem for netboot installations, nor for 
> hd-media installations.

1) So you are saying the NIC can netboot without firmware just fine
but won't work under linux at all?

2) Also which hd-media installations need firmware to access udebs?

3) A d-i image which contained the non-free firmware would work just
fine for netboot or hd-media.


Also it does not have to solve all use-cases. It just has to solve
more than without this solution. Further not all install media have to
work all the time. So what if the netboot.iso won't work and you need
a non-free-businesscard.iso due to firmware udebs? As long as it
allows at least one method to work and allows more people to install
Debian than without that is a plus.

> Also, D-I currently does not support switching CDs during early parts of 
> the installation. Implementing that would be a fairly major pain.

With a cd image which contains the firmware there is no need to switch
the CD to a second just firmware image.

> We don't want to have users jump through hoops. Having to burn an 
> additional image just for firmware and having to switch to that image and 
> then switch back to the installation image is IMO a major hoop.

The hoops are for the debian-cd team to jump through, for them to
generate a 100% free and an actually usable image. Just like there was
cd1 and cd1+non-us a while back there would be cd1 and cd1+firmware.

> It also does not really add anything to the option we already have to load 
> firmware from removable media.

It would remove the need for the user to jump through hoops to create
and use a second removable media. Plus you said above CD switching
isn't possible early on.

> Cheers,
> FJP

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Live 5.0.0 i386 is maybe not i386

[Goswin von Brederlow]

Gary Lawrence Murphy  writes:

> I don't know if the mailing list accepts outside submissions; this
> address is listed on the CD page as the primary contact so here goes...
>
> I just downloaded
> http://debian.yorku.ca/debian-cd/5.0.0-live/i386/iso-cd/ and tried an
> install on a 1998-vintage Compaq Presario 1210; the Live boot fails on
> loading the Linux kernel, citing an invalid instruction error -- if
> I'm not mistaken, invalid instruction could only happen if the kernel
> or some module of the kernel is NOT i386
>
> yes, it is a pretty esoteric error, but an error nonetheless, no?

Debian has dropped support for i386 some time ago and now only
supports i486 upwards. So the name is a bit of a misnomer but it is
historical.

MfG
Goswin

PS: Try sarge or older.


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org