[Solved] Mylivecd - worked yesterday, broken today

[AS]

kde here, this is my output of the same command, /usr/sbin is set up from /etc/profile/kde4env.sh which clearly it's not installed in your system.

/etc/profile.d/10lang.csh:    set consoletype=`/sbin/consoletype stdout`
/etc/profile.d/10lang.csh:                            if { /sbin/consoletype fg } then
/etc/profile.d/10lang.csh:                              if { /sbin/consoletype fg } then
/etc/profile.d/10lang.sh:      consoletype=$(/sbin/consoletype stdout)
/etc/profile.d/10lang.sh:               if [ -x /bin/unicode_start ] && /sbin/consoletype fg ; then
/etc/profile.d/10lang.sh:               [ -x /bin/unicode_stop ] && /sbin/consoletype fg && /bin/unicode_stop
/etc/profile.d/kde4env.sh:    PATH=/usr/bin:/usr/sbin:/usr/lib/kde4/libexec:/bin:/sbin:/usr/X11R6/bin:/usr/games:/usr/local/bin:/usr/local/sbin
/etc/profile.d/kde4env.sh:    PATH=$PATH:/usr/bin:/usr/sbin:/usr/lib/kde4/libexec:/bin:/sbin:/usr/X11R6/bin:/usr/games:/usr/local/bin:/usr/local/sbin

To fix your problem on the fly, try the following:

PATH=$PATH:/usr/bin:/sbin
export PATH
mylivecd test.iso

On the long run further investigation is needed to understand if the problem is related only to your system or not ...

AS

[Hallvor]

Code: [Select]

[root@localhost ~]# PATH=$PATH:/usr/bin:/sbin
[root@localhost ~]# export PATH
[root@localhost ~]# mylivecd test.iso
bash: mylivecd: command not found
[root@localhost ~]#
Sorry, that did not work.

[AS]

my typo sorry, I lost one 's' in /usr/sbin:

PATH=$PATH:/usr/sbin:/sbin
export PATH
mylivecd test.iso

AS

[Hallvor]

It seems to work now! Thank you so much! 

[AS]

It seems to work now! Thank you so much! 

glad it worked, still your system need to be fixed to have /usr/sbin and /sbin in your env PATH by default.

please post your file /root/.bashrc

AS

[Neal ManBear]

Your /root/.bashrc file should have this:

# .bashrc

PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/lib/kde4/libexec
ENV=$HOME/.bashrc
USERNAME="root"
export USERNAME ENV PATH

# Source global definitions
if [ -f /etc/bashrc ]; then
   . /etc/bashrc
fi

# This line was appended by KDE
# Make sure our customised gtkrc file is loaded.
export GTK2_RC_FILES=$HOME/.gtkrc-2.0
export PS1='\[\033[01;31m\][\u@\h \W]\$\[\033[00m\] '

This is from the LXDE version.

[Hallvor]

Your /root/.bashrc file should have this:

# .bashrc

PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/lib/kde4/libexec
ENV=$HOME/.bashrc
USERNAME="root"
export USERNAME ENV PATH

# Source global definitions
if [ -f /etc/bashrc ]; then
   . /etc/bashrc
fi

# This line was appended by KDE
# Make sure our customised gtkrc file is loaded.
export GTK2_RC_FILES=$HOME/.gtkrc-2.0
export PS1='\[\033[01;31m\][\u@\h \W]\$\[\033[00m\] '

This is from the LXDE version.

Thank you! Should there be any difference in the file belonging to root and the user's? Or would copying it to both be OK?

[Neal ManBear]

Yes, there can be differences in the file for users, but in this case it is the file in /root that we are concerned about. I'm also curious as to how and why your .bashrc would have been changed from the default.

[Hallvor]

Yes, there can be differences in the file for users, but in this case it is the file in /root that we are concerned about. I'm also curious as to how and why your .bashrc would have been changed from the default.

It may have happened when copying user config files to root and /etc/skel

[Neal ManBear]

Yes, there can be differences in the file for users, but in this case it is the file in /root that we are concerned about. I'm also curious as to how and why your .bashrc would have been changed from the default.

It may have happened when copying user config files to root and /etc/skel

  Copying user files to /etc/skel is fine, if you intend to create other users with the same profile, but making such changes to /root is not advisable. You can make problem-causing changes.

[Hallvor]

Yes, there can be differences in the file for users, but in this case it is the file in /root that we are concerned about. I'm also curious as to how and why your .bashrc would have been changed from the default.

It may have happened when copying user config files to root and /etc/skel

  Copying user files to /etc/skel is fine, if you intend to create other users with the same profile, but making such changes to /root is not advisable. You can make problem-causing changes.

I must be missing something: So would you instead make changes directly to /root, and afterwards copy the files over to /etc/skel and make new users from there?

[Neal ManBear]

Yes, there can be differences in the file for users, but in this case it is the file in /root that we are concerned about. I'm also curious as to how and why your .bashrc would have been changed from the default.

It may have happened when copying user config files to root and /etc/skel

  Copying user files to /etc/skel is fine, if you intend to create other users with the same profile, but making such changes to /root is not advisable. You can make problem-causing changes.

I must be missing something: So would you instead make changes directly to /root, and afterwards copy the files over to /etc/skel and make new users from there?

No. Leave /root alone. New users get their set up from /etc/skel, not /root.

[Hallvor]

Yes, there can be differences in the file for users, but in this case it is the file in /root that we are concerned about. I'm also curious as to how and why your .bashrc would have been changed from the default.

It may have happened when copying user config files to root and /etc/skel

  Copying user files to /etc/skel is fine, if you intend to create other users with the same profile, but making such changes to /root is not advisable. You can make problem-causing changes.

I must be missing something: So would you instead make changes directly to /root, and afterwards copy the files over to /etc/skel and make new users from there?

No. Leave /root alone. New users get their set up from /etc/skel, not /root.

OK. Thank you!