On Wed, Jun 05, 2002 at 01:12:34PM +0200, jfcarvajal wrote:
>
> I have a problem when trying to download a woody iso image with jigdo-easy.
> It always says "oops! some file missed. First I followed the readme
> intructions but i had always the same message.
I don't know about jigdo-easy (I assum
This is the error dvifb gives me. Here's what fbset says:
mode "1024x768-76"
# D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz
geometry 1024 768 1024 4096 8
timings 12714 128 32 16 4 128 4
rgba 6/0,6/0,6/0,0/0
endmode
What does it mean? If I try to change it, the console gets messed
up
Hello,
I'm using vesafb and have just noticed that pressing Alt-UpArrow
doesn't echo the usual "Keyboard Request--edit /etc/inittab ..." but
instead behaves as if there were no Alt key pressed. Obviously
there's a link between (vesa)fb and this problem. What do I do about
it? I run a 2.4.16 kernel
On Mon, Jun 10, 2002 at 10:07:28PM -0700, Jeffrey Baker wrote:
> I had the strangest problem tonight. There are new versions of many
> GNOME 2 packages, but apt-get does not offer to upgrade them. For
Maybe you have a preferences file lying around in your /etc/apt
directory?
--
echo ${girl_nam
On Thu, Jun 13, 2002 at 10:30:01AM +0800, Willy S wrote:
> What happen if I decide to use my CDROM again, that means the apt source-list
> will be
> replaced with CDROM? I mean, what happen to the program that I have in
You can have as many sources listed as you like -- they will be
added, not ov
On Tue, Jun 11, 2002 at 11:27:56AM +0200, Francois Chenais wrote:
> Is it possible to update this raw file with the new netinstall
> package without downloading everything ?
Yes, in fact it is. Using jigdo-lite, you just pretend to be
downloading the image from scratch. This way, you'l
Hello,
suddenly -- after a kernel upgrade, it's 2.4.18 with atyfb now -- ps
stopped working. This is the output:
Signal 7 caught by ps (procps version 2.0.7).
Please send bug reports to <[EMAIL PROTECTED]>
But top still works. What's wrong here?
andrej
--
echo ${girl_name} > /etc/dumpdates
-
I'm losing my temper here -- why did the first prompt work normally
and the second looks fine, yet if I try to type more than one line,
it doesn't start a new one but starts overwriting the very same one
instead!?
andrej
###
NC='\e[0m'
BLUE='\e[1;34m'
function
I've just migrated from masqmail to postfix and it's working fine as
far as I can tell, the only exception being local delivery. I can
send mail to myself but not to any other computer on a small home
LAN, consisting of three alltogether.
I obviously can't handle the transports file.
Here's my co
I thought I was clever and added an init script for setting the concole
with fbset. I've figured that "fbset -t 13334 144 24 29 3 136 6" yields
the best results. But it affects only the first console -- I have to
run the script every time I log in.
Is there a way to make it permanent for all conso
On Thu, Jun 20, 2002 at 11:21:59AM +0200, Ulf Rompe wrote:
>
> Just an idea - can't test it at the moment. What happens if you put
> something like this into your script?
>
> for i in 1 2 3 4 5 6; do
> chvt $i
> fbset -t 13334 144 24 29 3 136 6
> done
Unfortunatelly, not much. I get boun
On Thu, Jun 20, 2002 at 11:35:13AM +0200, Karoly VEGH wrote:
> #!/bin/sh
> echo "" > /dev/tty2
> echo "" > /dev/tty3
> echo "" > /dev/tty4
> echo "" > /dev/tty5
> echo "" > /dev/tty6
> fbset -a 640x480-100
>
> echo's u need, cause fbset works only on consoles on which there is
> already something.
This was posted a little while ago here by Vineet but I don't have the
mail anymore. The idea was to add the line append="console=/dev/ttyN" to
lilo.conf. I've tried to add it to grub (the right way, I suppose, without
quotes and the "append") but the results were a little different: at boot
up the
On Thu, Jun 20, 2002 at 12:17:10PM -0500, Derrick 'dman' Hudson wrote:
>
> You didn't show us your config, that's what <0.5 wink>. Clearly you
> didn't configure it correctly.
>
Sorry, it's here. I was sure it must have been something else, but
take a look at it. Here's the relevant section:
#2
For some reason, I cannot send mail to root directly anymore -- and
I know the cause; I've set up postfix to rewrite the address
[EMAIL PROTECTED] to my real e-mail address, thus [EMAIL PROTECTED] Since
this rewrites *all* occurrence of the above, writing mail root
results in mail to [EMAIL PROTECT
On Sat, Jun 22, 2002 at 10:35:32AM -0100, andrej hocevar wrote:
> Surely there's another way to solving this but I'm new to postfix
> and couldn't find a simpler/more advanced solution.
Sorry for that, I've found the answer -- obviously there *was*
another solution! :
Lately I've been playing a little with sending mail to myself
(great fun, that!:)). I'm using postfix and it works perfectly.
I've found out that if I send mail using "sendmail -f foo -F bar
root" to rewrite headers there's an effect I didn't plan: Here a
sample header.
sendmail -f "[EMAIL PROTECT
On Wed, Jun 26, 2002 at 09:08:40PM +0800, Patrick Hsieh wrote:
> Did you start portmap?
And did you compile it into your kernel?
There's a NFS-HOWTO that helped me back then, I don't remember
everything exactly. But you definitely need it in your kernel plus
the hosts-allow/deny files.
When I ma
101 - 118 of 118 matches
Mail list logo
