Search Results for 'ssh'

[Forum Admin anticapitalista]

@fungalnet – this thread is about sysVinit beta2 version.
Are you testing that version?
If so, those runit files come from upstream Debian ssh and acpid packages (particularly acpid as it depends on runit-helper)

Install xserver-xorg-legacy for startx to work without a login manager

Also see this post: https://www.antixforum.com/forums/topic/startx-on-antix-base-and-full/
Running live, I was able to boot to init 3 (just add 3 to the boot menu line and remove the splasht ‘cheat’).
Then I logged in as user, su to root and installed xserver-xorg-legacy (I didn’t need to edit Xwrapper file).
startx gives what we call our min/minimal-wm option.
I then removed slimski, elogind and the desktop still works ok.
Can’t get rid of dbus I’m afraid.

• This reply was modified 1 year, 8 months ago by anticapitalista. Reason: Added more info

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

I did the following searches on this young at heart forum, for libudev-zero, mdev, smdev, nldev, mdevd and found nothing, not a single mention, so here is the story:

Can we live without udevd?

Let’s recapitaluta how wide this struggle has been, to not depend on IBM for your open and free software to work.

On the logind front, consolekit2 is not dead, this is old propaganda, especially with all its development from its BSD fork, consolekit2 is alive and well. But you can live well and prosper (as Spok said) without any logind. I have for quite a while. Then there was the silly myth that wayland can not work without systemd/elogind. Myth busted, the guy that made seatd broke that myth right in the myth manufacturer’s face, and once people started considering using wayland without elogind, they also found out it works perfectly fine even without seatd (if compiled as such). That deep of a myth. It is like saying you need a fishing pole to go on a date…. folklore. Also you don’t need X for wayland/wlroots/sway … it works. I still don’t like it, but whether it works is a different story.

And dbus, that decorative snitch, monitoring and communicating your every click and keystroke? It even monitors and snitches on root’s activities. So to whom is this piece of crap in service of? I’ve lived without it for years now. So more folklore spread around by the IBM parakeets.

But we are stuck with a big IBM chunk, we are not out of the hole yet, we love what IBM does for us (like junkies love the pusher) from the second we hit enter on the bootloader screen. udev hooks running and rerunning and eternally running till everything is shutdown and gone to sleep.

IS (not are) there an alternative?

Years ago somebody decided they’ve had enough with udev and wrote smdev. As simple and lean as it can possibly be, with the ability to be enriched by hw modules for anyone that desired more than a simple x86 machine booting, having classic input/output abilities, reading/mounting disks, and a few simple additional hw. It worked, it is simple (suckless) and the great story is that it runs once and ends, doesn’t need to be daemonized (thank anticapitalista for that – if you have to thank anyone – because it takes a few seconds for each run). But as hw get more fancy and multiple in necessity, it wasn’t enough for people to adopt. So it remained.

Then comes this other solution, an intermediary, which can utilize any mdev provider, simulate the ability to be triggered by a change in hw, run the mdev (of choice!), and provide new definitions for hw adder/removed. This project was called nldev, a middle man.

Then skarnet begins work, not yet finished, to provide a true and complete udev alternative, still less than 1/3 of the code of (udev/eudev/libeudev), and it does work if you study the subject in depth and can configure it right. A nice template of a .conf file to uncomment all its abilities that are utilized, would have been nice, but skarnet wants you to do your own research and make your own choices, just like s6 s6-rc, etc. No ground food and chewed ready for swallowing from skarnet, they like to see you in tears before you make their sw work. Their server has been running for a ?decade? with it, with reboots only taking place in leap years, and if there is no pandemic.

BUT!!!

Why aren’t users and distro devs running to adopt such solutions? 1 reason! X is having problems with them, in most cases you can’t get the keyboard and mouse to work properly. That’s a big one … for most people, let’s be realistic. “Some” people don’t need X, they do all their work on console, their greps and cuts and sed and vis, is all they need, and lynx for a fancy browser to relax from coding.
Why is X so peculiar about the specific mdev? Because it was written with the single piece of available to them and looks for its coding.

Pop goes the myth of X would only work with IBM’s udev.

libudev-zero

A very young and promising project, getting about 5-6 upgrades just this past week alone, although it worked 10 days ago when I fist tried it.
On the early trials I replaced libeudev with libudev-zero, booted with eudev, then shut down the daemon, then started X. Cursor, cursor theme, keyboard, all working great. Then tried to substitute eudev with one of the alternatives, I admit I don’t have yet the knowledge and patience to configure mdevd right (Sorry mr.Bercot) but smdev worked, run manually once, and then libudev-zero takes over. As soon as smdev runs and throws 30 pages of nasty looking output on your screen, the screen readjusts (just like in udevd activity), net interfaces become available, and all is well.

