Command not found for "sudo ifconfig" when su - xilinx

Support
1

Hi,

I’m using PYNQ-Z1 with v2.4 image. However, it seems sometimes the sudo command doesn’t work for xilinx account but root can work. For example, When I switch to xilinx user, I execute the “sudo ifconfig” which it’s command not found.

However, whole I logout, the root account can work with the command ifconfig. Would you please point out what’s wrong with me ?? Thank you

After opening a terminal in Jupyter, I type the followings :

root@pynq:/home/xilinx# su - xilinx
xilinx@pynq:~$ ifconfig
-su: ifconfig: command not found
xilinx@pynq:~$ sudo ifconfig
[sudo] password for xilinx:
sudo: ifconfig: command not found
xilinx@pynq:~$ !sudo ifconfig
sudo ifconfig ifconfig
sudo: ifconfig: command not found
xilinx@pynq:~$ logout
root@pynq:/home/xilinx# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::218:3eff:fe02:f20e prefixlen 64 scopeid 0x20
inet6 fd5d:beef:beef:beef:218:3eff:fe02:f20e prefixlen 64 scopeid 0x0
ether 00:18:3e:02:f2:0e txqueuelen 1000 (Ethernet)
RX packets 23457 bytes 1222629 (1.2 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1368 bytes 163541 (163.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 27 base 0xb000

2

The jupyter terminal already gives you sudo access. Why would you want to use the xilinx user there? If you really want to use non-root access, you can use the normal serial terminal instead of the jupyter terminal.

3

Not special reason. Just no experience in using root account by default.

Is there any disadvantage if using root account for development work on PYNQ ? Also, it seems file exchange via SAMBA is using xilinx account.