Linux

55731 readers

997 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

[email protected]

regex and awk... (programming.dev)

submitted 3 weeks ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

cross-posted from: https://programming.dev/post/31833654

Hi,

I would like to found a regex match in a stdout

stdout
 /dev/loop0: [2081]:64 (/a/path/to/afile.dat)
I would like to match
/dev\/loop\d/
and return /dev/loop0

but the \d seem not working with awk ... ?

How to achieve this ? ( awk is not mandatory )

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 5 points 3 weeks ago (4 children)

Not sure if I'm understanding, but can't you just pipe the whole thing to awk and capture the first field? Like

echo "/dev/loop0: [2081]:64 (/a/path/to/afile.dat)" | awk -F: '{print $1}'

Which would print

/dev/loop0

[–] [email protected] 0 points 2 weeks ago* (last edited 2 weeks ago) (3 children)

That would also print the colon

Edit: missed the separator token. Sorry guys

[–] [email protected] 3 points 2 weeks ago

No, because we're telling to use : as a separator with the -F flag

load more comments (2 replies)