On 9/15/05, Art Fore wrote:

In the .xsession-errors I get

Wind/U X-session Toolkit wuDisplay: Cannot open display.

I am creating the link by right clicking and the desktop and selecting create new link to application. Then browse to the application and select it.

Art

Are you selecting "Run as another user" in the link? This may cause this error. -- -- Svetoslav Milenov (Sunny)

I switched the user group back to users, copied the files back to the user directory where they were originally install, changed group to users. Everything then worked. The changes I undid were made by the user of the machine, not me. Art Art Fore wrote:

No, I have not selected that. The user shows up as a member of root and trusted.

Art

Sunny wrote:

...

On 9/15/05, Art Fore wrote:

...

In the .xsession-errors I get

Wind/U X-session Toolkit wuDisplay: Cannot open display.

I am creating the link by right clicking and the desktop and selecting create new link to application. Then browse to the application and select it.

Art

Are you selecting "Run as another user" in the link?

This may cause this error.

On Thursday, September 15, 2005 @ 10:34 PM, I wrote: <snip>

...

...

You're doing better than me. I'm trying to make one work under root and can't get it going. When I click on it, I get a prompt pop-up window asking me what to open it with. Below is a list of "Known Applications". I don't see anything that would be considered an "executable".

Greg Wallace

Never mind. I think what I was trying was illogical. I thought maybe you could just click a desktop shortcut and it would launch a shell and run the command. Looks like if there is an executable stored under, say, /root/Desktop, the file shows up on your desktop but you can't actually make it execute by simply clicking on it. Now that would be slick if you could get it to automatically launch a shell and execute the script by simply clicking it! Greg Wallace

On Friday, September 16, 2005 @ 4:51 AM, Patrick Shanahan wrote:

* Greg Wallace [09-16-05 01:54]:

...

I think what I was trying was illogical. I thought maybe you could just click a desktop shortcut and it would launch a shell and run the command.

Don't know what makes you think it illogical. It is perfectly logical and _will_ work as you describe. Time to go back to the books. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

Nah. You shouldn't have to go to books for something like this if it's doable. You can do this in Windows. Why make it that hard for a Newbie to do it in Linux. It should be right there if you right click the icon. As for me, I'll remember that it is doable but don't have the time right now to "hit the books". Greg Wallace

On 9/16/05, Greg Wallace wrote:

On Friday, September 16, 2005 @ 4:51 AM, Patrick Shanahan wrote:

...

* Greg Wallace [09-16-05 01:54]:

...

I think what I was trying was illogical. I thought maybe you could just click a desktop shortcut and it would launch a shell and run the command.

...

Don't know what makes you think it illogical. It is perfectly logical and _will_ work as you describe. Time to go back to the books. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

Nah. You shouldn't have to go to books for something like this if it's doable. You can do this in Windows. Why make it that hard for a Newbie to do it in Linux. It should be right there if you right click the icon. As for me, I'll remember that it is doable but don't have the time right now to "hit the books".

Greg Wallace

I really hate that. Don't tell me that first time you saw Win'95, you knew how to create a shortcut of DOS program on the desktop, how to set the right memory settings, etc. Without any help or reading. Also - the other OS _was_ designed as a replacement of DOS, but with need for compatibility, so it can make a difference between a DOS and Win program. In *nix - you have executable - always a *nix executable (script or binary, doesn't matter). There's always time for books, and when you come to something new, do not forget that the old one was new in the past as well. Patrick is right, it is not _illogical_. Some reasons are: 1. The *nix way is that every command, which does its job OK, will not produce any output. Especially scripts, as they are meant to automate jobs, without user intervention. 2. The job of the graphic environment is _not_ to "think" for you and to guess what you may want. If you click on a command, it will execute it. Noone told it that this particular command needs a terminal output. By default it wont (see 1). 3. If you still need the terminal window - create one, or tell the environment to create one - with selecting the checkbox "Run in terminal window" of the shortcut. And again ... this ARE different OSes, with their own way of performing tasks. Do not expect that they will react the same way, they wont. Just put yourself in the place of an old *nix guy, who have used X, and possibly KDE :), and never Windows. Oh, never mind, I'm sure his reaction will be - what's that shell screen, how stupid :) Cheers -- Svetoslav Milenov (Sunny)

On Friday, September 16, 2005 @ 8:29 AM, Sunny wrote:

On 9/16/05, Greg Wallace wrote:

...

On Friday, September 16, 2005 @ 4:51 AM, Patrick Shanahan wrote:

...

* Greg Wallace [09-16-05 01:54]:

...

I think what I was trying was illogical. I thought maybe you could just click a desktop shortcut and it would launch a shell and run the command.

...

Don't know what makes you think it illogical. It is perfectly logical and _will_ work as you describe. Time to go back to the books. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

Nah. You shouldn't have to go to books for something like this if it's doable. You can do this in Windows. Why make it that hard for a Newbie to do it in Linux. It should be right there if you right click the icon. As for me, I'll remember that it is doable but don't have the time right now to "hit the books".

Greg Wallace

