most of that 'magical number' stuff is inserted by shills, anon.
any estimates as to a time when the public will know for sure that Trump won, like we do here?
with out a civil war?
marijuana should stay illegal but you're stoned?
I love the patch. If real TY for your service.
yes, this is what I see.
when the guy walking his dog who seemed out of politics knows that Trump won . . . and I can say to my blue wave Christmas light neighbor that he could try a different color scheme now . . . and he'll chuckle and keep pealing off the Biden stickers from his small 'lectric car
I think many will hear it like this:
"we can make weed legal now becuase if we want to arrest you will just do it anyway."
did they use the RPM Build functionality to . . . 'update' a steal?
it would not be hard to do.
the RPM BUILD directory is in . . .
and if you use it with sudo you can do anything to the harddrive . . . that the SELinux lets you do.
can they check the logs and see if it was updated during the counting process using the dnf/rpm build system? did they do a dnf upgrade during the use of the machine for voting?
if so do they have the rpm files still in the cache?
they'll both be at the same party and no one will get hurt by either.
they probably will be like 'what's up with the conflict mongerer' (that's you)
use journal control to dump a full set of logs in ascii and post them somewhere.
do they have the root passwords?
Do the machines run Linux? I read that the UcLinux is now a mainline Linux.
that means a lot and Ron (CM) must know these things.
journalctl -b will give a log for the current boot.
journalctl can be used to look at the logs for any boot going back to a time when the logs started, and it can be a very long time.
it should tell all about SE Linux denials or other suff as long as it was configured to do that. I hope (It would have to be a requirement?) that they were required to run it with SELinux enabled . . .
the RPM BUILD will be a directory under the root of the user and it allows one to 'place' the files in a tree structure so that they will be mirrored on the other drive. And then one takes the utility and essentially 'zips' that directory tree structure up and then . . . it will be reproduced on the target drive upon runing the rpm. But rpm is also 'proxied' by dnf and yum. This is not really that useful to know however:
if the user of RPMBUILD knows which file to replace, they could dummy one up on a different drive, and then zip that up into an rpm and then install that rpm on the target system.
the thing is that the rpm file would be an artifact of that. So they would also need to 'cover it all up' by deleting all that too . . .
safest way would be a local (safe meaning so they don't get caught) on a locally networked box running a secure client over to the other machine.
but if they had that they could jsut go to the driectory and do the swith usind a secure copy . . . if the system will let them.
all access to that system should be logged.
any access on odd ports should be blocked or unavailable.
the logs would give us a real heads up assuming they were enabled to do that.
one other point about RPM : you can set up to install from a USB using autoload functionalities of various subsystems of the operating system.
that, too, should be logged if the system were set up sanely.