For me,
export LD_LIBRARY_PATH=/usr/lib/libc5-compat; /usr/games/quake2
helps to resolve this problem.
On Sat, Jun 06, 1998 at 10:09:26PM +1200, Michael Beattie wrote:
> > >> After my fun experience upgrading to hamm, everything has been goin well,
> > >> but I have had one problem. After upgradi
In debian-user Torsten wrote:
>
>For a directory the set t-flag means that only the owner of a file may
>delete it.
Or the owner of the directory (but not the group of the
directory).
--
#includeLorens Kockum
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
On: Mon, 08 Jun 1998 09:57:10 -0500 Ed Cogburn writes:
> Is there a man page/info/FAQ that explains this? Is this why its
> referred to as 'sticky' or am I thinking of something else.
See the info page on Fileutils/File permissions/Mode structure. The
sticky bit is the t-bit for files and is pr
Torsten Hilbrich wrote:
>
> On: Sun, 07 Jun 1998 05:49:18 -0500 Ed Cogburn writes:
>
> >> > drwxrwxrwt 6 root root 6144 Jun 6 14:07 /tmp/
> >> >
> >> > If this is not how it is do a 'chmod 1777 /tmp' as root.
> >>
> >> Thanks! I got it before, but whats the 't'?? (all execute bit)
On Sun, 7 Jun 1998, Jaakko Niemi wrote:
> >> On Sat, 6 Jun 1998, Jaakko Niemi wrote:
> >>
[snip]
> >>
> >> I was told a fix for this was an ldconfig . It worked for me, and
> >> everything is fine now... except.. (who knew that was coming?)
>
> Didn't work for me. But it is now working with th
On: Sun, 07 Jun 1998 05:49:18 -0500 Ed Cogburn writes:
>> > drwxrwxrwt 6 root root 6144 Jun 6 14:07 /tmp/
>> >
>> > If this is not how it is do a 'chmod 1777 /tmp' as root.
>>
>> Thanks! I got it before, but whats the 't'?? (all execute bit)
>> typo, or what is it?
> 't' is a spec
Michael Beattie wrote:
> hmmm only this:
>
> libm.so.5 => /lib/libm.so.5 (0x4000a000)
> libvga.so.1 => /usr/lib/libc5-compat/libvga.so.1 (0x40013000)
> libc.so.5 => /lib/libc.so.5 (0x4004f000)
>
>
> but an ldconfig fixed it.. thanks!
My memory's shakey, but I think I fi
>> On Sat, 6 Jun 1998, Jaakko Niemi wrote:
>>
>> > >> After my fun experience upgrading to hamm, everything has been goin
>> > >> well,
>> > >> but I have had one problem. After upgrading svgalib, squake seg faults
>> > >> when started. (so does quake2) Is there a problem with svgalib?
>> > >>
>
Michael Beattie wrote:
>
> On Sat, 6 Jun 1998 [EMAIL PROTECTED] wrote:
>
> > On 7 Jun, Michael Beattie wrote:
> >
> > > btw: Pine can only open my mailbox readonly after hamm upgrade. what
> > > gives?
> >
> >
> > Check your permissions on /tmp. Most mail readers use tmp to store a
> > copy of
On Sat, 6 Jun 1998 [EMAIL PROTECTED] wrote:
> On 7 Jun, Michael Beattie wrote:
>
> > btw: Pine can only open my mailbox readonly after hamm upgrade. what
> > gives?
>
>
> Check your permissions on /tmp. Most mail readers use tmp to store a
> copy of the mail file and if it can't write to tmp
On 7 Jun, Michael Beattie wrote:
> btw: Pine can only open my mailbox readonly after hamm upgrade. what
> gives?
Check your permissions on /tmp. Most mail readers use tmp to store a
copy of the mail file and if it can't write to tmp then it can't modify
your mail spool and hence makes it read
[EMAIL PROTECTED] (Michael Beattie) writes:
[snip: quake crashing after hamm upgrade]
> I was told a fix for this was an ldconfig . It worked for me, and
> everything is fine now... except.. (who knew that was coming?)
This probably makes it a bug in svgalib.
> I dont know where the problem is,
On Sat, 6 Jun 1998, Shaleh wrote:
> The ldconfig was needed do to a bug in the next to the last release of
> the svga lib package.
I am sorry, I dont understand, what do you mean here?
> The maintainer helped w/ that one. I have no
> problems w/ sound. Is the permission on the audio devices o
On Sat, 6 Jun 1998, Edward Betts wrote:
> On Sat, 06 Jun, 1998, Michael Beattie wrote:
> > On Sat, 6 Jun 1998, Jaakko Niemi wrote:
> >
> > I was told a fix for this was an ldconfig . It worked for me, and
> > everything is fine now... except.. (who knew that was coming?)
> >
> > I am still havin
On Sat, 06 Jun, 1998, Michael Beattie wrote:
> On Sat, 6 Jun 1998, Jaakko Niemi wrote:
>
> I was told a fix for this was an ldconfig . It worked for me, and
> everything is fine now... except.. (who knew that was coming?)
>
> I am still having trouble with sound in squake and quake2.
>
> I dont
The ldconfig was needed do to a bug in the next to the last release of
the svga lib package. The maintainer helped w/ that one. I have no
problems w/ sound. Is the permission on the audio devices ok and does
sound work elsewhere?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Sat, 6 Jun 1998, Jaakko Niemi wrote:
> >> After my fun experience upgrading to hamm, everything has been goin well,
> >> but I have had one problem. After upgrading svgalib, squake seg faults
> >> when started. (so does quake2) Is there a problem with svgalib?
> >>
> >> svgalib-bin 1.2.13-3.2
>> After my fun experience upgrading to hamm, everything has been goin well,
>> but I have had one problem. After upgrading svgalib, squake seg faults
>> when started. (so does quake2) Is there a problem with svgalib?
>>
>> svgalib-bin 1.2.13-3.2
>> svgalibg11.2.13-3.2
>> svgalib1 1.2.13-
On Fri, 5 Jun 1998 [EMAIL PROTECTED] wrote:
> I recently ran into this. On my box, svgalib was crosslinked to libc6 -- so
> quake was linked to both libc5 and 6 so it segfaulted. To see if this has
> happened to you run ldd on your quake binary like this:
> ldd /usr/games/squake.real. If you
I recently ran into this. On my box, svgalib was crosslinked to libc6 -- so
quake was linked to both libc5 and 6 so it segfaulted. To see if this has
happened to you run ldd on your quake binary like this:
ldd /usr/games/squake.real. If you see libc5 and libc6 then you have the bad
lib package
After my fun experience upgrading to hamm, everything has been goin well,
but I have had one problem. After upgrading svgalib, squake seg faults
when started. (so does quake2) Is there a problem with svgalib?
svgalib-bin 1.2.13-3.2
svgalibg11.2.13-3.2
svgalib1 1.2.13-3.2
quake2 3
21 matches
Mail list logo