> The 'ip' command is in /bin/ip and always available in PATH. It is
> the currently recommended swiss-army chainsaw network tool. Give it a
> try.
>
> $ ip addr show
> Or:
> $ ip addr show eth0
>
> And of course you can add the sbins to your PATH in .profile so that
> you have what you wa
Carlos Alberto Lopez Perez wrote:
> You can't imagine how much I blame Debian each time I have to type the
> full path "/sbin/ifconfig" as a non-root user on virtual servers to just
> know the IP address the DHCP server assigned to the machine.
The 'ip' command is in /bin/ip and always available i
Ulrich Dangel writes:
> A similar solution was discussed some time ago by merging all the /bin
> and /sbin directories together (based on the UsrMove from Fedora) but
> the discussion wasn't really productive iirc.
Wasn't that discussion about merging /bin and /usr/bin? Or did we also
have the
On 08/08/12 04:15, Russ Allbery wrote:
>> Currently the default PATH for Debian does not include /sbin, /usr/sbin,
>> nor /usr/local/sbin. If an user wants to run a program in either /sbin/
>> or /usr/sbin the full path must be specified.
>
> I don't see any point in doing this as opposed to just
On 08/08/12 04:11, Marco d'Itri wrote:
>> Changing the default PATH for normal users to include /sbin, /usr/sbin as
>> well as
>> /usr/local/sbin would be a great thing for simplifying command line usage for
>> normal users.
> Fedora did it a few months ago, so probably we should do it as well to
On 08/08/12 03:16, Ulrich Dangel wrote:
> Currently the default PATH for Debian does not include /sbin, /usr/sbin, nor
> /usr/local/sbin. If an user wants to run a program in either /sbin/ or
> /usr/sbin
> the full path must be specified.
>
> Some programs don't necessarily need root privileges l
Ulrich Dangel writes:
> Currently the default PATH for Debian does not include /sbin, /usr/sbin,
> nor /usr/local/sbin. If an user wants to run a program in either /sbin/
> or /usr/sbin the full path must be specified.
I don't see any point in doing this as opposed to just moving everything
from
On Aug 08, Ulrich Dangel wrote:
> Changing the default PATH for normal users to include /sbin, /usr/sbin as
> well as
> /usr/local/sbin would be a great thing for simplifying command line usage for
> normal users.
Fedora did it a few months ago, so probably we should do it as well to
minimize t
On 08/08/12 03:54, Clint Adams wrote:
> On Wed, Aug 08, 2012 at 03:48:48AM +0200, Ulrich Dangel wrote:
>> So ignore the sudo part as it should be no problem. The bash completion even
>> changes PATH to contain the sbin directories for sudo but zsh seems to honor
>> PATH
>> and doesn't extend to ch
On Wed, Aug 08, 2012 at 03:48:48AM +0200, Ulrich Dangel wrote:
> So ignore the sudo part as it should be no problem. The bash completion even
> changes PATH to contain the sbin directories for sudo but zsh seems to honor
> PATH
> and doesn't extend to check for programs.
Perhaps you have changed
On 08/08/12 03:27, The Fungi wrote:
> Are you certain? For me, 'ifconfig' as a normal user returns
> "command not found" but 'sudo ifconfig' works just fine...
I was based on my experiments[1]. But I discovered that my
/etc/sudoers didn't contain following config line:
Defaults secure_path
On 2012-08-08 03:16:59 +0200 (+0200), Ulrich Dangel wrote:
[...]
> To run a program as root with sudo the user must specify the
> correct path, e.g. sudo /usr/sbin/visudo instead of just sudo
> visudo or su -c visudo.
[...]
Are you certain? For me, 'ifconfig' as a normal user returns
"command not
Currently the default PATH for Debian does not include /sbin, /usr/sbin, nor
/usr/local/sbin. If an user wants to run a program in either /sbin/ or /usr/sbin
the full path must be specified.
Some programs don't necessarily need root privileges like blkid, iwconfig,
ifconfig, service etc. and can b
Hi!
On Mon, 2012-08-06 at 15:37:11 +0200, Jakub Wilk wrote:
> The following package pairs:
> 1) are co-installable,
> 2) both ship binaries with the same name, but in different
> directories within $PATH (e.g. one in /usr/bin, another in
> /usr/sbin):
Ralf Treinen has been running automated tests
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
* Package name: libfile-data-perl
Version : 1.16
Upstream Author : Richard Foley
* URL : http://search.cpan.org/dist/File-Data/
* License : Artistic or GPL-1+
Programming Lang: Perl
Description :
On 6 August 2012 14:37, Jakub Wilk wrote:
> The following package pairs:
> 1) are co-installable,
> 2) both ship binaries with the same name, but in different directories
> within $PATH (e.g. one in /usr/bin, another in /usr/sbin):
>
> sethdlc: ax25-tools dahdi
> crm: crm114 pacemaker
> cutter: cu
Package: wnpp
Severity: wishlist
Owner: Clint Byrum
* Package name: python-shelltoolbox
Version : 0.2.1+bzr17
Upstream Author : Launchpad Yellow Squad
* URL : https://launchpad.net/python-shelltoolbox
* License : GPL-3
Programming Lang: Python
Description
Package: wnpp
Severity: wishlist
Owner: Edward Tomasz Napierala
* Package name: confctl
Version : 1.1
Upstream Author : Edward Tomasz Napierala
* URL : https://github.com/trasz/confctl/
* License : BSD
Programming Lang: C
Description : Utility to acce
> guess: nvram-wakeup sgt-puzzles
That's an awfully generic name for a program which gets run exactly once per
motherboard to figure out some hardware configuration :-(
Not knowing the game I would recommend renaming the nvram-wakeup thingy.
Olaf
--
To UNSUBSCRIBE, email to debian-devel-requ..
Ian Jackson wrote:
> So, Simon, if these puzzle names should be qualified to make them more
> unique on the PATH, what formulaic change should be made ? My
> recommendation would be "sgt-*" on the grounds that that's unlikely to
> conflict, although it might of course end up with your initials on
Ben Hutchings writes ("Re: node-like file conflicts"):
> On Tue, Aug 07, 2012 at 04:14:19PM +0200, Jakub Wilk wrote:
> [...]
> > guess: nvram-wakeup sgt-puzzles
> [...]
> > Ben Hutchings
> >sgt-puzzles
> [...]
>
> There are a lot of short and generic names in this package. I
> appended 'game
On Tue, Aug 07, 2012 at 04:14:19PM +0200, Jakub Wilk wrote:
[...]
> guess: nvram-wakeup sgt-puzzles
[...]
> Ben Hutchings
>sgt-puzzles
[...]
There are a lot of short and generic names in this package. I
appended 'game' to some of them to avoid such conflicts when
originally uploading. 'gues
* Josselin Mouette , 2012-08-07, 08:13:
The following package pairs:
1) are co-installable,
2) both ship binaries with the same name, but in different directories
within $PATH (e.g. one in /usr/bin, another in /usr/sbin):
Thanks.
There’s also epiphany (maybe your forgot /usr/games).
Hasn't
Package: wnpp
Severity: wishlist
Owner: Ritesh Raj Sarraf
* Package name: seascope
Version : 0.6
Upstream Author : Anil Kumar
* URL : http://code.google.com/p/seascope
* License : BSD
Programming Lang: Python
Description : source code navigation tool
Josselin Mouette writes ("Re: node-like file conflicts"):
> Le lundi 06 août 2012 à 15:37 +0200, Jakub Wilk a écrit :
> > The following package pairs:
> > 1) are co-installable,
> > 2) both ship binaries with the same name, but in different directories
> > within $PATH (e.g. one in /usr/bin, anot
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
* Package name: libio-detect-perl
Version : 0.004
Upstream Author : Toby Inkster
* URL : https://metacpan.org/release/IO-Detect
* License : Artistic or GPL-1+
Programming Lang: Perl
Description :
26 matches
Mail list logo
