Linux-Advocacy Digest #309, Volume #35           Sat, 16 Jun 01 17:13:05 EDT

Contents:
  Re: Will MS get away with this one? (Peter Hayes)
  Re: Why homosexuals are no threat to heterosexuals ("Aaron R. Kulkis")
  Re: Linux inheriting "DLL Hell" ("Ayende Rahien")
  Re: Linux inheriting "DLL Hell" ("Ayende Rahien")
  Re: Linux inheriting "DLL Hell" ("Ayende Rahien")
  Re: More microsoft innovation ("Ayende Rahien")
  Re: More microsoft innovation ("Ayende Rahien")
  Re: More microsoft innovation ("Ayende Rahien")
  Re: Windows makes good coasters ("Stuart Fox")
  Re: More micro$oft "customer service" (Woofbert)
  Re: More micro$oft "customer service" (Woofbert)
  Re: More micro$oft "customer service" (Woofbert)
  Re: Is Linux for me? (The Ghost In The Machine)
  Re: More micro$oft "customer service" (macman)
  Re: Linux inheriting "DLL Hell" (Bob Hauck)

----------------------------------------------------------------------------

From: Peter Hayes <[EMAIL PROTECTED]>
Crossposted-To: alt.destroy.microsoft
Subject: Re: Will MS get away with this one?
Date: Sat, 16 Jun 2001 21:27:03 +0100
Reply-To: [EMAIL PROTECTED]

On Sat, 16 Jun 2001 20:07:04 +0100, [EMAIL PROTECTED] (Mark)
wrote:

> In article <[EMAIL PROTECTED]>, Peter Hayes wrote:
> >On Thu, 14 Jun 2001 05:40:34 GMT, T. Max Devlin <[EMAIL PROTECTED]>
> >wrote:


> >> The fact that Windows is monopoly crapware in no way indicates that
> >> millions of people have not successfully used it as an OS on their PC.
> >> It isn't the numbers, it is the proportions, that damn the product as
> >> monopoly crapware.  
> >
> >Eh? Are you saying that just because something is used by 95% of  its target
> >market  then it automatically becomes " monopoly crapware"? Monopoly, yes.
> >Crapware? That's down to the individual product.
> 
> No, he didn't say that.  

Reads like that to me. 

> >Whatever Microsoft's faults, they've established a product that has resulted
> >in dirt cheap hardware. 
> 
> No, that was a result of IBM making the PC designs open.

No, it's software that sells. A computer without software is like a car with
no petrol, just so much scrap metal.

Of course the hardware design being open helped, Compaq cloning the BIOS
helped, but it was having apps that people wanted to run, plus "no-one ever
got fired for buying IBM" that established Microsoft. Plus, of course, their
dirty tricks department.

Given time and the economic motivation someone would have cloned the IBM
hardware anyway. Being open just saved time and money.

> > Do you think for one minute that there would be a
> >games market on any "personal computer" if Windows 9.x hadn't happened? 
> 
> The computer games market has existed since the days of 8-bit computers.

That was pre Sega and Nintendo. Yes, you're right, there would be some
computer games, but not the market we have today.

<...>

> >To buy a graphics card
> >with 32 meg of ram and a GPU capable of billions of t&l calculations/second
> >would set you back tens of thousands of dollars instead of about 100. To buy
> >even a card capable of up to 24 bit colour at 1024x768 would be hundreds,
> >instead of which that is now a sub entry level specification.
> 
> This is hypothetical, total, speculation.

Of course it is, but one of the high-end Oxygen cards would set you back
thousands only four or five years ago. You can get the equivalent for under
100 today. Extrapolate from that.

I conclude that with the economies of scale, combined with one dominant
platform, the drive for ever faster gaming and intense competition between
manufacturers (as you say, because the hardware standard is open) we have
incredibly powerful hardware at rock bottom prices.

Microsoft provided that dominant platform in their quest for world
domination. They've done little else good, and this current SmartTags
controversy is another example of them at their worst, but at least most
people can exchange files and data with little hassle.

Peter

------------------------------

