public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] strange one with gentoo guest in vmware
Date: Thu, 18 Feb 2010 22:37:59 +0000	[thread overview]
Message-ID: <167B7C51-167F-4045-9B8D-5BA78065A784@stellar.eclipse.co.uk> (raw)
In-Reply-To: <87aav6r2br.fsf@newsguy.com>


On 18 Feb 2010, at 15:27, Harry Putnam wrote:
> ...
> I now have all uppercase at the cmdline.  The actual keyboard is not
> in uppercase mode... and oddly the gentoo install apparently is not
> seeing uppercase at the cmdline since cmds that are supposed to be in
> lower case all work.
>
> typing what I see as `LS' at the command line does what `ls' is  
> supposed
> to do and lists the directory, so gentoo is seeing lowercase where I
> see uppercase.
>
> Anyone have a clue what this might be about?

I believe that *nix does this natively & transparently, so that it  
continues to function with ancient physical VTs & teletypes which lack  
a shift key.

I have this idea that the system will try to accommodate you this way  
if you attempt to log in with the CAPS LOCK on. I can't quite get this  
to work here, it seems to reject my password, but on at least one  
system I see the logon prompt change to ALL CAPS if I log on using my  
username but capitalised (i.e. "STROLLER" instead of "stroller").

Is it possible you have the CAPS LOCK stuck on your VM but not on your  
host system? I've not used VMs, so please excuse me if this is a  
ridiculous impossibility.

Stroller.




  reply	other threads:[~2010-02-18 22:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-18 15:27 [gentoo-user] strange one with gentoo guest in vmware Harry Putnam
2010-02-18 22:37 ` Stroller [this message]
2010-02-18 23:06 ` [gentoo-user] " Harry Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=167B7C51-167F-4045-9B8D-5BA78065A784@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox