Re: 5-star Fedora experience
On Sunday, June 19, 2011 10:58:28 AM Fernando Cassia wrote: > 73 year olds say "how cool"? I thought ´cool´ was a 1980s thing (sorry, > English is not my native language :) In a local restaurant, there is an old advertisement poster for men's boxer shorts, and in quotes the word 'coolness.' My oldest teenage daughter saw that and wondered about the 'modern' advertisement. Fortunately, there was a copyright date on the poster. The date? 1915. What's old is new again. It's quite possible that a little over twenty years after that ad was published the shorter 'cool' was still in use, around the time a 73 year-old would have been born. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: backup copy of F14 boots, but can't login
On Monday, June 27, 2011 04:41:43 PM jackson byers wrote:
> My backup copy of F14 boots, all looks normal,
> boot messages all "OK"
>
> but then I can't login: after entering my password
> the screen recycles to the login screen,
> and continues to do this if I keep trying.
Home directories require specific SELinux contexts. If you have SELinux on and
enforcing, and you back up /home without backing up the SELinux contexts this
will happen. If you go to a text console (Ctrl-Alt-F2 for one), and try to log
in there, if this is the problem it should tell you that it can't change the
working directory.
Either backup with an SELinux context preserving tool (such as star or dump or
a disk clone) or run fixfiles ('fixfiles relabel' or 'touch /.autorelabel' and
reboot)).
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: backup copy of F14 boots, but can't login
On Tuesday, June 28, 2011 07:44:32 AM Daniel J Walsh wrote:
> > Either backup with an SELinux context preserving tool (such as star or dump
> > or a disk clone) or run fixfiles ('fixfiles relabel' or 'touch
> > /.autorelabel' and reboot)).
> Easier is to just run
>
> restorecon -R -v /home
If only /home needs relabeling, that is true.
However, if /home is backed up without the correct contexts, the rest of the
system likely has context problems.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: kde desktop
On Aug 31, 2011, at 7:14 AM, Adel ESSAFI wrote: was the KDE desktop removed in F15?? No. KDE Software Compilation I don't find the corresponding group Yes, you did. The KDE Software Compilation is the current upstream name. smime.p7s Description: S/MIME cryptographic signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: "why is my Linux so damn slow?"
On Saturday, February 12, 2011 12:19:33 pm M. Fioretti wrote: > besides hard drive and DVD burner there are only Logitech webcam, > wheelmouse and earphone microphone, but everything is plugged in the > back which is not really accessible without moving furniture. I'll do > that if needed, but isn't a way to check for those interrupts from the > prompt? Let's see if iowaits are you issue. Install the sysstat package (yum install sysstat) and run: iostat -x 1 (this gives extended information on the disk, and updates at one second intervals) The number to look at is 'await' times, expressed in milliseconds. If those numbers are high, it's something with your drive. Also, if you run 'top' what does it show? I saw an F13 system brought to its knees due to a WD EADS series 'green' drive triggering insane awaits of multiple thousands of milliseconds, and system load averages in excess of 20. The command that reliably triggered the behavior was a simple 'yum update' from the command line, or the automatic packagekit update process; load averages went through the roof, and the system slowed to a slow crawl. Replaced the WD EADS series drive with a Seagate of the same capacity, and the problem went away. Now, in this specific case, the EADS drive was one half of a RAID-1 mirror, where the other half was a Seagate; the EADS drives and RAID don't get along. But others have reported performance issues with these drives not in a RAID configuration, with recent kernels; older kernels seemed to work better. I'd check that even though the WD2500JS-41MVB1 drive is a 'Caviar Blue' and not a Green drive. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: "why is my Linux so damn slow?"
On Saturday, February 12, 2011 02:15:02 pm Rick Sewill wrote: > Someone help us...I know there is a command to show open files, lsof. > Does that command include a way to find out disk activity per file or > is there another command that can find out disk activity per file? > I'm hoping, if we identify the file(s) with disk activity, we might identify > the service/application/kernel feature that is hogging the cpu. There is the 'iotop' package, which give I/O per process, but doesn't list files. Both iotop and top can be run in a batch mode with the -b switch; both can run a specified number of iterations with the -n # switch (where # is the number of iterations, infinite by default). Like many others I'm not seeing this issue; my box being a tad older, a Dell Precision M65 laptop with a 2.16GHz Core2Duo and 4GB of RAM, running the x86_64 dist. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: "why is my Linux so damn slow?"
On Saturday, February 12, 2011 02:42:25 pm Rick Sewill wrote: > I am curious about the Rescheduling interrupts. > I do not have a dual core system so I have no rescheduling interrupts. I do; here's my /proc/interrupts and uptime: lowen@localhost:~$ cat /proc/interrupts CPU0 CPU1 0:2368837 0 IO-APIC-edge timer 1: 17017 0 IO-APIC-edge i8042 4: 3 0 IO-APIC-edge 8: 1 0 IO-APIC-edge rtc0 9: 2 0 IO-APIC-fasteoi acpi 12:144 0 IO-APIC-edge i8042 14: 218006 0 IO-APIC-edge ata_piix 15: 229960 0 IO-APIC-edge ata_piix 16: 31864 0 IO-APIC-fasteoi nvidia 17: 22394 0 IO-APIC-fasteoi eth1 19: 8 0 IO-APIC-fasteoi yenta, firewire_ohci 20: 134569 0 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb2 21: 71 0 IO-APIC-fasteoi uhci_hcd:usb3 22: 0 0 IO-APIC-fasteoi uhci_hcd:usb4 23: 0 0 IO-APIC-fasteoi uhci_hcd:usb5 45:399 0 PCI-MSI-edge hda_intel 46: 191211 0 PCI-MSI-edge eth0 NMI: 0 0 Non-maskable interrupts LOC:20651792870695 Local timer interrupts SPU: 0 0 Spurious interrupts PMI: 0 0 Performance monitoring interrupts PND: 0 0 Performance pending work RES:19574922326386 Rescheduling interrupts CAL: 9221 16385 Function call interrupts TLB: 8814 10449 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts MCE: 0 0 Machine check exceptions MCP: 58 58 Machine check polls ERR: 1 MIS: 0 lowen@localhost:~$ uptime 15:47:24 up 4:51, 7 users, load average: 0.02, 0.09, 0.12 lowen@localhost:~$ (don't let the '7 users' throw you; that's just my 7 konsole tabs open.) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: "why is my Linux so damn slow?"
On Saturday, February 12, 2011 04:11:22 pm Aaron Konstam wrote: > I have noi Disk Utility under System->Administration. What is its real > name? palimpsest, which is provided by the gnome-disk-utility package. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: "why is my Linux so damn slow?"
On Saturday, February 12, 2011 04:48:46 pm compdoc wrote: > >> 7.024044] i2c i2c-0: nForce2 SMBus adapter at 0x600 > > AMD's Socket A. Pretty old, slow system. It's possible it doesn't implement > APIC and ACPI correctly. Someone suggested a bios update - if there is one, > that would be a good idea. Uh, by /proc/cpuinfo it's a Socket AM2 Athlon 4850e, which isn't too awfully old. Socket A was pre-Athlon64, and definitely not capable of 8GB of RAM. The motherboard he referenced is an ASUS M3N78-EM, which is a current product at NewEgg, among other vendors. > Does the command 'smartctl -a /dev/sda' show any reallocated sectors? That's a thought. Palimpsest (Disk Utility) includes a utility to run SMART tests; launch Disk Utility, select the disk, click on 'SMART Data', then select the test you'd like. It also lists the SMART information from the drive. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Where can I find a functional nslookup?
On Feb 13, 2011, at 1:03 PM, Bill Davidsen wrote: and a loud majority which feels that Linux is a toy OS because it's not "real UNIX" based. That's management as well as workers. Well, you could always ask them why IBM chose Linux for their Watson supercomputer system. smime.p7s Description: S/MIME cryptographic signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
USB 3.0 support, and results.
For future information searches. Bought a USB 3.0 external 2.5 inch hard drive the other day (WD 500GB 'My Passport Essential'), and bought a Goe (Generic off-eBay) ExpressCard USB 3.0 controller (generic NEC xHCI), and have now had opportunity to set up and test. The first thing, of course, was to re-enable USB 3.0 (xHCI) functionality; found that on the F14 bugs page ( http://fedoraproject.org/wiki/Common_F14_bugs#USB_3.0_ports_not_working ). Once that was done, the WD drive came up fine, and at SuperSpeed. (I can see it now: USB 6.0, with LudicrousSpeed!) Sorry, I digress. Anyway, I reformatted the drive (after copying the WD software off of it) as ext4, which was quite fast for a 500GB drive. Palimpsest (Disk Utility) tells me that it's connected at 705.0MB/s. How nice. Read preformance is essentially what I would expect of a SATA or eSATA 2.5 inch laptop drive in the low-power category, with read performance, according to hdparm, clocking at roughly 50MB/s. That's slower than the internal drive, a decidedly non-low-power Seagate 7200RPM 500GB 2.5 inch Momentus SATA-II drive, which clocks in at 93.5MB/s (hdparm -t, of course, take it with a grain of salt), but faster than the Seagate 320GB USB2 external, which manages 28.24MB/s, not bad for USB2. As the main purpose of the drive is for backups, I rsync'd my home directory over to it: roughtly 246GB of data in 2 hours and 8 minutes. Not bad at all, and less than half of the time it would have taken on the USB2 drive. Bonnie++ results are as follows (hard to read in proportional font; view in fixed point to get things lined up): .. Version 1.96 --Sequential Output-- --Sequential Input- --Random- Concurrency 1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP localhost.locald 6G 320 97 46635 11 16536 5 1675 96 52486 9 104.2 3 Latency 33221us 611ms 679ms 70682us 51564us3277ms Version 1.96 --Sequential Create-- Random Create localhost.localdoma -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 9493 54 + +++ 26436 59 13819 78 + +++ 24948 57 Latency 177us1123us 813us 200us 193us 118us Overall a good experience so far; we'll see how it goes over the next weeks and months. Now I'm on the prowl for a USB3 version of my Thermaltake blaX drive doc.and there are plenty of other brands out there, as I see with a quick look at eBay. I do note, however, that transfers use more CPU than transfers with eSATA to the Thermaltake's eSATA port, and so that's definitely a consideration. But the USB3 drive doesn't need a second wire for power, and the equivalent eSATA (not eSATAp) enclosures, like the Rocketfish units I've been using. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: USB 3.0 support, and results.
On Saturday, February 19, 2011 10:13:08 pm Chris Smart wrote: > So that ran at about 35MB/sec, which is probably what I'd expect on a > USB2.0 drive anyway. > What would be interesting, is if you repeated the test after taking > the drive out of the USB 3.0 enclosure and putting it into a USB 2.0 > one.. The easier thing is to connect the USB3 cable from the drive to a USB2.0 port (the PC side of a USB3.0 cable is downwards compatible; the device side connectors are not). Speed halves when I do that; re-rsyncing everything (all 246GB; I removed it all (I literally zeroed out the drive, remade the ext4 filesystem), and started from scratch)) took almost exactly twice as long, 5 hours and 14 minutes. The large number of small files in my .kde tree (mail, for one) slows things down; the VMware .vmdk's give a better indication of the true throughput of the drive. USB2's absolute max sustained speed on most EHCI implementations is ~32MB/s; even the average 35MB/s of the initial USB3 rsync is beyond that reach by 3MB/s, and that included the 195,000 files (consuming 6.7GB) that is my .kde tree. And then the development tree, with a number of svn checkouts: 422,000 files in 6.8GB of space. That sort of 'lots of small files' situation really slows down the transfer rate for rsync. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Old RH in production (Re: fc8 upgrade)
On Sunday, February 27, 2011 06:50:28 am Roberto Ragusa wrote: > I see your RH8 in a VM and raise a RH7.2 in a VM. :-) > For an Internet facing service, nonetheless! And I'll raise you an RH5.2, still running after nearly thirteen years. On physical hardware. It's just about to be decommissioned, with the one old app migrated to a CentOS 2.1 VM (the app needs libc5). The app does what is needed; and this one is not internet facing. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: SD card not seen by system after unmounting
On Sunday, March 06, 2011 01:49:20 pm Gordon Charrick wrote: > This is wierd. I've got a multicard reader installed on my Fedora 14 > system. If I insert an SD card, it gets recognized and mounted right > away. If I unmount the card, remove it, and reinsert it, the system does > nothing. No entries in the messages file about the device or anything. > If I want to use the SD card again, I have to reboot. > > Has anyone seen something like this before? Ideas on how to debug the > problem? Yes, I have seen it, in GNOME and in KDE, a few times. I predominantly use KDE, and it seems to be working in KDE now. As in I just put an SD card into the reader, opened it in dolphin, and used the dolphin 'safely remove' option; pulled the SD card from the reader, waited a few seconds (10 or so; log tells me it was 9), plugged the card back in, and it came right up. A client of mine who is still at Fedora 13 and is a GNOME user saw this issue, and found this was the way to get it working on his system: "I've tried something different and after 4 times, it's worked every time. What I'm doing now to remove a flash card from the reader, instead of usual - logical "safe to remove" option, try using the "eject" option. Thus far, it seems to be working." Can you try that and see what happens? (assuming you have an eject option; I'm not a GNOME user, and don't have the full GNOME installed on this box) I've also found that at least with KDE it seems to always be best to wait until you're logged in and the system has become somewhat quiescent before hotplugging any removable storage; at least my USB 3 external wasn't recognized at all when I booted with it plugged in, and the system refused to see it even after unplugging and replugging, but restarting with it not plugged in, then plugging it in after logging in worked ok. Made me a little nervous at first! (note for those who didn't see or have forgotten my first message on this: no, USB 3 does not work 'out of the box' with Fedora 14, you do have to do something special, and that something special is documented on the fedoraproject.org website, so if you need the info, go find it there or in the archives of this list.) (Also note that, yes, I do know my kernel is a rev old; I have installed the updates since, but since i use the nvidia driver, and there was a little bit of delay in delivery of the kmod-nvidia for the update, I set this particular kernel to boot in grub.conf; yes, I do need to set that back now that the updated kmod-nvidia is out there.) Here's the relevant /var/log/messages sections (which, since it spanned 5AM, spanned two files, /var/log/messages, and /var/log/messages-20110307) for my SD card swap a few minutes ago: ++ Mar 7 04:56:31 localhost kernel: [ 1177.005191] sd 2:0:0:0: [sdb] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB) Mar 7 04:56:31 localhost kernel: [ 1177.005935] sd 2:0:0:0: [sdb] Assuming drive cache: write through Mar 7 04:56:31 localhost kernel: [ 1177.007432] sd 2:0:0:0: [sdb] Assuming drive cache: write through Mar 7 04:56:31 localhost kernel: [ 1177.007438] sdb: sdb1 Mar 7 04:56:40 localhost hald: mounted /dev/sdb1 on behalf of uid 501 Mar 7 05:04:24 localhost hald: unmounted /dev/sdb1 from '/media/disk' on behalf of uid 501 Mar 7 05:13:35 localhost kernel: [ 2200.994365] sd 2:0:0:0: [sdb] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB) Mar 7 05:13:35 localhost kernel: [ 2200.995227] sd 2:0:0:0: [sdb] Assuming drive cache: write through Mar 7 05:13:35 localhost kernel: [ 2200.999476] sd 2:0:0:0: [sdb] Assuming drive cache: write through Mar 7 05:13:35 localhost kernel: [ 2200.999487] sdb: sdb1 Mar 7 05:13:48 localhost hald: mounted /dev/sdb1 on behalf of uid 501 Log sections dealing with the USB 3 drive's issue: lspci line: 0d:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03) lsusb line (current working): Bus 006 Device 002: ID 1058:0730 Western Digital Technologies, Inc. lsusb tree section for bus 6: Bus# 6 `-Dev# 1 Vendor 0x1d6b Product 0x0003 `-Dev# 2 Vendor 0x1058 Product 0x0730 /var/log/messages lines for first, unsuccessful try with disk plugged in at powerup: Mar 7 04:27:51 localhost kernel: [8.509681] xhci_hcd :0d:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 Mar 7 04:27:51 localhost kernel: [8.509925] xhci_hcd :0d:00.0: xHCI Host Controller Mar 7 04:27:51 localhost kernel: [8.510650] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 6 Mar 7 04:27:51 localhost kernel: [8.510877] xhci_hcd :0d:00.0: irq 19, io mem 0xdcdfe000 Mar 7 04:27:51 localhost kernel: [8.514183] usb usb6: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values Mar 7 04:27:51 localhost kernel: [8.514195] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003 Mar 7 04:27:51 localhost kern
Re: SD card not seen by system after unmounting
On Monday, March 07, 2011 06:01:10 am Lamar Owen wrote: > Here's the relevant /var/log/messages sections (which, since it spanned 5AM, > spanned two files, /var/log/messages, and /var/log/messages-20110307) for my > SD card swap a few minutes ago: > ++ > Mar 7 04:56:31 localhost kernel: [ 1177.005191] sd 2:0:0:0: [sdb] 3842048 > 512-byte logical blocks: (1.96 GB/1.83 GiB) Of course, I forgot a few lines; also, note that some dedicated SD readers aren't hot-swap on the SD side, but only on the USB side; my Targus reader does do hotswap on the SD side: ++ Mar 7 04:37:12 localhost kernel: [0.952883] ehci_hcd: USB 2.0 'Enhanced' Ho st Controller (EHCI) Driver Mar 7 04:37:12 localhost kernel: [0.952914] ehci_hcd :00:1d.7: PCI INT A -> GSI 20 (level, low) -> IRQ 20 Mar 7 04:37:12 localhost kernel: [0.952937] ehci_hcd :00:1d.7: EHCI Hos t Controller Mar 7 04:37:12 localhost kernel: [0.952997] ehci_hcd :00:1d.7: new USB bus registered, assigned bus number 1 Mar 7 04:37:12 localhost kernel: [0.953026] ehci_hcd :00:1d.7: using br oken periodic workaround Mar 7 04:37:12 localhost kernel: [0.953038] ehci_hcd :00:1d.7: debug po rt 1 Mar 7 04:37:12 localhost kernel: [0.956943] ehci_hcd :00:1d.7: irq 20, io mem 0xffa8 Mar 7 04:37:12 localhost kernel: [0.966019] ehci_hcd :00:1d.7: USB 2.0 started, EHCI 1.00 Mar 7 04:37:12 localhost kernel: [0.966045] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 Mar 7 04:37:12 localhost kernel: [0.966048] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 7 04:37:12 localhost kernel: [0.966050] usb usb1: Product: EHCI Host Controller Mar 7 04:37:12 localhost kernel: [0.966052] usb usb1: Manufacturer: Linux 2.6.35.10-74.fc14.x86_64 ehci_hcd Mar 7 04:37:12 localhost kernel: [0.966054] usb usb1: SerialNumber: :00:1d.7 Mar 7 04:37:12 localhost kernel: [1.588066] usb 1-4: new high speed USB device using ehci_hcd and address 4 Mar 7 04:37:12 localhost kernel: [1.704395] usb 1-4: New USB device found, idVendor=058f, idProduct=6366 Mar 7 04:37:12 localhost kernel: [1.704399] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 7 04:37:12 localhost kernel: [1.704403] usb 1-4: Product: Mass Storage Device Mar 7 04:37:12 localhost kernel: [1.704405] usb 1-4: Manufacturer: Generic Mar 7 04:37:12 localhost kernel: [1.704407] usb 1-4: SerialNumber: 058F63666471 Mar 7 04:37:12 localhost kernel: [1.763519] Initializing USB Mass Storage driver... Mar 7 04:37:12 localhost kernel: [1.763706] scsi2 : usb-storage 1-4:1.0 Mar 7 04:37:12 localhost kernel: [1.763816] usbcore: registered new interface driver usb-storage Mar 7 04:37:12 localhost kernel: [1.763819] USB Mass Storage support registered. Mar 7 04:37:12 localhost kernel: [2.764068] scsi 2:0:0:0: Direct-Access MultiFlash Reader 1.00 PQ: 0 ANSI: 0 Mar 7 04:37:12 localhost kernel: [2.764831] sd 2:0:0:0: Attached scsi gener ic sg2 type 0 Mar 7 04:37:12 localhost kernel: [2.767418] sd 2:0:0:0: [sdb] Attached SCSI removable disk [and then the lines I've already posted] + -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: fc14 upgrade fails, system now in partially-upgraded state...
On Monday, March 07, 2011 02:03:20 pm Alex wrote: > Hi, > > I started an upgrade from fc13 x86_64 to fc14 x86_64, and the computer > locked up during the install. I thought the problem with the PC was > that it was locking up due to insufficient memory. I've added more > memory, but now the upgrade won't complete. While you've been given the advice to reinstall, much like a Windows system, there is one other utility you can try first, if you haven't completely blown out the yum transaction, that is. yum install yum-utils yum-complete-transaction That's probably a slim possibility, but I had to do that with one F13->F14 upgrade; but yum-complete-transaction was the very first command I ran, and I didn't try another install in between, and the repositories hadn't changed enough to change the contents of the yum transaction (which will abort it). Another possibility is to run package-cleanup --dupes to list the duplicates, an rpm -aq to list all packages, edit out the dupes, then manually install the needed rpms to upgrade from the DVD. Good luck. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: rename flash drive auto mount point
On Friday, March 25, 2011 09:56:19 pm Kevin J. Cummings wrote: > But, the version of mlabel that Fedora provides does *not* support the > -i flag that the posted solution says to use. Perhaps the -i flag is an > Ubuntu only extension to their version of mlabel? > > So Aaron is right, the posted solution is not useful to Fedora users. Sorry, please read the full relevant manual section at: http://www.gnu.org/software/mtools/manual/mtools.html#SEC5 Then try the '-i' option; no, it doesn't show up in the man page, but that's because it's a GNU program stuck on texinfo instead of man pages. Repeating: for *many* GNU-originated packages the man pages are incomplete, and you must use the texinfo manual. Or you will be using outdated, unmaintained, documentation since the man pages aren't well maintained, since the primary docs for those packages are in texinfo format. Or to demonstrate: [root@localhost ~]# uname -r 2.6.35.11-83.fc14.x86_64 [root@localhost ~]# rpm -q mtools mtools-4.0.13-2.fc14.x86_64 [root@localhost ~]# mlabel --help Mtools version 4.0.13, dated February 28th, 2010 Usage: mlabel [-vscVn] [-N serial] drive: [root@localhost ~]# mlabel -i /dev/sdc1 -s :: Volume has no label [root@localhost ~]# which dosfslabel /sbin/dosfslabel [root@localhost ~]# dosfslabel /dev/sdc1 FEDORA [root@localhost ~]# Note that the label seen and manipulated by dosfslabel is the one that F14 is using for the mount point: [root@localhost ~]# mount [snip] /dev/sdc1 on /media/FEDORA type vfat (rw,nosuid,nodev,uid=501,utf8,shortname=mixed,flush) [root@localhost ~]# So the answer for the OP: use dosfslabel since it seems to really change the label that F14 is using. The mlabel utility, while it seems to be doing the proper thing with -i, isn't picking up the proper label. Good grief, guys, check your facts before posting that the version the poster is using isn't in F14. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: External HDD auto-mounted as root
On Saturday, March 26, 2011 01:04:31 am JD wrote: > That said, I do not know of any way that will let you > connect your drive to any (Linux?) system and expect it to be automounted > onto some specific mount point (assuming the mount point exists). F14 at least will take an ext4 formatted disk and automount it to /media/$LABEL where the label is set with e2label. Likewise with any filesystem F14 supports, using the filesystem-appropriate label utility. As to ownership, you have to set that after it's mounted with the normal filesystem tools. Example: [root@localhost ~]# mount [snip] /dev/sdb1 on /media/wd500gbu3-bak type ext4 (rw,nosuid,nodev) [root@localhost ~]# e2label /dev/sdb1 wd500gbu3-bak [root@localhost ~]#dmesg [snip] [ 27.017416] usb 6-1: new SuperSpeed USB device using xhci_hcd and address 2 [ 27.029856] xhci_hcd :0d:00.0: WARN: short transfer on control ep [ 27.030227] xhci_hcd :0d:00.0: WARN: short transfer on control ep [ 27.030609] xhci_hcd :0d:00.0: WARN: short transfer on control ep [ 27.031094] xhci_hcd :0d:00.0: WARN: short transfer on control ep [ 27.031281] usb 6-1: New USB device found, idVendor=1058, idProduct=0730 [ 27.031290] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 27.031297] usb 6-1: Product: My Passport 0730 [ 27.031301] usb 6-1: Manufacturer: Western Digital [ 27.031306] usb 6-1: SerialNumber: YOUDIDNTTHINKIDLEAVETHISHEREDIDYOU [ 27.121613] Initializing USB Mass Storage driver... [ 27.121766] scsi2 : usb-storage 6-1:1.0 [ 27.121876] usbcore: registered new interface driver usb-storage [ 27.121879] USB Mass Storage support registered. [ 29.104203] scsi 2:0:0:0: Direct-Access WD My Passport 0730 1012 PQ: 0 ANSI: 6 [ 29.104608] scsi 2:0:0:1: Enclosure WD SES Device 1012 PQ: 0 ANSI: 6 [ 29.107469] sd 2:0:0:0: Attached scsi generic sg2 type 0 [ 29.107640] scsi 2:0:0:1: Attached scsi generic sg3 type 13 [ 32.934134] sd 2:0:0:0: [sdb] 976707584 512-byte logical blocks: (500 GB/465 GiB) [snip] Works just like automount of a USB flash drive does. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Logging system usage -
On Wednesday, March 30, 2011 12:31:31 pm Bob Goodwin wrote: > Is there an application to log system usage that will enable me > to keep track of usage by individual computers on our LAN? [snip] > So I am looking for a scheme for tracking usage by mac or device > address. I check usage daily but when I see a jump upward I need > to know what caused it, I always begin to think through what I > have done before panicking the whole family. Any suggestion > appreciated. ntop is one possibility, and it's present in the Fedora repositories. You need a netflow source; nprobe can do that, and ntop can use built-in interfaces, or can take netflow data from your switch, if that switch is capable of netflow export. You need either what's known as a 'SPAN' port on your switch, or you need a hub on a common connection, possibly the WAN port itself, to be able to sniff all the traffic in lieu of netflow data export. For the DD-WRT side of things, since you mention that you use that, please see: http://netflowninjas.lancope.com/blog/2009/07/turn-your-linksys-into-a-netflow-exporter-ddwrt.html and http://www.dd-wrt.com/wiki/index.php/Useful_tools_for_the_WiFi_Network -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Logging system usage -
On Wednesday, March 30, 2011 02:40:16 pm Bob Goodwin wrote: > Netflow says their application is not intended for home use? > It's not clear to me if that has to be installed in a > computer/router or if it's something I can install here in this > computer or if it might already be installed in some routers out > of the box? Sorry for overwhelming with info; here's the simpler version. Netflow data export is a way the router can keep track of 'flows' of data (think of a flow as a connection; it isn't really, but it's still a good analogy) and export data on those flows passing through it to a 'collector.' DD-WRT apparently has some support for netflow data export (NDE for short) in this manner. One of the links I sent was a page that listed a few things about that, and possibly more links to how to set that up in DD-WRT. Once you have NDE set up to export (but before you actually turn the export on) you need to set up the collector; this is the ntop package that is included in Fedora. It is a web-based application; there are other flow collectors, but the key thing is that the box running the collector needs to have its firewall opened for the export from the router, and the router needs to know to export the flow data to that IP address. Once you have ntop collecting the flows, you can get all kinds of statistics on the top talkers, total bandwidth, connections used, IP addresses contacted, just to start. The setup isn't the easiest in the world; but, then again you have DD-WRT set up, so you've apparently got at least part of the skillset needed. Just tackle it with patience, and you can make that work. A hub and doing the collection with a sniffer and ntop will also work, but hubs have their own problems, and unless you'd just rather do it that way, having the router do NDE is the simplest way of getting the information you want. I'm doing this, using CentOS and ntop, with several Cisco routers of various types (a couple of 12000 series, a 7609, a 7206, a 7507, and a 7401) and it works pretty well. On CentOS 4 ntop isn't exceptionally stable; not a whole lot better on CentOS 5, but I would expect that the latest and greatest running on F14 might be the ticket. But my setup isn't the typical home setup, either, so your mileage may vary. What would be the 'cat's meow' would be ntop or similar integrated into the DD-WRT or other similar router interface, then it's all 'appliance based' and easy. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Logging system usage -
On Wednesday, March 30, 2011 02:52:04 pm Bruno Wolff III wrote: > Maybe start by seeing what you can do with ddwrt to see if that approach is > practical for you at all. Writing scripts to pull counter data periodically > shouldn't be too bad. If the device has any SNMP functionality, the Fedora package of MRTG works fine and will give basic statistics. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Cant get networking working in Fedora14
On Thursday, March 31, 2011 10:37:46 pm r...@dwf.com wrote: > Seems networking should just 'come up' on a new install. > Let the user decide how to tighten up his security, Fedora seems to be > taking the opposite approach. Well, if this were a Fedora-wide issue you'd see lots and lots of threads on the subject, so it's likely localized to your situation. There are a number of things you can still look for. It seems to me that you have layer 2 connectivity issues, since you can't see anything on your LAN, and nothing else on your LAN seems to be seeing this box. Do you have Wireshark installed? If you do, start it up, point it at eth0, start a capture, and see if you see any broadcast traffic. Go to that other machine, .17, and attempt to ping this box; you should see incoming broadcasts (for ARP) in Wireshark on this machine, .99. Or use tcpdump on this machine like you did previously on another machine: > Nope, tcpdump on another machine does not show anything coming > from the machine. If you don't see anything coming in, you may have a port negotiation mismatch with that particular Intel NIC (00:19:D1:75:E3:3E being your MAC address as listed by ifconfig; that's an Intel OUI) and your switch with the kernel driver in the Linux kernel included in Fedora. To see what it's set up for, and which driver is in use, use: ethtool eth0 ethtool -i eth0 ethtool -P eth0 in sequence; the first one will give you some general info, and the second one will tell you what driver is loaded and the bus ID of the NIC, and the third gives you the BIA (burned-in address), just to triple-check that the NIC has the HWADDR it's configured for. Then check your switch (if it's a managed switch) to see what it's negotiating to. Or perhaps you have port security enabled on the switch, or some other networking feature that's contributing to the seeming partitioning of you NIC. As I've already deleted the initial portions of the thread in my fedora folder, I don't recall if you said this NIC worked with another OS, but even then I have seen issues with certain Intel NICs connected to certain switches in Windows before, where the NIC wouldn't always auto-negotiate properly; but it would under Linux, so the reverse possiblity is always there. And it may be a malfunctioning NIC, as the Mythbusters say, failure is always an option. As to earlier versions of Fedora working and this one not, it's a different kernel, possibly different drivers, and udev I'm sure has changed. So I'm thinking, giving you've tried disabling all the security features built-in, that you have a problem at a deeper level, and it's not one that's there by design. Lots and lots of people are experiencing networking properly operating after F14 install, myself included. With multiple machines, and multiple types/brands of ethernet adapters; we just need to find the layer 2 issue you're having that looks almost like either a PHY misconfig/incompatibility or a layer 1 partitioning due to auto-negotiation issues -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: [OT Humor] "Obviously designed by morons"
On Sunday, April 03, 2011 05:17:54 AM Alan Cox wrote: > Still lots of Z80 based ones around in the UK too where the protocol work > is done on a magic box on a serial port - never seen anything running > CP/M however, the stuff I've seen all runs raw on the hardware. Lots of DVD drives use the Z80 and the successor chips (Z180, Z280, eZ80, etc), as have multiple manuafacturer's hard drives see the Z80 wikipedia article for many more. As an old Z80 hack, it's nice to know that skills I picked up as a teenager might still be marketable..I can put on my resume 'wrote a Z80 disassembler in hexadecimal in less than 2K' with a straight face. What I can't/won't do is put with it 'at age 16, in high school, on my free time.' as then it sounds ridiculous. even though it would be quite true. Way way OT at least until Fedora runs on a eZ80, that is. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: [OT Humor] "Obviously designed by morons"
On Tuesday, April 05, 2011 02:29:04 PM Tom Horsley wrote: > On Tue, 5 Apr 2011 14:06:03 -0400 > Lamar Owen wrote: > > Lots of DVD drives use the Z80 and the successor chips > That must explain why it takes 'em 10 minutes to figure > out what kind of disk you just put in the drive :-). Heh. Yours must use a Pentium my Z80-based DVD drive recognizes any disk I put into it within 30 seconds But lots of Fedora-running computers out there have a Z80 somewhere under the hood... (much like the I/O processor of a Tandy 6000 68K Xenix box.) It could be in the hard drive (lots of Seagate drives, mostly during their highly reliable days, have used Z80's as the system controller.). It might be in the NIC. It might be anywhere the hardware needs a system controller; and the Z80 handles that task extremely well. But, again, it would be cool to have a Linux kernel on the newest variant, the eZ80if it'll fit on an MMUless 68K (ucLinux variant) it should fit in the 24-bit space available to the eZ80. Just no Fedora. But that's enough of this OT thread -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: FC13 PS2 Mouse/Keyboard stops working after a while
On Tuesday, April 05, 2011 07:20:40 PM compdoc wrote: > So what you're saying is, while the M-Audio 1010 is working the ps/2 stuff > fails, and when the M-Audio 1010 has stopped working due to > suspend/hibernate the PS/2 stuff works fine. Coincidence? > > I find it odd that anything would interfere with a ps/2 keyboard, since it's > on such a low and well known IRQ. Keyboard is 1 and mouse is 12. I've seen issues with the M-Audio Delta 1010 and other Envy24-based boards with IRQ steering; I have a laptop with a dock that has a PCI slot in it, and have run a Delta 1010LT (same Envy24/ICE1712 chip; and it's the older 'still works with Linux/ALSA' version) in it. If I loaded the nvidia kmod, the nvidia GPU grabs an IRQ; just so happens the PCI slot in the dock and the GPU share the same physical INT line, and either the nvidia or the Envy24's driver apparently doesn't handle IRQ sharing very well. With the nvidia kmod loaded, I get frequent ALSA xruns, which glitch the audio. Running the alternative nvidia drivers found in Fedora just causes performance to drop substantially; I then get JACK xruns, and still have glitches This is both with and without the preemption-RT patched kernel. But it was an older Fedora; haven't tried in a while, since I installed the Delta 1010LT somewhere else and began using a different audio interface on the laptop. To the OP: try putting the Delta 1010 in a different physical PCI slot, or use a USB keyboard (just make sure, using 'cat /proc/interrupts' that the ice1712 entry has its own IRQ and doesn't share with anything else). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: FC13 PS2 Mouse/Keyboard stops working after a while
On Wednesday, April 06, 2011 06:21:25 PM John Mellor wrote: > Interesting. I have the opposite problem on my abit motherboard. The > PS2 mouse happens to work and my preferred USB mouse just locks up about > 5 times per day. > > Is this a known problem with a simple fix? Don't know; I have a client with an F13 box doing the same thing; different motherboard. Haven't gotten any useful troubleshooting information, either. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Cannot do KDE Graphic login
On Wednesday, April 13, 2011 07:21:43 AM Chris Smart wrote: > On Wed, Apr 13, 2011 at 9:19 PM, DB wrote: > > Hi all, > > > > Yet again a problem! > > Are you running NVIDIA driver? Do you have an /etc/X11/xorg.conf file? FWIW, and for the archives, the nvidia kmod driver doesn't show the 'acorn thingy' on boot, but a set of text-mode bars at the bottom of the screen, at least on my F14 boxk, a Dell Precision M65 with an nVidia Quadro FX 350M. The OP said upthread: "Firstly, trying to reboot, it shows the F14 blue screen with the acorn thingy in the middle,". Secondly, do make sure that when you get a kernel update you also get the corresponding kmod update for nvidia if you have an nvidia card. Otherwise you will get the blinking cursor in the upper left corner.and will need to reboot with an older kernel that still has a kmod-nvidia installed. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Problems reading files after writing them to DVD
On Thursday, April 14, 2011 09:46:24 AM Burkhard Plache wrote: > I had the same problem (Fedora 14 up-to-date, using Brasero), > and blamed it on my CD/DVD burner. Hmm. I have a client with the same problem; I showed him how to use k3b, which works fine. Doesn't help determine why brasero is doing this, but got him productive again, and he now prefers the k3b way of doing things. But he also likes the KDE version of Shisen-Sho, and so already had enough of KDE installed to make k3b an easy fix. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Problems reading files after writing them to DVD
On Thursday, April 14, 2011 11:24:18 AM Tom Horsley wrote: > On Thu, 14 Apr 2011 11:12:14 -0400 Lamar Owen wrote: > > I have a client with the same problem; I showed him how to use k3b, which > > works fine. > And if you want to avoid installing lots of KDE stuff, you could just > try figuring out how to use growisofs from the command line I anticipated that reply when I wrote: "...so already had enough of KDE installed to make k3b an easy fix." Or so I thought. :-) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Guidelines for a noob
On Wednesday, April 13, 2011 03:22:20 PM Aradenatorix Veckhom Vacelaevus wrote:
> Yesterday was boring to wait hours for the needed upgrade and for install
> few packages, perhaps a repository nearer will make this easier.
There are a couple of yum plugins that can help you.
The first, fastest-mirror, will help chose a mirror that is likely the fewest
hops away from you.
The second is yum-presto. With presto enabled, yum becomes able to work with
delta rpms; this means whole packages don't have to be downloaded, just delta
packages, which are typically much smaller. The debian apt program doesn't yet
have this feature.
I much prefer yum, even after using apt for a number of years professionally,
since yum allows a few things things apt does not do ('list' being one of the
more useful).
So, 'yum install yum-presto yum-plugin-fastestmirror' and have fun.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Cannot do KDE Graphic login
On Thursday, April 14, 2011 09:21:03 PM Chris Smart wrote: > It will show [the acron thingy], if they pass a vga option though.. Which option is that? Would be cool to get the real splash screen on boot instead of the text bars. > In fact, one should install akmod, instead of kmod, so that it's > automatically built on boot up and that issue goes away. That never seemed to work correctly here, but admittedly it's been a while since I last tried. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora weather station software? -
On Tuesday, April 19, 2011 01:23:21 PM Bob Goodwin wrote: > Has anyone been able to interface F-14 with a weather station > such as the Oregon Scientific stuff, e.g. the WMR100CA? The excellent Weather Display software is available in a Linux version; www.weather-display.com It's not open source, but it is available for no cost. We're doing this with Davis Instrument stations, not Oregon Scientific, however. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Best FOSS alternative for skype?
On Wednesday, May 11, 2011 07:49:12 AM Alan Cox wrote: > It's not really down to "FOSS alternatives". There are *standards* for > voice over IP. And thanks to NAT-hatred in the standards process, most of those require finagling firewall forwarding fritters..er... rules; H.323 for instance seems to be designed from the ground up specifically to break NAT, and requires some major work at the NAT box to make work properly. SIP and others as well. So supporting VoIP from behind a typical residential NAT box isn't as straightforward as it could be; behind a Cisco or a well-configured Linux NAT box it's not hard. Skype's big selling point is that it works just fine through NAT, even if the NAT is on both ends (NAT444), or on both ends and in the middle (NAT, CGN, etc)and no special port-forwards or other applications-level gatewaying or any of those other tricks the *standard* VoIP protocols seem to require for no good reasonother than to break NAT :-) Sorry, pet peeve there. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Best FOSS alternative for skype?
On Wednesday, May 11, 2011 01:03:56 PM Joe Zeff wrote: > On 05/11/2011 08:32 AM, James McKenzie wrote: > > There iS No Such Thing As A Free Lunch (TSNTAAFL). > > And that is Yet Another Way to mangle a perfectly good acronym: There > *Ain't* No Such Thing As A Free Lunch (TANSTAAFL). Bob Heinlein knew > what he was doing; second-guessing him just messes things up. And as much as I enjoy reading Heinlein and Niven, the term predates them both. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Protected WLAN
On Tuesday, May 17, 2011 11:36:50 PM James McKenzie wrote: > I'll try to make this simple for JD. > 1. Hidden SSID. Standard practice. [snip] > 7. Changing the channel. Standard practice and it prevents interference. 8. Turn off the router and the connection when (if) you're not using it. My home connection gets relatively little use; it stays off unless I or my wife are actively online, which varies as to time and duration, but rarely if ever is the connection up for longer than four hours per day. The casual 'connection sharer' won't want to piggyback an 'unreliable' connection. 9. Change the passphrase frequently, using a wired connection to do it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Protected WLAN
On Tuesday, May 17, 2011 02:10:21 PM Tim wrote: > Password length and wierdness increases security. You're less likely > to be hacked by lucky guesses if you don't have plain words in there. > Certainly don't use real names, phone numbers, birthdates, or anything > else that's easy for someone else to find out about you. And don't think that 1337 spelling will help your security. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Protected WLAN
On Tuesday, May 17, 2011 02:35:09 PM Michael Cronenworth wrote: > SSID hiding is *not* secure. It is *not* a deterrent. Security through > obscurity is *not* security. SSID hiding isn't about security. It's about being able to show that someone who hacked into your network intended to do so, it didn't just pop up on their screen as an open access point that they accidentally used. 'goes to intent' that is. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: bios update
On Wednesday, May 18, 2011 11:24:42 PM Doron wrote: > On 05/18/2011 04:55 PM, Sebastian wrote: > > I have a single boot FC14 system on a Dell precision M6500 precision > > notebook and wish to update the BIOS. > https://www.redhat.com/archives/rhl-list/2009-December/msg01603.html I have a Precision M65 (not M6500, the older M65, essentially a souped-up Lattitude D820); using the Dell repository (much of which is already in Fedora 14, except for the BIOS's themselves) the BIOS update was painless, from Fedora. Be sure to wait through the reflashing, and the memory size changed screens, took mine almost 90 seconds on the reboot after the reflash. And be sure to either be docked or on AC power. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Protected WLAN
On Thursday, May 19, 2011 02:45:38 PM Genes MailLists wrote: > Still a bad idea - some things may, for anything that violates the > 802.11 standards - such as non-broadcast of SSID, choose not to connect > to your router. That means some of your client devices may no longer > work ... That's fine. There's only two devices I need to use my AP, and both deal just fine with 'hidden' AP's. There are other things that violate the 'standards' too that many do anyway Some folks' use cases will find this 'breakage' to be a feature. > This is especially true if there are multiple wifi access points on > same SSID (standard practice for roaming in your big office/house case). > Hiding the SSID will break roaming completely. Not a problem here. Rural area. > So, turning off SSID broadcast is really not a good suggestion. It depends on what you want to do. Hammers are great for driving nails, but that doesn't mean that's the only thing they're good for. I've repurposed a lot of networking equipment for doing things for which it was never intended. :-) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Yum in 'diff' mode (was:Re: Fedora14 is filling up my HDD without a reason)
On Friday, May 13, 2011 09:01:57 AM Joel Rees wrote: > If I have, say, 90M of updated packages, are you saying that having > the old packages in my cache somehow saves bandwidth? Has yum been > upgraded to run in diff mode, then? That would be good news, indeed, > although I haven't seen such evidence in the download sizes. If you want download size reduction as you mention above using a 'diff' mode, try out the presto plugin. Do a: yum install yum-presto and see what I mean. Doesn't help with the metadata, though. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: bios update
On Saturday, May 21, 2011 10:25:30 PM Matt Domsch wrote: > http://linux.dell.com/wiki/index.php/Repository/firmware > > describes how to do this for many (but not all) Dell systems. The > firmware repository on linux.dell.com carries firmware payloads for > >300 different system types. firmware-addon-dell and firmware-tools > packages are included in Fedora and EPEL, so you only need the > firmware payload RPM from the firmware repository then. I've done this with my Precision M65; thanks much for all the hard work, Matt. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Happy birthday Fedora....
On Friday, November 12, 2010 01:23:34 pm Zoltan Hoppar wrote: > In a little delay, but currently 7 years before on 6th of november > Fedora Core 1 has been released. So happy 7th birthday Fedora! Reaching way back in the sands of time... that would be Severn years ago, then? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Convert ext4 lvm to normal ext4 partition
On Friday, November 12, 2010 01:34:09 pm Michael Miles wrote: > Agreed, I am just really surprised that Fedora would adopt this method > of storage as it slows down the drive by a huge margin. > That reason alone would say to me' No, don't want this" I'm curious as to what sort of performance issue you might be seeing, as I've done some benchmarks comparing LVM to raw disk before, and LVM is competetive in terms of performance in all the benchmarks I've run (I primarily use bonnie++, which is in Fedora, for this). LVM certainly gives you lots of flexibility afterwards, however, that a straight partition won't have. And that brings up your original question. How can you resize /boot? Now, it is possible to resize /boot using the Ext4 resizer, the LVM tools (specifically: lvresize, pvresize, pvmove, and friends) and very careful use of fdisk, without the loss of data, as long as you have over 50% free space on the disk. However, it is quite a bit easier to backup your data, reformat, and restore. And it is likely to be faster; the only advantage to the LVM method is that you can do it with the system on-line. The LVM method would require two pvmoves. To see part of the details of what this would look like, see: http://fedorasolved.org/Members/zcat/shrink-lvm-for-new-partition Especially if you're not extremely familiar with the operation of LVM in this scenario. I have done similar, where I migrated the / filesystem from a single disk to a RAID6 set without data loss and while the system was live, but it required a lot of thought, careful planning, and lots of reading beforehand to make sure I wasn't missing something obvious. You could use a similar procedure to convert your disk to not using LVM (short version: reduce the LVM size, make a new partition large enough to contain all the data, clone the filesystem to the new partition, blow away LVM, make a new swap partition, resize the main data partition with gparted, all from a LiveCD of course), but, there again, backup/reformat/restore is probably quicker, and it is the only option if you have less than 50% free. It will be nice when gparted and similar tools get full LVM support; and, for all I know, some commercial tool out there has it already. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Kudos (for a change) for some nice features.
I'm currently using (on my second F14 box) what I consider to be the nicest new feature of preupgrade: vnc remote install preloading. Perfect for semi-unattended upgrades. My initial impressions of F14 on my laptop, installed as a fresh install with a separate /home that was left from the F13 install (and prior): 1.) Lots of work have obviously gone into this release, and updates are coming along to take care of some of the niggles (like the pyxf86config one that causes nvidia issues); 2.) Faster responding than F13; 3.) The laughlin background is cool, very cool! Of course, I'm a KDE user, so some of my impressions are KDE upstream ones: 1.) Strigi is nice, but the initial indexing is a resource drain; 2.) My initial login into KDE 4.5 was unsuccessful; I moved my retained .kde tree out of the way, and could get logged in, then moved my stuff across piecemeal; 3.) Am I blind, or is there no document listing what all the files in .kde do? (My .kde is old, really old, with stuff left I'm sure from KDE 1 back in my Mandrake 5.3 and RedHatLinux 6.0 days that I could probably get rid of) 4.) Still trying to get Desktop effects to work with the RPMfusion kmod-nvidia and the Oxygen theme. but that's more an nvidia thing, not a Fedora thing. Hardware is a Dell Precision M65 laptop with Quadro FX 350 M w/ 256MB video, Core 2 Duo T7400 processor, 4GB RAM, and running the 64-bit version. Nice experience thus far. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Convert ext4 lvm to normal ext4 partition
On Friday, November 12, 2010 07:12:23 pm Peter Larsen wrote: > So create a partition, test it without lvm. Then add it as a pv, and do > the same test on the lvm on the same implementation. I'm running a benchmark now, using two 48GB partitions on a 100+GB drive; one LVM+ext3, one straight ext3. Since the machine in question has 10GB of RAM, it will take a while, since bonnie++ defaults to using twice the amount of RAM for the test, to remove the RAM cache from being a factor. Looking at this seeker program, I think comparing the small /boot partition to the larger / partition isn't really valid, since the seeks are going to be over a larger surface on / than on /boot. I'll post when it's done, or tomorrow morning if it's not done tonight. System is running CentOS 5.5 x86_64, but I also have a 32 bit F14 system in the midst of updating that I can try it out on, too. Once the ext3 benchmarks are in, I'm going to migrate to ext4 on both the straight 48GB partition and the 48GB LVM logical volume; I'm going to time the migrations, and rerun bonnie++ on the resulting ext4 filesystems. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Convert ext4 lvm to normal ext4 partition
On Friday, November 12, 2010 07:12:23 pm Peter Larsen wrote:
> So create a partition, test it without lvm. Then add it as a pv, and do
> the same test on the lvm on the same implementation.
Ok, the first set of two results are in. And I am surprised by one data point
in one of them. Surprised enough that I ran the benchmarks three times, and
got substantially the same results all three times. I also show hdparm -t
output below that confirms that hdparm -t is at best a 'best case' figure,
especially when used with a heavily cached controller. And last, but not
least, is Seeker output that should really shed some light on random access
benchmarks on different sized partitions.
System is running CentOS 5.5 x86_64, two 2.8GHz Opterons, 10GB RAM. Disk array
connected by 4Gb/s fibre-channel, using a QLogic QLE2460 PCI-e 4x HBA.
Individual drives on the array are 500GB 7200RPM FCAL drives. LUN was (as far
as I can tell) properly stripe-aligned prior to test. RAID group containing the
LUN is 16 drives, in a RAID6 configuration; the other LUNs in the RAID group
had little to no traffic during the testing. Array controller has substantial
read and write caches (multiple GB) and powerful CPU's. In other words, not
your typical home system. But it's what I had on-hand and available to test in
a rapid manner.
Using bonnie++ levels the playing field substantially, and wrings out what the
disk performance actually is; and I do know that the choice of 7200RPM drives
isn't the fastest; that's not the point here. The point is comparing the
performance of two ext3 filesystems (may possibly be doing the ext4 tests later
today, but honestly it shouldn't matter), where one is on a raw partition and
the other is in an LVM logical volume. Given the results, I should probably
swap the partitions, making sdb1 the LVM and sdb2 the raw ext3 (currently it's
the other way, with sdb1 the raw and sdb2 the LVM), and rerun the tests to make
sure I'm not running afoul of /dev/sdb1 not being stripe-aligned but /dev/sdb2
being stripe-aligned.
bonnie++ command line:
bonnie++ -d /opt/${filesystem}/bonnie -u nobody:nobody
No special options; nobody:nobody owns /opt/${filesystem}/bonnie.
${filesystem} is 50g-straight for the raw partition, 50g-lvm for the logical
volume.
The results:
+++
Raw Ext3:
Size: 19496M
SeqOutput:
PerChr: 48445K/sec
Block: 52836K/sec
Rewrite: 19134K/sec
SeqInput:
PerChr: 51529K/sec
Block: 26327K/sec (<--- this surprised me; one would think it would be larger,
but might be related to stripe size alignment, but I thought I had compensated
for that)
RandomSeeks: 576.5 per sec.
SeqCreate:
Files: 16
Creates/second: 10544
RandomCreate:
Creates/second: 11512
Time output: real 50m16.811s, user 6m49.498s, sys 5m45.078s
+++
For the LVM filesystem:
Size: 19496M
SeqOutput:
PerChr: 51841K/sec
Block: 54266K/sec
Rewrite: 26642K/sec
SeqInput:
PerChr: 54674K/sec
Block: 69696K/sec (<--- this looks better and more normal)
RandomSeeks: 757.9 per sec.
SeqCreate:
Files: 16
Creates/second: 10540
RandomCreate:
Creates/second: 11127
Time output: real 36m21.393s, user 6m47.328s, sys 6m17.813s
+++
Yeah, that means on this box with this array, LVM is somewhat faster than the
raw partition ext3, especially for sequential block reads. That doesn't seem
to make sense; the Sequential and Random Create results are more in line with
what I expected, with a small performance degradation on LVM.
Using the other common tools:
First, hdparm -t. Note that with this much RAM in the array controller, this
isn't a valid test, as the results below show very clearly (it also shows just
how fast the machine can pull data down 4G/s fibrechannel!).
+++
[r...@migration ~]# hdparm -t /dev/sdb1
/dev/sdb1:
Timing buffered disk reads: 298 MB in 3.00 seconds = 99.32 MB/sec
[r...@migration ~]# hdparm -t /dev/sdb2
/dev/sdb2:
Timing buffered disk reads: 386 MB in 3.01 seconds = 128.07 MB/sec
[r...@migration ~]# hdparm -t /dev/sdb1
/dev/sdb1:
Timing buffered disk reads: 552 MB in 3.01 seconds = 183.67 MB/sec
[r...@migration ~]# hdparm -t /dev/sdb2
/dev/sdb2:
Timing buffered disk reads: 562 MB in 3.01 seconds = 186.86 MB/sec
[r...@migration ~]# hdparm -t /dev/sdb1
/dev/sdb1:
Timing buffered disk reads: 704 MB in 3.01 seconds = 233.85 MB/sec
[r...@migration ~]# hdparm -t /dev/sdb2
/dev/sdb2:
Timing buffered disk reads: 614 MB in 3.01 seconds = 204.16 MB/sec
[r...@migration ~]#
+++
Now, the Seeker results (I test the raw disk first, then /dev/sdb1 and sdb2 in
turn, then twice on the LVM logical volume's device node, and then once on the
much smaller /dev/sdb3):
+++
[r...@migration ~]# ./seeker /dev/sdb
Seeker v2.0, 2007-01-15, http://www.linuxinsight.com/how_fast_is_your_disk.html
Benchm
Re: Convert ext4 lvm to normal ext4 partition
On Saturday, November 13, 2010 01:08:12 pm Michael Miles wrote: > Lamar Owen wrote: > > [r...@migration ~]# ./seeker /dev/sdb3 > > Seeker v2.0, 2007-01-15, > > http://www.linuxinsight.com/how_fast_is_your_disk.html > > Benchmarking /dev/sdb3 [7012MB], wait 30 > > seconds.. > > Results: 21459 seeks/second, 0.05 ms random access time > > [r...@migration ~]# > I have run all these tests and I have to say that Seeker is not a valid > test to show speeds of these disks > I ran hdparm and it shows the lvm to be a bit slower but not a lot. > With Seeker it shows a large difference because of the area on the disk > being tested > That's quite a difference on sdb3 by the way. It's amazing how much > speed a filesystem takes away from a disk The Seeker and hdparm -t results have nothing to do with the filesystem being there or not; if I run seeker on /dev/sdb or /dev/sdb1 or /dev/sdb3 I'm running it against the device; the presence or absence of a filesystem makes no difference. With LVM running it against the raw logical volume device (in my examples, the volume group was benchtest, and the logical volume was 50g, making the device node /dev/benchtest/50g) does the same thing, and doesn't have anything to do with the filesystem. The bonnie++ results do, however, reflect the filesystem performance, since bonnie++ is writing and reading files on the filesystem instead of raw device. What does make a difference is the size of the device being tested, in terms of cylinders or blocks. If the partition is 1000 cylinders, a true random seek will seek to cylinders between the start and the start+1000; if it's a 100 cylinder partition, it will seek between the start and the start+100, one-tenth of the distance, and thus it should produce an average seek that is quite a bit smaller than the partition with 1000 cylinders. Thanks to modern ZBR (zone bit recording) drives, ten times the number of blocks does not necessarily translate to ten times the number of cylinders (for more information about ZBR and what that means for disks, see http://en.wikipedia.org/wiki/ZBR for details. In any case, I've set up LVM on /dev/sdb3 (/dev/bench2/7g is the logical volume's device node), and here's some more seeker and hdparm -t "results" for your enjoyment: +++ Seeker v2.0, 2007-01-15, http://www.linuxinsight.com/how_fast_is_your_disk.html Benchmarking /dev/sdb3 [7012MB], wait 30 seconds. Results: 23546 seeks/second, 0.04 ms random access time [r...@migration ~]# ./seeker /dev/bench2/7g Seeker v2.0, 2007-01-15, http://www.linuxinsight.com/how_fast_is_your_disk.html Benchmarking /dev/bench2/7g [7012MB], wait 30 seconds.. Results: 37116 seeks/second, 0.03 ms random access time [r...@migration ~]# hdparm -t /dev/bench2/7g /dev/bench2/7g: Timing buffered disk reads: 852 MB in 3.00 seconds = 283.65 MB/sec [r...@migration ~]# hdparm -t /dev/sdb3 /dev/sdb3: Timing buffered disk reads: 774 MB in 3.01 seconds = 257.53 MB/sec [r...@migration ~]# +++ Of course, the fact that that entire partition can fit in the kernel's cache makes a difference here in the Seeker results; the hdparm -t (just a big sequential read, that's all) just shows that the array is very good at caching and doing readahead. So I tend to trust bonnie++'s results more, since it takes pains to take the cache out of the equation. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Convert ext4 lvm to normal ext4 partition
On Saturday, November 13, 2010 08:59:48 pm Dean S. Messing wrote: > Regarding your disk speed tests with hdparm, > you may want to look at the "--direct" switch. Oh, I like those numbers: [r...@migration ~]# hdparm -t --direct /dev/sdb3 /dev/sdb3: Timing O_DIRECT disk reads: 2054 MB in 3.02 seconds = 679.13 MB/sec [r...@migration ~]# hdparm -t --direct /dev/bench2/7g /dev/bench2/7g: Timing O_DIRECT disk reads: 2052 MB in 3.00 seconds = 683.36 MB/sec [r...@migration ~]# There's hardware cache (about 4GB) involved in the array controller that I'm just not able to bypass. Although I'm going to admit that those numbers seem fishy... And I do know why they look fishy. There's another cache involved. But I can't reproduce with /dev/sda on that box, and /dev/sda is on the same array, it's on the same HBA, and, while it's on a different LUN, it's on the same RAID group on the array: [r...@migration ~]# hdparm -t --direct /dev/sda /dev/sda: Timing O_DIRECT disk reads: 994 MB in 3.00 seconds = 331.18 MB/sec [r...@migration ~]# Which is more in line with 4G/s FC performance. I'll have to dig into that anomaly. Now, on my development F14 box hooked up to the same array, just a different LUN, and a 32-bit machine (dual Xeon 2.8, 4GB RAM), and using a 2G/s FC HBA (which will impact, and probably bottleneck, performance): [r...@www ~]# hdparm -t --direct /dev/sdw /dev/sdw: Timing O_DIRECT disk reads: 534 MB in 3.01 seconds = 177.46 MB/sec [r...@www ~]# On another CentOS 5 box (dual 3.4GHz Xeon's, 2GB RAM, x86_64), hooked up to a different array with 4G FC: [r...@backup670 ~]# hdparm -t --direct /dev/sdad /dev/sdad: Timing O_DIRECT disk reads: 864 MB in 3.00 seconds = 287.87 MB/sec [r...@backup670 ~]# (yeah, /dev/sdad, that's not a typo) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Yum - Different OS version and Arch
On Sunday, November 14, 2010 06:29:21 am Sawrub wrote: > On 11/14/2010 04:07 PM, Michael Schwendt wrote: > > On Sun, 14 Nov 2010 15:51:44 +0530, Sawrub wrote: > >> all i wanted was to know that why are they included in the > >> results for a different version of OS. > > Because [hopefully] they continue to work and [hopefully] the package > > maintainer has verified that they still work without a rebuild. > > > Or may be the maintainer is no longer interested in re-building. Then they would be in the orphans list, and they would eventually be dropped if a new maintainer didn't step up to the plate. At least that's my reading of the packaging guidelines; Michael is free to correct me, as he's been more closely involved over the years. If a package from, say, Red Hat Linux 5.2 (not RHEL5, but old-school RHL) were to run unmodified directly on F14 (don't know any that do, but 5.2 is the oldest dist I still have running in a production setting (not connected to the Internet!)) then why would a rebuild be needed? Ten years ago I was contracted by a company to build RPM's of PostgreSQL 7 for a number of different distributions. I was pleasantly surprised at how portable (to a degree) packages for different distribution versions were... even packages for a whole different distribution can be made portable, to a degree, as long as package names (for dependencies) are the same, and the versions are fairly close for most required packages. Essentially, I could take pains to make the dependencies as generic as possible, and I could install one distribution's package directly on another. Now, since I was being paid to do this, I did do native builds for all the supported distributions; but for testing it was fun to cross-install packages. And I know of several commercial packages that are portable in this way. VMware Workstation, when it was still distributed as RPM, was like this. CodeWeavers' CrossOver is still distributed in a distribution-independent RPM. The Fluendo DVD player, Media Center, and codec packs are distributed in distribution-independent RPM's. And there are other examples. So, as Michael said, don't read too much into dist tags; they're there only as a hint, not as a hard dependency. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Little niggle with a preupgraded F13->F14 (was:Re: End of life for FC12?)
On Saturday, November 13, 2010 06:40:03 pm Kevin Fenzi wrote: > I almost never have issues on os upgrades anymore. The last 2 machines > here I upgraded from 13->14 just worked. I didn't have to change > anything at all. I had my first issue with such this cycle; F12->F13 on this box went well, but I hit a snag with this one, but it was somewhat my own doing. I had forgotten that I had moodle installed, and, a while back, moodle kept failing to upgrade during yum updates. Since I wasn't actively using it, I didn't file a bug report at the time. I had intended to remove moodle (and all my PlanetCCRMA packages that don't have upgrades yet to F14), but forgot to do so. Made a really good learning opportunity! The moodle issue threw Anaconda for a loop, and generated a fatal error during package install (it looks like a corrupt package during execution). This was about 85% through the upgrade. I should really do a scratch F13 install, install moodle, do the preupgrade, and see if I can duplicate so I can file a proper bugzilla report; I just simply was in a rush. But the tools yum provides were able to fix the issue, but I did have to boot using the F13 kernel, since the initramfs for the F14 kernel wasn't there. One niggle: yum-complete-transaction didn't see any incomplete transactions, but there was one from Anaconda. Like I said, I need to file a complete report. And next time be more diligent. In a nutshell, "package-cleanup --cleandupes" then "yum update", then I removed all but the currently running F13 kernel, and then reinstalled the F14 kernel, and rebooted into the F14 kernel. And the box is running fine. In the old days this would have been a reinstall, but the yum tools have really gotten robust. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: End of life for FC12?
On Saturday, November 13, 2010 06:26:09 pm Patrick Bartek wrote: > I've never demeaned Fedora. There are things I don't like to be sure, but > that can be said of all things. I've been using it since FC3 after trying a > dozen or so other distros before settling on it as my primary desktop OS. So > that says something. And I'm VERY particular. It's just that over the years > Fedora's development model and my needs have diverged. And it's time to move > on. I would recommend you take a look at a RHEL6 rebuild when they become available. RHEL6 (and thus the rebuilds) are based off of essentially F12 with some F13 stuff in there, and you can then have the same setup for five years. Now, when the time does come to upgrade to, say CentOS 7, you will have a much harder time of it. But if you like what you have, and you're used to the Fedora tools and setup, either CentOS 6 or Scientific Linux 6, both in the early stages of building, should fit your bill. SL6 is already available in a 'pre-alpha' form; the pre-alpha meaning that, while the upstream source packages are stable, the process and binaries built may not be. You will still be getting quarterly updates that can be more major than you might think; Red Hat is very good about backporting stuff, but every once in a while it becomes necessary to do a version upgrade of some package, like Firefox for one, that can cause more grief than you might think. But, all in all, my experience running CentOS (2.1, 3, 4, and 5) has been very smooth. The old Red Hat Linux advice was always 'skip the X.0 release, test the X.1 release, use the X.2 release' but then 7 came along (which most everybody called 7.0), 7.3 came along (which to many people, was not as stable as 7.2 had been), 8.0 came along, and then there was 9. The most stable releases of Fedora have always seemed to be the ones right before a new RHEL, and the least stable the ones right after a new RHEL; this hasn't been true in a while, although I'll have to admit that going from F8 to F9 tried my patience; KDE 4 I really didn't need, I was productive in KDE 3.5.10. Enough that I went Kubuntu 8.04 LTS for a while, but after seeing that the grass wasn't any greener (in fact, it was browner!) in Kubuntu-land came back with F11, which seemed nice and solid. And there were quite a few more than the previous three Fedora releases between RHEL5 and RHEL6. And I'm now as productive in KDE 4 as I was in 3.5.10. But it did take a while. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Impossible Internet connection.Strange thing.
On Saturday, November 13, 2010 06:13:57 pm Luis Suzuki wrote: > > I did: > ping 18.7.22.69 and I have got : Network Unreachable. Ok, what is the output of the following two commands: ifconfig ip route > The strange thing is: everything points that the Internet connection should > be OK(the Gnome task bar widget when I point the cursor over it says Auto > eth0 active). If the ifconfig output shows a 169 address, the interface is up but didn't get a reply from the DHCP server in time, or in the right format. > I doubt that I am the only one to have this problem,so this is probably a bug > that came with Fedora 14. Conversely, it has to be something fairly unique to your setup, or there would be hundreds posting about it all over the Internet. You may not be the only one to see the problem, but if a lot of people saw it, there would be mayhem on this list. I'm using my F14 KDE install right now, wirelessly, just fine. With the wired connection I do have to connect 'System Eth0' manually, but when I do it grabs a DHCP address just fine. Haven't troubleshooted the need to manually activate System eth0 yet. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Kernel-PAE no longer 32 bit default?
On Saturday, November 13, 2010 07:51:17 pm Tom Horsley wrote: > I was finally getting around to tweaking my 32 bit fedora 14 > partition when I noticed that I was running kernel, > not kernel-PAE. For what it's worth, my pre-upgraded F14 box pulled in the PAE kernel, but that was an upgrade, not a fresh install. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Streaming audio out to an internet destination
On Saturday, November 27, 2010 10:49:13 pm JD wrote: > I use skype quiet a bit. > What I was interested in doing is this: > While talking to someone on skype, I would > like to be able to stream an audio track to > the same destination that I am speaking with > via skype. Set up things to use JACK; you then can patch, reroute, plug in synths, effects, or whatnot. See http://forum.skype.com/index.php?showtopic=25820 for how some folks are using skype with JACK. JACK frees your audio routing in ways like nothing else. It does have its quirks, though, and it might be overkill for something this simple; it was originally built to be the backend for professional-grade multitrack DAW work (in conjunction with Ardour, in other words). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Final release of RHEL 6
On Thursday, December 02, 2010 09:28:55 am Robert G. (Doc) Savage wrote: > On Thu, 2010-12-02 at 18:33 +0530, Jatin K wrote: > > may be it means Centos 6 will be released soon ... is it ? > If I had to guess when CentOS 6 might be released, I'd say mid- to > late-January 2011. Watch their web site at http://www.centos.org/. Jatin, in addition to following what Doc said in that last paragraph, if you want to see the status of the CentOS development follow the CentOS mailing lists and IRC channels, as that's where most of the planning and discussion is happening. An alternative is the Scientific Linux distribution, which is intended for a different audience than CentOS, but built from the same upstream source RPMS. Disc size and integration look to once again be opportunities. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: the console
On Saturday, December 04, 2010 06:53:20 am xinyou yan wrote: > hello everyone > > I am new to fedora , After i set fedora start in level 3 > The char is so small . How i set /etc/??? to make it more big > > my display mode is 1440*900 > > Is display resolution 's problem ? Or some others ? In /boot/grub/grub.conf (or menu.lst) add 'nomodeset' to the kernel line and see if that helps you upon a reboot. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: printer question
On Friday, December 03, 2010 01:36:57 pm ann kok wrote: > Hi all > > I would like to ask linux can do the networking printer as window > > Share it to office environment One client I set up with Fedora (he's on 13, but the same works otherwise) I set up to share his printers; you need to enable the network ports in the iptables configuration (the 'firewall configuration' application allows this with a simple checkbox next to 'Samba' and 'Samba Client' (the Samba line is a superset of the Samba Client line). Then, in the printer configuration dialog, right click on the printer; there is a checkbox for shared. His wife is running Ubuntu 6.06LTS (for some good business reasons, althought I'm going to upgrade her to CentOS 6 when that's out; she is, uh, kainotophobic, so a long-term supported release is a must for her and if there's going to be change, let's do it once; she can handle it once every five years). Both the Ubuntu 6.06 box and the F13 box are ethernet connected to their DSL router. In any case, he had bought a new Epson RX580 a while back, and had a hard time finding the USB 'B' port (the RX580 has an 'A' port in plain sight, and he wanted a 'USB crossover' cable to use that portthe USB 'B' port is located under the top cover that you raise to change the ink.). So, when I found the B port for him (and showed him where it was in the manual), we plugged it in. His F13 box found the printer, configured the drivers, offered to print a test page, and 'Just Worked' without either of us having to go into the printer configurator. About thirty seconds later the Epson RX580 showed up on his wife's Ubuntu 6.06LTS printing dialogs; a test page from her later and I had two happy campers. This is the way printing is supposed to work. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Reinstall -- Kernel panic
On Friday, December 03, 2010 12:21:58 pm Robert Moskowitz wrote: > Kernel panic - not syncing: VFS: Unalble to mount root fs on > unknown-block(0,0) > What is the problem and how do I fix it? Will a 'simple' rebuild of the > partition table by removing all the partitions then reconfiging them as > I want will work, or will this take a bigger hammer? Is there a valid initrd with the right modules for your hardware in /boot? Reboot, edit the command line, and add 'rdshell' to the kernel line. This will drop you into a dracut shell from the initramfs, assuming it exists. You can then see what's going on in terms of the init ramdisk. If this doesn't give you a dracut shell, then my guess is that your ks.cfg or something else didn't make an initrd using dracut. A saw this exact error after a failed preupgrade from F13; the failure was caused by a corrupted moodle, which didn't error until preupgrade had already installed 90% of the packages, but hadn't done any cleanup. The F13 kernels were still there, but the F14 kernel didn't get an initramfs built, and gave the same error you list above. A yum reinstall of the kernel fixed it, and then I had fun getting rid of the duplicate packages but we're good now. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Samsung Laser Printers - propietary Page Description Language? (ML-1665)
On Sunday, December 05, 2010 10:22:50 am Fernando Cassia wrote: > Samsung provides propietary, binary-only drivers for Linux at this location > http://downloadcenter.samsung.com/content/DR/201001/20100121132724343/UnifiedLinuxDriver_0.86.tar.gz > > However, they only mention Ubuntu, no word about Fedora. I performed an install of the Samsung driver stack for an ML-2525W just the other day on F13; worked fine. Yeah, it's a pain that it's proprietary, but it seems to work ok on Ubuntu and Fedora. Interestingly enough it installed just as easily on F13 as it did on Ubuntu 6.06. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: F14: can't get java running (problem solved)
On Monday, December 06, 2010 04:46:01 pm Tony Camuso wrote: > Setting SELinux to permissive fixed the problem. That's a workaround, not a fix. A fix would have the right file contexts labeled. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: 5 Beginner questions regarding Fedora 14
On Wednesday, December 08, 2010 07:21:02 am Alan Cox wrote: > https://www.eff.org/deeplinks/2010/06/encrypt-web-https-everywhere-firefox-extension > may be what he is thinking of ? I'm using that one, and it works rather well on the sites I frequent. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: VirtualBox on Fedora 14
On Wednesday, December 08, 2010 02:30:19 pm S Mathias wrote: > !! -> so the "/usr/src/kernels/2.6.35.9-64.fc14.i686.PAE" is MISSING! > > Where can i download it? yum install kernel-PAE-devel -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Package managers
On Thursday, December 16, 2010 11:11:03 am Temlakos wrote: > This isn't totally academic. I also administer a Web server, and I find > that a command-line interface is the only way that I can do any kind of > installation or upgrade. (I have to connect using secure-shell.) Might > as well learn how to do it in that context... Both kpackagekit and GNOME PackageKit run well through an ssh-tunneled X session or through NX. Some of the nicer GUI utilities for system administration on F14 run well through 'ssh -Y' as well; virtually the whole 'system-config-*' collection, as well as the palimpsest Disk Utility. The palimpsest utility, in particular, does a whole slew of things that takes multipe CLI utilities to do, and gives you lots of great information in a single window. While I use CLI (and I've used it for more than 20 years on different Unix and unixlike system) for many things, especially on slow connections, there are a few cases where the GUI is easier, as long as you have a relatively fast connection. SELinux configuration, for instance, is much much easier through the GUI, as all the options are right there and listed. Unless you have all of them memorized :-) -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora14: Strange and intermittent very slow disks on server
On Friday, December 17, 2010 06:14:31 pm Terry Barnaby wrote: > The two main RAID1 disks are WD10EARS (Green). I have seen reported some > issues with the performance of these but in my case they appear to work > fine when the system is running ok. [snip] > Anyone seen this sort of behaviour before ? > Any ideas one where to look ? Yes, I have. Use a different drive. Use iostat -x 1 to trace which disk in the RAID1 is causing problems; you'll likely find that the WD10EARS are throwing long awaits. Rumor is that this is by design; WD has enterprise 'RAID ready' drives and don't rate the lower priced drives for RAID. I have a WD15EADS that does this. At least the EARS version can possibly be put in a 'TLER' mode that allows RAID use. In my case, I had the WD15EADS drive as one half of a RAID1, with the other half being a Seagate 1.5TB drive of the same LBA. Every once in a while, performance would absolutely go to pot, and stay that way for minutes at a time (load averages >10 on a single core system). Using iostat -x 1 I was able to isolate the issue to that particular drive (I swapped controller channels, swapped cables, swapped out the power supply, swapped to a different controller chip on the motherboard, swapped motherboards, and the issue was always on this drive). When I replaced the WD15EADS with another Seagate 1.5TB, performance came back to normal. I'm using the WD15EADS in a single mode, now, with much lighter usage, and realizing that performance is not its strong suite. Also, the EARS version might use 4K sectors, exposing 512 byte sectors in an 'emulation' mode; properly aligning partitions to 4K boundaries solves that. Google 'WD EARS TLER' and get the whole story. You'll also want to disable the 'green' mode, as that will also negatively impact performance. There are tools out there to do that. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora14: Strange and intermittent very slow disks on server
On Saturday, December 18, 2010 03:08:45 am Terry Barnaby wrote: > It is strange, however, how the system can run perfectly fine with good > fast disk IO for a while and then go into this slow mode. In the slow > mode a command can take 30seconds or more to run on an unloaded system. > It smacks of some Linux kernel SATA driver/RAID1 versus WD EARS drive > interaction to me. It's definitely something; the TLER discussions I've seen are just partial explanations at best. > However, I think I will change the drives. I was hoping to try some WD10EADS > ones I have, but after your issues I will look at the RE series or > another make ... The RE series is WD's 'RAID Enterprise' or 'RAID Enabled' (depending on how you look at it) drives, and cost more. They should work fine in RAID. The lower cost WD drives have been giving problems in RAID, and not just on Linux. WD even says they are not designed for RAID. Please see the responses at: http://community.wdc.com/t5/Other-Internal-Drives/1-TB-WD10EARS-desynch-issues-in-RAID/m-p/11559 Also see: http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1397 That last link is to WD's FAQ; it explains the root cause of the issue, that of deep cycle recovery (saying point blank that the drive could take *2* *minutes* to recover *one* *sector* in error). So basically any time the drive hits an error, things slow to a crawl as the iowaits pile up. This is the info iostat -x 1 will give you; watch the await time (given in milliseconds); I saw awaits of up to 20,000 ms while trying to use my WD15EADS drive in RAID1. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Damn these Windows Virus Testers - Online
On Saturday, December 18, 2010 02:21:37 pm Jim wrote: > It does not make any difference what Website your on it's just pops up > and starts At least it doesn't infect your PC with the 'fake Windows AntiVirus' virus. I've seen these a time or two, from seemingly random websites; one of them was a technical blog about the merits of JFS versus XFS. I have a screenshot of that one. Yesterday I found another. In my case, I hit the X for that tab, and then hit ok (since the systempack107_2089.exe that that downloaded won't autorun on Linux; and you really don't want to set up autorun through wine...:-)). And it went away. Got the .exe though for future analysis. That same advice on Windows produces a tenacious infection of a rogue antivirus program that is in reality a virus itself that tries to scam you out of money for buying a subscription. It's just a matter of time before the rogue antivirus writers figure out how to make this work with Linux.unfortunately. Time for sandboxing of Firefox and other apps that can run that mess. And while such a virus can't overwrite system files if you're browsing as a normal user, it certainly *can* infect your own files, such as .bashrc for one, which would produce essentially the same effect as on Windows (and with the default F14 setup disallowing root logins, you need to make a second 'rescue' user to remove such nasties without reverting to a text console and root). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Damn these Windows Virus Testers - Online
On Saturday, December 18, 2010 02:21:37 pm Jim wrote: > It does not make any difference what Website your on it's just pops up > and starts More information about these 'surf-by' infection agents: http://blog.webroot.com/2009/11/25/fakealerts-building-a-better-mousetrap/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Error - Running Acroread
On Monday, January 03, 2011 06:38:08 pm Jim wrote: > F14 , fresh install > > $ acroread > /opt/Adobe/Reader9/Reader/intellinux/bin/acroread: error while loading > shared > libraries: libcrypto.so.0.9.8: cannot enable executable stack as > shared object > requires: Permission denied Please see https://bugzilla.redhat.com/show_bug.cgi?id=533987#c1 for more information. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: ipv6 question
On Tuesday, January 04, 2011 12:52:42 pm Marko Vojinovic wrote: > You have the exact same situation if you use IPv4 and NAT. The outside system > has the IPv4 of your router, and can use that IP to scan for any open port on > your inside machine. Namely, once your NAT-ed machine initiates the > connection > to the outside machine, NAT will happily accept any incoming connection from > that outside machine, typically on all ports, translate to your local IP and > forward back inside (at least in the default configuration). That's how NAT > works, it translates the addresses from non-routable to routable and back, > trying to keep the communication as open as possible, both ways. Didn't you > know this? This is incorrect for many implementations of NAT. I refer in particular to Cisco IOS NAT, IOS 12.4(23) mainline on a 7206/NPE-G1, using NAT pools and overloading. Incoming packets addressed to the outside interface that don't match the flows that the router knows about get dropped. So if I connect to your website from inside my network, you can't randomly initiate a connection back to my box (that's what the overloading, allowing multiple internal IP's onto a single 'inside global' (using Cisco terms) IP, prevents). The only conduit through the NAT is using the specific source-address:source-port/destination-address:destination-port pair that the translation sets up. If I have, say, 100 computers inside my network, and have 32 global addresses, and overload the dynamic translations onto three global addresses, you have no way of getting to the inside addresses except through the translations set up during the outgoing flow initiation. You have to jump through hoops to get things like H.323 to work (Cisco at least has support for connection tracking so the packets, mostly UDP, can get back to where they need to go). No ACL's necessary to create this behavior, at least with Cisco IOS NAT. The same (or similar) is true for Smoothwall, at least, naming one firewall appliance/distribution that I use and that uses the Linux kernel. Tested that one; you have to configure zone bridging and port forwarding to get the behavior you mention. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: ipv6 question
On Wednesday, January 05, 2011 07:51:19 pm Michael H. Warfield wrote: > On Wed, 2011-01-05 at 17:26 -0500, Lamar Owen wrote: > > I refer in particular to Cisco IOS NAT, IOS 12.4(23) mainline on a > > 7206/NPE-G1, using NAT pools and overloading. Incoming packets > > addressed to the outside interface that don't match the flows that the > > router knows about get dropped. > What you say is true but is equally true if you retain the stateful > firewall at the heart of the NAT engine and eliminate the NAT. The Cisco NAT is by default stateless; you have to specifically configure stateful NAT (on platforms that support it, and if your IOS feature set has that feature), but that mostly just gets you HSRP resilience for NAT; the packet translation itself is stateless (and hardware accelerated on some platforms, especially those with PXF which can do the IP header rewrites at wire speed). 'Stateful Firewalling' in Cisco-land is 'packet inspection' or even deep packet inspection, and is an additional feature set (and an additional cost for the IOS image), but images which cannot do stateful inspection can do NAT overload. Stateful firewalling in that context is also referred to as CBAC (Context-based Access Control). This inspection is a control-plane activity that writes ACLs, whereas NAT happens in the data (forwarding) plane, as a separate step from the ACL application (also in the forwarding plane). > The NAT > is not what's giving you this protection. It's the stateful nature of > THAT particular NAT which is the same as as a linear stateful firewall. > No difference. And other forms of NAT do not enjoy this. [snip valid NAT config that is set up to not provide that benefit] > NAT, in and of itself, is not providing the security. It's the state > engine at the heart of most (but not all) NAT devices and all stateful > firewalls. It's not the NAT, it's the firewall. NAT in cisco IOS is stateless unless certain features are turned on. The forwarding plane as part of the switching process performs the header translation (if one exists) and then routes; if there is no destination for the route it's blackholed, or hairpinned (depending on configuration). That is, given the NAT translation table snippet: tcp 10.10.10.10:52650 192.168.1.118:52650 74.125.67.99:8074.125.67.99:80 tcp 10.10.10.10:1769 192.168.1.166:1769 74.125.67.99:8074.125.67.99:80 And assuming no other translations are in the table, 74.125.67.99 could scan 10.10.10.10 all it wants; only packets to ports 52650 and 1769 will get statelessly translated (bidirectionally; the return packets also get translated for a tcp translation) to the respective addresses on the inside, and only to those ports; all other packets to that 10.10.10.10 address will be left untranslated and routed to the interface with 10.10.10.10 on its subnet. That could be a Null device for blackholing purposes, or it could be a honeynet, or it could even be a real host. Please see the Cisco document entitled 'NAT Order of Operation' (the direct link is long, and can change at seemingly random times for some reason) for more detail and pointers to how NAT works in IOS. The above example table is part of the following example IOS NAT config (both derived from what I have here, with addresses changed): ip nat pool metro-e 10.10.10.1 10.10.10.13 netmask 255.255.255.240 ip nat inside source list 1 pool metro-e mapping-id 10 overload This is not firewalling (nothing is blocked by the NAT itself; but only what's in the table gets translated), and is not stateful. The addresses that get added to the table have an associated access-list, but that's just a convenient way to list addresses; a route-map is also a possible source of addresses for the NAT operation (ip nat inside source route-map . ). And I realize that I'm describing what some call port address translation (PAT) or even as NAT-PT (network address translation - port translation), but it's all configured in the common NAT engine. NAT is a far simpler operation than stateful firewalling; packet inspection to overcome some of the broken protocols that are NAT-hostile brings in the stateful firewall engine that makes things like CBAC possible. NAT only has to deal with address and port number translation in the IP header, and, as mentioned, can be done in pattern matching hardware like Cisco's PXF. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: ipv6 question
On Thursday, January 06, 2011 01:30:45 pm Lamar Owen wrote: > That is, given the NAT translation table snippet: > > tcp 10.10.10.10:52650 192.168.1.118:52650 74.125.67.99:8074.125.67.99:80 > tcp 10.10.10.10:1769 192.168.1.166:1769 74.125.67.99:8074.125.67.99:80 > > And assuming no other translations are in the table, 74.125.67.99 could scan > 10.10.10.10 all it wants; only packets to ports 52650 and 1769 will get > statelessly translated (bidirectionally; the return packets also get > translated for a tcp translation) to the respective addresses on the inside, > and only to those ports; all other packets to that 10.10.10.10 address will > be left untranslated and routed to the interface with 10.10.10.10 on its > subnet. More to the point, using ssh to get to a machine outside my network: lo...@localhost:~$ ssh r...@outside.somewhere.com Last login: Wed Jan 5 13:46:24 2011 from 10.10.10.10 [r...@outside ~]# nmap 10.10.10.10 Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2011-01-06 13:42 EST Note: Host seems down. If it is really up, but blocking our ping probes, try -P0 Nmap run completed -- 1 IP address (0 hosts up) scanned in 1.069 seconds [r...@outside ~]# nmap -P0 -p 0- 10.10.10.10 Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2011-01-06 13:42 EST All 65536 scanned ports on dyn.somewhere-else.net (10.10.10.10) are: filtered Nmap run completed -- 1 IP address (1 host up) scanned in 1376.328 seconds [r...@outside ~]# The nat translation table entry on the NAT box at the time: tcp 10.10.10.10:46354 192.168.1.118:46354 10.20.20.20:22 10.20.20.20:22 Where 10.10.10.10 is the particular IP in the global NAT pool, 192.168.1.118 is my laptop on the inside of the NAT, and 10.20.20.20 is the outside box. Addresses and names of course have been changed, but consistently changed (that is, in the login banner from outside.somewhere.com showing last login from 10.10.10.10, and every other 10.10.10.10 is the same real-world address; that is, even though I had an ssh session open, and the translation from 192.168.1.118:46354 to 10.10.10.10:46354 to 10.20.20.20:22 was forwarding packets both directions, other packets from 10.20.20.20 on other source ports did not get translated at all, but (in this case) got blackholed by the routing to a Null device in the Cisco 7206 doing the NAT. In the interests of full disclosure, there is a second Cisco router (a 12008) with the only ACL's in front of the NAT box; for the duration of this test the following ACL was added to take the firewall out of the loop, and then removed after the nmap run was complete: access-list 150 permit ip any host 10.10.10.10 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Kororaa Lite beta released
On Thursday, January 06, 2011 04:19:08 pm Beartooth wrote: > On Wed, 05 Jan 2011 09:22:16 +1100, Chris Smart wrote: > > > Haha, well at least you gave it a shot!! :-) > > I'll do a bunch more, once I hear it has Gnome. Now why would a KDE-based respin want to include GNOME? :-) There is a similar GNOME respin called Omega; perhaps that would be a better fit. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: ipv6 question
On Thursday, January 06, 2011 06:22:06 pm Michael H. Warfield wrote: > You're just talking nameology here with this. Call it what you want, > there is still a state engine at the heart of the NAT driving the NAT > mappings. Sent a reply off-list, as this type of discussion is really off-topic for the Fedora list. If any one is interested in the details of the reply, please let me know and I'll forward you a copy. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: ipv6 question
On Sunday, January 02, 2011 05:40:00 pm Genes MailLists wrote: >How does one manage your internal ip6 network so that an ISP change > (which under NAT/ipv4 is irrelevant) - is straightforward/clean to manage ? Somehow I missed this message that started the whole thread... Shame on me. There as several ways, some of which have been mentioned. The one I'll mention is using the combination of provider-assigned (PA) IPv6 addresses on the outside with unique-local addresses (ULA; see RFC 4193) on the inside and one to one NAT66 in between ( see http://tools.ietf.org/html/draft-mrw-behave-nat66-02 for the draft for NAT66 at the IETF). A Linux ip6tables extension project to do this can be found at http://map66.sourceforge.net/ Unlike many, I see NAT as not primarily a security tool but as an end-user flexibility tool that keeps the end-user from ever having to renumber anything, as well as do sane internal addressing and subnetting. With IPv4 one inside global address to many inside local addresses (those are Cisco NAT's terms, as there are also outside global and outside local addresses that can be NATted) is the normal use-case; this isn't needed for IPv6, but an end user is not going to want to renumber the inside network when switching providers. Renumbering, even servers with DNS, is a pain, especially thanks to some DNS caches not honoring TTL. The alternative of running your own autonomous system (AS), running border gateway protocol (BGP), and getting your own provider-independent (PI) address space is not at all palatable to the ISP community (route table bloat due to prefix deaggregation); the only really valid case for PI space is multihoming, from an ISP and RIR/LIR perspective, in which case you'll already be an AS and running BGP to get the benefits of multihoming. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Printing directly on DVD
On Friday, January 07, 2011 08:04:30 pm Tom Horsley wrote: > I make no guarantees, I've only tried it on my C5580, but it has > worked OK through several updates of hplip now, so things may have > stabilized. This is nice. Now to try something like that with my Epson StylusPhoto R260. Then I can get rid of one other reason to bring up the Windows VM -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: mp3 libraries for f14
On Tuesday, January 18, 2011 02:45:25 am Kam Leo wrote: > If you need the mp3 plugin for gstreamer get it from here: > http://www.fluendo.com/shop/product/fluendo-mp3-decoder/ Let me second this. Fluendo has produced 'legal in the US' decoders for a number of codecs, including MP3, that have been properly licensed with the appropriate patent holder. The MP3 decoder is free; the codec bundle (which I have) is not, but it's well worth the price. A DVD player is also one of the items Fluendo has produced that has all the licenses necessary for legal DVD playback in the US. Some folks might actually need to pass a license audit with their Fedora; Fluendo's stuff will help you do that, whereas blindly installing the codecs from the 'freeworld' packages, or the gstreamer codecs available in several places, or the CSS decscrambling library available, will not pass a thorough license audit. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: [Fedora] Re: FC14 Installation Hangs
[Note that there is quite a list of things below to look at, but do look at the bugzilla entry at the very bottom and try that, possibly even first.] On Monday, January 24, 2011 02:09:52 pm Ashley M. Kirchner wrote: > What I don't get is how this dies with FC14 but not with CentOS 5 > ... did they figure out something that the FC developers haven't? No. The Fedora kernel is much newer than the C5 kernel, in terms of kernel version and IDE/ATA driver stack. CentOS 5, and Red Hat Enterprise Linux 5, are somewhat akin to Fedora *6* in terms of the versioning of the kernel. This does not mean security fixes since that kernel version have not been applied; they have been backported by Red Hat. What it does mean is that 17 versions of the 2.6 kernel (half of the versions to date) have passed, and the IDE/ATA drive handling has gone from the older IDE/ATA driver stack to the new libata driver stack, which makes the IDE/ATA drives be handled in the SCSI layer (and thus they become /dev/sdX# instead of /dev/hdX#). I find in the file "/usr/share/doc/kernel-doc-2.6.35.10/Documentation/i2c/busses/i2c-piix4" the statements: +++ If you own Force CPCI735 motherboard or other OSB4 based systems you may need to change the SMBus Interrupt Select register so the SMBus controller uses the SMI mode. 1) Use lspci command and locate the PCI device with the SMBus controller: 00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 4f) The line may vary for different chipsets. Please consult the driver source for all possible PCI ids (and lspci -n to match them). Lets assume the device is located at 00:0f.0. 2) Now you just need to change the value in 0xD2 register. Get it first with command: lspci -xxx -s 00:0f.0 If the value is 0x3 then you need to change it to 0x1 setpci -s 00:0f.0 d2.b=1 Please note that you don't need to do that in all cases, just when the SMBus is not working properly. Don't know if you're hitting this or not. Although I think I actually have one of those Force Computers CompactPCI boards; I'll have to check, if so I can test this there, at some point (not this week; too busy). Your dmesg shows you do, in fact, have an OSB4-based system, so this might be a part of the problem. Check to see if RHEL6 support is available for this system; if so, there might be a workaround for RHEL6 that might apply to the kernel in F14. Hmmm, looking closer at you C5 dmesg, I find: [snip] type=1404 audit(1295620090.833:2): selinux=0 auid=4294967295 ses=4294967295 hdb: ATAPI 48X CD-ROM drive, 128kB Cache, (U)DMA Uniform CD-ROM driver Revision: 3.20 piix4_smbus :00:0f.0: Found :00:0f.0 device 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html [snip] Yeah, the line right after the CD-ROM line, which is where F14 is hanging, is a callout for the piix4_smbus init. Doesn't mean that's the culprit Another possibility is tracked in the thread, and kernel bugzilla, started here: http://kerneltrap.org/mailarchive/linux-kernel/2010/8/13/4606665 Can you see if F13 will boot up? F14 shipped with 2.6.35.6; F13 with 2.6.33.3. You might be hitting a variant of https://bugzilla.redhat.com/show_bug.cgi?id=665109 There is some specific advice in that Bugzilla entry to try. It seems some of these machines with this chipset actually have ACPI, but it's not exactly 'all there' and a workaround has to be used. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: [Fedora] Re: FC14 Installation Hangs
On Tuesday, January 25, 2011 06:43:27 pm JB wrote: > Thirdly, stick around the thread for many days (even weeks) - there is > a good chance somebody will have time (like Lamar next week) and come up > with a good idea. Given what I've seen of Ashley's symptoms, it may be more BIOS related than chipset related, and I think the only OSB4 chipset board with a PC-style BIOS I have is the FORCE CPCI one; I checked my other boxen that are currently running, and the only other ServerWorks board I have up right now is a Dell 1600SC server, and it's an OSB5. I think I have four boxen with dual PIII's that probably have OSB4's, but they are oddballs that boot into Sun-style OpenPROM x86 (Network Appliance NetCaches; would love to get a Linux on them, but, AFAIK (and I'd love to be shown that I'm wrong), only the SPARC Linux distributions can boot from OpenPROM (used on virtually all Sun SPARC boxen) and don't have a PC-style BIOS). And even then if it's a BIOS issue that won't help any. As the ancient troubleshooting axiom goes 'to fix a problem you must find the problem.' -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Finding programs
On Wednesday, January 26, 2011 03:46:54 pm Wolfgang S. Rupprecht wrote: > The fact is that not only is the evince name non-decriptive, but the man > -k short description likewise has no mention of "pdf" so it won't be > found as a pdf viewer either. And that is a fault of upstream GNOME, not Fedora. The man page for evince should include meaningful (to apropos) keywords; fact of the matter is that the string 'PDF' does occur in the DESCRIPTION section of the man page, so why is apropos not seeing that? Using man -K PDF finds evince (among many others), but that's not just a quick list. But, as this is upstream GNOME doing this, you really should take it to upstream GNOME for change, which will then help out all GNOME using distributions, including Ubuntu, et al. Debian and Ubuntu also have the GNOME Document Reader named 'evince'. So this is not Fedora-unique, nor did it originate with Fedora. Do man -k PDF on a Ubuntu box and see what comes up. (I just did this; evince does not come up in a man -k pdf or a man -k PDF). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fun and games with 3TB hard drives.
On Sep 30, 2011, at 2:00 PM, linux guy wrote: As for the automount gpt issue, as far as I can tell, kernel support for gpt is fairly new. I'm sure this issue will be address shortly, if it hasn't been already. I've been using a GPT disk in my laptop for quite a while, F12 at least, dual-booting with Mac OS X and set up with native GPT support in F12 (am now at F14). The partitions on the internal disk show up in Dolphin, and have ever since F12. For fdisk-like usage but for GPT grab gdisk. smime.p7s Description: S/MIME cryptographic signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: kernel/system can't see all 4G memory
On Nov 3, 2011, at 3:46 AM, George R Goffe wrote: I upgraded my lenovo 60t to 4G memory and don't seem to be able to see all 4G of the upgrade. The hardware spec for this machine says it supports 4G memory. Any hints/clues/tips would be GREATLY appreciated. It is a hardware limitation in the 945M chipset; the chipset physically only has 32 address lines, and the PCI/PCI-e memory map has to go somewhere. That 'somewhere' is typically the top 1GB of address space, leaving 3GB (give or take) available for RAM. If you don't have that 33rd address line, you can't go above the 32-bit barrier PAE or 64 bit regardless. Same thing is true in my Dell Precision M65, although the Dell BIOS squeezes a little more out of it, 3.5GB or so is what I get with 4GB of RAM installed, and the 64-bit kernel, Fedora 14. The 965 chipset fixes this by adding physical address lines to the chipset and adding remapping support in hardware. In the Dell case, the Precision M65 is virtually the same machine as a Latitude D820; both have the 945; the Latitude D830 and equivalent Precision model have the 965, and can address all 4GB of RAM and can map the RAM that is displaced by the PCI/PCI-e address space above the 4GB (32-bit) line. (If your BIOS has 'PCI Memory Hole Remapping' support you can try that; see http://en.wikipedia.org/wiki/PCI_hole for more information. But this won't help go above the 32-bit addressing barrier if the chipset physically only has 32-bits of addressing capacity, regardless of processor installed. Again, neither PAE nor 64-bit OS will help since the 945 chipset physically does not have a 33rd (and above) address line, so the PCI/ PCI-e memory map has to go somewhere in the 4GB (32-bit) address space, taking away from the 4GB of installed RAM. Please also see http://www.dansdata.com/askdan00015.htm and http://www.linuxquestions.org/questions/linux-hardware-18/intel-945-chipset-and-4gb-of-memory-578912/ smime.p7s Description: S/MIME cryptographic signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: kernel/system can't see all 4G memory
On Nov 3, 2011, at 12:13 PM, George R Goffe wrote:
grep 'BIOS-e820' /var/log/dmesg
[0.00] BIOS-e820: - 0009f000
(usable)
0009F000=636K; this is to the bottom of the UMB. ("640K should be
enough for anyone")
[0.00] BIOS-e820: 0009f000 - 000a
(reserved)
[0.00] BIOS-e820: 000d2000 - 000d4000
(reserved)
[0.00] BIOS-e820: 000dc000 - 0010
(reserved)
UMB/BIOS (Real mode) which is still 'reserved' in this x86_64 day
[0.00] BIOS-e820: 0010 - bfed
(usable)
1MB and up to 3070MB, your 3GB of RAM.
[0.00] BIOS-e820: bfed - bfedf000 (ACPI
data)
[0.00] BIOS-e820: bfedf000 - bff0 (ACPI
NVS)
[0.00] BIOS-e820: bff0 - c000
(reserved)
[0.00] BIOS-e820: f000 - f400
(reserved)
[0.00] BIOS-e820: fec0 - fec1
(reserved)
[0.00] BIOS-e820: fed0 - fed00400
(reserved)
[0.00] BIOS-e820: fed14000 - fed1a000
(reserved)
[0.00] BIOS-e820: fed1c000 - fed9
(reserved)
[0.00] BIOS-e820: fee0 - fee01000
(reserved)
[0.00] BIOS-e820: ff80 - 0001
(reserved)
PCI and PCI express mapping areas. Your video (among other things)
needs memory addresses; think of this as the 32-bit equivalent of the
20-bit upper memory blocks. In the case of 386 and up processors,
hardware remapping of the reserved addresses was accomplished through
virtual 8086 mode from 32-bit protect mode, and thus a 386 memory
manager (QEMM, EMM386, etc) actually was a 32-bit 'kernel' that
presented a single V86 'VM' and emulated real mode in that V86 VM, and
set up the 386's MMU to map RAM into those holes. Microsoft built
upon this foundation the House of Windows/386, which morphed into the
House of Windows 3.x (enhanced), which morphed into the House of Win9x/
ME.
Many 386 motherboards from that era had '1MB' of RAM, but only 640K
was usable without UMB mapping (and address line A20 'rollover' into
the HMA, thanks to the segmented x86 architecture, for boards with
more than 1MB). The 32-bit boards have the same line, at 3GB, and for
much the same reasons.
The BIOSs on Dells with 945 chipsets allow the ACPI business to move
up, and thus frees up a few hundred MB of RAM address space.
The 965 chipset has hardware memory remapping, and can thus take the
1GB of RAM 'lost' by the PCI hole and put it above the 4GB line, thus
making the system need 33 bit or better hardware addressing (just
because the CPU has more than 32-bit addressing doesn't mean those
lines are connected to anything, after all.)
smime.p7s
Description: S/MIME cryptographic signature
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Yep, names like p4p1 are soooo much better than eth0 :-(
On Monday, October 17, 2011 11:39:29 PM Garry T. Williams wrote: > On Monday, October 17, 2011 16:57:42 jdow wrote: > > There is something wrong with ethp2p3? What KIND of device is easier > > to fathom if it is part of the name, ya know. > > Tell Sun, er, Oracle that. What are hme0, qfe0, and eri0? :-) :-) Happy Meal Ethernet 0 QuadFastEthernet 0 Haven't seen an ERI in the wild yet, and haven't Googled it, so don't know that one. The *BSD's also do this sort of thing. I would love something more consistent, similar to the cisco naming (even though depending upon which BU the device is from, interfaces and slots can either start with 0 or start with 1, but that's a digression). But PC hardware is so much more variable than cisco stuff is, and motherboards can have different lanes (for PCI-e) out of order relative to the slots, and server motherboards especially (like a SuperMicro P4DP6 to pull one off the top of my head) have multiple buses, so that the fifth slot is actually something like the third bus's second slot or similar, meaning you have to dig out the manual, and that's often of no help at all. Need the ability to 'blink LEDs' at times other than installation, IMO. (yes, you have this already in Fedora; install ethtool, and use ethtool -p $devname ) The current 'ethX' convention breaks in odd ways for different use cases. Especially when you replace a lightning-toasted NIC. And I have personally seen PCI enumeration order change on seemingly a whim, both due to kernel updates (this was EL4, so not a kernel version upgrade) and due to BIOS updates. And I'm not just talking slot order on a bus, but bus order on the northbridge. (Serverworks chipset in one instance, Intel chipset in another.) The fact of the matter is that consistent PC device enumeration is a hard problem, and people are working towards making this more consistent and better from the end-users' points of view. And I appreciate the effort, even with the bugs. Windows has the same problem, just a different flavor, and I've hit that, too, with XP, Vista, Server 2003, 7, and Server 2008. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to run preupgrade?
On Wednesday, November 09, 2011 06:57:54 AM Colin Paul Adams wrote: > I have F14 installed on my Macbook Air, and I want to upgrade to F16. > Everything appeared to go well. At the end I pressed the button to > re-boot as instructed, but my F14 system just re-booted as normal. How > do I actually perform the upgrade from this point? The preupgrade setup actually writes another boot entry to grub, and it may be confused by the way the booting is on you MacBook Air. During boot, break out to the grub menu and see if the preupgrade entry (I forget right off the top of my hat what it's called) shows up; look in /boot/grub/menu.lst (or /boot/grub/grub.conf) and see if it's there. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Fedora 16 on MacPro
On Wednesday, November 09, 2011 07:33:07 AM Don Quixote de la Mancha wrote: > There is a 32-bit UEFI boot loader that may work for you, that would > not require either Bootcamp or rEFIt. I looked into it a couple years > ago, but it was not then considered mature enough for production use. > Possibly it is now. I don't recall what it is called, though. Under a different EFI bootloader, parted sets the wrong GPT partition 'types' (type is really a misnomer, but it's a familiar term) and the Linux system won't boot. Has something to do with the hidden EFI boot partition and that there really can only be one of them. Here's a partition print from a working OS X/F-14 dual boot system (with grub installed to /dev/sda4, in this case, and not to the protective MBR; there's something else there), using the 'gdisk' partitioning utility: [root@localhost ~]# gdisk /dev/sda GPT fdisk (gdisk) version 0.8.1 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/sda: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): ---- Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 8-sector boundaries Total free space is 525717 sectors (256.7 MiB) Number Start (sector)End (sector) Size Code Name 1 40 409639 200.0 MiB EF00 EFI System Partition 2 409640 386210423 184.0 GiB AF00 Mac 3 386473984 402104319 7.5 GiB 8200 LinuxSwap 4 402104320 484024319 39.1 GiB0700 F14 5 484024320 861511679 180.0 GiB 0700 LinuxHome 6 861511680 976510983 54.8 GiBAF00 Interchange Command (? for help): -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to run preupgrade?
On Wednesday, November 09, 2011 11:41:48 AM Colin Paul Adams wrote: > > "suvayu" == suvayu ali writes: > suvayu> I think you misunderstood the bug. Your machine has already > suvayu> been upgraded to F16. It just boots the wrong kernel. To > suvayu> verify this, you can check with the following: > > suvayu> $ cat /etc/redhat-release Fedora release 16 (Verne) > > I don't get that, I get: > > Fedora release 14 (Laughlin) This is what I would expect, since the first boot after preupgrade is run on the older system is to anaconda in upgrade mode; that never ran, you've only downloaded all the pieces necessary to do the upgrade (pieces meaning the installer image with anaconda, the new boot, and all the rpm's necessary for your upgrade). That first reboot into anaconda does the upgrade itself. Do not trust the progress bar in an upgrade, incidentally. > I don't want to try any hacks to fix an upgrade process that doesn't > appear to have run. I have two more machines to upgrade as well. It appears that the grub entry to boot into the installer (anaconda) in upgrade mode isn't there, and thus it won't boot to it and thus won't upgrade. It's primed to boot to it, it just hasn't yet. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to run preupgrade?
On Wednesday, November 09, 2011 09:31:31 AM Colin Paul Adams wrote: > The bug says a new preupgrade will be released shortly. I think I should > wait for that, although I don't know how to find out when it is > available (I added myself to the CC list, so that should do the trick, i > hope). This is not your bug; anaconda hasn't yet run to do the upgrade at all. > Presumably if I yum erase preupgrade, and then install and run it again > when the new preupgrade is on the mirrors, it should just work. There's more to it than that, methinks. But see where the differences between grub.conf and menu.lst are; on my F-14 system (booting on a GPT disk): lowen@localhost:~$ ls -l /boot/grub total 348 ... -rw---. 1 root root 1510 Nov 7 12:07 grub.conf -rw-r--r--. 1 root root 11672 Nov 8 2010 iso9660_stage1_5 -rw-r--r--. 1 root root 13104 Nov 8 2010 jfs_stage1_5 lrwxrwxrwx. 1 root root 11 Nov 8 2010 menu.lst -> ./grub.conf ... -rw-r--r--. 1 root root 13576 Nov 8 2010 xfs_stage1_5 lowen@localhost:~$ which means, in a nutshell, that they are the same file and there should be no differences; but I've not run preupgrade, either. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: How to run preupgrade?
On Wednesday, November 09, 2011 08:52:43 AM Colin Paul Adams wrote: > I've not tried re-booting again yet (I have to look up to find out how > to break out to the grub menu), but just looking, I can see that it is > the first entry in grub.conf, but NOT in menu.lst. menu.lst is supposed to be a symlink to grub.conf. Odd that it's not. You could either manually add the line from grub.conf to menu.lst, or rename menu.lst to something else and symlink menu.lst to grub.conf ( using something like: ln -s ./grub.conf menu.lst ). Be careful, though, as a wrong edit or a missing file can cause your system to no longer boot. > I do see the keyword "hiddenmenu" in both. I'll try removing that to see > if it helps. Yeah, I always remove that line on machines that multiboot from grub (as opposed to multibooting to grub installed in the partition, which is the way this F-14 machine is set up, using a different bootloader). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Does Fedora repair itself..? What can't/doesn't Fedora repair in itself..?
On Nov 16, 2011, at 9:31 PM, Linda McLeod wrote: Is there a Fedora package that can send an active front-lines point, crawling through the whole OS, determining and repairing any new damage.. to fix it with an always clean secondary read only image, after custom configs done and locked-in the archive OS..? Something like DeepFreeze? Google for 'linux deep freeze fedora' and you'll find all kinds of pointers. There is a package called Ofris, a set of scripts called LinFreeze, among others. smime.p7s Description: S/MIME cryptographic signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Can't start portgresql after F15 -> F16 upgrade
On Nov 17, 2011, at 1:52 PM, Digimer wrote: 1. This should have generated a more useful error, like "data is from an old version and is not compatible." 2. Once the data directory was moved, I had to manually (re)initialize the database. There should be a mechanism for 'start' to realize the server needs to be initialized and do so. Oh, that's too funny. It used to, years ago. I know; I maintained the community packages from 1999 to 2004. The behavior was changed to require the separate initdb parameter to the SysV init file rather than automatically. I don't have the BZ number handy, but you shouldn't have too much trouble locating it. If nothing else, look in the changelog for the postgresql RPM ( use the command: rpm -qi --changelog postgresql ) The changelog entry listing in question, incidentally, can be found in the CentOS 6 RPM for postgresql, and is: + * Mon Dec 04 2006 Tom Lane 8.2.0-1 - Update to PostgreSQL 8.2.0 - Update to PyGreSQL 3.8.1 - Fix chcon arguments in test/regress/Makefile Related: #201035 - Adjust init script to not fool /etc/rc.d/rc Resolves: #161470 - Change init script to not do initdb automatically, but require manual "service postgresql initdb" for safety. Per upstream discussions. +++ So you'd want to look at the postgresql-hackers archive for this discussion thread. (the postgresql-hackers list is available on www.postgresql.org ). The current behavior is covered in the release notes; for Fedora 16 see: http://docs.fedoraproject.org/en-US/Fedora/16/html/Release_Notes/sect-Release_Notes-Changes_for_Sysadmin.html#id1410272 And for Fedora 15 see: http://docs.fedoraproject.org/en-US/Fedora/15/html/Release_Notes/sect-Release_Notes-Changes_for_SysAdmin.html#sect-RelNotes-Database_Servers However, the release notes do not mention the version upgrade from PostgreSQL 9.0.3 to PostgreSQL 9.1.1; they should have. As a general rule, special things are required to be done between major version releases of postgresql; a 9.1 server will not start against a 9.0 database. It has been this way for a very long time. That's why I linked to the F15 release notes, because the way to migrate from 9.0 to 9.1 should be pretty similar to the way the upgrade from 8.4 to 9.0 was handled, and that is in the F15 release notes. smime.p7s Description: S/MIME cryptographic signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Can't start portgresql after F15 -> F16 upgrade
On Nov 17, 2011, at 2:08 PM, Michael Cronenworth wrote: PostgreSQL version upgrades have always had to be handled by data dumps and data imports. With PostgreSQL 9.0 an upgrade utility was created, but it is not run by default as it is not considered stable. It works fine for me though. Perform a "yum install postgresql-upgrade" to install the utility and run "pg_upgrade" as root. :-) That wasn't the first cut at pg_upgrade, but IMO it's the best cut at it so far. What folks sometimes neglect to realize is how programmable the backend of PostgreSQL really is, and how that a full upgrade can involve recompiling or rebuilding functions inside the database (you can have user-written functions in C, Perl, Python, Tcl, and Ruby with Fedora-stock packages, for instance). That was always the hardest part of trying to upgrade PostgreSQL in a sane fashion. And there is a postgresql-upgrade package in the repositories, but not, apparently, on the install DVD. smime.p7s Description: S/MIME cryptographic signature -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Partition Management
On Thursday, December 01, 2011 09:31:25 PM Reindl Harald wrote: > Am 02.12.2011 02:55, schrieb Mike Dwiggins: > > My wife's machine is a full up FC14 x86_64 and I now have the joy of > > trying to put windows XP on due to constraints at her work. > why dual boot this days? 'Constraints at work' could mean a lot of different things; I've seen a few enterprise applications that don't work well in a VM for various reasons (anything that needs accurate timing works better on physical hardware, for instance, as does anything that needs access to certain physical hardware devices like hardware dongles (iLok, for instance, works better on physical hardware, and special interface cards, PCI and/or PC Card or Cardbus (or ExpressCard) sometime cannot be made work properly in a VM environment). More than likely it's the boss simply saying 'you will run Windows XP, period.' Most people either cannot afford to take a stand on principle (because there are bosses who will fire you if you don't do it their way, regardless) or would rather just fit in. Most people do not have OS freedom at work. Be glad if you do. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Partition Management SOLVED I Think
On Friday, December 02, 2011 03:41:50 AM Mike Dwiggins wrote: > Scary as it sounds [the i686 32-bit version] > recognized the built-in wireless equipment and That IS compatable > with her work environment. Ah, a wireless network requirement. That's another one to add to the list of things that can force an OS requirement, since Fedora (and other Linux) support for some wireless cards is spotty at best. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Using Draftsight on a 64 bit system
On Tuesday, December 06, 2011 10:03:41 AM Richard Shaw wrote: > I tried DraftSight many months ago while I was still running Fedora 14 > x86_64 but never got it to run. I'm running Draftsight on F14 x86_64 now; it seems to work fine. I don't recall having to do anything particularly special, but it has been a while since I installed it. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Using Draftsight on a 64 bit system
On Tuesday, December 06, 2011 03:15:14 PM Richard Shaw wrote: > I didn't spend too much time trying to get it to work, it was probably > some 32-bit library I was missing. I decided that using an open source > program like FreeCAD which includes solid modeling If solid modeling isn't important, there's always QCAD. The fully open source version is included in Fedora, but it's a version behind the 'pro' version that costs a little bit. Just another option; I've used QCAD for a while and like it, but it is definitely 2D only. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
