Correct, NIS has a protocol limitation which limits you to 1024.
The netid map is used to associate groups to users. For local things you
might need to grow the group lines but then you can create valid group
files which cannot be imported in NIS.
Casper
>CR #6800113 ("We need a /usr/xpg4/bin/printf utility for SUS
>conformance")
Is there a incompatibility between xpg4 printf and /usr/bin/printf?
Casper
>
>- The only difference between /usr/bin/printf and /usr/xpg4/bin/printf
>is
> that /usr/bin/printf's "%s" precision option counts in screen columns
> for SystemV backwards compatibity (e.g. a "screen column" means a
> character which only spans one column - there are multibyte characters
> w
>
>Hi!
>
>
>
>This is a sponsor request to fix CR #6807179 ("ksh93 does unneccesary
>|libc::getpwnam()| lookups for ~(modifer)pattern patterns")
>
>My contributor ID is "OS0025".
>
>Webrev can be found at
>http://cr.opensolaris.org/~gisburn/ksh93_integration_cr_6807179_001/
>(matching ksh93 te
>Casper.Dik at Sun.COM wrote:
>> >This is a sponsor request to fix CR #6807179 ("ksh93 does unneccesary
>> >|libc::getpwnam()| lookups for ~(modifer)pattern patterns")
>> >
>> >My contributor ID is "OS0025".
>> >
>> >Webrev can be found at
>> >http://cr.opensolaris.org/~gisburn/ksh93_integration_c
>Casper.Dik at Sun.COM writes:
>> So, if I can have some codereviewers then I can putback this change to
>> build 110.
>
>The 'suggested fix' in CR 6807179 doesn't seem to match this fix -- it
>includes a new test for the getpwnam problem, plus some other changes
>to alias.c. Is the webrev out of
>Avinash Joshi wrote:
>> I just wanted to know how to rename a directory.
>> For moving the dir, there is a built in function ret =
>> move_dir(pstruct->pw_dir, dir, logname); which is defined in
>> usr/src/cmd/oamuser/user/movedir.c
>>
>> Is there a similar function that renames a directory?
>
>On Thu, Feb 14, 2008 at 08:04:57PM +0530, Rishi M Nair wrote:
>> --- byteorder.h.orig Tue Oct 2 19:44:36 2007
>> +++ byteorder.h Thu Feb 14 17:53:39 2008
>> @@ -50,6 +50,17 @@
>> #include
>> #endif
>>
>> +#ifndef htonll
>> +#ifdef _BIG_ENDIAN
>> +#define htonll(x) (x)
>> +#define nto
>This is prob. overkill in this situation... since the main loop
>will only do stdio just before exiting, it could set
>signal handlers to SIG_IGN before doing any IO which should
>prevent any problems from arising.
Why not use snprintf and write?
Casper
>Note that SA_RESTART must be set; otherwise dd from a pipe or other slow
>device will return an error condition. I also like Casper's suggestion
>to use sprintf and write to stderr, since sprintf is now
>async-signal-safe.
Note also that there are three gettext()s of constant strings;
these sh
>Hello,
>
>request sponsor for #4890717 want append-only files.
>
>I have a working prototype where the administrator can put a zfs fs
>into "append only" mode by setting the zfs "appendonly" property to
>"on" using zfs(1M).
>
>"append only" mode in this case means
>
>1. Applications can only appe
>We're having some discussions about various ways of implementing "append
>only". There are some requirements around Sarbanes-Oxley about
>append-only *files*, and the possibility of using ACLs to specify
>append-only permissions. However, there may also be some use cases for
>append-only *f
>"Every day we are archiving documents. At the end of the day we want
>to freeze the filesystem. Would it be possible to add a time-lock
>property to ZFS? Could this be extended to still allow new files to be
>added to the locked file system , but not allowing to add/modify files
>(ZFS ACL's could
>I am told that there may be a synaptics driver in casper's frkit. If
>so, I've not checked it out yet. Our driver just behaves as a vuid
>module. (Casper, can you comment on this?)
That driver replaced the Xorg mouse_drv.so module.
>We also have a very nice Tcl/Tk configuration and test UI, t
>Well, I've never _seen_ a Ferrari laptop. But our systems have a 4
>scroll buttons, plus the normal 3 buttons, giving a total of 7 buttons.
>They all work.
Pretty much like the Ferrari.
>> The reason why I originally id my driver was the ability to use the
>> buttons then the next feature was
>Yes, our driver supports that.
>
>> I very much like that feature and implemented it in my driver.
>>
>> Also, do your scroll buttons auto-repeat? (I know that the touchpad
>> does not so you have to fake it)
>>
>
>I have to check into that, because I'm not sure.
The last feature request I
>Our driver supports it.
Excellent.
(These are all feature requests I got and (partially) implemented for
my driver, so I htink they're important for customers)
Casper
>On Mon 23 Oct 2006 at 05:40PM, Casper.Dik at Sun.COM wrote:
>>
>>
>> >Our driver supports it.
>>
>> Excellent.
>>
>> (These are all feature requests I got and (partially) implemented for
>> my driver, so I htink they're important for customers)
>
>So Casper, you're sponsoring this, right?
C
>Why, other than the returning an error we already have 5 such privileges
>in the basic set. Now in each of those cases (proc_info, proc_session,
>proc_fork, proc_exec, file_link_any) there is a way to return an error
>for sync(2) but there is for 'lockfs -f'.
And it's exactly what the basic
>/solarisws/usr/src/cmd/mv/mv.c
>
>this problem exist for unix domain sockets since 'mknod' cannot be used to
>create socket files.
>
>fix is, to check whether the file is a unix domain socket or not.
>
>note :value for S_IFSOCK = c000(hex) 'socketfile'
>_
>
>Bug ID Number1 : *6569630*
>synopsis: Vi cannot append text to named buffers
>category : *utility
>s*ubcategory : *editor
>*description : In Single Unix Specification version 2 and 3 vi is required
>that if a named buffer is specified with an upper-case letter, then the
>text from a yank
>> My personal stance on this one is that it'd be a good idea to report the
>> mountpoint instead of the device major/minor. What did you have in mind ?
>
>Here's what I was thinking:
>
>--- a/usr/src/uts/common/os/exec.c Mon Oct 08 20:24:50 2007 -0700
>+++ b/usr/src/uts/common/os/exec.c
>On 9/1/07, Roland Mainz wrote:
>> "Richard L. Hamilton" wrote:
>>
>> > > This is a sponsor request to implement the RFE/CR
>> > > #6451262 ("RFE:
>> > > /usr/bin/sleep should support floating-point values"
>> > > -
>
>considering that /usr/gnu/bin/sleep already does that, how important
>it is to
>
>I'd like to request a sponsor for this enhancement:
>
>===
>*Synopsis*: zlogin: Add a "-z zonename" option
>http://bt2ws.central.sun.com/CrPrint?id=6536837
>
>
>*Change Request ID*: 6536837
>
>*Synopsis*: zlogin: Add a "-z zonename" option
>
> Product: solaris
> Category: opensolaris
> Subca
> * But I am suggesting we add a "-z" option so that:
>
>zlogin -z THEHOST [other commands]
>
>...is equivalent to:
>
>zlogin THEHOST [other commands]
How are you supposed to make this work?
How do you propose to make it work, given that the following should work:
zlogin
>
>> * But I am suggesting we add a "-z" option so that:
>>
>>zlogin -z THEHOST [other commands]
>>
>>...is equivalent to:
>>
>>zlogin THEHOST [other commands]
>
>
>How are you supposed to make this work?
>
>
>How do you propose to make it work, given that the following should work:
>
>I threw pfzsh together yesterday afternoon using the SFW framework, and
>would like to request a sponsor to evaluate my work and help me get it
>integrated.
>
>I note that the CR is currently assigned to Casper Dik and so he is
>CC'd, but I don't expect that he will necessarily volunteer for the
>Hi Carol,
>
>Now , I have come to know that Ctrl-D doesnot generate a signal but signals
>EOF.
>So , i made the following changes in the code again.
>
>*
>
>char *getresponse(char *oldval)
>{
>
>Darren J Moffat wrote:
>> Roland Mainz wrote:
>>> Hi!
>>>
>>>
>>>
>>> Requesting sponsor for CR# 6488593 ("/etc/profile should set TMPDIR to
>>> /tmp/$LOGNAME/") - patch is included in the RFE...
>>
>> This will I believe need an ARC case since it is a change in default
>> behaviour. It a
>Yeah, you'll notice that if you try to su to root and run installers
>that run pkgadd internally. I use this method, and the StarOffice 8
>installer failed quite mysteriously until I realized it was just an
>instance of that problem and reset TMPDIR to something else.
This, unfortunately, ki
>> Assuming we do steps 1 and 2 above, do we get into any problems with
>> POSIX compliance if the default basic privilege set does not include
>> PRIV_SYS_SYNC?
There is no such thing as a "default basic set".
There's a "basic set" and there's the "default set" users get when
they login; they
>Casper.Dik at Sun.COM wrote:
>>
>> >Yeah, you'll notice that if you try to su to root and run installers
>> >that run pkgadd internally. I use this method, and the StarOffice 8
>> >installer failed quite mysteriously until I realized it was just an
>> >instance of that problem and reset TMPDIR
>I disagree. The flat layout in /tmp for all temporary files of all users
>is very very annoying for both admins and users. I doubt mode 1777 is
>"insecure" (yes, you can always craft a case where it goes wrong...).
Why? I hard ever look in /tmp.
OTOH, GNOME already dumps 3 or four temporary di
>hello,
>
>i'm looking for a sponsor for the CR mentioned in the subject. a patch
>can be found here:
>
> http://itanic.attenuate.org/~river/1218270.diff
>
>my contributor agreement # is OS0050.
I'll take it (this behaviour just happened to bite me again yesterday)
Casper
>Due to the 32-bit ABI's stdio file descriptor limit, an interposer is
>being used to F_DUPFD non-stdio file descriptors to 256 and above. This
>mitigates a problem with 3rd party modules and plugins that use
>fopen(3C), et al. streams in processes such as Apache HTTP Server that
>open a large num
>Casper.Dik at Sun.COM wrote:
>> >Due to the 32-bit ABI's stdio file descriptor limit, an interposer is
>> >being used to F_DUPFD non-stdio file descriptors to 256 and above. This
>> >mitigates a problem with 3rd party modules and plugins that use
>> >fopen(3C), et al. streams in processes such as
>Requesting a sponsor for 6410382 ZFS rename should update ->v_path.
I'll take this, but I think it may not be as simple as the
bug report suggests. Is the individual filesystem layer not the
wrong place to do this? (We end up doing it in ZFS, UFS, NFS, tmpfs,
etc; why is this not done in fop_
>> On Thu, Sep 01, 2005 at 11:18:50AM -0700, J?rgen Keil wrote:
>>
>> > See http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6317146
>> >
>> > The workaround section contains the suggested fix.
>>
>> I've got this one.
>
>This request for sponser can now be canceled. snv_28 includes
38 matches
Mail list logo