From: "Aaron R. Kulkis" <[EMAIL PROTECTED]>
Crossposted-To: soc.men,soc.singles,alt.fan.rush-limbaugh
Subject: Re: Why homosexuals are no threat to heterosexuals
Date: Sat, 16 Jun 2001 16:29:08 -0400

drsquare wrote:
> 
> On Fri, 15 Jun 2001 19:39:01 -0400, in comp.os.linux.advocacy,
>  (Rick <[EMAIL PROTECTED]>) wrote:
> 
> >"Aaron R. Kulkis" wrote:
> 
> >> >
> >> > Perhaps this is why he never gets any sex.
> >>
> >> I do...with WOMEN.
> >>
> >
> >Women. Thats plural. Thats multiple sexual partners. Well, did you know
> >your risk of contracting HIV is increasing exponentially?
> 
> Which is also going against all the right-wing idealism he seems to
> favour so much.

false premise.
I'm NOT right wing.

Right wing and Left-wing political views are BOTH a form of SOCIALISM

and...since I'm a libertarian, and libertarians are opposed to socialism
in ALL forms, that means that I am opposed to right-wingers just as
strongly as left-wingers.

Hope that helps, you politically illiterate MORON.

-- 
Aaron R. Kulkis
Unix Systems Engineer
DNRC Minister of all I survey
ICQ # 3056642

L: This seems to have reduced my spam. Maybe if everyone does it we
   can defeat the email search bots.  [EMAIL PROTECTED] [EMAIL PROTECTED]
   [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
   [EMAIL PROTECTED]

K: Truth in advertising:
        Left Wing Extremists Charles Schumer and Donna Shalala,
        Black Seperatist Anti-Semite Louis Farrakhan,
        Special Interest Sierra Club,
        Anarchist Members of the ACLU
        Left Wing Corporate Extremist Ted Turner
        The Drunken Woman Killer Ted Kennedy
        Grass Roots Pro-Gun movement,


J: Other knee_jerk reactionaries: billh, david casey, redc1c4,
   The retarded sisters: Raunchy (rauni) and Anencephielle (Enielle),
   also known as old hags who've hit the wall....

I: Loren Petrich's 2-week stubborn refusal to respond to the
   challenge to describe even one philosophical difference
   between himself and the communists demonstrates that, in fact,
   Loren Petrich is a COMMUNIST ***hole

H: "Having found not one single carbon monoxide leak on the entire
    premises, it is my belief, and Willard concurs, that the reason
    you folks feel listless and disoriented is simply because
    you are lazy, stupid people"

G:  Knackos...you're a retard.


F: Unit_4's "Kook hunt" reminds me of "Jimmy Baker's" harangues against
   adultery while concurrently committing adultery with Tammy Hahn.

E: Jet is not worthy of the time to compose a response until
   her behavior improves.

D: Jet Silverman now follows me from newgroup to newsgroup
   ...despite (C) above.
 
C: Jet Silverman claims to have killfiled me.

B: Jet Silverman plays the fool and spews out nonsense as a
   method of sidetracking discussions which are headed in a
   direction that she doesn't like.

A:  The wise man is mocked by fools.

------------------------------

From: "Ayende Rahien" <[EMAIL PROTECTED]>
Subject: Re: Linux inheriting "DLL Hell"
Date: Sat, 16 Jun 2001 23:04:40 +0200


"The Ghost In The Machine" <[EMAIL PROTECTED]> wrote in
message news:[EMAIL PROTECTED]...


> It might take quite a few, though.  This is a line
> from a handy VC++ .dsp file named, as it turns out, Hello.dsp:

Just tried to remove all the default linked libraries, this is what the
resulting compiler option looks like.

/nologo /subsystem:console /incremental:yes /pdb:"Debug/hello.pdb" /debug
/machine:I386 /out:"Debug/hello.exe" /pdbtype:sept

It compiled, linked & executed fine.

> # ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib \
> comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib \
> uuid.lib odbc32.lib odbccp32.lib  kernel32.lib user32.lib \
> gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib \
> ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib
>
> Most of these probably aren't needed for a Hello World (comdlg32??
> winspool??), but I wonder.

