Re: Is it wise to use discover in d-i?
* Thorsten Sauter | Coudn't we use the RedHat discovering tool? I thing it's better under | development and support more hardware (RedHat needs to extend the | supported haradware everytime) IIRC, kudzu's library is a lot larger than discover, so we'd need a second floppy for i386, which would really suck. I might remember wrong, though. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: daily d-i builds
* Matt Kraai | On Wed, Mar 19, 2003 at 03:55:14PM -0500, Joe Nahmias wrote: | It seems that the daily d-i builds aren't so daily: | | According to the build log[1], there is something wrong with the | Makefile: | | Makefile:224: *** missing separator. Stop. it has been fixed now; I had a conflict in my Makefile. I might miss mails to -boot, though it's one of the lists I try to read closely, so mailing me privately or mentioning it on IRC is a faster and more reliable way to get my attention on such matters as this. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: net image full
On Wed, Apr 02, 2003 at 03:04:10PM -0700, Erik Andersen wrote: I just did a bit of testing, and the script actually works this time. :) you forget that we want to use cvs busybox which contains an udhcpc with mask support. bastian -- Warp 7 -- It's a law we can live with. pgp0.pgp Description: PGP signature
Re: net image full
#!/bin/sh # udhcpc script using iproute by Erik Andersen [EMAIL PROTECTED] [ -z $1 ] echo Error: should be called from udhcpc exit 1 RESOLV_CONF=/etc/resolv.conf case $1 in deconfig) /bin/ip link set $interface up ;; renew|bound) /bin/ip addr flush dev $interface /bin/ip addr add $ip/$mask dev $interface if [ -n $router ] ; then /bin/ip route flush match 0 dev $interface for i in $router ; do /bin/ip route add default via $i dev $interface done fi if [ -n $hostname ]; then hostname $hostname fi echo # Generated automatically by udhcpc $RESOLV_CONF echo $RESOLV_CONF if [ -n $domain ] ; then echo search $domain $RESOLV_CONF fi for i in $dns ; do echo nameserver $i $RESOLV_CONF done ;; esac exit 0 -- It is necessary to have purpose. -- Alice #1, I, Mudd, stardate 4513.3 pgp0.pgp Description: PGP signature
boot problems with asus cuv266-d mainboard
Hello Linux-Support, I have several problems to install Linux on my computer. I have tested the distributions Debian Woody, Suse 8.1 and Knoppix 3.1 on my computer using any possibility of hardware configuration. Following I discribe all of my computer components: motherboard: ASUS CUV266-D DUAL Pentium III 1000 Mhz, chipset VIA Appollo Pro266 North Bridge VIA VT8633 South Bridge VIA VT8233 memory: 512 MB DDR266 graphic card: ASUS V8200 Pure GeForce 3 sound card: Terratec DMX XFire 1024 controller card: 1. Promise Ultra100 TX2 2. HighPoint Rocket133 HDD: 1. 40 GB Seagate 340824A U100 2. 40 GB Seagate 340016A U133 3. 80 GB Maxtor 4R080L0 U133 Zip: Iomega ZIP 250 MB CD-Burner: Sony CD-RW CRX175E2 DVD-ROM: Pioneer DVD-116 screen: EIZO F730, 19 Perhaps some hardware components are not supported by any of that distributions. I have searched on many internet pages and hardware data bases to solve my problem, but I still did not find any solution. I guess that my motherboard is not supported, because the tests with a minimum hardware configuration (motherboard, graphic card, 1.HDD, CD-Burner, no other cards or controller) fails also. Following I discribe the problems: Suse 8.1: There was no problem to install Linux from the bootable CD, but the system was not able to reboot from HDD after installation. It stops then it wants to detect my HDD or may be the IDE-Controller of the motherboard. (sorry, that I'm not able to give concret information I'm a total Linux-beginner and the Linux start up is very cryptical for me). I also tested several boot parameters like nodma, failsafe ... but without any effect the system stops. But I'm able to boot from CD to get access to the installed system as root in kde.(curious??!!??). Debian Woody: Here was also no problem to install Linux from bootable CD. The system reboots after installation properly, but with some failure messages with grahic card and/or screen detection. But I was able to get login as root so I started to find the problem in the system and a solution in the documentation of Debian Woody. But I was not able to install or configure Xfree86 or any of the windowmanager (xdm, gdm, kdm). So I got no GUI. That is the result of the installation with the compact kernel. All installations of the other kernels failed. Knoppix 3.1: The bootable CD starts and shows me the boot promt to enter any parameters, but whether I do so or not the system fades to black screen and stops, sometimes I see the Tux picture but nevertheless the system stops. Please give me any help. Whether my components are supported by any of your mentioned distribution (or higher versions) or any other distributions which I have not tested yet or which components are not supported. Please answer in german (preferential) or english. Yours sincerely André [EMAIL PROTECTED] or [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot problems with asus cuv266-d mainboard
Il gio, 2003-04-03 alle 15:18, kpn ha scritto: Hello Linux-Support, I have several problems to install Linux on my computer. I have tested the distributions Debian Woody, Suse 8.1 and Knoppix 3.1 on my computer using any possibility of hardware configuration. Following I discribe all of my computer components: motherboard: ASUS CUV266-D DUAL Pentium III 1000 Mhz, chipset VIA Appollo Pro266 North Bridge VIA VT8633 South Bridge VIA VT8233 memory: 512 MB DDR266 graphic card: ASUS V8200 Pure GeForce 3 sound card: Terratec DMX XFire 1024 ... Debian Woody: Here was also no problem to install Linux from bootable CD. The system reboots after installation properly, but with some failure messages with grahic card and/or screen detection. But I was able to get login as root so I started to find the problem in the system and a solution in the documentation of Debian Woody. But I was not able to install or configure Xfree86 or any of the windowmanager (xdm, gdm, kdm). So I got no GUI. That is the result of the installation with the compact kernel. All installations of the other kernels failed. I would suggest to install a 2.4 kernel in order to have the AGP support (kernel module agpgart) and then install XFree using the VESA driver. Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ethdetect - module name mismatch
Martin Sjögren [EMAIL PROTECTED] writes: ons 2003-04-02 klockan 11.55 skrev [EMAIL PROTECTED]: Hi, I'm trying to install with gluck.debian.org/cdimage/testing/netinst/i386/sarge-i386-netinst.iso as of 01/04 on ia32. My ethernet card is detected correctly as RTL8139. The installer attempts to load rtl8139 module however there is no module rtl8139 under /lib/modules (modprobe -v rtl8139, Can't locate module rtl8139). 8139too should be used instead. Yes, this is because discover 1.x doesn't support 2.4 kernels. This will be fixed when we migrate to discover 2.x. Thanks for explanation. I've noticed that choosing the module from list and loading it without autodetection works only for the net but not for the cdrom install. Giving full path to the module fails too (for the default boot arg). The listing in Load installer modules is not paged properly or the paging style is confusing. I could not list entries 1-6. I tried to select them by number or navigate back and forth by letters n,b. One line is skipped if Enter is pressed. The real problem is when it comes to Install the base system (default) nothing is installed - pressing Enter presents the same menu again. I believe all previous items (language/net hardware/keyboard/DHCP config/choosing mirror/CDROM/installer modules/partitioning/mounting filesystems) were completed. Any idea how to proceed? cheers Jiri -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Caburique sasko Debianboot INSURANCE? Debianboot
Debianboot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot problems with asus cuv266-d mainboard
In the BIOS setup, change MPS to 1.1 instead of 1.4. Xavier On Thu, 3 Apr 2003, kpn wrote: Hello Linux-Support, I have several problems to install Linux on my computer. I have tested the distributions Debian Woody, Suse 8.1 and Knoppix 3.1 on my computer using any possibility of hardware configuration. Following I discribe all of my computer components: motherboard: ASUS CUV266-D DUAL Pentium III 1000 Mhz, chipset VIA Appollo Pro266 North Bridge VIA VT8633 South Bridge VIA VT8233 memory: 512 MB DDR266 graphic card: ASUS V8200 Pure GeForce 3 sound card: Terratec DMX XFire 1024 controller card: 1. Promise Ultra100 TX2 2. HighPoint Rocket133 HDD: 1. 40 GB Seagate 340824A U100 2. 40 GB Seagate 340016A U133 3. 80 GB Maxtor 4R080L0 U133 Zip: Iomega ZIP 250 MB CD-Burner: Sony CD-RW CRX175E2 DVD-ROM: Pioneer DVD-116 screen: EIZO F730, 19 Perhaps some hardware components are not supported by any of that distributions. I have searched on many internet pages and hardware data bases to solve my problem, but I still did not find any solution. I guess that my motherboard is not supported, because the tests with a minimum hardware configuration (motherboard, graphic card, 1.HDD, CD-Burner, no other cards or controller) fails also. Following I discribe the problems: Suse 8.1: There was no problem to install Linux from the bootable CD, but the system was not able to reboot from HDD after installation. It stops then it wants to detect my HDD or may be the IDE-Controller of the motherboard. (sorry, that I'm not able to give concret information I'm a total Linux-beginner and the Linux start up is very cryptical for me). I also tested several boot parameters like nodma, failsafe ... but without any effect the system stops. But I'm able to boot from CD to get access to the installed system as root in kde.(curious??!!??). Debian Woody: Here was also no problem to install Linux from bootable CD. The system reboots after installation properly, but with some failure messages with grahic card and/or screen detection. But I was able to get login as root so I started to find the problem in the system and a solution in the documentation of Debian Woody. But I was not able to install or configure Xfree86 or any of the windowmanager (xdm, gdm, kdm). So I got no GUI. That is the result of the installation with the compact kernel. All installations of the other kernels failed. Knoppix 3.1: The bootable CD starts and shows me the boot promt to enter any parameters, but whether I do so or not the system fades to black screen and stops, sometimes I see the Tux picture but nevertheless the system stops. Please give me any help. Whether my components are supported by any of your mentioned distribution (or higher versions) or any other distributions which I have not tested yet or which components are not supported. Please answer in german (preferential) or english. Yours sincerely André [EMAIL PROTECTED] or [EMAIL PROTECTED] -- 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]
would you like to feel better cc emlsmmk
rsgdxgdihc y n t mbu
Processing of build-installer_0.0.001_i386.changes
build-installer_0.0.001_i386.changes uploaded successfully to localhost along with the files: build-installer_0.0.001.dsc build-installer_0.0.001.tar.gz debian-installer-i386_0.0.001_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
build-installer_0.0.001_i386.changes REJECTED
Rejected: debian-installer-i386_0.0.001_all.deb: architecture part of filename (all) does not match package architecture in the deb (i386). === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Stages
On Sun, Mar 30, 2003 at 12:16:44PM +0200, Martin Sj?gren wrote: sön 2003-03-30 klockan 11.49 skrev Alastair McKinstry: chroot is used in a bunch of code - the lilo, grub code etc install lilo on /target then run chroot /target /sbin/lilo similarly for a lot of prebaseconfig stuff. It could be removed from the initial floppy, however. Exactly, that'd be in the stage1 udeb (stage0 being everything up until anna runs, stage1 being the rest of d-i and stage2 being base-config, in my terminology) The definition of 'Stages' is not yet in the d-i documentation. Below is a proposal to patch it against design.txt Beware, I'm trying two fix two things at one time: Defining Stages and enforcing a single boot image ( kernel + initrd ) disk diff -u -r1.6 design.txt --- doc/design.txt 18 Sep 2002 16:24:45 - 1.6 +++ doc/design.txt 3 Apr 2003 18:00:12 - @@ -2,6 +2,7 @@ 1. initial boot off of install media (floppy, cd) - Syslinux (or other loader) is run, and it boots the kernel + (Stage0) 2. kernel boot - The kernel sets up an initrd, runs the installer. 3. installer @@ -9,11 +10,19 @@ initrd), and chooses one of them. - Starts up and configures the UI. - Configures enough so that some udebs can be retrieved. + (Stage1) 3.5 Main installer - Main menu runs (see ui.txt). + (Stage2) 4. reboot into a full debian system - Since the system was installed with a minimal kernel that cannot talk to the hard drive, an initrd must be used. The initrd has a syslinux file on it, and a set of modules. It just loads the modules, in a certain order, with certain parameters, and then lets the kernel pass control to init. - Set up all packages that need to be set up (timezone, password, etc, etc). + + + Stage0: being everything up until anna runs + which fits on a single 1.44M diskette + Stage1: being the rest of Debian Installer + Stage2: being base-config Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: net image full
On Thu Apr 03, 2003 at 02:49:09PM +0200, Bastian Blank wrote: On Wed, Apr 02, 2003 at 03:04:10PM -0700, Erik Andersen wrote: I just did a bit of testing, and the script actually works this time. :) you forget that we want to use cvs busybox which contains an udhcpc with mask support. True, with CVS we can skip using sed to chomp the whitespace, and we can skip the bitmask determination stuff as well. -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- pgp0.pgp Description: PGP signature
Re: Making d-i Not Suck
On Sun, Mar 30, 2003 at 06:50:11PM +0100, Alastair McKinstry wrote:
On Fri, 2003-03-28 at 12:52, Geert Stappers wrote:
Similarly a possible terminfo-udeb, for remote installs; we currently
build a subset (ansi,vt100, ..) of terminfo data on the rootskel;
suboptimal if you are remote-installing on a different terminal. Imagine
a terminfo-udeb; if [something] spots TERM that is not supported, it
should request a terminfo-udeb, and automatically fix it.
Supporting other terminals then ansi and vt100 can indeed be done in d-i.
However IMHO it doesn't make sense.
Most terminalprogramms can easy be configured to emulate an other terminal.
Or when not, then take another terminal programm at the non d-i side.
Yes, it can, but I gave it as an example; its cosmetic. (A better
example of a real use was given, pulling in the right console fonts).
If someone is installing debian remotely from an eg DECterm, they
shouldnt have to change TERM=vt100, or whatever. For the most part, how
it would work, would be eg in the S390 case (*) (see other thread; on
S390 there is no local console; you boot and then login via telnet).
The user logs in via telnet, which passes the TERM value.
if the TERM!={ansi,vt100,linux}, then terminfo-udeb is loaded, and the
terminfo data installed, and installation continues more beautifully.
Formatting screen output with terminfo data
is an other kind of problem then a floppy disk image that has to provide
an driver for the next driver such as harddisk driver or NIC driver.
I can't parse this; do you mean its different than the driver loading
problems; if so, yes, I agree; they are critical, this is cosmetic.
Yes, my worries are about critical items like driver loading.
These issues _must_ be solved at install target side.
Choosing a terminal screen protocol that both side understand,
is an issue that _can_ be solved at install target side.
I agree that missing functionality ( disk driver or screen formatting )
can be loaded in an universal way.
So take a different approach to handle it.
Not so smart.
So give different priorities to handle them.
(*) Actually, it may be useful in other cases too. See the netconsole
project, that aims to provide an ethernet console (simple TCP/IP stack
telnet login) or, I believe the Axis Communications Linux SoCs, which
provide an ethernet (telnet) login. In these cases, the telnet protocol
would be used for remote installation, rather than a serial console; and
so telnetd would be useful, and the terminfo issue would occur.
Yes, telnetd has benefits. I hope it stays in d-i
Geert Stappers
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Processing of build-installer_0.0.001_i386.changes
On Thu, Apr 03, 2003 at 01:25:16PM -0500, Archive Administrator wrote: build-installer_0.0.001_i386.changes uploaded successfully to localhost along with the files: build-installer_0.0.001.dsc build-installer_0.0.001.tar.gz debian-installer-i386_0.0.001_all.deb I should had ask this before: Why is there i386, an architecture, in an all package? Greetings, Your Debian queue daemon Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Stages
tor 2003-04-03 klockan 20.54 skrev Geert Stappers: On Sun, Mar 30, 2003 at 12:16:44PM +0200, Martin Sj?gren wrote: sön 2003-03-30 klockan 11.49 skrev Alastair McKinstry: chroot is used in a bunch of code - the lilo, grub code etc install lilo on /target then run chroot /target /sbin/lilo similarly for a lot of prebaseconfig stuff. It could be removed from the initial floppy, however. Exactly, that'd be in the stage1 udeb (stage0 being everything up until anna runs, stage1 being the rest of d-i and stage2 being base-config, in my terminology) The definition of 'Stages' is not yet in the d-i documentation. That's because it's my own personal rule of thumb. Stage0 starts when the main menu is shown, and lasts until after anna has been run, then it's Stage1. Stage2 starts after the reboot. So the patch doesn't exactly match my view of d-i, but it's a start. /M -- Martin Sjögren [EMAIL PROTECTED] -- [EMAIL PROTECTED] GPG key: http://www.mdstud.chalmers.se/~md9ms/gpg.html let hello = hello : hello in putStr (unlines hello) signature.asc Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signeradmeddelandedel
Improve sexual stamina.
p Are you starting to show signs of aging? p Could you afford to lose a little weight? p As seen on TV. This is the product everyone is talking about. p a href=http://www.mnjmtech.us/hgh4/home.html;PUSH THIS/a /p zojpiuki ddbcmtcrg sjsyms
Bug#172828: mklibs : problem on mips
Hi, I'm writing to you as the authors of mklibs I'm trying to debug a problem on mips / mipsel, using mklibs to reduce the debian-installer. (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=172828 for details) The bug manifests itself as a set of symbols, in libc.so.6 on mips, that aren't resolved properly, causing the mklibs step to loop, failing to resolve these symbols. The symbols are: Still need: _pthread_cleanup_pop_restore Still need: __pthread_mutexattr_init Still need: __pthread_mutexattr_destroy Still need: __pthread_mutexattr_settype Still need: __pthread_mutex_trylock Still need: _pthread_cleanup_push_defer Still need: __pthread_mutex_init Still need: __pthread_mutex_unlock Still need: __pthread_mutex_lock They are found in libc. Now, in i386, for example, they are of type: eg. NOTYPE WEAK DEFAULT UND _pthread_cleanup_pop_restore But on MIPs, they are all: [EMAIL PROTECTED]:/lib$ readelf -s -W libc.so.6 | grep WEAK | grep UND | grep FUNC 2023: 0 FUNCWEAK DEFAULT UND _pthread_cleanup_push_defer 2024: 000146f0 0 FUNCWEAK DEFAULT UND __pthread_mutexattr_init 2053: 0 FUNCWEAK DEFAULT UND __pthread_mutex_trylock 2059: 0 FUNCWEAK DEFAULT UND __pthread_mutex_unlock 2085: 000146e0 0 FUNCWEAK DEFAULT UND _pthread_cleanup_pop_restore 2101: 0 FUNCWEAK DEFAULT UND __pthread_mutex_init 2118: 000146d0 0 FUNCWEAK DEFAULT UND __pthread_mutexattr_settype 2129: 0 FUNCWEAK DEFAULT UND __pthread_mutex_lock 2133: 000146c0 0 FUNCWEAK DEFAULT UND __pthread_mutexattr_destroy I believe this means they are all weak objects, not normally marked as such. They will resolve to zero if not found elsewhere, but undefined_symbols() in mklibs treats them simply as undefined. Is my analysis correct? Can you provide a patch for mklibs ? (I'm not confident enough either of my understanding or python to risk doing it myself. ) This is needed to make the Debian installer build on MIPs and MIPSEL. Thanks, Alastair McKinstry -- Alastair McKinstry [EMAIL PROTECTED] GPG Key fingerprint = 9E64 E714 8E08 81F9 F3DC 1020 FA8E 3790 9051 38F4 He that would make his own liberty secure must guard even his enemy from oppression; for if he violates this duty he establishes a precedent that will reach to himself. - --Thomas Paine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of build-installer_0.0.001_i386.changes
build-installer_0.0.001_i386.changes uploaded successfully to localhost along with the files: build-installer_0.0.001.dsc build-installer_0.0.001.tar.gz debian-installer-i386_0.0.001_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
build-installer_0.0.001_i386.changes REJECTED
Rejected: debian-installer-i386_0.0.001_all.deb: architecture part of filename (all) does not match package architecture in the deb (i386). === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#172828: mklibs : problem on mips
Alastair McKinstry [EMAIL PROTECTED] writes: I'm writing to you as the authors of mklibs Damn. Why does everybody think I know how mklibs works just because I wrote it? ;) Seriously, I just stole most stuff from existing scripts, I'm not really an expert on dynamic linking... They are found in libc. Now, in i386, for example, they are of type: eg. NOTYPE WEAK DEFAULT UND _pthread_cleanup_pop_restore But on MIPs, they are all: [EMAIL PROTECTED]:/lib$ readelf -s -W libc.so.6 | grep WEAK | grep UND | grep FUNC 2023: 0 FUNCWEAK DEFAULT UND _pthread_cleanup_push_defer I believe this means they are all weak objects, not normally marked as such. They will resolve to zero if not found elsewhere, but undefined_symbols() in mklibs treats them simply as undefined. I am not quite sure about how to handle weak symbols properly. If they are provided somewhere, we would usually want them to be used. So just ignoring all weak symbols doesn't seem proper. The best way seems to be to check whether the set of unresolved symbols didn't change since the last pass, and if so, whether it consists of only weak symbols. If so, just leave them undefined and quit. Otherwise abort (better than looping infinitely). Does that sound sensible? I'm a bit short on time currently, I'll see whether I can make a patch the next few days. -- Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of build-installer_0.0.001_i386.changes
build-installer_0.0.001_i386.changes uploaded successfully to localhost along with the files: build-installer_0.0.001.dsc build-installer_0.0.001.tar.gz debian-installer-i386_0.0.001_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
build-installer_0.0.001_i386.changes is NEW
(new) build-installer_0.0.001.dsc extra devel (new) build-installer_0.0.001.tar.gz extra devel (new) debian-installer-i386_0.0.001_all.deb extra devel Debian Installer floppies and network images Used for CD, floppy and network installs. Changes: build-installer (0.0.001) unstable; urgency=low . * Initial release. Announcing to [EMAIL PROTECTED] Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot problems with asus cuv266-d mainboard
On Thu, Apr 03, 2003 at 04:19:38PM +0200, Geert Stappers wrote: This mailing list is about development the set of programs that does the installation ( hardware detect, disk partitioning, copying programs from install media to hard disk, create first user ) True, but since this is the go-to list as designated in the install manual, it's cool to just refer people to debian-x, debian-user, debian-kde as appropriate. It's always good for new users to learn what great resources we have at lists.debian.org. People often don't understand where the installer leaves off and the rest of Debian begins, because we've made it a pretty smooth transition in the manual and with base-config. -- http://Www.TruthAboutWar.org Chris Tillman - Linux Rox - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
