work needed for woody release: rationally looking at task pkgs
I wish we would take a look at the task packages and fix them up. Anyone can help with this process, which would significantly improve the experience for new users. All you have to do is run 'tasksel' and play around with it. For extra creds, on a base-only system (debootstrap can build one for you, and you can chroot into it), install the tasks, then play around with what the task packages get installed, what is lacking, etc. I'm really just throwing this out there, because I think it's important for woody release.People should look at this, file bugs, seeks out tasks not created and create them, etc. What is a task package? I conceive of it as a simple convenience mechanism for helping avoid dselect and pick a reasonable set of packages based on a use that the user wants to make of their system In other words, 'task-c++-dev' means: I want to do C++ development on this system. It should grab the compiler, baseline libs for development, debugger and other C++ debugging aids, even an IDE (emacs is acceptable!). (Note: task-c++-dev does little of this). Remember that 'depends' is all anyone *really* cares about. Remember that tasks are primarily for new users installing the system, and only as a very far second, IMHO, to ongoing users. One of my big big problems is how little of the 5000 or 6000 packages that Debian has is covered by task packages. It's better to get too much (disk is cheap, tasks can be removed) than too little. I propose the following thorough-going changes: rename server packages to 'task-server-*' rename devel packages to 'task-devel-*' rename l10n packages to 'task-l10n-*' The purpose of this is to group like packages together in tasksel. Other stuff: Why no 'task-desktop-gnome' and 'task-desktop-kde' ? Why no 'task-web-appserver' (which could include apache, mod_perl and other commonly used stuff). None of the tasks grab in common desktop stuff which a newbie, non-hacker user would expect, such as a nice web browser, some simple productivity apps, gimp, stuff to fiddle and play with... I really have absolutely no time to work on this, so I'm just throwing it out there. I am not on debian-devel, so please CC me if you really need my thoughts... All of this is MHO. And remember again I have no real time to do anything about this -- you guys will have to pick up the slack if you want to -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ task-c++-dev - Development in C++ task-c-dev - Development in C task-cyrillic - Cyrillic environment task-database-pg - PostgreSQL database task-debian-devel - Debian package development task-debug - Debugging of C, C++, Objective C and friends task-devel-common - Development in various languages task-dialup - Dialup utilities task-dialup-isdn - Dialup utilities (ISDN) task-doc - General documentation task-dns-server - DNS Server task-fortran - Fortran development environment task-games - A selection of games task-german - German-speaking environment task-harden - Harden your system task-imap - IMAP Server task-japanese - Japanese environment task-junior - The base install for a Debian Jr. system task-newbie-help - New user documentation task-news-server - USENET News Server task-objc-dev - Development in Objective C task-parallel-computing-dev - Packages for development of parallel computing applications task-parallel-computing-node - Libraries for parallel computing applications task-polish - Polish-speaking environment task-python - Python script development environment task-python-bundle - Full distribution of Python task-python-dev - Full Python development environment task-python-web - Python web application development environment task-samba - Samba SMB server task-science - Packages for numerical computing, data analysis and visualization task-sgml-dev - SGML and XML development environment task-sgml - SGML and XML authoring and editing task-spanish - Spanish environment task-tcltk - Running Tcl/Tk applications task-tcltk-dev - Developing Tcl/Tk applications task-tex - TeX/LaTeX environment task-x-window-system - X Window System (complete) task-x-window-system-core - X Window System (core components) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
potato: kernel removal and 2.2.19 for i386
While I like the idea of removing old kernels from the Potato (and woody) archives, I object to some of the removals. Here are my arguments: No way to use 2.2.19 for boot-floppies update for Potato, there are no PCMCIA for it. Moreover, I think 2.2.19 has some serious problems, although I need to do a side-by-side compare of the kernel config files and changes between 2.2.19pre17 and 2.2.19. Alpha uses 2.2.19pre13, so please don't remove that (or is it gone already?). Alpha porters could comment on the chance of getting an update there... M68k is stuck on 2.2.17 for good reason, so please retain that. Sparc is using 2.2.19pre11 -- not sure if there's a good reason. Summary: The alpha, sparc, and i386 versions of the boot-floppies certainly could be changed to use 2.2.19, but that would pretty much blow away any chance of 2.2r4 by end of month, IMHO. Let me know if you need me to put some energy into that. Other notes: I will build 2.2.24 boot-floppies targetted for 2.2r4 -- it does not have any kernel updates however. See the changelog snippet below. Just ARM fixes and documentation updates. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ boot-floppies (2.2.24) stable; urgency=low * Phil Blundell: ARM fixes for the following: - NetWinder kernel is now Image not vmlinuz - 2.2.19 tulip driver breaks on NetWinder; use old_tulip instead - build NetWinder TFTP image - correct name of RiscPC keymap - documentation updates * Fabian Wauthier: German rescue disk translation updates * Chris Tillman: documentation corrections -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: potato: kernel removal and 2.2.19 for i386
Adam Di Carlo [EMAIL PROTECTED] wrote:
No way to use 2.2.19 for boot-floppies update for Potato, there are no
PCMCIA for it.
PCMCIA modules have been compiled for 2.2.19. They've been around for
weeks.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
Previously Wolfgang Sourdeau wrote: Another argument is that zile is kind of a stripped-down version of Emacs, and Emacs is the standard editor for the GNU system, which I am sure most of the people on this list are using. Emacs is not `the standard editor', it is just one of the two most popular ones. More importantly, we need an editor in the b-f that everyone can use easily without having to know emacs, vi or any other editor. Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
Wolfgang == Wolfgang Sourdeau [EMAIL PROTECTED] writes: what do you think to include as basic editor? vim? and elvis-tiny for boot-floopies? Wolfgang I am just experiencing zile and I find it quite good. And, Wolfgang btw, it is meant primarily for boot floppies. Another Wolfgang argument is that zile is kind of a stripped-down version Wolfgang of Emacs, and Emacs is the standard editor for the GNU Wolfgang system, which I am sure most of the people on this list are Wolfgang using. Another option is e3. It is tiny (less than 10k and static linked) and it has keybindings for vi, emacs, wordstar, pico and nedit. On i386 it is written in 100% asm, but there is also a portable C version. -- Bye, Peter Korsgaard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Sat, May 12, 2001 at 11:33:30AM +0200, Bastian Blank wrote: rblcheck why standard? exim use this? i don't know There would be a dependency between them if it did. mtoolsonly usefull for dos users Considering of the number of DOS-formatted floppy disks in the world, not having it in standard would be a pity. -- Digital Electronic Being Intended for Assassination and Nullification -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
Bastian == Bastian Blank [EMAIL PROTECTED] writes: [1 text/plain; us-ascii (quoted-printable)] On Sat, May 12, 2001 at 03:46:13AM -0400, Adam Di Carlo wrote: aenot used as basic editor anymore, everyone seems to hate it what do you think to include as basic editor? vim? and elvis-tiny for boot-floopies? I am just experiencing zile and I find it quite good. And, btw, it is meant primarily for boot floppies. Another argument is that zile is kind of a stripped-down version of Emacs, and Emacs is the standard editor for the GNU system, which I am sure most of the people on this list are using. why a print daemon? most user doesn't need such service if it is necesary, why not use cups as standard? LPRng is far more secure and robust than anything else. LPR is an insecure pseudo-standard, while LPRng is more configurable, better designed, more RFC-compliant. CUPS is nice too, but does lack a lot of drivers in its free version, is buggy and a lot of security problems are found too often. ipchains,ipmasqadmwoody includes kernel-source 2.4.x, so it is obselete if using such kernel Nope. Ipchains are still emulated. And people migrating from 2.2 will likely appreciate having it at hand. Wolfgang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
woody release task needs help: package priorities
Woody installation (via boot-floppies, base-config, tasksel, apt) will change from Potato in that, normally, all packages marked as standard will be marked for installation. Citing Policy: `standard' These packages provide a reasonably small but not too limited character-mode system. This is what will install by default if the user doesn't select anything else. It doesn't include many large applications, but it does include Emacs (this is more of a piece of infrastructure than an application) and a reasonable subset of TeX and LaTeX. This has never been done before by boot-floppies as a rather known oversight, mostly because some many nasty and insecure and useless packages are marked as standard. I would appreciate it if someone or some team would work with archive maintainers and work this out. Here's a provisional list of packages which are standard or higher and should not be: aenot used as basic editor anymore, everyone seems to hate it setserial rather inappropriate for non-i386, AFAIK libstdc++2.9 obsolete libident why? not used by other std package, pidentd exim we should move to postfix, IMHO dpkg-ftp obsolete rcs few use it vacation why standard? fingerd not very secure for baseline ftpd not very secure for baseline lpr not very secure for baseline, poss use lprng? nfs-kernel-server why standard in god's name? rblcheck why standard? talk rather obsolete, but debatable talkd not very secure for baseline telnetd not very secure for baseline There are probably packages not in standard that should be, I'll leave that to others. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Sat, 12 May 2001 03:46:13 -0400, Adam Di Carlo wrote: exim we should move to postfix, IMHO Let's not go over this again, but why change at all if it is working ok? We should all have better things than to worry about such things. -ako -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
Previously Adam Di Carlo wrote: exim we should move to postfix, IMHO FWIW, I disagree, and I'ld like to see some really good arguments before we make a change like that. Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Sat, May 12, 2001 at 03:46:13AM -0400, Adam Di Carlo wrote: exim we should move to postfix, IMHO Whilst I agree with you on all the others. postfix is 3 times the size of exim, and a fraction harder to configure. (This isn't meant as flamebait.) -- Paul Martin [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Sat, May 12, 2001 at 01:13:54PM +0200, Wichert Akkerman wrote: Emacs is not `the standard editor', it is just one of the two most popular ones. More importantly, we need an editor in the b-f that everyone can use easily without having to know emacs, vi or any other editor. I seem to have picked up the feeling that nano-tiny is being considered for this job. -- Paul Martin [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
starting after boot
I just installed debian from the cd's and after entering name and password, I get a command line which reads jdj329@debian:~$ What do I do from here? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
* Bastian Blank | On Sat, May 12, 2001 at 03:46:13AM -0400, Adam Di Carlo wrote: |aenot used as basic editor anymore, everyone seems to hate it | | what do you think to include as basic editor? vim? and elvis-tiny for | boot-floopies? nano-tiny This has been decided alreay, please let's not go over that debate again. |dpkg-ftp obsolete |rcs few use it | | replace it with cvs Have both, imho. |lpr not very secure for baseline, poss use lprng? | | why a print daemon? most user doesn't need such service | if it is necesary, why not use cups as standard? CUPS breaks every second release, I've heard, and even the maintainer didn't want to have it as the standard print system last time the argument was raised. IIRC, non-ECC memory. |talk rather obsolete, but debatable |talkd not very secure for baseline I want those. They are very useful, and afaik, there are no security problems with talkd. | iamerican,ibritishhmm No way. Lots of users are non-American and non-British and don't care for this. | wenglish I think it is only usefull with dict ITYM ispell. -- Tollef Fog Heen Unix _IS_ user friendly... It's just selective about who its friends are. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Sat, May 12, 2001 at 03:46:13AM -0400, Adam Di Carlo wrote: Here's a provisional list of packages which are standard or higher and should not be: exim we should move to postfix, IMHO Just for education's sake, what are the reasons you hold this opinion? I use exim simply because it came standard. I'd like to know why postfix is better. Drew (p.s debian-devel: sorry for the resend, I wanted Adam to recieve the question since he doesn't read d-d) -- PGP public key available at http://dparsons.webjump.com/drewskey.txt Fingerprint: A110 EAE1 D7D2 8076 5FE0 EC0A B6CE 7041 6412 4E4A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Sun, May 13, 2001 at 12:42:01AM +1000, Drew Parsons wrote: On Sat, May 12, 2001 at 03:46:13AM -0400, Adam Di Carlo wrote: Here's a provisional list of packages which are standard or higher and should not be: exim we should move to postfix, IMHO Just for education's sake, what are the reasons you hold this opinion? opinions are like.. oh well i think you know this one. I use exim simply because it came standard. I'd like to know why postfix is better. how does something become standard? - Someone has to make new standards, why shouldn't it be us. personally i like postfix as it is safe and easy to configure. (and no, i'm not saying that exim is not safe) -- - Sami Haahtinen - - 2209 3C53 D0FB 041C F7B1 F908 A9B6 F730 B83D 761C - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
At 10:38 PM +0200 5/11/01, Giorgio Terzi wrote: Bug 4: dboostrap problem. dbootsrap was not able to recognize the driver's floppy disk because the drivers' default names was treated as complete names but they are really root names for example: drv14 is a root name drv14apus.bin is a driver's complete name. In file floppy_merge.c i have modified the line 197 : if (!strcmp (basenames[i], block.header.name)) as follows: if (!strncmp (basenames[i], block.header.name,strlen(basenames[i]))) I just fixed this in bf cvs, none of the powerpc driver disks were listed as known driver disks, so I added drv14pmac, drv14apus, drv14chrp, and drv14prep. Stephen -- Stephen R. MarenkaIf life's not fun, you're not doing it right! [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: APUS Debian Boot-Floppies Images and bugs
On Fri, May 11, 2001 at 10:38:07PM +0200, Giorgio Terzi wrote:
Hello Sven,
In first i wish to thank you for your help and for your last
e-mail. :)))
But let's speak about job.
The second goal is reached!
Now is possible to load install Rescue Driver images from
floppies, CD-ROMS,HD-Partitions.
But to do this we must correct some bugs :
Bug 1: dbootstrap
The APUS rescue image is MSDOS formatted but in file
choose_medium.c from line 34 the code is so:
#if cpu(sparc) || #cpu(powerpc)
const char *fs_type_tab[] = { ext2, NULL };
#else
const char *fs_type_tab[] = { msdos, ext2, NULL };
#endif
as you can understand is impossible for a powerpc machine
to load a msdos partition, so i have modified it so:
#if cpu(sparc) || #cpu(powerpc)
const char *fs_type_tab[] = { msdos, ext2, NULL };
#else
const char *fs_type_tab[] = { msdos, ext2, NULL };
#endif
After this, rescue.bin was loaded and kernel extracted configured.
I think this #if is obsolete because, as you will see some lines
after in the source file , mount loops between the various filesystems
(msdos ext2 now, but may will be more ?) attempting
to load the image files.
Ok, will check it in on monday. BTW, could you send me all your changes in
patch form ? You know how to do so, isn't it ? you use diff -ur original.tree
changed.tree, or if you did change only a file, you do diff -u file.orig
file.new. This is the most usefull manner of sharing changes to code.
As what happened here, i guess it worked ok before (as potato used msdos disks
also) but was changed later on. BTW, it don't really makes sense to use msdos
root images, so we could as well go with the ext2 stuff for apus, but we have
to find were it is that this is specified.
For CD-ROM for HD partition loading system the drivers was also
successfully loaded configured.
For CD-ROM i used my Potato CD-ROM N.1.For hard disk i have
built a debian tree in an Amiga partition.
mmm, ok, i guess this will not work well because of the link issue, but then
it is only for testing.
Bug 2: floppy images build configuration
After the kernel configuration, it was renamed as vmlinuz-2.2.19,
and this comes from the install.sh script.
For APUS this name is wrong as it is really a 2.2.10 kernel.
Maybe it is possible to use the $subarch variable to distinguish the
various powerpc kernel architecture's versions during the install.sh
configuration ?
Yes, i remember there was a apus subarch, and already in potato i had to use
2.2.10, while other ppc subarches used 2.2.12 or later kernels.
Maybe we should also go the 2.4.x route, but i am not sure if it is ready
already. Let's ask on the apus lists about it.
I have tested also the floppy disk use:
Bug 3: fd0 device problems
For APUS /dev/fd0 is unable to load the rescue floppy disk.
I think it defaults to the Amiga floppy formats.
I must erase it and recreate it with 'mknod fd0 b 2 28'
that is the same of /dev/fd0u1440 in a standard installation.
After this change the rescue floppy was successfully loaded.
Err, do you have a 1.44MB floppy ? Most people would have only 880KB ones, so
this is not really needed. Maybe it would be good if you changedebootstrap, so
as to look for fd0u1440 directly, instead of for /dev/fd0, in case we are on
the apus subarch. Also some comment somewhere about it would be welcome. Don't
know if there is a place for adding description of the entries though.
Also i think i recall that we had /dev/fd0 for 720Ko floppies, and /dev/df0
for 880KB amiga floppies, or maybe it was /dev/pc0 or somethign such ...
Bug 4: dboostrap problem.
dbootsrap was not able to recognize the driver's floppy disk
because the drivers' default names was treated as complete
names but they are really root names for example:
drv14 is a root name
drv14apus.bin is a driver's complete name.
In file floppy_merge.c i have modified the line 197 :
if (!strcmp (basenames[i], block.header.name))
as follows:
if (!strncmp (basenames[i], block.header.name,strlen(basenames[i])))
after this i have also loaded the drivers!
huh, this is very nice work already, very good.
Just when making such changes, it is needed to check that it don't break other
arches/subarches. Is there a way to test for the apus subarch when doing the
changes ? somethign like :
if (arch=ppc subarch=apus)
if (!strcmp (basenames[i], block.header.name));
else if (!strncmp (basenames[i], block.header.name,strlen(basenames[i])));
I remember being able to do things like that before.
Maybe they are even macros to do per arch things ?
I can't test network installations because at this moment i haven't it.
maybe we could put the files somewhere and ask for someone with a network
connection to test this ?
Next steps:
1) I shall take a look for ZIP installation.
mmm, should be the same as harddisk installation, should it not ?
2) I shall try
Re: woody release task needs help: package priorities
On 12 May 2001, Adam Di Carlo wrote: libident why? not used by other std package, pidentd rblcheck why standard? These are used by exim IIRC. Simon -- GPG public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc Fingerprint: DC26 EB8D 1F35 4F44 2934 7583 DBB6 F98D 9198 3292 Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
from the secret journal of Drew Parsons ([EMAIL PROTECTED]): Just for education's sake, what are the reasons you hold this opinion? I use exim simply because it came standard. I'd like to know why postfix is better. http://www.postfix.org/motivation.html Postfix is a little bigger on disk than exim on, but it goes to great lenghts to keep it's memory usage down, or at least consistent. As for complexity, I run several sites using postfix, and my most complicated setup has only 40 lines in main.cf. Exim still has a lot of the sendmail-ish feel to it, like a really long config file and one big deamon running the show (IIRC. It's been about 18 months since I stopped using exim). Postfix has a sendmail compatibility interface (http://www.postfix.org/sendmail.1.html), but under the hood is similar to qmail in design. -- Jacob Kuntz http://underworld.net/~jake -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
Previously Jacob Kuntz wrote: http://www.postfix.org/motivation.html From what I hear: postfix does not do IPv6 postfix does not do TLS (not officialy and juding by comments on #debian-devel from today not reliably either) postfix header rewriting isn't flexible postfix uses multiple files instead of one big file, if that is better or worse is personal taste. exim doesn't feel at all like sendmail to me, again that's just personal taste. I still haven't seen a single good argument for switching the Debian default, just personal preferences. Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
I'm a simple user, I think after install Debian base, switch from exim to postfix is just a matter of apt-get install! Regards, Paulo Henrique Quoting Wichert Akkerman ([EMAIL PROTECTED]): Previously Jacob Kuntz wrote: http://www.postfix.org/motivation.html From what I hear: postfix does not do IPv6 postfix does not do TLS (not officialy and juding by comments on #debian-devel from today not reliably either) postfix header rewriting isn't flexible postfix uses multiple files instead of one big file, if that is better or worse is personal taste. exim doesn't feel at all like sendmail to me, again that's just personal taste. I still haven't seen a single good argument for switching the Debian default, just personal preferences. Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D | -- 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: woody release task needs help: package priorities
WA postfix does not do IPv6 WA postfix does not do TLS (not officialy and juding by comments on WA#debian-devel from today not reliably either) Recently there was released new stable version of postfix. It does support TLS. AFAIK it doesn't support IPV6 out of box right now. There is exist patch for IPV6 support but it was not merged in last stable release. WA postfix header rewriting isn't flexible Never used exim so I can't compare. WA postfix uses multiple files instead of one big file, if that is better WA or worse is personal taste. Actually it has only two config files. One small which defines various services (local delivery agent, smtpd, etc) and another big config file which configures all postfix services. Almost usually you edit only second config. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Ilya Martynov (http://martynov.org/)| | GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80 E4AE BE1A 53EB 323B DEE6 | | AGAVA Software Company (http://www.agava.com/) | -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc woody bf installation status
At 12:46 PM -0700 5/11/01, David Whedon wrote: Fri, May 11, 2001 at 01:56:34PM -0500 wrote: The next major stumbling block I ran into was that pump doesn't work (bts# 94176). Pump has annoyed me for a number of reasons including bts#64092 and its kin. I think there was some discussion some time ago about perhaps using dhcp-client. So I hacked dhcp-client to work. It works very well. The downside is that dhcp-client takes up a bit more space than pump: 137930 (more if kernel 2.0 support is required) vs. I don't think we need to directly support 2.0.x on boot-floppies, though if we decide not to we should make a note in the docs that dhcp won't work if you replace the kernel with a 2.0 serias. 58112. It's easy enough to #def this into/out of dbootstrap, but not quite so trivial to maintain both versions of the EXTRACT files. Let me know if you want the patch, even if just for dbootstrap. I've got an idea. Why don't we use dhcp-client-udeb? It is destined for use with debian-installer and is a bit smaller than the .deb: ruff:davidw$ dpkg -c dhcp-client-udeb_2.0pl5-5_i386.udeb drwxr-xr-x root/root 0 2001-05-11 12:38:14 ./ drwxr-xr-x root/root 0 2001-05-11 12:38:11 ./sbin/ -rwxr-xr-x root/root107356 2001-05-11 12:38:11 ./sbin/dhclient drwxr-xr-x root/root 0 2001-05-11 12:38:08 ./etc/ -rwxr-xr-x root/root 5816 2001-05-11 12:38:08 ./etc/dhclient-script ruff:davidw$ The udeb already exists in the archive, the only thing to do would be to modify the apt magic so it looks for it. Saves us a little space, and a lot of people complain about pump. Sounds like a good plan. /sbin/dhclient in the deb is a script that calls either dhclient-2.2.x or dhclient-2.0.x depending on uname -r. I just dropped dhclient-2.0.x and dhclient from the EXTRACT lists. I wonder if dhclient-2.2.x is renamed dhclient in the udeb? I suppose I'll just have to see. Should I fix dbootstrap to look for dhclient and failing that pump? That would give us more flexibility and it shouldn't be hard to do. -- Stephen R. MarenkaIf life's not fun, you're not doing it right! [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: starting after boot
James Jackson [EMAIL PROTECTED] writes: I just installed debian from the cd's and after entering name and password, I get a command line which reads jdj329@debian:~$ What do I do from here? Wherever you want to... Most people generally get X11 worked out so they have a GUI environment. Search for packages that interest you: apt-cache search searchterm Get more info on them: apt-cache show pkg Install them (as root): apt-get install pkg Install games and play them. Whatever! -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
potato b-f 2.2.24 testing/building
I should be able to release 2.2.24 tomorrow -- I'm not testing that it builds and all that, then I'll tag it and build from exported sources tomorrow. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: potato: kernel removal and 2.2.19 for i386
Herbert Xu [EMAIL PROTECTED] writes: Adam Di Carlo [EMAIL PROTECTED] wrote: No way to use 2.2.19 for boot-floppies update for Potato, there are no PCMCIA for it. PCMCIA modules have been compiled for 2.2.19. They've been around for weeks. Well, auric is down so I can't even check for it. I didn't see pcmcia packages listed at http://people.debian.org/~joey/2.2r4/ nor could I find an upload announcement sent to debian-devel-announce -- the latest I saw was: 53652 06Apr Brian Mays Installed pcmcia-cs 3.1.25-3 (i386 source all) Which was unstable upload. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: potato: kernel removal and 2.2.19 for i386
Adam Di Carlo [EMAIL PROTECTED] writes: Herbert Xu [EMAIL PROTECTED] writes: Adam Di Carlo [EMAIL PROTECTED] wrote: No way to use 2.2.19 for boot-floppies update for Potato, there are no PCMCIA for it. PCMCIA modules have been compiled for 2.2.19. They've been around for weeks. Oh, I see them now. Duh. My bad. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: work needed for woody release: rationally looking at task pkgs
On Sat, May 12, 2001 at 03:32:39AM -0400, Adam Di Carlo wrote: I propose the following thorough-going changes: rename server packages to 'task-server-*' rename devel packages to 'task-devel-*' rename l10n packages to 'task-l10n-*' The purpose of this is to group like packages together in tasksel. FWIW, I've got a patch to tasksel which allows you to group task packages by Section: nicely, so this can be avoided, if we want. ftpmaster is quite happy to create some special sections purely for grouping tasks if that's considered desirable, btw. Other stuff: Why no 'task-desktop-gnome' and 'task-desktop-kde' ? There's a task-desktop (including both Gnome and KDE --- you get to choose what you want from gdm), at deb http://people.debian.org/~ajt/ task-desktop/ fwiw. (Ideally, I'd rather someone other than me maintain it) Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. ``_Any_ increase in interface difficulty, in exchange for a benefit you do not understand, cannot perceive, or don't care about, is too much.'' -- John S. Novak, III (The Humblest Man on the Net) PGP signature
Re: non-vanilla i386 kernels botched in 2.2r3
Herbert Xu [EMAIL PROTECTED] writes: My experience of the 2.2.19 kernels is that they are still unsuitable for building. I will research more so I can more demonstrations of this. Please do so. Hmm, I compared all the config files and they seem fine. My apologies. Nice work. Once 2.2.24 has finished building, I'll immediately embark on Potato update boot-floppies 2.2.25 for kernel updates for i386. Remember that i386 is not the only arch using 2.2.19pre -- alpha is using 2.2.19pre13 and sparc is using 2.2.19pre11. If a sparc and alpha port is willing and able, we could fix this for those arches as well. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/en by aph
Repository: boot-floppies/documentation/en who:aph time: Sat May 12 09:51:30 PDT 2001 Log Message: fix a SGML tagging error introduced by me Files: changed:Tag: potato partitioning.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies by aph
Repository: boot-floppies who:aph time: Sat May 12 09:58:49 PDT 2001 Log Message: strip out some cruft we'll never get to Files: changed:todo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc woody bf installation status
Stephen R Marenka [EMAIL PROTECTED] writes: At 12:46 PM -0700 5/11/01, David Whedon wrote: Fri, May 11, 2001 at 01:56:34PM -0500 wrote: The next major stumbling block I ran into was that pump doesn't work (bts# 94176). Pump has annoyed me for a number of reasons including bts#64092 and its kin. I think there was some discussion some time ago about perhaps using dhcp-client. So I hacked dhcp-client to work. It works very well. The downside is that dhcp-client takes up a bit more space than pump: 137930 (more if kernel 2.0 support is required) vs. I don't think we need to directly support 2.0.x on boot-floppies, though if we decide not to we should make a note in the docs that dhcp won't work if you replace the kernel with a 2.0 serias. No, kernel 2.0 not needed, no one uses it. 58112. It's easy enough to #def this into/out of dbootstrap, but not quite so trivial to maintain both versions of the EXTRACT files. Let me know if you want the patch, even if just for dbootstrap. I've got an idea. Why don't we use dhcp-client-udeb? Um, I'm a bit hesitant to add more special cases and wierd handling (such as udeb) to the boot-floppies. Are there any udebs in Woody? Remember, this needs to be buildable by pure woody. Sounds like a good plan. /sbin/dhclient in the deb is a script that calls either dhclient-2.2.x or dhclient-2.0.x depending on uname -r. I just dropped dhclient-2.0.x and dhclient from the EXTRACT lists. I wonder if dhclient-2.2.x is renamed dhclient in the udeb? I suppose I'll just have to see. Again, I'm fine with moving to dhclient -- I would prefer to use the proper package rather than the udeb, space be damned. Should I fix dbootstrap to look for dhclient and failing that pump? That would give us more flexibility and it shouldn't be hard to do. Sure, please. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc woody bf installation status
David Whedon [EMAIL PROTECTED] writes: Fri, May 11, 2001 at 01:56:34PM -0500 wrote: That got me all the way to installing base, but that slammed to a halt quickly since it appears that md5sum is broken (another busybox problem? ppc-only? needs more research). So, I commented out the md5 check in debootstrap to see how much further I could go. i I remember this one. Are you using busybox cvs? At the moment busybox cvs is working, bb 0.51-1 (the current Debian package) doesn't work for a number of reasons. That got me to mount -t proc proc /proc which failed miserably. Interestingly, /proc was already (successfully?) mounted. I don't see a good way to get around that so there it ends. I guess I'll be checking out the busybox cvs next. oh, yes, you should be using cvs. Could someone *please* just NMU busybox, urgency high? I am wanting to build this boot-floppies *now* and I don't want to wait anymore... :) -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
Bastian Blank wrote: On Sat, May 12, 2001 at 03:46:13AM -0400, Adam Di Carlo wrote: aenot used as basic editor anymore, everyone seems to hate it what do you think to include as basic editor? vim? and elvis-tiny for boot-floopies? The editor for boot floppies doesnt have to be very complex, probably only be used to edit a config file. busybox has a nice tiny vi editor that adds between 12 - 22kB to busybox, doesnt depend on any graphics libraries, and should work on all arch's, that could easily be used for boot floppies, but still vi isnt very useable to newbies. nano is very friendly and would be a good choice i think Or if we manged to scrounge some extra space we could go all out and include both, nano-tiny for newbies, vi for experts... that might be tough though. Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: work needed for woody release: rationally looking at task pkgs
BTW, anthony, I hadn't read your thread on task packages when I wrote this plea for help. But I think we're going after different things -- you, a sane task system for sid, me, just better tasks using existing tools for Woody. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: base-config cruft cleanup
Joey Hess [EMAIL PROTECTED] writes:
I want to check and see if some of the uglier cruft in base-config can
be removed for the woody boot-floppies. Can anyone verify:
- If LANG is set, will it be properly set to a ll_LL form? Base-config
had some code to deal with the ll form, which broke perl. (I've
already removed that code.)
Um, it's LANGUAGE, and I'm not sure. Would need testing. I'm pretty
sure it's not going to be in the form you want it Just murphy's law.
- Have any new settings been added to /root/dbootstrap_settings that I
should deal with?
Here's all of them:
baseconfig.c:write_userconfig(SERIALCONSOLE, true);
extract_base.c: write_userconfig(DEBIAN_MIRROR, source);
net-fetch.c:write_userconfig(HTTP_PROXY, txtbuf);
pcmcia.c: if (!rtn) write_userconfig (PCMCIA, yes);
util.c: if ( write_userconfig(BUILDTIME, BUILDTIME) != 0 ) { /* check that we can
write config */
util.c:write_userconfig(VERBOSE, yes);
util.c:write_userconfig(VERBOSE, quiet);
util.c:write_userconfig(DEBUG, true);
util.c:write_userconfig(CDROM, true);
util.c:write_userconfig(LANGUAGE, lang);
- This code probably better belongs in console-tools or something. Do I
still need to keep it?
No clue. You should direct this to Yann Dirson I guess.
- Is pcmcia handled more sanely now that we use debootstrap? It used to not
be in a package, just dumped onto the filesystem, so I have this code:
echo pcmcia-cs purge | dpkg --set-selections
echo pcmcia-modules-`uname -r` purge | dpkg --set-selections
# In a sane world, I would not need to do this. Welcome to my world.
rm -rf /etc/pcmcia /lib/modules/`uname -r`/pcmcia
depmod -a /dev/null || true
# Delete lines above if/when those files are registed with dpkg.
Nope, no more sanely, I don't think. You can add a boot-floppies todo
item if you think this is fixable.
--
.Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc woody bf installation status
Sounds like a good plan. /sbin/dhclient in the deb is a script that calls either dhclient-2.2.x or dhclient-2.0.x depending on uname -r. I just dropped dhclient-2.0.x and dhclient from the EXTRACT lists. I wonder if dhclient-2.2.x is renamed dhclient in the udeb? I suppose I'll just have to see. Again, I'm fine with moving to dhclient -- I would prefer to use the proper package rather than the udeb, space be damned. Fine by me, we don't save that much space with the udeb anyway, pretty much the only difference is the compiler options are -Os. Should I fix dbootstrap to look for dhclient and failing that pump? That would give us more flexibility and it shouldn't be hard to do. Sure, please. Sounds good. David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc woody bf installation status
On Sat May 12, 2001 at 01:05:55PM -0400, Adam Di Carlo wrote: David Whedon [EMAIL PROTECTED] writes: Fri, May 11, 2001 at 01:56:34PM -0500 wrote: That got me all the way to installing base, but that slammed to a halt quickly since it appears that md5sum is broken (another busybox problem? ppc-only? needs more research). So, I commented out the md5 check in debootstrap to see how much further I could go. i I remember this one. Are you using busybox cvs? At the moment busybox cvs is working, bb 0.51-1 (the current Debian package) doesn't work for a number of reasons. That got me to mount -t proc proc /proc which failed miserably. Interestingly, /proc was already (successfully?) mounted. I don't see a good way to get around that so there it ends. I guess I'll be checking out the busybox cvs next. oh, yes, you should be using cvs. Could someone *please* just NMU busybox, urgency high? I am wanting to build this boot-floppies *now* and I don't want to wait anymore... :) I'm building a new one now. Rather then waiting for 0.52 to stabalize, I'm backporting the critical bugfixes into 0.51. -Erik -- Erik B. Andersen email: [EMAIL PROTECTED], [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: building the cvs snapshot: pointerize troubles
Fabian Roth [EMAIL PROTECTED] writes: i've been trying to make the cvs-snapshot. make check succeeds, but make fails with: make[3]: Entering directory `/home/fin/cvs/boot-floppies/utilities/dbootstrap' pointerize -m po/C.mo floppy_merge.c build/floppy_merge.t.c String Some important data was not read from the floppy disks. You floppy disk from the drive. not found. make[3]: *** [build/floppy_merge.t.c] Error 255 any ideas? Sounds like catalogs need to be updated. look a the makefile in utilities/dbootstrap/po/ could it be because i got my packages out of unstable instead of testing? Absolutely not. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies by aph
Repository: boot-floppies who:aph time: Sat May 12 10:23:48 PDT 2001 Log Message: start 2.2.25; bump i386 kernel to 2.2.19 Files: changed:Tag: potato config -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/debian by aph
Repository: boot-floppies/debian who:aph time: Sat May 12 10:23:52 PDT 2001 Log Message: start 2.2.25; bump i386 kernel to 2.2.19 Files: changed:Tag: potato changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc woody bf installation status
Erik Andersen [EMAIL PROTECTED] writes: I'm building a new one now. Rather then waiting for 0.52 to stabalize, I'm backporting the critical bugfixes into 0.51. Thank you . Please let us know when it's up. I can do a source release tomorrow and then we can have working boot-floppies source package at least in woody. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tasks: counterproposal (and implimentation)
Anthony Towns wrote: you can't see the packages that comprise a task or their descriptions, nor can you include a long description. ie, the whole Task Info thing's missing. I don't think that's very important. A task is supposed to satisfy a simple, well-defined need. If you want a web server, you shouldn't care much which one. Also, this is one of the reasons I think we should give people the opportunity to drop into dselect/something better after broadly outlining their tasks to they can tweak the result if necessary. I think we should do that no matter what system we eventually decide upon for defining and presenting tasks. It also doesn't support third parties who might want to use tasks: you can't just add an extra line to your sources.list and get a Ximian Desktop made available, for example. True enough. I used to work at a company that internally used special debian tasks, so I suppose I should have thought of that. I'll think about it, but this may well be a fatal flaw in my proposal, if we consider this an important need to meet with tasks. Similarly, you can't look at the tasks available from a release without installing software from that release first. I don't really understand the importance of that. If you ever add apt-get support, btw, you'll need to be careful to avoid duplicating the existing task bug, ie if any package in a task goes missing an apt-get install foo bar baz (which is what tasksel does) will fail. Note that the way base-config runs tasksel avoids that: use dpkg --set-selections and if something is not available, dpkg ignores it. There's also the possibility that an entire task will need to be made unavailable, either because every package (or every significant package) included in it is buggy, or in postgresql/task-database's case, because might only be available from non-US. I actually have been thinking since I posted the code about some enhancements to deal with cases where all the packages in a task, or at least some of the important ones, are missing. Noticing all are missing and not displaying the task in the list is easy enough. Noticing that the core packages of a task (postgresl, apache) are missing and deciding not to show the task is also doable, it really just requires one list of the key packages that mist be present, and another list of ancillary packages that can go missing w/o badly breaking the task. This ought to be able to be done without modifying newtasksel, since, according to the freeze plans, newtasksel will be frozen (as part of the base system) while the tasks and their packages (as part of the standard system) are still be fixed or removed. Split out the task data and move it to a standard priority package then. And all the things you and others have already complained about are also applicable to newtasksel: no support for people who want to just install a task from the command line, tasks not being handled by dselect or apt-get or deity (and at this point, I'd have to say not ever being able to be handled, whatever the authors of those programs might want). Basically, if you're satisfied with newtasksel, I'm not really sure why you'd object to tasksel 1.1. But if you didn't object to tasksel 1.1, then you wouldn't've written newtasksel in the first place... The core to all of those objections about tasksel was that tasks were debian packages. So we *expected* to be able to use them just like regular debian packages. We wanted to be able to use them with apt, with dselect, and so on. If tasks are no longer enbodied by rather strange debian packages, all these expectations go away. They're something different, and you interact with them differently. That's the whole point of my proposal, really. If people don't understand that, I don't think I can explain it to them any better than I already have, and perhaps I should just give up and add another item to my list-of-things-I-really-wish-debian-did-differently-but-will-never-be-fixed. (BTW, could someone from Progeny PLEASE speak up and give us a summary of how your task analog works?) -- see shy jo, wondering about that German blood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On 12 May 2001, Peter Korsgaard wrote: Wolfgang == Wolfgang Sourdeau [EMAIL PROTECTED] writes: what do you think to include as basic editor? vim? and elvis-tiny for boot-floopies? Wolfgang I am just experiencing zile and I find it quite good. And, Wolfgang btw, it is meant primarily for boot floppies. Another Wolfgang argument is that zile is kind of a stripped-down version Wolfgang of Emacs, and Emacs is the standard editor for the GNU Wolfgang system, which I am sure most of the people on this list are Wolfgang using. Another option is e3. It is tiny (less than 10k and static linked) and it has keybindings for vi, emacs, wordstar, pico and nedit. On i386 it is written in 100% asm, but there is also a portable C version. e3 is a nice editor. e3c isn't a second version of e3 since upstream is more likely to remoce it than to make it a complete replacement of e3. cu Adrian (e3 maintainer) -- Nicht weil die Dinge schwierig sind wagen wir sie nicht, sondern weil wir sie nicht wagen sind sie schwierig. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
On Sat, May 12, 2001 at 01:13:54PM +0200, Wichert Akkerman wrote: Previously Wolfgang Sourdeau wrote: Another argument is that zile is kind of a stripped-down version of Emacs, and Emacs is the standard editor for the GNU system, which I am sure most of the people on this list are using. Emacs is not `the standard editor', it is just one of the two most popular ones. More importantly, we need an editor in the b-f that everyone can use easily without having to know emacs, vi or any other editor. The ed utility is the standard text editor. - ed(1) -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#96906: marked as done (Base-install over net doesnt load lilo)
Your message dated 12 May 2001 13:18:04 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#96906: Base-install over net doesnt load lilo has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Darren Benham (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 9 May 2001 21:44:52 + From [EMAIL PROTECTED] Wed May 09 16:44:52 2001 Return-path: [EMAIL PROTECTED] Received: from imo-d01.mx.aol.com [205.188.157.33] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14xblM-0001qH-00; Wed, 09 May 2001 16:44:52 -0500 Received: from [EMAIL PROTECTED] by imo-d01.mx.aol.com (mail_out_v30.10.) id l.cc.14a805aa (15700) for [EMAIL PROTECTED]; Wed, 9 May 2001 17:44:15 -0400 (EDT) Received: from web29.aolmail.aol.com (web29.aolmail.aol.com [205.188.222.5]) by air-id05.mx.aol.com (v77_r1.37) with ESMTP; Wed, 09 May 2001 17:44:15 -0400 Date: Wed, 09 May 2001 17:44:15 EDT From: [EMAIL PROTECTED] Subject: Base-install over net doesnt load lilo To: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Unknown (No Version) Message-ID: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Package: Boot-Floppies Version: 1.9 When installing the base system over the network, it doesnt install lilo. I noticed this when, at the last step, I couldnt make a boot floppy or a bootloader. I opened a console and tried to do it manually, and it sayed that I had to run the version installed in the target install. I did a find '/target -name lilo' and there were no matches. I reinstalled and I watched the network-install log, and it didnt appear to install lilo. I think that's an error. --- Received: (at 96906-done) by bugs.debian.org; 12 May 2001 17:17:56 + From [EMAIL PROTECTED] Sat May 12 12:17:56 2001 Return-path: [EMAIL PROTECTED] Received: from arroz.onshored.com [216.220.101.2] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14yd1f-0001bA-00; Sat, 12 May 2001 12:17:55 -0500 Received: from arroz.fake (localhost [127.0.0.1]) by arroz.onshored.com (Postfix) with ESMTP id B24FC93802; Sat, 12 May 2001 13:18:04 -0400 (EDT) Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Bug#96906: Base-install over net doesnt load lilo References: [EMAIL PROTECTED] From: Adam Di Carlo [EMAIL PROTECTED] Date: 12 May 2001 13:18:04 -0400 In-Reply-To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Lines: 27 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Package: Boot-Floppies Version: 1.9 This is not an actual version. We need to know the actual version of boot-floppies you used. On i386, it shows that on the syslinux screen you get with the boot: prompt. When installing the base system over the network, it doesnt install lilo. Yes, it does. It installs base2_2.tgz and that has lilo on it. I noticed this when, at the last step, I couldnt make a boot floppy or a bootloader. I opened a console and tried to do it manually, and it sayed that I had to run the version installed in the target install. I did a find '/target -name lilo' and there were no matches. I cannot reproduce this. Nor can any of my friends. We have done many network installs. Closing this bug, it's very wrong. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: tasks: counterproposal (and implimentation)
On Sat, May 12, 2001 at 01:39:43PM -0400, Joey Hess wrote: (BTW, could someone from Progeny PLEASE speak up and give us a summary of how your task analog works?) I'd tell you in IRC, but whoops, for no apparent reason I've been banned from the channel. Probably by someone who has said in the past that #debian-devel should be open to all...gotta love those double standards. We have package sets. Here's an example: /usr/share/package-sets/progeny/xemacs.contents /usr/share/package-sets/progeny/xemacs.description $ cat /usr/share/package-sets/progeny/xemacs.contents xemacs21 xemacs21-bin xemacs21-mule xemacs21-supportel xemacs21-support $ cat /usr/share/package-sets/progeny/xemacs.description XEmacs XEmacs is an enhanced version of Emacs, the extensible, customizable, self-documenting real-time display editor. This package includes XEmacs as well as an updated version of the Gnus news reader that is newer than the version included with XEmacs. You can override the contents (off the top of my head, not sure about the description) by creating a file in, e.g., /etc/package-sets/xemacs.contents . -- G. Branden Robinson | Experience should teach us to be most on Debian GNU/Linux| our guard to protect liberty when the [EMAIL PROTECTED] | government's purposes are beneficent. http://www.debian.org/~branden/ | -- Louis Brandeis PGP signature
Re: woody release task needs help: package priorities
On Sat, 12 May 2001, Wolfgang Sourdeau wrote: Bastian == Bastian Blank [EMAIL PROTECTED] writes: [1 text/plain; us-ascii (quoted-printable)] On Sat, May 12, 2001 at 03:46:13AM -0400, Adam Di Carlo wrote: aenot used as basic editor anymore, everyone seems to hate it what do you think to include as basic editor? vim? and elvis-tiny for boot-floopies? I am just experiencing zile and I find it quite good. And, btw, it is meant primarily for boot floppies. Another argument is that zile is kind of a stripped-down version of Emacs, and Emacs is the standard editor for the GNU system, which I am sure most of the people on this list are using. That most Debian developers use Emacs is not a good argument for including an Emacs-like editor in boot-floppies, because most people who will be using the boot-floppies are /not/ Debian developers, and we should not expect them to have the same background knowledge that we do. I've seen nano discussed as a replacement for ae, which I think is a very good idea; nano is *self-documenting*, which is the key feature for an editor we want to be useful for all users. I also don't think you'll get very far in trying to prove that most people on d-d use emacs. why a print daemon? most user doesn't need such service if it is necesary, why not use cups as standard? LPRng is far more secure and robust than anything else. LPR is an insecure pseudo-standard, while LPRng is more configurable, better designed, more RFC-compliant. CUPS is nice too, but does lack a lot of drivers in its free version, is buggy and a lot of security problems are found too often. Yes, I don't think CUPS is yet mature enough to be recommended for standard. BSD lpr is mature, but it hasn't gotten any better with age. :) LPRng seems a good choice to me. Steve Langasek postmodern programmer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/debian by bcollins
Repository: boot-floppies/debian who:bcollins time: Sat May 12 12:52:04 PDT 2001 Log Message: Sparc updates Files: changed:changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies by bcollins
Repository: boot-floppies who:bcollins time: Sat May 12 12:52:04 PDT 2001 Log Message: Sparc updates Files: changed:Makefile config release.sh rescue.sh silo_proto.sh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New Woody 2.3.2 boot images for sparc, need testing...
These are based on the latest CVS of boot-floppies. The major change is that the sun4u images are built from the 2.4.4 kernel images. The best part about this is that this means that should support Blade 100/1000 (don't hold me to this, I can't test them) since they are synced with vger CVS as of today. The sparc32 images are still based on 2.2.19. You'll notice that the sun4u rescue image is 2880k. I know that sparc's don't have 2880k floppies, but then again, most ultrasparc's that I have used can't boot from floppy anyway. You'll need to netboot with the provided tftp image, unless you know how to create a bootable CD with the provided files (isn't too hard). FYI, I have not tested these *at all*. I am getting ready to try the tftp image (atleast booting it) once I find the serial cable that was misplaced in my recent move. Let me know how things go. http://auric.debian.org/~bcollins/disks-sparc/current/ For netboot, you should only need the tftpimage under the subarch directory of your choice. The rest of the install should be able to download everything else itself. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation by aph
Repository: boot-floppies/documentation who:aph time: Sat May 12 13:17:37 PDT 2001 Log Message: modified PowerMac booting notes from Chris Tillman Files: changed:Tag: potato urls.ent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/en by aph
Repository: boot-floppies/documentation/en who:aph time: Sat May 12 13:17:38 PDT 2001 Log Message: modified PowerMac booting notes from Chris Tillman Files: changed:Tag: potato rescue-boot.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/en by aph
Repository: boot-floppies/documentation/en who:aph time: Sat May 12 13:20:43 PDT 2001 Log Message: ignorable Files: changed:Tag: potato partitioning.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/documentation/en by aph
Repository: boot-floppies/documentation/en who:aph time: Sat May 12 13:29:42 PDT 2001 Log Message: fix SGML errors in the last commit Files: changed:Tag: potato rescue-boot.sgml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies/debian by aph
Repository: boot-floppies/debian who:aph time: Sat May 12 13:30:04 PDT 2001 Log Message: more powermac changes from chris tillman Files: changed:Tag: potato changelog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Woody 2.3.2 boot images for sparc, need testing...
Ben Collins [EMAIL PROTECTED] writes: These are based on the latest CVS of boot-floppies. The major change is that the sun4u images are built from the 2.4.4 kernel images. The best part about this is that this means that should support Blade 100/1000 (don't hold me to this, I can't test them) since they are synced with vger CVS as of today. The sparc32 images are still based on 2.2.19. Oy. Is it really worth it to jump to 2.4.x just for blade? Is the 2.4.4 kernel in testing at all? If not, could it be uploaded with urgency HIGH to get it into testing? You'll notice that the sun4u rescue image is 2880k. I know that sparc's don't have 2880k floppies, but then again, most ultrasparc's that I have used can't boot from floppy anyway. You'll need to netboot with the provided tftp image, unless you know how to create a bootable CD with the provided files (isn't too hard). So you're completely dropping 1440k floppies? BTW, my only woody box is a SPARC, so I've been doing the boot-floppies source/binary builds on that. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Woody 2.3.2 boot images for sparc, need testing...
On Sat, May 12, 2001 at 04:40:51PM -0400, Adam Di Carlo wrote: Ben Collins [EMAIL PROTECTED] writes: These are based on the latest CVS of boot-floppies. The major change is that the sun4u images are built from the 2.4.4 kernel images. The best part about this is that this means that should support Blade 100/1000 (don't hold me to this, I can't test them) since they are synced with vger CVS as of today. The sparc32 images are still based on 2.2.19. Oy. Is it really worth it to jump to 2.4.x just for blade? Is the 2.4.4 kernel in testing at all? If not, could it be uploaded with urgency HIGH to get it into testing? Absolutely. It was worth upgrading auric to 2.4.x because of the stability issues. No, neither the 2.2.19 images, nor the 2.4.4 images are in testing. The 2.2.19 image needs one bug fix. The 2.4.4 images were 9 days old, now they are 1 day old again...so time is the only issue. I'll get new 2.2.19 images uploaded tonight. You'll notice that the sun4u rescue image is 2880k. I know that sparc's don't have 2880k floppies, but then again, most ultrasparc's that I have used can't boot from floppy anyway. You'll need to netboot with the provided tftp image, unless you know how to create a bootable CD with the provided files (isn't too hard). So you're completely dropping 1440k floppies? Read that, dropping 1440k floppy support for sun4u (not sparc32 like sun4c, sun4m, sun4d). It's not like the support was used much anyway. The 2.4.4 sun4u images wont fit on a 1440k image, so I have no choice. BTW, my only woody box is a SPARC, so I've been doing the boot-floppies source/binary builds on that. Yeah. That's why I'm just worrying about sun4u, since I can test those. Let me know if there are any oddities with sparc32 boot. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: preparing for initrd of cdlinux
I don't understand this. How is it related to debian-cd ? The list you should be posting to is [EMAIL PROTECTED] -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Full install from cd achieved (RFC)
Santiago Garcia Mantinan [EMAIL PROTECTED] writes: I have removed fdutils because the interactive setup it has was breaking the install, as aj had noticed when building debootstrap 0.1.7, has anybody noticed the maintainer about this? shall I do it? yes, please file a serious bug against fdutils. It is preventing us from making a boot floppy at install time. Well, the problem is what should be done to fdutils to correct this, I mean changing it to use debconf would do, wouldn't it? but... is there any other solution? To file a bug, it's sufficient to merely report the error that is occuring. Please do so ASAP. Not having fixed pkgs which are needed for root, base, etc, causes massive delays in boot-floppies development and stability. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian CDROM installation problems
You should be using the idepci flavor of i386 install disks. That is bootable from one of the ISO images -- see the manual. Or you can make a rescue floppy and use CD1 for the rest. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Patch] Galician (gl_ES) translation
Sat, May 12, 2001 at 05:00:53PM -0400 wrote: I assume this patch was already applied by David Weldon? s/Weldon/Whedon/ everybody does it, I don't know why :-) Yes, I applied it. If something is missing, unfinished or messed with respect to this patch I don't know about it. David -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- 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]
Bug#96237: boot-floopies problem
Doug Regehr [EMAIL PROTECTED] writes: Immediately before the main menu appears, I see a whole bunch of messages that look like this: modprob: modprob: Can't open dependencies file target/lib/modules/2.2.19pre17... Does the directory exist? AFter you install the kernel and modules, then /lib/modules/`uname -r` becomes a symlink to /target/lib/modules/`uname -r`. You can check in tty2 if that got fudged. Be sure your kernel and drivers disk are matching -- e.g., not from different sets. If you didn't mess up somehow, and the symlink is broken, then we have a problem. Try again from scratch, and see if it happens again. If so, give me 'ls -l' output in /lib/modules and /target/lib/modules, as well as 'uname -r' output please. I'm trying to install over a network. At the Select Installation Medium screen, my network card does not appear in the list. Sure... you don't have a network yet. Recognizing that I probably need to set up PCMCIA first, I select Configure PCMCIA support from the main menu. As documented, yes, no bug here... After answering all the questions, I receive the following error message: An error encountered while trying to load and configure the PCMCIA modules Very informative. Look in your system logs, tty3, or /var/log/message. Please RTFM before complaining about not being informative. At this point I am thoroughly confused. RTM. I select Configure Device Driver Modules from the main menu. After answering yes to the question, I receive the following error message: Problem: No modules were found in /target/lib/modules/2.2.19pre17 that could be configured. Please install the modules first. See the problem above. I have some vague notion that the modprob errors I got at the beginning are somehow related to the absence of device driver modules on the root disk I downloaded. Well, a possible symptom of the bad /lib/modules symlinks... I tried downloading the root disk again, but the same thing happened. I have read the installation manual, but I couldn't find the answer to my problem. I'm sorry, but your bug report gives me the impression you have *not* read the install manual, esp. the section on troubleshooing and where to look for logs. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Woody 2.3.2 boot images for sparc, need testing...
* Ben Collins [EMAIL PROTECTED] [010512 14:00]: Yeah. That's why I'm just worrying about sun4u, since I can test those. Let me know if there are any oddities with sparc32 boot. Sadly, it doesn't seem to work on the AX1105 (similar to SB100) that I have here: ok boot net Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: Timeout waiting for ARP/RARP packet 296e00 TILO Fast Instruction Access MMU Miss -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: bugs is fixed
Processing commands for [EMAIL PROTECTED]: close 96156 Bug#96156: dbootstrap install menus look wierd Bug closed, send any further explanations to David Whedon [EMAIL PROTECTED] Somehow this has been fixed. Unknown command or malformed arguments to command. End of message, stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc woody bf installation status
On Sat May 12, 2001 at 12:10:26PM -0600, Erik Andersen wrote: It is now in incoming. Lemme know if you have any problems with it. I did a rather quick hack-n-slash job to put this together. It should be fine now, and I think I have all bugs bothering the boot-floppies fixed. Hopefully I didn't create any new problems... It turns out I screwed up cp and mv. Another upload that should actually work this time is now in incoming. Sorry about that. -Erik -- Erik B. Andersen email: [EMAIL PROTECTED], [EMAIL PROTECTED] --This message was written using 73% post-consumer electrons-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Woody 2.3.2 boot images for sparc, need testing...
I have an Ultra1 and I installed Debian using the boot floppies. Typing in boot floopy at the ok prompt seemed to work just fine. Tom Korte On Sat, 12 May 2001 14:58:49 Ben Collins wrote: On Sat, May 12, 2001 at 04:40:51PM -0400, Adam Di Carlo wrote: Ben Collins [EMAIL PROTECTED] writes: These are based on the latest CVS of boot-floppies. The major change is that the sun4u images are built from the 2.4.4 kernel images. The best part about this is that this means that should support Blade 100/1000 (don't hold me to this, I can't test them) since they are synced with vger CVS as of today. The sparc32 images are still based on 2.2.19. Oy. Is it really worth it to jump to 2.4.x just for blade? Is the 2.4.4 kernel in testing at all? If not, could it be uploaded with urgency HIGH to get it into testing? Absolutely. It was worth upgrading auric to 2.4.x because of the stability issues. No, neither the 2.2.19 images, nor the 2.4.4 images are in testing. The 2.2.19 image needs one bug fix. The 2.4.4 images were 9 days old, now they are 1 day old again...so time is the only issue. I'll get new 2.2.19 images uploaded tonight. You'll notice that the sun4u rescue image is 2880k. I know that sparc's don't have 2880k floppies, but then again, most ultrasparc's that I have used can't boot from floppy anyway. You'll need to netboot with the provided tftp image, unless you know how to create a bootable CD with the provided files (isn't too hard). So you're completely dropping 1440k floppies? Read that, dropping 1440k floppy support for sun4u (not sparc32 like sun4c, sun4m, sun4d). It's not like the support was used much anyway. The 2.4.4 sun4u images wont fit on a 1440k image, so I have no choice. BTW, my only woody box is a SPARC, so I've been doing the boot-floppies source/binary builds on that. Yeah. That's why I'm just worrying about sun4u, since I can test those. Let me know if there are any oddities with sparc32 boot. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [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]
Re: tasks: counterproposal (and implimentation)
On Sat, May 12, 2001 at 01:39:43PM -0400, Joey Hess wrote: Anthony Towns wrote: Also, this is one of the reasons I think we should give people the opportunity to drop into dselect/something better after broadly outlining their tasks to they can tweak the result if necessary. I think we should do that no matter what system we eventually decide upon for defining and presenting tasks. Definitely. There's also the possibility that an entire task will need to be made unavailable, either because every package (or every significant package) included in it is buggy, or in postgresql/task-database's case, because might only be available from non-US. I actually have been thinking since I posted the code about some enhancements to deal with cases where all the packages in a task, or at least some of the important ones, are missing. Noticing all are missing and not displaying the task in the list is easy enough. Noticing that the core packages of a task (postgresl, apache) are missing and deciding not to show the task is also doable, it really just requires one list of the key packages that mist be present, and another list of ancillary packages that can go missing w/o badly breaking the task. For comparison, using task- packages, if I remove the core packages from a task from woody, I can just also remove the task- from woody. This ought to be able to be done without modifying newtasksel, since, according to the freeze plans, newtasksel will be frozen (as part of the base system) while the tasks and their packages (as part of the standard system) are still be fixed or removed. Split out the task data and move it to a standard priority package then. Which means the task data won't be installed in the base system, and thus won't be available when base-config is run. Doesn't it? Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. ``_Any_ increase in interface difficulty, in exchange for a benefit you do not understand, cannot perceive, or don't care about, is too much.'' -- John S. Novak, III (The Humblest Man on the Net) PGP signature
Re: New Woody 2.3.2 boot images for sparc, need testing...
Ben Collins writes: Let me know how things go. It gets an illegal instruction immediately on my sb1000. Something is hosed with the TILO image I think. The 'linux-a.out' image, on the other hand, booted just fine on the machine. Later, David S. Miller [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem
Hi, I wonder if anyone could help me with an installation problem. I'm trying to install Debian 2.2r2 from CD onto an AMD based PC. This is a completely empty drive I'm installing to. So far I have seen the black screen with the help pages (and read them), pressed enter, seen lots of info whizz past, and arrived at a credits screen with the word Continue and a blinking cursor at the bottom of the page, just waiting to be pressed.. Problem is I can't press that Continue button, so have never gotten past this screen. No response to any keyboard or mouse commands from this screen, including Ctrl-alt-delete: I have to reboot via the reset button. Of course it did respond to the keyboard up until the enter command to start installation. System is an AMD Athlon processor with 256MB pc133 dram, a Seagate Medalist drive 13GB with a MS natural keyboard connected to the PS2 keyboard connector, and a USB optical mouse connected to 'the first USB port. I don't know what other system info might be relevant to this situation? I am a complete beginner with Linux, though I have successfully installed Red Hat on a previous machine and played with it a bit, and so I have a very basic idea about what to expect of Linux. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New Woody 2.3.2 boot images for sparc, need testing...
On Sat, May 12, Ben Collins wrote: Let me know how things go. http://auric.debian.org/~bcollins/disks-sparc/current/ For netboot, you should only need the tftpimage under the subarch directory of your choice. The rest of the install should be able to download everything else itself. If I look at the size of the Image: Could it be that tilo prints a warning about PROMs and 5MB or so ? The error messages I read here assumes this. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/[EMAIL PROTECTED] SuSE GmbHDeutschherrnstr. 15-19 90429 Nuernberg Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody install report
Fri, May 11, 2001 at 05:39:21PM +0200 wrote:
Hello,
On Monday I had to install my new box and decided to go for Woody
directly. This is my report.
thanks for the report.
Install
---
Ok, a normal floppies install. Oh, they were compiled for Spanish, so I
could review the state of the translation.
The install went flawless until modconf. There, first I noticed it
wasn't in Spanish, and nearly any module had a description (description
unavailable). I don't know why it wasn't in Spanish. manty said he got
it in Galician just right, and I thought Joey had updated the Spanish
translation.
This could be the problem, or at least the cause:
int configure_drivers (void) {
struct stat statbuf;
if (! NAME_ISEXE(/usr/bin/whiptail, statbuf))
symlink(/target/usr/bin/whiptail, /usr/bin/whiptail);
setenv(LANG, _(C), 1);
add_modules_from_floppy();
Anybody know why we're setting the LANG to 'C' here, modconf keys off that in
source_eval().
Anyway, the big thing in modconf was when I tried to select
8139too in the net section.
Selected the driver, pressed enter in the parameters dialog (without
typing anything) and then I got a huge flood in console 1, which I had
to stop with two ^C's. In C2 I saw there was a process,
mv mv /etc/modules.199 /etc/modules.
ick, not sure about that one.
In the network configuration, I had a small problem too. When I finished
introducing the data (the last thing is DNS, right?), the installer
froze.
The only thing I can think of on this one is that the DNS entered was something
that dbootstrap had trouble parsing, there are two while loops that it might
have gotten stuck in. I just tried a number of odd combinations of spaces,
numbers, etc, and couldn't recreate this. Do you remember anythng about the DNS
servers, more than one? Possible typos?
When I ^C'd, it gave me the welcome message, pressed enter and I
was back in the network configuration.
That's good behavior in response to ^C, but not good that it froze.
This time, there wasn't any
freeze and I could go on into installing the base system using network.
Using http.us.d.o (the default) wasn't nice, there are no Release files
That is wierd, it has always worked for me. This was probably when
http.us.debian.org was down, I think that is the unhelpful error message you get
if the first wget fails for any reason.
Rebooted, and after the first boot, I came across some other problems.
First, debconf would whine about libterm-stool not installed, but dialog
I'm hoping these are fixed in the new debconf.
So, last run of base-config (with no pauses this time), dselect ran,
which I ignored (installed nothing), and the installer threw me to the
first login prompt.
Immediately I upgraded to sid, and I guess that's the end of the story.
I had problems with the default kernel. When I was trying to configure
X, starting them would freeze my keyboard. I guess it was something with
X, but then I tried gpm and same results. Gpm started, keyboard lock.
Remotely killing gpm unlocked it. I just had to compile 2.4.4 and it
went away.
I'm assuming these keyboard/gpm problems were after you upgraded to sid so I'm
not going to worry about them for now.
I think there's little more to say, the box's been working
like a charm since I installed it.
Thanks,
David
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: woody release task needs help: package priorities
Bastian Blank [EMAIL PROTECTED] writes: On Sat, May 12, 2001 at 03:46:13AM -0400, Adam Di Carlo wrote: rcs few use it replace it with cvs rcs and cvs solve very different problems. They are by no means equivalent, and I use both, and I know lots of people who use both on a regular basis. Replacing it with cvs is silly. Removing it because 'few use it' seems wrong. Making cvs 'standard' in addition to cvs might have some merit. vacation why standard? fingerd not very secure for baseline ftpd not very secure for baseline lpr not very secure for baseline, poss use lprng? These fall, IMHO, under the /important/ description: Important programs, including those which one would expect to find on any Unix-like system. If the expectation is that an experienced Unix person who found it missing would say `What on earth is going on, where is foo?', it must be an important package. [4] Other packages without which the system will not run well or be usable must also have priority important. This does not include Emacs, the X Window System, TeX or any other large applications. The important packages are just a bare minimum of commonly-expected and necessary tools. Experienced UNIX people [not necessarily experienced Debian people] will become confused and critical when somethinglike the above are missing. why a print daemon? most user doesn't need such service A lot of people rate being able to print as very important part of using a computer. talk rather obsolete, but debatable talkd not very secure for baseline telnetd not very secure for baseline see above. wenglish I think it is only usefull with dict No, it has nothing to do with dict. I believe this is the package that provides /usr/share/dict/words, which has been around on UNIX systems [as /usr/dict/words] since before many developers were born. [see above...] kcr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
