A handful of barley, rice or oats is a nice addition at the end of a soup. Leafy greensike spinach all chopped up are good at the end too. You wanna stop cooking them when they look more green.

You want a variety of vegetables in your food. Carrots, celery, turnips and all kinds of onions will make the food taste better and nourish you longer.

Here’s how to make soup, broken up into steps that can be done on different days:

Step 1: cook off your chicken. Take cheap cuts like skin on bone in leg quarters and bake them until they’re almost done. In the us you can get big bag for ~.50 cents a pound. When they’re almost cooked, pull em out of the oven and put them in the fridge for later.

Step 2: make stock. Sometime later, debone and remove the skin from your cooked chicken. Save the bones and skin. Take all the vegetables you’re gonna put in the soup and prepare them completely, peeling and slicing onions, carrots etc and slicing ends off celery. Save all that stuff except for potato and turnip parts. Those can go in compost or trash.

It’s easiest if you have an electric pressure cooker like an instant pot for this, but you can do it longer on stovetop if you need. Boil all the vegetable stuff and chicken bones and skin for about an hour and a half in the instant pot or stovetop. If you use the pressure cooker you’ll have rich flavorful broth, if you do stovetop you may need to wait longer for it to get good.

Strain everything out and save the stock.

Step 3: make soup. Start with a roux by melting butter then adding an equal amount of flour and whisking it together. Let it cook while you keep it whisking till it’s as brown as you like and then add your vegetables for a few minutes then stock and chicken. Salt, pepper and herbs can be added at this point and once everything is cooked you can put the handful of grains and chopped up greens in.

Pleco is the dictionary app I use. It does a good job translating phrases I type in and supports a variety of input methods. It has traditional Chinese characters as an option and offers the zhuyin(bopomofo) display as an option too.

I just booted up my copy and to remediate what I’m going out on a limb and assuming is the problem, you’d want to run level 3.

It reads and rewrites every block on the device which, if your slow ssd operations on boot are due to the ssd controller having to try to read a block a bunch of times in order to actually get the contents of the block and pass it down the bus, will speed up the ssd operations that reference frequently read blocks. Like the ones used during the decryption and boot process.

That wiki article is incredibly out of date. The reference for only using level 1 or 2 is from 2013.

E: also I like 4 because ssd endurance is not a big deal and ssds lowkey suck and need to be tested before I use em.

It’s sorted by length because you invoked the blame flag. The blame flag lists the output by start time.

Systemd is multithreaded so it’s not like all this stuff happens in sequence. If that were the case you’d have a computer that takes five minutes to boot.

The tpm is the thing that takes the longest because it has to check a bunch of shit. You can’t do anything about the tpm because you’re using it for encryption and measured boot.

You’re also looking at the wrong thing. Look at all the 3s sections where the system is fiddle fucking around with the ssd. Run spinrite lvl3 or 4 so all those sectors the ssd has to try to read 69000 times get rewritten and see if that doesn’t speed things up.

E: spinrite lvl3

No.

2017 and previous airs and 2016 and previous pros have replaceable storage.

If you’re doing surveillance of people for extrajudicial reasons, constantly need to report crime or are just slurping up all the images of what goes on around your location for some project then it might be useful.

For responding practically to sudden and unexpected crime, dumb game cameras are the goat. They’re cheap, completely self contained, simple, relatively camouflaged (at the very least they’re not a black dome or a hooded ptz up in the corner) and when you need to turn footage over to the cops you can give them the “originals” (the sd card) and keep a copy if they require the originals.

It’s not possible to avoid llm use in volunteer open source development if you prioritize software quality and security.

Whether we want it or not, people looking for bugs are using llms. They are finding phenomenal numbers of bugs. Implementing the fixes has created a huge workload.

Whether we want it or not, the Wayland people have decided that a new, piecemeal system for graphical desktops that relies on many disparate implementations of protocols is what we will use going forward. This has created a tremendous workload because there are now many different channels through which bugs and updates must be handled.

In this situation a volunteer development community must rely on every work saving tool they can just to keep up. For the person in the trenches there is no alternative.

If you prioritize quality as measured by the extent to which your software supports the various Wayland doohickies or security as measured by active exploitable bugs, you have to use llms.

These conditions will eventually remove the structure of incentives for open source development.

None of the above is a value judgement.

the reason I didnt address anything you asked earlier is because I don’t think people generally need this crap and it’s probably a mistake for me to have explained how a person can make semi decent decisions about rolling their own.

Ram doesn’t matter. You can buy more, yes even when it’s expensive. The reason it doesn’t matter if that your needs will vary wildly based on your workload. I don’t know your workload so I can’t recommend an amount of ram. Maybe start with 16gb for a few cameras and a zpool based storage.

You want an old server because consumer hardware has no pcie lanes and is in general designed around a short duty cycle which is how you get such great “efficiency” numbers out of consumer equipment compared to a computer designed to reliably run 24/7. Of course your computer isn’t using any electricity, it’s not fucking doing anything.

The os doesn’t actually matter. Just use whatever you can keep running reliably. If you need to ask what you can keep running reliably then buy an off the shelf solution.

Don’t use proxmox or some hypervisor. The whole point isn’t to have a cool hackerman surveillance room with a bunch of screens like in the movies, it’s to have a reliable record of what your cameras captured. Fewer things to fail is better.

If you need to ask if a raspberry pi is appropriate then a raspberry pi is not appropriate. That’s true in all situations but here’s why it’s true here: you would only use a sbc for this application because you either don’t have anything else or you’re worried about energy consumption. If you don’t have anything else then it doesn’t matter if it’s a smart choice and if you’re worried about energy consumption then you’re not factoring in the energy cost of maintaining a place for a human being to exist and look at the screens attached to the pi or you havent considered simply turning off the terminal when it’s not in use.

Don’t do an ip camera based security system as a learning experience. What you will learn is that it was a big waste of time and isn’t practical.

I would recommend you think critically about what you’re trying to accomplish first and foremost then implement the simplest system that has the fewest points of failure.

Apologies for the account change, credential rolling schedule waits for no man.

Yes, it’s device firmware.

Again, if you would like a more practical approach based on the experience of being robbed I will gladly volunteer it.

Yes. It all works by default. The ones you want to use for a cache device are m10, they come in 16, 32 and 64gb sizes.