Hello:

I've given that some thought.
The weakest link here is the Class 2 2.0Gb SD Card + SD Card reader.
disks clocks it at an average read rate of 10.5MB/s, average write speed is probably slower.
By comparison, the SAS drive from which the *.iso file was read is clocked at an average read rate of 105.2 MB/s.
ie: 10X higher using the same size (10MB) sample.

No need.
Patch the script, test it and let me know the additions.
ie: line number and syntax so I can just add them verbatim to the original.

Best,

A.

Edit:
Posts crossed while I was making espresso.
I'll run the tests and post as soon as I get it done, later tonight or early tomorrow.

.

Hello:

Glad I could be of help.

Box is a ca. 2009 Sun Microsystems Ultra 24 WS with an Intel Q9550 / 8Gb RAM - Linux 6.1.0-37-amd64 x86_64
Swap file in RAM.

$ sudo swapon -s
Filename				Type		Size		Used		Priority
/dev/sdb3                               partition	2749436		0		-2
/dev/zram0                              partition	6291452		0		100
$ 

The memory is a standard Sandisk SD (Class 2) 2.0Gb  Card on a generic USB 2.0 SD /MicroSD Card reader plugged into a USB 3.0 slot.

The difference in read/access speeds between a Class 2 SD card, USB 2.0 reader in a USB 3.0 slot and a swapfile in RAM may (?) account for whatever happens timing wise. I'd say that, in this specific case, you don't need fast.
ie: accurate and reliable would be the thing to aim for.

Best,

A.

Hello:

Indeed it was.  8^°
ie: pebkac

Fixed that.

$ cat /etc/default/su
# restore the old 'su' behaviour
# no 'su-' | just use 'su' as before
# see https://files.devuan.org/devuan_beowulf/Release_notes.txt
# ALWAYS_SET_PATH yes
$

Now, with su and sudo:

[root@devuan isos]# sudo ./fatstick.sh
/dev/sdg: 5 bytes were erased at offset 0x00008001 (iso9660): 43 44 30 30 31
Checking that no-one is using this disk right now ... OK

Disk /dev/sdg: 1.89 GiB, 2032664576 bytes, 3970048 sectors
Disk model: Storage Device  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x23927a24

Old situation:

Device     Boot Start     End Sectors  Size Id Type
/dev/sdg1  *       64 2333951 2333888  1.1G 17 Hidden HPFS/NTFS

/dev/sdg2: Created a new partition 2 of type 'W95 FAT32 (LBA)' and of size 798.9 MiB.
Partition #2 contains a vfat signature.
/dev/sdg3: Done.

New situation:
Disklabel type: dos
Disk identifier: 0x23927a24

Device     Boot   Start     End Sectors   Size Id Type
/dev/sdg1  *         64 2333951 2333888   1.1G 17 Hidden HPFS/NTFS
/dev/sdg2       2333952 3970047 1636096 798.9M  c W95 FAT32 (LBA)

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
[root@devuan isos]# 

I think it works properly.
ie: as advertised -> no small feat. 

Just one thing ...
At some point towards the end of the job, I think (?) the stick is unmounted and then remounted.
Not sure of that.

The first time I tried the script it ended with a a pop-up with an error and the second partition was not formatted. (unknown)
I then ran the script again and it ended with a formatted FAT32 partition, no errors.

To check, I ran the whole process again: blanked the SD card, ran the format / image writing applications and then the script.

Although the same thing happened ie: the pop-up with an error for writing the second partition, on checking I saw that the second partiton had been formatted.

You may want to test and see if a short pause somewhere between the creation of the second partition and formatting it to FAT32 would avoid that.

Let me know if you need anything else.

Best,

A.

Hello:

No problem, seems you are quite busy.

Done.
Used a 2.0GB SD Card on a generic USB SD/Micro SD Card reader and wrote a Chimaera i386 *.iso.
No problems, was abe to boot my 1000HE both from SD Card in slot and SD Card in reader.

disks and gparted reported as expected.

Labelled the script 'fatstick', made it executable.
Ran is as root, I have specific permissions for sudo and too lazy to add another entry in sudoers.d.

$ sudo ./fatstick.sh
Sorry, user is not allowed to execute './fatstick.sh' as root on localhost.
$ 

But I get an error/warning:

# ./fatstick.sh
(yad:2866): Gtk-WARNING **: 09:21:27.813: cannot open display: 
# 