I really hate that. Don't tell me that first time you saw Win'95, you knew how to create a shortcut of DOS program on the desktop, how to set the right memory settings, etc. Without any help or reading. Also - the other OS _was_ designed as a replacement of DOS, but with need for compatibility, so it can make a difference between a DOS and Win program. In *nix - you have executable - always a *nix executable (script or binary, doesn't matter).

What can I say. A reply of "hit the books" seemed curt and unnecessary. If it really is a "hit the books" situation, then I say it's more complicated than it should be. If something is an executable, the default when clicking it should be to execute it.

There's always time for books, and when you come to something new, do not forget that the old one was new in the past as well.

Patrick is right, it is not _illogical_. Some reasons are:

1. The *nix way is that every command, which does its job OK, will not produce any output.

The script has one statement, an echo. Echo is an output statement.

Especially scripts, as they are meant to automate jobs, without user intervention. 2. The job of the graphic environment is _not_ to "think" for you and to guess what you may want. If you click on a command, it will execute it.

No. It doesn't.

Noone told it that this particular command needs a terminal output. By default it wont (see 1). 3. If you still need the terminal window - create one, or tell the environment to create one - with selecting the checkbox "Run in terminal window" of the shortcut.

And again ... this ARE different OSes, with their own way of performing tasks. Do not expect that they will react the same way, they wont. Just put yourself in the place of an old *nix guy, who have used X, and possibly KDE :), and never Windows. Oh, never mind, I'm sure his reaction will be - what's that shell screen, how stupid :)

Cheers

-- Svetoslav Milenov (Sunny)

--

On Friday, September 16, 2005 @ 3:15 PM, Patrick Shanahan wrote: * Greg Wallace [09-16-05 17:57]:

The script has one statement, an echo. Echo is an output statement.

please provide 'ls -la <the-script>'

linux:~ # ls -la Desktop/Hello.bin -rwxr-xr-x 1 root root 10 Sep 15 04:43 Desktop/Hello.bin

Just refuse to trim your quotes, eh?

Most of those quotes aren't mine.

-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

Greg Wallace

On Friday, September 16, 2005 @ 4:14 PM, Patrick Shanahan wrote: <snip>

rt clk desktoop choose create new choose link to application give a name choose permissions choose advanced permissions make user exec say ok choose application enter for command '/home/<you>/Desktop/Hello.bin' choose advanced options choose run in terminal say ok say ok

example cat Desktop/hello.bin

echo "Hello Greg" sleep 100

perms -rwx-------

note: if you do not make a 'sleep xxx' command the window will close quickly and you will not see results.

note2: why does root own 'Hello.bin'? YOU should own it. root is the supreme being on your computer. You should treat it as such.

<snip>

-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2

Thanks for the example. It works fine. At first, the shell popped open and closed so fast that I couldn't see what happened. I went back in and discovered the "Do not close when command exits" option under APPLICATION/Advanced Options/Terminal/Run in Terminal. Selecting that causes the shell to remain open after the command ends. All in all, very nice. I had earlier been able to get it to run via the "Run Command" option off of the start menu, but not from the desktop. When right-clicking on the desktop, I now see that there are basically 3 types of objects you can create there -- a folder, a file (two types, text or HTML), and various types of links. What I needed was the "Link to Application" type of link, as per your instructions. I was trying to make this work by right-clicking the document on the desktop, going to properties, and clicking the button next to "Type". It looked like it was designed to somewhat mirror a Windows system, with file types at the top and applications at the bottom. I couldn't make any headway coming from that direction, but now it would appear that was the wrong way to go about it in the first place (though I still need to play around with that some to see just what it is for). Thanks, Greg Wallace

Anders, On Friday 16 September 2005 16:27, Anders Johansson wrote:

On Friday 16 September 2005 14:51, Patrick Shanahan wrote:

...

* Greg Wallace [09-16-05 01:54]:

...

I think what I was trying was illogical. I thought maybe you could just click a desktop shortcut and it would launch a shell and run the command.

Don't know what makes you think it illogical. It is perfectly logical and _will_ work as you describe. Time to go back to the books.

Patrick, why is it that you see it as your mission to kill this list? This list is meant as a discussion forum between users, it is not meant as a sponsoring site for google. If you know the answer, give it. If not, don't answer. It really is that simple

I'm not sure I think we should coddel every addle-brained, inept poster who just wants personal, customized, "do it for me" help from this list. Catering to that expectation is what will kill this list. I do agree that if you're going to chastise someone, even if it's just to refer them to a search engine, that you should also include some kind of answer content in the reply. I try to follow that rule whenever I have to give some kind of negative feedback. Randall Schulz

On Friday 16 September 2005 04:09, BandiPat wrote:

On Thursday 15 September 2005 07:32 am, Art Fore wrote:

...

I have Xilinx FPGA tools installed from the Xilinx CDROM. I can go to /usr/xilinx/bin and execute the isc binary with Konqueror fine. File

Hi . I have had to odd program that i have had to write a quick script to get them to behave from a desktop icon .. along the lines of cd /usr/xilinx/bin xilinx cd / put this in some directory in your path i have found that bin user/bin or sbin all seem to work not shure of the correct choice it's needs must Then your desktop link points to the script and that should work it has done every time for me so far Oh script needs to be made executable "chmod +x script name" Hope this helps a little .. Pete . -- If Bill Gates had gotten LAID at High School do YOU think there would be a Microsoft ? Of course NOT ! You gotta spend a lot of time at your school Locker stuffing underware up your ass to think , I am going to take on the worlds Computer Industry -------:heard on Cyber Radio.:------- AFFA