Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.

From	Brian <ad44@cityscape.co.uk>
Newsgroups	linux.debian.user
Subject	Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please.
Date	2016-09-27 18:00 +0200
Message-ID	<sm2Xv-2S0-15@gated-at.bofh.it> (permalink)
References	(5 earlier) <sllSx-1a9-1@gated-at.bofh.it> <slLtE-wZ-3@gated-at.bofh.it> <slLWF-Gc-5@gated-at.bofh.it> <sm1oK-260-37@gated-at.bofh.it> <sm1I5-2cv-15@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue 27 Sep 2016 at 10:29:44 -0400, Greg Wooledge wrote:

> On Tue, Sep 27, 2016 at 03:15:54PM +0100, Brian wrote:
> > Ok, let's go along with ~/.xsessionrc being the simplest way for a user
> > to configure his X session. I'll follow the advice on the wiki and have
> > 
> >   PATH=~/bin:$PATH
> >   xterm &
> >   iceweasel &
> >   exec fvwm
> 
> No, this is not what I advised.  You don't start a window manager from
> this file.

You advised ~/.xsessionrc as the best user route to configuration.
Starting a WM is a crucial part of configuration.

> > Putting 'exec fvwm' in ~/.xsession is the solution, of course; it's your
> > best friend, so may as well put everything else there. What price this
> > upstart ~/.xsessionrc? Does it ever get anything right? The only thing
> > it is good for is getting round restrictions set by the administrator.
> 
> You are not a beginner.  You're advanced.

I was trying to put myself in the same position as one. The target
audience matters.

> A beginner would just install *one* window manager, and this
> would be executed automatically by the Debian X session (via the
> /usr/bin/x-window-manager symlink ultimately).  (S)he would use
> a ~/.xsessionrc file only to set the PATH variable, or JAVA_HOME, or
> whatever the original question is.

Most people (beginners or not) install GNOME, KDE etc and that's it.
They see no need to go beyond that. Nothing wrong there. They are not
your audience.

> You don't need a ~/.xsession file until you get to the point where
> you want to install multiple WMs at the same time and choose among
> them.  And even then, at that point, many beginners will still prefer
> update-alternatives (as root) over editing a ~/.xsession file in their
> own home directory.  This may shock you, since you have a strong
> Linux or Unix background, but I see it all the time.  These are the
> same people who think putting a colored PS1 prompt in /etc/bash.bashrc
> is a Really Awesome Idea.

We are talking about a wiki which concentrates on user configuration;
what root can do is immaterial.

You need a ~/.xsession file when you need a ~/.xsession file. Isn't it
one purpose of the wiki to explain how it fits into the traditional X
configuration and why one might be useful. Instead, we appear to have
~/.xsessionrc promoted as the One True Way; how did you come to that
conclusion?

-- 
Brian.
Who is sometimes bemused but very rarely shocked.

Thread

