Re: A GPG question
Dan H. skrev: > On Mon, Jan 28, 2008 at 03:54:42AM -0600, Ron Johnson wrote: >>> You can revoke identities from your key. 'gpg --edit ' and >>> then use 'revuid'. Don't forget to save and upload to a keyserver your >>> modified key afterwards. >> But will you lose access to any data that you have encrypted under >> the old key? > > No, I think the key itself stays valid. It's just the UID. > > --D. Yes, only the userid is made unusable if you revoke it. The key is still valid. BTW if you revoke a key it is made unusable for encryption, but you can still use it for decryption. Per Tunedal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A GPG question
Dan H. skrev: > Hello folks, > > this is not s strict Debian question but it is so small and easy that it's > not worth subscribung to a GPG list for. > > Q: How can I remove an email address from my GPG key? I'm changing jobs, so > one of my three addresses won't be valid any more. Do I have to make a new > key pair from scratch? If so, how can my "web of trust" (I don't have one so > this is rather theoretical) be transferred from the old to the new key? > > Thanks, > --D. You'd better consult the list for GnuPG users: http://lists.gnupg.org/pipermail/gnupg-users/ If I remember correctly you should revoke the old userid (e-mail address). Yours, Per Tunedal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "Waiting for root file system" problem
[EMAIL PROTECTED] skrev: > [This message has also been posted to linux.debian.user.] > This is becoming a FAQ. There is a problem with udev. > Before udev, there was a strong association between > device names and devices. With udev, that association > is much weaker. > There's new randomness in how partitions are named > during boot. > Debian and other installers have not > yet worked around this relatively new problem. > > What you're seeing is an effect of that. > The udeb installer kernel got a different set of > device names than the installed kernel did, and the > root file system never appears where the installed > kernel has been told it would. > Yes, I noticed that I had to call the partition /dev/sda5 to boot with GRUB, but when booted Debian showed me the partition as /dev/sdc5 ! > The workaround is to use file system labels or UUIDs > not device names in /etc/fstab and /boot/grub/menu.lst. > But the Debian 4.0 installer doesn't know that. > > Please read the discussion at > http://www.debianhelp.org/node/11653 > Yes, this worked fine. > > In article <[EMAIL PROTECTED]>, dave N wrote: >> >> I booted with Knoppix live and there is nothing in /var/log/messages, >> none of the logs appear to have changed since I last booted 2 days ago. >> I have not run fsck or anything else on this yet. > > Apparently Knoppix doesn't use udev. > > > Cameron > > I tried Knoppix too and found that my partition was called /dev/sda5 and used that information to edit the GRUB configuration in order to boot. And was surprised when the partition was called sdc5 after boot, exactly what was preventing boot in the GRUB configuration! Thanks for your explanation! I hope this inconsistency will be fixed in new Debian versions. Per Tunedal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
NTFS and discover1
Hi, as a new user I am puzzled about the inability of my Debian installation to handle NTFS-partitions from start. I installed in expert mode and chose to install support for NTFS. The NTFS-partitions are shown alright if I click the My Computer icon on my Gnome desktop. But they cannot be mounted when I click at the icons. I get an error message from pmount stating that they cannot be mounted because they are not detachable. (The partitions are on fixed drives.) I note that the NTFS-partitions are mounted for reading if I boot with a KNOPPIX CD. I searched the documentation and found that KNOPPIX uses kudzu (and not discover1) for hardware detection. Synaptic doesn't offer kudzu for Debian. hwinfo uses parts of kudzu, but cannot be used for hardware detection. Have I overlooked some settings during the installation? Or are there any flaws in discover1? It might be useful to add some instructions for NTFS in the installation manual. Yours, Per Tunedal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "Waiting for root file system" problem
Florian Kulzer skrev: > On Thu, Jan 03, 2008 at 06:39:11 -0500, dave N wrote: > > [...] > >> Question: In the menu.lst grub file, how would I use >> the label assignment in the line: >> >> kernel /vmlinuz-2.6.18-5-686 root=/dev/sdc2 ro > > I think this should be OK: > > kernel /vmlinuz-2.6.18-5-686 root=LABEL=your_root_label ro > > I have > > # kopt=root=LABEL=my_root_label ro > > in my menu.lst and this works for all the auto-generated entries. > Thanks for this very useful advice! I had the same problem and managed to log in simply by entering "e" at the GRUB-menu for editing the failing line. Afterwords I put a label on the partition with e2label and changed the reference in menu.lst It works like a charm! Per Tunedal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