You certainly don't need it.
I also wonder why it has some of those files twice.

> (Don't ask me why it's using a '#' as the first char, either.)

I think that it's being used as a comment mark.
Other files in windows does it as well. (hosts, frex)




------------------------------

From: "Ayende Rahien" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.nt.advocacy
Subject: Re: Linux inheriting "DLL Hell"
Date: Sat, 16 Jun 2001 23:15:09 +0200


"The Ghost In The Machine" <[EMAIL PROTECTED]> wrote in
message news:[EMAIL PROTECTED]...
>
> After all, Linux is essentially a large, distributed development effort;
> not everyone is going to have the same version of everything.
>
> The only way to solve that problem is to rebuild everything from
> scratch -- an idea which I for one would love to do someday on
> my own personal system -- so that everything refers to the same version
> of everything else, and everything is consistent.  More or less.

One way to do it is to have a directory where all the shared libraries are
stored, which no one has write/delete access to.
The only way to add/remove libraries is via system API, which would check
for versioning.
It would require package management, I think, so when you install
application foo, which depend on libarary bar3.1.3, the package management
ask the system whatever it has this library's version, and if not, install
it.
When you uninstall an application, the package management tells the system
that it no longer need this version of the application
The system keeps tracks on how many applications uses a library & library
version, when no application uses this library, it's deleted.
An application that wants to use a library will ask the system for the
spesific version of the library that they need, the system will query the
libraries that it has. If it has a library with the correct version, the
application gets that, if it doesn't, it search for other versions, and
query if they support the version that the application wants, if so, the
application gets this version, if not, the system returns an error.

That should work, but it require users only adding/removing stuff to the
system via the package management.

> Microsoft presumably tries to do this, to some extent.  I'm not sure if
> they are horribly successful -- and there are issues such as SOL.EXE which
> is so old no one wants to touch it, apaprently. Crr-r-r-r-r-e-a-k! :-)

SOL.EXE?



------------------------------

From: "Ayende Rahien" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.ms-windows.nt.advocacy
Subject: Re: Linux inheriting "DLL Hell"
Date: Sat, 16 Jun 2001 23:18:01 +0200


"pip" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> The Ghost In The Machine wrote:
> > How are we supposed to use them?
> >
> > After all, Linux is essentially a large, distributed development effort;
> > not everyone is going to have the same version of everything.
> >
> > The only way to solve that problem is to rebuild everything from
> > scratch -- an idea which I for one would love to do someday on
> > my own personal system -- so that everything refers to the same version
> > of everything else, and everything is consistent.  More or less.
>
> Well that sounds like a good idea to me (yes I know hear me out). Make
> sure that we can start from a good base point standard with a good clean
> interface and dump the rest. Yes, programs will break and the
> maintainers will just have to update them. Radical ? Well, the carrot
> and stick approach may work :) Of course the problem is that no
> distribution will do this because they are concerned with making things
> "work", so that plan is out. Oh well, if I get annoyed I have only a few
> thousand apps to make changes to :)

There is a really big problem doing stuff like that.
This alienate people from your platform.

Exmale: (Regardless of the quality of binary only drivers.) One of the
reason that some hardware makers don't makes drivers for Linux is that the
driver model isn't stable. It changes with kernel revisions.

Of course, MS took the other approach regarding backward compatability.



------------------------------

From: "Ayende Rahien" <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.mac.advocacy
Subject: Re: More microsoft innovation
Date: Sat, 16 Jun 2001 23:19:35 +0200


"Rick" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...


> Which parts? And BTW, I didnt say they did, although they probably have.
> I said -you- prove they cant. You cant prove it, because they can.

It's useless to try and prove a negative.




------------------------------

From: "Ayende Rahien" <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.mac.advocacy
Subject: Re: More microsoft innovation
Date: Sat, 16 Jun 2001 23:27:01 +0200


"Rick" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...


> Why do ALWAYS fail to see anything wrong with anything that micro$oft
> does?

I don't, I've criticize MS in number of occations, usually on their prices,
licenses, and 9x.

