Re: [RfS] Request for Submissions: Upcoming Debian Logo
Martin Schulze wrote: [a bunch of stuff I agree with, except] > . A logo is NOT a set of letters. Thus the string "Debian" rendered >very nice is ... a picture but not a logo. Forget that. Um, IBM's logo is just letters. Sun's logo is, well, just letters, technically. I wouldn't rule out a logo based on letters, but it should *be* a logo, which most of the entries in the GIMP contest aren't. -- Chris Waters [EMAIL PROTECTED] | I have a truly elegant proof of the or[EMAIL PROTECTED] | above, but it is too long to fit into http://www.dsp.net/xtifr | this .signature file.
Re: Debian Logo *Idea* Contest! (Delay for painting contest required)
Andreas Tille wrote: > So let us define first, *what* we want to show on our logo. > This is always the first step in software related things. Wy did > we step over it?? Actually, I tried to start with that. Look in the debian-devel archives for a thread entitled "Mascot for Debian" (or something like that). > Idea no. 1: Orca for Debian Um, this is actually idea number 24 or so. :-) We batted around a bunch of mascot ideas. I believe dolphins were suggested, but not Orca. OTOH, several people were objecting to the use of carnivores, which would disqualify Orca. :-) After watching the lengthy debate that ensued following my lone innocent post, I decided that we might as well allow the artists the freedom to propose ideas through their art, rather than trying to force them to render a pre-selected image. This follows the traditional Debian cry: "show me the code!" Those who actually *do* the work are in charge. :-) Here's a scattering of other proposals that came out of the earlier thread: 1. Dragon 2. Octopus 3. Monkey 4. Flying pig 5. Ant 6. Bee 7. Dolphin 8. Monkey 9. Eagle And that's just what I can recall without browsing the thread. A number of those had, er, philosophical arguments behind them, much as you had with your proposal. My suggestion: if you like the idea of Orca, create a logo and submit it. Note that the fans of the octopus and the bee already have logo submissions in the Gimp contest. -- Chris Waters [EMAIL PROTECTED] | I have a truly elegant proof of the or[EMAIL PROTECTED] | above, but it is too long to fit into http://www.dsp.net/xtifr | this .signature file.
Re: Intent to Party like its 1999
Disclaimer: I live in San Jose. :-)
But still, if this is supposed to be a post-Linuxworld gettogether,
wouldn't it make the most sense to have it *near* Linuxworld?
Convenient for people visiting the area for Linuxworld and staying in
nearby {h,m}otels, convenient for people attending Linuxworld from
around the bay. Inconvenient only for those who aren't going to
Linuxworld and aren't nearby.
If this *isn't* really supposed to be a post-Linuxworld gettogether (I'm
a little confused, since I think this thread started with a mention of
the *IRC* party), then maybe Oakland or SF would be reasonable. But in
that case, I'd like to propose that we have one or more post-Linuxworld
gettogethers near Linuxworld. The south bay has plenty of nice spots.
Do we want coffee, bheer, or bhoth?
Traffic is another issue, and one that would tend to suggest that we not
go too far from the convention center till later, i.e. *after* the
gettogether when we're heading toward home (or temporary equivalent).
Bay area traffic is extremely bad, if not world-class bad quite yet
--
Chris Waters [EMAIL PROTECTED] | I have a truly elegant proof of the
or[EMAIL PROTECTED] | above, but it is too long to fit into
http://www.dsp.net/xtifr | this .signature file.
Re: Intent to Party like its 1999
David Bristel writes: > Well, if you wanted to get into downtown San Jose from Caltrain, you > can take Caltrain into Santa Clara. [and take a bus a long way to light rail] Huh? Caltrain goes to San Jose. It stops right by the Arena, which is only a few blocks from downtown and light rail (and the convention center, and etc.). And the SJ train station is a major hub for bus lines. SJ to or from SF is pretty easy. Kevin Dalley writes: > People tend to forget how spread out the Bay Area really is. Yes, and the only centrally located area is underwater. :-) One advantage of doing this in the south bay is that, for most people in or out of the south bay, you're going opposite to the normal flow of commuters. Which means less traffic, less crowding on public transit, etc. Plus, if we meet reasonably near the convention center, it'll allow people to scout out routes to the convention center, and may allow people staying nearby for Linuxworld thingie to attend, if they've arrived early. OTOH, if we weight the bay area by number of packages, then obviously we should meet at Joey Hess's house. If debian packages had mass, Joey's computer would be inside a Schwarzchild radius. :-) -- Chris Waters [EMAIL PROTECTED] | I have a truly elegant proof of the or[EMAIL PROTECTED] | above, but it is too long to fit into http://www.dsp.net/xtifr | this .signature file.
Re: slashdot.org linux distribution poll - vote for debian
Gary L. Dolan wrote: > > Joey Hess wrote: > > > > > > At http://www.slashdot.org/, there is a poll of favorite linux > > > distributions. I encourage you all to go vote for debian, which is > > > currently > > > trailing redhat by about 50 votes. > > I just went and voted, and it worked fine, shows debian at 118 and > red hat at 154. My vote put us over the top, at least for the moment -- debian 200, redhat 199! :-) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Rebuilding the kernel
Andrew Akins wrote: > I've read all the howtos and got all the files, so I'm pretty sure I > have a good idea of how to do it (but I'm open to suggestions, if anyone > has them). When I followed the directions, everything worked fine. Easy as pie. > My problem is this - my &*$#&$ laptop manual doesn't say what the > settings of my ESS688 sound chip are (IRQ, Mem base, etc). And I no > longer have any other OS on my machine (I dived into Linux head > first...), so I have no easy way of running a program to find out. You might be able to figure it out by poking around in the /proc filesystem. I don't have a soundcard, so I can't tell you if this will actually help. > The menuconfig script is asking me for these settings (obviously) Aren't there some sort of defaults? If the default kernel worked... >...if I provide the wrong numbers, will the machine boot (without sound), > or will it completely crash? I doubt if it will crash, though I might try to avoid specifying any interrupts or whatevers that are in use by *another* device. Good advice for anyone doing major surgery on any *NIX system is to have a rescue disk or something you can boot if everything goes south. If your surgery involves the kernel, make sure you know how to restore the kernel from your rescue disk. If you do all that, the answer to your question becomes: who cares? Try it and see! :-) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: PLEASE: standard package README file/orientation
On Sat, Aug 19, 2000 at 03:23:22PM -0400, Daniel Barclay wrote: > Why don't all Debian packages come with installation instructions > in a _standard_ place that tell you what you need to do (after > installing the package) to configure or use the package you just > loaded? Most Debian packages don't need additional configuration after they've been installed. (A pretty big majority also have binary names that match the package names.) > PLEASE think about what happens right after users install a > package: > They know the name of the package. Yes. > They don't necessarily know the name of any commands, other > executables, or configuration files provided by the package. > Therefore, they can't use any of those names to try to find any > manual pages for those the package. Yes, they can: dpkg --listfiles pkgname > There needs to be root documentation for each package that contains > or points to information on: For "each package"? I don't think so! The great majority of packages do not need any such documentation. I think it would be extremely pointless for me to add a file saying "To run ted, type 'ted'. To configure 'ted', type 'ted' and then use the menus. To see the documentation, type 'man ted' or type 'ted' and click on 'Help'." If we do this for every package in the system, we add a bunch of useless, bloated crap to the system. Furthermore, it's just one more thing to worry about and to have get out of sync with reality. Now, for those packages where it isn't easy to figure out what to do (and where dpkg --listfiles doesn't help), there should be some information in /usr/share/doc/README.Debian or something. If you find such packages, and they aren't adequately documented already, I suggest that you file wishlist bug reports. But let's not go overboard here. Making this a requirement for all packages is just silly. I venture to guess that 80% of all packages have a binary that matches the package name, and don't need *any* (re)configuration. And of the remainder, most do have adequate documentation already. cheers -- Chris Waters [EMAIL PROTECTED] | I have a truly elegant proof of the or[EMAIL PROTECTED] | above, but it is too long to fit into | this .signature file.
Re: package compilation madness
Drew Parsons <[EMAIL PROTECTED]> writes: > Running on the theory that it might help speed up my Pentium II system > (debatable, but that's beside the point), I've tried > recompiling a selection of packages with pentium optimisation, downloading > the debian source and running `./debian/rules binary`. > However, after having done this, every time I `apt-get upgrade`, these > packages get downloaded from the debian ftp server Ok, 1) this isn't really a laptop issue, and 2) yes, you're correct. Apt will assume you want the most up-to-date package, and, since the package on the ftp server is newer than the one you built, it gets preferred. The easy solution is to put the package on hold -- but this has the disadvantage that you *don't* get newer versions at all. Actually, it's not really about "newer", it's about having a version number that sorts later, so, one possibility is to use a special version number that will always sort later. This is the trick suggested for custom kernels. Thus, you could make bzip 0.9.5d-my2 or even my-0.9.5d-2. The former would stick until a new upstream release, the former would stick basically forever (unless the debian maintainer increases the "epoch", which we won't get into now). This doesn't just happen with pentium-optimized packages. It happens any time you make a local custom version of a package. What I'd really like to see is a way to flag a package as "maintained locally". Ideally, this would make apt download the source when a new version appears, merge it into your local CVS repository, wait for you to resolve any conflicts, then build and install the package. There's a little bit of work involved for that to happen though :) For now, putting the package on hold is probably your best bet. cheers (This thread really belongs on debian-user, so I've set the reply-to field.) -- Chris Waters [EMAIL PROTECTED] | I have a truly elegant proof of the or[EMAIL PROTECTED] | above, but it is too long to fit into http://www.dsp.net/xtifr | this .signature file.
Re: package compilation madness
Drew Parsons <[EMAIL PROTECTED]> writes: [with an unattributed quote from Chris:)] > > That's no excuse for off-topic posts! I mean, by that logic, > > *everyone* should move all their questions to deb-laptops. > Everyone who has a laptop. No -- general questions about Debian that aren't specific to laptops should go in more general forums. Otherwise, -laptop will soon become just as difficult to follow as -user. > Why should I think I'm special? I'm not the only one with a laptop. I > speak for anyone who does have one, and wants keep their laptop running > optimally. Anyone using Debian might have been interested in the topic. But since you only posted to -laptop, that means that only people using laptops will benefit from the information. Which is rather unfair, IMO. If you have problems with the volume of mail on -user (and I confess, I do too), you can simply use either a newsreader or web browser to skim for the answers to questions you ask there. > > Note: since this is a flame, I posted it off list. But I'm not really > > mad, so, if you ask me again off-list, I might actually answer your > > question. :) > OK, I'm listening... Actually, someone else already answered: yes, the version number that dpkg uses is extracted from the debian/changelog file. Renaming the deb won't have any effect. So, if you want to override a package, you need to edit this file, and create a new entry with a version number that will sort later than any future revisions. E.g. if the official Debian package is 2.3-6, and you want your privately built package to take precedence, you'd have to make a changelog entry that sets the version number to, e.g. "my.2.3-7". Note: I sent this to the -user list, in case others have been struggling with the same question. (Note to anyone reading it there -- I'm not on -user, so followups may need to be cc'd to me.) cheers, Chris -- Chris Waters [EMAIL PROTECTED] | I have a truly elegant proof of the or[EMAIL PROTECTED] | above, but it is too long to fit into http://www.dsp.net/xtifr | this .signature file.
