date:20041110

[SOLVED - mysteriously...not quite] Re: xorg installation fails, 99% complete only

2004-11-10 Thread Carlo Florendo

Carlo Florendo wrote:
Christopher Faylor wrote:
It seems like you have a lot of XFree86 packages still installed.
I have a couple of these in my installation but certainly not the
number that I see above.

Yes.  I did it after installing cygwin minus xorg.   Regarding the 
(version) numbers, I don't remember choosing other versions besides 
the ones indicated by default  at setup.

I guess I'm a little confused now as to who's seeing what problem.
I thought that you needed a clean install to duplicate this but the
above obviously didn't come from a clean install.

I'll be doing a clean uninstall and reinstall in a short while.
Thank you cygwin people for doing such a great job at cygwin!  I'm 
seeing this not as a problem (Really!!!) but another exciting episode 
of the wonders of open source software and open-source collaboration.  
Thank you!

Cygwin Rocks!
I tried to reproduce the problem on the WinXP SP2 machine in question 
and I was unsuccessful in reproducing it...

Cygwin installed like a charm =)
Now, I don't  know why such is the case.  

Hmmm...To tell the truth, I was actually asking  someone to follow 
instructions from me, (i.e. press this button, select "Unix", click ok, 
etc.).  However, when I myself tried do a fresh uninstall and fresh 
install, all worked well. 

In any case, I'm now attaching cygcheck.out and setup.log (compressed) 
so the experts could point out what difference it had with my previous 
posting of cygcheck.out and setup.log,

My suspicion is that the one whom I asked to install cygwin did 
something else that she didn't tell me(What I saw when she was 
installing cygwin was the "99% completed" on xorg that never stopped.  
This, I verified with my  eyes.   On her following my instructions,  I 
didn't see it with my own eyes.  She just said she did.)

Sheesh...sorry for all these noise for the past 3 days. 

Thank you to all you cygwin developers.
Cygwin Rocks!
Best Regards,
Carlo
--
Carlo Florendo
Astra Philippines Inc.
www.astra.ph

Why Xming.exe?

2004-11-10 Thread Ãyvind Harboe

First of all: I love CygWin! 

If I didn't, I would not passionatly dive into this discussion. :-)

Here are a couple of reasons why I think a discussion of 
Xming.exe can bring something to CygWin.

Basically, I believe that the Xming.exe would never have seen the
light of day if if all was well with CygWin. It is a cry for help.

Also, I believe the next useful solution to the set of problems that
CygWin is facing is non-local. I think it is in the interest of CygWin
to allow discussions and hacks to wander somewhat freely. 

If you stomp out this discussion, you are going to make people look elsewhere 
for a solution to "the CygWin mess". See bottom of this message for 
what I mean.

Some issues that CygWin could address to make Xming.exe moot:

- Side-by-side install. There is a need for e.g. SSH + and an X server in
a single package that is easily deployable. This package 
*must* be unaffected by updates to CygWin. This would of course
not be uniquely useful for X server, but would be useful for e.g. multiple
independent GCC toolchains used for embedded development. E.g. its more
than once that CygWin updates have broken http://sources.redhat.com/ecos
tools, without bringing any new features or improvements for those tools.
The many examples of cygwin1.dll being distributed along with various 
applications,
is further evidence of this need(which is contrary to the CygWin license, BTW).

- Side-by-side means CygWin next to CygWin, and CygWin next to any Windows
program.

- It is currently impossible for the casual programmer to debug CygWin
X using GDB. See http://cygwin.com/ml/cygwin-xfree/2004-10/msg00159.html

- CygWin is a pain to install. It takes long to download(many files more than
size with a broad connection), takes long to install and many things can and do
go wrong. 

- CygWin messes with Windows environment variables, breaking other programs. 

- CygWin is broken by other programs using the Windows environment variables.

- CygWin is always in motion.  There is no "CygWin distribution version" 
like the Linux distributions operate with. There is no way to install
"a specific old boring CygWin" to run some tools that never change.


--- ever-so-slightly off topic :-) ---

Could I delete CygWin?

What I would need in it is place was the ability for Windows programs to 
interface
to Linux programs.  Where those programs run(under Linux or under Windows) is 
somewhat
secondary.

