Re: failed to ..
by Patrick Dupre
Hello Chris,
More information. This what I get until the first FAILED
kvm: disabled by bios
started Configure read-only root support
Starting Load Random Seed
Started Load Random Seed
scsi
sd
sd [sdb]
World regulatory domain
(start_freq - end_freq @
Calling CRDA for country
systemd-udevd[390]: renamed
[ OK ] Found device ST9500420AS
Activating swap /dev/disk/by-uuid/026838a7-740a-4630-bb7d-b8b7e74657c0
Adding 3077840k swap on /dev/sda5
[ OK ] Activated swap /dev
[ OK ] Reached target Swap
[ OK ] Started Monitoring of LVM2 mirrors,
[ OK ] Found device ST9500420AS
Starting File System on /dev/sda16
[ OK ] Found device /dev/mapper/VolGrpSys3-usr_src
Starting File System Check on /dev/mapper/VolGrpSys3-usr_src
[ OK ] Started File System on /dev/sda16.
[ OK ] Started File System on /dev/mapper/VolGrpSys3-usr_src
Mounting /usr/src....
Mounting /boot
[ OK ] Found device /dev/mapper/VolGrpSys3-tmp.
Starting File System Check on /dev/mapper/VolGrpSys3-tmp.
Mounting FUSE Control File System
[ OK ] Mounted FUSE Control File System
[ OK ] Mounted /usr/src
EXT4-fs (sda16): mounted
[ OK ] Started File System on /dev/mapper/VolGrpSys3-tmp.
Mounting /tmp
[ OK ] Mounted /boot
[ OK ] Mounted /tmp
[ OK ] Found device /dev/mapper/VolGrpSys3-usr_local
Starting File System Check on /dev/mapper/VolGrpSys3-usr_local
Mounting /usr/local
[ OK ] Found device /dev/disk/by-uuid/225d0e0d-3fd0-4757-88be-ae4862470358.
Starting Cryptography Setup for luks-225d0e0d-3fd0-4757-88be-ae4862470358..
[ OK ] Listening on Journal Service...
[FAILED] Failed to start Journal Service.
See `systemctl status system-journal.service' for details.
The crypted partition is the /home
What do you think?
Thank.
> ----- Original Message -----
> From: Chris Murphy
> Sent: 12/28/13 08:13 PM
> To: Community support for Fedora users
> Subject: Re: failed to ..
>
> On Dec 28, 2013, at 11:46 AM, Patrick Dupre <pdupre(a)gmx.com> wrote:
>
> > Dear Chris,
> >>
> >> On Dec 27, 2013, at 7:25 PM, Patrick Dupre <pdupre(a)gmx.com> wrote:
> >>>
> >>> cp -a /mnt/linux1/* /mnt/linux2
> >>
> >> This does not copy .hidden files. There are quite a few:
> > You are right and wrong
> > cp -a copies all the hidden files located inside the sub-directories recursively
> > (I checked on that).
>
> Aha, so as long as there are no hidden files in /mnt/linux1 then it's fine, I see. I tested this only with /boot/* and it did not copy the hidden .vmlinuz*.hmac files.
>
> Anyway there are reasons why live desktop installs use rsync and not cp, it's more reliable. I'm not sure what isn't being copied, or is being copied wrongly, but if things are copied correctly this should work. I've done it with rsync, xfs dump restore, btrfs send receive, and LVM thinp snapshots and those are all way easier and reliable than cp.
>
> > There is something else to fix. I cannot guess what is it!
>
> Post a photo of the failure.
>
>
> Chris Murphy
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 5 months
F20 Installs Fail From Every Angle
by Brian Hanks
Maybe I'm just getting old, but it seems to me that Fedora is becoming
less and less stable with each release. I've just tried repeatedly to
install Fedora 20 using a myriad of different methods over three
different machines. Not a single attempt was successful.
I've been using RedHat/Fedora since version 1.1 back in 1995 and I don't
think I've ever been as frustrated by the installation process as I am
now. It seems to me that the old installer was much more stable and
capable of dealing with complicated installation scenarios. With each
release I hope for improvements to the installation process, but I am
repeatedly disappointed.
Here's what I've tried so far and the outcome of each attempt:
1. Fedup Upgrade of two different HP laptops each currently with Fedora
19 and simple partitioning (ext4 only). I've attempted this upgrade
multiple times on each machine. It fails every time with a VirtualBox
dependency error. When I check the dependency issue that is reported I
find that all of the packages are actually installed. Ignoring the error
does not work either as the upgrade does not succeed.
2. DVD/USB install (64-bit F20 DVD ISO) of an older custom desktop
(Intel E6550 chip) currently with Fedora 19 and complex partitioning
(LVM & RAID 1). I've tried four times to do this install from DVD/USB.
Each time the installation has terminated with an unexpected error.
Twice this happened early in the installation process and twice when
attempting to install the boot loader. In all four cases, I used
BugZilla from within the installer to report the issue. In all four
cases it indicated that there was an open bug for the issue.
3. Net install (64-bit F20 boot.iso) of an older custom desktop (Intel
E6550 chip) currently with Fedora 19 and complex partitioning (LVM &
RAID 1). I managed to successfully get through the entire installation
process and reboot the machine only to be greeted with the dreaded
"Welcome to emergency mode." message on my screen.
I fully admit that I am not participating in the pre-release testing to
the degree that I did in the past, so I guess I shouldn't complain.
That said, it just seems like the installation process should be a lot
more stable than what I have experienced. If it were, there would
likely be a lot more Fedora users out there.
If you have any insight that will help complete one of the above failed
installations, please let me know.
Thanks,
Brian
10 years, 5 months
Tool to convert a video DVD for YouTube uploading
by Paul Smith
Dear All,
I have a video DVD with the following structure:
$ dir
AUDIO_TS VIDEO_TS
$
I would like to upload the video into YouTube. However, it seems that
I have first to convert the video DVD to one of the formats accepted
by YouTube. Could someone please direct me about how to achieve that
in Fedora?
Thanks in advance,
Paul
10 years, 5 months
Re: failed to ..
by Patrick Dupre
Dear Chris,
>
> On Dec 27, 2013, at 7:25 PM, Patrick Dupre <pdupre(a)gmx.com> wrote:
> >
> > cp -a /mnt/linux1/* /mnt/linux2
>
> This does not copy .hidden files. There are quite a few:
You are right and wrong
cp -a copies all the hidden files located inside the sub-directories recursively
(I checked on that). The thing that if does not is copy the
hidden file located right in /mnt/linux. It is why I copies the only file
which is concerned (.readahead)
IE, that doing rsync -avAHX source/ destination is not going to help
I would have done it if gparted live was offering this option
There is something else to fix. I cannot guess what is it!
Regards.
> find / -name .\*
>
>
> > I do not like to use dd, because I want to keep the size of the 2 patitions are different
> > I could use tar -c tar -x
>
> I would sooner use rsync -avAHX source/ destination
>
> http://www.mikerubel.org/computers/rsync_snapshots/#Rsync
>
> FYI new feature in Fedora 20 is LVM Thin Provisioning. You can create a snapshot of an existing LV and just use that as your new root. No copying. And it saves space because the snapshot uses the extents of the original (without changing them, changes cause new extents to be created that apply only to the snapshot). Basically the snapshot becomes a new LV.
>
> Chris Murphy
>
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 5 months
Re: failed to ..
by Patrick Dupre
> ----- Original Message -----
> From: Chris Murphy
> Sent: 12/28/13 03:04 AM
> To: Community support for Fedora users
> Subject: Re: failed to ..
>
> On Dec 27, 2013, at 6:55 PM, "Patrick Dupre" <pdupre(a)gmx.com> wrote:
>
> > the cp -a /boot_cloned and /boot_clone (when partition not active).
>
> I don't follow this.
I did this tons of times before without problem
Actually I did:
mount VolGrpSys2-root /mnt/linux1 - o ro
mount VolGrpSys3-root /mnt/linux2
cp -a /mnt/linux1/* /mnt/linux2
In the past it did not miss directories. Would it do it know?
I do not like to use dd, because I want to keep the size of the 2 patitions are different
I could use tar -c tar -x
You used cp /dev/sda /dev/sdb? Device to device? Or you specified directories to copy? I've had cp -a of directories not work, in particular it misses hidden files unless you explicitly copy them. I've had better luck with rsync. And I've had impressively good luck with btrfs send/receive, that's a cake walk, and fast.
>
> Chris Murphy
>
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 5 months
Disable PulseAudio on a NAS
by John Obaterspok
Hi,
I don't think I'll need to have PA enabled on my NAS. What is the easiest
way to *disable* it?
-- john
10 years, 5 months
Smooth Upgrade
by Dave Cross
Upgraded my Dell XPS 14z laptop from F19 to F20 last night using
fedup. Everything went smoothly and within an hour I was happily using
F20. Probably the smoothest upgrade I've seen between two versions of
Fedora (and I've been using Fedora for ten years).
Thanks to everyone who put time and effort into making the upgrade
process work so well.
Dave...
--
Dave Cross :: dave(a)dave.org.uk
http://dave.org.uk/
@davorg
10 years, 5 months
BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
by Steven P. Ulrick
Hello, Everyone
I just ran "yum update" and rebooted. Some time not long after that
reboot, I started getting message like this:
Dec 22 20:11:26 afolkey2 kernel: [ 4130.161465] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
I ran "grep -i "soft lockup"" with the following results:
[root@afolkey2 log]# grep -i "soft lockup" messages
Dec 22 20:11:26 afolkey2 kernel: [ 4130.161465] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:11:50 afolkey2 kernel: [ 4154.123765] BUG: soft lockup - CPU#1 stuck for 22s! [httpd:1793]
Dec 22 20:11:54 afolkey2 kernel: [ 4158.146632] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:12:26 afolkey2 kernel: [ 4190.104690] BUG: soft lockup - CPU#1 stuck for 23s! [httpd:1793]
Dec 22 20:12:26 afolkey2 kernel: [ 4190.129677] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:12:54 afolkey2 kernel: [ 4218.089855] BUG: soft lockup - CPU#1 stuck for 22s! [httpd:1793]
Dec 22 20:12:54 afolkey2 kernel: [ 4218.114842] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:13:22 afolkey2 kernel: [ 4246.075021] BUG: soft lockup - CPU#1 stuck for 22s! [httpd:1793]
Dec 22 20:13:22 afolkey2 kernel: [ 4246.100008] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:13:50 afolkey2 kernel: [ 4274.060185] BUG: soft lockup - CPU#1 stuck for 22s! [httpd:1793]
Dec 22 20:13:50 afolkey2 kernel: [ 4274.085171] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:14:18 afolkey2 kernel: [ 4302.045349] BUG: soft lockup - CPU#1 stuck for 22s! [httpd:1793]
Dec 22 20:14:18 afolkey2 kernel: [ 4302.070335] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:14:46 afolkey2 kernel: [ 4330.030515] BUG: soft lockup - CPU#1 stuck for 22s! [httpd:1793]
Dec 22 20:14:46 afolkey2 kernel: [ 4330.055500] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:15:26 afolkey2 kernel: [ 4370.009320] BUG: soft lockup - CPU#1 stuck for 22s! [httpd:1793]
Dec 22 20:15:26 afolkey2 kernel: [ 4370.034307] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
Dec 22 20:15:54 afolkey2 kernel: [ 4397.994486] BUG: soft lockup - CPU#1 stuck for 22s! [httpd:1793]
Dec 22 20:15:54 afolkey2 kernel: [ 4398.019473] BUG: soft lockup - CPU#3 stuck for 22s! [httpd:1889]
I rebooted into an older kernel and have not had any more of these
messages popping up.
Eventually, my system became unresponsive and I had to reboot.
I am running Fedora 20 (fully updated)
Installation method: fedup
Any ideas?
Steven P. Ulrick
10 years, 5 months
dual boot test
by bruce
Hi - I know I should probably post to centos, but I'm testing this
with centos, and then with fedora.
I'm trying to basically do a dual boot test, that will allow me to
dual boot into 2 different versions of centos, although, in this case,
I'm using the centos 6.5 image.
I went through the process that I've found from different
sites/articles, in order to set up the 2 OS installs.
I can boot into the 1st OS. I have screwed something up, as I'm not
able to boot into the 2nd OS.
I don't know if I screwed something up during the Install/Creation
process via the GUI, or if I've screwed something up during the
grub.conf modifications.
Any help/pointers would be greatly appreciated.
Thanks
-------------------------------------
The system setup:
-lenovo laptop
-250G Drive
-Centos 6.5
Steps:
-Went through the initial setup for the OS1
-setup the root/backup/home/swap
OS2 - master
root / 50
boot
home /home 10
apps /apps 10
backup /backup 5
set the boot to be on sda1 - as 500M
I then went back and installed the 2nd install of the Centos OS
using
lv2_root root / 10
boot
lv2_home home /home2 5
lv2_apps apps /apps2 5
lv2_backup backup /backup2 5
the boot was set to be the "/" on the sda so it's the same as the 1st..
I also didn't install the bootloader, which was the option on the
boot/install page of the GUI for the install process
I then modified the grub.conf page
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hidemenu
title Centos (2.6.32-431.e16.x86_64)
root (hd0,0)
kernel /vmlinux-2.6.32-431.e16.x86_64 ro
root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD
rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16
rd_LVM_LV=VolGroup/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb
quiet
initrd /initramfs-2.6.32-431.e16.x86_64.img
title Centos2 (2.6.32-431.e16.x86_64)
root (hd0,1)
kernel /vmlinux-2.6.32-431.e16.x86_64 ro root=/dev/sda2
initrd /initramfs-2.6.32-431.e16.x86_64.img
====================================
the fdisk -l for the system is ::
[root@localhost ~]# fdisk -l
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x77e3ed41
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 30402 243685376 8e Linux LVM
Partition 2 does not end on cylinder boundary.
Disk /dev/mapper/VolGroup-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap: 4009 MB, 4009754624 bytes
255 heads, 63 sectors/track, 487 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_home: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_backup: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_apps: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical):[root@localhost ~]# fdisk -l
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x77e3ed41
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 30402 243685376 8e Linux LVM
Partition 2 does not end on cylinder boundary.
Disk /dev/mapper/VolGroup-lv_root: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_swap: 4009 MB, 4009754624 bytes
255 heads, 63 sectors/track, 487 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_home: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_backup: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv_apps: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv2_root: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv2_home: 5242 MB, 5242880000 bytes
255 heads, 63 sectors/track, 637 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv2_backup: 5242 MB, 5242880000 bytes
255 heads, 63 sectors/track, 637 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv2_apps: 5242 MB, 5242880000 bytes
255 heads, 63 sectors/track, 637 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv2_root: 10.5 GB, 10485760000 bytes
255 heads, 63 sectors/track, 1274 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv2_home: 5242 MB, 5242880000 bytes
255 heads, 63 sectors/track, 637 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv2_backup: 5242 MB, 5242880000 bytes
255 heads, 63 sectors/track, 637 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/mapper/VolGroup-lv2_apps: 5242 MB, 5242880000 bytes
255 heads, 63 sectors/track, 637 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
10 years, 5 months
A question about chromium (not related to installation)
by Kevin Wilson
Hello,
Following the question about chromium installation in F20 recently in
this mailing list, but not related directly to it (and this is the
reason that I post it as a separate thread):
What are the benefits of using Chroimium over using google stable
chrome on Fedora ? Especially, are there any chances that using
chromium will play some audio streams which will not be played with
google stable chrome? I am asking it because I had some problems
with playing some mms content (but not all), which I **could** play
with firefox.
Regards,
Kevin
10 years, 5 months
