iptables host/network not found error

I am testing the 5.8-rc4 kernel, and /tmp/bootsysinit.log, which is the log of stdout and stderr from /etc/rc.d/rc.sysinit, reports this multiple times:

iptables v1.8.2 (legacy): host/network `' not found

This error is from /etc/init.d/rc.firewall, which is the firewall generated by "firewall_ng", which is "Alien Bob's Easy Firewall Generator" modified for Puppy by 01micko.

There is a "Puppy Rules" section in 'rc.firewall' that is responsible for these error messages.

Did not have these error messages before, it is new with the 5.8-rc4 kernel. Here is an example of one line that produces the error:

/usr/sbin/iptables -A udp_inbound -p UDP -s /8 --destination-port 137 -j ACCEPT
iptables v1.8.2 (legacy): host/network `' not found

After a quick search online, it seems the " /8 " syntax is wrong. It is supposed to be prefixed with an IP address. OK, so I replaced all occurences of " /8 " with " 127.0.0.1/8 ", and no longer get error messages.

However, I don't know if what I have done is correct. Does the " /8 " imply that it is 127.0.0.1 host? Why did it work before?

The Puppy Forum has been down all day, so cannot pose these questions there. Indeed, the answer may already be somewhere on that forum. So, if there is anyone knowledgeable with iptables and firewall rules, would you mind posting via the "Contact me" button at top of this page?

If you want to see the firewall_ng generator, it is in this tarball, at easy-code/rootfs-skeleton/usr/sbin/firewall_ng:

http://distro.ibiblio.org/easyos/project/woof/woof-project-20200622.tar.gz 

Tags: easy

The mysterious missing iwl-debug-yoyo.bin firmware

As reported a couple of days ago, I am testing kernel 5.8-rc4:

https://bkhome.org/news/202007/kernel-58-rc4-compiled.html

Running 'dmesg' reports that failed to load firmware 'iwl-debug-yoyo.bin':

iwlwifi 0000:04:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2

After much searching, I failed to find it, nor any explanation about what it is for, or even whether it is really needed. Well, it isn't needed, as my wifi works. Wolfram has been through the same fruitless search, and has proposed a patch to remove that failure message:

https://lkml.org/lkml/2020/6/25/625

if the issue still exists when we get to the 5.8.1 kernel, and if that firmware still remains elusive, then I will probably apply that patch. 

Tags: easy

PETget Package Manager supports zstd

The PPM was originally "Puppy Package Manager", but I have named it "PETget" in EasyOS, but you can still call it the PPM.

Arch Linux packages are now using zstd compression, and are named with ".pkg.tar.zst" extension.

I have added support for .pkg.tar.zst and .tar.zst to PETget. The modified scripts are installpkg.sh, petget and verifypkg.sh, in path /usr/local/petget.

I posted yesterday about mime-handling and Xarchive support added for zstd:

https://bkhome.org/news/202007/mime-handling-for-zstd.html 

Tags: easy

Mime handling for zstd

EasyOS has the zstd utility, however lacks proper mime handling. Like, assigning a mime-type, handling when click on a .zst or .zstd file, support in Xarchive.

I have run out of steam to explain all the changes, just take it as done.

Zstd mime type:

https://www.iana.org/assignments/media-types/application/zstd

Thanks to peebee for zstd support in Xarchive:

http://www.murga-linux.com/puppy/viewtopic.php?p=1048178#1048178

...I only used the Xarchive wrapper, usr/lib/x86_64-linux-gnu/xarchive/wrappers/tar-wrap.sh, from peebee's tarball. All of the mime-handling I implemented independently.

Note, /usr/local/bin/pkghandler.sh has been expanded to handle all tarball types, that is, .tar.gz, .tgz, .tar.xz, .txz, .tar.bz2, .tbz2, .tar.zstd, .tar.zst. A left mouse click on any of these file types will run 'pkghandler', which tests whether the tarball is a binary package (is not a source package) and if so, asks if want to install it or open it in Xarchive. If not a binary package, immediately opens in Xarchive.   

Tags: easy

Kernel 5.8-rc4 compiled

I am interested in the changes to procfs in the 5.8 kernel, to enhance container security. The plan is that the next release of EasyOS will be after the 5.8.1 kernel is released. For now, getting started...

I started with the '.config' file for the 5.4.47 kernel, as used in EasyOS 2.3.2. Enabled some more drivers, in addition, made some changes, here are the highlights:

General setup
  [*] Boot config support CONFIG_BOOT_CONFIG Documentation/admin-guide/bootconfig.rst 
Processor type and features
  [*] IOPERM and IOPL emulation CONFIG_X86_IOPL_IOPERM