Hmm… not so fast slick, how is your kernel image created with smdev?

That begun being tough, mkinitcpio run aground without eudev/udev available, possibly with the libudev-zero in place of libeudev. Here comes the “middleman” that makes any mdev availability work, nldev. You substitute nldev for udev in mkinitcpio.conf and the image is created properly, nldev is configured to run smdev during the boot hooks, and you get a nice console login: with any parts of e/udev removed from the system.
And of course X started normally and my favorite terminal provided a shell.

Not so fast slick! Now that you got linux-lts image booting without udev, what else is there missing?

Ok, Ok, Ok, … (Joe Pesci voice in lethal weapon X) … some things must not work because they were compiled with udev’s existence, which eudev does wonders for substituting because …. IT IS THE SAME CODE!!! Like what, you might ask. lsusb for example, still works but throws some garbage up on top for not being able to get the udev version. The output is still the same as with eudev. /dev/disk/ is empty, but blkid works fine (it doesn’t depend on udev). All mounting/unmounting/ssh/sshfs all work. How about Gparted, does it work? NO! Why? Because it is compiled based on the specific udevd and unless it gets the version number it exits with an error. If you can bypass this, or if you and the coder of libudev-zero figure out a way to fake this functionality, I don’t think there is an issue.

Yet, again, not so fast slick!!! You are tripping over yourself.

libeudev
├─device-mapper
├─eudev
├─libgudev
├─libusb
├─lvm2
├─usbutils
└─util-linux
eudev
├─colord
└─dhcpcd

This is a list of what I have found up to now, that are very base/core parts of almost any linux distro. that depend and ARE built based on udev, and some may work fine, but internally they think that udev is there. So idially they must be rebuilt with the alternative in presence, in my case smdev, nldev, libudev-zero.
This is a little harder to do than I thought, but my abilities are limited. So it is not to say it can’t be done, I’m just passing the torch here for those that understand the importance of doing so and are willing to try it in a test installation.
I can assist with details anyone willing to give it a try, I have a runit script that works with mldev, and a 66/s6 script for not so clear solution for boot@-66, and more.

Just to see the light in the tunnel though, it is rewarding and new land will not be discovered unless we all do a little more pushing of the fence we are trapped in.

Because they want us fenced in and dependent to control us. It is our single mission in life to bring those fences down, because on our land we can build autonomy, on their land we will always be slaves. We will not make this mistake again, to allow our land to be purchased for individual use. Am I losing it? No, anticapitalista knows what I am talking about.

A las barricadas!

anti-X - Adélie - obarun - systemd Free Space

[Member oops]

anticapitalista wrote:

We have in-house apps that you may want to try. 1-1 Assistant, 1-1 Voice and ssh-conduit. See the antiX FAQ for more details.

Right, these antiX tools seem very interesting, but need to change some practices.

[Forum Admin SamK]

Kjellinux wrote:

@aticapitalista

anticapitalista wrote:

We have in-house apps that you may want to try. 1-1 Assistant, 1-1 Voice and ssh-conduit. See the antiX FAQ for more details.

Can 1-1 Assistant be used cross platform?

A few reasons for the in-house antiX apps:
• They are extremely lightweight in the demands placed on the system CPU and RAM. This minimalist approach means they are able to run on a very wide range of of old and new kit

• They work within a local network and/or across the internet

• Except for an ISP, connections across the internet do not depend upon the availability of third party services. Registration with an external provider is not required. This approach means they avoid the whims and changing attitudes of third party providers

• The connection between systems is automatically secured.

The apps in the antiX repos are primarily aimed at use between antiX boxes and are configured for simplicity and security of use. After installing the in-house app, the underlying apps can still be used with other similar apps. In such cases you have to take care of configuration yourself.

Outline
You seem to be interested in VNC connections. For this antiX uses x11vnc to serve a remote desktop and SSVNC to view the remote desktop. They are two independent apps that work together very well but do not depend on each other. It is possible to run x11vnc server on an antiX box and view it using a VNC viewer of your choice running on a box from an entirely different distro or even on a Windows system. The opposite is also possible i.e. the Windows system runs a VNC server of your choice and an antiX box runs an SSVNC viewer.

