On Sun, 2006-02-05 at 18:09 +1300, Timothy Musson wrote:
>
> I'm pretty sure that's all been moved to the Nautilus "File Properties"
> dialog.
>
> 1) Right-click on any file of the type you're interested in.
> 2) Select "Properties". The File Properties dialog will appear.
> 3) Use that dialog's
John W. M. Stevens, 2006-02-04 18:05:36:
> There used to be a tool (Called "File Types and Programs") that would
> allow me to associate verbs with nouns in my [GNOME] desktop (in other
> words, to associate a program with a given file type
> Does anybody know what happened to this capplet (progra
On Sat, 2006-02-04 at 22:24 +, Chris Lale wrote:
> John W. M. Stevens wrote:
>
> >On Sat, Feb 04, 2006 at 08:19:41PM +, Chris Lale wrote:
> >
> >
> >>Ralph Katz wrote:
> >>
> >>
> >>
> >>>On 02/02/2006 03:11 PM, John W. M. Stevens wrote:
> >>>
> >>>
> >>>
> >>>
> In the hel
John W. M. Stevens wrote:
On Sat, Feb 04, 2006 at 08:19:41PM +, Chris Lale wrote:
Ralph Katz wrote:
On 02/02/2006 03:11 PM, John W. M. Stevens wrote:
In the help for gnome, under:
10.2 Where to Find Preference Tools
It says that to find the File types and programs pref
On Sat, Feb 04, 2006 at 08:19:41PM +, Chris Lale wrote:
> Ralph Katz wrote:
>
> >On 02/02/2006 03:11 PM, John W. M. Stevens wrote:
> >
> >
> >>In the help for gnome, under:
> >>
> >>10.2 Where to Find Preference Tools
> >>
> >>It says that to find the File types and programs preference
> >>to
Ralph Katz wrote:
On 02/02/2006 03:11 PM, John W. M. Stevens wrote:
In the help for gnome, under:
10.2 Where to Find Preference Tools
It says that to find the File types and programs preference
tool, look under:
Applications → Desktop Preferences → Advanced → File types and programs
But
On 02/02/2006 03:11 PM, John W. M. Stevens wrote:
> In the help for gnome, under:
>
> 10.2 Where to Find Preference Tools
>
> It says that to find the File types and programs preference
> tool, look under:
>
> Applications → Desktop Preferences → Advanced → File types and programs
>
> But on S
Hi there,
] What I'm doing is running a pipe between two background processes. Opening
] pipe for reading and writing both fail "illegal seek". Does this qualify
] as "special requirements" ?
Not at all. Probably your program is trying some funny file-oriented
syscall on the pipe, so it fails.
On Fri, Apr 16, 1999 at 21:58:36 +0800, [EMAIL PROTECTED] wrote:
> What I'm doing is running a pipe between two background processes.
> Opening pipe for reading and writing both fail "illegal seek". Does this
> qualify as "special requirements" ?
No.
> In any event I'm curious now to know what t
On Fri, Apr 16, 1999 at 12:48:48PM +0200, J.H.M. Dassen wrote:
> On Fri, Apr 16, 1999 at 18:19:14 +0800, [EMAIL PROTECTED] wrote:
> > The strace log gives the following error
> > open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or
> > directory)
>
> > I checked the directory and
On Fri, Apr 16, 1999 at 18:19:14 +0800, [EMAIL PROTECTED] wrote:
> The strace log gives the following error
> open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or
> directory)
> I checked the directory and this file is definitely missing. Should this
> file be present
Not unless
On Wed, 2 Dec 1998, Curt Howland wrote:
> Many thanks, but...
>
>
> # dpkg -S /usr/lib/i486-linuxaout/libdb.so.1
> dpkg: /usr/lib/i486-linuxaout/libdb.so.1 not found.
>
>
> Anyone else want to take a stab at it? There are several
> packages that will not install due to this err
At 09:05 PM 12/2/98 -0800, Curt Howland wrote:
>> > After getting hacked over the holidays, I decided to upgrade
>> > to slink. I'm getting the following error:
>> >
>> > Setting up e2fsprogs (1.12-4) ...
>> > ldconfig: warning: can't open /usr/lib/i486-linuxaout/libdb.so.1 (No
>> > such file r dir
> > After getting hacked over the holidays, I decided to upgrade
> > to slink. I'm getting the following error:
> >
> > Setting up e2fsprogs (1.12-4) ...
> > ldconfig: warning: can't open /usr/lib/i486-linuxaout/libdb.so.1 (No
> > such file r directoryg
> >
> > There's nothing in that directory but
Hello:
On Wed, Dec 02, 1998 at 12:36:20PM -0800, Curt Howland wrote:
>
> After getting hacked over the holidays, I decided to upgrade
> to slink. I'm getting the following error:
>
> Setting up e2fsprogs (1.12-4) ...
> ldconfig: warning: can't open /usr/lib/i486-linuxaout/libdb.so.1 (No
> suc
On Tue, Mar 24, 1998 at 12:16:49PM -0500, Ben Pfaff wrote:
> It looks like I may have given you misleading advice, or advice that
> you have inadvertently misinterpreted. The Debian X Window System is
> set up slightly different from the standard XFree86 setup. The file
> /etc/X11/Xserver contain
I just did the exact same upgrade that you did for my Matrox Millenium II
AGP. Here are some pointers that may help you:
0. DO NOT setup a link from the server to "X." Debian uses the
/etc/X11/Xserver file to determine what X server to run. IIRC,
/usr/X11R6/bin/X is a SUID wrapper so that X ser
It looks like I may have given you misleading advice, or advice that
you have inadvertently misinterpreted. The Debian X Window System is
set up slightly different from the standard XFree86 setup. The file
/etc/X11/Xserver contains the full path to the X server as its first
line; /usr/X11R6/bin/X
Jason Westervelt <[EMAIL PROTECTED]> writes:
> Anyone know what package stddef.h is in? I had to re-install debian in
> attempts to get my AWE32 drivers to work.
I had this problem recently, and it turned out all I had to do was
delete the references to this header from the .depends file.
Obviou
Oh, your're very welcome!
Btw, after installing the awe-package, did you also execute the install
script that patches the kernel sources before trying to reconfigure the
kernel?
Regards,
Andree
--
| Institute of Geophysics phone: +49 40 4123 4389
ANDREE LEIDENFROS
> Anyone know what package stddef.h is in?
Although I knew the answer, I asked it
http://sunsite.tut.fi/finder/
and it also told me your package is libc5-dev or libc6-dev.
> I had to re-install debian in
> attempts to get my AWE32 drivers to work. I had this problem the first
> time around and
ok, well when running 'make config' it gets to the sound driver part
and lists 4 or 5 *.h files that call for stddef.h, which can't be
found. This happened the first time I tried compiling my kernel.
Copying /usr/lib/gcc-lib/i486-linux/2.7.2.1/include/stddef.h into
/usr/include seems to do
Hi Jason,
you can find out to which package a certain file belongs with:
dpkg -S
E. g. 'dpkg -S stddef.h' on my system yields:
gcc: /usr/lib/gcc-lib/i486-linux/2.7.2.1/include/stddef.h
kernel-source-2.0.30:
/usr/src/kernel-source-2.0.30/include/linux/stddef.h
libc5-dev: /usr/include/li
23 matches
Mail list logo
