Date: Fri, 1 Feb 2008 07:18:27 -0800 From: Garrett Cooper <yanegomi@gmail.com> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: hackers@freebsd.org Subject: Re: vmstat layout Message-ID: <E02086F1-AB42-4C74-862C-AE981AC44C81@u.washington.edu> In-Reply-To: <86k5lovrwj.fsf@ds4.des.no> References: <86k5lovrwj.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 1, 2008, at 3:26 AM, Dag-Erling Sm=F8rgrav wrote: > vmstat(1) tries very hard to fit everything in 80 columns. > > Unfortunately, it's been years since anyone had a machine where none =20= > of > the columns overflowed. [...] > Removing columns is not an acceptable solution (it would break too =20 > many > existing scripts), so I'm afraid we're going to have to make the =20 > output > wider than 80 columns, unless someone can come up with a better =20 > solution. > > DES What about multiline entries with indentation to group fields for =20 "human readable output"? For example... procs memory page =20 disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad1 ad2 ad3 ad10 =20= ad12 in sy cs us sy id 2 1 0 193M 1015M 444 2 8 0 4862 0 0 0 0 0 0 =20= 0 348 1297 4704 1 7 92 ...may become something like... field_title_0 field_title_1 field_title_2 [subfields go here] [...] [...] field_title_3 [...] = field_title_n [...] [...] = [...] Does that make sense? Cheers, -Garrett=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E02086F1-AB42-4C74-862C-AE981AC44C81>