> micro$oft provides the intial links list. CAN you remove those?

Yes.
> micro$oft CAN insert links to ftheir pages from competitor pages.

Can you prove that they do that?



------------------------------

From: "Ayende Rahien" <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.mac.advocacy
Subject: Re: More microsoft innovation
Date: Sat, 16 Jun 2001 23:31:58 +0200


"drsquare" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> On Sat, 16 Jun 2001 18:37:41 +0200, in comp.os.linux.advocacy,
>  ("Ayende Rahien" <[EMAIL PROTECTED]>) wrote:
>
> >"Peter Hayes" <[EMAIL PROTECTED]> wrote in message
> >news:[EMAIL PROTECTED]...
>
> >> legal, to alter the contents of that site by any means whatsoever.
> >
> >Like removing graphics? Sounds? JavaScript?
>
> If you think that removing trivial extras

Those aren't trivial extras.



------------------------------

From: "Stuart Fox" <[EMAIL PROTECTED]>
Subject: Re: Windows makes good coasters
Date: Sun, 17 Jun 2001 08:38:24 +1200


"Mark" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> In article <9gb4j2$13tg$[EMAIL PROTECTED]>, Stuart Fox wrote:
> >
> >Haha.  Yes, of course it was always going to be slow, but it was slower
than
> >Windows 95 on the same box, which was not what I was lead to belive.
>
> I find that amazingly difficult to believe.  Windows 95 crawls on a
> Pentium, let alone a 486.

This machine was used for a salesperson for quite a while with Windows 95,
running Office 95 + Reflection 5.  It ran adequately, and faster than X did.

> I recall our secretaries having no problems moving files around,
> creating/deleting directories etc., using dos, all those years
> ago.

Yes, as long as they had it all written down in front of them



------------------------------

From: Woofbert <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.mac.advocacy
Subject: Re: More micro$oft "customer service"
Date: Sat, 16 Jun 2001 20:36:06 GMT

In article <9gfgpr$e45$[EMAIL PROTECTED]>, "Ayende Rahien" 
<[EMAIL PROTECTED]> wrote:

> "Woofbert" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> 
> > Who controls the content of these added links?
> 
> The user.

I was under the impression that once you turn the feature on, certain 
words already have links supplied by Microsoft.

-- 
Woofbert: Chief Rocket Surgeon, Infernosoft
email <woofbert at infernosoft dot com> 
web http://www.infernosoft.com/woofbert

------------------------------

From: Woofbert <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.mac.advocacy
Subject: Re: More micro$oft "customer service"
Date: Sat, 16 Jun 2001 20:38:07 GMT

In article <9gfgpm$e45$[EMAIL PROTECTED]>, "Ayende Rahien" 
<[EMAIL PROTECTED]> wrote:

> "Woofbert" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > In article <[EMAIL PROTECTED]>, macman
> > <[EMAIL PROTECTED]> wrote:
> >
> > > In article <[EMAIL PROTECTED]>,
> > >  Dan <[EMAIL PROTECTED]> wrote:
> > >
> > > > In article <[EMAIL PROTECTED]>,
> > > >  Macman <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > PLEASE GET IT THROUGH YOUR THICK SKULL---No one has ever 
> > > > > suggested
> > > > > that
> > > > > it goes through Microsoft's servers.
> > > > >
> > > > > But Microsoft's software does change the structure of the web 
> > > > > page
> by
> > > > > adding hyperlinks that the author never intended. Microsoft is
> > > > > clearly
> > > > > involved.
> > > >
> > > > PLEASE GET THIS THROUGH *YOUR* THICK SKULL--- I can make more
> > > > "structural changes" to a page by changing fonts, colors, turning 
> > > > off
> > > > graphics and sounds.   Hell, I can use a text-only browser.   Is 
> > > > the
> > > > author of my text-only browser involved in a copyright issue?
> > >
> > > NONE of your examples changes the content of the page -- or adds
> > > hyperlinks. This is something new.
> >
> > They look like hyperlinks. They act like hyperinks. They are...
> 
> They don't look like hyperlinks, they don't act like hyperlinks, they
> aren't...

