Stephen Masterman wrote:
>
> I seem to remember reading some comments in the XFree86 docs about how it
> does not support Diamond cards. I think its some political thing, since
> Diamond won't release the code freely to make the driver or something..
> But this information may be obsolete now.
> > You could also grab the raw source and use kernel-package
> > package to generate your new image package. This is the recommended
> > method for generating custom kernel images.
>
> Could you point me to exactly where this is recommended?
>
> In any case, though, I have no des
Manoj Srivastava writes [ SuperCite undone - iwj ]:
> Brian C White <[EMAIL PROTECTED]> writes:
> > So... Should there be a restriction against listing the
> > kernel-image as a dependancy in another package?
>
> No, since if you follow the recommended method of generating
> kernel images,
Hi,
>>"Ian" == Ian Jackson <[EMAIL PROTECTED]> writes:
Ian> On the contrary, we should not require people to follow this
Ian> method, especially when it's easy not to make this requirement.
Ian> Packages which need a particular kernel or kernel feature to run
Ian> correctly should test for the ke
Hi,
>>"Dale" == Dale Scheetz <[EMAIL PROTECTED]> writes:
Dale> In the past these source/image packages clobbered the
Dale> modules.dep file for the currently running kernel. I understand
Dale> that they no longer do that, however, I have not been happy with
Dale> the position taken by the package
On Fri, 31 May 1996, R. Gugisch wrote:
>
> Richard G. Roberto wrotes:
> >
> > how did you capture the output?
> >
>
> I wrote it by hand. But by the side, capturing the booting output to a file
> would make sense.
>
try "dmesg > dumpfile"
It's me, Manolo!
Brian C. White writes ("Re: How to handle new packages"):
> > As I understand dselect, it looks at the Packages file to determine
> > the list of packages, their dependencies, and whatever else.
> >
> > Suppose I want to upgrade a single package. I grab the .deb file.
> > But now what? The Packa
Well, the first things I would check would be to make sure that the script
you want to run is executable, and barring that, perhaps your path is not
set correctly. If you're running these as root, try ./scriptname because
the current directory should not be part of root's path.
>I am running a number of shell scripts and find I have to
>specify sh and then the script name. The first line of the
>script is always #!/bin/sh which I am assuming takes care
>of this. Could someone provide some hints what I have done
>wrong or some pointers.
You probably need to make th
...
>System 2:
> motherboard: ASUS P55TP4N
> CPU: Intel Pentium 166MHz
>Graphics card: Diamond Stealth64 VIDEO 2001 (PCI, S3 765 (Trio64V+), 2 MB)
>Linux: Debian 1.1beta
...
>
> System 2 runs svgalib programs fine, no problems. System 1 with the
>video card from System 2 al
On Fri, 31 May 1996, Alberto Brizio wrote:
> Hello,
> I have an old AMD' 80386 40MHz with 4MB of RAM and I really like
> to install Linux on it. I spent some time looking around and
> then I decided to proceed with the Debian distribution.
> Got the five disks of the 0.93R6 version I started the
On Thu, 30 May 1996, Brian C. White wrote:
> > >> There is indeed a Debian-ized version of the kernel. The package is
> > >> called kernel-image.
> >
> > You could also grab the raw source and use kernel-package
> > package to generate your new image package. This is the recommended
> > m
> By the way, I created a script to handle debian packages as an extfs,
> similar to the one included for Red Hat packages. Would you be willing to
> include it in your mainstream distribution?
I will be happy to do so.
Best wishes,
Miguel.
Martin Rheumer writes:
>I am running a number of shell scripts and find I have to specify sh
>and then the script name. The first line of the script is always
>#!/bin/sh which I am assuming takes care of this. Could someone
>provide some hints what I have done wrong or some pointers.
Have you mad
I have successfully installed (from scratch) the debian 1.1 beta on
two server machines (an i-386 and an i-486). Everything seems to be
working as planned and I have no complaints. I am getting ready to
*upgrade* my existing pentium machine (my main workstation) from
0.93R6 to 1.1 beta. I have a
Just installed Debian 1.1beta. It was pretty smooth, except for X, and
i dont think the X problems are really Debians fault, but what the heck,
i'll ask for help here anyway.
I have two systems...
System 1:
motherboard: ASUS SP3G
CPU: AMD 486 dx4 100MHz
Graphics card: Orchi
I know this is not Debian-specific, but, still, as it is Linux related, I
thought there might be someone out there interested. Please flame me
through email so that nobody suffers more because of me!
Forwarded message:
> From: [EMAIL PROTECTED] (Lee Giles)
> Subject: Student summer job at NEC Rese
Richard G. Roberto wrotes:
>
> how did you capture the output?
>
I wrote it by hand. But by the side, capturing the booting output to a file
would make sense.
Ralf Gugisch
[EMAIL PROTECTED]
Hello,
I have an old AMD' 80386 40MHz with 4MB of RAM and I really like
to install Linux on it. I spent some time looking around and
then I decided to proceed with the Debian distribution.
Got the five disks of the 0.93R6 version I started the installation
but with no success at all.
I disabled
I am running a number of shell scripts and find I have to
specify sh and then the script name. The first line of the
script is always #!/bin/sh which I am assuming takes care
of this. Could someone provide some hints what I have done
wrong or some pointers.
Also perhaps how I could also start my s
in my previous setup I used to have "setterm -blank 15 -powersave on"
launched in my init scripts.
in the debian 1.1beta distribution, setterm does not seems to support
such options. (the -msg option dissapeard, also).
Is this because the setterm included in debian is not up-to-date
(in which
Hi,
>>"Brian" == Brian C White <[EMAIL PROTECTED]> writes:
>> >> There is indeed a Debian-ized version of the kernel. The package
>> is >> called kernel-image.
>> You could also grab the raw source and use kernel-package package
>> to generate your new image package. This is the recommended meth
Manoj Srivastava writes:
> This _is_ standard practice for debian (including
> /usr/include/linux and /usr/include/asm in libc5-dev). This has been
> discussed at length and the decision reached after a long, drawn out
> debate. This is on it;s way to becoming a faq:
Already started. There
> >> There is indeed a Debian-ized version of the kernel. The package is
> >> called kernel-image.
>
> You could also grab the raw source and use kernel-package
> package to generate your new image package. This is the recommended
> method for generating custom kernel images.
Could you po
> As I understand dselect, it looks at the Packages file to determine
> the list of packages, their dependencies, and whatever else.
>
> Suppose I want to upgrade a single package. I grab the .deb file.
> But now what? The Packages file doesn't know about the new package.
>
> I know I could ins
Hi,
>>"Juha" == Juha Heinanen <[EMAIL PROTECTED]> writes:
Juha> i had istalled debian beta kernel sources and later noticed that
Juha> /usr/include/linux and /usr/include/asm were real directories
Juha> instead of links to /usr/src/linux. is that still so? if so,
Juha> it is very dangerous and s
Rick Macdonald:
> Someone recently posted a long patch file to fix the spelling of Linux
> in Emacs 19.31. Well, I just had a look and it is not a spelling
> mistake: it is quite intentional. "Lignux" is GNU's new short name for
> a "Linux-based GNU system".
Rick,
Calling it a "spelling mistake"
On Tue, 28 May 1996, Miguel de Icaza wrote:
> I just wonder if it is possible for the maintainer of the debian
> package to configure the program to not use ncurses (ie, to let the
> default screen manager be used) and to upgrade to a newer version of
> the program (3.2.1 is current, I announced
28 matches
Mail list logo
