SShortSingh.
Back to feed

Linux Fundamentals for Terminal Work: Permissions, Processes, and Essential Tools

0
·2 views

A DevOps write-up argues that learning Linux basics is not a throwaway prerequisite, since tools like Docker, Kubernetes, and Terraform all run on Linux underneath. The article centers on file permissions, explaining how the permission string in ls -l encodes read, write, and execute rights for the owner, group, and others. It walks through numeric chmod notation, showing how r, w, and x map to values of 4, 2, and 1 to build common modes such as 755 and 644. It also covers chown and chgrp for changing ownership, and contrasts sudo, which elevates a single command, with su, which switches the whole 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 ·

Shifting from overconfidence to systems that protect everyday digital life

The eighth installment of a series on cybercrime argues that ordinary people, not only the careless, are targeted through everyday tools like email, routers, apps, and cloud services. It notes that relying on constant vigilance is unrealistic, since busy or tired users can be fooled and attackers exploit trusted services and routine systems. The article points to IPA's 2026 Top 10 threat lists, which cover ransomware, supply-chain attacks, account theft, and phishing for both organizations and individuals. It recommends structural safeguards such as multi-factor authentication or passkeys, timely updates, tested backups kept separate from live systems, and removing access for departed staff. It also points to IPA's 2026 small-business guidelines and a basic six-point checklist that can be adopted step by step.

0
ProgrammingDEV Community ·

API Error Returned as Successful Temporal Workflow Result in Agent Examples

A developer building a Temporal-backed agent discovered that a truncated API key triggering an authentication error caused a Workflow to finish successfully. The affected examples, which used the Claude Agent SDK through Temporal's integration, returned the message text without first checking the is_error flag, so Temporal treated the error string as a normal return value. In one structured-output case, the failure instead surfaced as a misleading missing-output error that obscured the real authentication problem. The developer extended an offline test fixture to simulate HTTP 401 responses and confirmed that nine of ten cases mishandled the error before the fix. The corrected handler now checks is_error first and raises a Temporal ApplicationError, though the fix does not determine whether such failures should be retried.

0
ProgrammingDEV Community ·

Designing SMS OTP Verification to Gate Release of Sensitive Report Attachments

The article argues that sending a marketplace settlement report by email should depend on a verified authorization decision, not merely on an SMS being accepted or delivered. It recommends a Node.js implementation with a server-owned challenge record, server-side expiry enforcement, and an atomic single-use transition. Authentication success and attachment delivery are to be tracked as separate outcomes, with report release recorded durably. The piece also promotes the Infrai API as a unified vendor for SMS and email with one credential and one bill, while stating that it establishes no authentication or delivery service-level objectives.

0
ProgrammingDEV Community ·

Rail operator's AI platform links fault histories across two builders without copying their data

A passenger rail operator in Saudi Arabia runs mixed trainsets from two builders, but door faults and maintenance records sit in separate systems that cannot be joined cleanly. The engineering team has published an open reference architecture that projects data from the existing systems of record rather than copying or migrating it. Source systems are read only, and the only write path goes into the model's own case and draft objects. The platform is advisory and stays outside the safety case, though its introduction is filed under the operator's safety management system before any contract-facing output goes live. Fleet and passenger data stay on the operator's network, and no third-party model service is used.