Bsrhrki

What is the reasoning behind standardization (dividing by standard deviation)?

Does the Shadow Magic sorcerer's Eyes of the Dark feature work on all Darkness spells or just his/her own?

Exposing a company lying about themselves in a tightly knit industry: Is my career at risk on the long run?

Print last inputted byte

Would mining huge amounts of resources on the Moon change its orbit?

Why are there no stars visible in cislunar space?

Air travel with refrigerated insulin

Why didn’t Eve recognize the little cockroach as a living organism?

Is VPN a layer 3 concept?

Weird lines in Microsoft Word

When should a starting writer get his own webpage?

Can "few" be used as a subject? If so, what is the rule?

What is the difference between something being completely legal and being completely decriminalized?

Are hand made posters acceptable in Academia?

"Marked down as someone wanting to sell shares." What does that mean?

Can a university suspend a student even when he has left university?

Why I don't get the wanted width of tcbox?

Animating wave motion in water

Error in master's thesis, I do not know what to do

Does convergence of polynomials imply that of its coefficients?

Turning a hard to access nut?

is this saw blade faulty?

The English Debate

Fair way to split coins

How to read string as hex number in bash?

3

I have the bash line:

expr substr $SUPERBLOCK 64 8

Which is return to me string line:

00080000

I know that this is, actually, a 0x00080000 in little-endian. Is there a way to create integer-variable from it in bash in big-endian like 0x80000?

bash numeric-data hex expr

share|improve this question

edited 9 hours ago

Jesse_b

13.7k23471

asked 10 hours ago

DenisNovacDenisNovac

186

add a comment | 

3

I have the bash line:

expr substr $SUPERBLOCK 64 8

Which is return to me string line:

00080000

I know that this is, actually, a 0x00080000 in little-endian. Is there a way to create integer-variable from it in bash in big-endian like 0x80000?

bash numeric-data hex expr

share|improve this question

edited 9 hours ago

Jesse_b

13.7k23471

asked 10 hours ago

DenisNovacDenisNovac

186

add a comment | 

I have the bash line:

expr substr $SUPERBLOCK 64 8

Which is return to me string line:

00080000

I know that this is, actually, a 0x00080000 in little-endian. Is there a way to create integer-variable from it in bash in big-endian like 0x80000?

bash numeric-data hex expr

share|improve this question

edited 9 hours ago

Jesse_b

13.7k23471

asked 10 hours ago

DenisNovacDenisNovac

186

expr substr $SUPERBLOCK 64 8

00080000

share|improve this question

edited 9 hours ago

Jesse_b

13.7k23471

asked 10 hours ago

DenisNovacDenisNovac

186

share|improve this question

edited 9 hours ago

Jesse_b

13.7k23471

asked 10 hours ago

DenisNovacDenisNovac

186

edited 9 hours ago

Jesse_b

13.7k23471

edited 9 hours ago

Jesse_b

13.7k23471

asked 10 hours ago

DenisNovacDenisNovac

186

asked 10 hours ago

DenisNovacDenisNovac

186

2 Answers
2

active

oldest

votes

4

Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):

printf '0x%xn' "$((16#00080000))"

Which you could write as:

printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"

share|improve this answer

answered 9 hours ago

Jesse_bJesse_b

13.7k23471

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
  
  – DenisNovac
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)
  
  – Ped7g
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.
  
  – DenisNovac
  9 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000
  
  – Jesse_b
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
  
  – DenisNovac
  9 hours ago
  

  
  
  
  

 | 
show 4 more comments

2

There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:

$ echo '16'; echo i; echo 00080000; echo p; | dc
524288
$ echo 'ibase=16'; echo 00080000; | bc 
524288

For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).

share|improve this answer

answered 5 hours ago

Greg A. WoodsGreg A. Woods

52248

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f507044%2fhow-to-read-string-as-hex-number-in-bash%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

4

Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):

printf '0x%xn' "$((16#00080000))"

Which you could write as:

printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"

share|improve this answer

answered 9 hours ago

Jesse_bJesse_b

13.7k23471

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
  
  – DenisNovac
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)
  
  – Ped7g
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.
  
  – DenisNovac
  9 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000
  
  – Jesse_b
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
  
  – DenisNovac
  9 hours ago
  

  
  
  
  

 | 
show 4 more comments

4

Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):

printf '0x%xn' "$((16#00080000))"

Which you could write as:

printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"

share|improve this answer

answered 9 hours ago

Jesse_bJesse_b

13.7k23471

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
  
  – DenisNovac
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  @DenisNovac I'm not sure if you use big/little endian correctly (maybe you have something else on mind, but I'm doing some assembly programming for fun, so for me endianness is per bytes), but 0x12345678 is in other endianness 0x78563412, not 0x87654321. (and the value in your question 00080000 is after byte swap 00000800, i.e. 2048 decimal)
  
  – Ped7g
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Oh, you are right. I just got the right answer by wrong way. I am rewriting some code from python to bash, so i know all answers before i got them.
  
  – DenisNovac
  9 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @DenisNovac: You didn't have the right answer FYI. 0x8000 was originally in your question which is not the same as 0x80000 or 0x00080000
  
  – Jesse_b
  9 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
  
  – DenisNovac
  9 hours ago
  

  
  
  
  

 | 
show 4 more comments

Probably a better way to do this but I've come up with this solution which converts the number to decimal and then back to hex (and manually adds the 0x):

printf '0x%xn' "$((16#00080000))"

Which you could write as:

printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"

share|improve this answer

answered 9 hours ago

Jesse_bJesse_b

13.7k23471

printf '0x%xn' "$((16#00080000))"

printf '0x%xn' "$((16#$(expr substr "$SUPERBLOCK" 64 8)))"

share|improve this answer

answered 9 hours ago

Jesse_bJesse_b

13.7k23471

answered 9 hours ago

Jesse_bJesse_b

13.7k23471

answered 9 hours ago

Jesse_bJesse_b

13.7k23471

2

There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:

$ echo '16'; echo i; echo 00080000; echo p; | dc
524288
$ echo 'ibase=16'; echo 00080000; | bc 
524288

For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).

share|improve this answer

answered 5 hours ago

Greg A. WoodsGreg A. Woods

52248

add a comment | 

2

There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:

$ echo '16'; echo i; echo 00080000; echo p; | dc
524288
$ echo 'ibase=16'; echo 00080000; | bc 
524288

For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).

share|improve this answer

answered 5 hours ago

Greg A. WoodsGreg A. Woods

52248

add a comment | 

There are two more or less standard (and ancient) command-line unix tools that offer very easy ways to convert numbers between different bases:

$ echo '16'; echo i; echo 00080000; echo p; | dc
524288
$ echo 'ibase=16'; echo 00080000; | bc 
524288

For normal human use I very much prefer bc, but when writing a program that generates code, especially from a parser of some sort, a stack-based tool like dc may be easier to deal with (and indeed the original version of bc was a front-end parser for dc).

share|improve this answer

answered 5 hours ago

Greg A. WoodsGreg A. Woods

52248

$ echo '16'; echo i; echo 00080000; echo p; | dc
524288
$ echo 'ibase=16'; echo 00080000; | bc 
524288

share|improve this answer

answered 5 hours ago

Greg A. WoodsGreg A. Woods

52248

answered 5 hours ago

Greg A. WoodsGreg A. Woods

52248

answered 5 hours ago

Greg A. WoodsGreg A. Woods

52248