Items tagged with: commands
5/23/06 From YahuShua HaMashiach, Our Lord and Savior
The Word of The Lord Spoken to Timothy
For All Those Who Have Ears to Hear
Thus says The Lord, your Redeemer: I AM COME - I have come already and shall also return; I shall gather My #elect and come on the #clouds of #heaven, with #power and great #glory. Yet you of this #world do not believe. #Beloved ones, how is it you do not #understand My #speech? Behold, I proclaim it through your own #kindred and #countrymen, in a familiar #tongue, yet you can not #bear to #listen; indeed, you refuse to #hear! For your #hearts remain far from Me, #married to a world of unbridled #sin, caught up in a deluge of #lies, false truths called #science and #religion which deny My name and steal from My glory!
Beloved, I AM THE #TRUTH, which was born into the world to testify! Yet you of this world will in no wise hear Me! Yes, even you who dwell in the churches of men reject Me, refusing to accept Me as I truly am! Woe to you, therefore! Woe, I say to you! Woe to all who reject My words and hold fast to the #doctrines and #traditions of #men!
Thus says The Lord, to all those who call of themselves Christian: Beloved, do I #live in you? Do you even know My name? For I tell you the truth, you all slumber, you have all fallen asleep. In #beds filled with man’s conceit, overlain with #purple and #scarlet, you have lain down and remain at ease.
Behold, upon false #foundations of corrupt #doctrine and filthy #tradition, you build up high #walls with untempered #mortar - church after church, denomination after #denomination, walking always in the #commandments of men! YOU HAVE WROUGHT IN VAIN! For I tell you the truth, your every #church shall come to nothing - every #house devastated, all denominations brought to ruin! For I have not dwelt there!
#Repent therefore, and #tear down all you
Have built up in My name, for yourselves,
Of yourselves, to your own glory...
Tear it all down, and begin again in Me...
#Obey My #Word as it is written,
#Cast off all you have written,
And walk no more in the way
Set forth by the #founders...
Break up this fallow #ground, and #sow
No more among all these #briers and #thorns,
And I may yet receive you, says The Lord.
Churches of men, hold your #lamps up, so I may see your #faces. Shine your lamps on your houses, that I may behold your good works, all these grand works you boast of in My name, saying, “Lord, Lord, have we not prophesied in Your name, cast out demons in Your name, and done many wonderful works in Your name?” Yet most assuredly, I say to you, I do not know you!
Your lamps have gone out, and you have nothing at all with which to relight them. Neither are you willing to go out and receive from those I send, for you do always offend. Thus you shall remain in your darkened houses, folding your #hands to #sleep, until #destitution overtakes you and #scarcity drives you out. For I have purposed #disaster upon every house of #worship, until every church is torn down and every denomination is left in ruins. Therefore come out from among them, and embrace The True #Light and receive of the #pure #oil, says The Lord.
Beloved, how long shall I wait for you? How long will you put Me last, as one who is made to wait in an outer #room? How long shall you forget My #Sabbaths and forsake My #Holy Days? How long shall you #pollute My name and forsake The #Commandments of God, in the name of #Grace?!
Beloved, follow Me as I am, and not as you would have Me be! #Walk in MY ways, and #forsake all these commandments of men! For I dwell not in any church made by #human #hands... I dwell in the #hearts of men! I live in those who #love Me and obey My #commands; I abide with those who continually seek My #face and long to know Me as I truly am; I dwell in the #temple of God made by HIS hands!
Therefore again, I call you to repent, to repent in #sincerity and in truth; to return to your First Love, to walk in the first works; to embrace The Word of God anew and bring forth works worthy of repentance, that you may truly be #born again. For there is only One #Way, Only One Truth Absolute, Only One #Life without end... I am He, beloved! I AM HE!
Therefore awake, all you churches of men,
And listen to the #sound of this #Trumpet...
Be wide #awake and very #sober, pay close attention,
For the #mouth of The Living God has spoken...
Says The Holy One of #Israel.
#prophecy #prophet #Jesus #Yeshua #Christ #Messiah #God #church #bible #scripture #christian #christianity #JesusChrist #HolySpirit #Savior #Saviour #Lord
I came across Taco Bell Programming recently, and think this article is worthy to read for every software engineer. The post mentions a scenario which you may consider to use Hadoop to solve but…
Article word count: 192
HN Discussion: https://news.ycombinator.com/item?id=19293331
Posted by nanxiao (karma: 261)
Post stats: Points: 91 - Comments: 74 - 2019-03-03T08:02:27Z
#HackerNews #commands #may #need #only #pipeline #unix #what #you
I came across Taco Bell Programming recently, and think this article is worthy to read for every software engineer. The post mentions a scenario which you may consider to use Hadoop to solve but actually xargs may be a simpler and better choice. This reminds me a similar experience: last year a client wanted me to process a data file which has 5 million records. After some investigations, no novel technologies, a concise awk script (less than 10 lines) worked like a charm! What surprised me more is that awk is just a single-thread program, no nifty concurrency involved.
The IT field never lacks “new” technologies: cloud computing, big data, high concurrency, etc. However, the thinkings behind these “fancy” words may date back to the era when Unix arose. Unix command line tools are invaluable treasure. In many cases, picking the right components and using pipeline to glue them can satisfy your requirement perfectly. So spending some time in reviewing Unixcommand line manual instead of chasing state-of-the-art techniques exhaustedly, you may gain more.
BTW, if your data set can be disposed by an awk script, it should not be called “big data”.
HackerNewsBot debug: Calculated post rank: 85 - Loop: 112 - Rank min: 80 - Author rank: 27
I am starting to realize that the Unix command-line toolbox can fix absolutely any problem related to text wrangling. Let me tell you about a problem I had, and how I used some Unix command-line…
Article word count: 1046
HN Discussion: https://news.ycombinator.com/item?id=19160659
Posted by v3gas (karma: 155)
Post stats: Points: 104 - Comments: 80 - 2019-02-14T09:20:46Z
#HackerNews #commands #problem #solving #unix #with
I am starting to realize that the Unix command-line toolbox can fix absolutely any problem related to text wrangling. Let me tell you about a problem I had, and how I used some Unix command-line utilities to solve it.
I’m working on research for my master thesis. As with many statisticians, I am running a lot of simulations. I first simulate some data according to some numerical seed (to ensure reproducibility), and then use an algorithm to estimate something based on that data. For each simulation run, I create some files, typically like so:
Sometimes a run fails. This doesn’t really matter in this case: For any failed simulation, I can just do another one. For the 0001 data, I had a successful run with algorithm A. Therefore I want to use the 0001 data on algorithm B as well. But what I do need is to keep track of which runs have failed.
After running algorithm A on a lot of data, I end up with a large list of files like
The astute observer will note that the file for algorithm A on data 0004 and 0008 are missing. How can I get a list of all the numbers for which A didn’t succeed?
I certainly could go over manually, but that would be error prone, and incredibly boring. It’s much better to write a program to do it!
To be obtuse: Those that didn’t succeed are the numbers from 0001 to 0500 except those that suceeded. And one handy command to get a list of numbers is seq:
$> seq 10
(If only one number is given, it is implied that the sequence starts with 1. seq 2 10 would do what you think it would, as well.)
Now, if we can get a list of all the successful runs, we should be able to get what we want by cross-checking the list of successful runs with a seq command which prints all possible numbers!
Most command-line utilities do one pretty specific thing. For example, with cut you can get the characters on specific locations on each line
$> cat text
dolor sit amet
$> cat text | cut -c 2-5
Notice here the use of the so-called pipe operator |. Like I said, most utilities do one specific thing, and it does that thing well. The neat thing is that these can be combined. By using these pipes, the output from the command to the left of the pipe is directed to the command to the right. Note that these commands treat the input as a stream of lines, which is often really handy.
We can get a list of the successful file names by piping the list of files into a grep command, which is a command which can use regular expressions. Since all files start with an equal length of 4 digits, we can match these to the regular expression \d\d\d\d, matching 4 digits in a row, and add the file ending for the A algorithm to the regular expression. To get the list of files with one line for each file, we do ls -1. (It turns out that just piping ls will give each file its own line.)
$> ls -1 dataset-directory | grep ʼ\d\d\d\d_A.csvʼ
For some reason, these show up in a scrambled order after using grep. We can use sort to fix that. And we are only interested in the numbers, so we can use cut -c 1-4 to extract the number parts.
$> ls -1 dataset-directory | grep ʼ\d\d\d\d_A.csvʼ | sort | cut -c 1-4
These numbers aren’t exactly the same as the numbers from the seq command, since these are zero-padded. Therefore we write a quick Python script to parse them as integers.
import sys for line in sys.stdin: i = int(line) print(i)
Now, piping into this script will give us the numbers that we want:
$> ls -1 dataset-directory | grep ʼ\d\d\d\d_A.csvʼ | cut -c 1-4 | python3 parse.py
But we’re repeating the numbers here. The uniq command takes repeated lines and only prints one of each, which is exactly what we want.
$> ls -1 dataset-directory | grep ʼ\d\d\d\d_A.csvʼ | cut -c 1-4 | python3 parse.py | uniq
We’re getting there! Now we have to figure out how to cross-check these lists of numbers. Luckily, there exists a command called comm, which checks for common characters in two input streams. To get the input of a sequence of commands such as the one above, we can evaluate it and redirect it, which we do by wrapping it in <(...).
$> comm <(ls -1 dataset-directory | grep ʼ\d\d\d\d_A.csvʼ | cut -c 1-4 | python3 parse.py | uniq) <(seq 500) 1 2 3 4 5 6 7 8 9 10
This output is a bit disorienting. If we read the manual of comm (by doing man comm), we see that comm “produces three text columns as output: lines only in file1; lines only in file2; and lines in both files.” To suppress column 1 – which is empty, since no numbers are only from the file list – call comm with the flag -1. And since we are not interested in the numbers which are in both streams, we suppress with the -3 flag as well.
$> comm -1 -3 <(ls -1 dataset-directory | grep ʼ\d\d\d\d_A.csvʼ | cut -c 1-4 | python3 parse.py | uniq) <(seq 500)
And we’re done!
Update: This post generated some interesting discussion on Hacker News. There’s many ways to solve this problem, and the way I did it is probably not the best. Be sure to check it out for tips on how to improve.
Do you want to get notified of new blog posts? Go here for an RSS feed.
HackerNewsBot debug: Calculated post rank: 96 - Loop: 177 - Rank min: 80 - Author rank: 31