Hi,
When I try to get the date of 2012-10-21:
root@cidLogin:~#
date -d 20121021
date: invalid date `20121021'
Is this a bug? The
result is the same both in Opensuse Tumbleweed and Ubuntu 12.04.
Thanks and sorry for disturbing,
Danilo Luvizotto
Dears
Could we print values to be as three column ,each column present the values of
each file.
More explanation :
I have three files ,each file include a queue of values .I need to print all
the values by one command to be in one page
Thanks
[cid:image001.jpg@01CDECEE.BDCB6ED0]
www.stc.
tag 13388 notabug
thanks
On 01/08/2013 06:02 AM, dan...@controlid.com.br wrote:
>
>
> Hi,
>
> When I try to get the date of 2012-10-21:
>
> root@cidLogin:~#
> date -d 20121021
>
> date: invalid date `20121021'
>
> Is this a bug?
No. It is a factor of daylight savings in your timezo
tag 13389 notabug
thanks
On 01/08/2013 06:57 AM, Mohanad Azzam wrote:
> Dears
>
> Could we print values to be as three column ,each column present the values
> of each file.
>
> More explanation :
> I have three files ,each file include a queue of values .I need to print all
> the values by on
tag 13389 notabug
thanks
On 01/07/2013 10:57 PM, Mohanad Azzam wrote:
> Dears
>
> Could we print values to be as three column ,each column present the values
> of each file.
>
> More explanation :
> I have three files ,each file include a queue of values .I need to print all
> the values by on
On Tue, 2013-01-08 at 10:50 -0700, Eric Blake wrote:
> tag 13389 notabug
> thanks
>
> On 01/07/2013 10:57 PM, Mohanad Azzam wrote:
> > Dears
> >
> > Could we print values to be as three column ,each column present the values
> > of each file.
> >
> > More explanation :
> > I have three files ,e
On 01/08/2013 11:05 AM, Ondrej Vasik wrote:
>> $ join <(join <(cat -n one) <(cat -n two)) <(cat -n three) |\
>>sed 's/^[0-9]* *//'
>> 1 a x
>> 2 b y
>> 3 c z
>>
>> There's probably other ways of doing it, as well.
>
> Actually,
> pr -m -t -s' ' one two three
> seems to be easier to me for thi
On Tue, 2013-01-08 at 11:09 -0700, Eric Blake wrote:
> On 01/08/2013 11:05 AM, Ondrej Vasik wrote:
>
> >> $ join <(join <(cat -n one) <(cat -n two)) <(cat -n three) |\
> >>sed 's/^[0-9]* *//'
> >> 1 a x
> >> 2 b y
> >> 3 c z
> >>
> >> There's probably other ways of doing it, as well.
> >
> >
Hi all,
While trying to diagnose a weird filesystem bug, I found an error in GNU dd
v8.12.
The weird bug is causing lseek() to fail improperly. That's not the problem
I'm reporting, though. I was trying to use dd to demonstrate the lseek
error to my sysadmin. Instead, I found that dd is ignoring
On 01/08/13 10:11, Neil Klopfenstein wrote:
> Note that it begins reading at the _beginning of the ar file_ -- the 'skip'
> argument has failed silently.
But the 'skip' hasn't failed. It's merely being implemented via 'read'
rather than via 'lseek'. The records are being skipped correctly.
It m
On 01/08/2013 08:55 PM, Paul Eggert wrote:
On 01/08/13 10:11, Neil Klopfenstein wrote:
Note that it begins reading at the _beginning of the ar file_ -- the 'skip'
argument has failed silently.
But the 'skip' hasn't failed. It's merely being implemented via 'read'
rather than via 'lseek'. The
On 01/08/2013 05:14 PM, Pádraig Brady wrote:
> Worth applying the attached?
Looks good, except I would avoid calling lseek on
STDOUT_FILENO unless oflag=seekable is set. Just being
conservative: the effect of lseek on unseekable files is
implementation-defined.
Hi,
On Wed, Jan 09, 2013 at 01:14:22AM +, Pádraig Brady wrote:
> On 01/08/2013 08:55 PM, Paul Eggert wrote:
>> On 01/08/13 10:11, Neil Klopfenstein wrote:
>>> Note that it begins reading at the _beginning of the ar file_ -- the 'skip'
>>> argument has failed silently.
>>
>> But the 'skip' hasn
On 01/09/2013 02:14 AM, Pádraig Brady wrote:
> I had a look around for a tool to verify
> that a file/device supports the seek operation
> and couldn't find one.
> So this seems like useful functionality.
> Worth applying the attached?
> * cfg.mk (sc_dd_O_FLAGS): Add O_SEEKABLE to the list of pr
14 matches
Mail list logo
