Page 3 of 3 FirstFirst 123
Results 21 to 26 of 26

Thread: Having issues on upgrading 18.04 to latest version

  1. #21
    Join Date
    Nov 2007
    Location
    Coldwater, OH
    Beans
    534
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Having issues on upgrading 18.04 to latest version

    Code:
    tim@mail:~$ -bash: syntax error near unexpected token `newline'
    > tim@mail:~$         ether d4:3d:7e:e2:7c:xx  txqueuelen 1000  (Ethernet)
    > -bash: syntax error near unexpected token `('
    -bash: syntax error near unexpected token `('
    tim@mail:~$ tim@mail:~$         RX packets 38840380  bytes 2420519911 (2.4 GB)
    -bash: syntax error near unexpected token `('
    tim@mail:~$ -bash: syntax error near unexpected token `('
    > tim@mail:~$         RX errors 0  dropped 0  overruns 0  frame 0
    > RX: command not found
    > tim@mail:~$         TX packets 1013865  bytes 187634619 (187.6 MB)
    > -bash: syntax error near unexpected token `('
    -bash: syntax error near unexpected token `('
    tim@mail:~$ tim@mail:~$         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    TX: command not found
    tim@mail:~$
    tim@mail:~$
    tim@mail:~$ ERROR: cannot create file run/systemd/network/10-netplan-enp2s0: Failed to create file “/run/systemd/network/10-netplan-enp2s0.network.FRVF50”: Permission denied
    ERROR:: command not found
    tim@mail:~$
    tim@mail:~$ An error occurred: the configuration could not be generated
    An: command not found
    tim@mail:~$
    tim@mail:~$ Reverting.
    Reverting.: command not found
    tim@mail:~$ Something really bad happened while reverting config: [Errno 13] Permission denied: '10-netplan-enp2s0.network'
    Something: command not found
    tim@mail:~$ You should verify the netplan YAML in /etc/netplan and probably run 'netplan apply' again.
    You: command not found
    tim@mail:~$ tim@mail:~$ sudo netplan try
    tim@mail:~$: command not found
    tim@mail:~$ Warning: Stopping systemd-networkd.service, but it can still be activated by:
    Warning:: command not found
    tim@mail:~$   systemd-networkd.socket
    systemd-networkd.socket: command not found
    tim@mail:~$ Do you want to keep these settings?
    Do: command not found
    tim@mail:~$
    tim@mail:~$
    tim@mail:~$ Press ENTER before the timeout to accept the new configuration
    Press: command not found
    tim@mail:~$
    tim@mail:~$
    tim@mail:~$ Changes will revert in 114 seconds
    Changes: command not found
    tim@mail:~$
    tim@mail:~$ tim@mail:~$ networkctl list
    tim@mail:~$: command not found
    tim@mail:~$ IDX LINK             TYPE               OPERATIONAL SETUP
    IDX: command not found
    tim@mail:~$   1 lo               loopback           carrier     unmanaged
    1: command not found
    tim@mail:~$   2 enp2s0           ether              routable    configured
    2: command not found
    tim@mail:~$
    tim@mail:~$
    tim@mail:~$ ●        State: routable
    ●: command not found
    tim@mail:~$        Address: 70.33.xxx.xxx on enp2s0
    Address:: command not found
    tim@mail:~$                 fe80::d63d:7eff:fxx2:7cxx on enp2s0
    fe80::d63d:7eff:fxx2:7cxx: command not found
    tim@mail:~$        Gateway: 70.33.xxx.xxx on enp2s0
    Gateway:: command not found
    tim@mail:~$            DNS: 70.33.168.193
    DNS:: command not found
    tim@mail:~$                 1.1.1.1
    1.1.1.1: command not found
    tim@mail:~$            NTP: 129.6.15.28
    NTP:: command not found
    tim@mail:~$
    tim@mail:~$ tim@mail:~$ resolvectl status
    tim@mail:~$: command not found
    tim@mail:~$ resolvectl: command not found
    resolvectl:: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$
    Code:
    : No such file or directory
    tim@mail:~$: command not found
    tim@mail:~$ TX: command not found
    TX:: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
    -bash: UP,LOOPBACK,RUNNING: No such file or directory
    tim@mail:~$ -bash: UP,LOOPBACK,RUNNING: No such file or directory
    -bash:: command not found
    tim@mail:~$ tim@mail:~$         inet 127.0.0.1  netmask 255.0.0.0
    tim@mail:~$: command not found
    tim@mail:~$
    tim@mail:~$ Command 'inet' not found, did you mean:
    Command: command not found
    tim@mail:~$
    tim@mail:~$   command 'inetd' from deb openbsd-inetd
    
    Command 'inetd' not found, but can be installed with:
    
    sudo apt install openbsd-inetd
    
    tim@mail:~$   command 'dnet' from deb golang-libnetwork
    
    Command 'dnet' not found, but can be installed with:
    
    sudo apt install golang-libnetwork
    
    tim@mail:~$   command 'net' from deb samba-common-bin
    
    Command 'net' not found, but can be installed with:
    
    sudo apt install samba-common-bin
    
    tim@mail:~$   command 'init' from deb systemd-sysv
    Too many arguments.
    tim@mail:~$
    tim@mail:~$ Try: sudo apt install <deb name>
    -bash: syntax error near unexpected token `newline'
    tim@mail:~$
    tim@mail:~$ tim@mail:~$         inet6 ::1  prefixlen 128  scopeid 0x10<host>
    -bash: syntax error near unexpected token `newline'
    tim@mail:~$ -bash: syntax error near unexpected token `newline'
    > tim@mail:~$         loop  txqueuelen 1000  (Local Loopback)
    > -bash: syntax error near unexpected token `('
    -bash: syntax error near unexpected token `('
    tim@mail:~$ tim@mail:~$         RX packets 3417140  bytes 2228544225 (2.2 GB)
    -bash: syntax error near unexpected token `('
    tim@mail:~$ -bash: syntax error near unexpected token `('
    > tim@mail:~$         RX errors 0  dropped 0  overruns 0  frame 0
    > RX: command not found
    > tim@mail:~$         TX packets 3417140  bytes 2228544225 (2.2 GB)
    > -bash: syntax error near unexpected token `('
    -bash: syntax error near unexpected token `('
    tim@mail:~$ tim@mail:~$         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    tim@mail:~$: command not found
    tim@mail:~$ TX: command not found
    TX:: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ ERROR: cannot create file run/systemd/network/10-netplan-enp2s0: Failed to create file “/run/systemd/network/10-netplan-enp2s0.network.FRVF50”: Permission denied
    tim@mail:~$: command not found
    tim@mail:~$ ERROR:: command not found
    ERROR::: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ An error occurred: the configuration could not be generated
    tim@mail:~$: command not found
    tim@mail:~$ An: command not found
    An:: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ Reverting.
    tim@mail:~$: command not found
    tim@mail:~$ Reverting.: command not found
    Reverting.:: command not found
    tim@mail:~$ tim@mail:~$ Something really bad happened while reverting config: [Errno 13] Permission denied: '10-netplan-enp2s0.network'
    tim@mail:~$: command not found
    tim@mail:~$ Something: command not found
    Something:: command not found
    tim@mail:~$ tim@mail:~$ You should verify the netplan YAML in /etc/netplan and probably run 'netplan apply' again.
    tim@mail:~$: command not found
    tim@mail:~$ You: command not found
    You:: command not found
    tim@mail:~$ tim@mail:~$ tim@mail:~$ sudo netplan try
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$: command not found
    tim@mail:~$:: command not found
    tim@mail:~$ tim@mail:~$ Warning: Stopping systemd-networkd.service, but it can still be activated by:
    tim@mail:~$: command not found
    tim@mail:~$ Warning:: command not found
    Warning::: command not found
    tim@mail:~$ tim@mail:~$   systemd-networkd.socket
    tim@mail:~$: command not found
    tim@mail:~$ systemd-networkd.socket: command not found
    systemd-networkd.socket:: command not found
    tim@mail:~$ tim@mail:~$ Do you want to keep these settings?
    tim@mail:~$: command not found
    tim@mail:~$ Do: command not found
    Do:: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ Press ENTER before the timeout to accept the new configuration
    tim@mail:~$: command not found
    tim@mail:~$ Press: command not found
    Press:: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ Changes will revert in 114 seconds
    tim@mail:~$: command not found
    tim@mail:~$ Changes: command not found
    Changes:: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ tim@mail:~$ networkctl list
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$: command not found
    tim@mail:~$:: command not found
    tim@mail:~$ tim@mail:~$ IDX LINK             TYPE               OPERATIONAL SETUP
    tim@mail:~$: command not found
    tim@mail:~$ IDX: command not found
    IDX:: command not found
    tim@mail:~$ tim@mail:~$   1 lo               loopback           carrier     unmanaged
    tim@mail:~$: command not found
    tim@mail:~$ 1: command not found
    1:: command not found
    tim@mail:~$ tim@mail:~$   2 enp2s0           ether              routable    configured
    tim@mail:~$: command not found
    tim@mail:~$ 2: command not found
    2:: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ ●        State: routable
    tim@mail:~$: command not found
    tim@mail:~$ ●: command not found
    ●:: command not found
    tim@mail:~$ tim@mail:~$        Address: 70.33.xxx.xxx on enp2s0
    tim@mail:~$: command not found
    tim@mail:~$ Address:: command not found
    Address::: command not found
    tim@mail:~$ tim@mail:~$                 fe80::d63d:7eff:fxx2:7cxx on enp2s0
    tim@mail:~$: command not found
    tim@mail:~$ fe80::d63d:7eff:fxx2:7cxx: command not found
    fe80::d63d:7eff:fxx2:7cxx:: command not found
    tim@mail:~$ tim@mail:~$        Gateway: 70.33.xxx.xxx on enp2s0
    tim@mail:~$: command not found
    tim@mail:~$ Gateway:: command not found
    Gateway::: command not found
    tim@mail:~$ tim@mail:~$            DNS: 70.33.168.193
    tim@mail:~$: command not found
    tim@mail:~$ DNS:: command not found
    DNS::: command not found
    tim@mail:~$ tim@mail:~$                 1.1.1.1
    tim@mail:~$: command not found
    tim@mail:~$ 1.1.1.1: command not found
    1.1.1.1:: command not found
    tim@mail:~$ tim@mail:~$            NTP: 129.6.15.28
    tim@mail:~$: command not found
    tim@mail:~$ NTP:: command not found
    NTP::: command not found
    tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$ tim@mail:~$ resolvectl status
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$: command not found
    tim@mail:~$:: command not found
    tim@mail:~$ tim@mail:~$ resolvectl: command not found
    tim@mail:~$: command not found
    tim@mail:~$ resolvectl:: command not found
    resolvectl::: command not found
    tim@mail:~$ tim@mail:~$ tim@mail:~$
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$: command not found
    tim@mail:~$:: command not found
    tim@mail:~$ tim@mail:~$

    Code:
    tim@mail:~$ systemd-resolve status
    status: resolve call failed: No appropriate name servers or networks for name found
    tim@mail:~$
    Code:
    tim@mail:~$ route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    0.0.0.0         70.33.168.xxx   0.0.0.0         UG    100    0        0 enp2s0
    70.33.168.xxx   0.0.0.0         255.255.255.240 U     0      0        0 enp2s0
    70.33.168.xxx   0.0.0.0         255.255.255.255 UH    100    0        0 enp2s0
    Code:
    tim@mail:~$ ip route
    default via 70.33.168.xxx dev enp2s0 proto dhcp src 70.33.168.xxx metric 100
    70.33.168.xxx/28 dev enp2s0 proto kernel scope link src 70.33.168.xxx
    70.33.168.xxx dev enp2s0 proto dhcp scope link src 70.33.168.xxx metric 100
    For Security reasons I have edited the Public IP address
    Last edited by kustomjs; June 28th, 2021 at 02:33 AM.
    Tim's Computer Repair
    trpcrepair.com

  2. #22
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Having issues on upgrading 18.04 to latest version

    Tim: It's a lot simpler than you think... I just spent 2 hours trace through every onne of you posts. Through all the errors and parsing through them...

    My apologies on asking you for your .yaml file again... I found it in post#4
    Quote Originally Posted by kustomjs View Post
    Code:
    tim@mail:~$ cat /etc/netplan/*.yaml
    # This file is generated from information provided by
    # the datasource.  Changes to it will not persist across an instance.
    # To disable cloud-init's network configuration capabilities, write a file
    # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
    # network: {config: disabled}
    network:
        version: 2
        renderer: networkd
        ethernets:
            enp2s0:
                dhcp4: true
    Along the way I asked you to do this:
    Quote Originally Posted by MAFoElffen View Post
    Then post the reslults of
    Code:
    netplan try
    Later you posted output, but didn't post the associated commands that went with that out... I asked you to go back and edit that... no matters.

    This is is important and is reoccurring throughout you errors...Here was your results of "netplan try":
    QUOTE=kustomjs;14045922]

    Code:
    ERROR: cannot create file run/systemd/network/10-netplan-enp2s0: Failed to create file “/run/systemd/network/10-netplan-enp2s0.network.FRVF50”: Permission denied
    
    An error occurred: the configuration could not be generated
    
    Reverting.
    Something really bad happened while reverting config: [Errno 13] Permission denied: '10-netplan-enp2s0.network'
    You should verify the netplan YAML in /etc/netplan and probably run 'netplan apply' again.
    tim@mail:~$ sudo netplan try
    Warning: Stopping systemd-networkd.service, but it can still be activated by:
      systemd-networkd.socket
    Do you want to keep these settings?
    
    Press ENTER before the timeout to accept the new configuration
    
    Changes will revert in 114 seconds
    [/quote]
    Which say's your NetPlan network configuration is not working...

    I parsed through those errors... Look what I find besides the above error:
    Code:
    mafoelffen@Opti-Ubuntu-Main:~$ sudo find ~/Test/ -type f -name "*.log" -print0 | xargs -I {} -0 grep -i ": command not found" "{}"
    > RX: command not found
    TX: command not found
    ERROR:: command not found
    An: command not found
    Reverting.: command not found
    Something: command not found
    You: command not found
    tim@mail:~$: command not found
    Warning:: command not found
    systemd-networkd.socket: command not found
    Do: command not found
    Press: command not found
    Changes: command not found
    tim@mail:~$: command not found
    IDX: command not found
    1: command not found
    2: command not found
    ●: command not found
    Address:: command not found
    fe80::d63d:7eff:fxx2:7cxx: command not found
    Gateway:: command not found
    DNS:: command not found
    1.1.1.1: command not found
    NTP:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ resolvectl: command not found
    resolvectl:: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ TX: command not found
    TX:: command not found
    tim@mail:~$: command not found
    -bash:: command not found
    tim@mail:~$: command not found
    Command: command not found
    > RX: command not found
    tim@mail:~$: command not found
    tim@mail:~$ TX: command not found
    TX:: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ ERROR:: command not found
    ERROR::: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ An: command not found
    An:: command not found
    ## I stopped highlighting here... I think you get the idea. ##
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ Reverting.: command not found
    Reverting.:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ Something: command not found
    Something:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ You: command not found
    You:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$: command not found
    tim@mail:~$:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ Warning:: command not found
    Warning::: command not found
    tim@mail:~$: command not found
    tim@mail:~$ systemd-networkd.socket: command not found
    systemd-networkd.socket:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ Do: command not found
    Do:: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ Press: command not found
    Press:: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ Changes: command not found
    Changes:: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$: command not found
    tim@mail:~$:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ IDX: command not found
    IDX:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ 1: command not found
    1:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ 2: command not found
    2:: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ ●: command not found
    ●:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ Address:: command not found
    Address::: command not found
    tim@mail:~$: command not found
    tim@mail:~$ fe80::d63d:7eff:fxx2:7cxx: command not found
    fe80::d63d:7eff:fxx2:7cxx:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ Gateway:: command not found
    Gateway::: command not found
    tim@mail:~$: command not found
    tim@mail:~$ DNS:: command not found
    DNS::: command not found
    tim@mail:~$: command not found
    tim@mail:~$ 1.1.1.1: command not found
    1.1.1.1:: command not found
    tim@mail:~$: command not found
    tim@mail:~$ NTP:: command not found
    NTP::: command not found
    tim@mail:~$: command not found
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$: command not found
    tim@mail:~$:: command not found
    tim@mail:~$ tim@mail:~$ resolvectl: command not found
    tim@mail:~$: command not found
    tim@mail:~$ resolvectl:: command not found
    resolvectl::: command not found
    tim@mail:~$: command not found
    tim@mail:~$ tim@mail:~$: command not found
    tim@mail:~$:: command not found
    mafoelffen@Opti-Ubuntu-Main:~$
    Which strangely looks like some misdirect of stdout as stdin... Either a piping, direction of output, or ??? But that has nothing to do with your networking. That's just another problem.

    I see nothing wrong what your routing table. It goes to your local DNS, which goes to the OpenDNS at CloudFlare.


    ### ### ### ### ### ### ###
    Some things about your NetPlan file:
    RE: Canonical NetPlan Reference
    Change your's to this:
    Code:
    # This file is generated from information provided by
    # the datasource.  Changes to it will not persist across an instance.
    # To disable cloud-init's network configuration capabilities, write a file
    # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
    # network: {config: disabled}
    network:
        version: 2
        renderer: networkd 
        ethernets:
            enp2s0:
                dhcp4: true
    Last edited by MAFoElffen; June 29th, 2021 at 08:48 PM. Reason: Correction

    Concurrent coexistance of Windows, Linux and UNIX...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    UbuntuForums system-info Script

  3. #23
    Join Date
    Nov 2007
    Location
    Coldwater, OH
    Beans
    534
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: Having issues on upgrading 18.04 to latest version

    I sent you a other PM
    Tim's Computer Repair
    trpcrepair.com

  4. #24
    Join Date
    Sep 2011
    Location
    Behind you!
    Beans
    1,533
    Distro
    Ubuntu 20.04 Focal Fossa

    Re: Having issues on upgrading 18.04 to latest version

    networkd "is" my renderer in all of my 20.04 config files.

    Code:
    # This file describes the network interfaces available on your system
    # For more information, see netplan(5).
    network:
      version: 2
      renderer: networkd
      ethernets:
        ens160:
          dhcp4: false
          dhcp6: false
          addresses: [192.168.1.42/24]
          gateway4: 192.168.1.1
          nameservers:
            addresses: [192.168.1.1,192.168.1.2,1.1.1.1,8.8.8.8]
    I suspect the bungled code in post #21 was just the OP copying the output, then accidentally pasting it in PuTTY to get all those "command not found" messages and then for some reason, copied that and pasted it into the thread here.

    LHammonds
    Last edited by LHammonds; June 29th, 2021 at 03:57 PM.

  5. #25
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Having issues on upgrading 18.04 to latest version

    @LHammands

    Yes. You are right. The problem is somewhere in NetPlan and systemd.networkd on that system. It could be as simple as an extraneous character in a file or an old/extra file in the build path. I think the smart way to go about it is to run a trace in the "netplan generate" and "netplan try" processes to narrow done where the problem lies. That is not something you would post the results of in a public forum, for a public facing host.

    The problem with NetPlan, yaml, and the .yaml file, is that the .yaml config file is very picky about formatting, idents, and whitespace!!! An extra space or a tab in it and it will cause the generate to "fail." And just using a --debug switch with the netplan utility won't display those errors. It reminds me of Python language conventions.


    EDIT: @LHammonds... Thank you for triggering my memory on that! His fix could be as easy as recreating his .yaml file and trying it. (just in case there is an extraneous character or formatting error in that file...)
    Last edited by MAFoElffen; June 29th, 2021 at 08:52 PM.

    Concurrent coexistance of Windows, Linux and UNIX...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    UbuntuForums system-info Script

  6. #26
    Join Date
    Mar 2007
    Location
    Denver, CO
    Beans
    7,913
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Having issues on upgrading 18.04 to latest version

    @MAFoElffen

    Slightly off topic -- I never understood why Ubuntu has netplan in the first place when it relies on systemd-networkd?? On Arch for example I just configure systemd-networkd directly without any netplan intermediate. The syntax is a little different, but it's no more or less difficult. I'm a big fan of yaml config files (like used in docker compose), however I've setup vim to provide for the correct spacing since I'm aware one extra space can screw things up. With systemd-networkd, the config files don't depend on yaml syntax and seem less prone to errors. I guess some things I just don't understand.

Page 3 of 3 FirstFirst 123

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •