On 06.11.11 03:18, James Carlson wrote:
On 11/5/11 5:40 AM, Andrey N. Oktyabrski wrote:
On 04.11.11 14:14, James Carlson wrote:
I'd say #1. ...
So it is a lot of words in the justification of not to change anything
in the OI/Illumos...
That's not entirely true. If someone wants to change OI
On 11/5/11 5:40 AM, Andrey N. Oktyabrski wrote:
> On 04.11.11 14:14, James Carlson wrote:
>> I'd say #1. ...
> So it is a lot of words in the justification of not to change anything
> in the OI/Illumos...
That's not entirely true. If someone wants to change OI to make things
better for this appli
On 04.11.11 14:14, James Carlson wrote:
I'd say #1. ...
So it is a lot of words in the justification of not to change anything
in the OI/Illumos...
Anyway, thanks for your opinion :-) You have lighted some non-trivial
aspects.
___
OpenIndiana-disc
Andrey N. Oktyabrski wrote:
> On 03.11.11 16:22, James Carlson wrote:
>> Andrey N. Oktyabrski wrote:
>>> More about e2fsprogs. Now from the pkgsrc. There is a same bug as here:
>>> http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45499
>>>
>>> Is it correct to expect ifr_hwaddr member in i
On 03.11.11 16:22, James Carlson wrote:
Andrey N. Oktyabrski wrote:
More about e2fsprogs. Now from the pkgsrc. There is a same bug as here:
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45499
Is it correct to expect ifr_hwaddr member in ifreq structure if
SIOCGIFHWADDR defined?
It
Andrey N. Oktyabrski wrote:
> More about e2fsprogs. Now from the pkgsrc. There is a same bug as here:
> http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45499
>
> Is it correct to expect ifr_hwaddr member in ifreq structure if
> SIOCGIFHWADDR defined?
It might be correct on some platform
More about e2fsprogs. Now from the pkgsrc. There is a same bug as here:
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45499
Is it correct to expect ifr_hwaddr member in ifreq structure if
SIOCGIFHWADDR defined?
___
OpenIndiana-discuss mai
On 28.10.11 23:11, James Carlson wrote:
Perhaps, it is necessary to remove unusable headers from system?
Well, much luck in that. Years ago at Sun, I filed a bug on it, and I
had lengthy discussions with some of the senior architects while trying
to find a way to address it. I never really di
James Carlson writes:
> If one were malicious, it'd be a way to catch people who write code
> without reading the documentation. :-/
You mean, like the stupid passcode you need to specify when you
want to apply the Recommended patch cluster? :-(
> I also tried removing headers that were utterly
On 28.10.11 18:26, Alan Coopersmith wrote:
(Cite from:
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45491)
The problem is that on OI-151 EXT2_IOC_GETFLAGS is defined as
_IOR('f', 1, long)
where _IOR is defined in drm/drm.h which is not included.
drm.h defines it only as a compatib
Andrey N. Oktyabrski wrote:
> On 28.10.11 18:29, James Carlson wrote:
>> You might have an argument that e2fsprogs shouldn't include this header
>> file. Most projects (for what it's worth) just toss in the kitchen sink
>> -- anything that's built is shipped, even if it's not normally useful
>> fo
On 28.10.11 18:29, James Carlson wrote:
pkg:/system/file-system/e2fsprogs@1.41.14-0.151.1
That doesn't come with the system. It's part of OI-SFE.
Looking over the software, it doesn't look to me like anyone should
assume that if the header files are present, then the kernel bits are
present a
Andrey N. Oktyabrski wrote:
> On 28.10.11 16:29, James Carlson wrote:
>>> In which bug tracker I must create a bug report for this issue?
>>>
>>> The problem is that on OI-151 EXT2_IOC_GETFLAGS is defined as
>>> _IOR('f', 1, long)
>>> where _IOR is defined in drm/drm.h which is not included.
On 10/28/11 03:45, Andrey N. Oktyabrski wrote:
Good day.
In which bug tracker I must create a bug report for this issue?
(Cite from: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45491)
The problem is that on OI-151 EXT2_IOC_GETFLAGS is defined as
_IOR('f', 1, long)
where _IOR
On 28.10.11 16:29, James Carlson wrote:
In which bug tracker I must create a bug report for this issue?
The problem is that on OI-151 EXT2_IOC_GETFLAGS is defined as
_IOR('f', 1, long)
where _IOR is defined in drm/drm.h which is not included.
To me this looks like a bug in OpenIndiana.
On 10/28/11 06:45, Andrey N. Oktyabrski wrote:
> Good day.
>
> In which bug tracker I must create a bug report for this issue?
>
> (Cite from:
> http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45491)
>
> The problem is that on OI-151 EXT2_IOC_GETFLAGS is defined as
>
>
> _IOR('f'
Good day.
In which bug tracker I must create a bug report for this issue?
(Cite from: http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45491)
The problem is that on OI-151 EXT2_IOC_GETFLAGS is defined as
_IOR('f', 1, long)
where _IOR is defined in drm/drm.h which is not includ
17 matches
Mail list logo
