[scilab-Users] Re: scilab on Ubuntu 11.10

[Charles Warner]

Just gave chroot a try- works nicely, but my system won't let me run a
second X server, which seems to limit the second root to command line
only.  Useful, but not much imporvement over my reboot approach.  Note that
I can access files on either system from whatever system is active...I
could run Scilab from the command line on the new root, but, since Scilab
comes installed and configured on my preferred distro, I really have no
need to do this.

What I use the dual boot system for primarily is to have an "experimental"
system where I can try out new software, check for conflicts, etc. before
adding it to my "working" system.  As time goes on, my "experimental"
system starts looking more like my "working" system- when it seems stable
enough, and has all the critical functions I need, I then start using it as
the "working" system, and the old system is discarded and a new base distro
can be explored without causing problems.  This also gives me the chance to
evaluate new releases of projects like Scilab without losing my existing
capabilities.

The conflict between the libgl versions that I encountered actually
occurred when trying to run Dassault Systemes' DraftSight2 (latest release)
on the same platform as Salome.  Not being to fond of the idea of rebooting
to switch between systems to resolve library conflicts, and the fact that
an older version of DraftSight2 plays nicely with Salome, and the fact that
Salome is by far the more important package, Salome wins.  I am not sure I
could easily make the same choice with Scilab requiring a different library
version- although rebooting to run Scilab is not nearly as unpalatable as
the other two, since I seldom, if ever, need to run Scilab when I am
running Salome.  The question is, are ther atoms that rely on one version
of the libgl library while other atoms rely on the other version?

This is a conflict I have never encountered on Linux before, but, I suspect
that, with the "desktop wars" between Gnome 3 and Unity running rampant, I
suspect we can look for more such conflicts in the future...

Charlie

On Mon, Nov 21, 2011 at 3:40 AM, Antoine Monmayrant <
antoine.monmayrant at laas.fr> wrote:

> Le 20/11/2011 22:19, Charles Warner a écrit :
>
>  Anttoine-
>> My version of Linux (Ubuntu 10.04) will not allow me to install the two
>> libraries simultaneously on the same file system.  I have not considered
>> chroot- I don't know if it will find the alternative file system.  Worth a
>> try, I suppose.  Since I like to keep two instances of the entire distro
>> on
>> my computer (one, my "working" system, one my "experimental" system)
>> rebooting has always been my "lazy" approach.  I'm not sure how to use
>> chroot in this process, since both systems have root named "/"...maybe
>> worth experimentings with.
>>
> Well, we use it at work (I have to admit I was not the one setting it up)
> and it's quite convenient.
> Basically, the only common points between your two systems will be the
> linux kernel.
> Apart from the kernel, the two systems are totally independent and have
> their one filesystems.
> We use it to run a debian distro (that have nice packages for
> electromagnetic simulations) on a centos system (needed for a lot of other
> simulations softwares).
> Switching from Centos to Debian is as easy as "/local/chroot/debian" and
> it's even easier to switch back: "exit".
> We didn't bother setting up the X server on Debian (the softs we use are
> command-line only) but it might be possible to share the same X server on
> both systems.
>
> Cheers,
>
> Antoine
>
>  Charlie
>> On Sun, Nov 20, 2011 at 3:03 PM, Antoine Monmayrant<
>> antoine.monmayrant at laas.fr>  wrote:
>>
>>   Le 20/11/11 18:25, Charles Warner a écrit :
>>>
>>> "install libgl1-mesa-swx11 or removing libgl1-mesa-glx should fix the
>>> issue."  The problem is, other software may require libgl1-mesa-glx-
>>> changing to *-swx11 may break something else.  The two libraries
>>> apparently
>>> cannot co-exist on the same system.  I encountered this with a couple of
>>> other software packages I have been working with- the solution is a dual
>>> boot system, one with *-glx to satisfy one software package, the other
>>> with
>>> *-swx11 to satisfy the other software package.  Not an elegant
>>> solution...
>>>
>>> Why don't you chroot instead of dualboot?
>>> This could be a more elegant solution, even if it's not perfect.
>>>
>>>
>>> On Sun, Nov 20, 2011 at 7:18 AM, Tibault Reveyrand<reveyrand at gmail.com>*
>>> *wrote:
>>>
>>>  Here is a way to fix this problem :
>>>>
>>>> https://twitter.com/#!/**SylvestreLedru/status/**138217732360515584<https://twitter.com/#%21/SylvestreLedru/status/138217732360515584>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>
> --
> ++++++++++++++++++++++++++++++**+++++++++++++++++++++++++
>
>  Antoine Monmayrant LAAS - CNRS
>  7 avenue du Colonel Roche
>  31077 TOULOUSE
>  Cedex 4 FRANCE
>
>  Tel:+33 5 61 33 64 59
>
>  email : antoine.monmayrant at laas.fr
>  permanent email : antoine.monmayrant@**polytechnique.org<antoine.monmayrant at polytechnique.org>
>
> ++++++++++++++++++++++++++++++**+++++++++++++++++++++++++
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20111121/dfeaae73/attachment.htm>