Setup for ipv4

1. Enable forwarding for the kernel:

   # sysctl net.ipv4.ip_forward=1

2. Add a masquerading rule to the kernel's networking:

   # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

3. Set up ifupdown configuration for eth1 using dnsmasq for DHCP.
    

   1. This involves the initial step of disabling its default deployment that you get when installing it, and then just use it for downlink DHCP service. Something like the folllowing:

      # sed 's/ENABLED=1/ENABLED=0/' -i /etc/dnsmasq/default
      # update-rc.d dnsmasq stop
      # update-rc.d dnsmasq disable

   2. Write a file /etc/network/interfaces.d/downlink.conf with the following, where you replace $DNSHOST with the ip address of your DNS server:

      iface eth1 inet static
      address 192.168.200.1/24
          up /usr/sbin/dnsmasq -i eth1 -a 192.168.200.1 -I lo -I wlan0 -I eth0 \
             -p 0 -K -D -N -b --dhcp-sequential-ip \
             --dhcp-option=3,192.168.200.1 \
             --dhcp-option=6,$DNSHOST \
             -F 192.168.200.2,192.168.200.254,255.255.255.0,192.168.200.255 \
             --dhcp-hostsfile=/var/run/eth1.dhcphosts
          down pkill -f 'dnsmasq -i eth1'

       

4. Make sure your /etc/network/interfaces includes that configuration with e.g. a line:

   source /etc/network/interfaces.d/downlink.conf

   (or with the wildcard statement source /etc/network/interfaces.d/* that is a debian default)

5. Bring up eth1 with that configuration

   # ifup eth1

   This will also start dnsmasq for serving IP addresses via DHCP on eth1, and it will also store the allocations in the file /var/run/eth1.dhcphosts. dnsmasq is killed when eth1 is deconfigured with ifdown or ifdown --force.

I think that would be all, but I do forget things now and then.

@Élisabeth it appears you are using "Expert install" method and are skipping the "load components" step. (Otherwise you would have an ext4 formatting option).

May advice on that would be: Don't.

The plain "install" method works fine for the overwhelming majority of cases and it's only if you really insist on some special peculiarity during the installation procedure that you would use "Expert install". I know that some people feel good about running an "Expert install" even though their need for that is nil, but if you do, you will need to explicitly take all the steps that are needed (which presupposes knowing which they are).

Obviously I might be wrong in my guesswork and in that case you should just ignore me.

No, according to the log there is a serial link set up (over USB) on /dev/ttyUSB0, so the next is to point the software to that.

First, of course, you need to make sure that the software (user) has permission to read and write /dev/ttyUSB0.
The "professional" way for that would be to make sure the user is in the special user group for operating that device, while the "hobbyist" approach is to simply chmod a+rw /dev/ttyUSB0 and let any user (on that computer) do anything to it.

Hmm. I'm not sure how then to verify.
Maybe, after doing dd, eject the USB and put it back in, while still in windows.
It should then contain two partitions; the first of some unknown format (format zero) and the second a FAT12 partition. If you mount that, it should have a folder named EFI.

Possibly you can use the diskpart command, then select the USB disk and use the sub command list partition.
https://docs.microsoft.com/en-us/window … s/diskpart

sorry about editing your post.. must be tired...

Ok. so AnyBurn is no good, then. Possibly dd-windows? but you must make sure to select The Whole usb stick and not any of its partitions.. except that possibly dd-windows uses the name "partition0" for the whole disk (again I've picked that idea from my web searching)

@Élisabeth, the ISO file is supposed to be put onto a USB memory stick to reside from the physical block 0 and up on the USB. Copying onto a partition is not the right way.

To achieve that on windows seems unduly complicated but it should be possible, and in particular I believe dd-windows may be used for it. The important point is that the USB becomes an exact copy of the ISO from its block 0 up to whatever size the ISO is, and then the USB stick can have whatever on the blocks after that. (Somewhere I saw the suggestion that "the disk as a whole" is Partition0 with dd-windows)

The first partition on a disk starts some few blocks in and the first few blocks contain the partition table. The ISO file starts at block 0 and includes a partition table for its partition layout, which includes an EFI partition and a CDROM partition. All that must be put onto the USB memory stick from its block 0.

Note that when you "format the USB as FAT32" you actually create a single first partition on that USB, and then copy&paste just copies the ISO file to be a file on that partition. Doing that is not the right way. Again, just to have it repeated three times: you'll need to copy the ISO onto the USB stick as a whole to become the exact memory image of the USB stick from block 0 and up.

Ralph.

VBOX doesn't see the EFI partition of the devuan iso?

My web search lead to
https://www.cocosenor.com/articles/comp … aptop.html
where at least the first option seems quite safe to try.

EDIT: duly edited. Thanks @Camtaf.

"Use the source, Luke"

Yes, one could say, without imparting disrespect on any particular developers, that sometimes "fondness of gilding" strays from "diligent QA standard"... luckily it's scripts and not binaries.

Thanks, and there's now a new setup for forum translations, via a git project https://git.devuan.org/devuan/forum-lang

To make a new or existing language:

(*) It is feasible to clone into a personal workspace elsewhere than the git store as long as that workspace later is available to service the eventual pull request. But it's significantly less effort for us to merge it if you rather use the fork button on the web interface and make it a personal project on Devuan's git store.

(**) It is of course important to leave everything other than the phrase part as is.

(***) Again, it's easiest for us if you use the pull request button on web interface for submitting the pull request.

Thanks.

Your @Jackoline account was invalidated on your own request. Welcome back.

The note above was for the desktop-live installer that you find at the path variation devuan_chimaera/desktop-live/ and then the file name pattern is devuan_chimaera_4.0.beta-2021-08-27_xxxxxx.iso.

The devuan_chimaera/installer-iso/ collection will find themselves updated into isos of the pattern devuan_chimaera_4.0.beta-20210830_xxxxxx.iso, with and for the desktop-base improvement, at some near future.