They look a little different (squiggly lines instead of colored and 
underlined) and act a little different (make a popup menu of hyperlinks 
instead of be a single hyperlink) but the end result is the same: new 
hyperlinks are added to the web page.

-- 
Woofbert: Chief Rocket Surgeon, Infernosoft
email <woofbert at infernosoft dot com> 
web http://www.infernosoft.com/woofbert

------------------------------

From: Woofbert <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.mac.advocacy
Subject: Re: More micro$oft "customer service"
Date: Sat, 16 Jun 2001 20:39:21 GMT

In article <9gfgpi$e45$[EMAIL PROTECTED]>, "Ayende Rahien" 
<[EMAIL PROTECTED]> wrote:

> "Woofbert" <[EMAIL PROTECTED]> wrote in message 
> news:[EMAIL PROTECTED]...
> > In article <[EMAIL PROTECTED]>, Dan 
> > <[EMAIL PROTECTED]> wrote:
> >
> > > > I still don't like the idea of someone changing or adding to 
> > > > the content of my page. Hyperlinks are part of the content.
> > >
> > > So what about using a text only browser?   Have I "changed your 
> > > page" by eliminating the graphics?
> > >
> > > Same thing.
> >
> > Not the same thing. The Web was created from the start to be a way 
> > for browsers of different capabilities to display text and 
> > graphics. Everyone creating web pages knew that some browsers could 
> > display images within the text while others required helper 
> > applications to view the images. Viewing images may be optional, 
> > but no browser ever enabled viewing different images than what the 
> > server sent.
> 
> I'm surprised that you aren't bashing MS for this too. After all, IE 
> does this too, if an image it too large to fit on screen, it will 
> resize it.

I don't know how you can believe that resizing an image for formatting 
reasions is the same sort of change as adding new hyperlinks.

-- 
Woofbert: Chief Rocket Surgeon, Infernosoft
email <woofbert at infernosoft dot com> 
web http://www.infernosoft.com/woofbert

------------------------------

From: [EMAIL PROTECTED] (The Ghost In The Machine)
Subject: Re: Is Linux for me?
Date: Sat, 16 Jun 2001 20:42:23 GMT

In comp.os.linux.advocacy, Jack Tripper
<[EMAIL PROTECTED]>
 wrote
on Sat, 16 Jun 2001 14:16:06 -0500
<[EMAIL PROTECTED]>:
>>
>>>I don't mind reformatting the whole
>>>hard drive, 
>>
>>I wouldn't bother doing that just yet.
>
>I've been reading up a bit on disk partitioning and apparently it
>*does* involve erasing all my programs? Don't I have to reformat the
>whole hd anyway, to ge the partition? Or, is it simply a matter of
>creating the space (yeah, and I meant 8.4 MEGS) and partitioning it?
>I'm very confused. From reading all your comments it's obvious that
>because of my limited UNIX experience I shouldn't put all my eggs in
>one basket. 
>Thanks for all your help! And what I meant with all that GUI HTML
>interface stuff was a program like netscape composer, editors for
>making web pages.

To (hopefully) clarify the partition issue.