If I could somehow tell the Windows programs to talk to a Linux box
(http://www.colinux.org  or a real Linux box) as if those Linux programs ran
under Windows, then it would do the trick. http://www.colinux.org is an 
interesting case, because they pretty much support side-by-side installs 
already.

The Windows programs that need to interface to the Linux programs only talk to
those programs through the following mechanisms:

- stdin/stdout/stderr 
- ctrl-c to abort applications(there is a name for this communication channel, 
but I don't know what it is).
- current directory
- files (from Windows to Linux box and vice versa).
- console

(What did I leave out?)

Below is an a rough idea on how this might be solved:

- create a Windows filing system that makes the Linux box filing system
available through e.g. a drive letter. This filing system is different from
Samba. This filing system talks to the Linux box using SSH, say.
- when Windows is accessing a Linux executable via this filing system, it
does not serve up the Linux executable. Instead it serves up a Windows 
executable.
This Windows executable uses, say, SSH to communicate with the Linux box to
execute the command. Lets call this executable an SSH-Proxy. 
- The Linux box needs to be able to see the files on the Windows machine. 
Mechanism 
TBD. The SSH-Proxy knows how to translate from a Windows filename to the Linux
filename. It uses this capability to set the current directory before executing 
the
Linux command.
- The SSH-Proxy tells the Linux box about the limitations of the Windows 
console.

Example:

- On the Windows machine the root of the Linux box is accessible via the drive
letter e:\
- e:\etc maps to /etc, e:\usr to /usr, etc.
- e:\exec is special. It does not map to /exec. Instead it is used in execution
of programs that are in the path, as shown below.
- On the Linux box, there is an equivalent of "/cygdrive", which I'll call
"/windows"

To grep my local harddrive I would:

c:\bar> e:\exec\grep -r foo *

On the Linux box, this would actually be executed as:

[EMAIL PROTECTED] /windows/c/bar
$ grep -r foo *


-- 
Øyvind Harboe
http://www.zylin.com

Re: xorg installation fails, 99% complete only

2004-11-10 Thread Carlo Florendo

Christopher Faylor wrote:
It seems like you have a lot of XFree86 packages still installed.
I have a couple of these in my installation but certainly not the
number that I see above.
Yes.  I did it after installing cygwin minus xorg.   Regarding the 
(version) numbers, I don't remember choosing other versions besides the 
ones indicated by default  at setup.

I guess I'm a little confused now as to who's seeing what problem.
I thought that you needed a clean install to duplicate this but the
above obviously didn't come from a clean install.
I'll be doing a clean uninstall and reinstall in a short while. 

Thank you cygwin people for doing such a great job at cygwin!  I'm 
seeing this not as a problem (Really!!!) but another exciting episode of 
the wonders of open source software and open-source collaboration.  
Thank you!

Cygwin Rocks!
--
Carlo Florendo
Astra Philippines Inc.
www.astra.ph

Re: xorg installation fails, 99% complete only

2004-11-10 Thread Carlo Florendo

Igor Pechtchanski wrote:
What did you do, exactly, on the last setup run? The log file shows that
you installed the following packages:
startup-notification-0.7-1
transfig-3.2.4-2
xorg-x11-bin-dlls-6.8.1.0-1
xorg-x11-devel-6.8.1.0-1
xorg-x11-fcyr-6.8.1.0-2
xorg-x11-fenc-6.8.1.0-2
xorg-x11-fscl-6.8.1.0-2
xorg-x11-fsrv-6.8.1.0-1
xorg-x11-libs-data-6.7.0.0-3
xorg-x11-man-pages-html-6.8.1.0-1
xorg-x11-nest-6.8.1.0-1
xorg-x11-vfb-6.8.1.0-1
Hmmm. what I did was to install cygwin without any xorg. After the
successful installation, I installed the xorg packages (as specified in
the xorg-base README) via setup once again. IIRC, I do not remember
clicking the buttons that would change the install versions.

(which means you've downgraded xorg-x11-lib-data). It also shows that
the
following postinstall scripts ran:

xorg-x11-devel.sh
xorg-x11-f100.sh
xorg-x11-fcyr.sh
xorg-x11-fenc.sh
xorg-x11-fnts.sh
xorg-x11-fscl.sh
xorg-x11-libs-data.sh
xorg-x11-xwin.sh
which is odd, since you didn't reinstall xorg-x11-xwin or
xorg-x11-f100 or
xorg-x11-fnts. The previous run clearly shows setup installing
xorg-x11-f100 and running the postinstall script for that package, so it
should have renamed it to .done and not re-run it.
I did install xorg *after* installing cygwin minus xorg.

Hmm, the fact that it attempts to reinstall packages, coupled with the
fact that it's not renaming postinstall scripts properly, makes me wonder
whether your Cygwin directory tree is writable by the user that performs
the install. This would also be consistent with the "Cannot open
c:\cygwin\var\log\setup.log for writing" message that others reported.
Igor

I was logged as a user under the administrator's group when I did the install.
I've gotten hold of the WinXP SP2 Machine now, on line! I'll uninstall everything and try to reproduce the error once more.

I'll run ps and cygcheck at the point where it stalls and provide as much
detail as possible.
Thanks!
Best Regards,
Carlo
--
Carlo Florendo
Astra Philippines Inc.
www.astra.ph

37 matches

Mail list logo