You are not logged in.
James1138 wrote:Here are drivers to help with USB Tethering - [redacted]
What are you trying to pull? Is that pure malware or are you just advertising for your shitty company?
@all: *do not* follow the installation instructions, the .deb packages contain opaque binaries that do god-only-knows-what and the "configuration files" are complete nonsense.
Tethering does not require drivers.
Not that this means anything but easytether is in the AUR ??
https://aur.archlinux.org/packages/easytether-bin/
But you are right, no android phone should need 3rd party software to tether.
It might not be as bad as you make it out to be. If firefox is anything to go by in regards to csd then the customization of compact toolbars and modes might be worthwhile. There will be a period of ugliness though i doubt xfce would want to be a clone of gnome, would be very unoriginal.
wicd is fairly straightforward, look in preferences and all the configs are there for wired and wireless.
devuan uses the old interface names so wired should be "usb0" for any tethered smartphone.
plenty of tutorials on the internet "enable usb debugging on smartphone"....
commands to get your tethered link info would be something like.
ip link
Are you using a network manager? Is your phone set to usb debugging?
whether you build a package of hacks or adhock hacks, you are still hacking which later on down the line could present issues, especially with incompatibilities like systemd
Im a firm believer of it must work for the intended operating system without too many indirection's, if not then well look elsewhere.
Sorry it just reads like a pointless abstraction layer, not your fault of course, you are trying to circumvent systemd pervasiveness in programming. Debian was supposed to be a universal operating system, not a universal init system.
Add this one to the list "maybe"....PsychOS (im not affiliated, just found it on distrowatch).
Very retro man!
https://psychoslinux.gitlab.io/index_modern.html
website doesn't format very well on my end?
Distrowatch
https://distrowatch.com/weekly.php?issu … 13#waiting
Downloads
HevyDevy wrote:also have a look at the link below for the issue with "ifup: wating for lock on /run/network/ifstate.eth0".
So, now onto EVIOCGABS /dev/input/event7
I presume something is not coming up quick enough for the system, although everything seems to be working.
I seem to remember something link this in ubuntu many years ago and it was because the MBP keyboard uses usb connection.
what are your computer specs. Neofetch is a good peice of software for this.
sudo apt install neofetch
then show us the output of below command.
neofetch --stdout
also have a look at the link below for the issue with "ifup: wating for lock on /run/network/ifstate.eth0".
open wicd-gtk if you have it, go to preferences and untick
"always switch to a wired connection when available"
im assuming that is ticked and it is eth0 ?
you should be able to set wireless "wlan0" to automatically connect if that is what you want in wicd-gtk.
^ afaik, that package houses intel wifi firmware for various devices, not sure why you get that message though, probably spurious.
that version has a hard dependancy on systemd, that is why it is not in the devuan repos. If you want this to work, use debian stable. You link to a debian testing package too, why?
jamesthedisciple wrote:on installing I had to connect through eth0 as wlan is a broadcom card. now that wifi is working I'm not using eth0.
What setting do I need to change?Have you installed the Broadcom drivers? I would just throw that POS away and buy an Intel card instead but you should be able to get it working, after a fashion.
I think you misread that, i dont blame you either.
1. connection is ok in broadcom land (probably installed brcm80211 driver).
2. not using eth0 lets get rid of it, why is it hanging around fmd, fml.
James, what network manager are you using if any?
HevyDevy wrote:So you are saying openbsd arbitrary downloads non-free firmware upon booting a newly installed system?
Not arbitrarily, only firmware that is required by the hardware is downloaded. The reasoning is that any hardware that doesn't load firmware blobs from the operating system has them implanted in ROM at the factory instead so the battle is already lost, so to speak.
HevyDevy wrote:as far as i am aware fw_update is/was a manual process?
No, it's run automatically on first boot and also after updating to a fresh snapshot in -current.
HevyDevy wrote:are these the only firmware files openbsd supplies?
Yes, I think so.
when i installed openbsd iwm firmware was already in the install i think as going by the boot messages i had a fatal failure for my card (intel wifi chip) , i had no working net connection until i finished installing the sets and booted into openbsd and connected from the smart phone. I havent touched that partition in a few weeks, maybe i dont understand the process properly in regards to firmware, is that firmware bundled with the sets and only installs when needed?
sort of defeats the purpose of being systemd free in a way doesnt it? Would openrc be of any help, its easy enough to create startup scripts for openrc.
pj1967 wrote:OpenBSD seems like a viable starting point for a new opensource OS fork. It's clean, simple, and resists binary blobs
No it doesn't, fw_update(1) is run automatically on first boot of a new system and that downloads any firmware blobs required by the hardware and loads it.
So you are saying openbsd arbitrary downloads non-free firmware upon booting a newly installed system?
as far as i am aware fw_update is/was a manual process?
are these the only firmware files openbsd supplies?
Looks like that version is unavailable in the devuan repos.
I dont think so...
~$ apt search tomcat9
Sorting... Done
Full Text Search... Done
libtomcat9-embed-java/testing 9.0.16-4 all
Apache Tomcat 9 - Servlet and JSP engine -- embed libraries
libtomcat9-java/testing 9.0.16-4 all
Apache Tomcat 9 - Servlet and JSP engine -- core libraries
tomcat9-admin/testing 9.0.16-4 all
Apache Tomcat 9 - Servlet and JSP engine -- admin web applications
tomcat9-common/testing 9.0.16-4 all
Apache Tomcat 9 - Servlet and JSP engine -- common files
tomcat9-docs/testing 9.0.16-4 all
Apache Tomcat 9 - Servlet and JSP engine -- documentation
tomcat9-examples/testing 9.0.16-4 all
Apache Tomcat 9 - Servlet and JSP engine -- example web applications
tomcat9-user/testing 9.0.16-4 all
Apache Tomcat 9 - Servlet and JSP engine -- tools to create user instances
Right-click on the lxqt desktop should have "Terminal"
You could quite easily create a panel launcher or keyboard shortcut for this.
Non-root user specified in text install is not added to sudoers - please fix
This is ultimately a user choice as it varies from user to user, some people dont use sudo at all.
Anything to do with Linux headers, Development tools and Vbox is also user choice , i for one would not want them on my install as per default.
Working great for me so far. Is gvfs getting better i wonder, ive always been wary of it but it picks my smartphone up no worries and file transfer is a breeze.
HevyDevy wrote:there must be a good explanation of why /etc/mtab is symlinked to /proc/mounts ?
Probably so but that isn't the case for Debian buster and symlinking to another symlink just sounds wrong.
The content would be the same either way.
So far all ive been able to understand is that it is easier to have /etc/mtab symlinked to /proc/self/mounts in the case of loop devices / losetup. Debian buster uses systemd, so maybe there is a difference in devuan having these symlinks?
You may be right on this, sorry. Man page says....
/proc/mounts
Before kernel 2.4.19, this file was a list of all the filesys‐
tems currently mounted on the system. With the introduction
of per-process mount namespaces in Linux 2.4.19 (see
mount_namespaces(7)), this file became a link to
/proc/self/mounts, which lists the mount points of the
process's own mount namespace. The format of this file is
documented in fstab(5).
Hold on there head on a stick, there must be a good explanation of why /etc/mtab is symlinked to /proc/mounts ?
Maybe run update-grub again and see if the message disappears.
sudo update-grub
HevyDevy wrote:I dont believe removing lvm2 is a solution head on a stick.
Yeah, you're probably right. It was just a stab in the dark tbh.
Its probably something t do with os-prober.