Re: Mandrake 8.1 Desktop Gone

On 27 Mar 2007, in the Usenet newsgroup alt.os.linux, in article
<1175011236.051864.183420@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, ffitz2@xxxxxxxxx wrote:

You got it in 1. The /tmp permissions were the problem on the KDE.

Not uncommon problem.

I've tried to talk the owners into a more recent distribution, but
they don't wanna.

A problem is that Linux evolves more rapidly than windoze - and this is
made worse by using a generic distribution. The "popular" Linux
distributions like Mandrake/Mandriva, SuSE, Slackware, etc. have a normal
supported life of up to _three_ years. By that time, a LOT of the
distribution has been changed to something almost unrecognizable. You need
only look at Mandrake 8.1, compared to 9.2 compared to Mandriva 2007. If
you need a release that is going to be supported for a decade or so, you
need to be using one of the enterprise distributions which have that as a
feature. If they don't want to spend money (a rather foolish stance for
a business), they can get one of the GPL copies of a commercial release.
See http://www.distrowatch.com for a vast selection.

I support all the windows systems here, and I don't get enough practice
on *ix to stay current. (I forget too fast.)

That's another major disadvantage.

The FTP daemon is proftpd.

It worked just fine for users on MSIE 6, ws-ftp, etc.
When MSIE 7 came around, after a user logs in, they can
navigate anywhere.

That makes no sense at all. RFC0959 makes no difference in the commands
that a client can use, and in any case predates Internet Exploiter by ten
years.

Based on your reference to chroot, I checked the proftpd.conf
and the users have "DefaultRoot" directories assigned.

That's a usual solution - the capability has been in FTP servers since
the late 1980s.

I now think this must be a proftpd bug.

I honestly don't see how. If you haven't chrooted the FTP server, then
ANY client can give a CDUP command to change to the parent directory. on
up to the top that the server will allow. The FTP protocol has no idea
what client is being used - unlike a web browser, because the protocol is
simple and capabilities simply don't depend on new features the client may
include. (Actually, the FTP protocol can be traced back to RFC0114 in April
1971 - a heck of a long time before microsoft bought QDOS from Seattle
Computer Products to have something to sell to IBM for the 1981 PC.)

Old guy
.

Relevant Pages

  • Re: Outlook 2k7 and Ex2k7 -> 0X80190197
    ... If the client hosts have been updated with 842309, then you can do a GPO to ... push the reg setting (UseLMCompat). ... on and then look at the configuration for that OAB in the Offline Address ... See if this OAB is configured for PF distribution, ...
    (microsoft.public.exchange.admin)
  • Re: DP not function?
    ... "Systems Management Server clients use existing connections from the ... Client Access Points and Distribution Points (DPs) designated in their ...
    (microsoft.public.sms.admin)
  • Re: schannel.dll, secur32.dll, and DSCLIENT.EXE redistribution
    ... > include it in the distribution package. ... > when not present in a client attempting to access server. ... >> distributing these DLLs to them, ...
    (microsoft.public.platformsdk.security)
  • Re: nat is a "natural" firewall?
    ... >> cams, have FTP servers, even SQL database services running on their ... >> virus that scans your drive, find your quick books file, then FTP's it ... Once upon a time they used your email client to send mails. ... I've seen many ISP's take a stance against virus/spam filtering as the ...
    (comp.security.firewalls)
  • RE: Finding y-Values in budget curve app w/ excel
    ... We proposed a two parts automation with distribution per period as linear. ... > for a given number of periods in the budget term. ... The client has told me that he believes the problem can ... > period $ for period percent of whole budget spent per period ...
    (microsoft.public.excel.misc)
Loading