search for: ibase

On Aug 31, 2015, at 10:05 AM, Mike - st257 <silvertip257 at gmail.com> wrote: > > On Mon, Aug 31, 2015 at 11:15 AM, Warren Young <wyml at etr-usa.com> wrote: > >> ibase=A and obase=A > > Not sure how this helps me with my most recent example of bin_to_hex where > the ibase within the define clause wasn't honored. That?s because your bin_to_hex function is erroneously assuming that its input is just a string of digits that has no base interpretation,...

...[ "$(echo $1|wc -c)" = "41" ];then >> hex=$(echo $1|base64 -d| od -x -w28 --endian=big|head -n1|sed >> 's/^0000000 //'|sed 's/ //g') >> echo ${hex} >> hex_chunk=$(echo ${hex}|cut -c1-2); >> echo ${hex_chunk} >> rev=$(echo "ibase=16; ${hex_chunk}" | bc) >> hex_chunk=$(echo ${hex}|cut -c3-4) >> echo ${hex_chunk} >> dashes=$(echo "ibase=16; ${hex_chunk}" | bc) >> hex_chunk=$(echo ${hex}|cut -c5-16) >> echo ${hex_chunk} >> notsure=$(echo "ibase=16; ${hex_chunk}" | bc...

...orrect so I'll keep working on it #!/bin/bash if [ "$(echo $1|wc -c)" = "41" ];then hex=$(echo $1|base64 -d| od -x -w28 --endian=big|head -n1|sed 's/^0000000 //'|sed 's/ //g') echo ${hex} hex_chunk=$(echo ${hex}|cut -c1-2); echo ${hex_chunk} rev=$(echo "ibase=16; ${hex_chunk}" | bc) hex_chunk=$(echo ${hex}|cut -c3-4) echo ${hex_chunk} dashes=$(echo "ibase=16; ${hex_chunk}" | bc) hex_chunk=$(echo ${hex}|cut -c5-16) echo ${hex_chunk} notsure=$(echo "ibase=16; ${hex_chunk}" | bc) hex_chunk=$(echo ${hex}|cut -c17-24) echo ${hex_chun...

...ubt the syntax is in some way wrong, but when I test from the CLI and the right values are returned, I have to wonder. Other than a few other define statements, the only other option I have set is scale=5 in my bcrc. In reference to the order of (o|i)base parameters, I have specified obase before ibase [0]. [0] http://docstore.mik.ua/orelly/unix/upt/ch49_03.htm See below for my examples. Thanks! ]$ echo "bin_to_dec(1001)" | bc 1001 # should be decimal 9 ]$ echo "obase=10; ibase=2; 1001" | bc 9 ]$ grep bin_to_dec ~/.bcrc define bin_to_dec(b) { obase=10; ibase=2; return b;...

On Mon, Aug 31, 2015 at 1:06 PM, Warren Young <wyml at etr-usa.com> wrote: > On Aug 31, 2015, at 10:05 AM, Mike - st257 <silvertip257 at gmail.com> wrote: > > > > On Mon, Aug 31, 2015 at 11:15 AM, Warren Young <wyml at etr-usa.com> wrote: > > > >> ibase=A and obase=A > > > > Not sure how this helps me with my most recent example of bin_to_hex > where > > the ibase within the define clause wasn't honored. > > That?s because your bin_to_hex function is erroneously assuming that its > input is just a string of digits...

...l.com> wrote: > I decided to continue trying the ldap route as well > > littlehex2int() > { > hex=$1 > hex_chunk=$(echo ${hex}|cut -c$2-$3) > little=$(echo ${hex_chunk}|awk '{print > substr($0,7,2)substr($0,5,2)substr($0,3,2)substr($0,1,2)}') > echo "ibase=16; ${little}" | bc > } > > base64_to_sid() > { > OBJECTSID="$1" > hex=$(echo ${OBJECTSID}|base64 -d|od -A n -x -w28 --endian=big|sed 's/ > //g'|awk '{print toupper($1)}') > hex_chunk=$(echo ${hex}|cut -c1-2); > rev=$(echo "ibase=16; $...

I decided to continue trying the ldap route as well littlehex2int() { hex=$1 hex_chunk=$(echo ${hex}|cut -c$2-$3) little=$(echo ${hex_chunk}|awk '{print substr($0,7,2)substr($0,5,2)substr($0,3,2)substr($0,1,2)}') echo "ibase=16; ${little}" | bc } base64_to_sid() { OBJECTSID="$1" hex=$(echo ${OBJECTSID}|base64 -d|od -A n -x -w28 --endian=big|sed 's/ //g'|awk '{print toupper($1)}') hex_chunk=$(echo ${hex}|cut -c1-2); rev=$(echo "ibase=16; ${hex_chunk}" | bc) hex_chunk=$(echo ${he...

On Aug 31, 2015, at 6:55 AM, Mike - st257 <silvertip257 at gmail.com> wrote: > > I suppose my only options for this are to use shell functions or write a > script using a language that handles things properly (sanely?). No, there?s a fairly common hack around this problem: ibase=A and obase=A *always* means ?base 10? regardless of the current base, due to a quirk in the way values for these settings are interpreted. Thus you can always force your way back to sanity. My objection is that this is even necessary in the first place.

...wrote: >> Thoughts as to why my BC functions aren't properly converting between bases? >> >> Decimal to binary or hex works fine, but not binary or hex to decimal and >> so forth. > > I'm not an expert in bc, so I might be wrong, but it looks like setting the ibase inside a function is simply too late. ibase affects how bc interprets input. Yes, and it?s a serious design mistake in bc, IMHO. No other programmable system I?ve ever used changes how numbers in program text are interpreted based on prior commands to the system. I wrote a long answer explainin...

...d to continue trying the ldap route as well >> >> littlehex2int() >> { >> hex=$1 >> hex_chunk=$(echo ${hex}|cut -c$2-$3) >> little=$(echo ${hex_chunk}|awk '{print >> substr($0,7,2)substr($0,5,2)substr($0,3,2)substr($0,1,2)}') >> echo "ibase=16; ${little}" | bc >> } >> >> base64_to_sid() >> { >> OBJECTSID="$1" >> hex=$(echo ${OBJECTSID}|base64 -d|od -A n -x -w28 --endian=big|sed 's/ >> //g'|awk '{print toupper($1)}') >> hex_chunk=$(echo ${hex}|cut -c1-2); &g...

...gt; #!/bin/bash > if [ "$(echo $1|wc -c)" = "41" ];then > hex=$(echo $1|base64 -d| od -x -w28 --endian=big|head -n1|sed > 's/^0000000 //'|sed 's/ //g') > echo ${hex} > hex_chunk=$(echo ${hex}|cut -c1-2); > echo ${hex_chunk} > rev=$(echo "ibase=16; ${hex_chunk}" | bc) > hex_chunk=$(echo ${hex}|cut -c3-4) > echo ${hex_chunk} > dashes=$(echo "ibase=16; ${hex_chunk}" | bc) > hex_chunk=$(echo ${hex}|cut -c5-16) > echo ${hex_chunk} > notsure=$(echo "ibase=16; ${hex_chunk}" | bc) > hex_chunk=$(echo...

...15 07:15 AM, Mike - st257 wrote: > Thoughts as to why my BC functions aren't properly converting between bases? > > Decimal to binary or hex works fine, but not binary or hex to decimal and > so forth. I'm not an expert in bc, so I might be wrong, but it looks like setting the ibase inside a function is simply too late. ibase affects how bc interprets input. So "echo "bin_to_dec(1001)" | bc" is going to interpret the value of 1001 while reading it from input, not after passing it to a function where ibase is reset. Supporting that theory: $ bc ... def...

...BC functions aren't properly converting between > bases? > >> > >> Decimal to binary or hex works fine, but not binary or hex to decimal > and > >> so forth. > > > > I'm not an expert in bc, so I might be wrong, but it looks like setting > the ibase inside a function is simply too late. ibase affects how bc > interprets input. > Thanks Gordon. Big bummer given that behavior. :-/ I had (and did test) definitions for other conversions (though I didn't post them), but this one also drives it home. ~]$ grep bin_to_hex ~/.bcrc define b...

There existing a bug in newer Wine versions. I use SuSE 9.3 as system. If I used the Wine-version, which comes with the distribution (wine-20050211), then the following window comes at start: http://user.web-gear.com/theuserbl/wine1.png But if I update to wine-20050830 or wine-20050930 then it looks like http://user.web-gear.com/theuserbl/wine3.png It is NOT a font-problem. I have copied the

On Fri, Nov 3, 2017 at 2:43 PM, Rowland Penny <rpenny at samba.org> wrote: > On Fri, 3 Nov 2017 13:53:22 -0600 > Jeff Sadowski via samba <samba at lists.samba.org> wrote: > >> just get objectsid and use this >> >> https://blogs.msdn.microsoft.com/oldnewthing/20040315-00/?p=40253 > > Why ??? > So that when someone on a linux machine writes to disk

...ki Tuomi: > Please keep replies on list. Can you provide doveconf -n and output of > doveadm user victim ? > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" > <a.hoepner at ibased.de> > Date: 18/09/2018 19:13 (GMT+02:00) > To: Aki Tuomi <aki.tuomi at dovecot.fi> > Subject: Re: dovecot (2.2.13) panic on imap-login from iphone se > > > Sorry. I think upgrade is not possible because it is a very outdated > gentoo installation and im not abe to c...

On 08/31/2015 05:55 AM, Mike - st257 wrote: >>> I'm not an expert in bc, so I might be wrong, but it looks like setting >> >the ibase inside a function is simply too late. ibase affects how bc >> >interprets input. >> > > Thanks Gordon. > Big bummer given that behavior. :-/ I suppose that depends on what you're trying to accomplish. Most conversions you can do entirely within bash, if that's yo...

Hi! I have already in an other post mentioned IBasic. But if I use tabs in IBasic and the word which comes after it is a internal command, so that it will be colered, in wine-20050930 it looks like that on the right side: http://user.web-gear.com/theuserbl/newwine.png I think using spaces works still very well. Only tabs for it makes this problem. An other thing (I don't know if it is

Please keep replies on list. Can you provide doveconf -n and output of doveadm user victim ? ---Aki TuomiDovecot oy -------- Original message --------From: "Andre Hoepner - i.based: Systemhaus GmbH + Co. KG" <a.hoepner at ibased.de> Date: 18/09/2018 19:13 (GMT+02:00) To: Aki Tuomi <aki.tuomi at dovecot.fi> Subject: Re: dovecot (2.2.13) panic on imap-login from iphone se Sorry. I think upgrade is not possible because it is a very outdated gentoo installation and im not abe to compile without compiling the whol...

...5, at 6:55 AM, Mike - st257 <silvertip257 at gmail.com> wrote: > > > > I suppose my only options for this are to use shell functions or write a > > script using a language that handles things properly (sanely?). > > No, there?s a fairly common hack around this problem: ibase=A and obase=A > *always* means ?base 10? regardless of the current base, due to a quirk in > the way values for these settings are interpreted. Thus you can always > force your way back to sanity. > Not sure how this helps me with my most recent example of bin_to_hex where the ibase w...