similar to: "\088" is legal syntax?

On Wed, 2018-05-23 at 15:27 -0600, Jens Axboe wrote: > On 5/23/18 2:05 PM, Joe Perches wrote: > > Convert the S_<FOO> symbolic permissions to their octal equivalents as > > using octal and not symbolic permissions is preferred by many as more > > readable. > > > > see: https://lkml.org/lkml/2016/8/2/1945 > > > > Done with automated conversion

On Wed, 2018-05-23 at 15:27 -0600, Jens Axboe wrote: > On 5/23/18 2:05 PM, Joe Perches wrote: > > Convert the S_<FOO> symbolic permissions to their octal equivalents as > > using octal and not symbolic permissions is preferred by many as more > > readable. > > > > see: https://lkml.org/lkml/2016/8/2/1945 > > > > Done with automated conversion

On Thu, 2018-05-24 at 06:47 -0600, Jens Axboe wrote: > On 5/23/18 4:35 PM, Joe Perches wrote: > > On Wed, 2018-05-23 at 15:27 -0600, Jens Axboe wrote: > > > On 5/23/18 2:05 PM, Joe Perches wrote: > > > > Convert the S_<FOO> symbolic permissions to their octal equivalents as > > > > using octal and not symbolic permissions is preferred by many as more

On Fri, Aug 21, 2020 at 06:02:49PM +1200, Peter wrote: > On 21/08/20 5:55 pm, Aki Tuomi wrote: > > > At a guess it was removed from the spec for el8 (which does not support > > > tcpwrap) and somehow got removed from el7 by accident. The ghettoforge > > > dovecot23 packages have tcpwrap support for el7: So is el8 truly incompatible with tcpwrap? Or is it just too

On Fri, 2018-05-25 at 09:41 +0300, Jani Nikula wrote: > On Thu, 24 May 2018, Joe Perches <joe at perches.com> wrote: > > There is currently a mixture of octal and symbolic permissions uses > > in files in drivers/gpu/drm and one file in drivers/gpu. > > > > There are ~270 existing octal uses and ~115 S_<FOO> uses. > > > > Convert all the

The story of this problem, AFAIK, is that Solaris 8 YASSP and JASS and vigilant/paranoid sysadmins have been known to set a restricitve umask in /etc/default/login. OpenSSH compatibility for Solaris 8 has been spotty at times for sparcv9 targets. This time, when a sparcv9 binary tries to sscanf(3C) the numeric umask as a long octal and put it in a mode_t, SIGBUS happens. What this looks like in

I agree - we should use only hex or octal, but not mixed. Cheers, Silvia. On Sat, May 31, 2008 at 2:20 AM, Ivo Emanuel Gon?alves <justivo at gmail.com> wrote: > I received the following comment regarding the table: > >> The table contains a mix of octal and hexadecimal 'escape sequences' >> for non-printable / non-ASCII octets. >> I strongly suggest to only

Hello, http://llvm.org/docs/TableGen/LangIntro.html says I can use octal integer value (indicated by a leading 0). In fact the number is converted to decimal. With best regards, Romick.

Hi, I ran into an odd problem with the print command for R-2.0 on a windows machine. The icelandic character thorn (??,??) which is included in in the Latin-1 character set [iso/8859-1 char# 222 (upper case) and #254 (lower case)] prints out incorrectly. Instead of getting the correct character I get the octal codes for upper and lower case thorn (\336 or \376). This only happens on a windows

----- Original Message ----- > From: "Rowland Penny" <rowlandpenny241155 at gmail.com> > To: samba at lists.samba.org > Sent: Wednesday, August 12, 2015 1:46:53 AM > Subject: Re: [Samba] ACLs on Samba share not preserved when copying with Windows Explorer > > >> > > Hi Rowland, > > > > This Samba 3 server is joined to a Samba 4 AD domain

Sorry bugging you for this simple command. ls command displays question marks for the local characters (ones not included in 8859-1 space) in filenames. ie. [root at server aa]# touch ?arp [root at server aa]# ls ??arp [root at server aa]# ls -b #for octal escapes \303\247arp [root at server aa]# However, ls|less, ls|more or vi <directory name> all display filename

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=489 netfilter@linuxace.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |netfilter@linuxace.com Status|NEW |RESOLVED Resolution|

Is there a straightforward way to convert character information from decimal representation to the octal one used by R? I'd like something like a function ascii(number,base=10), such that > ascii(91) [1] "\133" I can easily do the mapping from 91 to 133, but what is a good way to operate on 133 to deliver "\133"? Would a lookup table be a better solution? David

Hi Rich, I ran this command to spot a few typos: git ls-files|misspellings -f -|grep -v '^po' Here are fixes: >From ec62fad96cc2884c8fd43ecb550a8bcac317cca0 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Wed, 18 Apr 2012 11:15:57 +0200 Subject: [PATCH libguestfs] maint: fix doc typos Fix typos spotted by http://github.com/lyda/misspell-check. *

https://bugzilla.netfilter.org/show_bug.cgi?id=1363 Bug ID: 1363 Summary: nft: invalid octals silently parsed as zero Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at

----- Original Message ----- > From: "Rowland Penny" <rowlandpenny241155 at gmail.com> > To: samba at lists.samba.org > Sent: Tuesday, August 11, 2015 2:19:09 PM > Subject: Re: [Samba] ACLs on Samba share not preserved when copying with Windows Explorer > > Hi, is the share stored on a standalone server or an AD member server or > what ? > > Not that

Hi Rich, I've updated hivex to use the latest from gnulib and fixed a few syntax-check failures. With these changes, almost all of "make distcheck" succeeds. (details coming separately) >From c6300c44a1eda1a55a23249fde94882ea5a1c430 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Tue, 28 Aug 2012 11:28:40 +0200 Subject: [PATCH hivex 1/2] maint:

Hello :-) According to my reading of the rsyncd.conf man page, "incoming chmod" accepts comma-separated "chmod" strings as defined by the chmod(1) man page optionally prefixed by D or F to make them apply to directories or files. The local chmod(1) man page does not mention strings. It refers to modes which may be symbolic or octal/numeric. Accordingly I tried incoming

I found (and fixed) a problem with my realtek onboard 8139 controller. dhcpd server sends filename "pxelinux.0" but realtek requests "pxelinux.0\377" (i.e. the octal character 377 is appended), resulting in a file not found during the tftpd phase. I fixed this by adding a mapping to tftpd: # strip ending garbage from filenames (Realtek PXE bug) r ^([[:graph:]]*)(.+)$ \1

Hi all, Is there any more exhaustive explanation on this command? find / -type f -perm -2. Someone said that it means to find all files which have 'other' write access. From the man page it only says: -perm mode File?s permission bits are exactly mode (octal or symbolic). Symbolic modes use mode 0 as a point of departure. -perm -mode All of the permission bits mode are set for the