Re: Bug#1013079: installation-reports: GUI install option isn't visible on boot

[Chris Hofstaedtler]

Control: reassign -1 debian-cd

Hi,

* Holger Wansing :
> > > - On Jun 17, 2022, at 7:43 AM, Philip Hands p...@hands.com wrote:
> > > > 
> > > >  https://openqa.debian.net/tests/60553#step/_boot_to_debianinstaller/2
> > > > 
> > > > if you look closely in the highlighted box, you can just about see
> > > > "Graphical install" as a black font on dark_blue background, but it's
> > > > very close to invisible.
> > > > 
> > > > It should have an inverted background on the selected item, which then
> > > > makes the black text easily visible, as seen in the last working test,
> > > > using a netinst ISO from 2022-06-07 17:27:
> > > > 
> > > >  https://openqa.debian.net/tests/59056#step/_boot_to_debianinstaller/1

I'm reassigning this to debian-cd, because:
- grub2 upstream has deleted support for grayscale PNGs. I don't
  think this is coming back.
- the menu on the installer ISOs uses a grayscale image to highlight
  the currently selected menu entry. As demonstrated in the bug
  report, this is now broken.

While technically grub2 broke this, I'd think the way forward is for
debian-cd to convert the highlight PNGs to non-grayscale.

FTR:
debian-cd/data/bookworm/hl_c.png: PNG image data, 20 x 20, 8-bit grayscale, 
non-interlaced

Hope this helps in resolving the issue,
Chris

Bug#547454: cdrom: Installed system 2.6.26 fails to boot if CD is inserted upside down in drive

[Chris Hofstaedtler]

Control: reassign -1 initscripts

Reassigning to initscripts, as thats the most likely source for the
mount try after network startup.

Problem with non-free iso-dvd

[Chris De Boeck]

Hello,

I have problems installing Debian buster with the ISO at the following
location:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/10.2.0+nonfree/amd64/iso-dvd/


After a quick look, it seems the 'firmware' folder is empty.

Is this a known issue?

Kind Regards
Chris

Fwd: debian buster (weekly build of 2019-04-22) ISO-Hybrid LXQt no gui on dell optiplex

[Chris Guiver]

I've included the prior email for reference.

Testing 
https://cdimage.debian.org/mirror/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-lxqt.iso

dated : 2019-04-29 06:28

This week's boots on both
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
(mentioned as it failed on the first d755 [e8300,8gb] last week)

But fails (going to bash shell only) on
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
(booted fine on this box last week)

I haven't tried yet on the d960 (failed [bash only] using last week's
ISO); it's the machine I'm writing this on and haven't been willing to
reboot to try it today, and it booted to gui on other desktop boxes I
tried, plus all laptops (as per last week's) that I tried it on.

Same thumb drive used on each machine, and tried at least twice on any
failed machine (non-consecutive, ie. after a successful boot on
another box) like last time.

Chris Guiver
-- Forwarded message --
From: Chris Guiver 
Date: Fri, 26 Apr 2019 16:29:01 +1000
Subject: debian buster (weekly build of 2019-04-22) ISO-Hybrid LXQt no
gui on dell optiplex
To: debian-cd@lists.debian.org

I've been testing

https://cdimage.debian.org/mirror/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-lxqt.iso

dated   2019-04-22 06:17 (copy/paste from web site)

(I've had troubles getting into #debian-live so apologies for how this
is presented.)

The Debian Buster (10) LXQt ISO fails to boot into gui (booting into
terminal) on

dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)

(these are how I report these systems in Ubuntu testing; details being
from `lshw` copy/pasted from a list of hardware)

however of note I had NO issues on

dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
& others using same thumbdrive  (I'm excluding multi-screen issues
already reported, on debian, ubuntu and/or upstream, eg.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916105)

The [first] working system was used primarily as example; it's very
similar hardware (same model as one of the failed though it has
different external IO ports so yes it's different and with different
video card).  I haven't had issues with any laptop thus far tested.

There was no `reportbug` on the system, and if you need more
information, or want me to report another way - please just ask.

Chris Guiver

debian buster (weekly build of 2019-04-22) ISO-Hybrid LXQt no gui on dell optiplex

[Chris Guiver]

I've been testing

https://cdimage.debian.org/mirror/cdimage/weekly-live-builds/amd64/iso-hybrid/debian-live-testing-amd64-lxqt.iso

dated   2019-04-22 06:17 (copy/paste from web site)

(I've had troubles getting into #debian-live so apologies for how this
is presented.)

The Debian Buster (10) LXQt ISO fails to boot into gui (booting into
terminal) on

dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)

(these are how I report these systems in Ubuntu testing; details being
from `lshw` copy/pasted from a list of hardware)

however of note I had NO issues on

dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
& others using same thumbdrive  (I'm excluding multi-screen issues
already reported, on debian, ubuntu and/or upstream, eg.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916105)

The [first] working system was used primarily as example; it's very
similar hardware (same model as one of the failed though it has
different external IO ports so yes it's different and with different
video card).  I haven't had issues with any laptop thus far tested.

There was no `reportbug` on the system, and if you need more
information, or want me to report another way - please just ask.

Chris Guiver

Re: Bug#900918: debian-installer: Please make the generated images reproducible

[Chris Lamb]

Hi Cyril,

> I think I'd prefer closing this very bug report whenever what's in
> git gets uploaded

That would definitely work for me. Indeed, it would probably help
separate discussions/issues correctly as any followups are likely =
to be much more specific.

> half the build time is spent waiting for gzip to finish its work on
> a single core. Reproducibility is very nice but I would definitely
> hate to lose this huge speed-up.

Absolutely, hence my regret at suggesting a fallback to gzip. *nod*

> > Perhaps we need to record the environment after all
[…]
> Ah right, pigz isn't in Build-Depends, so it's not included in the
> .buildinfo file…

"the .buildinfo"? As I understood it we are not recording any
explicit debian-installer build attestation document that records
the environment at the moment. Again, will reload this all into my
head soon and come up with a suggested solution if required in
another bug report.

Thanks again. :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Re: Bug#900918: debian-installer: Please make the generated images reproducible

[Chris Lamb]

Philipp,

> > > Alternatively, we could make pigz a strict build requirement but
> > > that sounds a little antisocial.
> >
> > Right.
>
> In what way do you consider this antisocial and what's speaking against
> doing that?

I was using this word in a somewhat romantic sense; fewer
dependencies are "better" in some aesthetic or poetic sense.

Please do not read too much into it. :)

(I had also slightly assumed that pigz was only on some archs, but
I am clearly mistaken there...)


Regards,

-- 
  ,''`.
 : :'  :     Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Re: Bug#900918: debian-installer: Please make the generated images reproducible

[Chris Lamb]

Dear Cyril,

Thank you for your review and timely merge.

> That's looking good but I'm seeing new warnings because of gzip's being
> unhappy about the GZIP environment variable.

Interesting. However when you say "new" warnings I don't believe my
patch set actually added/changed this; indeed, it has not changed
since:

   
https://salsa.debian.org/lamby/debian-installer/commit/28b863340cc5fd73fbaac85a3fb89e72e842b15c

… so I'm just checking what you are requesting to be done here.

§

> All gtk files have fontconfig-related cache/uuid changes…
[…]
> FWIW, dropping all fontconfig-related bits (see attached patch)

This is #864082 in src:fontconfig — I've been playing whack-a-mole
with fontconfig over the past 18 months or so and this was a
fairly recent regression.

Are you planning on applying this patch to debian-installer.git?
Naturally, I would prefer if #864082 was applied and in buster, or
otherwise closed again.

§

> The mini.iso has apparently other changes… I'm attaching the diffoscope
> output. Could this be because of missing tweaks to the xorriso calls in
> build/config/x86.cfg?

Possibly. Let me try and reproduce and reload all of that into my
brain and get back to you on this; IIRC there was some pushback
against making it change behaviour only on SOURFE_DATE_EPOCH being
present so — as you imply — a command-line change might be required.

§

> (Including lintian runtime, using pigz on a 8-way machine cuts real time
> from 8m8s to 4m23s.)

TIL pigz; thanks.

> Checking what happens [it] seems successive builds with pigz lead to the
> same results. But those aren't the same as the results generated with
> gzip. I don't suppose this is going to be a particularly huge problem
> though?

Alas, it is a problem in thatfrom the outside nobody will know
whether one built with pigz or gzip and thus it will be unclear how
to reproduce the bit-for-bit identical binary. In other words, there
is currently no ".buildinfo" equivalent here that specifies "I used
Arch^Wpigz, btw" and got a SHA of $foo.

One easy solution would be if that, if SOURCE_DATE_EPOCH is present,
then we force the use of one tool. Although that would regrettably
mean the lowest common denominator (ie. gzip)  which probably isn't
the ideal due to the aforementioned performance gain for using pigz.
Alternatively, we could make pigz a strict build requirement but
that sounds a little antisocial.

Perhaps we need to record the environment after all; again, I will
reload all of this into my head anyway due to mini.iso (^) so this
will be top-of-stack again.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Re: Bug#900918: debian-installer: Please make the generated images reproducible

[Chris Lamb]

[Keeping Kibi in CC as requested off-list, dropping mtools@p.d.o]

Dear Kibi,

First, thank you so much for your review. I believe I have resolve
all of your issues on the corresponding merge request, as well as
rebasing it against the current master:

  https://salsa.debian.org/installer-team/debian-installer/merge_requests/3
  
§

>  * 0c19a29645a6a3136f3a51da5d5cf1cfcec5fdfb mentions file system
>ordering only, but that's just the sort part

I've split this commit and it is much clearer now.

>  * 71391967763708055a65ed68999db8f4ea6fc6e6 sets “deb1” as the FAT
>volume ID; have you checked with people like debian-cd@ whether
>another constant might make more sense?

Clarified where this comes from in the commmit and in the code
itself.

>  * 7c533fa721c3ae89ca81d1336b5928a80ed0d531 thanks for the clarity
>[ also: “becuase” in commit message. ]

Fixed.

>  * c35b8688696b1b4563a45d0feeabc3a0c0f2eccb “determinstic”

Fixed.

>  * ea1a896181daa3b82c5a62ae31839b457a0dbe0b modifies BUILD_DATE, adding
>a few characters (“:SS”); that ends up in various help screens

In my tests, this did not break any visual text wrapping, etc.

>  * f181b4fe90b9030f515c7e6129239b96131b3926 oh more en_GB, yay.

Fixed (use 'results' instead).

§

Thank you again for your review. Let me know if you would require
any further modifications before merging. :-)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
     `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Re: Do the file timestamps in ISOs matter ?

[Chris Lamb]

> > I believe [--set_all_file_dates] is entirely unnecessary
> 
> if SOURCE_DATE_EPOCH sets the default, there must be some option to set
> non-default values, especially the value which is default without
> SOURCE_DATE_EPOCH.

Consider the state space:

If someone does not set SOURCE_DATE_EPOCH, they are going to get an
unreproducible regardless. Therefore, whichever set_all_file_dates option
they choose is entirely meaningless and thus xorriso can simply inherit
{a,c,m}time just as before.

If someone does set SOURCE_DATE_EPOCH, they want a reproducible image by
definition. Thus, inheriting {a,c}time from the filesystem makes no sense
as their image will then not be reproducible and setting {a,c,m}time to a
specific date is not necessary as that can be trivially done pre-build.

Therefore folding it all into inheriting {a,c}time from mtime iff S_D_E
is the logical conclusion, from the angles of complicating xorriso itself
and complicating the end-user UI for someone who wants a reproducible ISO.

Putting it another way, the "semi-reproducible" scenario seems so unlikely
we can entirely discount it and thus there is need to for people who "just"
want a reproducible ISO to tediously scour the documentation to discover they
need to set --set_all_file_dates.

> I decided to let SOURCE_DATE_EPOCH only set the defaults of existing
> and new options, in order to protect ISO producers like grub-mkrescue from
> negative effects by overriding their program options.

They won't be run with SOURCE_DATE_EPOCH exported.

> Not to forget that it offers those users a workaround, who do not agree
> with the final decision about the question posed here, but want to use
> SOURCE_DATE_EPOCH nevertheless.

I just don't see this usecase of being "partly" reproducible being remotely
useful to anyone, ever. I'm probably misunderstanding something, however.


Regards,

