« first day (3830 days earlier)      last day (1123 days later) » 

12:10 AM
having read the complaint, it's not complete garbage, but the FreeBSD-destroying claims are quite weak, and the copyright claims are all about AIX this time
 
 
8 hours later…
8:19 AM
@AndrasDeak apparently it was actually posted on March 31st (the press release on their site has that date, I didn't look at the court papers, I have to keep some of my sanity)
@MichaelHomer you have curious hobbies. (assuming it was voluntary. If it's part of your job or such, then I'm sorry.)
 
@ilkkachu I read it in between those two messages
 
ok
 
 
2 hours later…
10:32 AM
@ilkkachu the court papers are also dated 31 March
 
 
3 hours later…
1:28 PM
Hey
I need some help with grep
 
 
2 hours later…
3:43 PM
@pourjour we have a bunch of grep questions on the site, but if none of those are your situation, consider asking a question. If you need help describing your problem, feel free to use this chat for that!
 
 
5 hours later…
8:34 PM
Do you, with "use crontab", mean "run cron jobs", or do you mean just "use crontab"? The proper way to test whether you can run cron jobs is to try to use the crontab command. Well, that's would be the proper way to test whether you can use crontab too, of course. So, what's the issue with testing this? It seems to me that you just need to be able to test crontab -l with sudo changing you into any given user. — Kusalananda ♦ 36 mins ago
Is it possible to have a user (regular user, one with a proper login shell in /etc/passwd) who cannot run crontab?
 
ugh
> You may obtain the original behaviour by setting the environment variable CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.
DONT_NOT_FLIP_NEGATED_LACK_OF_HEADERLESS_STATE='N'
 
9:05 PM
@terdon Yes. In Vixie cron, there's /etc/cron.{allow,deny}: manpages.debian.org/buster/cron/crontab.1.en.html
 
 
2 hours later…
10:56 PM
@ilkkachu Aaah! Thank you. Now that you mention it, I remember the .allow and .deny files but hadn't realized that's how they work. Makes sense, thanks.
 

« first day (3830 days earlier)      last day (1123 days later) »