On Tuesday 18 December 2001 16:29, dman wrote:
> On Tue, Dec 18, 2001 at 04:06:56PM +0100, Emiel Metselaar wrote:
> ...
>
> | sys c:
>
> I did this once. Destroyed the disk! I don't recommend doing it
> again.
>
> The story :
> A few years back I acquire
On Tuesday 18 December 2001 16:06, o polite wrote:
> Some time ago I tried to install the userfriendly OS Windows 98 on spare
> partition. Of course it succeded in rendering my laptop unusable. It took
> me two days to get my system back. This was four weeks ago, so now I'm
> ready for some more pa
Yesterday I installed glutg3-dev & xlibmesa-dev for my visualisation code,
since the non-dev things do not have the header files. Today going
throught the apt-get update, upgrade routine I see that these 2 files
will be removed. My question is why, i didnot deselect them...
A related question is ho
On Wednesday 14 November 2001 13:44, Daniel Faller wrote:
> has someone tried and/or managed to install the
> Intel(R) Fortran Compiler on a debian (potato/unstable) system ?
yep, I did it the dirty way install on a RH machine and then copy it to the
debian machine
It is not a clean way of do
man reportbug:
--email=ADDRESS
Set the email address for your report. This should
be the actual Internet email address on its own
(i.e. without a real name or comment part). This
setting will override any environment variable that
is
Are you getting error's like these:
delibs3 (>= 4:2.2.2-1) but 4:2.2.1-14 is to be installed
Then head over to the debian-kde lists (thread 2.2.2 changes), in short the
files are not uploaded yet, but the meta package is..
emiel
On Tuesday 13 November 2001 12:50, Tom Allison wrote:
> Tom Allis
On Thursday 25 October 2001 14:42, Colin Watson wrote:
> On Thu, Oct 25, 2001 at 02:28:09PM +0200, Emiel Metselaar wrote:
> > I was trying to print using lprng on a woody machine and it did not work.
> > After some poking around i found that in
> > /usr/share/lprngtool/ps-to-
On Thursday 25 October 2001 14:28, Emiel Metselaar wrote:
> I was trying to print using lprng on a woody machine and it did not work.
> After some poking around i found that in
> /usr/share/lprngtool/ps-to-printer.fpi something did not work allright.
>
> It seems that the line &qu
I was trying to print using lprng on a woody machine and it did not work.
After some poking around i found that in
/usr/share/lprngtool/ps-to-printer.fpi something did not work allright.
It seems that the line "source ${SPOOLDIR}/postscript.cfg" does not
work. I am not much of a shell script expe
I also had some problems with alien, but since i just converted from a red
hat machine and i had backups i could just *ahum* copy the backup /opt/intel
directory and it worked. So try to find a rh machine and try the same
approach.
Not clean & nice, but one could call it pragmatic
good
10 matches
Mail list logo