Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #261517
| From | Charlie <ariestao@skymesh.com.au> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: su |
| Date | 2023-09-06 08:00 +0200 |
| Message-ID | <HaTK2-72jv-9@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <Hax6N-6O9x-1@gated-at.bofh.it> <HaKdH-6Wyq-11@gated-at.bofh.it> <HaKQp-6X0R-21@gated-at.bofh.it> <HaRfb-70Vt-3@gated-at.bofh.it> <HaRId-714u-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, 5 Sep 2023 23:41:45 -0400 Greg Wooledge <greg@wooledge.org> wrote: > To perform that installation, you run "su", which gives you a root > shell, and then you do something like "make install". > > But the Red Hat answer says you should use "su -" instead, to become > root. What happens now? You've created a login shell. Now you're no > longer in the directory where your source code was extracted and > compiled. You're in root's $HOME directory. So "make install" fails. > > You could use a "cd" command to get to the source code. But "cd -" > won't work, because the previous working directory is not known to > the root login shell. The root login shell has intentionally > discarded everything from your previous shell, including the old > working directory's name. So you can't "cd -", but instead, you have > to re-type the entire path to the source code directory. Or copy and > paste it out of your shell prompt, if that's still visible on the > screen, and if it happens to contain the entire path. > > Wouldn't it be *nicer* if su simply WORKED?! > > You can make su work by creating a ONE-LINE CONFIGURATION FILE. Thank you Greg -- ** ** ** ** ** ** ** ** ** ** Registered Linux User:- 329524 *********************************************** There is no exercise better for the heart than reaching down and lifting people up.-- John Holmes *********************************************** Debian GNU/Linux - just the best way to create magic _______________________________________________
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
just a question about the iwlwifi_20230515-3 file Maureen L Thomas <silverorb@verizon.net> - 2023-09-05 06:30 +0200
Re: just a question about the iwlwifi_20230515-3 file jeremy ardley <jeremy.ardley@gmail.com> - 2023-09-05 07:50 +0200
Re: just a question about the iwlwifi_20230515-3 file Greg Wooledge <greg@wooledge.org> - 2023-09-05 13:20 +0200
Re: just a question about the iwlwifi_20230515-3 file "Andrew M.A. Cater" <amacater@einval.com> - 2023-09-05 21:50 +0200
Re: just a question about the iwlwifi_20230515-3 file Charles Curley <charlescurley@charlescurley.com> - 2023-09-05 22:30 +0200
Re: just a question about the iwlwifi_20230515-3 file Charles Curley <charlescurley@charlescurley.com> - 2023-09-06 00:40 +0200
Re: just a question about the iwlwifi_20230515-3 file Michel Verdier <mv524@free.fr> - 2023-09-06 05:20 +0200
Re: just a question about the iwlwifi_20230515-3 file Max Nikulin <manikulin@gmail.com> - 2023-09-06 06:00 +0200
Re: just a question about the iwlwifi_20230515-3 file debian-user@howorth.org.uk - 2023-09-06 12:30 +0200
Re: just a question about the iwlwifi_20230515-3 file <tomas@tuxteam.de> - 2023-09-06 13:00 +0200
Re: just a question about the iwlwifi_20230515-3 file Greg Wooledge <greg@wooledge.org> - 2023-09-05 22:30 +0200
Re: just a question about the iwlwifi_20230515-3 file Michel Verdier <mv524@free.fr> - 2023-09-06 05:20 +0200
Re: su Greg Wooledge <greg@wooledge.org> - 2023-09-06 05:50 +0200
Re: su Charlie <ariestao@skymesh.com.au> - 2023-09-06 08:00 +0200
Re: su Max Nikulin <manikulin@gmail.com> - 2023-09-06 09:40 +0200
Re: su Vincent Lefevre <vincent@vinc17.net> - 2023-09-14 12:40 +0200
Re: su Max Nikulin <manikulin@gmail.com> - 2023-09-14 16:30 +0200
Re: su Vincent Lefevre <vincent@vinc17.net> - 2023-09-14 17:30 +0200
Re: su Max Nikulin <manikulin@gmail.com> - 2023-09-15 04:20 +0200
Re: su Michel Verdier <mv524@free.fr> - 2023-09-06 11:10 +0200
Re: just a question about the iwlwifi_20230515-3 file Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-09-05 12:00 +0200
Re: just a question about the iwlwifi_20230515-3 file Charles Curley <charlescurley@charlescurley.com> - 2023-09-05 17:20 +0200
Re: just a question about the iwlwifi_20230515-3 file David Wright <deblis@lionunicorn.co.uk> - 2023-09-05 20:40 +0200
Re: just a question about the iwlwifi_20230515-3 file Charles Curley <charlescurley@charlescurley.com> - 2023-09-05 22:50 +0200
Re: just a question about the iwlwifi_20230515-3 file Greg Wooledge <greg@wooledge.org> - 2023-09-06 00:50 +0200
Re: just a question about the iwlwifi_20230515-3 file Charles Curley <charlescurley@charlescurley.com> - 2023-09-06 01:00 +0200
Re: just a question about the iwlwifi_20230515-3 file Max Nikulin <manikulin@gmail.com> - 2023-09-06 09:50 +0200
Re: just a question about the iwlwifi_20230515-3 file piorunz <piorunz@gmx.com> - 2023-09-06 00:00 +0200
Re: just a question about the iwlwifi_20230515-3 file Greg Wooledge <greg@wooledge.org> - 2023-09-06 00:20 +0200
csiph-web