How to read string as hex number in bash?2019 Community Moderator ElectionIn bash, how to convert 8 bytes to an unsigned int (64bit LE)?Bash: integer expression expected, using read/testHow to change bash prompt string in current bash session?How to convert an special hex character from an html page in bash?Loop over a string in zsh and BashModifying empty string variable inside switch statement in function bashExtract Complex String Inside Parentheses in Linux BashConstruct bash array with only string formatprintf escape %q string vs variableHow are ext4fs checksums being calculated?
Would it be believable to defy demographics in a story?
Can other pieces capture a threatening piece and prevent a checkmate?
How can I create URL shortcuts/redirects for task/diff IDs in Phabricator?
Do native speakers use "ultima" and "proxima" frequently in spoken English?
Why is indicated airspeed rather than ground speed used during the takeoff roll?
Hackerrank All Women's Codesprint 2019: Name the Product
Why is this tree refusing to shed its dead leaves?
Error in master's thesis, I do not know what to do
Writing in a Christian voice
Exit shell with shortcut (not typing exit) that closes session properly
How can a new country break out from a developed country without war?
Should I be concerned about student access to a test bank?
Is there any common country to visit for uk and schengen visa?
pipe commands inside find -exec?
Can "few" be used as a subject? If so, what is the rule?
Why is participating in the European Parliamentary elections used as a threat?
Does convergence of polynomials imply that of its coefficients?
Why do I have a large white artefact on the rendered image?
What is the tangent at a sharp point on a curve?
Is xar preinstalled on macOS?
How do hiring committees for research positions view getting "scooped"?
Would mining huge amounts of resources on the Moon change its orbit?
How do researchers send unsolicited emails asking for feedback on their works?
10 year ban after applying for a UK student visa
How to read string as hex number in bash?
2019 Community Moderator ElectionIn bash, how to convert 8 bytes to an unsigned int (64bit LE)?Bash: integer expression expected, using read/testHow to change bash prompt string in current bash session?How to convert an special hex character from an html page in bash?Loop over a string in zsh and BashModifying empty string variable inside switch statement in function bashExtract Complex String Inside Parentheses in Linux BashConstruct bash array with only string formatprintf escape %q string vs variableHow are ext4fs checksums being calculated?
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
edited 3 hours ago
Jesse_b
13.7k23371
asked 4 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
edited 3 hours ago
Jesse_b
13.7k23371
asked 4 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
edited 3 hours ago
Jesse_b
13.7k23371
asked 4 hours ago
DenisNovacDenisNovac
186
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
bash numeric-data hex expr
edited 3 hours ago
Jesse_b
13.7k23371
asked 4 hours ago
DenisNovacDenisNovac
186
edited 3 hours ago
Jesse_b
13.7k23371
asked 4 hours ago
DenisNovacDenisNovac
186
edited 3 hours ago
Jesse_b
13.7k23371
edited 3 hours ago
Jesse_b
13.7k23371
edited 3 hours ago
Jesse_b
13.7k23371
13.7k23371
asked 4 hours ago
DenisNovacDenisNovac
186
asked 4 hours ago
DenisNovacDenisNovac
186
asked 4 hours ago
DenisNovacDenisNovac
186
186
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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)))"
answered 3 hours ago
Jesse_bJesse_b
13.7k23371
Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
– DenisNovac
3 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 question00080000is after byte swap00000800, i.e. 2048 decimal)
– Ped7g
3 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
3 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
3 hours ago
Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
– DenisNovac
3 hours ago
|
show 4 more comments
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
);
);
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
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
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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)))"
answered 3 hours ago
Jesse_bJesse_b
13.7k23371
Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
– DenisNovac
3 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 question00080000is after byte swap00000800, i.e. 2048 decimal)
– Ped7g
3 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
3 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
3 hours ago
Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
– DenisNovac
3 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)))"
answered 3 hours ago
Jesse_bJesse_b
13.7k23371
Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
– DenisNovac
3 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 question00080000is after byte swap00000800, i.e. 2048 decimal)
– Ped7g
3 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
3 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
3 hours ago
Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
– DenisNovac
3 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)))"
answered 3 hours ago
Jesse_bJesse_b
13.7k23371
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)))"
answered 3 hours ago
Jesse_bJesse_b
13.7k23371
answered 3 hours ago
Jesse_bJesse_b
13.7k23371
answered 3 hours ago
Jesse_bJesse_b
13.7k23371
answered 3 hours ago
Jesse_bJesse_b
13.7k23371
13.7k23371
Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
– DenisNovac
3 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 question00080000is after byte swap00000800, i.e. 2048 decimal)
– Ped7g
3 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
3 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
3 hours ago
Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
– DenisNovac
3 hours ago
|
show 4 more comments
Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
– DenisNovac
3 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 question00080000is after byte swap00000800, i.e. 2048 decimal)
– Ped7g
3 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
3 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
3 hours ago
Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
– DenisNovac
3 hours ago
Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
– DenisNovac
3 hours ago
Thank you! I actually added |rev inside to convert to big-endian: printf "$((16#$(expr substr $SUPERBLOCK 64 8|rev)))"
– DenisNovac
3 hours ago
5
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
3 hours ago
@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
3 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
3 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
3 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
3 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
3 hours ago
Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
– DenisNovac
3 hours ago
Yes, but i needed to get exactly 0x8000, so i've made mistake somewhere before. This is offset or something.
– DenisNovac
3 hours ago
|
show 4 more comments
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