The original author of x11vnc/SSVNC made binaries available for installation on Windows systems. Of course these were never included in any antiX repo. I don’t know if they are still available, you will have to search for them.

Useful links
https://www.antixforum.com/forums/topic/1-to-1-suite-of-apps-2
https://www.antixforum.com/forums/topic/ssh-conduit-suite
http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/index.html
https://www.youtube.com/watch?v=aEmtZTpKR0A

[Member Kjellinux]

@aticapitalista

anticapitalista wrote:

We have in-house apps that you may want to try. 1-1 Assistant, 1-1 Voice and ssh-conduit. See the antiX FAQ for more details.

Can 1-1 Assistant be used cross platform?

[Forum Admin anticapitalista]

We have in-house apps that you may want to try. 1-1 Assistant, 1-1 Voice and ssh-conduit. See the antiX FAQ for more details.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member Xecure]

There was a small bug in gpm service (sorry for that). It is fixed here.

For some reason, if /etc/default/runit file doesn’t exist, on installed, runsv tries to start to write to the disk for 3 services (). Creating a symlink to /etc/default/runit-antix
sudo ln -s /etc/default/runit-antix /etc/default/runit

calciumsodium wrote:

I don’t see a herbsluftwm desktop option.

There is a problem getting to herbstluft from the live boot menus. I will see what happened there. You can reach herbstluft from the slimski F1 toggle (log out first), or make it appear on the “Other Desktops” menus with the command
sudo /usr/local/lib/desktop-session/desktop-session-update-wm-menus -f

anticapitalista wrote:

We basically removed the logs (not sure if that is a good idea or not to be honest).
I think we missed a couple though, eg acpid, ssh

acpid and openssh-server automatically add the runit services to /etc/sv, so nothing else we should do.

logs (at least for acpid on this ISO) require the existence of a user named runit-log from group adm (runit-log:adm). On some devuan posts they stated user “_runit-log” (see the “_” symbol) instead. I think that this user should be created by the runit installer, but it isn’t, so something else needs to create it instead of services expect it to exist.

A log folder can be created for any of the services. If you add this run file:

#!/bin/sh
set -e

NAME=template
LOG="/var/log/runit/$NAME"

test -d "$LOG" || mkdir "$LOG"
exec chpst svlogd -tt "$LOG"

Replacing “NAME=template” with the correct service name, it will work properly and log as root to /var/log/runit/$NAME

If you decide it is a better idea to have logs, then let me know and I will edit the runit-services-antix project.

• This reply was modified 1 year, 8 months ago by Xecure. Reason: Explain better

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Forum Admin anticapitalista]

You should see it (herbstluftwm) at the login screen by toggling F1.

We basically removed the logs (not sure if that is a good idea or not to be honest).
I think we missed a couple though, eg acpid, ssh

