[EMAIL PROTECTED] (Kai Großjohann) writes:
> /etc/printcap has to do with the lpr, not lp, program.
(You need to install the cupsys-bsd (or similar) package.)
--
~/.signature is: umop ap!sdn(Frank Nobis)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
[EMAIL PROTECTED] (sdownes) writes:
> Printing from Abiword to lp does nothing
> command line (lp -d lp@rm "filename") returns:-
> lp unable to print file server-error-service-unavailable
> from a remote host or:-
> job queued but cant start daemon
> (it isn't queued in cups)
/etc/pri
Oliver Fuchs <[EMAIL PROTECTED]> writes:
> See also man make-kpkg and option --initrd:
That's nice. I think I've got to try it first, before asking more
questions. (I'm wondering whether it's possible/necessary to modify
the initrd setup thus created.)
--
~/.signature is: umop ap!sdn(Fran
Raghavendra Bhat <[EMAIL PROTECTED]> writes:
> Kai posts :
>
>>> I hear good stuff about the hw detection facilities in Knoppix,
>>> could they be pilfered for my purpose?
>
> The hw detection is done by kudzu, GPLed stuff.
Ah, and there are even Debian packages for this! Cool.
> They can
I've read the howto on initrd, and it looks fascinating. But it also
looks intimidating to set it all up from scratch. So maybe someone
else has done it already?
I'm using sarge and I'd like to use initrd to be able to boot the
same kernel on different hardware. So, for example, I don't need to
I installed laptop-net, and it appears that this will bring up an
interface when I plug in a cable. So I'm thinking that it's not
necessary to bring up eth0 on boot -- laptop-net will take care of
that.
So I commented out the "auto eth0" statement in
/etc/network/interfaces, but it seems that eth
When building a new kernel (with make-kpkg) I always forget to also
build new VMware kernel modules.
It would be easy to put make-kpkg and vmware-config.pl into a script,
but that is not enough: we have multiple machines using the kernel
package I thus create. Therefore, we need to find a way to
martin f krafft <[EMAIL PROTECTED]> writes:
> good spot. but dhclient.conf has the script directive disabled in
> Debian:
>
> #script "/etc/dhcp3/dhclient-script";
>
> anyway, i'll experiment... thanks!
I think this is the default, at least that string occurs in the
/sbin/dhclient binary on my sy
Alan Shutko <[EMAIL PROTECTED]> writes:
> No, you can't seem to do this in calendar. I think you could in
> KOrganizer, Evolution, ical, plan, remind, jpilot, gnome-pim, Emacs's
> Calendar, and other things. If you got really tricky, you might be
> able to do it within the C preprocessor, since
martin f krafft <[EMAIL PROTECTED]> writes:
> also sprach Bob Proulx <[EMAIL PROTECTED]> [2002.11.18.1816 +0100]:
>> Idea1: It seems strange that you can't use the same interface to dhcp
>> on the second time. Just render the client impotent so that it does
>> not change the current parameters.
martin f krafft <[EMAIL PROTECTED]> writes:
> is there a tool i can use as a DHCP client, which does everything
> a regular DHCP client does, except for actual interface configuration?
> In fact, I would love it to simply call a shell script whenever it
> obtains a lease, or even better, whenever
We use CFengine to maintain the configuration of our machines. It's
great stuff. Now, one possibility for CFengine to manage the
XF86Config would be to just copy or edit the file. But it occurred
to me that it might be better to just maintain the answers asked by
debconf. Do you think that migh
On Sat, 19 May 2001, Karsten Kruse wrote:
> ich möchte unter windows und linux gerne meine mail mit imap
> verwalten. auf dem server werde ich wohl den uw-imapd
> installieren. ist es egal mit welchem clienten ich auf meine
> imap-verzeichnisse zugreife? sind die clients hundertprozentig
> austaus
13 matches
Mail list logo
