-
Overview
-
redpesk OS releases
-
Security updates
- Security CVE / errata
- CVE quick look
-
Redpesk OS Tips and Tricks
-
Application Framework Manager
-
Application Framework Binder
-
APIs & Services
-
Security manager
-
OP-TEE within redpesk
-
Trusted Boot
-
Recovery features
-
redpak
-
Minimal image
- Reduce image size
- Optimizing boot time
-
Kernel fragments description
- Introduction to Linux Kernel Configuration
- 01 Disable IPC, Timers and Audit
- 02 Disable Kconfig, Scheduler and Initrd
- 03 Disable Perf, Profiling and Errata
- 04 Disable EFI, Power Management Debug and Energy Model
- 05 Disable Schedutil, CPUFreq Governors and Virtualization
- 06 Disable Kprobes and Jump Labels
- 07 Disable GCC Plugins and Function Alignment
- 08 Disable Partition Parsers
- 09 Enable Inline Spinlocks and Kernel Operations
- 10 Disable Swap, Memory Hotplug and KSM
- 11 Disable Networking IPv4, IPv6, Netfilter
- 12 Disable SCTP, VLAN, TIPC, BATMAN
- 13 Disable Wireless, Bluetooth, CAN and RFKILL
- 14 Disable PCI and Firmware
- 15 Disable GNSS and ProcEvents
- 16 Disable Block Storage NBD and AoE
- 17 Disable EEPROM and Misc Drivers
- 18 Disable Network Device Drivers
- 19 Disable PHY Drivers
- 20 Disable PPP, WLAN Coexistence, and Failover
- 21 Disable Input Devices
- 22 Disable Serial, TTY and TPM
- 23 Disable I2C, Power and Sensor Drivers
- 24 Disable MFD, Display and Media Drivers
- 25 Disable USB, Sound, RTC and VirtIO
- 26 Disable Filesystem Encodings and Compatibility
- 27 Enable Minimal Cryptographic Core with SHA3 and XTS
- 28 Disable Hardware Cryptography, Keep DRBG and Jitter Entropy
- 29 Disable Kernel Debugging Features
- 30 Disable Filesystem Verity and SecurityFS
-
Zephyr in Redpesk
-
PERM-CHECK extension
-
Mender redpesk (OTA)
-
Hardware support
- Download images
- Image metrics
- Trusted Boot
- Boards - ARM64
- Boards - x86_64
- Boards - Virtual
- Miscs
-
Building microservices natively within SDK container
-
Building microservices and framework from sources
Environment
Package repositories
Each SDK container shares the same package repositories as a redpesk image.
For example in a corn-3.0-update SDK container:
sh-5.2$ dnf repolist
repo id repo name
epel Extra Packages for Enterprise Linux corn - x86_64
redpesk-baseos-update RedPesk Baseos corn-3.0 Update - x86_64
redpesk-config RedPesk Config
redpesk-middleware-update RedPesk Middleware corn-3.0 Update - x86_64
redpesk-third-party RedPesk Third Party corn-3.0 Update - x86_64
Any packages available in the redpesk OS version your SDK container is linked to can be installed.
sh-5.2$ dnf info afb-binder
RedPesk Middleware corn-3.0 Update - x86_64 187 kB/s | 36 kB 00:00
RedPesk Baseos corn-3.0 Update - x86_64 8.9 MB/s | 3.5 MB 00:00
Extra Packages for Enterprise Linux corn - x86_64 15 MB/s | 6.8 MB 00:00
RedPesk Config 3.6 kB/s | 639 B 00:00
RedPesk Third Party corn-3.0 Update - x86_64 753 kB/s | 240 kB 00:00
Installed Packages
Name : afb-binder
Version : 5.3.1
Release : 44.redpesk.core.rpcorn
Architecture : x86_64
Size : 73 k
Source : afb-binder-5.3.1-44.redpesk.core.rpcorn.src.rpm
Repository : @System
From repo : redpesk-middleware-update
Summary : Application framework binder
URL : https://github.com/redpesk-core/afb-binder
License : GPL-3.0-only
Description : The application framework binder
Integrated Development Environment
Both SDK can be used with integrated development environment.
SDK core
You can easily connect the SDK core container with an IDE as long as it handled remote development.
For example, using vscode, install the ms-vscode-remote.remote-containers extension.
SDK openvscode-server
An openvscode-server is runing in the SDK, and accessible on port 3000 from your host.