-- 
  ,''`.
     : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Re: Do the file timestamps in ISOs matter ?

[Chris Lamb]

Hi Thomas,

> Still undecided is whether [SOURCE_DATE_EPOCH] shall by default override
> all timestamps inside the ISO

I believe this steps outside the scope of what exporting SOURCE_DATE_EPOCH
should do, both philosophically, æsthetically, and practically as it
prevents ISO producers from having differing mtimes in files.

It's easy enough to clamp (or simply override) the mtimes prior to calling
xorriso anyway…


> [SOURCE_DATE_EPOCH] shall only copy each file's mtime to the same file's
> ctime and atime (to ease reproduction of input file trees).

+1 for this.


> xorriso will support all three models by allowing to override 
> SOURCE_DATE_EPOCH
> by one of three parameters to a new program option:
>   --set_all_file_dates  default
>   --set_all_file_dates  set_to_mtime
>   --set_all_file_dates  ="$SOURCE_DATE_EPOCH"

Given that there is no believable use-case where one would be exporting
SOURCE_DATE_EPOCH but somehow desire the atime and ctime to vary but have a
fixed mtime, I believe this option is entirely unnecessary. No need to
complicate things.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Re: Call For Participation Debian Cloud Sprint

[Chris Fordham]

Have added myself as remote. Look forward to disrupting!

On Fri, Aug 12, 2016 at 7:13 AM, Zach Marano  wrote:

> We are organizing a Debian cloud sprint to focus on subjects like:
> - What does it mean to run Debian in the cloud.
> - Define the official Debian cloud image.
> - In depth look at how Debian works on current cloud platforms (AWS,
> Azure, GCE, etc).
> ... etc (complete agenda TBD)
>
> Ideally, we solve all (or as many as possible) of the open questions which
> were discussed at Debconf and on the debian-cloud list and come to
> consensus on what an official Debian cloud image is, how it works in the
> various cloud offerings, and have a realistic timeline to offer such an
> image for the community at large. Bonus points if we actually have
> something working.
>
> I am targeting November 2 - 4, 2016 in Seattle, WA (USA).
> https://wiki.debian.org/Sprints/2016/DebianCloudNov2016
>
> Please respond if you are interested in attending so we can find a
> suitable space (or if you happen to have such a space). Thanks!
>
> -
> Zach Marano
> zmar...@google.com
>

Re: Building cloud images on Debian infrastructure

[Chris Fordham]

On Fri, Apr 8, 2016 at 4:56 AM, Bastian Blank <wa...@debian.org> wrote:

> On Thu, Apr 07, 2016 at 06:35:52PM +1000, Chris Fordham wrote:
> > It does not however need to be based on a tar if that is what is being
> > debated (or the master is a tar). Its a completely normal practice to
> build
> > an image in mounted loopback with a .img (raw) and then convert that to
> > desired formats, packages and the root fs into a flat file tar.
>
> I see no reason to have two code-paths doing the same thing.  So using
> the tar as input always reduces the overall complexity of the software.
>
> > For 'transformations' where you modify files or run commands in chroot of
> > the filesystem that is within the artifact, its actually more dancing to
> > extract a tarball than it is to simply mount an image in loopback.
>
> The is a lot more than "simply mount an image", as this image contains
> partitions, not neccesarily at the same location.  So no, this is not
> easy.
>
I'll be honest, I don't believe that either are hard also.


>
> Bastian
>
> --
> I'm a soldier, not a diplomat.  I can only tell the truth.
> -- Kirk, "Errand of Mercy", stardate 3198.9
>
>

Re: Building cloud images on Debian infrastructure

[Chris Fordham]

On Thu, Apr 7, 2016 at 5:59 PM, Bastian Blank  wrote:

> On Fri, Apr 01, 2016 at 12:13:59AM +0200, Thomas Goirand wrote:
> > I don't get your thing about tar. Can you explain why we should use tar?
>
> This makes it possible to build small variations without doing the whole
> dance again.  Plus it makes it possible to review if the output is
> reasonable.
>
I agree that a tar should be provided as one of the outputs yes. This is
one of the formats that Ubuntu Cloud does too ala 'rootfs' (and insert X
usb linux distro here).
It does not however need to be based on a tar if that is what is being
debated (or the master is a tar). Its a completely normal practice to build
an image in mounted loopback with a .img (raw) and then convert that to
desired formats, packages and the root fs into a flat file tar.

For 'transformations' where you modify files or run commands in chroot of
the filesystem that is within the artifact, its actually more dancing to
extract a tarball than it is to simply mount an image in loopback.


>
> Bastian
>
> --
> Deflector shields just came on, Captain.
>
>

Bug#497471: sarge images have syslinux binaries without source

[Chris Knadle]

For what it's worth, syslinux-2.04 source is available here:

   https://www.kernel.org/pub/linux/utils/boot/syslinux/2.xx/

This is a list files shown for version 2.04:

   syslinux-2.04.lsm   20-Oct-2011 19:13  3.0K
   syslinux-2.04.lsm.sign  20-Oct-2011 19:13  836
   syslinux-2.04.tar.bz2   20-Oct-2011 19:08  309K
   syslinux-2.04.tar.gz20-Oct-2011 19:08  379K
   syslinux-2.04.tar.sign  20-Oct-2011 19:08  836
   syslinux-2.04.tar.xz20-Oct-2011 19:08  257K
   syslinux-2.04.zip   20-Oct-2011 19:13  462K
   syslinux-2.04.zip.sign  20-Oct-2011 19:13  836

Hopefully there's a way of verifying that this is the correct source for
what was shipped with the Sarge images.

GPL license compliance requires that users be able to get the source for the
binary upon request -- so I believe what's required to handle this bug is
verification and documentation.  I'd like to think that can be done with
some kind of errata file placed /next to/ the Sarge images in the archive
rather than having to rebuild the Sarge images themselves.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us

Bug#747384: Acknowledgement (cdimage.debian.org: Powerpc testing image contains mismatched kernel and modules)

[Chris Tillman]

This inconsistency appears to be fixed now:

...

zlib-modules-3.14-1-powerpc-di_3.14.4-1_powerpc.udeb
linux-image-3.14-1-powerpc_3.14.4-1_powerpc.deb
linux-image-3.14-1-powerpc-smp_3.14.4-1_powerpc.deb
linux-image-3.14-1-powerpc64_3.14.4-1_powerpc.deb

At my next opportunity I'll retest.


On Thu, May 8, 2014 at 12:30 AM, Debian Bug Tracking System 
ow...@bugs.debian.org wrote:

 Thank you for filing a new Bug report with Debian.

 This is an automatically generated reply to let you know your message
 has been received.

 Your message is being forwarded to the package maintainers and other
 interested parties for their attention; they will reply in due course.

 As you requested using X-Debbugs-CC, your message was also forwarded to
   toff.till...@gmail.com
 (after having been given a Bug report number, if it did not have one).

 Your message has been sent to the package maintainer(s):
  Debian CD-ROM Team debian-cd@lists.debian.org

 If you wish to submit further information on this problem, please
 send it to 747...@bugs.debian.org.

 Please do not send mail to ow...@bugs.debian.org unless you wish
 to report a problem with the Bug-tracking system.

 --
 747384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747384
 Debian Bug Tracking System
 Contact ow...@bugs.debian.org with problems




-- 
Chris Tillman
Developer

Bug#747384: cdimage.debian.org: Powerpc testing image contains mismatched kernel and modules

[Chris Tillman]

Package: cdimage.debian.org
Severity: important
Tags: d-i

Dear Maintainer,

   * What led up to the situation?

I tried to use the jessie installer downloaded from
http://ftp.nz.debian.org/debian/dists/jessie/main/installer-
powerpc/current/images/powerpc/hd-media/

with the iso downloaded from
http://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-cd/debian-testing-
powerpc-netinst.iso
dated 2014-05-05

In the installer, I was warned that no modules were available. I checked uname
-a, and the installer had linux-image-powerpc-3.13-1 (3.13.5-1).

The iso got loaded OK from the hard disk. I then checked the iso contents and
verified there were no modules available for that kernel. It looked like some
were available for other kernels like image-powerpc-smp and image-powerpc64.

After quitting the installation (no installation was possible) I checked in

http://cdimage.debian.org/cdimage/weekly-builds/powerpc/list-cd/debian-testing-
powerpc-netinst.list.gz

It looked like the modules are version 3.14, while the kernels are version
3.13:


affs-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
affs-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
ata-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
ata-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
btrfs-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
btrfs-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
core-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
core-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
crc-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
crc-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
crypto-dm-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
crypto-dm-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
crypto-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
crypto-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
event-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
event-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
ext4-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
ext4-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
fancontrol-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
fat-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
fat-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
fuse-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
fuse-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
hfs-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
hfs-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
hypervisor-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
isofs-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
isofs-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
jfs-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
jfs-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
loop-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
loop-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
md-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
md-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
multipath-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
multipath-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
nbd-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
nbd-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
nic-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
nic-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
nic-pcmcia-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
nic-pcmcia-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
nic-shared-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
nic-shared-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
pata-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
pata-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
pcmcia-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
pcmcia-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
pcmcia-storage-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
pcmcia-storage-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
ppp-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
ppp-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
sata-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
sata-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
scsi-extra-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
scsi-extra-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
serial-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
serial-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
squashfs-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
squashfs-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
udf-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
udf-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
uinput-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
uinput-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
usb-serial-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
usb-serial-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
virtio-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
virtio-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb
xfs-modules-3.14-1-powerpc-di_3.14.2-1_powerpc.udeb
xfs-modules-3.14-1-powerpc64-di_3.14.2-1_powerpc.udeb

Bug#744959: installer amd64 cdimage fails to boot on Macbook 2,1

[Chris Bainbridge]

Package: cdimage.debian.org
Version: all

Originally reported on https://bugs.launchpad.net/ubuntu-cdimage/+bug/1298894

  Does the Debian ISO boot? 
  http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso

 No, this Debian ISO does not boot either.
...
 My Macbook 2,1 is from the late 2006 series; 
 http://support.apple.com/kb/ht1635

 From the comments on http://mjg59.dreamwidth.org/11285.html :
 You're booting via the BIOS compatibility layer, which is broken on images 
 with multiple
 El-Toritos on Macs. The problem is that the Macbook 2,1 has 32-bit firmware 
 even though it
 has a 64-bit CPU, and right now we don't support that.

 The ISO that works is
 http://cdimage.ubuntu.com/daily-live/current/trusty-desktop-amd64+mac.iso
 which is fine; I just wanted to flag up that the normal ISO does not work


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAP-bSRby+PG7=-e+m2pgvvf7thqjkmrw_ol0xqbp1afsmik...@mail.gmail.com

Bug#740504: cdimage.debian.org: Released ISO images have invalid GPT tables

[Chris Bainbridge]

On 8 April 2014 18:14, Steve McIntyre st...@einval.com wrote:
 Other folks: could you please test the output of the next daily builds
 and verify these work better for you?

I still can't create a partition, which was the original aim. Is it
supposed to work? If it is not possible to produce an image that can
have a partition added, that should be mentioned in the Debian Manual
(at the moment the manual suggests that the user create an extra
partition on the image in order to add any required firmware files).

# /dev/sdb is a USB drive I wrote the image to with dd

# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Error: The backup GPT table is not at the end of the disk, as it
should be.  This might mean that
another operating system believes the disk is smaller.  Fix, by moving
the backup to the end (and
removing the old backup)?
Fix/Ignore/Cancel? Ignore
Warning: Not all of the space available to /dev/sdb appears to be
used, you can fix the GPT to use
all of the space (an extra 14905344 blocks) or continue with the
current setting?
Fix/Ignore? Ignore
Error: Unable to satisfy all constraints on the partition.
(parted)

# parted debian-testing-amd64-netinst.iso
GNU Parted 2.3
Using /home/chrb/Downloads/debian-testing-amd64-netinst.iso
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Error: Unable to satisfy all constraints on the partition.
(parted)

# parted /dev/sdb
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Error: The backup GPT table is not at the end of the disk, as it
should be.  This might mean that
another operating system believes the disk is smaller.  Fix, by moving
the backup to the end (and
removing the old backup)?
Fix/Ignore/Cancel? Fix
Warning: Not all of the space available to /dev/sdb appears to be
used, you can fix the GPT to use
all of the space (an extra 14905344 blocks) or continue with the
current setting?
Fix/Ignore? Fix
Error: Unable to satisfy all constraints on the partition.
(parted) p
Error: The backup GPT table is corrupt, but the primary appears OK, so
that will be used.
OK/Cancel? OK
Warning: Not all of the space available to /dev/sdb appears to be
used, you can fix the GPT to use
all of the space (an extra 14905344 blocks) or continue with the
current setting?
Fix/Ignore? Fix
Error: Unable to satisfy all constraints on the partition.
(parted)

# gparted debian-testing-amd64-netinst.iso
[create partition table in gui]
No partition table found on device debian-testing-amd64-netinst.iso
A partition table is required before partitions can be added.
To create a new partition table choose the menu item:
Device -- Create Partition Table.


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cap-bsrygwn+hfiwx3heg8bet6r0dm+5n8kua2ydfaybqqdk...@mail.gmail.com

Bug#740504:

[Chris Bainbridge]

 I am also a bit curious to know how the information regarding which
 versions of software were used to create the .ISO . It seems this
 info. is embedded in the .iso generated but there doesn't seem to be
 any answers.


Mount the iso image, the file /.disk/mkisofs has the exact xorriso
command line used to generate the image.


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAP-bSRaD--Hou37=aVvWLYDOfk-LSKpDFiwC3+2+RWsGH=2...@mail.gmail.com

Bug#740504:

[Chris Bainbridge]

 Mount the iso image, the file /.disk/mkisofs has the exact xorriso
 command line used to generate the image.


Apologies for the dupe info, I now see that Thomas already posted this detail.

btw the Ubuntu images have the same issue - Launchpad bug
https://bugs.launchpad.net/debian/+bug/1298912


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cap-bsrb7hzda-r3mf2pckahmft5zhoumq4z6xbketkgmh_t...@mail.gmail.com

Bug#727204:

[Chris Bainbridge]

This looks like a dupe of #663504 Wheezy netinstaller does not search
inserted media for additional files


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAP-bSRZky-9w7=lqfmkflx8z6arud2lipbqz8q3zd0tf4_w...@mail.gmail.com

Bug#740504: cdimage.debian.org: Released ISO images have invalid GPT tables

[Chris Bainbridge]

Package: cdimage.debian.org
Severity: important

Dear Maintainer,

The GPT checksum of debian-7.4.0-amd64-netinst.iso (and other
wheezy and testing images) is incorrect due to a bug in the Xorriso build
tool used on the build system (confirmed by author of build tool). Reported on
mailing list but no response received: 
https://www.mail-archive.com/debian-cd@lists.debian.org/msg21403.html

I am not sure what the impact of this is (hypothetically, some EFI
systems could refuse to boot the ISO). It does mean that it is not
possible to add extra partitions to the image (which the documentation
states can be done for firmware files).

Thomas Schmitt (author of xorriso) confirmed that: The problem
described there affects versions 1.2.6 and 1.2.8.
debian-7.3.0-amd64-netinst.iso indeed bears as preparer id
XORRISO-1.2.6 2013.01.08.103001, LIBISOBURN-1.2.6, LIBISOFS-1.2.6,
LIBBURN-1.2.6

It _should_ be fixed in xorriso-1.3.2 as in Debian testing
and in the current upstream release 1.3.4.


-- 
To UNSUBSCRIBE, email to debian-cd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140302124124.GF10964@localhost

Invalid gpt on wheezy images

[Chris Bainbridge]

It seems the currently distributed iso images may contain invalid GPT
tables. I downloaded debian-7.3.0-amd64-netinst.iso, wrote it to a USB
stick and tried to add a partition for firmware files as described at
https://www.debian.org/releases/stable/amd64/ch04s03.html.en - but
gdisk reported Found invalid GPT and valid MBR.

This appears to be due to a bug in xorriso as discussed at
https://lists.debian.org/debian-cd/2013/05/msg00035.html

Thomas Schmitt confirmed that: The problem described there affects
versions 1.2.6 and 1.2.8.
debian-7.3.0-amd64-netinst.iso indeed bears as preparer id
XORRISO-1.2.6 2013.01.08.103001, LIBISOBURN-1.2.6, LIBISOFS-1.2.6,
LIBBURN-1.2.6

You will have to ask at debian-cd@lists.debian.org whether
the problem is supposed to be fixed in the xorriso binary
that produces the images.

It _should_ be fixed in xorriso-1.3.2 as in Debian testing
and in the current upstream release 1.3.4.


-- 
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/cap-bsrzrdea8l8qfzxxzlxhetfazdmgd+wqbxyyagkaionp...@mail.gmail.com

3 DVDs on download website but 11 DVDs listed in the MD5SUM file?

[Chris Steffen]

debian-cd@lists.debian.org

Dear Debian:

There are 3 DVDs on the download website but 11 DVDs listed in the 
MD5SUM file?


http://www.debian.org/CD/http-ftp/#stable
Select Link AMD64
http://cdimage.debian.org/debian-cd/7.2.0/amd64/iso-dvd/

Where is the rest of the distribution?

Thanks,
Chris Steffen
cestef...@arvig.net
303-588-8056






--
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/529a30fc.c8e.46d3e700.b4db...@arvig.net

debian-squeeze-live-rc2-amd64-xfce-desktop.iso

[Chris Bell]

Hello,
   I have downloaded the iso image three times from
ftp://cdimage.debian.org/cdimage/squeeze_live_rc2/iso-hybrid/debian-squeeze-live-rc2-amd64-xfce.iso
and attempted to burn it four times, but each time K3b halts just before the
end of write and eventually gives an error. I have tried most of the other
images for amd64 and i386 and they appear OK.


-- 
Chris Bell www.chrisbell.org.uk (was www.overview.demon.co.uk)
Microsoft sells you Windows ... Linux gives you the whole house.


-- 
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/marcel-1.53-0205124151-965h...@riscpc.main

Re: PowerPC daily install CDs? [Was: Re: Netinst for testing?]

[Chris Bigguy]

I have been directing folks to
http://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-cd/
and as of now Sunday 25 October 9:15 Eastern Time I'm seeing a full set of 
discs dated 19 October, last Monday.  All seems right with the world at that 
url.

All my best - Chris Reich; Rochester, New York
twittername: chrisreich

--- On Sat, 10/24/09, Rick Thomas rbthoma...@pobox.com wrote:

 From: Rick Thomas rbthoma...@pobox.com
 Subject: PowerPC daily install CDs?  [Was: Re: Netinst for testing?]
 To: CD List Debian debian-cd@lists.debian.org
 Cc: PowerPC List Debian debian-powe...@lists.debian.org
 Date: Saturday, October 24, 2009, 11:25 PM
 
 On Oct 24, 2009, at 10:03 PM, Frans Pop wrote:
 
  On Saturday 24 October 2009, Dennis Wicks wrote:
  I thought that I had previously gotten net install
 CD iso
  for what was then the testing release of Debian.
  
  Links to current images are available from:
  http://www.debian.org/devel/debian-installer/
  
  Cheers,
  FJP
 
 
 Hmmm... If I follow that link, then click on
     • netinst ... and businesscard ... CD
 images ... [powerpc]
 I get taken to a directory that claims This build finished
 at Thu Oct 1 23:28:01 UTC 2009.
 
 Is it possible that PowerPC CD builds have been down for
 over three weeks and nobody noticed?
 
 !?!?!?!
 
 Rick
 
 --
 To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 



--
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

[Chris Bannister]

On Sun, Mar 15, 2009 at 10:57:08AM +0100, Richard Atterer wrote:
 So unfortunately the standard Debian installer is not the right choice for 
 you. Try a distribution specialized for low-spec machines, e.g. 
 http://damnsmalllinux.org/! Once installed, you may be able to convert it 
 into a normal Debian installation.

You can, but it is quite a lot of work[1] to get to a *pure* Debian system.
It is not called damnsmalllinux for nothing. :)

It was a while ago when I did it. (It was based on Sarge.)

-rw-rw-r-- 1 root root 16479 2006-02-28 10:03 
/usr/share/doc/dsl/getting_started.html

Mmmm ... still got gremlins.
chr...@box:~$ ls -al /opt/
total 32
drwxrwsr-x  6 root staff 4096 2007-12-22 02:49 .
drwxr-xr-x 22 root root  4096 2008-09-29 02:23 ..
-rw-rw-r--  1 root staff0 2004-08-10 16:54 .backup_device
drwxrwxrwx  2 root root  4096 2004-11-17 18:39 .firefox_plugins
drwxr-xr-x  2 root root  4096 2004-11-13 06:32 apsfilter
lrwxrwxrwx  1 root staff   12 2007-09-21 18:16 monkey - monkey-0.9.1
drwxr-xr-x  7 root root  4096 2005-05-18 07:14 monkey-0.9.1
-rwxrwxr-x  1 root root   213 2005-07-01 09:53 powerdown.sh
-rw-r--r--  1 root root 0 2003-12-14 01:24 printcap
drwxr-xr-x  2 root root  4096 2004-11-13 06:32 samba
-rw-r--r--  1 root staff   17 2008-10-24 18:24 timezone

[1] For one thing, they have a lot of customised config files and just 
blindly replacing them is not recommended.

-- 
Chris.
==
I contend that we are both atheists. I just believe in one fewer god
than you do. When you understand why you dismiss all the other
possible gods, you will understand why I dismiss yours.
   -- Stephen F Roberts


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

Bug#466991: Package: installation-reports

[Chris Dent]

Hi Frans,

Many thanks for your message.  I do not doubt that DVD-1 *should* fit on any
DVD but here it just doesn't - its probably just this (old) Sony DVD-RW -
and I can't argue with your first reaction.  I have now downloaded CD-1 and
I'll see how I get on with that over the weekend.

With very best wishes,
Chris

 -Original Message-
 From: Frans Pop [mailto:[EMAIL PROTECTED] 
 Sent: 22 February 2008 12:23
 To: [EMAIL PROTECTED]
 Cc: Chris Dent; debian-cd@lists.debian.org
 Subject: Re: Bug#466991: Package: installation-reports
 
 reassign 466991 debian-cd
 thanks
 
 On Friday 22 February 2008, Chris Dent wrote:
  Comments/Problems:
  The problem is that with Sony Sonic CD burner a 4.7Gb disk can only 
  hold 4.1Gb of data, too little to contain DVD-1 (4.4Gb).  
 Maybe reduce 
  the contents a little to allow for similar fault tolerance? 
  Shall try 
  the CD version now...
 
 I'm not sure if we've had reports of similar issues before. I 
 cannot remember any.
 
 The problem probably is that DVD is a fairly well defined 
 standard, so if your hardware does not follow that standard, 
 my first reaction would be to
 say: sorry but we cannot allow for hardware that is not 
 standards compliant.
 Especially as that would mean we will be using 4 DVDs a lot 
 sooner than we have to (you're basically asking us to reduce 
 the size by half a CD...). 
 
 However, if you can show that the 4.1GB limit _is_ part of 
 some standard (and I don't mean the documentation of your DVD 
 writer), maybe the debian-cd team will consider lowering the size.
 
 Cheers,
 FJP
 




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

Re: DVD image download issue Opera, Konqueror, and Firefox/iceweasel

[Chris Howie]

On Jan 8, 2008 1:10 PM, joseph lockhart [EMAIL PROTECTED] wrote:

  Maybe you could use bittorrent?

 that would be possible, but many isp now make it hard
 to download large torrent files (in a supposed attempt
 to stop movie piracy) so torrent is out, and i admit i
 did not check all the mirrors, though stopping at the
 same spot is certianly odd


Jigdo?

-- 
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers

RE: Mail Delivery System [Qurb #358686]

[Klaus, Chris (ISSAtlanta)]

This is an automated message.

I apologize for the inconvenience, but I need your help in fighting
spam. Messages from approved senders go directly to my Inbox. 
Messages from addresses that have not put into my whitelist 
are quarantined until the address of the sender can be
confirmed.

TO CONFIRM YOUR ADDRESS PLEASE REPLY TO THIS MESSAGE WITHOUT
MODIFYING THE SUBJECT.

There is no need to include any additional information in your
reply. I will be notified of your original message immediately and
you should not receive a confirmation message like this from me in
the future.

Thanks!

Re: revising the first cd contents...

[Chris Cheney]

On Wed, Jun 23, 2004 at 09:57:54PM -0400, Joey Hess wrote:
 I don't know if kde-core and gnome-core are sufficient to get a working
 kde and gnome environment. I doubt it, especially for KDE, but if they
 are I can make tasksel install them, and pull in the full kde and gnome
 only if it's available. KDE and GNOME people, please let us know.

kde-core is enough to get KDE running, it includes arts/kdelibs/kdebase,
but it doesn't include any of the other official KDE packages. It does
include basic apps like kate, konqueror and konsole. The kde package
installs the full official KDE release, but doesn't include 3rd party
apps they are included in the kde-extras package instead.

Chris


signature.asc
Description: Digital signature

Re: [Fwd: Stable DVD and jigdo error]

[Chris]

On Tue, Apr 20, 2004 at 10:34:28AM +0200, Richard Atterer wrote:


 On Tue, Apr 20, 2004 at 06:55:28AM +0200, Jan Kesten wrote:
  I obtained the two files:
  
  debian-stable-i386-binary-1-nonfree.jigdo
  debian-stable-i386-binary-1-nonfree.template
 
 These files are 11 days old, and the person who created them did not set up
 a so-called fallback mirror for the files which were removed from the
 Debian archive (or whose content changed) during those last 11 days.
 
  I have used a number of mirrors to obaining the files, using the ones in
  the [Server} section of the jigdo file, as well as ftp.au.debian.org for
  both the normal and non-US data.
 
 You could try getting these files by using the Debian snapshot mirror:
 
 http://snapshot.debian.net/archive/2004/04/09
 
  The following files are always attempted to be grabbed each time i run
  jigdo-lite
  
   
  ftp.de.debian.org/debian/dists/woody/main/disks-i386/3.0.23-2002-05-21/doc/cs/install.cs.txt'
  
   8 files all from with the name  ...doc/*/install.*.txt
  
  Could someone help me here so that I can obtain a working DVD image?
 
 Ah - looks like those missing files are just documentation! If you don't 
 mind these files' data being all-zero on your DVD, you can just write the 
 iso.tmp file to it.
 
 Cheers,
 
   Richard
 
 -- 
   __   _
   |_) /|  Richard Atterer |  GnuPG key:
   | \/¯|  http://atterer.net  |  0x888354F7
   ¯ '` ¯


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

