[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openmosix-general
Subject:    [openMosix-general] Fw: /bin or /usr/bin for Debian?
From:       Mirko Caserta <mirko () mcaserta ! com>
Date:       2003-09-30 16:54:21
[Download RAW message or body]


Hey Vance,
are you still unable to post to the list?

About the "recursive" symlinks problem mentioned in your mail, I was not able
to find a solution myself. What I've come up with is this:

mcaserta@dexter tmp $ find . -type l -xtype d | sort | uniq
./icons-normal/icon-normal
./mdk-icons
mcaserta@dexter tmp $ find . -follow -xtype l | sort | uniq
./icons-normal/icon-normal
./mdk-icons
./mdk-icons/icon-normal

Now, if only I could get two stdins and print only the lines which differ
between the two... :)

I'm quite sure some more seasoned *NIX guru here has a cleaner solution :)

Begin forwarded message:

Date: 30 Sep 2003 07:42:38 -0400
From: Vance Morgan <vmorgo@alabang.dyndns.org>
To: Mirko Caserta <mirko@mcaserta.com>
Subject: Re: [openMosix-general] /bin or /usr/bin for Debian?


Hey, Mirko!

Thanks for answering my other question about openMosix.

The problem described below by DongXu Li is still a problem.  The
"patch" for it (it works with the last two releases of the Debian-based
ClusterKNOPPIX) is available at my site,
www.lafeyette.net/KludgeKollection.  It is not listed as a separate
file, though in the descriptions page, because it is very early "works
for me alpha quality" (Read 'kind of crappily written') script, and is
included in the "KludgeKlump" compressed tarball.  The script is called
"install" and must be run from /root/bin/, where the rest of the
KludgeKollection files go.

If you download and decompress KludgeKlump.tgz in /root/bin and then run
./install, it will install all the KludgeKlump scripts, then offer to
add a few .debs (or rpms--user's choice), then, finally, it offers to
make a few adjustments to Debian installs, one of which is attending to
the problem of cpujob, mosctl, and mosrun by either creating symlinks to
the file, or modifying the cpujob scripts.  Generally, I do the
symlinks, rather than the script mod.

Each step is described and the user is given the choice of executing it
or not.  Steps where a choice of rpm or deb are presented must be
answered with "r" for rpm or "d" for deb.  Steps that apply only to
debian systems (such as the mods described above) require a "y" response
to activate, otherwise, they are skipped.

Hope this helps....

Vance.

P. S.

Yeah, I know an update to KludgeKollection is overdue....

I've got a few additions about to come out, including something called
"snapback", which does a nice job of handing rsync-based backups over
nfs, mfs, or smbfs.  mfs is not recommended, because it still will fail
under heavy load, but that's not snapback's fault.  One thing, though: 
If I have some symlinks pointing to each other, like this:

/share/normal/mdk-icons points to /usr/bin/icons-normal, and
/usr/bin/icons-normal contains icons-normal, which points to
/share/normal/mdk-icons

do you know if there is a way to back up this mess without having to
follow the mis-pointed symlinks in an eternal loop that gets ever
deeper?  I am wondering how this might be accomplished with rsync.  I am
finding that such symlink loops are quite common in Linux distros.  (The
one I mention above comes with Mandrake 9.1.)  It's a pain having to dig
through an entire distro and try to find and remove such silly
mistakes...  (I did get rid of the ones I had created, and was
disheartened to find that the distro, itself, seems to have a number of
these!)

Vance.

On Tue, 2003-09-30 at 03:23, Mirko Caserta wrote:
> On Mon, 29 Sep 2003 15:17:40 -0500
> Dongxu Li <dli@riz-sage.uchicago.edu> wrote:
> 
> > I installed the oM kernel 2.4.22-1 and the debian package,
> > 
> > openmosix_0.3.4-1_i386.deb 
> > <http://prdownloads.sourceforge.net/openmosix/openmosix_0.3.4-1_i386.deb?
> > do wnload>
> > 
> > Even though 0.3.4-1 improved quite a lot from 0.3.3, I still get 
> > problems with scripts like cpujob or iojob. mosrun is installed in /bin, 
> > but still /usr/bin in scripts.
> > 
> > Hope you guys already corrected this.
> 
> I thought so, but since you have pointed out this problem for the 0.3.4-1
> tools (the latest) I'll have to look again at the autoconf/sources as soon
> as we have the new cvs repository working.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
openMosix-general mailing list
openMosix-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openmosix-general
[prev in list] [next in list] [prev in thread] [next in thread]