WasPentalive @ waspentalive @lemmy.one

Posts

43

Comments

360

Joined

2 yr. ago

A stein is a cup to drink beer from, If your beer is not very yellow, you might have a pale stein.

I guess if you write a set of declarations for NixOS you can copy that same file to the new machine. Thanks for the pointers. What about the "install facts" being just a byproduct of the first install? You don't even have to write a script.. anyway. It seems there are ways to do this already, Thanks!

I have changed the syntax a little: //jo jobname owner(username) log(mailto=user@location) class(a) //** Note that the next step copies /etc/passwd to /tmp/jobname/passwd and then later deletes it when the job is done //dd passwd disp(scratch) source(file=/etc/passwd)
//ex cat passed //!! End of Job

What if one could use this to submit jobs to run on a local server (or a far away one) via email - mail lcl@remoteserver.org Then either paste in the lcl file or attach it to the email. If your owner clause is an email address, the job will be returned via email. The username on the owner clause has to be also a user on the remoteserver. If your username on the two machines differ, you may have to use a //ex to send the log back to you.

ce n'est pas un comment

It is not mandatory that you install it - Yes, there are other choices already. But in the beginning, Unix only had C and Assembly why didn't we just stick with those?

More Detail::: What SUBMIT Does with Each LJL Statement:

For every statement, SUBMIT generates corresponding commands in the .deck file. Below is a step-by-step breakdown:

One //jo line, as many /dd lines as are required, and as many //ex as are required

//jo sumjob owner=me@mail.com log=print class=a

• Generates a deck command to invoke ifclass a, which checks if the job's class allows execution at run time.
• Generates a deck command to Log "sumjob is starting" to /var/log/JCL/ with a timestamp.
• Generates a deck command to create /tmp/sumjob
• Generates a deck command to initializes /tmp/sumjob/jobname.log with a formatted header (e.g., via figlet sumjob).

Job Classes: A = Runs as soon as submitted B = Runs only if load is low enough C = Runs in Off-Hours

//dd alias source(here|file=pathandfilename|new) disp(keep|scratch)

• Note the disp (disposition) if keep the put the file in /home/user/.lcl/jobname as whatever the alias is if the disp(scratch) then the file will go into the /tmp/jobname directory as named by the alias.
• Generate deck commands to

-- if source is here: copy lines from lcl up to '/*' to the deck file as a here document if source is a file: add commands to copy the file into a working directory either in user's home or in the tmp directory under the alias. //dd users source(file=/etc/passwd) disp(keep) ==> copy /etc/passwd to /home/user/.ljl/users

//ex somecommand --options < alias

-Generate doc commands to execute the program as specified and save the output to the logfile In this case echo (somecommand --options < aliasproperlyexpanded ) > logfile

The deck file now forms a fully functional batch file to do the specified computation.

I manually created a .deck file to compile and run a Fortran program with specific data and to create a .log file of all the output, the Fortran program, and the data. I found it to be picky and somewhat hard. So I thought to myself: With something like JCL, one could take simple JCL-like statements, here documents for the source and data files, and programmatically combine them to make a script like the one I created manually.

Debian/KDE because I like the way I can customize (1 panel on the left with everything) No features removed just as one gets used to them. (looking at you gnome) No breaking changes to the desktop gadget api every update (you gnome again) Nice big repo.

Sorry my drawing did not come out well.

Drawing it up.. : ^) Sorry, I am not a very good artist and it's hard getting AI to give you exactly what you want when you want something exact.

t+ and T- to upstream neighbor (2) + a single wire from upstream to tell you to send (3), R+ and R- (5) to down stream neighbor + a single wire to let downstream know when you can receive from them.(6) And a pair to control a relay in what would be like a token ring MAU. Token ring is also a logical ring and a physical star: All the physical cables come to a central hub (physical star) but the machines are connected

    
Logical Ring                                                       Physical Star
+-->[ r t ]--> [r  t] -->[ r  t ]--> [r  t] --> [ r t]--+       [ machine1 ] ===== cat 6 ==== |  mau |=====cat6== [ machine 3 ]
 |                                                                 |       [ machine2 ]====== cat 6 ====|          |====cat 6 == [ machine 4 ]
+-----------------------------------------------------+


  

until the last machine loops around to connect to the first.

Is it anything like token ring? No, The difference is no token to lose, No ring master or deputy ring master to lead things- everyone just plays along according to basic rules. Any machine can move data to it's upstream neigbor at any time that neighbor is ready to take it, no one machine at a time getting to talk. So it's not like token ring. Also unlike Ethernet, you can connect any number of machines in a ring: 5 for a small office, 20 for a department of a large firm, 200 for every employee of a firm, 2000 for all the offices of a company or a part of a neighborhood. Since machines are not contending for bandwidth there is no collision, no backdown and resend.

Rings of machines are connected to bigger rings via gateways - which also have their own way of assigning addresses to each of their ports.

1. enough network wide addresses for anyone
2. addresses not controlled by any agency, but each machine gets a "computed" address by virtue of it's own port address+the port on the gateway it is talking to.

I don't bend my values for entertainment. I pick my OS for privacy and freedom first. If a game won't run on it, that game doesn't run in my life.

I used chatGPT to work up a backup program that tracked rsync backups as I wanted and could report which backups needed to be run and which ones should be started fresh because too many rsync runs from my home dir to the target dir. It's call Loci, and it's on codeberg.

I think I read this is how HP supplies their "no OS" machines - a very thin Linux with a VM running the FreeDOS fullscreen.

"UEFI does have a legacy compatibility layer" And this is how one may have a "system firmware" that allows both. Could DOS be made UEFI compatible maybe by loading a .sys driver or maybe by replacing io.sys with one that made use of UEFI?

My system came with Python3 installed. Debian 12.

Ah, Improvements!

Looks like a line by line translation from the python. Will you use it to backup your home directory?