I’m also not too sure if user really wants all the symlinks in /etc/service/
Although the deamon itself does not run with a blank down file, it seems sv still checks for it eg cron, cups.
If you delete all folders in /etc/services/ (or better unlink them to /etc/sv/*) EXCEPT the following connman (actually if you use ceni it isn’t necessary), dbus, dhclient, elogind, getty-tty1, getty-tty1, slimski, udevd, both RAM as CPU usage goes down with no obvious issues I can see.

Anyone know how Void or artiX linux sets up services running once installed to hard disk?

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

————————————————————————
The Debian Project https://www.debian.org/
Debian 11 “bullseye” released press@debian.org
August 14th, 2021 https://www.debian.org/News/2021/20210814
————————————————————————

After 2 years, 1 month, and 9 days of development, the Debian project is
proud to present its new stable version 11 (code name “bullseye”), which
will be supported for the next 5 years thanks to the combined work of
the Debian Security team [1] and the Debian Long Term Support [2] team.

1: https://security-team.debian.org/
2: https://wiki.debian.org/LTS

Debian 11 “bullseye” ships with several desktop applications and
environments. Amongst others it now includes the desktop environments:

* Gnome 3.38,
* KDE Plasma 5.20,
* LXDE 11,
* LXQt 0.16,
* MATE 1.24,
* Xfce 4.16.

This release contains over 11,294 new packages for a total count of
59,551 packages, along with a significant reduction of over 9,519
packages which were marked as “obsolete” and removed. 42,821 packages
were updated and 5,434 packages remained unchanged.

“bullseye” becomes our first release to provide a Linux kernel with
support for the exFAT filesystem and defaults to using it for mount
exFAT filesystems. Consequently it is no longer required to use the
filesystem-in-userspace implementation provided via the exfat-fuse
package. Tools for creating and checking an exFAT filesystem are
provided in the exfatprogs package.

Most modern printers are able to use driverless printing and scanning
without the need for vendor specific (often non-free) drivers.
“bullseye” brings forward a new package, ipp-usb, which uses the vendor
neutral IPP-over-USB protocol supported by many modern printers. This
allows a USB device to be treated as a network device. The official SANE
driverless backend is provided by sane-escl in libsane1, which uses the
eSCL protocol.

Systemd in “bullseye” activates its persistent journal functionality, by
default, with an implicit fallback to volatile storage. This allows
users that are not relying on special features to uninstall traditional
logging daemons and switch over to using only the systemd journal.

The Debian Med team has been taking part in the fight against COVID-19
by packaging software for researching the virus on the sequence level
and for fighting the pandemic with the tools used in epidemiology; this
work will continue with focus on machine learning tools for both fields.
The team’s work with Quality Assurance and Continuous integration is
critical to the consistent reproducible results required in the
sciences. Debian Med Blend has a range of performance critical
applications which now benefit from SIMD Everywhere. To install packages
maintained by the Debian Med team, install the metapackages named med-*,
which are at version 3.6.x.

Chinese, Japanese, Korean, and many other languages now have a new Fcitx
5 input method, which is the successor of the popular Fcitx4 in
“buster” ; this new version has much better Wayland (default display
manager) addon support.

Debian 11 “bullseye” includes numerous updated software packages (over
72% of all packages in the previous release), such as:

* Apache 2.4.48
* BIND DNS Server 9.16
* Calligra 3.2
* Cryptsetup 2.3
* Emacs 27.1
* GIMP 2.10.22
* GNU Compiler Collection 10.2
* GnuPG 2.2.20
* Inkscape 1.0.2
* LibreOffice 7.0
* Linux kernel 5.10 series
* MariaDB 10.5
* OpenSSH 8.4p1
* Perl 5.32
* PHP 7.4
* PostgreSQL 13
* Python 3, 3.9.1
* Rustc 1.48
* Samba 4.13
* Vim 8.2
* more than 59,000 other ready-to-use software packages, built from
more than 30,000 source packages.

With this broad selection of packages and its traditional wide
architecture support, Debian once again stays true to its goal of being
“The Universal Operating System”. It is suitable for many different use
cases: from desktop systems to netbooks; from development servers to
cluster systems; and for database, web, and storage servers. At the same
time, additional quality assurance efforts like automatic installation
and upgrade tests for all packages in Debian’s archive ensure that
“bullseye” fulfills the high expectations that users have of a stable
Debian release.

A total of nine architectures are supported: 64-bit PC / Intel EM64T /
x86-64 (amd64), 32-bit PC / Intel IA-32 (i386), 64-bit little-endian
Motorola/IBM PowerPC (ppc64el), 64-bit IBM S/390 (s390x), for ARM, armel
and armhf for older and more recent 32-bit hardware, plus arm64 for the
64-bit “AArch64” architecture, and for MIPS, mipsel (little-endian)
architectures for 32-bit hardware and mips64el architecture for 64-bit
little-endian hardware.

If you simply want to try Debian 11 “bullseye” without installing it,
you can use one of the available live images [3] which load and run the
complete operating system in a read-only state via your computer’s
memory.

3: https://www.debian.org/CD/live/

These live images are provided for the amd64 and i386 architectures and
are available for DVDs, USB sticks, and netboot setups. The user can
choose among different desktop environments to try: GNOME, KDE Plasma,
LXDE, LXQt, MATE, and Xfce. Debian Live “bullseye” has a standard live
image, so it is also possible to try a base Debian system without any of
the graphical user interfaces.

Should you enjoy the operating system you have the option of installing
from the live image onto your computer’s hard disk. The live image
includes the Calamares independent installer as well as the standard
Debian Installer. More information is available in the release notes [4]
and the live install images [5] sections of the Debian website.

4: https://www.debian.org/releases/bullseye/releasenotes
5: https://www.debian.org/CD/live/

To install Debian 11 “bullseye” directly onto your computer’s hard disk
you can choose from a variety of installation media such as Blu-ray
Disc, DVD, CD, USB stick, or via a network connection. Several desktop
environments — Cinnamon, GNOME, KDE Plasma Desktop and Applications,
LXDE, LXQt, MATE and Xfce — may be installed through those images. In
addition, “multi-architecture” CDs are available which support
installation from a choice of architectures from a single disc. Or you
can always create bootable USB installation media (see the Installation
Guide [6] for more details).

6: https://www.debian.org/releases/bullseye/installmanual

There has been a lot of development on the Debian Installer, resulting
in improved hardware support and other new features.

In some cases, a successful installation can still have display issues
when rebooting into the installed system; for those cases there are a
few workarounds [7] that might help log in anyway. There is also an
isenkram-based procedure [7] which lets users detect and fix missing
firmware on their systems, in an automated fashion. Of course, one has
to weigh the pros and cons of using that tool since it’s very likely
that it will need to install non-free packages.

7:
https://www.debian.org/releases/bullseye/amd64/ch06s04#completing-installed-system

In addition to this, the non-free installer images that include firmware
packages [8] have been improved so that they can anticipate the need for
firmware in the installed system (e.g. firmware for AMD or Nvidia
graphics cards, or newer generations of Intel audio hardware).

8:
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/

For cloud users, Debian offers direct support for many of the best-known
cloud platforms. Official Debian images are easily selected through each
image marketplace. Debian also publishes pre-built OpenStack images [9]
for the amd64 and arm64 architectures, ready to download and use in
local cloud setups.

9: https://cloud.debian.org/images/openstack/current/

Debian can now be installed in 76 languages, with most of them available
in both text-based and graphical user interfaces.

The installation images may be downloaded right now via bittorrent [10]
(the recommended method), jigdo [11], or HTTP [12]; see Debian on
CDs [13] for further information. “bullseye” will soon be available on
physical DVD, CD-ROM, and Blu-ray Discs from numerous vendors [14] too.

10: https://www.debian.org/CD/torrent-cd/
11: https://www.debian.org/CD/jigdo-cd/#which
12: https://www.debian.org/CD/http-ftp/
13: https://www.debian.org/CD/
14: https://www.debian.org/CD/vendors

Upgrades to Debian 11 from the previous release, Debian 10 (code name
“buster”) are automatically handled by the APT package management tool
for most configurations.

For bullseye, the security suite is now named bullseye-security and
users should adapt their APT source-list files accordingly when
upgrading. If your APT configuration also involves pinning or
APT::Default-Release, it is likely to require adjustments too. See the
Changed security archive layout [15] section of the release notes for
more details.

15:
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information#security-archive

If you are upgrading remotely, be aware of the section No new SSH
connections possible during upgrade [16].

16:
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information#ssh-not-available

As always, Debian systems may be upgraded painlessly, in place, without
any forced downtime, but it is strongly recommended to read the release
notes [17] as well as the installation guide [18] for possible issues,
and for detailed instructions on installing and upgrading. The release
notes will be further improved and translated to additional languages in
the weeks after the release.

17: https://www.debian.org/releases/bullseye/releasenotes
18: https://www.debian.org/releases/bullseye/installmanual

About Debian
————

Debian is a free operating system, developed by thousands of volunteers
from all over the world who collaborate via the Internet. The Debian
project’s key strengths are its volunteer base, its dedication to the
Debian Social Contract and Free Software, and its commitment to provide
the best operating system possible. This new release is another
important step in that direction.

Contact Information
——————-

For further information, please visit the Debian web pages at
https://www.debian.org/ or send mail to <press@debian.org>.

--
Brian Masinick

[Forum Admin Dave]

Not 100% sure, I am quite rusty with manually setting ip tables.
I think you will need to specify the master INPUT DROP after all the other entries, otherwise it will be the first to match and always drop.
Also I am not sure what services you are using, but if I recall correctly for SSH (based on the port 22 rule) you will also need an OUTPUT –sport rule. Otherwise the server will receive the client request but not be able to reply. This is assuming you do not allow all output.

• This reply was modified 1 year, 9 months ago by Dave.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Moderator christophe]

Devo dizer que não sou um especialista, de forma alguma. Eu gosto de habilitá-lo – “apenas no caso”.

https://averagelinuxuser.com/linux-firewall/

Aqui está um pequeno trecho desse link, que expressa minhas idéias sobre segurança na internet / web:

Mas não se preocupe, seu Linux ainda está seguro, mesmo sem um firewall ativo. Por padrão, a maioria das distribuições como Ubuntu e Linux Mint não tem portas abertas, portanto, seu computador não pode ser acessado por invasores.

No entanto, recomendo ativar um firewall. É melhor estar seguro do que pesaroso. Um firewall não usa muitos recursos, mas adiciona uma camada extra de segurança. Um usuário inexperiente pode abrir acidentalmente algumas portas sem saber, por exemplo, instalando samba, ssh, apache. Nesse caso, o firewall ainda protegerá o sistema de acessos externos.

MAS – Eu também uso um capacete sempre que dirijo um carro.

Só estou brincando sobre esse último …;)

——————————————-
original text:

I have to say I am not an expert, by any means. I like to enable it — “just in case.”

https://averagelinuxuser.com/linux-firewall/

Here’s a short excerpt from that link, which expresses my thoughts on internet/web safety:

But don’t worry, your Linux is still secure even without an active firewall. By default, most of the distributions such as Ubuntu and Linux Mint have no open ports so your computer cannot be accessed by intruders.

Nevertheless, I recommend to activate a firewall. It is better to be safe than sorry. A firewall does not use many resources, but it adds an extra layer of security. An inexperienced user can accidentally open some ports without knowing it, for example, by installing samba, ssh, apache. In this case, the firewall will still protect the system from outside access.

BUT — I also wear a crash helmet whenever I ride in a car.

Only joking about that last one… 😉

confirmed antiX frugaler, since 2019

[Anonymous]

but he has massive file transfers and

disk-to-disk?
across a LAN?
downloading from an external network? FTP? NFS? SAMBALAMBALOO?

https://unix.stackexchange.com/questions/48399/fast-way-to-copy-a-large-file-on-a-lan

mbuffer!

The biggest bottleneck in transferring large files over a network is, by far, disk I/O. The answer to that is mbuffer or buffer. They are largely similar but mbuffer has some advantages. The default buffer size is 2MB for mbuffer and 1MB for buffer. Larger buffers are more likely to never be empty. Choosing a block size which is the lowest common multiple of the native block size on both the target and destination filesystem will give the best performance.

Buffering is the thing that makes all the difference! Use it if you have it! If you don’t have it, get it! Using (m}?buffer plus anything is better than anything by itself. it is almost literally a panacea for slow network file transfers.

If you’re transferring multiple files use tar to “lump” them together into a single data stream. If it’s a single file you can use cat or I/O redirection. The overhead of tar vs. cat is statistically insignificant so I always use tar (or zfs -send where I can) unless it’s already a tarball. Neither of these is guaranteed to give you metadata (and in particular cat will not). If you want metadata, I’ll leave that as an exercise for you.

Finally, using ssh for a transport mechanism is both secure and carries very little overhead. Again, the overhead of ssh vs. nc is statistically insignificant.

Regardless of O/S, optimizations are probably avilable via tweaks to sysctl parameters, and choice of filesystem + settings. Changing O/S instead of identifying//fixing the bottleneck seems like misdirected effort.
.

[Member Xecure]

The who command pulls its data from /var/run/utmp, which contains information about users currently logged in via services such as telnet and ssh.
I think it doesn’t show on users logged in with the display manager.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

I’ve been playing around with remaster so I can better understand the consequences of choosing this or that.

I boot up using p_static_root

Lets say I create a file in my home directory (not in the live-usb-storage) and call it test.txt

Unless I tell the remaster (using personal) to save /home to the new linuxfs file my test.txt (and anything else, like .vim configuration files, etc) are NOT going to get put into the new remastered system correct?

I guess I’m just confirming because I did a test and that was what happened. It would seem to me though you would WANT you home directory data to be retained after a personal remaster, so I don’t understand the case where you are looking to blast everything in /home after a personal remaster. For instance, .vim or a .ssh folder which by default are home to be in /home/user which it seems you would want to keep.

• This topic was modified 1 year, 11 months ago by Danathar.

There is a bug in the runit editions of antiX-19.4 (full and base) after installation via the gui installer.
Fix: As root user, remove all /etc/sv/* folders EXCEPT /etc/sv/getty-*

Alternatively, BEFORE installation, change line 25 (as root) of /usr/share/gazelle-installer-data/installer.conf to this:

#ENABLE_SERVICES=anacron,cron,sudo,rpcbind,cpufrequtils,smartmontools,acpi-support,acpid,hddtemp,dbus,gpm,saned,avahi-daemon,irqbalance,loadcpufreq,rmnologin,mdadm,lvm2,wicd,connman,connman-vpn,ofono,dundee,haveged,ssh,openVPN,bluetooth,rsync,cups,cups-browsed

• This topic was modified 1 year, 11 months ago by anticapitalista. Reason: Added pre-installation alternative

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.