SShortSingh.
Back to feed

Beginner Documents Linux, Bash Scripting, Cron Jobs, and Networking Fundamentals

0
·1 views

A self-taught learner has published personal study notes covering foundational topics in Linux, Bash scripting, task scheduling, and computer networking. The notes detail hands-on steps such as installing Ubuntu, renaming a terminal hostname, and writing a first Bash script using a shebang line and basic commands. Key scripting concepts documented include variables, loops, conditional case statements, file redirection, and using chmod to make scripts executable. The learner also outlined how cron jobs work, including the five-field time syntax and commands like crontab -e and crontab -l for managing scheduled tasks. Networking basics such as MAC addresses, CSMA, bandwidth, exponential backoff, and collision domains were also noted as part of the study session.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

GitHub's pull_request_target changes will break workflows in 27% of top repos by November

GitHub is rolling out two breaking changes to its pull_request_target Actions trigger, with a key deadline on November 2, 2026, when the trigger will be blocked on public repositories lacking an explicit Actions policy. A scan of the 1,000 most-starred GitHub repositories conducted on September 26, 2026 found that 269 of them run at least one workflow using the affected trigger, putting those workflows at risk of silently stopping. Since July 20, 2026, the actions/checkout action also refuses to check out fork pull request code in privileged workflows unless maintainers explicitly opt in. More critically, three repositories were found using an older, unpatched version of actions/checkout that bypasses the new guard, potentially exposing workflow tokens and secrets to fork code. A free open-source tool called prt-check has been released to help repository maintainers audit their own workflows for these vulnerabilities.

0
ProgrammingDEV Community ·

Developer shares human-led AI workflow to build apps from idea to working API

A developer has published a detailed guide demonstrating how to build software applications using AI tools without producing low-quality, unreliable output. The workflow was tested through a demo project called Orbit, a Slack-style team chat app, built with assistance from ChatGPT, Claude, and Grok. The process involved setting clear requirements, reviewing AI-generated changes at each stage, and deriving an API only after the user interface behavior was accepted. The author emphasizes that AI cannot self-certify code as production-ready, and that human oversight at every handoff is essential to useful results. Orbit itself remains a limited demo with no authentication, shared public data, and no persistent storage across restarts.

0
ProgrammingDEV Community ·

Developer Builds AI Smart TV OS on AWS After Tackling Vega OS Compatibility Hurdles

A developer building Vid30, a self-described AI Streaming Operating System for Smart TVs, documented the first sprint of their public build journey on DEV Community. Despite warnings that Vega OS development is designed for Linux and macOS environments, they chose to proceed using an Ubuntu EC2 instance on AWS as a remote development environment. Using Kiro as an AI-assisted IDE, they successfully forked Amazon's React Native Multi-TV starter project and learned the Vega SDK from scratch, encountering multiple issues along the way including Git, Yarn, Metro, and SDK compatibility problems. The developer resolved most obstacles but hit a final blocker in the Vega simulator workflow, publicly asking the Fire TV and Vega developer community for help. They are also seeking a physical Fire TV Stick from Amazon to test Vid30 on real hardware, framing the experience as a lesson in knowing when to pivot rather than pursuing every problem to completion.

0
ProgrammingDEV Community ·

System Prompts Are Not Guardrails: Why AI Agent Safety Needs External Controls

Developers commonly place safety rules for coding agents inside system prompts, but this approach offers weaker protection than it appears. System prompts share the same channel as user messages and tool outputs, making policy rules vulnerable to being overridden, forgotten, or reinterpreted by the model. Unlike external controls, prompt-based rules are difficult to version, test on a subset of agents, or roll back quickly when something goes wrong. They also leave poor audit trails, making it hard to diagnose exactly which control failed after an incident. Experts recommend moving hard limits into external enforcement layers — such as tool allowlists, scoped credentials, and gated approval steps — while reserving the system prompt for style and reasoning guidance only.

Beginner Documents Linux, Bash Scripting, Cron Jobs, and Networking Fundamentals · ShortSingh