Failed to execute child process (no such file or directory), but the  script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Tony Baldwin <tonybaldwin@gmx.com> - 2016-09-21 15:50 +0200
  Re: Failed to execute child process (no such file or directory) ... "Thomas Schmitt" <scdbackup@gmx.net> - 2016-09-21 16:00 +0200
  Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-21 16:10 +0200
    Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Tony Baldwin <tonybaldwin@gmx.com> - 2016-09-21 16:50 +0200
      Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-21 17:10 +0200
        Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Anthony Baldwin <baldwinlinguas@gmx.com> - 2016-09-21 21:30 +0200
          Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users,  especially take a look, please. David Wright <deblis@lionunicorn.co.uk> - 2016-09-22 04:30 +0200
            Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 15:20 +0200
              Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. <tomas@tuxteam.de> - 2016-09-22 15:30 +0200
              Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 16:00 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-22 16:30 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Ric Moore <wayward4now@gmail.com> - 2016-09-22 18:30 +0200
              Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-22 16:00 +0200
              Re: Failed to execute child process (no such file or directory),  but the script DOES exist in $HOME/bin, openbox users, especially take a  look, please. Tixy <tixy@yxit.co.uk> - 2016-09-22 16:20 +0200
                Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 17:00 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Darac Marjal <mailinglist@darac.org.uk> - 2016-09-22 17:20 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-22 18:40 +0200
                Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 22:20 +0200
                Re: Failed to execute child process (no such file or directory),  but the script DOES exist in $HOME/bin, openbox users, especially take a  look, please. Dominic Knight <dominicknight@gmx.com> - 2016-09-23 01:30 +0200
                Re: Failed to execute child process (no such file or directory),  but the script DOES exist in $HOME/bin, openbox users, especially take a  look, please. Curt <curty@free.fr> - 2016-09-23 11:00 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. <tomas@tuxteam.de> - 2016-09-23 11:40 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. tomas@tuxteam.de - 2016-09-23 11:50 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-23 18:40 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-24 21:40 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-25 20:00 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-26 23:20 +0200
                Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-26 23:50 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Seeker <seeker5528@comcast.net> - 2016-09-27 07:50 +0200
                Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-27 14:30 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-27 16:20 +0200
                Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-27 16:40 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-27 18:00 +0200
                Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-27 18:10 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-27 21:00 +0200
                Re: Failed to execute child process (no such file or directory),  but the script DOES exist in $HOME/bin, openbox users, especially take a  look, please. "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu> - 2016-09-27 00:00 +0200
                Re: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-27 14:30 +0200
                Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-22 18:00 +0200
                Re: Failed to execute child process (no such file or directory),  but the script DOES exist in $HOME/bin, openbox users, especially take a  look, please. Tixy <tixy@yxit.co.uk> - 2016-09-22 21:00 +0200
                Resolved: Failed to execute child process (no such file or  directory), but the script DOES exist in $HOME/bin, openbox users, especially  take a look, please. Tony Baldwin <tonybaldwin@gmx.com> - 2016-09-22 17:30 +0200
                Re: Resolved: Failed to execute child process (no such file or  directory), but the script DOES exist in $HOME/bin, openbox users, especially  take a look, please. Seeker <seeker5528@comcast.net> - 2016-09-22 18:10 +0200
                Re: Resolved: Failed to execute child process (no such file or directory), but the script DOES exist in $HOME/bin, openbox users, especially take a look, please. Greg Wooledge <wooledg@eeg.ccf.org> - 2016-09-22 18:20 +0200
                Re: Resolved: Failed to execute child process (no such file or  directory), but the script DOES exist in $HOME/bin, openbox users,  especially take a look, please. Brian <ad44@cityscape.co.uk> - 2016-09-22 19:50 +0200
                Re: Resolved: Failed to execute child process (no such file or  directory), but the script DOES exist in $HOME/bin, openbox users, especially  take a look, please. Seeker <seeker5528@comcast.net> - 2016-09-23 03:30 +0200
                Re: Resolved: Failed to execute child process (no such file or  directory), but the script DOES exist in $HOME/bin, openbox users, especially  take a look, please. Seeker <seeker5528@comcast.net> - 2016-09-23 19:10 +0200
                Re: Resolved: Failed to execute child process (no such file or  directory), but the script DOES exist in $HOME/bin, openbox users,  especially take a look, please. Brian <ad44@cityscape.co.uk> - 2016-09-23 19:30 +0200
                Re: Resolved: Failed to execute child process (no such file or  directory), but the script DOES exist in $HOME/bin, openbox users, especially  take a look, please. Seeker <seeker5528@comcast.net> - 2016-09-24 08:40 +0200
              Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-22 21:10 +0200
              Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Brian <ad44@cityscape.co.uk> - 2016-09-22 21:50 +0200
          Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Seeker <seeker5528@comcast.net> - 2016-09-22 18:20 +0200
  Re: Failed to execute child process (no such file or directory), but  the script DOES exist in $HOME/bin, openbox users, especially take a look,  please. Darac Marjal <mailinglist@darac.org.uk> - 2016-09-21 16:10 +0200

csiph-web