Re: boot with numlock?

Hi, Pete

For brief answer just skip to the down to the indented part.

This question is addressed in The Linux Documentation Project at
<http://www.tldp.org/> (which turns ten years old today! Hurray!).
There are two HOWTOs that pertain too your question:
The Linux Keyboard and Console HOWTO in more technical and abstract
(and less helpful, IMO) terms at:
<http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO.html>.
The HOWTO covers a ton of info on linux keyboard & console; the
section on numlock is Section 10 "The keyboard LEDs" at:
<http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO-10.html>.

A briefer (and better IMO) answer is in the Configuration HOWTO at
<http://www.tldp.org/HOWTO/Config-HOWTO/index.html>.  It's keyboard
section is at <http://www.tldp.org/HOWTO/Config-HOWTO/x43.html#AEN64>.
To quote this Configuration HOWTO:

    To enable NumLock on by default, add these lines to the startup
    script /etc/rc.d/rc.sysinit:

    for tty in /dev/tty[1-9]*; do
      setleds -D +num < $tty
    done

In this example, change the /dev/tty[1-9]* to however many consoles
you have on startup; for example my distro (Slackware) defaults to
having 6 initial consoles, so I would use: /dev/tty[1-6]*

What - Linux Video Capture Interface, V1.0???

Greetings: Am messing with the Gatos Groups avview and km. Have
avview working OK, but got into trouble with the capture routine km
and would like to uninstall it..

I found the modules it created and rm'd them but dmesg now reports
"Linux Video Capture Interface, V1.0" several times and I can't find
what file is doing this.. It's not in the kernel because I can boot
from both the HD or floppy and get the same dmesg report.. It _has_
to be somewhere on the HD - but where??? I'm booting command line
only so X11 shouldn't have anything to do with it, IMHO. :^)... Of
course I've grep'd so many times I'm blue in the face.. If the
routine is in a binary file - am I stuck??

Any suggstions?? Anyone run into this before??

TIA and cheers,

    Hal - in Terra Alta, WV - Slackware GNU/Linux 9.0   (2.4.20)
                Proprietary  Formats  Unacceptable
.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: What - Linux Video Capture Interface, V1.0???

At 04:11 PM 11/1/2003 -0500, Hal MacArgle wrote:
>Greetings: Am messing with the Gatos Groups avview and km. Have
>avview working OK, but got into trouble with the capture routine km
>and would like to uninstall it..
>
>I found the modules it created and rm'd them but dmesg now reports
>"Linux Video Capture Interface, V1.0" several times and I can't find
>what file is doing this.. It's not in the kernel because I can boot
>from both the HD or floppy and get the same dmesg report.. It _has_
>to be somewhere on the HD - but where??? I'm booting command line
>only so X11 shouldn't have anything to do with it, IMHO. :^)... Of
>course I've grep'd so many times I'm blue in the face.. If the
>routine is in a binary file - am I stuck??
>
>Any suggstions?? Anyone run into this before??

Is it possible that what you are seeing in dmesg is actually

         "Linux video capture interface: v1.00"

(note the differences in capitalization - this is from my dmesg file on a 
vidcap host I have)?

If so, it is a sort of section header for the v4l modules. On my system, it 
opens the section that reports installation of the bttv driver. For help, 
you need to quote the 2 lines that precede it, and the group that follows 
it, in dmesg. Since I use a Hauppauge vidcap card, not the ATI vidcap stuff 
that GATOS supports (kind of), I don't know what you might see in this 
section of dmesg. But the details should help.

Re: What - Linux Video Capture Interface, V1.0???

On 11-01, Ray Olszewski wrote:
> At 04:11 PM 11/1/2003 -0500, Hal MacArgle wrote:
> >Greetings: Am messing with the Gatos Groups avview and km. Have
> >avview working OK, but got into trouble with the capture routine km
> >and would like to uninstall it..
> >
> >I found the modules it created and rm'd them but dmesg now reports
> >"Linux Video Capture Interface, V1.0" several times and I can't find
> >what file is doing this.. It's not in the kernel because I can boot
> >from both the HD or floppy and get the same dmesg report.. It _has_
> >to be somewhere on the HD - but where??? I'm booting command line
> >only so X11 shouldn't have anything to do with it, IMHO. :^)... Of
> >course I've grep'd so many times I'm blue in the face.. If the
> >routine is in a binary file - am I stuck??
> >
> >Any suggstions?? Anyone run into this before??
> 
> Is it possible that what you are seeing in dmesg is actually
> 
>         "Linux video capture interface: v1.00"
> 
> (note the differences in capitalization - this is from my dmesg file on a 
> vidcap host I have)?

	True w/Slackware9.0 also.. I quoted it wrong. The "editor" in
me I guess. :^).. It, apparently, is a report from 'videodev.o'

> If so, it is a sort of section header for the v4l modules. On my system, it 
> opens the section that reports installation of the bttv driver. For help, 
> you need to quote the 2 lines that precede it, and the group that follows 

Can't write VFAT filesystem

