Yum and dkms -
by Bob Goodwin
After"yum update" this morning I have this notice. I recall needing dkms
for some reason after installing vbox but don't recall the reason for
it. I assume there is some action required on my part but what? It seems
easier to ask here than to muddle through this again.
What command do I need to execute to fix this or should I just forget dkms?
Bob
dkms: removing: vboxhost 4.2.16 (3.10.6-200.fc19.x86_64) (x86_64)
-------- Uninstall Beginning --------
Module: vboxhost
Version: 4.2.16
Kernel: 3.10.6-200.fc19.x86_64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
Removing any linked weak-modules
vboxdrv.ko:
- Uninstallation
- Deleting from: /lib/modules/3.10.6-200.fc19.x86_64/extra/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxnetflt.ko:
- Uninstallation
- Deleting from: /lib/modules/3.10.6-200.fc19.x86_64/extra/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxnetadp.ko:
- Uninstallation
- Deleting from: /lib/modules/3.10.6-200.fc19.x86_64/extra/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxpci.ko:
- Uninstallation
- Deleting from: /lib/modules/3.10.6-200.fc19.x86_64/extra/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod.....
DKMS: uninstall completed.
--
http://www.qrz.com/db/W2BOD
box10 Fedora-19 Linux/XFCE
10 years, 7 months
A couple of random questions about login
by William Oliver
So, I was watching a TV show the other day where it was one of those things where the good guy tries to break into the bad guy's computer and, because of his great investigative skills, guesses that the password is a word a book from the bad guy's favorite author. But, first, the good guy tried a couple of other obvious guesses -- the name of the bad guy's boat, etc.
My wife turned to me and said, "If I were the bad guy, I'd just have the computer delete everything if someone entered the boat name, or at least send me a text. The boat was an obvious guess, and I would never accidentally type it in."
My answer was "That makes sense, but I have no clue about how to do it."
Now I can't get the idea out of my head. Worse, I've realized that I don't know, at a process level, what happens when one types in a password. Yes, I know about /etc/password and /etc/shadow files, and I know about encryption. But I don't know step by step in terms of what processes do what when a password is entered.
So:
1) What happens at a process level when one hits return after typing in a password? Is everything handled by the kernel? Where is this described?
2) Is it possible to script different responses to different (incorrect) passwords?
Thanks,
billo
10 years, 7 months
Re: Announcing Fedora GPG Key Server - keys.fedoraproject.org
by Stephen Gallagher
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09/02/2013 11:10 PM, Nick Bebout wrote:
> You could also put in ~/.gnupg/gpg.conf: keyserver
> hkp://keys.fedoraproject.org
>
Might be worth opening a BZ against the gnupg2 package to have this
made the default for the Fedora package.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIlx8kACgkQeiVVYja6o6M36gCgmMztUgoAJ9Ex6/D9mOchRZD6
LssAoJxNfvX7ifHuhU+COfxHYumUhLMG
=5H6F
-----END PGP SIGNATURE-----
10 years, 7 months
Today update problem
by Cristian Sava
Hi,
Updating today I got this:
[ ... ]# sudo yum update
...
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
kde-settings-kdm-19-23.1.fc19.noarch is a duplicate with
kde-settings-kdm-19-23.fc19.noarch
When trying to delete the old package:
[ ... ]# sudo yum remove kde-settings-kdm-19-23.fc19.noarch
...
Transaction test succeeded
Running transaction
/var/tmp/rpm-tmp.gqT87e: line 1: fg: no job control
error: %preun(kde-settings-kdm-19-23.fc19.noarch) scriptlet failed, exit
status 1
Error in PREUN scriptlet in rpm package
kde-settings-kdm-19-23.fc19.noarch
Verifying : kde-settings-kdm-19-23.fc19.noarch
1/1
Failed:
kde-settings-kdm.noarch
0:19-23.fc19
Complete!
Trying "rpm -e kde-settings-kdm-19-23.fc19.noarch" also fail.
Any advice how to fix that?
Thanks,
C. Sava
10 years, 7 months
Re: Announcing Fedora GPG Key Server - keys.fedoraproject.org
by Suvayu Ali
(Apologies to announce mods, I accidentally sent my reply there instead
of the users list)
Unrelated question:
On Mon, Sep 02, 2013 at 10:10:29PM -0500, Nick Bebout wrote:
> This server may be accessed in the following ways:
> Web interface at http://keys.fedoraproject.org or
> https://keys.fedoraproject.org
I often see new webservices provide both an http and an https url.
Earlier when https was not supported by many browsers, I would
understand that. But is there any reason to still keep supporting http?
I would think the only way we get an encrypted Internet is by not
offering the older option. For a new serivce this should be easy
without breaking bookmarks and people's setup.
Just a thought.
--
Suvayu
Open source is the future. It sets us free.
10 years, 7 months
3d printing software and solidoodle?
by Tom Horsley
Now that Fedora has lots of 3d printing related
software in the repos and my Solidoodle 2 printer
is arriving this week, I just thought I'd ask if
anyone has used any of the fedora supplied versions
of the software with a solidoodle?
I'll be giving it a try, but wondered if anyone
else already has experience and advice tweaking
things for the solidoodle.
10 years, 7 months
Yum: a suggestion
by Timothy Murphy
Yum only tells me the sites it has _failed_ to download from.
Wouldn't it be nice if it also told us which sites _succeed_?
I'd like to know who to be grateful to.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 7 months
Trouble setting up kickstart
by Michael Larsen
I'm trying to set up a kickstart server on my home network. I can't get
network booting working. DHCPD and tftp are working, but the tftp request
on the client is timing out with:
PXE-E32 TFTP open timeout
I've googled the heck out of this issue and can't find a fix. I was hoping
someone here could help me out.
My dhcpd.conf file:
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.example
# see dhcpd.conf(5) man page
#
option space pxelinux;
option pxelinux.magic code 208 = string;
option pxelinux.configfile code 209 = text;
option pxelinux.pathprefix code 210 = text;
option pxelinux.reboottime code 211 = unsigned integer 32;
allow booting;
allow bootp;
class "pxeclients" {
match if substring (option vendor-class-identifier, 0, 9) =
"PXEClient";
next-server 192.168.10.90;
filename "pxelinux.0";
}
subnet 192.168.10.0 netmask 255.255.255.0 {
option domain-name "larsenhaus.org";
option domain-search "larsenhaus.org";
option domain-name-servers 192.168.10.60,192.168.10.90;
option routers 192.168.10.10;
range dynamic-bootp 192.168.10.100 192.168.10.200;
default-lease-time 3600;
max-lease-time 4800;
}
My xinetd tftp file:
# default: off
# description: The tftp server serves files using the trivial file transfer
\
# protocol. The tftp protocol is often used to boot diskless \
# workstations, download configuration files to network-aware
printers, \
# and to start the installation process for some operating systems.
service tftp
{
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
#server = /usr/sbin/in.tftpd
server_args = -s /tftpboot/pxelinux -v
disable = no
per_source = 11
cps = 100 2
flags = IPv4
}
The contents of /tftpboot:
[root@kickstart tftpboot]# ls
cat.c32 disk.c32 gpxelinux.0 * install* lua.c32
pcitest.c32 pxelinux.0 ver.com
chain.c32 dmitest.c32 hdt.c32 int18.com mboot.c32
pmload.c32 reboot.c32 vesainfo.c32
cmd.c32 elf.c32 host.c32 kbdmap.c32 memdisk
poweroff.com rosh.c32 vesamenu.c32
config.c32 ethersel.c32 ifcpu64.c32 *ks-cfg* memdump.com
pwd.c32 sanboot.c32 vpdtest.c32
cpuid.c32 gfxboot.c32 ifcpu.c32 linux.c32 meminfo.c32
pxechain.com sdi.c32 whichsys.c32
cpuidtest.c32 gpxecmd.c32 ifplop.c32 ls.c32 menu.c32 *pxelinux
* sysdump.c32 zzjson.c32
The contents of /tftpboot/install/fedora19:
[root@kickstart tftpboot]# ls install/fedora-19/
Fedora-19-i386-netinst.iso
The contents of /tftpboot/ks-cfg:
[root@kickstart tftpboot]# ls ks-cfg
netbook-ks.cfg
The contents of /tftpboot/pxelinux:
[root@kickstart tftpboot]# ls pxelinux
initrd.img pxelinux.0 pxelinux.cfg vesamenu.c32 vmlinuz
The contents of /tftpboot/pxelinux/pxelinux.cfg:
[root@kickstart tftpboot]# ls pxelinux/pxelinux.cfg/
default
The contents of the default file:
[root@kickstart tftpboot]# cat pxelinux/pxelinux.cfg/default
default vesamenu.c32
prompt 1
timeout 600
display boot.msg
label linux
menu label ^Install a new system
menu default
kernel vmlinuz
append initrd=initrd.img repo=nfsiso::kickstart.larsenahus.org:
/tftpboot/install/fedora-19
ks=nfs:192.168.10.90:/tftpboot/ks-cfg/netbook-ks.cfg
label vesa
menu label Install system with ^basic video driver
kernel vmlinuz
append initrd=initrd.img xdriver=vesa nomodeset
repo=nfsiso::kickstart.larsenahus.org:/tftpboot/install/fedora-19
label memtest86
menu label ^Memory test
kernel memtest
append -
My exports:
[root@kickstart ~]# exportfs
/tftpboot/install/fedora-19
<world>
Perms on /tftpboot and subdirs are currently 777, everything owned by root.
The netbook acquires an IP address from DHCP and begins the tftp request,
but times out as described above. tcpdump shows the client connecting to
the tftp server:
[root@localhost ~]# tcpdump port 69 -v -i em1
tcpdump: listening on em1, link-type EN10MB (Ethernet), capture size 65535
bytes
19:41:53.028845 IP (tos 0x0, ttl 20, id 2, offset 0, flags [none], proto
UDP (17), length 55)
dhcp-101.larsenhaus.org.ah-esp-encap > kickstart.larsenhaus.org.tftp:
27 RRQ "pxelinux.0" octet tsize 0
19:41:55.027661 IP (tos 0x0, ttl 20, id 3, offset 0, flags [none], proto
UDP (17), length 55)
dhcp-101.larsenhaus.org.acp-port > kickstart.larsenhaus.org.tftp: 27
RRQ "pxelinux.0" octet tsize 0
19:41:59.037376 IP (tos 0x0, ttl 20, id 4, offset 0, flags [none], proto
UDP (17), length 55)
dhcp-101.larsenhaus.org.msync > kickstart.larsenhaus.org.tftp: 27 RRQ
"pxelinux.0" octet tsize 0
19:42:05.024477 IP (tos 0x0, ttl 20, id 5, offset 0, flags [none], proto
UDP (17), length 55)
dhcp-101.larsenhaus.org.gxs-data-port > kickstart.larsenhaus.org.tftp:
27 RRQ "pxelinux.0" octet tsize 0
19:42:12.988945 IP (tos 0x0, ttl 20, id 6, offset 0, flags [none], proto
UDP (17), length 55)
dhcp-101.larsenhaus.org.vrtl-vmf-sa > kickstart.larsenhaus.org.tftp:
27 RRQ "pxelinux.0" octet tsize 0
19:42:22.932113 IP (tos 0x0, ttl 20, id 7, offset 0, flags [none], proto
UDP (17), length 60)
dhcp-101.larsenhaus.org.newlixengine > kickstart.larsenhaus.org.tftp:
32 RRQ "pxelinux.0" octet blksize 1456
But no boot.
During my research I saw a post somewhere that talked about tftp having
issues with some RealTek network cards. The kickstart server is running a
controller with the RTL8101E/RTL8102E chipset. The poster said he fixed his
problem by setting the tftp block size explicitly to 512, but I've been
unable to determine how to do so.
Are there any obvious errors in my configuration? If not, can anyone advise
how to set the tftp block size? Thanks in advance.
James
10 years, 7 months