Turbo Fredriksson <[EMAIL PROTECTED]> writes:
> Sure, no prob, IF I know what the differences are... :)
Assuming you have libc6-dev and libc5-altdev installed,
/usr/include/utmpbits.h has the new structure, and
/usr/i486-linuxlibc1/include/utmp.h has the old structure.
The new structure has many
On 13 Dec 1997, Guy Maor wrote:
> oh, yuck. You're just going to have to rewrite your routines to use
> the new structure.
Thing is, I _THINK_ I'm already using the new structure, but I don't know
for sure...
> I'm sure you can figure out a way to dynamically
> determine which type of structur
[EMAIL PROTECTED] (Guy Maor) wrote on 13.12.97 in <[EMAIL PROTECTED]>:
> Turbo Fredriksson <[EMAIL PROTECTED]> writes:
>
> > Sorry... I'm using perl, and these functions are not avalible.. *sigh*
>
> oh, yuck. You're just going to have to rewrite your routines to use
> the new structure. I'm su
On Dec 12, Turbo Fredriksson wrote
> On 12 Dec 1997, Andreas Jaeger wrote:
>
> > Just use the libc functions setutent/getutent. They're available in
> > both libc5 and glibc2.
>
> Sorry... I'm using perl, and these functions are not avalible.. *sigh*
[...]
> *sigh* What can a poor perl proggramme
Turbo Fredriksson <[EMAIL PROTECTED]> writes:
> Sorry... I'm using perl, and these functions are not avalible.. *sigh*
oh, yuck. You're just going to have to rewrite your routines to use
the new structure. I'm sure you can figure out a way to dynamically
determine which type of structure is bei
On 12 Dec 1997, Andreas Jaeger wrote:
> Just use the libc functions setutent/getutent. They're available in
> both libc5 and glibc2.
Sorry... I'm using perl, and these functions are not avalible.. *sigh*
> If you're never writing/reading the files
> directly (opening them), you don't have proble
> Scott Ellis writes:
Scott> On Fri, 12 Dec 1997, Turbo Fredriksson wrote:
>> On Fri, 12 Dec 1997, Scott Ellis wrote:
>> [...]
>> How do I know which type of utmp/wtmp I'm currently using, my package
>> 'TCPQuota' is using utmp to find out the users online... That is, when
>> (exactly) did the
On Fri, 12 Dec 1997, Scott Ellis wrote:
> The change in utmp was made when libc6 was released. If your program is
> libc6, the libc6 utmp/wtmp functions should be used at all times.
I'm using perl, reading the utmp 'raw'... (using unpack(), if that's
familiar)... Is it 'login' (etc) one should l
On Fri, 12 Dec 1997, Turbo Fredriksson wrote:
> On Fri, 12 Dec 1997, Scott Ellis wrote:
>
> > Corruption of utmp/wtmp is a MINOR PROBLEM. Many people don't care if the
> > file is corrupted, they just want to use some libc6 stuff without being
> > forced completely into libc6.
>
> How do I kn
On Fri, 12 Dec 1997, Scott Ellis wrote:
> Corruption of utmp/wtmp is a MINOR PROBLEM. Many people don't care if the
> file is corrupted, they just want to use some libc6 stuff without being
> forced completely into libc6.
How do I know which type of utmp/wtmp I'm currently using, my package
'T
On 11 Dec 1997, Guy Maor wrote:
> "Scott K. Ellis" <[EMAIL PROTECTED]> writes:
>
> > I'm sick of trying to find a useful workaround for people who just
> > want to install a few packages from hamm without upgrading the whole
> > thing.
>
> There isn't one. I assumed you, as libc5-to-libc6 maint
On 12 Dec 1997, Martin Mitchell wrote:
> "Scott K. Ellis" <[EMAIL PROTECTED]> writes:
>
> > Still doesn't solve the problem of the hamm libc5 conflicting with
> > libc5-dev and the bo libc5 conflicting with libc6. It is a compilation of
> > different breakages here. My concern is for people who
"Scott K. Ellis" <[EMAIL PROTECTED]> writes:
> I'm sick of trying to find a useful workaround for people who just
> want to install a few packages from hamm without upgrading the whole
> thing.
There isn't one. I assumed you, as libc5-to-libc6 maintainer, knew
that.
Yes, it is theoretically pos
"Scott K. Ellis" <[EMAIL PROTECTED]> writes:
> Still doesn't solve the problem of the hamm libc5 conflicting with
> libc5-dev and the bo libc5 conflicting with libc6. It is a compilation of
> different breakages here. My concern is for people who still want to do
> libc5 development WITH THEIR N
On 12 Dec 1997, Martin Mitchell wrote:
> "Scott K. Ellis" <[EMAIL PROTECTED]> writes:
>
> > > Huh? The upgrade path is quite clear: install a newer libc5 (5.4.33-7)
> > > from hamm, then you may install libc6.
> >
> > The solution isn't quite so simple. The libc5 from hamm DEPENDS ON libc6.
> >
"Scott K. Ellis" <[EMAIL PROTECTED]> writes:
> > Huh? The upgrade path is quite clear: install a newer libc5 (5.4.33-7)
> > from hamm, then you may install libc6.
>
> The solution isn't quite so simple. The libc5 from hamm DEPENDS ON libc6.
> There is a definate problem here.
You install both h
On 12 Dec 1997, Martin Mitchell wrote:
> Chris Fearnley <[EMAIL PROTECTED]> writes:
>
> > debian/bo/binary-i386/base/libc5_5.4.33-6.deb conflicts with libc6
> > making it IMPOSSIBLE to upgrade!! I had to downgrade to
> > libc5_5.4.33-3.deb from a LSL CD (thank goodness this bug is not
> > shippe
17 matches
Mail list logo
