Hacker Newsnew | past | comments | ask | show | jobs | submit | LaSombra's commentslogin

As a contractor sysadmin at the time, managing both Exchange and Notes/Domino, I loved Notes for the simplicity of dealing with backups, to tape and over the VPN.

You mark the database as read only, copy the .nsf file over, unmark the database as read only, done. Brightstor had a plugin for Notes that did that automatically and could do incremental backups with ease.

Move to Exchange and it's horrible single file mail storage solution which was inconceivable when hard drives weren't that big. 10,000 users? It's 100MB of mail so it can fit nicely in a single storage volume. Backups? Well, only at night because you have to unmount the file from Exchange, copy it over, and mount it again, which took a good couple of hours.

I miss Notes "simplicity".


I don't buy the argument that it was an accident or mistake.

If you decide to let things run haywire, then unexpected outcomes will definitely happen.


We do not need more datacenters as well.


As you don't _need_ a datacenter as well


I'm pretty sure it'll be an AI dump fest with barely any humans except the long term maintainers having to cope with it all.


I mean, it won't be neither the first nor the last slopdump, but it's the first that's backed by a threat of project takeover.

“Maintainers of last resort”, my [back].


We need more activism like this.


This might be the move that cements BYD in western markets.


If you want to create a new systemd unit file you can run:

   $ sudo systemctl edit --force --full my-scheduled-work@.timer
or

   $ systemctl edit --user --force --full my-scheduled-work@.timer


Why the @?


Systemd lets you create templates that take an argument in from the scheduled service. It gets that from the value after the @. So you can write a unit file that schedules a task to run say every 3 days and in that unit file reference `jobs/%i`, then put your task in a file in jobs and say `systemctl start every-3-days@script1.sh` to run `script1.sh` on your schedule without needing to create a new unit file for each script. StepCA has a nice write up on their site about using these templates to schedule cert renewals for any arbitrary service


Oh cool, thank you


As long as we don't see the damaged areas around data centers than all is fine, right?

Where have I heard this before?


What damage do you have in mind? I live next to a big cluster of data centers, second biggest in Europe, and I haven't seen anything like "damage" from them.


What damage?


Don’t let facts get in the way of a catchy headline


:love


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: