Re: Sarge r7 CDs released
On Mon, Jan 21, 2008 at 08:12:11PM +0100, Jens Franik wrote: >Guten Tag Mattias Wadenstein, > >am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: > http://cdimage.debian.org/cdimage/archive/3.1_r7/ > >> They are now authorized on the tracker > >I put on my seeding this images: > >debian-31r7-i386-binary-1.iso >debian-31r7-i386-binary-2.iso >debian-31r7-i386-businesscard.iso >debian-31r7-i386-netinst.iso >debian-update-3.1r7-i386-DVD-1.iso > >But the only item, which has been downloaded until now is >the Update-i386-DVD with 1,26 Mb - nothing more. > >I guess nobody really needs them :-) Yup. Oldstable point releases are like that. There tends to be rather more interest in new major stable releases, as you might imagine. :-) -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Is there anybody out there? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Tuesday 22 January 2008, Steve McIntyre wrote: > On Mon, Jan 21, 2008 at 08:12:11PM +0100, Jens Franik wrote: > >Guten Tag Mattias Wadenstein, > > > >am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: > >But the only item, which has been downloaded until now is > >the Update-i386-DVD with 1,26 Mb - nothing more. > > > >I guess nobody really needs them :-) > > Yup. Oldstable point releases are like that. There tends to be rather > more interest in new major stable releases, as you might imagine. :-) How about just removing the directory for bittorent and any links to it for oldstable? If we cannot seed the images and they unlikely to get seeded much by others, should we really offer bittorent at all? Wouldn't it be better to just offer jigdo and the ISOs and be done with it? Cheers, FJP signature.asc Description: This is a digitally signed message part.
Re: Sarge r7 CDs released
On Tue, Jan 22, 2008 at 12:23:48PM +0100, Frans Pop wrote: >On Tuesday 22 January 2008, Steve McIntyre wrote: >> On Mon, Jan 21, 2008 at 08:12:11PM +0100, Jens Franik wrote: >> >Guten Tag Mattias Wadenstein, >> > >> >am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: >> >But the only item, which has been downloaded until now is >> >the Update-i386-DVD with 1,26 Mb - nothing more. >> > >> >I guess nobody really needs them :-) >> >> Yup. Oldstable point releases are like that. There tends to be rather >> more interest in new major stable releases, as you might imagine. :-) > >How about just removing the directory for bittorent and any links to it for >oldstable? If we cannot seed the images and they unlikely to get seeded >much by others, should we really offer bittorent at all? > >Wouldn't it be better to just offer jigdo and the ISOs and be done with it? Yup, I guess so. We should be able to handle the ISO/jigdo downloads directly from cdimage; bittorent is just adding overhead if there aren't a lot of users. Maswan - you may as well kill the bt stuff. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] "I've only once written 'SQL is my bitch' in a comment. But that code is in use on a military site..." -- Simon Booth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Tuesday 22 January 2008, Steve McIntyre wrote: > >How about just removing the directory for bittorent and any links to it > > for oldstable? If we cannot seed the images and they unlikely to get > > seeded much by others, should we really offer bittorent at all? > > > >Wouldn't it be better to just offer jigdo and the ISOs and be done with > > it? > > Yup, I guess so. We should be able to handle the ISO/jigdo downloads > directly from cdimage; bittorent is just adding overhead if there > aren't a lot of users. Maswan - you may as well kill the bt stuff. OK. I'll remove the links from http://www.debian.org/releases/sarge/debian-installer/ Who will remove the relevant directories from the mirrors: http://cdimage.debian.org/cdimage/archive/3.1_r7/*/bt-*/ ? (And probably also for older oldstable releases?) signature.asc Description: This is a digitally signed message part.
Re: Sarge r7 CDs released
On Tue, 22 Jan 2008, Frans Pop wrote: On Tuesday 22 January 2008, Steve McIntyre wrote: On Mon, Jan 21, 2008 at 08:12:11PM +0100, Jens Franik wrote: Guten Tag Mattias Wadenstein, am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: But the only item, which has been downloaded until now is the Update-i386-DVD with 1,26 Mb - nothing more. I guess nobody really needs them :-) Yup. Oldstable point releases are like that. There tends to be rather more interest in new major stable releases, as you might imagine. :-) How about just removing the directory for bittorent and any links to it for oldstable? If we cannot seed the images and they unlikely to get seeded much by others, should we really offer bittorent at all? Wouldn't it be better to just offer jigdo and the ISOs and be done with it? An alternative, that I've been thinking that we should include in the torrents is: http://getright.com/seedtorrent.html But it requires some changes in how torrents are currently generated (either switch of generating software or some python hacking). /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Tue, Jan 22, 2008 at 12:50:13PM +0100, Frans Pop wrote: >On Tuesday 22 January 2008, Steve McIntyre wrote: >> >How about just removing the directory for bittorent and any links to it >> > for oldstable? If we cannot seed the images and they unlikely to get >> > seeded much by others, should we really offer bittorent at all? >> > >> >Wouldn't it be better to just offer jigdo and the ISOs and be done with >> > it? >> >> Yup, I guess so. We should be able to handle the ISO/jigdo downloads >> directly from cdimage; bittorent is just adding overhead if there >> aren't a lot of users. Maswan - you may as well kill the bt stuff. > >OK. I'll remove the links from >http://www.debian.org/releases/sarge/debian-installer/ > >Who will remove the relevant directories from the mirrors: >http://cdimage.debian.org/cdimage/archive/3.1_r7/*/bt-*/ ? > >(And probably also for older oldstable releases?) I'll clean up all the bt-* directories in the central archive/ directory, but I just want to check with maswan that that won't cause any problems for him. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] "I can't ever sleep on planes ... call it irrational if you like, but I'm afraid I'll miss my stop" -- Vivek Dasmohapatra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Tue, 22 Jan 2008, Steve McIntyre wrote: On Tue, Jan 22, 2008 at 12:50:13PM +0100, Frans Pop wrote: On Tuesday 22 January 2008, Steve McIntyre wrote: How about just removing the directory for bittorent and any links to it for oldstable? If we cannot seed the images and they unlikely to get seeded much by others, should we really offer bittorent at all? Wouldn't it be better to just offer jigdo and the ISOs and be done with it? Yup, I guess so. We should be able to handle the ISO/jigdo downloads directly from cdimage; bittorent is just adding overhead if there aren't a lot of users. Maswan - you may as well kill the bt stuff. OK. I'll remove the links from http://www.debian.org/releases/sarge/debian-installer/ Who will remove the relevant directories from the mirrors: http://cdimage.debian.org/cdimage/archive/3.1_r7/*/bt-*/ ? (And probably also for older oldstable releases?) I'll clean up all the bt-* directories in the central archive/ directory, but I just want to check with maswan that that won't cause any problems for him. Nope, no problems, go ahead and clean it up unless you want to keep it for historical reasons. /Mattias Wadenstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Tuesday 22 January 2008, Mattias Wadenstein wrote: > An alternative, that I've been thinking that we should include in the > torrents is: http://getright.com/seedtorrent.html > > But it requires some changes in how torrents are currently generated > (either switch of generating software or some python hacking). Won't that still cause a big burden on the server? The main issue here is that it is quite unlikely that anybody else will actually be seeding these images, so almost any bittorent download will effectively result in the iso being downloaded from the main server anyway (if I understand text at getright.com correctly after quick read). I just see that the sarge/d-i page currently [1] does not even have direct links to the jigdo images, only to the iso's and bittorents. I've got a patch ready to _replace_ the bittorent links with jigdo links, but will wait with commit until this discussion is finished. [1] http://www.debian.org/releases/sarge/debian-installer/ signature.asc Description: This is a digitally signed message part.
Re: Sarge r7 CDs released
On Tue, Jan 22, 2008 at 01:00:14PM +0100, Mattias Wadenstein wrote: >On Tue, 22 Jan 2008, Steve McIntyre wrote: > >>On Tue, Jan 22, 2008 at 12:50:13PM +0100, Frans Pop wrote: >>>On Tuesday 22 January 2008, Steve McIntyre wrote: >How about just removing the directory for bittorent and any links to it >for oldstable? If we cannot seed the images and they unlikely to get >seeded much by others, should we really offer bittorent at all? > >Wouldn't it be better to just offer jigdo and the ISOs and be done with >it? Yup, I guess so. We should be able to handle the ISO/jigdo downloads directly from cdimage; bittorent is just adding overhead if there aren't a lot of users. Maswan - you may as well kill the bt stuff. >>> >>>OK. I'll remove the links from >>>http://www.debian.org/releases/sarge/debian-installer/ >>> >>>Who will remove the relevant directories from the mirrors: >>>http://cdimage.debian.org/cdimage/archive/3.1_r7/*/bt-*/ ? >>> >>>(And probably also for older oldstable releases?) >> >>I'll clean up all the bt-* directories in the central archive/ >>directory, but I just want to check with maswan that that won't cause >>any problems for him. > >Nope, no problems, go ahead and clean it up unless you want to keep it >for historical reasons. Gone. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Mature Sporty Personal More Innovation More Adult A Man in Dandism Powered Midship Specialty -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Tue, Jan 22, 2008 at 01:09:24PM +0100, Frans Pop wrote: >On Tuesday 22 January 2008, Mattias Wadenstein wrote: >> An alternative, that I've been thinking that we should include in the >> torrents is: http://getright.com/seedtorrent.html >> >> But it requires some changes in how torrents are currently generated >> (either switch of generating software or some python hacking). > >Won't that still cause a big burden on the server? >The main issue here is that it is quite unlikely that anybody else will >actually be seeding these images, so almost any bittorent download will >effectively result in the iso being downloaded from the main server anyway >(if I understand text at getright.com correctly after quick read). > > >I just see that the sarge/d-i page currently [1] does not even have direct >links to the jigdo images, only to the iso's and bittorents. >I've got a patch ready to _replace_ the bittorent links with jigdo links, >but will wait with commit until this discussion is finished. Go for it. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] "I suspect most samba developers are already technically insane... Of course, since many of them are Australians, you can't tell." -- Linus Torvalds -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sarge r7 CDs released
On Tue, Jan 22, 2008 at 12:34:25PM +0100, Mattias Wadenstein wrote: >On Tue, 22 Jan 2008, Frans Pop wrote: > >>On Tuesday 22 January 2008, Steve McIntyre wrote: >>>On Mon, Jan 21, 2008 at 08:12:11PM +0100, Jens Franik wrote: Guten Tag Mattias Wadenstein, am Sonntag, 20. Januar 2008 um 10:29 schriebst Du: But the only item, which has been downloaded until now is the Update-i386-DVD with 1,26 Mb - nothing more. I guess nobody really needs them :-) >>> >>>Yup. Oldstable point releases are like that. There tends to be rather >>>more interest in new major stable releases, as you might imagine. :-) >> >>How about just removing the directory for bittorent and any links to it for >>oldstable? If we cannot seed the images and they unlikely to get seeded >>much by others, should we really offer bittorent at all? >> >>Wouldn't it be better to just offer jigdo and the ISOs and be done with it? > >An alternative, that I've been thinking that we should include in the >torrents is: http://getright.com/seedtorrent.html > >But it requires some changes in how torrents are currently generated >(either switch of generating software or some python hacking). /me really needs to get jigdoofus finished. Then we'd be able to offer full ISOs and bittorrents using just the jigdo files and the mirror (for at least older images). ENOTUITS. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] "Every time you use Tcl, God kills a kitten." -- Malcolm Ray -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Custom Debian Installer CD
I was wondering if there was any good documentation or a HowTo somewhere that would help me create a custom Debian Installer CD. I basically want to use the standard debian installer, package a subset of the debs on the CD and instead of running the tasksel program at the end I would like it to automatically install a preselected set of packages and set those up. Any help on this would be appreciated. Thanks in advance. Let me know if I should be posting to a different list as well. -- o) Derek Wueppelmann (o (D . [EMAIL PROTECTED] D). ((` http://www.monkeynet.ca ( ) ` -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Custom Debian Installer CD
On Tuesday 22 January 2008, Derek Wueppelmann wrote: > I was wondering if there was any good documentation or a HowTo somewhere > that would help me create a custom Debian Installer CD. I basically want > to use the standard debian installer, package a subset of the debs on > the CD and instead of running the tasksel program at the end I would > like it to automatically install a preselected set of packages and set > those up. > > Any help on this would be appreciated. Thanks in advance. Try these links as a starter: http://alioth.debian.org/~fjp/debian-cd/ http://dzongkha.sourceforge.net/wiki/index.php/D-i pkgsel (the d-i component that calls tasksel) also has several options to install additional packages or change its behavior. You'll have to read the source for those though. Cheers, FJP signature.asc Description: This is a digitally signed message part.
Bug#462157: please bring back default64 option
Package: syslinux Severity: wishlist Tags: patch Please can you bring back default64 option so that lenny CDs can use it? Patch attached, based on the previous one. Tested with qemu/qemu-system-x86_64 and known to work. Thanks -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) diff -ur syslinux-3.55.old/cpuinit.inc syslinux-3.55/cpuinit.inc --- syslinux-3.55.old/cpuinit.inc 2008-01-11 07:39:36.0 +0100 +++ syslinux-3.55/cpuinit.inc 2008-01-22 21:38:31.0 +0100 @@ -48,12 +48,10 @@ rep movsd ; -; Check if we're 386 (as opposed to 486+); if so we need to blank out -; the WBINVD instruction +; Determine if we're running on a 64-bit CPU ; -; We check for 486 by setting EFLAGS.AC +; First, check if we're 386. If so, we need to blank out the WBINVD instruction ; -%if DO_WBINVD pushfd ; Save the good flags pushfd pop eax @@ -69,9 +67,40 @@ ; ; 386 - Looks like we better blot out the WBINVD instruction ; +%if DO_WBINVD mov byte [try_wbinvd],0c3h ; Near RET -is_486: %endif ; DO_WBINVD + jmp is_32bit +is_486: +; +; Check if this CPU supports the CPUID command +; + pushfd ; Save the flags again + pushfd + pop eax + mov ebx,eax + xor eax,(1 << 21) ; CPUID bit + push eax + popfd + pushfd + pop eax + popfd ; Restore the original flags + xor eax,ebx + jz is_32bit +; +; Now check for the 64-bit flag (bit 29) in the CPU extended features byte ($8000_0001, edx) +; + mov eax, 8000h ; Find last AMD cpuid # + cpuid + cmp eax, 8000h + jbe is_32bit + mov eax, 8001h ; Read AMD CPU flags + cpuid + bt edx, 29 ; 64-bit if bit 29 is set + jnc is_32bit + +is_64bit: mov byte [Is64Bit],1; Flag that we're 64-bit +is_32bit: section .data err_noram db 'It appears your computer has less than ' diff -ur syslinux-3.55.old/keywords syslinux-3.55/keywords --- syslinux-3.55.old/keywords 2008-01-11 07:39:36.0 +0100 +++ syslinux-3.55/keywords 2008-01-22 21:33:50.0 +0100 @@ -4,6 +4,7 @@ append config default +default64 display font implicit diff -ur syslinux-3.55.old/keywords.inc syslinux-3.55/keywords.inc --- syslinux-3.55.old/keywords.inc 2008-01-11 07:39:36.0 +0100 +++ syslinux-3.55/keywords.inc 2008-01-22 21:39:07.0 +0100 @@ -50,6 +50,7 @@ keyword include,pc_filecmd, pc_include keyword append, pc_append keyword default,pc_default + keyword default64, pc_default64 keyword display,pc_filecmd, get_msg_file keyword font, pc_filecmd, loadfont keyword implicit, pc_setint16,AllowImplicit diff -ur syslinux-3.55.old/kwdhash.gen syslinux-3.55/kwdhash.gen --- syslinux-3.55.old/kwdhash.gen 2008-01-11 07:39:41.0 +0100 +++ syslinux-3.55/kwdhash.gen 2008-01-22 21:33:50.0 +0100 @@ -4,6 +4,7 @@ hash_append equ 0xc53999a4 hash_config equ 0xc0c69547 hash_defaultequ 0xcc5159ed +hash_default64 equ 0x4567b1c5 hash_displayequ 0xd509bc40 hash_font equ 0x0032b1b4 hash_implicit equ 0xa6f50207 diff -ur syslinux-3.55.old/parseconfig.inc syslinux-3.55/parseconfig.inc --- syslinux-3.55.old/parseconfig.inc 2008-01-11 07:39:36.0 +0100 +++ syslinux-3.55/parseconfig.inc 2008-01-22 21:33:50.0 +0100 @@ -20,7 +20,20 @@ ; ; "default" command ; -pc_default:mov di,default_cmd +pc_default:cmp byte [HasDefault64],0 ; Check if we accepted 'default64' + ja pc_getline ; If so, do nothing + mov di,default_cmd + call getline + mov byte [di-1],0 ; null-terminate + ret + +; +; "default64" command +; +pc_default64: cmp byte [Is64Bit],0; Make sure cpu is 64-bit + je pc_getline + mov byte [HasDefault64],1 ; Note that we saw a default64 + mov di,default_cmd call getline mov byte [di-1],0 ; null-terminate ret @@ -431,6 +444,8 @@ SerialPort dw 0; Serial port base (or 0 for no