jigdo??

[Chris Chaffee]

Ok, so I just spent the last30 minutes trying 
to figure out how to get thecurrent set of Debian CD images, all to find 
out that the ONE and ONLY site (the one referenced onthe Debian 
website)that hosts the "jigdo" client app is down... I 
evenwent through a few search engines, trying to see if I couldfind 
the client elsewhere,but nosuchluck. In the time I 
wasted trying to figure this stuff out, I could have been agreatdeal 
closer to having downloaded the images, and on to bigger and better 
things... Instead Iam unable to get the Debian images at all because 
I can't get some off-the-wall download client that is only (un)available 
fromsome dude'spersonal website.

When you guys get things all sorted out over there, 
I'd love to hear of a way I can actuallyget my hands on the current Debian 
images. Until then, I think I'll give Mandrake a try.

Regards,
Chris

jigdo??

[Chris Chaffee]

Ok, so I just spent the last30 minutes trying 
to figure out how to get thecurrent set of Debian CD images, all to find 
out that the ONE and ONLY site (the one referenced onthe Debian 
website)that hosts the "jigdo" client app is down... I 
evenwent through a few search engines, trying to see if I couldfind 
the client elsewhere,but nosuchluck. In the time I 
wasted trying to figure this stuff out, I could have been agreatdeal 
closer to having downloaded the images, and on to bigger and better 
things... Instead Iam unable to get the Debian images at all because 
I can't get some off-the-wall download client that is only (un)available 
fromsome dude'spersonal website.