[1] One must distinguish between a low-level disk format, a
    higher-level partition data wipe, and a file delete.
    One can contrast these to a form of road-grading.

    A low-level disk format digs the trench, wiping out all roads.
    (Nowadays, low-level disk formats are extremely rare, on consumer
    equipment; if a disk fails, the manufacturer might fix it, but
    otherwise one's left with a dead disk.  A special servo platter
    identifies where the "roads" are in modern designs, mostly because
    there are a variable number of sectors, depending on which
    cylinder one is accessing.  All this requires intelligent logic --
    supplied on the disk's interface card -- to handle the complexity.
    Note that this is not the same as the interface card one plugs into
    one's PC -- the disk's card is on the disk itself, with two cables:
    the familiar one that plugs into the computer interface card (the
    usual 40 pin or so affair), and a small, usually orange, one that
    goes between the seal to connect to the heads.)

    A software partition manager will design the intersections and
    point out where the roads should go, or pour the asphalt and
    do some basic striping.

    (Yes, yes, I know; this is one reason why analogies are suspect. :-)
    Some partition managers can even move partitions around, although
    it's more like restriping already-existing roadway, without removing
    the debris; if the striping paints over the debris, one loses the
    debris.  Fortunately (or unfortunately, depending on how one views
    the matter), the partition process is unaffected by this debris.)

    A partition data wipe sweeps the streets within that partition's
    boundaries, and lays down more striping.  A file delete removes
    a particular piece of debris -- although, again, the analogy is
    suspect, as debris is not important, whereas a user's files often
    are.  One can also add directories -- which are either debris with
    striping, or striping with debris -- and remove them, which .... well,
    you get the idea, I hope; my head is beginning to hurt. :-)

    The DOS format command is essentially a street-sweeper,
    as far as hard drives are concerned (it can low-level format
    floppies, though).  All FORMAT.EXE does is wipe out certain
    critical blocks on a partition, making it look empty to the
    rest of DOS, after testing all blocks to see if they're readable
    (unless someone uses the /Q switch, IIRC).  It's so dumb it
    had problems if the first block of a partition has faulty data in it.
    (Hopefully they've fixed that by now.  But I wonder.)

    FDISK is a partition manager, albeit it's not all that bright;
    it can handle FAT12, FAT16, and FAT32 partitions, but that's
    about it.  Other types show up as non-DOS, and can't be manipulated.

    In Linux, most of the functions are represented:
    fdformat is a floppy low-level formatter.  (There doesn't
    appear to be a hard disk low-level formatter, but, again, it's
    not clear that it's needed.)

    Linux's fdisk (same name, more intelligent than DOS's) manages
    the partitioning of the drive.  Linux's version can set the
    drive type to a large number of identifiers, among them
    Linux (duh), Linux swap, OS/2, DOS (various), and even Xenix.
    (Swap files/partitions probably deserve a different article; this
    one's getting too long as it is... :-) )

    mke2fs or mkfs.ext2 will take an existing partition, and set up
    structures on it (by writing superblocks) that will allow for later
    mounting (association of a partition with a particular part of
    the directory tree by using the 'mount' command).

    And 'rm' will remove particular files or directories, once a
    partition is mounted.

[2] As far as Linux and Windows are concerned, programs are files.
    In the case of Windows, programs are universally labeled *.EXE
    and may use components such as dynamically loadable libraries (*.DLL).
    In the case of Linux, programs are a little more varied; the
    true executable is an ELF (extended-link format, IIRC) of the
    appropriate machine type; however, there are also interpreted scripts
    (text files whose first line starts with '#!'; most of the time,
    they start with '#!/bin/sh' or '#!/bin/bash', identifying them as
    Bourne shell scripts or Bourne-again shell scripts, respectively;
    some of them might start with '#!/usr/bin/perl', which identifies
    a PERL script), which are often called programs.  ELF files can also
    refer to dynamically-loadable libraries; on Linux, these are *.so
    or *.so.* (where the trailing * is a version number).  Not that
    Linux cares about the extension, actually -- these are naming
    conventions only.

    NT also has interpreted scripts: .BAT, .VBS, and .WSH, IIRC.
    The main difference is that Linux (like Unix before it) actually
    looks at the first line of the file to determine what to do with it;
    if it looks like an ELF, it will execute it; if it starts with '#!',
    the rest of the line is most likely a command line with another
    executable which Linux will try to execute (occasionally, this
    second executable is not found, leading to some confusion as the
    error message only refers to the script file -- "what, file not found?
    It's right here....oooooooh, it's a script pointing to the
    wrong place; that's easily fixed...")

    Since mkfs.ext2 doesn't take into account existing data on a partition,
    all files are effectively wiped -- although one might, with a lot
    of care (and some luck!) recover some of the data -- unless one uses
    the -c option to check each and every block to see if it's good
    (I for one don't bother, but it's there if one wants to take the time).

    It's rather tricky to recover the data, though -- but that's one
    reason why some systems (NT and some Unixes among them) implement
    the notion of overwriting all blocks a file previously occupied
    with zeroes, when a file is deleted, if a file is appropriately
    marked (I forget the details, but there's probably an options flag
    somewhere).  Note that even this is no guarantee that someone won't
    get that sensitive data, as the head can presumably "jitter" slightly,
    leaving some data off track.  But it would probably take rather
    sophisticated equipment to get that data back.

    Probably easier just to use backups. :-)

[3] Partitioning one's drive intelligently can lead to improvements in
    security.  For example, currently in Linux one can mark the entire
    /usr partition read-only -- *nobody* can modify any file or directory
    on it, even if it's left wide open (permissions -rwxrwxrwx, 777) [*]!
    To modify it, one must remount it -- and that can only be done by root,
    assuming nothing dumb was done in /etc/fstab.
    (All this assumes /tmp and /var are somewhere else, admittedly.
    Some programs -- games, mostly -- also do things in /usr/lib/wherever.)

    Admittedly, there are problems with this -- adding new software requires
    remounting the partition -- but it can help to avoid the casual
    hacker.

[.sigsnip]

[*] there are additional flags, such as 4000 (setuid), which probably
    still shouldn't be set.

-- 
[EMAIL PROTECTED] -- insert random misquote here
EAC code #191       1d:23h:40m actually running Linux.
                    Linux.  The choice of a GNU generation.

------------------------------

From: macman <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.mac.advocacy
Subject: Re: More micro$oft "customer service"
Date: Sat, 16 Jun 2001 20:42:47 GMT

In article <[EMAIL PROTECTED]>,
 [EMAIL PROTECTED] (Mark) wrote:

> In article <9gfgp3$e45$[EMAIL PROTECTED]>, Ayende Rahien wrote:
> >
> >"macman" <[EMAIL PROTECTED]> wrote in message
> >news:[EMAIL PROTECTED]...
> >> In article <[EMAIL PROTECTED]>,
> >>  Dan <[EMAIL PROTECTED]> wrote:
> >>
> >> > In article <[EMAIL PROTECTED]>,
> >> >  Macman <[EMAIL PROTECTED]> wrote:
> >> >
> >> > > Neither Google nor anonymizer changes the _content_ of pages. If they
> >> > > start changing the content, then they should be stopped.
> >> >
> >> > Smart Tags do not change the *content* of pages, either.   It just
> >> > presents more navigation options to the individual user.
> >> >
> >>
> >> For a web page, hyperlinks are part of the content.
> >
> >But it doesn't add hyperlinks.
> >
> >
> 
> What's the term Microsoft have coined for their hyperlinks which aren't?

They call them 'smart tags'.

But on one of their web pages, they admit that they're 'extended 
hyperlinks'.

Of course, what they call them is irrelevant. They could call them 
'swiss cheese' and they'd still be adding content to the web pages.

------------------------------

From: [EMAIL PROTECTED] (Bob Hauck)
Crossposted-To: comp.os.ms-windows.nt.advocacy
Subject: Re: Linux inheriting "DLL Hell"
Reply-To: bobh = haucks dot org
Date: Sat, 16 Jun 2001 20:44:05 GMT

On Sat, 16 Jun 2001 13:31:33 +0200, Ayende Rahien <[EMAIL PROTECTED]> wrote:

> > That's why God made LD_LIBRARY_PATH.

> http://www.visi.com/~barr/ldpath.html

Well, in spite of the title, his rant is mostly about apps that make
use of private shared libraries and don't provide a way to specify the
installation directory at run time.  I can agree with that.  

He seems to be against using LD_LIBRARY_PATH in the startup script in
order to provide this.  His suggested alternative alternative of doing
binary edits on the app isn't real appealing though.  The idea of
linking at install time has some appeal, but would seem to provide more
ways for an install to fail.

The use I was talking about, using LD_LIBRARY_PATH in a wrapper to fix
breakage, seems to be on his approved list.

-- 
 -| Bob Hauck
 -| To Whom You Are Speaking
 -| http://www.haucks.org/

------------------------------


** 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 by posting to comp.os.linux.advocacy.

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-Advocacy Digest
******************************

Reply via email to