It's Saturday A.M, so please forgive me. On Fri, 2008-03-07 at 10:54 -0500, Filipe Brandenburger wrote: > On Fri, Mar 7, 2008 at 10:35 AM, Jerry Geis <geisj@xxxxxxxxxxxxxxx> wrote: > > If /proc/cmdline looks like > > > > option1 option2 ... ks=http://192.168.1.8/ks/ks.cfg option3 option 4 ... > > > > How can I get the 192.168.1.8 out of this cmdline. A 12 gage shotgun ought to get the job done! > > Cryptic but does the job: > <snip> Seriously, by the time I got to this thread, answers had flowed like river water, so that left only my perverse sense of humor in play. -- Bill _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: parsing /proc/cmdline
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS General List <centos@xxxxxxxxxx>
- Subject: Re: parsing /proc/cmdline
- From: "William L. Maltby" <CentOS4Bill@xxxxxxxxxxxx>
- Date: Sat, 08 Mar 2008 07:06:04 -0500
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <e814db780803070754t5be640ffsd4eaed33f3b0963d@xxxxxxxxxxxxxx>
- References: <47D160A7.7060909@xxxxxxxxxxxxxxx> <e814db780803070754t5be640ffsd4eaed33f3b0963d@xxxxxxxxxxxxxx>
- References:
- parsing /proc/cmdline
- From: Jerry Geis
- Re: parsing /proc/cmdline
- From: Filipe Brandenburger
- parsing /proc/cmdline
- Prev by Date: pdflatex: fuzzy fonts in Evince, but not on paper output
- Next by Date: Re: Unable open raw socket in CentOS 5 - SE Linux andkernelcapability interaction?
- Previous by thread: Re: parsing /proc/cmdline
- Next by thread: Re: parsing /proc/cmdline
- Index(es):
 |