linuxlab.io
Tutorials▾
  • Linux & networking
    File system, processes, TCP/IP, BGP and OSPF
    →
  • Terraform & IaC
    HCL, state, plan/apply on a LocalStack sandbox
    →
  • Git & GitHub
    Object model, plumbing, branching, GitHub Actions
    →
All tutorials →
PricingAboutSign inCreate account
/
  • Введение
  • Уроки
  • How it works
  • Симулятор
  • База знаний
  • Собеседование
Lessons
Footer
linuxlab-TutorialsPricingAboutPrivacy & cookies
Copyright © 2026 LinuxLab. All rights reserved.

← из прошлого урока

You saw that a file is an inode behind a name, and that a hard link and a symlink do different things. Next: how to make commands talk to each other through stdin/stdout, and how to write straight to a file instead of the screen.

← к прошлому уроку

Базовый

Pipes and redirects: connecting commands

12 мин · урок входит в курс «Базовый»

The core idea of the Unix shell is to connect simple commands into chains. Each command (its own process-and-pid) reads from stdin, writes to stdout, and sends errors to stderr. You can redirect these streams into each other and into files.

Урок закрыт

Чтобы запустить sandbox и пройти этот урок целиком, нужен соответствующий курс. Внутри - ещё много практических уроков того же уровня и сквозной прогресс.

Купить курсВойти← Все уроки

дальше →

You just learned to assemble commands into a pipeline and send their output to files. The natural next question is who is even allowed to read and write those files. That is what we tackle next.

Открыть превью: Permissions: rwx and chmodв курсе «Базовый» - /pricing
Footer
linuxlab-
Copyright © 2026 LinuxLab. All rights reserved.
Tutorials
Pricing
About
Privacy & cookies