hi,
i am, mayur kulkarni, studying final year of computer science and engg.
i am interested to contribute to hurd.
i am using it.
please mail me what to do.
i will take as small project
thanking you.NEVER DENY HIS EXISTANCE...
Yahoo! India Insurance Special: Be informed on the best polic
I'm a bit confused about the padding that we add to the core note
segment in elfcore.c, it seems that it is 8 bytes long. If that is
the case, then I really can't see any problems in the reading code,
here is a small bit from my debug session:
,
| Breakpoint 3, elfcore_grok_lwpstatus (abfd=0x
On Fri, Feb 13, 2004 at 10:56:32PM +0100, Marco Gerards wrote:
> Marcus Brinkmann <[EMAIL PROTECTED]> writes:
>
> > In the future, please either build yourself a Debian package of the Hurd, or
> > use make install DESTDIR=... (if that works, otherwise prefix=...) and copy
>
> These two files and
>>This is clearly wrong, it being zero. This suggests to me that
>>elfcore_grok_lwpstatus still does not have
>>HAVE_LWPSTATUS_T_PR_FPREG. Can you check that again?
>>
>> Yes, it is defined and all.
>
>Then you will have to step through that function to see w
> I was thinking more along the lines so that the user will know that
> he/she is using a old version of libc. Because otherwise we would
> have to add each feature we depend on into our configure.in.
Or just write it off.
___
Bug-hurd mailing list
[E
Why not just mentioning the required version/date of glibc in
INSTALL?
It already says:
|The Hurd version 0.2 has been verified to work with versions 2.0.3
|and 2.0.4 of the GNU C library. (But note that version 2.0.3 has
|some easily-fixed bugs in compilation for the i386-gnu
Ognyan Kulev wrote:
http://debian.fmi.uni-sofia.bg/~ogi/hurd/ext3fs/ext2fs_20040211.txt
New snapshot:
http://debian.fmi.uni-sofia.bg/~ogi/hurd/ext3fs/ext2fs_20040213.txt
It includes "public" interface that is used by EXT2 code. No
description of internals yet, neither description of libpager chan
On Fri, Feb 13, 2004 at 08:24:58PM +0100, Alfred M. Szmidt wrote:
>> I was thinking more along the lines so that the user will know
>> that he/she is using a old version of libc. Because otherwise we
>> would have to add each feature we depend on into our
>> configure.in.
>
>O
,
| (top-gdb) x/480 note->descdata
| 0x82bf854: 0x 0x 0x 0x
| 0x82bf864: 0x 0x 0x001f 0x001f
| 0x82bf874: 0x001f 0x001f 0x 0x0003
| 0x82bf88
> I was thinking more along the lines so that the user will know
> that he/she is using a old version of libc. Because otherwise we
> would have to add each feature we depend on into our
> configure.in.
Or just write it off.
If you mean that it is not worth it, then maybe. But th
There is no reason to do version checks. If you check for
anything, you check for the features you need.
I was thinking more along the lines so that the user will know that
he/she is using a old version of libc. Because otherwise we would
have to add each feature we depend on into our conf
There is no reason to do version checks. If you check for anything, you
check for the features you need.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Quoting "Alfred M. Szmidt" <[EMAIL PROTECTED]>:
>> > GNU tar also supports POSIX archives since some months. I
>> > wrote a patch for GNU tar to support passive translators
>> > (GNU.translator). It should not be too hard to support this on
>> > GNU/Linux as well.
>>
>>
eagle relaxation leaden
madras meson mitosis quadrant congratulatory salaam transferred flatulent
statesmen credential biota horoscope banister tampon edit superb biochemic
legacy polemic cavern ,euridyce yea broomcorn kinesic acquisitive invidious
bridegroom stipulate earthquake
> > GNU tar also supports POSIX archives since some months. I
> > wrote a patch for GNU tar to support passive translators
> > (GNU.translator). It should not be too hard to support this on
> > GNU/Linux as well.
>
> If you reformulate it as generic xattr support that interoper
Honestly, I would prefer that we just require pretty darn new libc
for use with hurd. But if that is really an imposition, using
#ifdef is fine for this. There is no great loss in just disabling
the new functionality.
I don't see any problems with this, the Hurd and glibc are quite
t
Quoting Roland McGrath <[EMAIL PROTECTED]>:
> > GNU tar also supports POSIX archives since some months. I wrote a patch
> > for GNU tar to support passive translators (GNU.translator). It should
> > not be too hard to support this on GNU/Linux as well.
>
> If you reformulate it as generic xattr
> GNU tar also supports POSIX archives since some months. I wrote a patch
> for GNU tar to support passive translators (GNU.translator). It should
> not be too hard to support this on GNU/Linux as well.
If you reformulate it as generic xattr support that interoperates with
star's archives, then
Roland McGrath wrote:
If people find this useful, then I can try my luck at getting this
incorporated into Linux.
It's definately useful! And using xattr interface looks like very clean
approach.
Regards,
ogi
___
Bug-hurd mailing list
[EMAIL PROTECTE
Quoting Roland McGrath <[EMAIL PROTECTED]>:
> This makes it possible to use a GNU/Linux system to not only create but
> also populate a Hurdish ext2 filesystem complete with passive translator
> settings so that it can boot the Hurd normally. It also makes it possible
> to back up and restore a H
20 matches
Mail list logo
