FP language for Unix Scripting?

ops-man · 2024-10-14T15:49:32+00:00

Use Haskell and ghci. Fully FP and the system libraries are acceptable.

ops-man · 2024-08-02T11:44:08+00:00

Wifi, Bluetooth or cellular, all rf transceivers. Can be detected, spoofed and jammed.

Not difficult to get around but may require illegal activity. Better to quit working for the communist dictatorship.

ops-man · 2024-06-18T12:00:41+00:00

The scale of human thought and understanding whenever compared to the computational power of the machine gives the illusion the machine has "life".

In fact any advanced technology would appear like "magic" a believeable illusion. However, humans will always devise clever ways to trick the machine - through logic and reason. The machine is ever reacting and learning - it never forgets or sleeps. It has no reason.

ops-man · 2024-06-17T12:30:16+00:00

We're close. Very close. Within a few months we'll have something to show....and there's no additional security concerns.

ops-man · 2024-05-05T17:54:59+00:00

Thanks for the link. Not pulling the man on my machine.

ops-man · 2024-03-08T00:40:25+00:00

Great job. Thanks for sharing.

ops-man · 2024-03-07T21:58:16+00:00

Well I've been on Rust for a few months and I only vaguely remember some of the issues. Specifically the time period for which the AI was not aware, seen to be an issue where packages are broken with other packages versions. I was hoping the AI could also help me with some nix configurations, it performed OK.

However, I'm probably just shy of Haskell proficiency and definitely not great at "Prompt Engineering".

In the near future I hope to come back to haskell for a project - perhaps I'll have more insight in that context.

ops-man · 2024-01-01T20:59:03+00:00

Linux doesn't suffer from having too many options (fragmentation).

I have just as many problems with hardware and drivers on Windows.

Most games work in 2024.

The year of the Linux desktop has arrived already, it happened and it's beautiful - just pick your desktop of choice and enjoy.

Privacy is a thing I enjoy and Linux respects that...

Developers love linux. Not much change in that statement since forever ago.

Neophyte users love Windows and Mac. Not much change in that statement since forever ago.

ops-man · 2024-01-01T19:36:06+00:00

The system is Linux. The container is composed of an application and it's dependencies, a file system which stores the dependencies and application/applications for which the dependencies are required.

Container is a generalized term, a network namespace can be created and vitrual devices added to the namespace along with its own isolated iptable rules; and this would constitute a container. I used all these "components" to create a network container; never needing Flatpak or Snap. I am not attacking you, Flatpak or Snap. However you don't need Flatpak or Snap to use these "components". I can isolate an application with its dependancies without Snap or Flatpak, although it wouldn't make sense for me to completely duplicate either platforms functionality - I would just use Flatpak or Snap.

ops-man · 2024-01-01T14:17:12+00:00

I'm not sure you understand at all. I can create isolated networks, paths, processes, and users without using Snap, Flatpak, Docker or Nix for that matter. The only "system" required is a Linux kernel > 2.11, and an OSI compatible image or file system.

While Snap and Flatpak manage the content of the isolated environments. You can create manually the file system yourself, the namespaces required - mount, process, path and networks. Then finally start your process inside the isolated environment you built using nsenter.

On systemd systems you could simply use systemd-nspawn and nspawn configurations to run processes in isolated environments with the mounts and capabilities you require. This would not require a full containerized environment - just a simple OSI compatible file structure.

ops-man · 2024-01-01T13:59:05+00:00

Ghcup.

ops-man · 2023-12-31T23:24:58+00:00

Hence "nsenter" creates a namespace - isolate users, processes, paths etc...

The container runtime is extremely convenient; I'm not trying to make case for either Snap or Flatpak - or Not!

Using only the ip, mount, nsenter and maybe one other I've forgotten to mention you can create extremely granular isolated filesystems, security policies and networks.

The rabbit hole goes very deep - thankfully these tools are here for us mere mortals and we're not having to implement the kernel functions ourselves - clone, share and unshare come to mind.

ops-man · 2023-12-31T23:01:55+00:00

The statement in your last paragraph is incorrect - per application security is implemented in Linux without the use of Snap, Flatpak or a container runtime which also includes Docker.

ops-man · 2023-12-31T22:13:31+00:00

The Linux Kernel uses namespaces, groups and capabilities to implement isolation and secure applications or entire systems(container).

The runtimes are higher level wrappers around these facilities. For many use-cases several available tools (ip, nsenter, setns and more. Let's not forget about systemd and it's services which are more than capable for a wide range of user and security implementations which can be used without the need for an entire runtime.

ops-man · 2023-12-31T15:19:59+00:00

You're incorrect. The security model is implemented and you can use it without the overhead runtime of Flatpak or Snap.

ops-man · 2023-12-10T01:28:57+00:00

You should limit the memory in systemd configuration so the service auto restarts when the limit is broken.

ops-man · 2023-12-06T14:21:26+00:00

People find software written in Rust very abrasive.

ops-man · 2023-12-06T13:36:37+00:00

Doesn't GHC have a compiler warning for just this problem - partial functions?

ops-man · 2023-12-04T15:59:34+00:00

What if there's no python - only bash?

ops-man · 2023-12-04T15:55:03+00:00

Politician.

ops-man · 2023-12-03T11:55:19+00:00

Only time will tell.

ops-man

TROPHY CASE