Something in the script?

Best,

A.

Hello:

I expect that it would be the same with my 1000HE which is ca. 2009.

No idea, but I expect that it could be possible.

From what little I understand, it seems that the task would involve compiling a kernel from source but including only what you need for your netbook.
ie: tailored for your target hardware and compiled on it.

There's also the question of who is going to do it and then maintain it.
For starters, is there a large enough user base?
There used to be specific eee kernels / distributions but as the differnet models were mothballed, they lost all traction.

Interesting side note:
Asus does not have the eee series in theri tech support databases.

I have recently been able to get a very important boost for my netbook by enabling zram and generating a /dev/zram0 swap file.

The Asus eee series is not alone in this.
Absolutely every discontinued and perfectly working netbook / notebook is in the same situation.

All victims of the decades old WinTel consortium. (see what is going on with Win 11 these days)

Best,

A.

Hello:

So ...
How is that a surprise?
ie: to you or anyone else

+1

Best,

A.

Hello:

@greenjeans

Likewise.
(Shit, man ... made me blush.)

@golinux

I'm quite aware of the implications re: Devuan being Debian without systemd.

[OT]
But I don't think that is a long lasting status quo.
The weave that keeps it in place is permanently being pecked at by the usual suspects.
It will eventually come loose. 
When it does (no, no if) Devuan+all derivatives will need a fall back position.
[/OT]

That said, a basic Devuan installation (like a netinstall), would (by definition?) not have a DE or a WM for that matter.
So no radical change there.
Just a meta-package / script or whatever.
It would be downloaded separately and applied post-installation.

Seems like it would be like that but for a Devuan netinstall.
ie: systemd less.

I really don't know how much of that script would have to be adjusted to work on a Devuan netinstall.

Thanks to all for your input.

Best,

A.

Hello:

I think it fits Devuan just right.
In the true Linux spirit.

That would be great.

You know better than I, but I was not referring to an out of the box thing, ie: incorporated in the *.iso.

What I had read about (if I undestood it correctly) was a script you could download and run on an basic Debian installation.
ie: one without a DE/WM, after the installation was finished and everything else was running as expected.

Found the post by HoaS here.
Have a look and tell us what you think.
Maybe a different thread?

Edit:
https://archive.org/details/sharpbang-b … 386.hybrid
https://archiveos.org/sharpbang/

Best,

A.

Hello:

So I have discovered, thanks for the heads-up.

I had a start-up entry in xfce+Session and Startup+Application Autostart and unchecked it.
Ran through all my routines and they worked perfectly well, so I just uninstalled it.
Worst case, I'd have to re-install it.

I would not be caught dead doing that. 8^° 

That I don't have.

The only gnome thing I have is the gnome-disk-utility which has given me no problems.
I have found it quite useful but it comes with a (built-in?) gnome-disk-utility notification plugin which I never set to startup.
You will find it in /usr/libxec/gsd-disk-utilty-notify.

That's that, so I'll mark this one solved.

Best,

A.

Hello:

That's what I think, but the fact that they are cached makes me doubt.
ie: why are they not cleared on reboot?

Good to know.

Why am I not surprised?

This is what I have installed in terms of 'keyrings':

$ apt list | grep installed | grep keyring
debian-archive-keyring/stable,stable,now 2023.3+deb12u2 all [installed]
devuan-keyring/stable,stable,now 2023.05.28 all [installed]
gnome-keyring/stable,now 42.1-1+b2 amd64 [installed]
python3-keyring/stable,stable,now 23.9.3-2 all [installed,automatic]
python3-keyrings.alt/stable,stable,now 4.2.0-1 all [installed,automatic]
$ 

Q: just how many keyrings do I need for my desktop?

Best,

A.

Hello:

Right ...  8^°
Sorry, my bad.

Yes, update-rc.d uses the INIT INFO fields and is mandatory when adding a script to /etc/init.d.

Best,

A.

Hello:

@Raulcla
@Kristof12

The site's search function is quite useful.
You may want to consider trying it out.

That said, have a look at these two threads:
https://dev1galaxy.org/viewtopic.php?id=2918
https://dev1galaxy.org/viewtopic.php?id=2449

TL;DR
Devuan is a systemd-less distribution.
snapd requires systemd -> because of this, snapd is a banned package.
Hence the lack of snapd or anything snap related in the Devuan repository.

Best,

A.