/explore
|
You are here 
|
sanchayanmaity.net | ||
| | | | |
www.collabora.com
|
|
| | | | | An in-depth look at WirePlumber, the modular and extensible session manager for PipeWire | |
| | | | |
nyanpasu64.gitlab.io
|
|
| | | | | Adventures in programming, hardware, DSP, and chiptune | |
| | | | |
golb.hplar.ch
|
|
| | | | | [AI summary] This tutorial walks through setting up a serverless application using AWS services. The main components are an API Gateway, a Lambda function, and a DynamoDB table. The Lambda handles CRUD operations for todo items, while the API Gateway provides the HTTP endpoints. The application is deployed using Pulumi, which manages the infrastructure as code. The tutorial also covers setting up IAM roles for Lambda execution, configuring permissions for API Gateway to invoke Lambda, and deploying the Lambda with ARM64 architecture to reduce costs. Finally, the tutorial demonstrates how to start the client application and test the functionality. | |
| | | | |
www.kroah.com
|
|
| | | Note This post is based on a whitepaper I wrote at the beginning of 2016 to be used to help many different companies understand the Linux kernel release model and encourage them to start taking the LTS stable updates more often. I then used it as a basis of a presentation I gave at the Linux Recipes conference in September 2017 which can be seen here. With the recent craziness of Meltdown and Spectre , I've seen lots of things written about how Linux is released and how we handle handles security patches that are totally incorrect, so I figured it is time to dust off the text, update it in a few places, and publish this here for everyone to benefit from. | ||