When you guys get things all sorted out over there, 
I'd love to hear of a way I can actuallyget my hands on the current Debian 
images. Until then, I think I'll give Mandrake a try.

Regards,
Chris

Re: Patch to make it possible to toggle contrib on CDs

[Chris Halls]

On Fri, Dec 06, 2002 at 06:33:09PM +0100, Tollef Fog Heen wrote:
 | Why is it in contrib then ? Things like that only complicates life. :-(
 
 Build-deps on non-free software, perhaps?

Yes that's right - we need the Blackdown JDK to build, or someone with the
time to make it work with other JDKs.  That job is on the TODO list but that
list is very long and stuff like fixing bugs and splitting the source
package is higher priority for the (small) team.

Chris



msg04972/pgp0.pgp
Description: PGP signature

Re: Patch to make it possible to toggle contrib on CDs

[Chris Halls]

On Fri, Dec 06, 2002 at 06:33:09PM +0100, Tollef Fog Heen wrote:
 | Why is it in contrib then ? Things like that only complicates life. :-(
 
 Build-deps on non-free software, perhaps?

Yes that's right - we need the Blackdown JDK to build, or someone with the
time to make it work with other JDKs.  That job is on the TODO list but that
list is very long and stuff like fixing bugs and splitting the source
package is higher priority for the (small) team.

Chris


pgp7FaiHorn7N.pgp
Description: PGP signature

Re: Jigdo needs concept work

[Chris Severance]

At 10:56 AM 12/2/2002 -0800, Gordon Huff wrote:

I for one am looking forward to your efforts in this field.
I have tried to understand how to write for Windows Sockets but it was way 
too complicated for me. None of the available calls did anything resembling 
something useful. Then I tried some pre built libraries which were easy 
enough to use but were too buggy and slow.

Bad things that Jigdo does:
Downloads as files... like unix file names can be represented
Do you have an alternative to downloading as files? Why would downloading 
anything else be any different?
All I'm saying is that downloading 10,000 files one FTP at a time will 
substantially increase your transfer volume over the same ISO's. The 
traffic to open and close connections for so many 1K files is not trivial. 
I do have bandwidth but I don't have time to figure out how to get Jigdo to 
recognize my 3 Debian 2.2r4 CD's nor do I have time to ask Jigdo to 
download 7 CD's one CD at a time.

separate FTP session for each file and you guys think you're saving 
something. Sounds to me like an ISO will generate half as much traffic! 
If you were really clever you'd ZIP the releases to guarantee delivery.
If a separate FTP session for each file really bothers you, HTTP may be 
your protocol of choice.
The author already answered: Some day it might be a streaming protocol so 
that the losses from separate sessions would be minimized.

Don't gripe! Write your download tool!
I gripe because y'all call me evil for heading to the security of ISO 
downloads. Y'all think I could download less if I were to follow a hundred 
steps. I tried the Jigdo game and it was so hard to play that I just went 
into the Jigdo file, found the name, did a Google search, and picked a 
relatively close mirror. One day later, they were all done. 2 hours of 
fooling with Jigdo were repaired with 20 minutes of google and FTP.

The Jigdo process may have been adapted to other OS but it is clearly 
designed for *nix systems. In the future the jigdo
And after you use the Jigdo system once, you should be on *nix! Not a 
problem!(tm)

Looking forward to your efforts in Debian,
My speciality isn't in Unix. I don't like the file system. I maintain a 
casual interest in Debian and Linux in general because it is the ultimate 
server system. Linux, or at least Debian as of 2.24r was not suitable as a 
workstation for many reasons, one being that it was Internet leaky and 
constantly causing dials. I had to block the Debian computer at the router 
to keep things working normally.

Jigdo needs concept work

[Chris Severance]

A proper implementation of Jigdo:

1. It is a GUI program, not a CLI program.

2. Jigdo only asks for a single link. The information at this link 
maintained by the head of the system, in this case some link advertised at 
debian download page.
Provide this _link_ when jigdo asks for your online distribution link
  A. A list of everything available for on the distribution network. The 
debian network would include all present and past releases of everything 
that debian wants to be available. This includes the current release, the 
latest patch level, and any previous popular releases. The list would also 
be tree structured so if I wanted all 8 CD's of Woody then I could check a 
single box and they would all be marked. If there were optional items, 
these would be in the same group but may not be checked via the group check.

Downloading to C:\TEMP;d:\|PackageSummary
[x] Debian Woody 3.0 Release i386 (8 cd's, 4900MB)
  [=]Debian Woody 3.0 Release i386 CD 1 ISO
  [=]Debian Woody 3.0 Release i386 CD 1 (Non US) ISO
  [=]Debian Woody 3.0 Release i386 CD 2 ISO
  [=]Debian Woody 3.0 Release i386 CD 3 ISO (let's say I already got the 
first 3)
  [~]Debian Woody 3.0 Release i386 CD 4 ISO (and part of 4)
  [x]Debian Woody 3.0 Release i386 CD 5 ISO
  [x]Debian Woody 3.0 Release i386 CD 6 ISO
  [x]Debian Woody 3.0 Release i386 CD 7 ISO
  --Unix File Groups allow you to not download files available from 
earlier downloads
  and releases.
  ( )Generate OS independent ISO files
  (-)Generate hard disk folders (not available on your OS)
  [ ]Debian Woody 3.0 Release i386 CD 1 Unix File Group
  [ ]Debian Woody 3.0 Release i386 CD 1 (Non US) Unix File Group
  [ ]Debian Woody 3.0 Release i386 CD 2 Unix File Group
  [ ]Debian Woody 3.0 Release i386 CD 3 Unix File Group
  [ ]Debian Woody 3.0 Release i386 CD 4 Unix File Group
  [ ]Debian Woody 3.0 Release i386 CD 5 Unix File Group
  [ ]Debian Woody 3.0 Release i386 CD 6 Unix File Group
  [ ]Debian Woody 3.0 Release i386 CD 7 Unix File Group
  -- Optional Components not by debian.org--
  [ ]Debian Power Tools updated for Debian Woody 3.0
  [ ]Star Office updated for Debian Woody 3.0
[ ]Debian Woody 3.0 Stable Beta Release 3.01r1000 (updated 10/06/2002)
  ..
  ..
[ ]Debian Woody 3.0 Current Beta Release 3.02r1252 (updated 11/29/2002)
  ..
  ..

  B. A list of every place where that stuff might be obtained

3. The program then presents me a list of what I have, what I want, and 
optionally, presents me a list to limit places to obtain it from.

4. Hit run, and it gets all checked items.



Bad things that Jigdo does:

Downloads as files... like unix file names can be represented on other file 
systems! This sounds like a trick to ensure that I *don't* get a usable 
release unless I'm a *nix buf. A separate FTP session for each file and you 
guys think you're saving something. Sounds to me like an ISO will generate 
half as much traffic! If you were really clever you'd ZIP the releases to 
guarantee delivery.

There are 8 links that I must feed Jigdo to get the Woody release. Each 2 
hour wait is rewarded with another request for a link. This takes 16 human 
hours and 16 computer hours to get the entire release.  Apparently noone 
around here has ever heard of batch downloading. With FTP, I hit mark 8 
times in a GUI program, hit start, and come back tomorrow morning and see 
whether it finished or crashed. When jigdo can meet or beat that standard 
it will get more popular. GUI... mark-em-all... download... wake up the 
next morning all done!

Ads more than one step. I'm willing to tolerate an additional step or two 
for your convenience but 8 steps with 2 hour waits in between, I'll see you 
in the next version!

The Jigdo process may have been adapted to other OS but it is clearly 
designed for *nix systems. In the future the jigdo lists need to provide 
distributed downloading of ISO images too. If it's any more complicated 
than download the ISO, burn to CD, it will continue to fly like a lead baloon.


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

Re: Is GPL source for binary cd1 all on source cd1?

[Chris Lawrence]

On Nov 01, Blars Blarson wrote:
 In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes:
  On Thu, Oct 31, 2002 at 12:09:59AM -0800, Blars Blarson wrote:
   Is all the source for the GPL software on the Official woody
   3.0r1_nonUS x86 cd contained on the first source CD, or am I going to
   have to download the entire source set if I give away the binary CDs?
 
 If you don't want to give away a full set of CD then you have to
 regenerate your own shrinked CD set to be sure that the match
 between binary packages and source packages is ok.
 
 Or, in the case of giving away several copies of binary CD1, with the
 required offer of GPL source, I have to generate and keep the entire
 source set for three years.  (Doing so is less labor than figuraing
 out exactly what sources I need.)  Anyone giving the CD to a freind
 has the same obligation.
 
 Oh well, I had hoped not to have to tie up my DSL line for that long.

I believe you would only need to give away source CDs 1 and 2, at
least for woody, as the code that creates the CD images puts the
source packages in the same order they are added to the binary CDs.
You may want to verify this manually, though.  (I know this is the
case for the CDs I make, but I use a different script to create the
images.)

Alternatively, you could give away the LordSutch.com mini-ISO image;
the complete source will burn on a single CD.  However, it's not a
very complete installation (no X, for example).


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/

Computer Systems Manager, Physics and Astronomy, Univ. of Mississippi
125B Lewis Hall - 662-915-5765


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

RE: jigdo-cd ... mirror site?

[SELINE, CHRIS [RD/0111]]

unsubscribe [EMAIL PROTECTED]

-Original Message-
From: Greg C. Madden [mailto:[EMAIL PROTECTED]]
Sent: Sunday, October 13, 2002 3:20 PM
To: debian-cd
Subject: Re: jigdo-cd ... mirror site?



On Sun, 2002-10-13 at 14:02, Brian Wiese wrote:
 I was looking at getting debian on cd, so it looks like the way to do this
 now is with something called jigdo.  Well, on the webpage talking about
 this:
   http://www.debian.org/CD/jigdo-cd/
 
 the link to the jigdo homepage says the webpage does not exist.
 so, this jigdo thing is some software I run (on windows and linux) to
 manage a download of a debian ISO or something?  please let me know what I
 need to do to get debian on cd. 
 
 thanks, peace
 
   Brian Wiese | [EMAIL PROTECTED] | aim: unolinuxguru
snip

It may be a broken link. You can get Jigdo here.. or if you have a
Debian install it is included in Woody.
http://home.in.tum.de/~atterer/jigdo/

There is a good howto on th LDP site
http://www.tldp.org/HOWTO/mini/Debian-Jigdo/index.html


-- 
Greg C. Madden
Debian GNU/Linux



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


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

RE: cvs commit to debian-cd by hertzog

[SELINE, CHRIS [RD/0111]]

unsubscribe [EMAIL PROTECTED]

-Original Message-
From: Attila Nagy [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 11, 2002 8:43 AM
To: Raphael Hertzog
Cc: [EMAIL PROTECTED]
Subject: Re: cvs commit to debian-cd by hertzog


Hello,

 Duh. I wonder what's wrong. Can you give me some more information ? At
 what moment does it fail ? How ? Is there a message or something ? Do
 you have the isolinux prompt or not ?
I quickly did the images and booted them with VMWare.
For the first image it did not boot (could not find the image, don't
remember the name exactly :-O), the fourth booted but I couldn't get
further than the debian-installer text-menu (detect CD, set up d-i,
shell).

 Does it work with the old isolinux.bin of woody ? I really wonder what
 I've done wrong...
Don't know, and until monday I will have no chance to get to that
machine...

 I also added the -l switch to the mkisofs call. Does it work without
 that switch ?
I will try.

--[ Free Software ISOs - http://www.fsn.hu/?f=download ]--
Attila Nagy e-mail: [EMAIL PROTECTED]
Free Software Network (FSN.HU)phone @work: +361 210 1415 (194)
cell.: +3630 306 6758


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


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

Jigdo Mirror

[Chris]

Hi,

I am trying to burn the source-2 disk (I use Debian a lot and I wanted the
latest disks.)  Disks 1-7 and source 1 (nonus) downloaded fine but source 2
has over five hundred files for which a 'no permission' error is returned
when downloading over ftp.  I tried more than one mirror, they all have the
same error.  I'm going to try http now, but I though I'd let you know.

Thanks,
Chris Rhodes



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

unsubscribe

[chris adler]

- Original Message -
From: Debian Boot CVS Master [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 11, 2002 11:39 PM
Subject: cvs commit to debian-cd by tfheen


 Repository: debian-cd
 who:tfheen
 time:   fre jul 12 08:39:14 CEST 2002
 Log Message:
   Fix extra semicolon typo.


 Files:
 changed:Makefile


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




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

Re: Fwd: Re: Running translated install system from harddisk?

[Chris Tillman]

On Mon, Jul 15, 2002 at 12:17:18AM +0200, Raphael Hertzog wrote:
 Selon Chris Tillman [EMAIL PROTECTED]:
 
  For the first point release, can we include the xlp extra language pack on 
  the CD for all architectures?
 
 Sure, this has already been done a long time ago. :-)
 
 Cheers,
 -- 
 Rapha?l Hertzog -+- http://strasbourg.linuxfr.org/~raphael/
 Formation Linux et logiciel libre : http://www.logidee.com
 

OK, so it won't hurt anything on your end if we actually put it in the 
archive under disks-powerpc, etc. Thanks!

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  http://www.debian.org/releases/woody/installmanual  |
|   debian-imac (potato): http://debian-imac.sourceforge.net   |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


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

Re: boot-m68k script on debian-cd

[Chris Lawrence]

On Jun 30, Santiago Garcia Mantinan wrote:
 I've been having trouble because of the wget lines on this scripts and I
 had to tell wget to use passive mode to retrieve them, when I tols Raphael
 about this and if I should commit the passive changes he told me to ask you
 if there was any particular reason why this should be downloaded instead of
 including it on debian-cd itself.
 
 Is there any reason for us not including those files on debian-cd?

At least in the case of woody, dmesg and dmesg.readme appear to
already be in the disks-m68k directory, so the wget lines should no
longer be necessary in woody/boot-m68k.  You can safely remove them.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: Boot Floppy Image?

[Chris Lawrence]

On Jul 01, Matthew Tedder wrote:
 Does anyone know of the existance of a boot floppy image for
 installing Woody?
 
 I downloaded the 8 CD images, but no floppy image appears to exist
 on the first one under the install directory that would start an
 installation program.  This is a problem for me, because the test
 system I am trying to use does not boot off the CD ROM.

Floppy images are under dists/woody/main/disks-$ARCH/; probably you
want ones from the images-1.44 directory.

As an alternative, you can use the sbm.bin image as a floppy image; it
will let you boot the CD without needing bootable CD support.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: About harware detection and configuration tools in 1st CD

[Chris Lawrence]

On Jun 14, Michael Stone wrote:
 On Fri, Jun 14, 2002 at 07:38:42AM +0100, Philip Hands wrote:
  Fair enough --- perhaps popularity-contest should be made standard?
 
 No. Debian doesn't need spyware by default.

popcon asks if you want it to send in its results, after a page-long
description of what it does, and the default is no.  (popcon is useful
for more than just spyware; it's an easy way to tell what YOU use on
YOUR system.)


Chris, who runs popcon on all of his systems
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: Unofficial woody MiniCD images updated

[Chris Lawrence]

On Jun 10, Anthony Towns wrote:
 It doesn't need the uncompressed Packages file, but it *does* need the
 correct entry for the uncompressed Packages file in the Release file.
 
 (In truth, it could probably avoid needing the entry in the Release file
 too, but it does need it atm)

Thanks for the clarification.  It's not that big a deal, but I
expected it to just work after skimming the code, and it didn't.
Really just more frustrated that I should have tested it...

(As it is, the entry in the Release file won't be there the way
debian-cd works unless the uncompressed file is generated by
apt-ftparchive, so I'd have to remove it after building the Release
file.  But then the Release file would be technically incorrect,
because it would reference a missing file.  Catch-22.)


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/

Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi
208 Deupree Hall - 662-915-5765


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

Re: Unofficial woody MiniCD images updated

[Chris Lawrence]

On Jun 10, Chris Lawrence wrote:
 On Jun 09, Andrea Balzi wrote:
  I've try to install your MiniCD but I've found some problems.
  I've this error when I start the installation base system:
  
  Invalid Release file, no entry for main/binary-i386/Packages
  
  To resolve this error I've change the MiniCd with the first CD of unoffical 
  Woody CD pack.
 
 Grr, why does debootstrap need the *uncompressed* Packages file?  Look
 for a fix shortly...

All four CD images are now updated; sorry for the mixup.  I should
know better than to mess with something that works to save a couple
hundred kB for people :-)


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Unofficial woody MiniCD images updated

[Chris Lawrence]

I have updated the LordSutch.com MiniCD images for alpha, i386, m68k,
and PowerPC available at http://www.phy.olemiss.edu/debian-minicd/ to
the current state of woody as of today; the main change is the upgrade
of dpkg to 1.9.21.  I also added ipppd for the benefit of ISDN users.

The updates should propogate to the mirrors over the next day or so.
Additional mirrors would be greatly appreciated.

From the README file (http://www.phy.olemiss.edu/debian-minicd/README.txt):

These ISO images are installation media for the upcoming release of
the Debian GNU/Linux operating system (Debian 3.0).  For more
information about Debian, please visit http://www.debian.org/.

The ISOs are small enough to burn to a 8 cm (3 inch) CD-R/RW (although
they'll also work on a 12 cm/5 inch CD-R/RW media), and contain enough
packages to install a functional version of Debian woody without going
to the net -- all packages from required, important and standard are
included, as are emacs21, postfix, ssh, and gnupg when they fit.  A
complete list of included packages is available in the .packages file
for each architecture.

More discussion about these images is at:
http://www.debianplanet.org/article.php?sid=681
http://www.debianplanet.org/article.php?sid=642


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/



msg03993/pgp0.pgp
Description: PGP signature

Something to add to http://www.debian.org/CD/netinst/

[Chris Kulas]

Finally found some time to install Debian on my home box. I do have a
broadband connection and need kernel 2.4  / ext3fs support so I have
been
hunting for a suitable netinst CD.

The much quoted image at http://people.debian.org/~ieure/netinst/ is of
no use to me unfortunately since my old trusty Adaptec 2940UW (albeit
with an 2.23 bios) is unable to load the bf2.4 image.

The image found at
http://people.debian.org/~dwhedon/boot-floppies/
however worked like a charm.

I only noticed that it was unable to create the final boot floppy disk
at the end of base installation. Doesn't matter much though since
rescue from the boot CD works great for the first boot-up until all
the bootmanager stuff is sorted out. :)

Thanks.

Best regards,
Chris



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

Re: Woody Mini-cd results

[Chris Lawrence]

On Jun 01, D  E Radel wrote:
 Your 185MB CD was a life-saver! It's a keeper!

On the same topic, I've added a CD for Alpha and updated the CDs to
woody as of a couple of days ago (that makes this revision 15 for
those of you keeping score at home).  The Alpha CD is fairly important
to test because I used a isomarkboot compiled for i386 to make it
bootable; IIRC nobody has tested whether that works yet (there was
some discussion on the debian-cd list about it though).

Anyway, the URL:
http://www.phy.olemiss.edu/debian-minicd/

For rsync locations, mirrors, and md5sums, see:
http://www.phy.olemiss.edu/debian-minicd/README.txt


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: About harware detection and configuration tools in 1st CD

[Chris Lawrence]

On May 31, Santiago Vila wrote:
 Mantas K. wrote:
  Most simple users don't like debian, because they think, that there are not
  user-friendly configuration tools (they simply download 1 CD, try to install
  and find that they are rigth).
 
 Well, if they really think Debian is just CD #1, I would much prefer
 that they continue using Red-Hat or whatever...

Well, IMHO if a user needs more than CD #1 then they're doing
something more sophisticated that what Red Hat would include anyway.
In reality, I'll keel over and die if I meet anyone who *needs* more
than CDs 1 and 2 of woody; if they need anything else, it's one or two
weird packages that they're better off spending 10 minutes
downloading (on *dialup*) than spending $$ to buy all 6+ CDs.

Frankly we already have too many people who think that I need all
6/7/8 CDs; it's becoming a nightmare for distributors and mirrors
alike, especially since virtually nobody needs what's on 3+ anyway.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: What kernel stuff on CD1? Was Still no TeX in CD#1

[Chris Lawrence]

On May 29, Santiago Vila wrote:
 The first number is the number of people in the popularity contest who
 use the package regularly.
 
 Hmm, I wonder why doc-linux-text has priority standard at all, when so few
 people use it regularly... Anyway, I would drop all the aspell packages, plus
 libopenh323-dbg, timidity-patches, xspecs, erlang and emacs20-dl.

Note that for non-binary packages, popularity-contest gives weird
results because it only pays attention to stuff in a normal $PATH;
lots of people may read docs, but popcon ignores them.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/

Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi
208 Deupree Hall - 662-915-5765


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

Re: What kernel stuff on CD1? Was Still no TeX in CD#1

[Chris Lawrence]

On May 24, Philip Charles wrote:
 I have been convinced.
 
 What kernel images, packages, source, patches do we want on CD1?
 
 At the moment we have, rough list.  Resubmitted in case you have deleated
 it.  What no source!

Certainly all the 2.4.16 packages could go; there's no point in having
them and 2.4.18 as well.  FWIW I'd ditch the whole lot of precompiled
images (they're not on my CDs any more), especially since most are
already on the CD as part of boot-floppies, but that's just me.

kernel-source-2.2.20 and kernel-source-2.4.18 are probably the most
useful; I'd add pcmcia-source and kernel-package too.

(I also added kernel-patch-2.2-ext3 for good measure; maybe some other
patches would be nice if they're small.)


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Mini-ISO updated for bf 3.0.23

[Chris Lawrence]

I've updated the unofficial mini-ISO at www.phy.olemiss.edu to include
the 3.0.23 boot-floppies along with a few other goodies; so, go forth
and test!

http://www.phy.olemiss.edu/debian-minicd/
(also rsync:://www.phy.olemiss.edu/debian-minicd/)

The mirrors should pick up the changes in the next day or so.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: Mini-ISO updated for bf 3.0.23

[Chris Lawrence]

On May 22, Steve Haslam wrote:
 OK, I'll poke around with what I've got at the moment and see if I can find
 out why these packages are being brought in... maybe I'll just drop a load
 of them into an exclude list

I believe make status is responsible for most of the bloat; if you
poke around in that part of the makefile, you can probably streamline
it.  (I also recommend getting the latest debian-cd out of CVS if you
haven't already; make status seems to have been trimmed a bit lately
in the mainline debian-cd.  My code was a bit less subtle and just
makes a smaller status file on its own using debootstrap IIRC.)

Alternative B is to hack tasks/list2cds to remove the use of the
status file; with a well-formed TASK file, it's unneeded, though it is
nice to get a warning that the base system won't fit on a 5MB ISO...


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/

Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi
208 Deupree Hall - 662-915-5765


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

boot-floppies 3.0.22

[Chris Beswick]

Hi the cd image for x86 and ppc from people.debian.org/~ieure/netinst is not
working, the apt-sorces are set to stable NOT woody/testing, i'm not sure if
this is a boot images or a cd thing so i am reporting it here as it is the
'closest' email to the iso download.

c.


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

Re: About 1st debian CD

[Chris Lawrence]

On May 03, Mantas K. wrote:
 I think 1st debian CD is very important for all users, especially for 
 beginners and should not contain duplicates like now:
 
 See for example /pool/main/k - there are about 130MB of various 
 kernel-images:
 /kernel-image-2.2.20-i386 
   - ~9MB
 /kernel-image-2.2.20-reiserfs-i386 
 - ~2MB
 /kernel-image-2.2.20-udma100-ext3-i386- ~5MB
 /kernel-image-2.4.16-i386 
   - ~58MB !!!
 /kernel-image-2.4.18-i386 - ~52MB
 /kernel-image-2.4.18-i386bf   - ~6MB
 
 Who needs 130MB of various kernel-images in 1st CD ???
 I understand - kernel 2.2.20 and 2.2.18 are really usefull, but what about 
 2.4.16 ? How many users will use kernel-image-2.4.16-i386 when there are 
 newer version - kernel-image-2.4.18-i386 ?
 We shoult remove ar least kernel-image-2.4.16-i386, then x-window-system
 (xserver-xfree86, xserver-common, xfonts-base, xfonts-100dpi, xfonts-75dpi) 
 will fit in 1st CD without problems.
 
 In previous prelelease (debian-30pre1-i386-binary-1_NONUS.iso) almost all 
 x-window-system packages were in the 1st CD, why in pre2 most X packages 
 are moved in second CD ?

1. What CD images are you referring to?  The ones on ftp.fsn.hu are
unofficial, as are any other CD images floating around on the net.

2. (To whomever is responsible for these images:) You probably should
update your copy of debian-cd from CVS and remove base-woody from
the task file you are using.  This will eliminate a lot of stuff
that's allegedly base but unimportant.  Pick a 2.2 and a 2.4 kernel
image and put them in your task file.

Woody CD 1 should be fairly complete with minimal hassle, at least for
all ISO-8859-* languages.  (The cjk tasks bring in a lot of extra
stuff, so it might be worthwhile to have a separate Woody CJK cd that
has cjk tasks on it.)

Hope this helps some.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/

Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi
208 Deupree Hall - 662-915-5765


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

isolinux image updated

[Chris Lawrence]

I've updated the ISOLINUX test image as follows:
 - Updated to woody as of Wed, 17 Apr 2002 19:57:19 UTC
 - Added pptp-linux
 - Added a symlink woody-i386-1.iso
 - Added a few records (Application ID, Publisher ID, Preparer ID)

Size:   193101824 bytes
MD5SUM: 08d438f8e8a994088aaad5b3838e69f8

HTTP:  http://www.phy.olemiss.edu/debian-cd/
RSYNC: rsync://www.phy.olemiss.edu/debian-cd/


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: Please test this woody cd image

[Chris Tillman]

On Mon, Apr 15, 2002 at 09:27:56AM +0200, Raphael Hertzog wrote:
 Le Sun, Apr 14, 2002 at 05:02:49PM -0700, Chris Tillman ?crivait:
   Also it would be fine if we could give some guidance about how to make that 
   choice - type of system, connected hardware, age? I guess the differences
   are already covered for vanilla/compact/idepci, but how about bf2.4? Which
   hardware is 'highly recommended' to go with 2.4; new within the last 
   year or two, or ???
 
 Well, bf24 is to be used by people who want a 2.4.x kernel. It should
 be used if you have recent hardware with USB keyboard for example.
 
  +On newer hardware, allows a selection of kernel images to boot from. On
  +older hardware, it will boot the `idepci' flavor kernel.
 
 That's wrong. It won't boot idepci on older hardware. Either the menu
 works and it will boot, or it won't boot at all. In which case they
 should boot on one of the other CDs available.
 

Ok, I'll fix it. Thanks, I must have been reading about the MultiBoot
thing instead.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  http://www.debian.org/releases/woody/installmanual  |
|   debian-imac (potato): http://debian-imac.sourceforge.net   |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


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

Re: Please test this woody cd image

[Chris Tillman]

Here's the patched patch:

Index: rescue-boot.sgml
===
RCS file: /cvs/debian-boot/boot-floppies/documentation/en/rescue-boot.sgml,v
retrieving revision 1.98
diff -u -r1.98 rescue-boot.sgml
--- rescue-boot.sgml2002/04/15 04:33:21 1.98
+++ rescue-boot.sgml2002/04/16 04:08:55
@@ -338,16 +338,23 @@
 the ttboot:/tt prompt.  Here you can enter your boot arguments, or
 just hit ementer/em.
 p
-
-Note that official Debian CD-ROM sets for arch-title; will boot
-different ``flavors'' depending on which CD-ROM you boot from.  See
-ref id=kernel-choice for a discussion of the different flavors.
-Here's how the flavors are laid out on the different CD-ROMs:
+CD #1 of official Debian CD-ROM sets for arch-title; will present a
+ttboot:/tt prompt on most hardware. Press ttF3/tt to see the
+list of kernel options available from which to boot. Just type your
+chosen flavor name (idepci, vanilla, compact, bf24) at the
+ttboot:/tt prompt followed by return.
+p
+If your hardware doesn't support booting of multiple images, put one
+of the other CDs in the drive.  CD's 2 through 5 have no selection
+menu but will boot different ``flavors'' depending on which CD-ROM is
+inserted. See ref id=kernel-choice for a discussion of the
+different flavors.  Here's how the flavors are laid out on the
+different CD-ROMs:
 taglist
 tagCD 1/tag
 item
-On newer hardware, allows a selection of kernel images to boot from. On
-older hardware, it will boot the `idepci' flavor kernel.
+Allows a selection of kernel images to boot from (the idepci flavor is
+the default if no selection is made). 
 /item
 
 tagCD 2/tag
@@ -371,15 +378,8 @@
 /item
 
   /taglist
-So, if you want to boot from one of the above flavors, put that CD in
-the drive for booting. 
 p
-If you are using CD #1, and your hardware supports it, a ttboot:/tt prompt
-will be displayed. Press ttF3/tt to see the list of kernel options
-available from which to boot. Just type your chosen flavor name
-(idepci, vanilla, compact, bf24) at the ttboot:/tt prompt followed by
-return. If your hardware doesn't support booting of multiple images, 
-CD #1 will boot the idepci flavor.
+
 
 !--   Which is right on a CD? \install or \boot ?  --
 

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  http://www.debian.org/releases/woody/installmanual  |
|   debian-imac (potato): http://debian-imac.sourceforge.net   |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


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

Re: Please test this woody cd image

[Chris Tillman]

On Sun, Apr 14, 2002 at 10:00:52PM +0200, Raphael Hertzog wrote:
 Le Sat, Apr 13, 2002 at 07:44:42PM -0400, Adam Di Carlo ?crivait:
   1: multiboot
   2: vanilla
   3: compact
   4: idepci
   5: bf2.4
 [...]
  
  Sounds excellent to me.  I'm excited to try it, I've never even seen
  the ISO boot in action.
 
 Can you update the installation manual if it hasn't already been done ?

I can - since I don't have an i386 or a burner, where can I find out what 
the user will see with the multiboot CD, and what choices will be available?
The other four flavors are all available on multiboot? Anything else?

Also it would be fine if we could give some guidance about how to make that 
choice - type of system, connected hardware, age? I guess the differences
are already covered for vanilla/compact/idepci, but how about bf2.4? Which
hardware is 'highly recommended' to go with 2.4; new within the last 
year or two, or ???

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  http://www.debian.org/releases/woody/installmanual  |
|   debian-imac (potato): http://debian-imac.sourceforge.net   |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


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

Re: solution for base-config/cat:: problem

[Chris Lawrence]

On Apr 09, Eduard Bloch wrote:
 #include hallo.h
 Raphael Hertzog wrote on Mon Apr 08, 2002 um 11:31:46PM:
 
  The cat:: missing command is an error which someone else already
  reported to debian-cd when using the bf24 flavor.
 
 Chris: Please, use ALL arguments from particular syslinux.cfg files. I
 was able to reproduce this bug. IMHO caused by missing ram_size
 specification, so the ramdisk-filesystem gets random IO errors, so the
 dbootstrap_settings file is not written correctly (contains cat:
 input/outpur error) and base-config dies while parsing it.
 
 I extracted the rootfs from your image, built an own CD with it (rest
 was from bf2.4 flavor), and it worked fine.

I wasn't sure what all the bootargs were for, so I wasn't sure which
ones were needed (I didn't want to accidentally end up with a disk
prompt or something).  I'll fix this in debian-cd cvs and update the
ISO image accordingly.

The boot.bat command lines will probably have to be fixed too.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: Multiboot testing please ...

[Chris Lawrence]

On Apr 06, Raphael Hertzog wrote:
 Chris Lawrence is willing to do tests with isolinux, please continue as
 we may want to try that if we have troubles with the actual
 multiboot stuff. Feel free to prepare a patch too. :) It may also
 have more interesting features (no size limit on the boot
 image, more configurable menu and so on).

Ok, I have put together some files to make the isolinux idea work,
swiping quite a bit from the boot-floppies CVS (mainly the text files
for f1-f10 and the intro screen).  The only file in debian-cd that I
had to modify was tools/boot/woody/boot-i386, and the changes are
are enabled with a $ISOLINUX setting in CONF.sh .  CDs 2-4 keep the
old boot sector images.

This actually *frees* space on the ISO (about 1 MB), as only the root
disk needs to be included separately in the isolinux directory, and
the boot sector is not a full floppy image.

How it works: on boot, it displays a screen similar to the rescue
floppy's first screen.  The F-keys are the same; the only real changes
are on F3, where you can choose from:

dbootstrap: (loads root.bin with the same options written to install.bat)
 linux or idepci (default)
 bf24
 compact
 vanilla

And these rescue settings: (noinitrd)
 rescue
 rescbf24
 resccomp
 rescvanl

Anyway, I burned a CD and tested it, and it seems to work OK.  I'll
post a URL for downloading it for testing as soon as it gets done
rsyncing.

Note that this will be a 185MB 5cm/3in CD image.  It contains all of
the base system and standard, so you can treat it as a normal CD #1;
just make sure you have a network connection to install anything other
than the 229 packages that are on it when you set up APT.

Anyway, let me know what you think; I'll put together a patch against
CVS debian-cd once I'm sure it's all OK.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: Multiboot testing please ...

[Chris Lawrence]

On Apr 07, Heikki Vatiainen wrote:
 Chris Lawrence [EMAIL PROTECTED] writes:
 
  http://relativity.phy.olemiss.edu/~cnlawren/woody-i386-1.raw
 
 Could you give us a MD5SUM for it? I am pulling it from Mattias and
 thought about mentioning it in our national Usenet linux group.

quantex ~$ md5sum /cdimage/hardcore/woody-i386-1.raw 
28250339f99ced5281e1c3c9ba7fe560  /cdimage/hardcore/woody-i386-1.raw

I checked and it made it to relativity OK with that md5sum.

Anyway, let me know success/failure reports.  It works on both of my
laptops here (both 2001 hardware) but I'd like to know about earlier
systems.  Also, feedback about the initial screen (and F1-F10) would
be nice.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

isolinux test image, debian-cd changes available

[Chris Lawrence]

(CC'd to debian-boot since the discussion there seems to be lingering
on this topic too.)

Per discussion on debian-cd, I have prepared a test ISO and changes to
debian-cd to allow the use of ISOLINUX in the boot sector.

The changes to debian-cd are at:
  http://www.lordsutch.com/cds/debian-cd/isolinux-bits.tar.gz

  (You only need these to build an ISO from a local mirror.  I'll
  probably commit this to debian-cd cvs if Raphael says it's OK; the
  only file changed is tools/boot/woody/boot-i386, while the remainder
  is filched  modified from boot-floppies CVS or is new)

The CD image (updated to ensure the prompt shows up) is available at:
  http://www.phy.olemiss.edu/debian-cd/woody-i386-1.raw
  Size: 194281472 bytes
  MD5SUM: 37f463f20265d8b3e2300cd304783ba9

  Also at rsync://www.phy.olemiss.edu/debian-cd/
  The rsync should be very fast if you have the previous image.

  (If you have the old image, you need to hold down SHIFT to get the
  boot: prompt to show up.)

Don't worry about killing the server; I'll throttle it if necessary.

See http://lists.debian.org/debian-cd/2002/debian-cd-200204/msg00067.html 
for all the details of how this is implemented.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: ISOLINUX testing (was Re: Multiboot testing please ...)

[Chris Lawrence]

On Apr 08, Raphael Hertzog wrote:
 Le Sun, Apr 07, 2002 at 10:29:31PM +0100, Philip Hands écrivait:
  Just tried this -- If one tries an install of the bf24 kernel, when you
  get to the Configure Device Driver Modules, it's obviously not taking
  account of the kernel it was booted with, but is unpacking the modules
  for 2.2.20.
 
 Did you try by booting the rescue targets ?
 rescue
 rescbf24
 resccomp
 rescvanl
 
 Since Chris said dbootstrap: (loads root.bin with the same options
 written to install.bat), I'm afraid that installing via boot.bat
 gives the same problem ?

I tracked down the problem... each flavor uses its own root.bin.
After some tweaking, I fixed the build process and updates are now
online (see my lagged mail to the list).


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: ISOLINUX testing (was Re: Multiboot testing please ...)

[Chris Lawrence]

On Apr 08, Raphael Hertzog wrote:
 Le Sun, Apr 07, 2002 at 04:54:15PM -0500, Chris Lawrence écrivait:
  Hmm.  I see the problem.  There's a separate root.bin for each flavor,
  and the code isn't accounting for that.
 
 Are you going to fix it also for the boot.bat that is generated by
 debian-cd in tools/boot/woody/boot-i386 ?

Sure.  Do you want me to commit the whole set of changes for ISOLINUX
or just this fix?  (The whole set will be easier, but I can give you a
manual patch to fix the boot.bat file with a bit of work.)


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: ISOLINUX testing (was Re: Multiboot testing please ...)

[Chris Lawrence]

On Apr 08, Philip Hands wrote:
 On Mon, 2002-04-08 at 00:05, Chris Lawrence wrote:
 
  I tracked down the problem... each flavor uses its own root.bin.
  After some tweaking, I fixed the build process and updates are now
  online (see my lagged mail to the list).
 
 Hm, doesn't fix it for the bf2.4 flavour when I try it I'm afraid.
 
 It's still unpacking current/drivers.tgz, whereas it should be unpacking
 something like current/bf24/drivers.tgz
 
 Just to make sure, the md5sum for the one I just tried is:
 
   af6c34970ae8295f46c2e00e72292cd1  woody-i386-1.raw

Hmm.  It may need Yet Another Special Argument.

Boy do I love how wonderfully opaque boot-floppies are.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: 2.4 kernel as default boot kernel on CD #1 ??

[Chris Lawrence]

On Apr 06, Philip Hands wrote:
 The closest I'd be willing to go towards making a change, would be some
 form of kernel selection menu on the first CD, still with the vanilla
 2.2 kernel as the default, but giving people the choice even if they
 only get CD#1.
 
 That would be conditional on some evidence being forthcomming that the
 resulting CD would be bootable on at least as many machines as is
 currently the case.  Can anyone provide that?
 
 The ISOLINUX/MEMDISK thing mentioned earlier looks interesting.  Has
 anyone played with this?  Presumably we could use MEMDISK to select
 between boot floppies, with no changes required to the boot floppy
 images, so would only change things by bumping a few packages off the
 end of CD#1.

I'll try an experiment this weekend.  My gut feeling is that you can
probably do it without bumping anything off the ISO, as the other
flavors are already on disc 1 anyway (just not in the boot sector).

Now, whether or not this is going to be acceptable to aj on the
official CDs is another question.  But it's an option that most
vendors will probably jump at.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: debian-cd 2.2.13 and woody.

[Chris Lawrence]

On Mar 16, Philip Charles wrote:
 On Sat, 16 Mar 2002, Chris Lawrence wrote:
 
  That's a bit of a head-scratcher, as I had no trouble getting all of
  games and junior on CD 1.  Granted, I was using 700MB as my blank
  size, rather than 650MB.
  
  Do you have including of suggestions disabled?  Also, is basedebs.tar
  being stuck (needlessly) on your CD #1?
 
 I am rather unhappy about using 700MB media as many people use old
 hardware for their first installation.  No basedebs.tar, but multiboot.

True, it's probably best that the official CDs fit on 650MB media.
Especially since CD-RW media doesn't seem as available in the 700MB size.

 I took a look at list2cds and discovered a YAUO (yet another undocumented
 option) NORECOMMENDS.  Is this what you meant?  IMO this is a rather
 violent option.  Should list2cds be hacked to include a NOSUGGESTS option?

Probably; at least, that's what I did in my rewritten script
(list2cds-cram; unfortunately, it's not a drop-in replacement, which
is why I haven't stuck it in CVS).  I usually build with just depends
and recommends honored, though I've been experimenting with code to
avoid recursive suggestion inclusion (suggested packages don't need to
pull in THEIR suggestions too, otherwise you get a really dense graph
really quickly... debconf will pull in half of GNOME if you let the
suggestions get away from you).  I also hacked in code to allow
treating doc packages that are suggested or recommended as
dependencies for purposes of building the CD.

 Anyway I will try a YAB (yet another build) with the NORECOMMEDS enabled.

That should free up a TON of space.

I probably should tar up my hacks as inserted atop debian-cd CVS; at
the moment, they just sort of sit in a directory on the lordsutch.com
website.  (http://www.lordsutch.com/cds/debian-cd/hacks.html for
details.)


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: debian-cd 2.2.13 and woody.

[Chris Lawrence]

On Mar 16, Philip Charles wrote:
 I carefully built task-woody so that packages for each task were grouped
 together in the list.  All the packages for basic-desktop, desktop,
 laptop, dialup, and print-server are on the first CD.  games and junior
 are split between the first and second CDs.  All the other tasks are on
 the second CD.  The following CDs are clear of Task: foo packages.

That's a bit of a head-scratcher, as I had no trouble getting all of
games and junior on CD 1.  Granted, I was using 700MB as my blank
size, rather than 650MB.

Do you have including of suggestions disabled?  Also, is basedebs.tar
being stuck (needlessly) on your CD #1?


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: we're underrepresented in India. :-(

[Chris Lawrence]

On Mar 12, Saugata Chakrabarti wrote:
 Dear Richard,
 Debian is not underrepresented in India,
 
 We use to download ISO or raw format, write CDs and distribute within
 our LUG members. Most of the time, we just pay only the cost of blank CD
 and get our favorite Linux distributions in hand. 
 
 I am shocked and astonished in your comment :-(
 What makes you feel like that  ..  
 
 Hope, in future you will think twice before comment anything in public
 ;-)

I think Richard's point is that there is a lack of vendors for people
who don't have contact with a LUG and/or don't have the bandwidth for
dowloading ISOs.  While a number of vendors ship to India, it would be
good to have a few more vendors in India so people could get CDs more
quickly and inexpensively.

Being a vendor isn't all that hard - you need the ISOs, a CD burner,
good access to blank media, envelopes, and stamps, and a spreadsheet
to keep track of the money for the taxman to get his cut.  Nobody's
going to get rich selling Debian CDs, but it's a nice supplemental
income for relatively little work.

(Having said that, I suspect Debian could do better in India if our
website was available in Hindi and other Indian languages.  I realize
a lot of the tech community there speaks English, but that's true in a
lot of other countries where we've translated stuff too.)


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: Official woody netinst images

[Chris Lawrence]

On Mar 07, Karl-Martin Skontorp wrote:
 * Richard Atterer ([EMAIL PROTECTED]) wrote:
   - 100MB, should fit on a credit-card sized CD (=150MB) - maybe just
 boot-floppies and base. One should be able to install via the net
 even with hardware which is not supported by boot-floppies, e.g. 
 PCI ISDN cards.
 
 I don't think my credit-card CDs will fit more than about 30 MB. The
 images from here fit:
 
   http://people.debian.org/~ieure/netinst/
 
 There are also some 80 mm. CDs, about 200 MB. They are not
 rectangular, but will fit in a shirt pocket.

Here are the sizes I am aware of:

Business card CDs: ~50 MB (approximately 8 cm by 5 cm)
8 cm (3 in) CDs:~185 MB
12 cm (5 in) CDs:   ~650 MB / ~700 MB

(DVD-R(G) 2.0: ~4300 MB or 4.7x10^9 bytes)

I assume the first two formats can also be produced with the 700 MB
track spacing, but I don't think any vendors do that.

These are traditional megabyte figures, not 10^6 byte figures.

My general feeling is that the 50 MB size is really something of a
gimmick, as you can't really carry it around safely in a wallet
without breaking the CD.  The 185 MB size is pretty nice, though, and
you can put a useful Debian install on it.  (I can see the value in
providing all three sizes for CD 1: 50, 185, and 650.  But, you won't
fit anything much beyond disks-$ARCH on a 50 MB blank.)


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Building DVD images

[Chris Lawrence]

I recently built a woody DVD-R image and wanted to share my
experiences with the group.  (The code I used will appear on my CD
hacks area at http://www.lordsutch.com/cds/debian-cd/ sometime
soon... nag me if you don't see it by Monday.)

The main issue I faced was that the shell's math seems to be limited
to 32 bit integers, which broke some of my disk sizing code (and may
also break bits of the standard scripts).  I decided to change all the
code to use kilobytes instead of bytes, which resolved that problem.
I also had to hack my list2cds-cram code to use kilobytes (I could
have used Python longs instead, but with the 2kbyte rounding I decided
that there was no need to keep track of bytes any more).

I didn't hack the source disk building code, but it probably would
need it too.  (You can't put source and binaries on the same DVD;
woody's binaries took up 3.9 gigabytes on Intel, just including main
and non-US/main.  Double-sided media might work nice for this, if you
can get it...)

I was able to successfully write the ISO image at 2x to a Pioneer
DVD-R drive using the free DVD-R patch
(http://www.abcpages.com/~mache/cdrecord-dvd.html) for cdrecord.  The
DVD-R was readable on both the drive that wrote it and the DVD-ROM on
my Toshiba laptop.  (The laptop was also able to boot from the DVD-R.)

This was a one-off deal to test the DVD drive for my employers; I may
consider adding a DVD-R to my CD production farm if I can locate a
reasonably-priced 2x unit.

Anyway, I hope this info helps anyone who's considering building
Debian DVDs.  I should have the code on the website in the next couple
of days.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/

Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi
208 Deupree Hall - 662-915-5765


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

custom woody boot cd

[Chris Zubrzycki]

Hey, sorry for bothering everyone, but I have a question about the boot 
cds. I have a custom woody boot cd with an xfs kernel package, and xfs 
utils to format the partions xfs in the install process. I have been 
using this cd for my customers, but I wanted to know if there was a good 
tutorial on making a boot cd with a custom kernel and custom packages 
(so they do not have to be downloaded each time.) and I would need to 
add the xfs format options to the installer.

I've looked on the web for some ideas, but i could not find anything i 
understood well enough.

thanks again for the help.

PS: Please CC any replies to me, as I'm not on this list.

-chris zubrzycki
==

   One disk to rule them all, One disk to find them. One disk to bring
   them all and in the darkness grind them. In the Land of Redmond
   where the shadows lie. -- The Silicon Valley Tarot


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

Re: choose_medium.c and the /instmnt issue

[Chris Tillman]

On Fri, Dec 28, 2001 at 10:09:05AM -0800, John H. Robinson, IV wrote:
 On Thu, Dec 27, 2001 at 05:08:35PM -0800, John H. Robinson, IV wrote:
  
  it seems that i have resolved, either through accident or design, most
  of the /instmnt problems.
  
  the only issue left is the Live CD.
 
 and, of course, after putting the code down for a night, i came up with
 some possibly better ideas:
 
 my proposal: 
  a) add a new method, ``target'' that specifically looks under /target 
  b) look to see if we are a LiveCD, add a method ``LiveCD'' or whatever,
 that looks under some #define'd variable, so we can change it at will
 to meet the whims of the LiveCD people. (with some trickery, and if
 the LiveCD people say they want this, we can override the compiled in
 default via some bootargs variables)
 c) have ``mounted'' only available if there is a partition mounted on
/instmnt 
 d) same as it ever was 
 
 so b) and c) would be new, on demand, methods, similar in nature to the
 ``cdrom'' method.  
 
 this seems to leave everything as robust as possible, while making
 things seem a bit more natural.
 

FWIW John, my thought is that you've become familiar enough with this
stuff, which no one else has taken the time to do, that I would trust
your judgment as to how it should work. Also, I'm assuming you'll be
able to easily fix it if it does break something someone's
expecting. I just think it's horribly broken now, and that usually
means rethinking assumptions and trying to build in robustness as you
are doing.

-- 
*--v- Installing Debian GNU/Linux 3.0 v--*
|  http://www.debian.org/releases/woody/installmanual  |
|   debian-imac (potato): http://debian-imac.sourceforge.net   |
|Chris Tillman[EMAIL PROTECTED]  |
|   May the Source be with you   |
**


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

Re: list2cd rewrite

[Chris Lawrence]

On Nov 05, Martin Michlmayr wrote:
 * Chris Lawrence [EMAIL PROTECTED] [20011105 14:48]:
  in both MiniCD and 650 MB sizes, but it still needs work, and I don't
  know if I should commit it to CVS (under a different name, of course)
  until I get all this business worked out with the makefile and getting
  more accurate sizing info.
 
 Can you put it on http/ftp somewhere in the meantime and give us an
 URL?

Here's the location:

http://www.lordsutch.com/cds/debian-cd/hacks.html

Elsewhere in that directory (and under it) are the actual files; the
hacks.html file explains what's going on.  If something that's
required by the stuff there is missing, let me know and I'll make sure
it gets updated.

Hack away!

Also, if anyone's interested I probably can find the disk space to
serve woody network install MiniCD images (185MB) for Intel, m68k, and
PowerPC in the next few days.  Since I really don't make any money off
of them anyway after expenses (about $1 a pop for the media and cases,
plus $2 donated to Debian = $1 left over for me that pays for CD
burners, the 1394 hard drive, etc.) it's not like it's a big economic
loss for me :-)  It'd be nice if we could put together official images
like this for the network install crowd.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/


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

Re: Mark Montague: success report with sparc and hppa cd images (with minor issues)

[Chris Tillman]

On Thu, Oct 11, 2001 at 05:45:41PM -0700, Mark Montague wrote:
 
 I also thought a little more about the mime-support issue below, and
 realize that it's an extra-weird situation, in that, e.g. lynx
 Recommends: mime-support, and certainly shouldn't Depends:
 mime-support, but it would need the equivalent of Pre-Depends, e.g.
 Pre-Recommends: mime-support or some such, but no such category seems
 to exist. I'm not sure where I should bug report this...
 
 - -- a number of base packages complain that mime-support needs to be set
up; the ones I had problems with were lynx, less, and lpr:
 
 Setting up less (358-9) ...
 Warning: could not read '/etc/mailcap' (update stopped) -- No such
 file or directory
 restore from backup or delete and re-install mime-support package

I filed a bug on tasksel for this, but that was the wrong place. It's
actually a message from update-mime. The problem is that these packages are
not supposed to depend on mime-support, and just call update-mime if it
exists. apt-get does all the installations, then goes back and does all the
postinst's. So the deal is, the update-mime script has been installed, but
the mime-support postinst hasn't been run yet, which is where /etc/mailcap
gets created. And apparently update-mime isn't smart enough to create a new
/etc/mailcap when it's missing, and complains instead.

I was going to try to figure out a patch to send in with a bug report, but
if you beat me to it, so much the better...

-- 
**
|  .''`.  |   Debian GNU/Linux: http://www.debian.org  |
| : :'  : |   debian-imac: http://debian-imac.sourceforge.net  |
| `. `'`  |  Chris Tillman[EMAIL PROTECTED]  |
|   `-|May the Source be with you|
**


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

Re: Mark Montague: success report with sparc and hppa cd images (with minor issues)

[Chris Tillman]

On Thu, Oct 11, 2001 at 05:45:41PM -0700, Mark Montague wrote:
 
 I also thought a little more about the mime-support issue below, and
 realize that it's an extra-weird situation, in that, e.g. lynx
 Recommends: mime-support, and certainly shouldn't Depends:
 mime-support, but it would need the equivalent of Pre-Depends, e.g.
 Pre-Recommends: mime-support or some such, but no such category seems
 to exist. I'm not sure where I should bug report this...
 
 - -- a number of base packages complain that mime-support needs to be set
up; the ones I had problems with were lynx, less, and lpr:
 
 Setting up less (358-9) ...
 Warning: could not read '/etc/mailcap' (update stopped) -- No such
 file or directory
 restore from backup or delete and re-install mime-support package

I filed a bug on tasksel for this, but that was the wrong place. It's
actually a message from update-mime. The problem is that these packages are
not supposed to depend on mime-support, and just call update-mime if it
exists. apt-get does all the installations, then goes back and does all the
postinst's. So the deal is, the update-mime script has been installed, but
the mime-support postinst hasn't been run yet, which is where /etc/mailcap
gets created. And apparently update-mime isn't smart enough to create a new
/etc/mailcap when it's missing, and complains instead.

I was going to try to figure out a patch to send in with a bug report, but
if you beat me to it, so much the better...

-- 
**
|  .''`.  |   Debian GNU/Linux: http://www.debian.org  |
| : :'  : |   debian-imac: http://debian-imac.sourceforge.net  |
| `. `'`  |  Chris Tillman[EMAIL PROTECTED]  |
|   `-|May the Source be with you|
**

- End forwarded message -

-- 
**
|  .''`.  |   Debian GNU/Linux: http://www.debian.org  |
| : :'  : |   debian-imac: http://debian-imac.sourceforge.net  |
| `. `'`  |  Chris Tillman[EMAIL PROTECTED]  |
|   `-|May the Source be with you|
**


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

[Humor] Re: your ad

[Chris Lawrence]

[Response clipped]

I didn't realize we had diversified into placing ads in the personals...


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/

Instructor and Doctoral Student, Political Science, Univ. of Mississippi
208 Deupree Hall - 662-915-5949


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

Bug#85672: mkisofs: symlink tree support for mkisofs

[Chris Lawrence]

Package: mkisofs
Version: 3:1.9-1
Severity: important
Tags: patch

(CC'd to debian-cd this report is probably of interest to people there.)

The following patch should cleanly incorporate the symlink tree
support into mkisofs, provide the mkhybrid symlink and man page, and
make the package replace mkhybrid for people running apt-get
dist-upgrade.

I have marked this report as important as people creating Debian CDs
find this functionality useful.  I have not tested the patch myself
but it does compile and I didn't change any of the code (except
indentation, to match the current style) from the mkhybrid .diff.gz.

*** mkisofs-tree.diff
diff -urN cdrecord-1.9-official/debian/control cdrecord-1.9/debian/control
--- cdrecord-1.9-official/debian/controlSun Feb 11 17:41:27 2001
+++ cdrecord-1.9/debian/control Sun Feb 11 22:23:19 2001
@@ -18,13 +18,17 @@
 Package: mkisofs
 Architecture: any
 Depends: ${shlibs:Depends}
+Provides: mkhybrid
+Replaces: mkhybrid
+Conflicts: mkhybrid
 Suggests: cdrecord
 Section: otherosfs
 Description: Creates ISO-9660 CD-ROM filesystem images.
  mkisofs is a pre-mastering program for creating ISO-9660 CD-ROM 
  filesystem images, which can then be written to a CD-ROM using the 
  cdrecord program.  mkisofs now includes support for making bootable 
- "El Torito" CD-ROMs.
+ "El Torito" CD-ROMs, as well as CD-ROMs with support for the
+ Macintosh HFS filesystem (as in the old "mkhybrid" package).
 
 Package: cdda2wav
 Architecture: any
diff -urN cdrecord-1.9-official/debian/mkisofs.files cdrecord-1.9/debian/mkisofs.files
--- cdrecord-1.9-official/debian/mkisofs.files  Sun Feb 11 17:41:27 2001
+++ cdrecord-1.9/debian/mkisofs.files   Sun Feb 11 22:24:02 2001
@@ -4,4 +4,5 @@
 usr/bin/isodump
 usr/bin/isovfy
 usr/share/man/man8/mkisofs.8
+usr/share/man/man8/mkhybrid.8
 usr/share/man/man8/isoinfo.8
diff -urN cdrecord-1.9-official/mkisofs/mkisofs.8 cdrecord-1.9/mkisofs/mkisofs.8
--- cdrecord-1.9-official/mkisofs/mkisofs.8 Thu Jul 20 11:29:10 2000
+++ cdrecord-1.9/mkisofs/mkisofs.8  Sun Feb 11 22:02:31 2001
@@ -93,6 +93,10 @@
 .B \-f
 ]
 [
+.B \-F
+.I root_directory
+]
+[
 .B \-d
 ]
 [
@@ -709,6 +713,12 @@
 in use, symbolic links will be entered using Rock Ridge if enabled, otherwise
 the file will be ignored.
 .TP
+.BI \-F " root_directory
+Follow symbolic links which point outside specified
+.I root_directory 
+when generating the filesystem.  This allows a symlink farm structure,
+where symlinks inside the base directory stay symlinks, but symlinks
+outside the base directory become real files on the CD.
 .B \-gui
 Switch the behaviour for a GUI. This currently makes the output more verbose
 but may have other effects in future.
diff -urN cdrecord-1.9-official/mkisofs/mkisofs.c cdrecord-1.9/mkisofs/mkisofs.c
--- cdrecord-1.9-official/mkisofs/mkisofs.c Thu Jul 20 11:31:17 2000
+++ cdrecord-1.9/mkisofs/mkisofs.c  Sun Feb 11 22:07:05 2001
@@ -111,6 +111,7 @@
 intgui = 0;
 intall_files = 1;  /* New default is to include all files */
 intfollow_links = 0;
+intfollow_links_sensible = 0;
 intrationalize = 0;
 intgenerate_tables = 0;
 intdopad = 0;
@@ -130,6 +131,7 @@
 char   *boot_catalog = BOOT_CATALOG_DEFAULT;
 char   *boot_image = BOOT_IMAGE_DEFAULT;
 char   *genboot_image = BOOT_IMAGE_DEFAULT;
+char   follow_links_base[PATH_MAX];
 intucs_level = 3;  /* We now have Unicode tables so use level 3 */
 intvolume_set_size = 1;
 intvolume_sequence_number = 1;
@@ -383,6 +385,8 @@
'D', NULL, "Disable deep directory relocation (violates ISO9660)", ONE_DASH},
{{"follow-links", no_argument, NULL, 'f'},
'f', NULL, "Follow symbolic links", ONE_DASH},
+   {{"follow-outside-links", required_argument, NULL, 'F'},
+   'F', NULL, "Follow symbolic links which point outside the CD base directory", 
+ONE_DASH },
{{"graft-points", no_argument, NULL, OPTION_USE_GRAFT},
'\0', NULL, "Allow to use graft points for filenames", ONE_DASH},
{{"help", no_argument, NULL, OPTION_HELP},
@@ -1017,7 +1021,7 @@
int hfs_ct = 0;
char*root_info = 0;
 #endif /* APPLE_HYB */
-
+   charold_dir[PATH_MAX];
 
 #ifdef __EMX__
/* This gives wildcard expansion with Non-Posix shells with EMX */
@@ -1274,6 +1278,20 @@
break;
case 'f':
follow_links++;
+   break;
+   case 'F':
+   follow_links_sensible++;
+   if(getcwd (old_dir, PATH_MAX)) {
+   chdir (optarg);
+   if(!getcwd (follow_links_base, PATH_MAX)) {
+   perror("getcwd");
+   exit(1);
+   }
+   chdir (old_dir);
+   } else {
+   

Re: [lawrencc@debian.org: Please remove mkhybrid from sid, woody]

[Chris Lawrence]

On Feb 06, J.A. Bezemer wrote:
 
 #include sorry_for_the_late_reply.h
 #include i_was_just_far_too_busy.h
 
 On 28 Jan 2001, Adam Di Carlo wrote:
 
  Chris Lawrence [EMAIL PROTECTED] writes:
  
   I have requested that mkhybrid be removed from sid and woody, so
   mkisofs can "take over" the package.  Let me know if you need the
   symlink tree patch or anything.  The report is #83823
 
 The "official" procedure to make Debian CDs (i.e. with hardlinks) works well
 with mkisofs. However there probably also are people using a symlink farm,
 which requires mkhybrid's -F option ("-follow-outside-links   Follow symbolic
 links which point outside the CD base directory"). AFAICS this option is not
 available in mkisofs 1.13, so it seems mkisofs does _not_ incorporate all of
 the features of mkhybrid. 

Yeah, -F is sort of an issue.  I'll try to get a clean patch and
forward it to the mkisofs maintainer.


Chris
-- 
Chris Lawrence [EMAIL PROTECTED] -  http://www.lordsutch.com/chris/

Computer Systems Manager (Physics  Astronomy, 125 Lewis, 662-915-5765)
Instructor, POL 101  (Political Science, 208 Deupree, 662-915-5949)


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