Hello:

After trying the two or three out there, I cannot but emphatically recommend SLiM to one and all.
It is not systemd compatible which is not an issue for us but probably the reason nobody is taking care of it these days.

A real pity.
With so many capable developers out there, going after the newest shiniest whatever instead of supporting/maintaining good software.  :^ *

Cheers,

A.

Hello:

I see.

Yes, my use of su is rather limited to the basics, so I really have quite a bit of reading to do.
That's what you get from arriving to Linuxland late in life.  8^7

Thanks for your input.

Cheers,

A.

Hello:

I did not have /etc/default/su and generating the file and adding ALWAYS SET PATH  yes did not work.

What did work was ...

root@devuan2:/home/groucho# export PATH=$PATH:~/usr/local/sbin

root@devuan2:/home/groucho# $echo $PATH
bash: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/usr/local/sbin: No such file or directory
root@devuan2:/home/groucho# 

Got it from https://wiki.debian.org/EnvironmentVariables:

--- snip ---
... after doing su, your PATH may not contain directories like /sbin, and many system administration commands will fail. There are several workarounds:
...

Put the system administration directories (/sbin, /usr/sbin, /usr/local/sbin) in your regular account's PATH (see EnvironmentVariables for help with this).

--- snip ---

BTW: whatever the reason for the change in how su works, I hope it is a good/justified one and not another one of Poettering's wet dreams. It is a PITA.

A.

Hello:

Windows is not Linux.  8-⁷
The Startech webpage for this card does not mention Linux support.

That said ...

The card uses the Texas Instruments Texas Intruments -TSB82AA2 chipset and Startech's vendorID is 14b0.

Looking up TSB82AA2+14b0 on the linux-hardware.org website, we get this.

----

Results for 'Texas Instruments', 'TSB82AA2', id='14B0-*', type='firewire controller', bus='PCI' (0)
No data

----

Given that it is a card you can probably replace for less than US$25, I suggest that you get one that has Linux support.
   
See this one with a different TI chipset.

There are probably a few others, you'll have to shop around.

Cheers,

A.

Hello:

I see ...

This is just with Pegasus Mail or is it ...

Just read about it and it is probably common to all email clients or text to binary data conversions.
Like you say, base64 inflates the size of the data, but much less than decimal or hexadecimal:

https://stackoverflow.com/a/201536

Still, 15.5Mib x 1.3 = 20.15MiB, not 30.5MiB ...

What could be causing the other 10.35MiB worth of bloat?

Could it be that I am not sending a text file but *.pdf file, with all its complexities? ie: symbols, compression, etc. and the file is 15.5Mib 'on-disk'.

Thanks for your input.

A.

Hello:

Could you post your surces list?

~$ cat /etc/apt/sources.list

I run on an updated Devuan ascii 2.0

~$ uname -a
Linux devuan 4.9.0-13-amd64 #1 SMP Debian 4.9.228-1 (2020-07-05) x86_64 GNU/Linux
~$ 

# apt-get update && apt-get upgrade && apt-get install -f
Hit:1 http://deb.devuan.org/merged ascii InRelease
Hit:2 http://deb.devuan.org/merged ascii-security InRelease
Hit:3 http://deb.devuan.org/merged ascii-updates InRelease
Hit:4 http://deb.devuan.org/devuan ascii-proposed InRelease
Hit:5 http://deb.devuan.org/merged ascii-backports InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# 

Here's my sources.list, please disregard the comments:

~$ cat /etc/apt/sources.list

deb http://deb.devuan.org/merged/ ascii main 
deb http://deb.devuan.org/merged/ ascii-security main 
deb http://deb.devuan.org/merged/ ascii-updates main 

# needed x virtualbox backport - enable to update package
deb http://deb.devuan.org/devuan/ ascii-proposed main contrib non-free 
deb http://deb.devuan.org/merged/ ascii-backports non-free contrib main 

# needed x nvidia non-free drivers installation
deb http://deb.devuan.org/merged/ ascii contrib 
deb http://deb.devuan.org/merged/ ascii non-free 

# virtual box repository 
# deb http://download.virtualbox.org/virtualbox/debian/ stretch non-free contrib  

With those sources, if I try to install vlc, I get this:

# apt-get install vlc
Reading package lists... Done
Building dependency tree       
Reading state information... Done
vlc is already the newest version (3.0.11-0+deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# 

Same with the plugin:

# apt-get install vlc-plugin-video-output
Reading package lists... Done
Building dependency tree       
Reading state information... Done
vlc-plugin-video-output is already the newest version (3.0.11-0+deb9u1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# 

Check your sources.list, maybe there's something there that should not be or maybe there's something missing.

Cheers,

A.

Hello:

Is there a *.deb package available for ASCII?
Can't seem to find it.

TIA,

A.

Hello:

Right ...

But why has this happened with my VM Devuan ascii ...

groucho@devuan:~$ uname -a
Linux devuan 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1+deb9u1 (2020-06-07) x86_64 GNU/Linux
groucho@devuan:~$ 

... and not with my everyday rig:

groucho@devuan:~$ uname -a
Linux devuan 4.9.0-12-amd64 #1 SMP Debian 4.9.210-1+deb9u1 (2020-06-07) x86_64 GNU/Linux
groucho@devuan:~$ 

ie: what difference is there between them that causes those packages to be kept back? <- which was the reason for my OP.

There's more ... 

EDIT:
It seems that between running apt-get update and apt-get upgrade on my rig and then doing the same on the VM used for the USB plug, the repos were updated.

So it looked like two different update/upgrade processes were taking place.

ie: one machine did it on the repos just before they were updated and the other just after they were updated.

Just what are the chances?  8^D

Thanks a lot for your input.

Cheers,

A.

Hello:

+1

When (in a hurry) I purchased a M2020W, the only thing that worked almost right away (Devuan 2.0 ascii) was CUPS.
No issues since.

Cheers,

A.

Hello:

So the rig was working perfectly well until "adding printer driver for a Brother laser printer"?
If so, maybe it is just the old and well known cause -> effect mechanism doing it's thing here.

Q: Just where did the driver come from?

1.
Scan through dmesg for errors and see what /var/log/Xorg.0.log has to say about X not starting.

2.
Try seeing if there's something missing, as root do:

# apt-get install -f

Please post back results.

Cheers,

A.

Hello:

From where I stand ie: not a coder or developer, just a 65+ advanced (?) user, what you say makes a lot of sense.

But I also believe that it makes sense to take into account that for Devuan, which has a hard time as things stand, things won't get easier if it has no access to or ignores SBC hardware such as RPis of which over 35 million have been sold.

These inexpensive SBP are the entry point to IT for a great many people who maybe cannot afford something else, just want to play and see what it is like or just need an inexpensive solution to a small and simple problem.

And if you leave it all to Raspbian, you will have lost a lot of potential users many of which may eventually become IT staff or pros ie: just the people Devuan needs to survive in the future.

I'm afraid that spawning dozens of derivatives will not be enough.

The Devuan project is not just a distribution, it also represents a core philosophy (Unix) or an ideology if you will.
Exactly the opposite of what mainstream MS software represents today. 

It urgently needs to develop a strategy to occupy the RPi field or get permanently pushed out of it.

Just another point of view and as always, YMMV.

Cheers,

A.