Sebastien Andre wrote:
Bob Proulx wrote:
I have added a tip to the date faq entry. It hasn't been an faq but
but seemed useful just the same.
For those interested by an implementation of this technique,
a shell script is available at
http://scriptutils.svn.sourceforge.net/viewvc
Jason Pepas wrote:
#!/usr/bin/env FOO=buzz bash
This looks very suspicious to me. You are trying to pass *two*
arguments on the #! line. If that worked it would be quite
unportable. Different kernels deal with that differently. I would
fully expect that both of those second arguments would
Tom Trauth wrote:
Is it absolutely essential? Probably not, especially in shell scripts. But
when typing at the command line, I think it's a great convenience. I'd much
rather type ls -lM or du -sM than ls -l --si or du -s --si, though
the latter aren't particularly long either. And I
Rob Gom wrote:
this is my first post to this list, which I think is the best place to
ask. I have searched web, but couldn't found an answer.
Yes. This is a great place to discuss coreutils issues. The
coreutils mailing list is for general discussion. The bug-coreutils
mailing list is
Rob Gom wrote:
Bob Proulx wrote:
And the last one copied wins? Okay.
Well, that's not the case. There's make called. Make spawns some
submakes. Every submake calls target which copies files (--parents
--update).
Every submake has its own files list, so only one cp is handling any
given
Jan Girke wrote:
can somebody deposit that info in the man page for ls
{
ls
dir
List the content of the current directory. The command dir is an alias
to ls so this two commands do exactly the same thing.
But dir isn't the same thing as ls. Saying that it is the same thing
is incorrect.
Philipp Thomas wrote:
Eric Blake wrote:
(using d2u on the checksum file before handing it to md5sum is usually a
decent workaround to having to teach md5sum about alternate line endings).
That's what the person who asked is doing atm.
While dos2unix isn't always available I would also
Rakib Mullick wrote:
Yes, right. Then, touch only supposed to change file's timestamp. No?
But, touch also creates a file for us. Not only it creates a file for
us, when it creates a file it takes reference from other files.
Yes. That is what touch does.
So, althrough we're in philosophy of
Melikamp T. Medley wrote:
I think I want to write a utility that prints pseudo-random
integers (I have in CL, but I like it fast, so this time in C),
I am confused by the connection of using the shell on one hand and by
saying you need speed on the other. The shell is quite fast and good
Melikamp The Medley wrote:
You seem to be implying that I am suggesting that my yet to be written
code is to be added to coreutils. I don't believe I gave out that
impression.
I am sorry if I misunderstood but you said this:
I think I want to write a utility that prints pseudo-random
Melikamp The Medley wrote:
Bob Proulx wrote:
People are often writing to the mailing list asking to include their
code in coreutils. I believe that is the same impression
that everyone else had too.
I don't believe you can guess what other people are thinking with
any kind of certainty
Adam Sjøgren wrote:
I often have programs that output stuff I would like have logged with
timestamps, but they don't print timestamps themselves. I have been
using various shell-scripts/hacks calling date(1) to wrap them.
I think it would be really great to be able to just go:
$
e-letter wrote:
I have tried to copy base64 encoded text from the clipboard (i.e. a
web mail message) to the command terminal:
base64 -d 'xyz'
where 'xyz' is the base64 text. According to the manual, standard
input can be accepted if a file is not accepted but instead the
terminal
e-letter wrote:
I wrote 'xyz' not as literal, verbatim encoded text but as an example.
But your example displayed the output from base64 that corresponded
exactly to literally giving it xyz as input. We only know what you
are doing from the data you show us. Therefore literal and verbatim
is
Jim Meyering wrote:
Bob Proulx wrote:
Jim Meyering wrote:
For minimal overhead ls, use only the -1U options.
I.e., type exactly this:
env ls -1U
What benefit is provided by invoking through 'env' in that example
without any environment modifications specified? I am sure I am
scott n-h wrote:
-I or --ip-address
I'm hoping the usefulness of this would be apparent.
The coreutils manual:
http://www.gnu.org/software/coreutils/manual/html_node/sort-invocation.html#sort-invocation
Shows an example of sorting IPv4 addresses this way:
sort -s -t. -k 1,1n -k 2,2n -k
Diogo Sousa wrote:
One feature that some users search for is a progress bar on the cp program.
I would like to implement a progress bar in cp, would that patch be
accepted? Is there any reason not to do it?
If cp had every feature of rsync then it would be rsync.
$ ls -ldogh /bin/cp
tags 9460 + notabug
close 9460
thanks
Since this isn't a bug but rather discussion I am closing this bug
ticket, CC'ing the discussion line, and directing follow-ups there.
Gregory Dancker wrote:
Can this be used with a hex input file?
What would the input file look like?
I tried a simple
e-letter wrote:
Eric Blake wrote:
Common convention among many unix tools is to treat '-' as a synonym for
stdin. I don't know if 'info tar' explicitly calls this out, though
that would be a question for bug-tar.
Couldn't find explanation in 'man tar' and after a few years, have yet
to
Peng Yu wrote:
would you care to submit a patch?
I have finished relpath.c. When I push it (after commit), I get the
following error. I'm new to git. Does anybody know what the problem
is? And how to get my patch to the central git repository?
~/coreutils$ git push
fatal: The remote end
Bjartur Thorlacius wrote:
Paul Eggert wrote:
+ /* On GNU/Hurd hosts, getuid etc. can fail and return -1.
+ However, on GNU/Linux hosts, uid_t is an unsigned value and
+ getuid etc. can return the positive value (uid_t) -1. To
+ handle both cases correctly,
Jim Meyering wrote:
Eric Blake wrote:
Also, I tend to see etc. used primarily in the context of a list, when
at least two items have already been given (so that it is more obvious
what similar items have been omitted from the list). It's hard to see
what similar functions are implied
Jim Meyering wrote:
The point is that the separation is not clear.
Even /sbin programs like mkfs.* can be useful to non-root users.
I use a few of those in parted tests.
Also, ifconfig is useful to non-root users, yet resides in /sbin.
I am sure that you like me always add
Erik Auerswald wrote:
Bernhard Voelker wrote:
Bob Proulx wrote:
I am sure that you like me always add /usr/local/sbin:/usr/sbin:/sbin
to your PATH as a normal non-root user. This shields us from most of
those problems. And sometimes hides the problem.
That is what I do as well
Pádraig Brady wrote:
Eric Blake wrote:
Amr Ali wrote:
I'm not sure if this was discussed before, but I've got tired
from having to work around the lack of native recursion within
`shred`. So, attached is a patch to add recursion, including
documentation.
Thanks for taking the
Peng Yu wrote:
man mktemp says Create a temporary file or directory, safely, and
print its name.
I'm wondering what it means by safely.
Does mktemp test if there is already a tempfile with the given name?
If there is indeed with the same file name, will mktemp use a
different name rather
Francois Marier wrote:
Pádraig Brady wrote:
p.s. There is no need to specify count if write to the whole device.
Also bs=1M might be faster.
That's good to know. So I guess I should have done this:
dd if=/dev/zero of=/dev/sda bs=1M
Yes. That would be just fine. I never include the
Francky Leyn wrote:
Dear Bob,
thanks for your intervention.
The problem is a lot clearer to me right now.
It is indead a Virtual Box on top of Windows 7 with an NTFS system
and the Linux virtual box is Ubuntu 11.04.
NTFS doesn't have any concept of the same file modes as a Unix-like
francky.l...@telenet.be wrote:
some more questions.
I abstract a file system as something where each dir/file has a header
where all properties reside.
Yes. This information is stored in the Inode. You can read about it here.
http://en.wikipedia.org/wiki/Inode
There doesn't exist a
Jim Meyering wrote:
Here's a little bash/zsh script that does it:
Much of the time find can do this nicely. Of course this may do more
than the posted script but often the difference isn't important in the
provided context of creating new directories and installing new files
into those new
Glenn Morris wrote:
I should have checked debbug's exim log first:
2012-03-01 13:23:32 [29132] 1S3Aeb-0007Zr-Op ** bug-coreut...@gnu.org
F=debian-debb...@debbugs.gnu.org P=debian-debb...@debbugs.gnu.org
R=dnslookup T=remote_smtp: SMTP error from remote mail server after
end of data: host
e-letter wrote:
File 1 contains data:
/some/text/abcd.xyz
File 2:
abcd.xyz
The manual does not seem to indicate that regular expressions can be
used with 'comm'.
They can't be. It doesn't make sense for comm. Perhaps you should be
using 'grep' or 'sed'?
The task is to be able to
e-letter wrote:
Bob Proulx wrote:
Sounds like a homework assignment.
Well, my own assignment in my own home (managing files)!
Okay then. You can imagine that a lot of students try to short
circuit things!
They can't be. It doesn't make sense for comm. Perhaps you should be
using
Quinton Dunning wrote:
Sometimes when I execute the split command I want to use removable
media and take a file part over to another machine. To do this, the
split command would have to have a switch that would pause and wait
for a keystroke before writing the next file.
I remember having
Davide Brini wrote:
igro...@gmail.com wrote:
Just a suggestion that it woild be good
idea to have speed limit in dd tool
so one can use it to for example
spare network bandwidth when copying file
...
You can use a tool named pv (available in all the distros I've worked
with) to
Pádraig Brady wrote:
Thinking a bit more about this, as I see it:
/tmp = stateless
/var/tmp = stateful
Yes. Because /tmp is typically cleared on a reboot. But reboots are
either scheduled regularly *or* never scheduled and can be quite few
and far between. But that is a different
Robert Milasan wrote:
Hello, I think I found an issue, but not sure if it's a bug or
feature :)
That is always the hardest question! :-)
When using option -c from tail there are 3 ways, two working and one
not:
1. cat /etc/passwd|tail -c 10 (doesn't work)
2. cat /etc/passwd|tail -c -10
Ivan Korotkov wrote:
this is an enhancement proposal to use sendfile instead of read/write loop
in cp(1) on Linux 2.6.33 and above to speed up copying. WDYT?
The feature is very new. It think it is too new to use in a coreutils
command like cp. For anyone who uses a single binary on multiple
Just an FYI for frequent bug tracking system users...
Glenn Morris made a nice improvement to the Mail-Followup-To header
that is added to the closed bug email. The closed bug email includes
a MFT header to keep follow-ups from going to the -done address and
closing a possibly later reopened
Raphael S Carvalho wrote:
So what do you think? Which language should I use? I'm going to sleep
in few minutes, so I would get started tomorrow.
As Bernhard Voelker we could create a C program which would use those
tools (mv, cp, ln).
It would be hard to object to a C program. But this is
sreekanth dhulipalla wrote:
when iam trying to install the apache 2.2.23 in my linux pc i get the below
error?
You have reached the GNU Coreutils mailing list. The GNU Coreutils
are the basic file, shell and text manipulation utilities of the GNU
Operating System. You can learn more about GNU
sreekanth dhulipalla wrote:
This is the error iam getting when iam run the command ./startadmin.sh
startadmin.sh is an executable file when iam trying to run it shows the
below error
You have reached the GNU Coreutils mailing list. The GNU Coreutils
are the basic file, shell and text
I figure I better give a report on the usage.
I have been seeing people use -1 to refer to the current bug in the
upstream BTS. If the control message has the bug number in the
subject then it can extract the number from it and it doesn't need to
be included in the command. Seemed very
Derek Ashley Thomas wrote:
I have a string with a custom date format written in Japanese: 2013年
1月8日20時19分. I wish to convert this string to any other format
using date. I expected to use date -d 2013年1月8日 20時19分 +%F
%R but this produces the wrong date 2013-01-08 20:13 because it
sees the
Filip Kocina wrote:
I'd like to ask you why the owner and the group of a file is retained
while moving a file via mv.
Moving a file on the same filesystem does not copy the file. Moving a
file from one directory to another on the same filesystem simply
creates a new inode pointer in the new
tag 13742 + moreinfo notabug
close 13742
thanks
Taroe90 wrote:
sorry for my poor english
Please do not worry. But there are questions.
ping@ping-kubuntu:~/mywork/test/shell/ln/a$ ll
What is the ll command? And alias for ls -l? Or an alias for
ls -lF? Or something different?
总用量 8
Sami Kerola wrote:
Secondly,pardon my ignorance, I thought '/' and '//' or how ever many
slashes are the same root. Is this some non-obvious portability
gotcha? A link to education material would be great.
Correct. Anywhere except in the leading position the number of '/'
characters is not
Eric Blake wrote:
Sakse Dalum wrote:
Anywho, I've attached a diff to this mail, which may or may not be
applicable to the most recent version (I just did an apt-get
source in Trisquel 6.0 to get the source for coreutils).
Thanks for the attempt. We prefer patches against libvirt.git;
Bernhard Voelker wrote:
Michael Boldischar wrote:
For what it's worth, I still think a safe move flag in mv adds value.
Instead of a general safe idea, I'm wondering against what error cases
mv should be made aware of?
I.e., there are cases when creating the new files/directories fails,
Jim Meyering wrote:
Ole Tange wrote:
I was astonished to learn that:
perl -MMIME::Base64 -e 'while(read(STDIN,$buf,770*50)){print
decode_base64($buf)}'
is faster than:
base64 -d
...
Thanks for raising the issue.
I confirm the perl-based version takes less than 50% of base64
Bernhard Voelker wrote:
Dear e-letter,
e-letter wrote:
Readers,
Apologies if irrelevant, but curious to investigate why 'less'
installed on a mandriva box is able to open an opendocumentformat
file, but less on a opensuse box complains that such file is binary?
Any ideas how to
Jeffrey Streifling wrote:
This additional feature would be used with external scripting
interpreters that use 0 and 1 as truth values, such as GNU bc. The
useful idiom would be
if `bc $VAL1 $VAL2`
Of course the use of `...` backticks makes even a traditionalist guy
like me cringe. I
Eric Blake wrote:
Bob Proulx wrote:
But even expr is now obsoleted by built in shell math. Use ((...)) to
perform the math in the shell with no external program calls.
In bash, yes, but not portable. $(()) is standardized by POSIX, but
(()) is not, and has some surprising corner cases
Not so much to the coreutils mailing lists but to the other mailing
lists there have been quite a few large files attempted to be posted.
And when I say large I mean 10M files posted to mailing lists with
1200+ subscribers in the worst cases! Usually somewhat less large.
I wanted to say a few
Pádraig Brady wrote:
Thanks for the patch,
however I still think it adds inconsistency for little gain.
Creating this inconsistency also feels wrong to me too. It just
doesn't seem right that everything else is implemented consistently
but this one case is made special. In effect making this
Erik Auerswald wrote:
Eric Lavarde wrote:
to check multiple files I often tend to use 'cat *somefiles*' but it's
all concatenated and difficult to read, so I switch back to 'head
-nSOMETHINGBIG *somefiles*' but it's not optimal and I might miss lines
if a file is bigger than
Pádraig Brady wrote:
I've put this in place at:
http://www.gnu.org/software/coreutils/rejected_requests.html
I like it!
Bob
Andreas Schwab wrote:
Bob Proulx writes:
Erik Auerswald wrote:
Try head -n-0.
I like it!
This is non-standard. tail -n+1 is portable.
Yes. That is better. (I did know about tail -n+1 but had forgotten
about it. Thanks for the reminder.)
Bob
Pádraig Brady wrote:
Bob Proulx wrote:
Pádraig Brady wrote:
I've put this in place at:
http://www.gnu.org/software/coreutils/rejected_requests.html
I like it!
In retrospect it should be grouped by command,
which I'll do when a get a few mins.
It would be nice if the formatting
Henrik Juul Pedersen wrote:
Lokesh Walase wrote:
I am interested in adding progress bar feature to cp and mv commands.
For this I downloaded the latest source code GNU-coreutils-8.21.
A progress bar is somewhat intrusive to the copy command, but patches and
tools exist already.
Adding
Koteswararao Nelakurthi wrote:
Thanks again for your valuable response.
May I know to how to check the difference
(May be patches wise) between r6.0.6 to
r6.0.7 of coreutils package
Probably..by looking at git web interface
of coreutils package ?
can we find the same?
What distribution are
smu johnson wrote:
I have a suggestion for 'ls'. My idea is a GNU extension switch which
commafies (for lack of a better word) the filesizes in the basic -l output
of integers. This has been the default for 'dir' since MS-DOS, but I think
it might be a good addition for an optional switch in
Eric Blake wrote:
Bob Proulx wrote:
And you can always set
export LS_BLOCK_SIZE='1kB
in your environment to have that by default all of the time for ls.
That only works if you use a locale where %'d inserts thousands
separators. If you ever run with LC_ALL=C, the ' flag is a no-op
Anthony G. Basile wrote:
Pádraig Brady wrote:
I don't suppose you could use `cp` rather than `install` for this
use case?
Using cp instead of install would be a long shot here for our
package manager people but I can talk to them.
Why? What makes cp scary? (I would be inclined to use
jeff.gr...@kantarmedia.com wrote:
Running the command date on our server in Mongolia gives
$ date
Wed Jun 19 18:13:14 ULAT 2013
However entering a date with the ULAT timezone to calculate the UTC
date of an event in the past gives an error
$ date -u --date=25 May 2013 20:13 ULAT
Aijaz Baig wrote:
hi.
Hi.
Im trying to compile Gnu time 1.7 for a powerpc system using the windriver
build system which is based on yocto.
Thanks for the report. However you are reporting a bug in the time
project to the coreutils project. Time and coreutils are two separate
projects. GNU
Ben Lentz wrote:
I suspect I may get laughed off the list... but would you folks ever
consider restricting the use of chmod such that world-writable files
are reserved for 1) /tmp-style permissions (1777) or 2) reserved for
root-only users? Despite training (berating?) users, it seems the
Bernhard Voelker wrote:
ravi kothari wrote:
when i am running my process with nohup command and exit from
the server and again login process is not alive,it is
killed.
Without more information, it's hard to guess.
What was the exact command line you were running?
Is there something
Volker Klasen opened a bug in the Debian bug tracker concerning a
change in behavior in cut. I have CC'd the bug on this message. I
have manually set an appropriate Reply-To header.
http://bugs.debian.org/718898
There has been a lot of improvements made to cut. But the issue is
this one.
Bernhard Voelker wrote:
Eric Blake wrote:
Enda wrote:
$ echo cat $(ls -Qv *.pdf)
Why are you even bothering with ls, when the following is faster and
does what you want, without having to worry about awkward quoting in the
first place?
Probably because of the -v sorting order ...
Pádraig Brady wrote:
Pascal wrote:
cat - concatenate files and print on the standard output -
offers -s option to suppress repeated empty lines.
However, an empty line (visual perspective) that behave only
spaces or tabs is not considered as empty : one option -S that
would address
Update of bug #1212 (project coreutils):
Status:None = Fixed
Assigned to:None = rwp
Open/Closed:Open = Closed
Update of bug #1584 (project coreutils):
Assigned to:None = rwp
Open/Closed:Open = Closed
___
Follow-up Comment #1:
Doing
Summary: The old coreutils CVS is now marked read-only.
Details: Recently one of the other projects on Savannah moved from CVS
to GIT. They wanted to mark the old CVS source repository as
read-only to ensure that no developers accidentally committed to it.
And to have it produce a useful error
Erik Auerswald wrote:
Eric Blake wrote:
If the astronomical term is what you want, then maybe you really
do have a format that cannot be expressed in any existing
notation, and maybe it really is worth burning a % notation. But
how common is the Astronomical Julian Date in shell programming?
Brian Nash wrote:
I recently noticed that someone on IRC was looking for a way to use
`ls -la' without the destination of symlinks clogging up the
output. I believe this would be an excellent feature to include in
the coreutils package. It would also (theoretically) be an easy
addition.
Jim Meyering wrote:
I like it.
Thanks a lot. I'm sure that will answer many questions that would
otherwise end up on the list.
Thanks for the feedback. Committed.
http://www.gnu.org/software/coreutils/faq/#uname-is-system-specific
Bob
jayanthi radhakrishnan wrote:
Hi ,
When i download coreutils-8.22.tar.xz , it gets downloaded as
coreutils-8.22.tar.tar.
So , I get this error,
tar -xf coreutils-8.22.tar.tar
tar: directory checksum error
Is the tar file correct?
It appears that your browser has mangled the name.
Peng Yu wrote:
man sort says Set LC_ALL=C to get the traditional sort order that
uses native byte values.
Yes.
man comm says Note, comparisons honor the rules specified by 'LC_COLLATE'.
Yes. No. Almost. It honors LANG if neither LC_COLLATE nor LC_ALL is
set. It honors LC_COLLATE if
Julie Seamore wrote:
Attempting a dual boot with win xp and solydxk. I loaded Iso disk and the
screen shows a blue solydxk@solddxk ~ $ What do I type in next?
Sorry but you have posted to the wrong mailing list. Don't know
anything about either Windows-XP or solydxk here. You will
Pádraig Brady wrote:
Masataro Asai wrote:
Is this a bug or the intended behavior?
I think the main confusing here is that for POSIX timezones
you need to do the opposite to standard convention (and date output),
and use TZ=UTC-9 rather than TZ=UTC+9
POSIX timezones are inconsistent and
ravi kothari wrote:
I'd like to add you to my professional network on LinkedIn.
I have moderated him due to the recent spam to the mailing list.
Bob
Peng Yu wrote:
`sort input.txt -o input.txt` overwrites the input file. My
understanding is that sort reads everything and then write the output.
So it is OK to overwrite the original file. But I want to be sure. Can
anyone confirm if this is the case? Thanks.
Yes. Using -o is how you sort a
Markus Kuhn wrote:
A destination file D can be updated atomically by
1) first writing the new content of the destination file
into a temporary file T (e.g. created with mkostemp()),
located in the same directory as D, then
2) rename T into D (which atomically replaces D on
Colton Peltier wrote:
While working with some coworkers recently we noticed a strange
inconsistency between cp and scp, that caused us some confusion. For
the cp tool a -r or -R will do a recursive copy of directories, but
for scp only -r will. The -R flag for scp is gives illegal
option.
Pádraig Brady wrote:
djcj wrote:
Can you add an option to md5sum that allows one to output only the checksum?
Here's a code example:
Thanks for the patch.
However this is one of those marginal cases where it's
probably not worth the extra option to do this simple adjustment.
After all
Pádraig Brady wrote:
Sebastian Rückerl wrote:
Everything seems to work fine as long as I am not trying to
interrupt this process (using CTRL-C).
Only in this case everything just freezes for some time (for about
1 minute the terminal is blocked) even if I try to kill it from
another
Sebastian Rückerl wrote:
Bob Proulx wrote:
In your trap handler don't 'exit 1'. That washes off the correct exit
code. Instead reset your trap handler to the default handler and then
send the kill signal back to the current process. That will cause it
to exit with the correct, kill
Bernhard Voelker wrote:
Sebastian Rückerl wrote:
while ps ax | grep $dd_pid # might also need | grep -v grep here
Bernhard's comment improves this greatly.
The construct with ps ax | ... is rather fragile.
I'd use something like the following instead to get
the intermediate I/O
Jim Meyering wrote:
Pádraig Brady wrote:
POSIX says that `pwd` without options should assume -L is specified.
Hmm... It does? If so I think that is a bad thing in the standard
since it does not standardize existing behavior but requires an
incompatible change to it. Existing behavior of
Jim Meyering wrote:
Do you know of other uses of /bin/pwd that require -P's behavior?
About every script at my old employer used to use it in one way or
another. Since that is my past employer I no longer have access to
take an inventory. But it was quite a popular thing for people to do.
As
Jim Meyering wrote:
Pádraig Brady wrote:
OK you've convinced me.
Yay! :-)
It seems all /bin/pwd default to -P
while all builtin pwd default to -L
I think so too.
POSIX should probably say something about that.
Yes. Because it really should be standardizing on existing behavior
Pádraig Brady wrote:
Subject: Re: [PATCH] maint: avoid clang -Wint-to-pointer-cast warning
What was the text of the original warning? I think that would be
interesting to review. I think it would provide an additional clue.
* src/chroot.c: Explicitly cast int to pointer type.
- g
Pádraig Brady wrote:
Is this useful enough that newer scripts are incompat
with older systems without this functionality?
I'm 50:50 TBH
I know that Jim already opened the door by saying he would accept the
feature if it were written. For my part I see this as creeping
featurism and would vote
jb wrote:
It looks like fdisk, cfdisk, etc are confused about identifying those
partitions and their start/end sectors. Is there a partition table at all ?
If so, where is it located, sectorwise ?
If fdisk and cfdisk are confused then it is probably because the
partition table used in the
operations wrote:
I found out that a file existed which name was -R ...
Please see the FAQ:
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#I-have-a-file-_0027_002df_0027-and-it-affects-rm_002e
Bob
I have a string of hex encoded us-ascii characters. The hex sequence
48 61 70 70 79 is obviously Happy. Is there an easy way to convert
them to ascii using printf? It seems like there should be.
$ printf %c\n 0x48 0x61 0x70 0x70 0x79
0
0
0
0
0
Nope. It doesn't operate like C
Hello LxC,
LxC wrote:
Bob Proulx wrote on 25 Dec 2014:
Is there any way to use the shell printf like the C printf and do this
conversion in the coreutils printf? Or perhaps another way?
I use a shell alias with perl as hexer:
alias hx='perl -ne'\''printf %*vX\n, ,$_'\'
alias hxr=perl
LxC wrote:
Pádraig Brady wrote:
LxC wrote:
I was astonished that Linux dir/ls could not count files/dirs like DOS
and implemented it myself month ago.
Astonished? I am astonished that you are astonished! :-)
It's now indispensable for me and maybe useful for others too?
I think it is each
Bernhard Voelker wrote:
tee - duplicates stdin to stdout (maybe in interleaved order)
since v5.2.1-1247-g8dafbe5; this behavior is documented as such.
But POSIX explicitly mandates different behavior:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/tee.html
If a file
1 - 100 of 1396 matches
Mail list logo
