Re: SL 6.0 printer-configuration problems
On 19 March 2011 01:22, Rick wrote: > kmod-lp worked perfectly for me too. Thank you, Alan. Thanks for letting me know, Rick. I'll pass your news on to the ELRepo Admin team. Alan. (On behalf of the ELRepo Project.)
Re: SL 6.0 printer-configuration problems
kmod-lp worked perfectly for me too. Thank you, Alan.
Re: SL 6.0 printer-configuration problems
On 18 March 2011 20:08, Spencer Buckner wrote: > On 03/17/2011 05:21 PM, Akemi Yagi wrote: > On Thu, Mar 17, 2011 at 3:51 PM, Spencer Buckner > wrote: > I am using System->Administration->Printing to configure an HP DeskJet 500 > printer connected to the parallel port of a stand-alone computer (not part > of a network). The HP DeskJet 500 is the only printer connected to the > computer and is specified to be the default printer. > SL6 does not have parallel port support (it was dropped upstream). But > ELRepo comes to the rescue :-) > > http://elrepo.org/tiki/kmod-lp > After installing kmod-lp and configuring the printer again, printing the > test page worked on the first try! Excellent news. Thanks you for reporting back with details of your success. Alan. (On behalf of the ELRepo Project.)
Re: SL 6.0 printer-configuration problems
On Fri, Mar 18, 2011 at 1:08 PM, Spencer Buckner wrote: > On 03/17/2011 05:21 PM, Akemi Yagi wrote: > > On Thu, Mar 17, 2011 at 3:51 PM, Spencer Buckner > wrote: > > I am using System->Administration->Printing to configure an HP DeskJet 500 > printer connected to the parallel port of a stand-alone computer (not part > of a network). The HP DeskJet 500 is the only printer connected to the > computer and is specified to be the default printer. > SL6 does not have parallel port support (it was dropped upstream). But > ELRepo comes to the rescue :-) > > http://elrepo.org/tiki/kmod-lp > > Try installing that package and see if that solves your problem. > After installing kmod-lp and configuring the printer again, printing the > test page worked on the first try! > > Thank you very much. > > Spencer Glad to hear it worked. You are quite welcome (on behalf of Alan who built the package). Akemi
Re: SL 6.0 printer-configuration problems
On 03/17/2011 05:21 PM, Akemi Yagi wrote: On Thu, Mar 17, 2011 at 3:51 PM, Spencer Buckner wrote: I am using System->Administration->Printing to configure an HP DeskJet 500 printer connected to the parallel port of a stand-alone computer (not part of a network). The HP DeskJet 500 is the only printer connected to the computer and is specified to be the default printer. (snip) I have seen messages from Ubuntu users with the same problems but have not found any understandable fixes. Can anyone help? SL6 does not have parallel port support (it was dropped upstream). But ELRepo comes to the rescue :-) http://elrepo.org/tiki/kmod-lp Try installing that package and see if that solves your problem. Akemi After installing kmod-lp and configuring the printer again, printing the test page worked on the first try! Thank you very much. Spencer
Re: PXE kernel on SL6 missing network drivers for Dell Optiplex 380
On 03/18/2011 10:10 AM, Simon Butcher wrote: Hello Attempting to perform a network kickstart from a local mirror on a Dell Optiplex 380 with the onboard Broadcom BCM57780 Gigabit ethernet controller. It appears that the pxe boot kernel on SL60 does not have the drivers, although SL55 definitely has them and we regularly kickstart these machines with SL55 (and SL54 i think also worked). SL53 did not. However for SL60 not to have them is a considerable regression. I am using the pxeboot images mirrored from: http://rsync.scientificlinux.org/linux/scientific/6.0/i386/os/images/pxeboot/ Anyone have any insights, or confirm/deny this behaviour for this network card (or workarounds not involving physical media)? regards Hi, Do you know which driver it is? Also, have to you tested yet with the non pxe install images? Troy -- __ Troy Dawson daw...@fnal.gov (630)840-6468 Fermilab ComputingDivision/SCF/FEF/SLSMS Group __
PXE kernel on SL6 missing network drivers for Dell Optiplex 380
Hello Attempting to perform a network kickstart from a local mirror on a Dell Optiplex 380 with the onboard Broadcom BCM57780 Gigabit ethernet controller. It appears that the pxe boot kernel on SL60 does not have the drivers, although SL55 definitely has them and we regularly kickstart these machines with SL55 (and SL54 i think also worked). SL53 did not. However for SL60 not to have them is a considerable regression. I am using the pxeboot images mirrored from: http://rsync.scientificlinux.org/linux/scientific/6.0/i386/os/images/pxeboot/ Anyone have any insights, or confirm/deny this behaviour for this network card (or workarounds not involving physical media)? regards -- Simon Butcher Computer and IT Systems Manager School of Mathematical Sciences, Queen Mary, University of London
Re: Marking SL errata packages as such in Spacewalk
On 15 March 2011 19:48, Troy Dawson wrote: > On 03/15/2011 02:28 PM, Matthew Willsher wrote: > >> On 12 Mar 2011, at 22:24, Matthew Willsher wrote: >> >> I've been having some fun with Spacewalk and have been trying to get >>> errata to get correctly marked in the errata view automagically. Having done >>> some searching around I've found some references that seem to indicate that >>> it can be made to work with SL somehow. Is there any way to get the errata >>> working with SL? >>> >> >> I just wanted to check this again before I start doing some scripting to >> attempt to parse the errata mailing list archive. Anything would be helpful, >> no matter how rough. >> > > Hi Matt, > Hi Troy, > Sorry for not replying. > No problem - I'm not in any rush :) > There are two ways of doing this. > > 1 - simple and easy, no real descriptions, just marking packages as > security or fastbugs. > That should be easy enough by going through the SL yum repo's. > This is the approach I'll use I think. I'll see if I can come up with something that parse the rhn.redhat.com/errata list, which is public, and cross reference that to the SL errata mailing list perhaps. Or I might just do it manually :) > 2 - Having all the detail for each errata. > For that you need to have a current RHEL machine and an account on rhn. > You download the errata metadata, convert it to whatever you want (if it's > your personal spacewalk, I suspect you don't need to convert much) and then > push it up onto your spacewalk server. > I was giving option 2 some serious consideration but it appears to fall foul of the RH license agreement, in particular the Appendix 1, Paragraph 1: Any unauthorized use of the Subscription Services is a material breach of the Agreement, such as [...] (e) using Subscription Services to support or maintain any non-Red Hat Software products. It does go on to say 'For the purposes of this paragraph (for example, in calculating the total number of Units of Software), Software would include versions or copies that have the Red Hat trademark(s) and/or logo file(s) removed'. I don't know if SL, CentOS etc class as a 'version or copy' of RHEL in this context. Even if it does it it means that if I were to use 2. I would need an additional subscription for that purpose, and then quite likely need a further subscription with RHEL for every other instance of SL using that data. The usual disclaimer applies - I am not a lawyer. Kind regards, Matt
Re: Persistent Data in SL LiveDVD on USB
Many Many thanks Urs, Will surely follow your suggestions, once I have a window. I believe persistence will work smoothly now! Regards, William. --- On Thu, 3/17/11, Urs Beyerle wrote: From: Urs Beyerle Subject: Re: Persistent Data in SL LiveDVD on USB To: "William Shu" Cc: scientific-linux-us...@fnal.gov Date: Thursday, March 17, 2011, 11:38 PM Hi William, You have definitely no overlay file with the name "overlay--4C04-9372" in /LiveOS folder on your USB stick. So overlay will not work. > [root@livecd sluser]# dir /overlayfs/LiveOS/ > home.img osmin.img squashfs.img It's hard to say why this happened. However, it should be possible to create the overlay file just manually. Change to the /LiveOS on your USB stick and run dd if=/dev/zero of=overlay--4C04-9372 count=1024 bs=1M This will create a 1024 MB file (/LiveOS/overlay--4C04-9372) filled with zeros. If you now boot your USB stick the file /LiveOS/overlay--4C04-9372 should be found and take to store the persistence changes. Please note that the overlay file should not be used completely: http://www.livecd.ethz.ch/usbdisk.html#limits In worst case you can just remove it again and start with a new and "empty" one. Cheers, Urs On 03/17/2011 08:56 PM, William Shu wrote: Dear Urs, What I obtained is below. Unfortunately, a bit mobile now, I have only the USB stick to work on SL6 and so cannot un-install it as such; but I had no complaints! I recall when installing SL6 on the USB that I had warning about its label (made up of some control-character sequence, starting, I think, with ^17). Since installation was complete, and in prior attempts the label was changed, I did not think it was a problem. Now, I'm not so sure! Regards, William. [sluser@livecd ~]$ su [root@livecd sluser]# dir /LiveOS/overlay--4C04-9372 dir: cannot access /LiveOS/overlay--4C04-9372: No such file or directory [root@livecd sluser]# dir /LiveOS/overlay--4C04-9372 [root@livecd sluser]# find / -iname "*4C04-9372*" -print /dev/disk/by-uuid/4C04-9372 /dev/.udev/links/disk\x2fby-uuid\x2f4C04-9372 [root@livecd sluser]# mkdir /overlayfs [root@livecd sluser]# mount -n -t auto UUID=4C04-9372 /overlayfs [root@livecd sluser]# [ -f /overlayfs/LiveOS/overlay--4C04-9372 -a -w /overlayfs/LiveOS/overlay--4C04-9372 ] && echo ok [root@livecd sluser]# dir /overlayfs/ boot/ EFI/ LiveOS/ syslinux/ [root@livecd sluser]# dir /overlayfs/LiveOS/ home.img osmin.img squashfs.img [root@livecd sluser]# William --- On Thu, 3/17/11, Urs Beyerle wrote: From: Urs Beyerle Subject: Re: Persistent Data in SL LiveDVD on USB To: "William Shu" Cc: scientific-linux-us...@fnal.gov Date: Thursday, March 17, 2011, 10:00 AM Hi William On 03/17/2011 06:15 AM, William Shu wrote: Thank you very much Urs. Below are the requested outputs: (A) for losetup; and (B) for dracut. It seems the overlay is not being found! On a related matter, you say livecd-tools and liveusb-creator are part of the live iso's, but I had to "yum install" them before I could use them in making the USB! Thanks for the debug info. You are right. liveusb-creator is not part of Live iso's. But livecd-tools and therefore livecd-iso-to-disk should be installed. However, doing "yum update livecd-tools" is always a good idea. Yes, the overlay is not found in your case: dracut: + mkdir /overlayfs dracut: + mount -n -t auto UUID=4C04-9372 /overlayfs dracut: + [ -f /overlayfs/LiveOS/overlay--4C04-9372 -a -w /overlayfs/LiveOS/overlay--4C04-9372 ] dracut: + umount -l /overlayfs dracut: + [ -z ] dracut: + [ -n UUID=4C04-9372 -a -n /LiveOS/overlay--4C04-9372 ] dracut: + warn Unable to find persistent overlay; using temporary Can you quickly check, if the overlay file is on your Live USB drive and if it is writable (w)? In your case the overlay file should be /LiveOS/overlay--4C04-9372 You might want to reproduce the mounting of your USB stick (as done be dracut) on a SL6 system. Plugin the stick. If it gets auto-mounted, un-mount it. As root try mkdir /overlayfs mount -n -t auto UUID=4C04-9372 /overlayfs [ -f /overlayfs/LiveOS/overlay--4C04-9372 -a -w /overlayfs/LiveOS/overlay--4C04-9372 ] && echo ok Cheers, Urs
Re: GDM theme
On 3/17/2011 15:42, Vaclav Mocek wrote: On 03/17/2011 09:21 PM, Chris Tooley wrote: How do I change the theme for GDM in SL6? Not sure, it has been changed in Fedora 12/13 and SL6 uses the same way. If you want to change the background of the login screen, change the file "default.xml" in "/usr/share/backgrounds/"; there is a file "tuv.xml" which is . The rewritten GDM gets its configuration from gconf [1], so if you want to change any settings you should edit the "gdm" user's gconf settings. For instance, if I wanted to disable the login screen's restart buttons I would run this: gconftool-2 --direct --config-source xml:readwrite:/var/lib/gdm/.gconf -s /apps/gdm/simple-greeter/disable_restart_buttons --type bool false Rather than changing the XML files in /usr/share/backgrounds to change the login screen's background you can likewise edit another gconf setting: gconftool-2 --direct --config-source xml:readwrite:/var/lib/gdm/.gconf -s /desktop/gnome/background/picture_filename --type string /path/to/your/preferred/background The commands above are both from memory, so make sure to double-check them before trying them. ;-) [1] http://library.gnome.org/admin/gdm/2.28/configuration.html.en -- Garrett Holmstrom
