I assume that the format of the ifconfig -a output will always be the same; that is, interface followed by interface information. If that is the case, then the following code sample will work for you. NOTE:
1) the output of ifconfig -a has been stored in a file
2) the interface information is stored in a hash where the interface name is the key and its status is the value.

#!/usr/bin/perl
use strict;

my ($if, %hash, $key);
open(FILE, "<f.txt");

while(<FILE>) {
    chomp $_;
    ($if = $_) =~ s/^(\w+?):.+/$1/ if $_ =~ m/^\w+:/;
    ($hash{$if} = $_) =~ s/.+status:\s+(.+)/$1/ if $_ =~ m/status/;
}

close(FILE);

foreach $key (keys %hash) {
    print "$key: $hash{$key}\n";
}

exit;

[download]
hope this helps,
davidj

In reply to Re: Need help to parse the text by davidj
in thread Need help to parse the text by GS

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.