On 2020-08-04 20:44, Tim via users wrote:
Tim:
You know they'll start removing those lights, because the average
user doesn't need to know about them.
ToddAndMargo:
But fortunately those will be the e-cheap-o computers
and they only come with one Ethernet port.
Then they'll replace the
Tim:
>> You know they'll start removing those lights, because the average
>> user doesn't need to know about them.
ToddAndMargo:
> But fortunately those will be the e-cheap-o computers
> and they only come with one Ethernet port.
Then they'll replace the keyboard with a single button, because
On 2020-08-04 00:04, Tim via users wrote:
On Sun, 2020-08-02 at 18:41 -0700, ToddAndMargo via users wrote:
Here is a trick I use when I can't tell who is plugged
into what on the back of a computer:
Networking: blink the Ethernet jack's lights
# ethtool --identify eth1
# ethtool --identify
On Sun, 2020-08-02 at 18:41 -0700, ToddAndMargo via users wrote:
> Here is a trick I use when I can't tell who is plugged
> into what on the back of a computer:
>
> Networking: blink the Ethernet jack's lights
>
> # ethtool --identify eth1
> # ethtool --identify eno1
> # ethtool --identify eno2
On 2020-08-03 07:58, Tom H wrote:
On Mon, Aug 3, 2020 at 4:09 AM ToddAndMargo via users
wrote:
On 2020-08-01 19:41, Tom H wrote:
On Sun, Aug 2, 2020 at 3:24 AM ToddAndMargo via users
wrote:
"disconnected" contains "connected"!
grep -w connected
Awesome. Whole words only. Never used
On Mon, Aug 3, 2020 at 4:09 AM ToddAndMargo via users
wrote:
> On 2020-08-01 19:41, Tom H wrote:
>> On Sun, Aug 2, 2020 at 3:24 AM ToddAndMargo via users
>> wrote:
>>>
>>> "disconnected" contains "connected"!
>>
>> grep -w connected
>
> Awesome. Whole words only. Never used that before.
>
>
On 2020-08-02 06:30, Sam Varshavchik wrote:
ToddAndMargo via users writes:
On 2020-08-01 16:27, Ed Greshko wrote:
[egreshko@meimei ~]$ nmcli device status
DEVICE TYPE STATE CONNECTION
enp2s0 ethernet connected enp2s0
virbr0 bridge
On 2020-08-01 19:41, Tom H wrote:
On Sun, Aug 2, 2020 at 3:24 AM ToddAndMargo via users
wrote:
"disconnected" contains "connected"!
grep -w connected
Awesome. Whole words only. Never used that before.
Thank you!
___
users mailing list --
On 2020-08-01 17:53, ToddAndMargo via users wrote:
On 2020-08-01 17:50, ToddAndMargo via users wrote:
On 2020-08-01 16:27, Ed Greshko wrote:
On 2020-08-02 07:26, Ed Greshko wrote:
On 2020-08-02 07:05, Samuel Sieb wrote:
On 8/1/20 3:20 PM, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo
On 2020-08-02 21:30, Sam Varshavchik wrote:
> ToddAndMargo via users writes:
>
>> On 2020-08-01 16:27, Ed Greshko wrote:
>>> [egreshko@meimei ~]$ nmcli device status
>>> DEVICE TYPE STATE CONNECTION
>>> enp2s0 ethernet connected enp2s0
>>> virbr0
ToddAndMargo via users writes:
On 2020-08-01 16:27, Ed Greshko wrote:
[egreshko@meimei ~]$ nmcli device status
DEVICE TYPE STATE CONNECTION
enp2s0 ethernet connected enp2s0
virbr0 bridge connected virbr0
vnet0 tun
On 08/01/2020 06:50 PM, ToddAndMargo via users wrote:
Ah poop! "disconnected" contains "connected"!
Well, that means that my one-liner will always return the status.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an
On Sat, Aug 01, 2020 at 05:50:58PM -0700, ToddAndMargo via users wrote:
> On 2020-08-01 16:27, Ed Greshko wrote:
> > On 2020-08-02 07:26, Ed Greshko wrote:
> > > On 2020-08-02 07:05, Samuel Sieb wrote:
> > > > On 8/1/20 3:20 PM, Joe Zeff wrote:
> > > > > On 08/01/2020 03:06 PM, ToddAndMargo via
On Sun, Aug 2, 2020 at 3:24 AM ToddAndMargo via users
wrote:
>
> "disconnected" contains "connected"!
grep -w connected
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora
On 8/1/20 5:53 PM, ToddAndMargo via users wrote:
On 2020-08-01 17:50, ToddAndMargo via users wrote:
On 2020-08-01 16:27, Ed Greshko wrote:
On 2020-08-02 07:26, Ed Greshko wrote:
On 2020-08-02 07:05, Samuel Sieb wrote:
On 8/1/20 3:20 PM, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo
On 2020-08-01 17:50, ToddAndMargo via users wrote:
On 2020-08-01 16:27, Ed Greshko wrote:
On 2020-08-02 07:26, Ed Greshko wrote:
On 2020-08-02 07:05, Samuel Sieb wrote:
On 8/1/20 3:20 PM, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or
On 2020-08-01 16:15, ToddAndMargo via users wrote:
On 2020-08-01 15:20, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or Raku?
$ nmcli device status | grep eno2 | awk '{print $3}'
connected
nmcli device status | grep eno2 |
On 2020-08-01 16:27, Ed Greshko wrote:
On 2020-08-02 07:26, Ed Greshko wrote:
On 2020-08-02 07:05, Samuel Sieb wrote:
On 8/1/20 3:20 PM, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or Raku?
$ nmcli device status | grep eno2 | awk
On 2020-08-02 07:26, Ed Greshko wrote:
> On 2020-08-02 07:05, Samuel Sieb wrote:
>> On 8/1/20 3:20 PM, Joe Zeff wrote:
>>> On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or Raku?
$ nmcli device status | grep eno2 | awk '{print $3}'
On 2020-08-02 07:05, Samuel Sieb wrote:
> On 8/1/20 3:20 PM, Joe Zeff wrote:
>> On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
>>>
>>> Any way around grep and awk or Raku?
>>>
>>> $ nmcli device status | grep eno2 | awk '{print $3}'
>>> connected
>>
>> nmcli device status | grep
On 8/1/20 4:16 PM, ToddAndMargo via users wrote:
On 2020-08-01 16:05, Samuel Sieb wrote:
On 8/1/20 3:20 PM, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or Raku?
$ nmcli device status | grep eno2 | awk '{print $3}'
connected
On 2020-08-01 15:20, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or Raku?
$ nmcli device status | grep eno2 | awk '{print $3}'
connected
nmcli device status | grep eno2 | grep connected
This will either return connected, or a
On 2020-08-01 16:05, Samuel Sieb wrote:
On 8/1/20 3:20 PM, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or Raku?
$ nmcli device status | grep eno2 | awk '{print $3}'
connected
nmcli device status | grep eno2 | grep connected
On 8/1/20 3:20 PM, Joe Zeff wrote:
On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or Raku?
$ nmcli device status | grep eno2 | awk '{print $3}'
connected
nmcli device status | grep eno2 | grep connected
This will either return connected, or a
On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
Any way around grep and awk or Raku?
$ nmcli device status | grep eno2 | awk '{print $3}'
connected
nmcli device status | grep eno2 | grep connected
This will either return connected, or a blank line, without using awk or
any
On 2020-08-01 14:10, Samuel Sieb wrote:
On 8/1/20 2:06 PM, Samuel Sieb wrote:
On 8/1/20 1:43 PM, ToddAndMargo via users wrote:
Now the specify as "specified" device:
$ nmcli device status eno2
Error: invalid extra argument 'eno2'.
"status" doesn't take any arguments. Maybe
On 2020-08-02 05:03, ToddAndMargo via users wrote:
> Is there a way to get just "connected" back from
> nmcli?
Not that I know of. At least not at 05:10,
--
The key to getting good answers is to ask good questions.
___
users mailing list --
On 8/1/20 2:06 PM, Samuel Sieb wrote:
On 8/1/20 1:43 PM, ToddAndMargo via users wrote:
Now the specify as "specified" device:
$ nmcli device status eno2
Error: invalid extra argument 'eno2'.
"status" doesn't take any arguments. Maybe "nmcli d show eno2" would do
what you want?
On 8/1/20 1:43 PM, ToddAndMargo via users wrote:
Now the specify as "specified" device:
$ nmcli device status eno2
Error: invalid extra argument 'eno2'.
"status" doesn't take any arguments. Maybe "nmcli d show eno2" would do
what you want?
On 2020-08-01 14:03, ToddAndMargo via users wrote:
On 2020-08-01 13:57, Ed Greshko wrote:
On 2020-08-02 04:43, ToddAndMargo via users wrote:
Now the specify as "specified" device:
$ nmcli device status eno2
Error: invalid extra argument 'eno2'.
Okay, what am I doing
On 2020-08-01 13:57, Ed Greshko wrote:
On 2020-08-02 04:43, ToddAndMargo via users wrote:
Now the specify as "specified" device:
$ nmcli device status eno2
Error: invalid extra argument 'eno2'.
Okay, what am I doing wrong/misreading?
If you were to use "tab completion" you'd find
On 2020-08-01 13:55, Earl Terwilliger via users wrote:
Hi All,
I am trying to use the nmcli command to cough up
(a highly technical term) the connected state on
a particular network interface.
According to the man page:
nmcli device {status | show | set | connect | reapply
On 2020-08-02 04:43, ToddAndMargo via users wrote:
> Now the specify as "specified" device:
>
> $ nmcli device status eno2
> Error: invalid extra argument 'eno2'.
>
> Okay, what am I doing wrong/misreading?
If you were to use "tab completion" you'd find that upon hitting tab after
> Hi All,
>
> I am trying to use the nmcli command to cough up
> (a highly technical term) the connected state on
> a particular network interface.
>
> According to the man page:
>
> nmcli device {status | show | set | connect | reapply
> | modify | disconnect | delete |
Hi All,
I am trying to use the nmcli command to cough up
(a highly technical term) the connected state on
a particular network interface.
According to the man page:
nmcli device {status | show | set | connect | reapply
| modify | disconnect | delete | monitor |
35 matches
Mail list logo
