Re: [shell-discuss] Re: [osol-code] Coding (style) guidelines forshell scripts ?

2007-06-19 Thread Roland Mainz
James Carlson wrote: > Roland Mainz writes: > > * Be carefull with using TABS in script code, they are not portable > > between editors or platforms > > Could you clarify this one, please? > > Are you referring to the ASCII TAB (0x09) character? Yes... > If so, what's > not "portable" about it?

Re: [osol-code] dispq setup

2007-06-19 Thread Eric Saxe
Neale Ferguson wrote: As part of the startup of CPUs in mp_startup, struct cpu entries are created for CPUs (other than the boot cpu0). Each cpu area is zeroed and a call to disp_cpu_init() is made. It in turn calls cpu_dispqalloc() ... cpu_dispqalloc() is called fairly early in boot (main() =>

Re: [osol-code] dispq setup

2007-06-19 Thread johansen-osdev
Neale, I may be wrong, but it looks like you may have gotten confused by parallel code-paths. cpu_disqalloc() is called by disp_setup(). disp_setup() is only called by dispinit(), at platform initialization time, and by disp_add(), when you add a new scheduler class. The code that allocates a dis

[osol-code] dispq setup

2007-06-19 Thread Neale Ferguson
As part of the startup of CPUs in mp_startup, struct cpu entries are created for CPUs (other than the boot cpu0). Each cpu area is zeroed and a call to disp_cpu_init() is made. It in turn calls cpu_dispqalloc() which has the following loop: cpup = cpu_list; do {

Re: [osol-code] Re: utmp pad - reserved for future use or is it for something else?

2007-06-19 Thread Casper . Dik
>The reason that pad is being treated as hex is that invoke_utmp_update() >should have converted utm px->pad from binary to hex before invoking utmp_update. utmp_update really shouldn't have bothered about ut_pad in the first place. It is "reserved for future use"; i.e., it is not used at all

[osol-code] Re: utmp pad - reserved for future use or is it for something else?

2007-06-19 Thread Stacey Marshall
The reason that pad is being treated as hex is that invoke_utmp_update() should have converted utmpx->pad from binary to hex before invoking utmp_update. This message posted from opensolaris.org ___ opensolaris-code mailing list opensolaris-code@open

Re: [osol-code] When will |mkdirat()|&co. be available ?

2007-06-19 Thread Casper . Dik
> >The problem with this function is that it does not give you what you expect: >access to long path names. > >"/proc/self/fd/%d" is a symlink and for this reason, the whole path resolution >is still done as if you did call open(2) with the complete long path. No it is not a symlink; it's a "pre

Re: [osol-code] When will |mkdirat()|&co. be available ?

2007-06-19 Thread Joerg Schilling
[EMAIL PROTECTED] wrote: > Note, though, that much of the *at functions can be implemented as > follows: > > int > fchownat(int fd, const char *path, uid_t owner, gid_t group, int flag) > { > char *buf; > size_t len = snprintf(buf, 0, "/proc/self/fd/%d/%s", fd, path); > buf = all

[osol-code] Re: [osol-discuss] Does solaris support spin lock?

2007-06-19 Thread Casper . Dik
>Hi, > >> Does solaris have the similiar spin lock like linux spin_lock_t ? > >opensolaris-code is a much better place for this type of question. I've cc'ed it there instead of opensolaris-discuss. >The kernel provides both adaptive and spin locks, man mutex(9F) and >mutex_init(3C) and also take