Hi,

I've set up my /etc/fstab file as usual, so that I can 
access my Windows C: and D: drives, as shown in the attachment.

I can mount/unmount both these drives and read them.  I can 
also write to the /mnt/c filesystem.  But for some reason I 
can't write to the /mnt/d filesystem.  Specifically:

$ whoami
yawar
$ pwd
/mnt/d/My Documents
$ touch file
touch: creating `file': Permission denied
$

Can some kind soul tell me what I'm doing wrong?

Thanks,
Yawar Amin

LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
none                    /dev/pts                devpts  gid=5,mode=620  0 0
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
/dev/hda4               swap                    swap    defaults        0 0
/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,user,unhide,kudzu,ro 0 0

MSN Messenger clones keep failing

Hi,

Recently I got my internet connection up at home again and 
downloaded the latest versions of Alvaro's MSN Messenger for 
Linux and Ayttm for Linux.  These are clones meant to get me 
into MSN Messenger chat.  But they keep failing, saying my 
username and/or password are incorrect.

I can easily sign in with MSN Messenger 6 on the same 
machine---I dual boot with Win98---but I'd much rather use 
Linux 

Does anybody have any experience with this?  And can anyone 
lend a  hand?  Thanks.

Yawar Amin

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: MSN Messenger clones keep failing

On Tue, 4 Nov 2003, Amin wrote:
>
> Recently I got my internet connection up at home again and
> downloaded the latest versions of Alvaro's MSN Messenger for
> Linux and Ayttm for Linux.  These are clones meant to get me
> into MSN Messenger chat.  But they keep failing, saying my
> username and/or password are incorrect.
>
> I can easily sign in with MSN Messenger 6 on the same
> machine---I dual boot with Win98---but I'd much rather use
> Linux 
>
> Does anybody have any experience with this?  And can anyone
> lend a  hand?  Thanks.
>
Well, I don't have direct experience with any of those clients, nor with
trying to chat on MSN from Linux.  But I do read some computer news, and
have seen articles recently (within the last month?) that talk about an
impending M$ plan to cut off their network from other chat clients.  I
understood that this was to apply to all non-M$ clients as well as to
earlier versions of M$'s client as well.  Maybe this explains the trouble
you're having?

James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: MSN Messenger clones keep failing

At 09:23 AM 11/4/2003 +0100, James Miller (office) wrote:
>On Tue, 4 Nov 2003, Amin wrote:
> >
> > Recently I got my internet connection up at home again and
> > downloaded the latest versions of Alvaro's MSN Messenger for
> > Linux and Ayttm for Linux.  These are clones meant to get me
> > into MSN Messenger chat.  But they keep failing, saying my
> > username and/or password are incorrect.
> >
> > I can easily sign in with MSN Messenger 6 on the same
> > machine---I dual boot with Win98---but I'd much rather use
> > Linux 
> >
> > Does anybody have any experience with this?  And can anyone
> > lend a  hand?  Thanks.
> >
>Well, I don't have direct experience with any of those clients, nor with
>trying to chat on MSN from Linux.  But I do read some computer news, and
>have seen articles recently (within the last month?) that talk about an
>impending M$ plan to cut off their network from other chat clients.  I
>understood that this was to apply to all non-M$ clients as well as to
>earlier versions of M$'s client as well.  Maybe this explains the trouble
>you're having?

If the original poster is referring to the Sourceforge project

         http://amsn.sourceforge.net/

it purports to work with the "new" (post-Oct 15)  MSN standards ... that 
is, version 0.83 does. So if that (or something later) is what he means by 

Re: MSN Messenger clones keep failing

James Miller (office) wrote:
> 
> Well, I don't have direct experience with any of those clients, nor with
> trying to chat on MSN from Linux.  But I do read some computer news, and
> have seen articles recently (within the last month?) that talk about an
> impending M$ plan to cut off their network from other chat clients.  I
> understood that this was to apply to all non-M$ clients as well as to
> earlier versions of M$'s client as well.  Maybe this explains the trouble
> you're having?
> 
> James

This seems likely.  The latest version of one of the clones 
I use tells me that MSN Messenger is using a new protocol 
and new security, something about SSL, and would I like to 
download a small patch to handle this?  I said yes, and got 
the patch ... but even that seems to be a little behind the 
curve.  Well then it's back to good ol' Yahoo Messenger for me.

Thanks,
Yawar Amin

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: Can't write VFAT filesystem

> I've set up my /etc/fstab file as usual, so that I can
> access my Windows C: and D: drives, as shown in the attachment.
>
> I can mount/unmount both these drives and read them.  I can
> also write to the /mnt/c filesystem.  But for some reason I
> can't write to the /mnt/d filesystem.  Specifically:

Perhaps your D: - drive is NTFS, not VFAT?
I think the Kernelmodule for writing on NTFS is "dangerous" at the moment, so
not installed by the most distributions...
(if you have installed Windows XP, this is the standard (like on my own
system))

HTH,
Dennis Schridde

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs