Linux-Misc Digest #679, Volume #24 Thu, 1 Jun 00 21:13:03 EDT
Contents:
Re: Zip for Linux (brian moore)
Re: Zip for Linux (Hal Burgiss)
Re: recursively deleting selected files ("Andrew N. McGuire ")
Re: Is identd necessary ? (lobotomy)
Re: Is identd necessary ? (Hal Burgiss)
pctel 'linmodem' driver with 2.2.15 problem (lobotomy)
Re: Need Netscape killer... (David Efflandt)
Re: Only one channel in CD Player.... (David Efflandt)
Installing Caldera 2.4 (Martin Racette)
Re: libraries philosophy under linux (Christopher Browne)
Re: Announce: Motif release to Open Source Community leads to Open Motif
Everywhere (Christopher Browne)
Re: HP-UX vs. Linux (Christopher Browne)
Re: Problem with no valid display modes. (David Efflandt)
Re: Need ideas for university funded project for linux (Christopher Browne)
Re: Need ideas for university funded project for linux (Christopher Browne)
Re: Video Trouble (David Efflandt)
Re: ASUS K7V KX133 motherboard problems (F. Heitkamp)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (brian moore)
Subject: Re: Zip for Linux
Date: 1 Jun 2000 23:19:20 GMT
On Thu, 01 Jun 2000 10:16:46 GMT,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Where can I find the zip utility for Linux ?
On debian, 'apt-get install zip unzip' (I would assume you want unzip,
since that was the original question.)
I believe Slack includes it (it used to anyway) and would be shocked if
other distributions didn't. See your distribution or rpmfind.net or
freshmeat.net.
> Please send your reply to [EMAIL PROTECTED]
No thanks. Read here for replies.
--
Brian Moore | Of course vi is God's editor.
Sysadmin, C/Perl Hacker | If He used Emacs, He'd still be waiting
Usenet Vandal | for it to load on the seventh day.
Netscum, Bane of Elves.
------------------------------
From: [EMAIL PROTECTED] (Hal Burgiss)
Subject: Re: Zip for Linux
Reply-To: [EMAIL PROTECTED]
Date: Thu, 01 Jun 2000 23:27:29 GMT
On Thu, 01 Jun 2000 10:16:46 GMT, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>Where can I find the zip utility for Linux ?
>Please send your reply to [EMAIL PROTECTED]
[hal@feenix hal]$ which zip
/usr/bin/zip
Maybe you have it?
--
Hal B
[EMAIL PROTECTED]
--
------------------------------
From: "Andrew N. McGuire " <[EMAIL PROTECTED]>
Subject: Re: recursively deleting selected files
Date: Thu, 1 Jun 2000 18:42:11 -0500
On 1 Jun 2000, Lee Doolan wrote:
+ >>>>> "Andrew" == Andrew N McGuire <" <[EMAIL PROTECTED]>> writes:
+ [. . .]
+ Andrew> Yikes! From the current working directory:
+
+ Andrew> find . -type f -name '*.class' -exec rm {} \;
+
+ this is wasteful. try
+
+ find . -type f -name '*.class' -print | xargs rm -f
+
+ it's much quicker.
True, but I wasn't trying to be quicker... Just simpler.
The poster i responeded to used this...
for i in $(find /yourdirectory -name '*.class' -printf "%p%n "); do i
rm $i
done
I was just pointing out an easier way, and was not concerned with
speed.. But yes, using xargs is *much* faster. :-)
anm
--
/*-------------------------------------------------------.
| Andrew N. McGuire |
| [EMAIL PROTECTED] |
`-------------------------------------------------------*/
------------------------------
From: [EMAIL PROTECTED] (lobotomy)
Subject: Re: Is identd necessary ?
Date: Thu, 01 Jun 2000 23:46:00 GMT
You will want it if you ever plan on using IRC. Not only do many
servers require it, but you will be automatically kicked from the
#linux channel if you come in without it.
On Thu, 01 Jun 2000 14:28:52 GMT, [EMAIL PROTECTED] wrote:
>Hi,
> I have identd as a default in my startup sequence.
>Since it is the slowest daemon to load, I would like to know if it is
>necessary to load it for normal activity, such as using intenet, using
>email and normal things like these.
>If not, I will surely exclude it from the startup process.
>
>Thanks.
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
------------------------------
From: [EMAIL PROTECTED] (Hal Burgiss)
Subject: Re: Is identd necessary ?
Reply-To: [EMAIL PROTECTED]
Date: Thu, 01 Jun 2000 23:48:12 GMT
On Thu, 01 Jun 2000 23:46:00 GMT, lobotomy <[EMAIL PROTECTED]> wrote:
>You will want it if you ever plan on using IRC. Not only do many
>servers require it, but you will be automatically kicked from the
>#linux channel if you come in without it.
A lot of mail servers like it too (though it may not be necessary).
>On Thu, 01 Jun 2000 14:28:52 GMT, [EMAIL PROTECTED] wrote:
>
>>Hi,
>> I have identd as a default in my startup sequence.
>>Since it is the slowest daemon to load, I would like to know if it is
>>necessary to load it for normal activity, such as using intenet, using
>>email and normal things like these.
>>If not, I will surely exclude it from the startup process.
Try it and see.
--
Hal B
[EMAIL PROTECTED]
--
------------------------------
From: [EMAIL PROTECTED] (lobotomy)
Subject: pctel 'linmodem' driver with 2.2.15 problem
Date: Thu, 01 Jun 2000 23:53:48 GMT
I have been using a Zoltrix Phantom 56k winmodem (yes I know it is
junk and I should get a real modem...but it was really cheap and it
does generally work...) under RH6.0 with the pctel 'linmodem' driver
for some time (with the included 2.2.5-something kernel) for some
time, and it has worked reasonably well. I upgraded to 2.2.15
recently, and recompiled the pctel module for it as well. I don't
think the configuration is much different than before, other than
enabling svga text mode and compiling in the sound and iomega drivers,
but now whenever it accesses the modem, it gives a segmentation fault.
Is there any known workaround, or will I just have to live with 2.2.5
until I replace the modem?
------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Subject: Re: Need Netscape killer...
Date: 1 Jun 2000 23:53:47 GMT
Reply-To: [EMAIL PROTECTED]
On 1 Jun 2000 21:55:29 GMT, Andrew Purugganan <[EMAIL PROTECTED]> wrote:
>i need a simple script that would be monitoring the netscape job before
>it starts thrashing my hard drive. It happened again while I left several
>Nscape windows running (well, open if you will). Even switching to
>a VC with root couldn't help me in time, not even to do a killall; it had
>gotten too far along already.
Normally Netscape only runs away if you exit X with it still running (top
would tell you what is hogging your cpu at that point). But some bad
pages might do that too. But 'killall netscape" will not kill it.
Actually I am not sure if kill -15 works, I think you have to use kill -9
to kill off the netscape process or any remainders that do not die.
>BTW Nscape 4.61 I think on Mandrake 6.0 but kernel 2.2.13-22mdk or
>something like that
>Have you written anything like this, I would appreciate any assistance
I haven't really written a script for that because you only have to kill
off one or two pocesses to get rid of it.
--
David Efflandt [EMAIL PROTECTED] http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://hammer.prohosting.com/~cgi-wiz/ http://cgi-help.virtualave.net/
------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Subject: Re: Only one channel in CD Player....
Date: 2 Jun 2000 00:03:13 GMT
Reply-To: [EMAIL PROTECTED]
On Thu, 01 Jun 2000 16:30:07 GMT, NTK <[EMAIL PROTECTED]> wrote:
>With Helix Gnome 1.2 and MKD 7.1 beta3, I only hear one channel when I
>play a music CD. But, all EVENT SOUNDS are played on both channels. Is
>this something to do with the actual hardware? But seems to me it is
>more of a software problem. I tried a couple of differenct CD Player,
>but same result. Any ideas?
There is usually a separate cable that connects directly from your cdrom
to your soundcard for CD music. But sound files are played through the
software sound drivers. That is why some people who do not even have
sound configured can play CD music. So it is quite possible that you have
a hardware problem. Maybe when you did something in the box (add drives,
etc) you pulled a wire loose.
But it is also possible that you messed up a mixer setting. Usually you
can switch between adjusting the volume of both channels or each one
individually and maybe your 2 CD channels are not matched. Or maybe
something got switch to mono.
--
David Efflandt [EMAIL PROTECTED] http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://hammer.prohosting.com/~cgi-wiz/ http://cgi-help.virtualave.net/
------------------------------
From: Martin Racette <[EMAIL PROTECTED]>
Subject: Installing Caldera 2.4
Crossposted-To: alt.os.linux.caldera,comp.os.linux.question
Date: Fri, 02 Jun 2000 00:07:06 GMT
Hi guys
I'm having a weird problem, when I try to Install Linux Caldera 2.4,=20=
the installation goes all the to the end without any problem, I can=20
even use it the first time, but there it stop
When I try to boot Linux again I get an error that says something like=20=
"The Partition is not formatted", when I boot with the floppy I can=20
see everything on the partition but I can't use anything, and not even=20=
boot Linux
My set-up is :
DISK 1
Bootmanager (OS/2 WARP, Windows, Linux)
OS/2 Warp 4
Windows
D:, E:, F:, G: (Which are for OS/2 only, HPFS)
DISK 2
LINUX
LINUX SWAP
H: (HPFS)
I: (FAT16)
J: (HPFS)
K: (HPFS)
DISK 3 (ZIP Drive)
All my HDD and the ZIP Drive are SCSI
Any help would be appreciated
Thank you in advance
Merci a l'avance
Martin
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Subject: Re: libraries philosophy under linux
Reply-To: [EMAIL PROTECTED]
Date: Fri, 02 Jun 2000 00:16:12 GMT
Centuries ago, Nostradamus foresaw a time when [EMAIL PROTECTED]
would say:
>To be more synthetic, these are my questions:
>o How can I use (old) programs with a new distribution without
>installing tons of unuseful libraries and without getting the last
>version of the program itself ?
Recompile the programs using the source RPMs.
That will mean that they use the libraries you've got, thus
eliminating any need to worry about looking for old libraries.
--
[EMAIL PROTECTED] - <http://www.hex.net/~cbbrowne/>
Rules of the Evil Overlord #48. "I will treat any beast which I
control through magic or technology with respect and kindness. Thus if
the control is ever broken, it will not immediately come after me for
revenge." <http://www.eviloverlord.com/>
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Subject: Re: Announce: Motif release to Open Source Community leads to Open Motif
Everywhere
Reply-To: [EMAIL PROTECTED]
Date: Fri, 02 Jun 2000 00:16:27 GMT
Centuries ago, Nostradamus foresaw a time when Chuck Dillon would say:
>They are not trying to compete with Qt, GTK, GNOME... They are trying
>to pave the way for UNIX ISVs to bring their products to 'Open Source
>platforms'. Most likely to prevent those ISVs from abandoning Motif
>for another GUI solution.
Sounds reasonable.
>But Motif was already there at little cost, about $120 bucks, from a
>solid vendor (MetroLink). If someone is going to shell out cash for
>significant UNIX products that $120 isn't going to be a problem.
>Reducing or eliminating that $120 isn't going to contribute much to the
>above stated goal. The ISVs could eliminate that cost by statically
>linking to libXm. But statically linking doesn't scale well as the
>number of 3rd party dependencies increases. Statically linking is a
>bad thing.
... But it _does_ guarantee that you've got a compatible version ...
The unfortunate thing would be if four "in use" versions of libXm
proliferated, as _that_ would lead to people needing to have four
copies installed to expect apps to run, not unlike the several LIBC5
and LIBC6 libs that people often have around.
>So if the cost of MetroLink's Motif isn't the barrier what is it and
>how does 'Open Motif' address it?
Good observation (on the $120) and a good question.
>It seems to me that the barrier is the dependency on too many system
>vendors, IOW, too many independent variables. It seems to me that what
>this is intended to do is to make it possible for LINUX distributors to
>bundle and support standard Motif so that ISVs can take that
>independent variable off their list.
Ah. I think you've hit the nail on the head. This is a _good_
explanation for the policy.
>This is what the LSB is all about. The logical next step is for the
>LINUX vendors and the LSB to embrace 'Open Motif'. That doesn't mean
>they make Motif exclusively the LSB GUI of choice. It just means they
>make sure that an LSB compliant system will provide the Motif runtimes.
>The big question is whether the 'Open Motif' license will be a
>problem. I'm guessing that the Open Group wouldn't have made this move
>unless they had some assurance that it would not be a problem.
I suppose it begs the question of whether or not "OpenMotif" will
actually become part of the LSB.
It will almost certainly _not_, with present licensing, become part of
Debian "main," and thus apps that depend on it won't be able to be in
"main."
Of course, those that are likely _interested_ in Motif are, as you
suggest, ISVs, whose applications doubtless won't be public. In
effect, they won't _need_ to care about this restriction.
And if most newer apps are deployed using GTK (which is getting fairly
common; witness ApplixWare), there's not a _big_ downside to having a
very static OpenMotif library.
Happily, _that_ has a further merit, namely that it means there's not
likely to need to be a bunch of versions of libXm.so out there.
I think the net effect that the desire will _not_ be to put
improvements in, or to "clean Motif up" of the cruft that has
collected, but rather to just plain keep the legacy stable.
Availability of source code has the merit that if people run into
thorny problems with Motif, even if they can't expect to see bugs
fixed, at least they can look at the code and know exactly what it is
that they're working around. That's not the case today for those that
use binary deployments of Motif libs.
On balance, I think I'm starting to like the approach that has been
taken....
- It provides source, which enables developers to better work around
the problems;
- It is sufficiently "under the thumb" of TOG that it has a "force to
help keep it the same," e.g. - stay "stable" (even if ugly);
- It _isn't_ "free software," which discourages "free software folk"
from trying to create hacked versions for their own purposes;
- Despite not being "DFSG-Free," it's "free enough" to become
ubiquitous on Linux (and *BSD), which is supportive of ISVs and
LSB, and the "stability" needs thereof.
I'm not sure we should expect, or even _want_ to expect, a freer
license.
--
Windows 'XCV - A 32 bit patch for a 16 bit interface to an 8 bit OS
designed for a 4 bit chip from a 2 bit company that can't stand 1 bit
of competition...
[EMAIL PROTECTED] <http://www.ntlug.org/~cbbrowne/lsf.html>
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Subject: Re: HP-UX vs. Linux
Reply-To: [EMAIL PROTECTED]
Date: Fri, 02 Jun 2000 00:16:28 GMT
Centuries ago, Nostradamus foresaw a time when Ben Chauss� would say:
>Do you know what is best between HP-UX and Linux. We want to create a
>web server, and we would like to know what is best does two one ????
I think you'll find that HP-UX runs much better on PA-RISC boxes than
Linux does.
And that Linux runs much better on IA-32 boxes than HP-UX does.
--
"Rather than complaining, I suggest shopping where Linux is
appreciated." -- Phil Hughes <[EMAIL PROTECTED]>
[EMAIL PROTECTED] <http://www.ntlug.org/~cbbrowne/lsf.html>
------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Subject: Re: Problem with no valid display modes.
Date: 2 Jun 2000 00:17:21 GMT
Reply-To: [EMAIL PROTECTED]
On Thu, 01 Jun 2000, ~=Darek M=~ <[EMAIL PROTECTED]> wrote:
>Hi, startx gives me the following error:
>
(snip)
>(--) SVGA: PCI: Trident TGUI 96xx rev 211, Memory @ 0xe5000000,
>0xe5400000
>(--) Trident chipset version: 0xd3 (TGUI96xx)
>(--) SVGA: BIOS reports Clock Control Bits 0x0
>(--) SVGA: Detected a Trident 9680.
>(--) SVGA: Revision 1.
>(--) SVGA: Using Trident programmable clocks
>(--) SVGA: chipset: tgui9680
>(--) SVGA: videoram: 2048k
>(**) SVGA: Using 8 bpp, Depth 8, Color weight: 666
>(--) SVGA: Maximum allowed dot-clock: 135.000 MHz
>(--) SVGA: There is no mode definition named "640x480"
>(--) SVGA: Removing mode "640x480" from list of valid modes.
>(--) SVGA: There is no mode definition named "800x600"
>(--) SVGA: Removing mode "800x600" from list of valid modes.
>(--) SVGA: There is no mode definition named "1024x768"
>(--) SVGA: Removing mode "1024x768" from list of valid modes.
>(--) SVGA: There is no mode definition named "1280x1024"
>
>Fatal server error:
>No valid modes found.
>
>My monitor manufacturer says that the monitor I have can do
>1024x768 at 60kHz 75Hz and at 68.7kHz 85Hz. How do I specify the
>vertical and horizontal refresh rates in /etc/XF86Config.
>
>Here is some info out of the XF86Config file:
>
>%%%%%%%%%%%%%%%%%%
>Section "Monitor"
>
> Identifier "Dell"
> VendorName "Dell"
> ModelName "D82dTM"
>
> HorizSync 30-70 //these are the values specified
> VertRefresh 50-120 //by Dell, I put those in manually
You don't actually have the // and following text on those lines in your
real XF86Config file do you? That might be what is messing you up. Try
clean lines or put the comment on a separate line beginning with '#'
like this:
# These are the values specified by Dell, I put those in manually
HorizSync 30-70
VertRefresh 50-120
Also make sure that nothing in the file accidently word wrapped that
should not be.
--
David Efflandt [EMAIL PROTECTED] http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://hammer.prohosting.com/~cgi-wiz/ http://cgi-help.virtualave.net/
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Crossposted-To:
comp.os.linux.development,comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.advocacy
Subject: Re: Need ideas for university funded project for linux
Reply-To: [EMAIL PROTECTED]
Date: Fri, 02 Jun 2000 00:17:16 GMT
Centuries ago, Nostradamus foresaw a time when Donovan Rebbechi would say:
>On Wed, 24 May 2000 11:14:50 -0600, Praedor Tempus wrote:
>
>>And the right to fork is good because...?
>
>Because if the maintainer abandons or neglects a project, someone else
>can pick it up. However, while "the right" to fork is a good thing,
>that doesn't mean that gratuitous forking is a good thing.
>
>ESR talks about this kind of thing and uses the phrase "promiscuous
>theory, puritan practice", I think the essay is "homesteading the noosphere".
>
>Some examples of "good" forks include egcs ( which I believe has been handed
>back to the FSF. egcs-c++ is a vast improvement over g++ ) and x-emacs.
"When Umberto Eco classified the Mac OS as catholic and DOS as
protestant, he unleashed a minor religious war."
<http://lwn.net/1999/0114/a/wizards2.html>
I can't locate the web page where I saw this, but recently saw where
someone took the analogy of a code fork as a would-be "Protestant
Reformation," where you start with the One True Catholic Code Base,
and fork off a Protestant version.
The analogy is remarkably good...
- As with Martin Luther, the point of the exercise is _not_ primarily
to start wars (though that may well happen), but rather to reform
the things seen as "broken" in the catholic tradition.
- As with the wars between Catholics and Protestants, _violent_
disputes tend to arise over matters on the periphery from the
reasons why the split took place.
- The fact that people _can_ get worked up over code forks means that
they are sufficiently committed to whatever software is in question
as to suggest that there is a "religious-like" fervor.
Mind you, there have been rather fewer people outright _killed_ in the
disputes of Software Protestant Reformations...
>> Because it is GOOD to fragment software and libraries so that apps
>>fail to work nicely? So that if you
>
>Like I said, the fact that the right to fork is a good thing doesn't
>mean that forking for the sake of it is a good thing.
The Protestant Reformation didn't happen because all was well and
good; it was a reaction to some _significant problems_ in the Catholic
Church.
Similarly, code forks do not occur as an inherent good; they happen as
what is considered, at least by the reformers, as a "lesser of evils."
>>the unix baby early on. It is brought up as a fear of something that
>>could possibly kill linux (for general use...but then, there are
>
>The fragmentation that exists within Linux has very little to do with
>forking. THe main problem is that there is a lack of standardisation
>on versions of the different APIs.
There are some of the APIs _within_ Linux (e.g. - VFS, kernel modules)
where nobody has gotten arrogant enough to consider that they may
speak "Ex Cathedra" to indicate that they signify "authoritative
teaching."
>>I would like a nice, clear explanation of why forking should be
>>considered >good.
>
>Your confusing "the right to fork" with forking itself. The right to fork
>is one that should be exercised judiciously.
>
>>Standards
>>make coder's lives easier, make user's lives easier. SOME things should
>
>The main problem at the moment ( at least wrt Linux ) is not about forks,
>but it's about failure of the distributors to use the same versions of
>core components such as glibc, the compiler, and other shared libs.
Actually, this _isn't_ a persistent failure that they are suffering
from. If it represented a failure, then it _would_ result in forks.
They are all "suffering" from the fact that the core components
continue to be developed, and that releases of those components do not
happen in a "lock step" manner that is well-synchronized with when
distribution makers decide to "make golden" _their_ releases.
So long as the distributions have independent "source trees," which
are being independently updated from the _true_ sources (e.g. -
periodically pulling updates from what Ulrich Drepper does with
GLIBC), they will "suffer" from this problem.
In contrast, when multiple distributions are able to treat a single
maintained source tree as "their canon," as is, to a great extent,
true for the Debian-based distributions, this diminishes the
differences.
An _encouraging_ bit of news is that SuSE has plans to use SourceForge
as their "compile server," which presumably means that they'll have
substantially _all_ of their sources sitting there, and thereby means
that _that_ tree represents a "publicly available canon" not unlike
those published by Debian, FreeBSD, OpenBSD, and NetBSD.
>As far as the developers are concerned, there is not much difficulty writing
>code that will compile on any Linux distribution. Also, KDE and GNOME make
>writing for multiple distributions or even UNIX flavours pretty easy.
>Basically, you can use "GNOME" or "KDE" as your target platform. If you
>use glib data types or QT classes and the KDEsupport stuff, you usually don't
>really need to worry about the peculiarities of your target platform.
I'd go along with GLIB as being a helpful thing; it qualifies as a
library that has been around long enough to have fairly much
stabilized.
On the other hand, other components of KDE/GNOME are still pretty much
of "alpha test" quality. (Bonobo and GNOME-print come to mind...)
>However, failure to standardise on lib versions, compilers and
>package managers makes releasing binaries for multiple distributions
>a bit of a pain.
A failure of there to _be_ One True Library Version is the problem.
By the way, the introduction of XFree86 4.0 is going to cause much the
same problem for distribution makers over the next six months or so.
At this point in time, the 4.0 release is "only really suited to those
happy to play with code," as it lacks the config tools as well as some
device drivers that is needed for it to be considered "generally
available."
Yes, there are RPMs out there, but if you're not prepared to fiddle
with config files by hand, and to trouble-shoot, it is best to beware
of it at this point.
Give it a few months for work to start to solidify on the config
tools, and aficionados will be clamouring for Red Hat to rush to
"include it now!"
My prediction is that whomever first _sells_ a distribution that
contains XFree86 is likely to rush it into place _far_ too quickly,
and that _horrible_ things will be said about them. RHAT has a
history of this, to some extent; they adopted GLIBC 2.0, an
experimental version, and got bashed pretty heavily over the problems
that arose not only with incompatibilities between GLIBC 2.0 and LIBC
5.4.x, but also with the "production" release of GLIBC, 2.1.
--
[EMAIL PROTECTED] - <http://www.hex.net/~cbbrowne/>
"never post anything you don't want to see on your resume..."
-- Martin Minow <[EMAIL PROTECTED]>
------------------------------
From: [EMAIL PROTECTED] (Christopher Browne)
Crossposted-To:
comp.os.linux.development,comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.advocacy
Subject: Re: Need ideas for university funded project for linux
Reply-To: [EMAIL PROTECTED]
Date: Fri, 02 Jun 2000 00:17:18 GMT
Centuries ago, Nostradamus foresaw a time when [EMAIL PROTECTED] would say:
>"Anthony W. Youngman" <[EMAIL PROTECTED]> writes:
>> In other words, it's not the package maintainer's fault if the
>> maintenance package has no way of correctly marking-up the dependency.
>
>I don't really understand how this can be so. If the required bit is
>set, the package is required; if it's not, it's not. Even the most
>basic usable package-management system has to have at least these two
>states.
Other possibility:
- System has a "base" package that may exist only to establish
Forcible Dependancies.
- The tools are designed to filter out references to "base," or
perhaps to be aware that If You Try To Delete Base, This Is A Very
Bad Thing, And You Should Be Told Of The Danger, Given Every
Possible Opportunity To Recant...
- "Base" then has dependancies that establish the need for some
mandatory set of packages without which the system cannot function
at all.
In the dependancy system, deleting Base would then trigger deleting
all of the packages that depend on it (much like an SQL "ON DELETE
CASCADE" constraint).
When that request to nuke out one package results in _every_ package
on the system leaping onto the "list of stuff to delete," methinks
this can show the gentle user that they may be making a mistake.
No "state" required; merely dependancies...
--
[EMAIL PROTECTED] - <http://www.hex.net/~cbbrowne/>
Rules of the Evil Overlord #227. "I will never bait a trap with
genuine bait." <http://www.eviloverlord.com/>
------------------------------
From: [EMAIL PROTECTED] (David Efflandt)
Subject: Re: Video Trouble
Date: 2 Jun 2000 00:23:22 GMT
Reply-To: [EMAIL PROTECTED]
On Thu, 01 Jun 2000, Boddhisatva Troutwaxer
<[EMAIL PROTECTED]> wrote:
>I've just installed Red Hat 6.1 on a Toshiba Satellite 415CS
>Laptop with a Chips & Technologies CT65548 video chip with one
>meg of memory. When I start X with this configuration I get a
>correct set of colors and readable type, but it does not cover my
>entire screen. The right 1/5th of the screen is blank. I have
>this problem regardless of whether I use a 640x480 or 800x600
>screen. Has anyone run into this problem before? (The screen
>works properly at 800 X 600 with 256 colors in Windows, so I am
>assuming for now that there is nothing wrong with the hardware.)
I am not familiar with that particular computer or chipset, but which LCD
monitor did you select? If the max resolution of your monitor is 800x600
did you select the LCD 800x600 monitor.
I have a Sony and I selected LCD 1024x768 monitor because that is my max
resolution. It stretches 800x600 or 640x480 modes to fill (or nearly
fill) the screen (though fonts in those modes are less than perfect).
--
David Efflandt [EMAIL PROTECTED] http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://hammer.prohosting.com/~cgi-wiz/ http://cgi-help.virtualave.net/
------------------------------
From: [EMAIL PROTECTED] (F. Heitkamp)
Date: Thu, 1 Jun 2000 20:37:04
Subject: Re: ASUS K7V KX133 motherboard problems
Reply-To: [EMAIL PROTECTED]
In message
<[EMAIL PROTECTED]> -
[EMAIL PROTECTED] writes:
>
>Ryan Sackenheim <[EMAIL PROTECTED]> writes:
>
>
> Mostly people reported no problems, and some of them had the
>K7V motherboard. I'm interested because I'm seriously thinking about
I have a ABIT KA7 with 650 Athlon. I pulled my SCSI drives and controller
from my old PI200 and plugged them into the Athlon system. After a
few little problems related to my own ignorance, I got the system
working. I've had several hard lockups (no warning) both using X
and just console. They've appeared to be related to heavy disk
thrashing between my SCSI drives. I just got a heavy duty PS to
see if that helps as I heard the Athlon needs lots of stable power.
I have a linux 2.2/glibc-2.1.3 system that used to be Slackware
a long, long time ago. There is very little if any Slackware left
though.
Fred
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.misc) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Misc Digest
******************************
