do corporaresearch with any kinds of "texts".
lbrtchx
virtual machine. I would stress test using Windows
Subsystemfor Linux just fine. I like the java on Linux environment.
Would HP let youaccess their BIOS setup, memory card, ... within Linux?
How do you dealwith such "secure BIOS" nonsense?
lbrtchx
"${_URLs}"
but in this way youstart an instance every time. I need to:
1) open a number oftabs at once;
2) once I close thelast one ff should clear the cache or shut down and re start
It shouldn't be sohard, but I haven't figured it out yet.
lbrtchx
en
_UTIL="${_L_AR[1]}"
#
which "${_UTIL}"
"${_UTIL}"${_L_AR[2]} 2>&1 | head -n ${_L_AR[3]}
# _V=${_L_AR[4]};"${_UTIL}" ${_L_AR[2]} 2>&1 | head -n ${_L_AR[3]} |awk '{print
$'${_V}'}' # can't get the version ..
else
echo "// __\$_L: |${_L}|, \$_L_ARL: |$_L_ARL|"
fi
~
lbrtchx
MSS|00:19:09|, seconds=1149
// __ $_HHMMSS|00:19:08|, seconds=1148
// __ $_HHMMSS|19:09|, seconds=68940
// __ $_HHMMSS|19:08|, seconds=68880
$
~
I will have to go over, learn from Greg's reply when I get the chance. I still
think that there should be a way to make what I need straight forward using
date's own formatting.
lbrtchx
_HHMMSS="19:09" means 19*60 + 9 = 1149 seconds
_HHMMSS="19:08" means 19*60 + 8 = 1148 seconds
so, it seems date is also somehow parsing that value as octal even though it is
being formatted in a date friendly way. is there a way to exactly specify the
encoding of the input for date?
OK, it makes some more sense now. The range of digits in the octal system is
from 0 to 7, so it would complain with "08" and "09" (but not with "10" which
would then be "8" in octal), but why would command line utilities assume you
are encoding numeric values as octal? Now I notice many people h
: _SEKNDS + 08: value too great for base (error token is "08")
~
yet, it works for _HHMMSS={"3:54:14", "20:01", "20:00", "19:07", "19:06",
"19:05", ... } and all other similar conversion?!
lbrtchx
8 matches
Mail list logo