Networking support --> Bluetooth subsystem support
  [*] Enable Microsoft extensions CONFIG_BT_MSFTEXT
Networking support
  [*] Netlink interface for ethtool CONFIG_ETHTOOL_NETLINK
Device Drivers --> PCI support
  [ ] Support for PCI hotplug CONFIG_HOTPLUG_PCI REMOVED 
Device Drivers --> Generic Driver Options --> Firmware loader
  [*] Enable firmware caching during suspend CONFIG_FW_CACHE
Device Drivers
  < > Memory Technology Device (MTD) support CONFIG_MTD REMOVED  
Device Drivers --> Block devices
  (65536) Default RAM disk size (kbytes) CONFIG_BLK_DEV_RAM_SIZE Increased from 32768 
Device Drivers --> Pin controllers
  <*> Intel Ice Lake PCH pinctrl and GPOI driver CONFIG_PINCTRL_ICELAKE
  <*> Intel Jasper Lake PCH pinctrl and GPIO driver CONFIG_PINCTRL_JASPERLAKE
  <*> Intel Tiger Lake pinctrl and GPIO driver CONFIG_PINCTRL_TIGERLAKE
Device Drivers --> Hardware monitoring support
  <m> Hard disk drives with temperature sensors CONFIG_SENSORS_DRIVETEMP

Some of those, I don't know anything about, but look interesting. "Boot config support" for example.

Also went on a big hunt for firmware for the 5.8 kernel, and have created a new PET (59MB):

http://distro.ibiblio.org/easyos/noarch/packages/pet/pet_packages-noarch/firmware_linux_all_k5p8-5.8.0-20200711.pet

Using the 5.8-rc4 kernel right now. Had to fix the aufs patch, and getting an iptables error at bootup. Other than that, seems OK. 

Tags: easy

Android phone data transfer fixed

Some time ago, someone reported being unable to connect to their Android phone, running EasyOS. The desktop has a "share" icon, that is supposed to make it easy to setup file transfer and printing over a network, and file transfer with a Android phone connected via USB cable.

There was also a report of a problem with Samba, I think, so checking that is on the to-do list ...um, perhaps that report was for EasyPup.

Anyway, for now have tackled Android connectivity. I ran "easyshare" in a terminal, and immediately discovered the problem: the 'adb' utility is missing.

Debian developers have been changing package names again. The DEB package 'android-tools-adb' used to have the 'adb' utility, but no longer. Now we need the 'adb' DEB plus some dependencies.

Having done that, connection with my LG Nexus 5 works.

I added an extra bit of information in the GUI. When an ADB connection is attempted from a device that the phone has not connected to before, it pops up a confirmation dialog on the phone screen. If you fail to acknowledge that popup, EasyShare reports nothing, that is, no phone, found. I have changed this so that EasyShare reports the phone is found but you haven't authorized the connection on the phone screen.

Another bug bites the dust! 

Tags: easy

EasyDD color fix in terminal

I received an email from Bob, testing EasyDD in Ubuntu. he reports it works great, but when writing to USB-stick, the terminal window has bright-yellow background and light-grey text, making the text very difficult to read.

EasyDD searches for a suitable terminal emulator utility in the host OS, in order of:

1. VTE terminal builtin to gtkdialog
2. rxvt
3. urxvt
4. xterm
5. gnome-terminal
   

For items 1 and 5, the default background and foreground colours are used, that is, no attempt is made to change them in the EasyDD script.

For items 2, 3 and 4, the terminal is executed with the "-bg '#ffff80'" commandline option, which is light-yellow background. The default text colour is used, which in EasyOS is black.

However, in other distros the default text may be some other colour, such as light-grey in Bob's case.

I have now explicitly set the foreground colour to black, with the "-fg '#000000'" commandline option.

The latest EasyDD is here:

https://bkhome.org/files/easydd.gz

If you are new to EasyDD, read about it here:

https://bkhome.org/linux/easydd-write-image-file-to-drive.html

Just an extra note, for gnome-terminal, setting the background and foreground colours on-the-fly, on the commandline execution, isn't possible. Instead, have to jump through hoops:

https://unix.stackexchange.com/questions/133914/set-gnome-terminal-background-text-color-from-bash-script

...yikes! Haven't bothered, just using the defaults.    

Tags: easy

Install page updated for fixed rEFInd

Refer to the previous blog post:

https://bkhome.org/news/202007/refind-patch-for-ext4-fscrypt.html

As ext4 driver is now fixed, I have updated this tutorial page:

https://easyos.org/install/install-to-pc-with-existing-refind-boot-manager.html

There are other pages that need to be updated, will get to those sometime. 

Tags: easy