On 07/09/2013 01:22 AM, Gordon Messmer wrote:
> On 07/08/2013 09:39 AM, John Reiser wrote:
>> 1. Install a userid whose login shell is /usr/bin/sync
>> (or a script which does "sync; sync")
>> 2. Login as the sync user (twice, perhaps.)
>
> Running
On 07/08/2013, Adam Pribyl wrote:
> On Mon, 8 Jul 2013, "Jóhann B. Guðmundsson" wrote:
>
>> No need to open a discussion. SysRq is disable for are a reason and what you
>> are propose allows anyone that sits at the keyboard to kill all
>> process,reboot without syncing or authorization and all b
> I successfully installed fedora-19-live-kde-x86-64 by USB key.
> When I install DVD , after choose language, it has one more step to choose
> install media, from sdb1(USB key ), iso image or network. It reported
> the sdb1 not available , but the system is booting up by USB key, [so why?]
Anacon
> I made a USB device, and could boot up into the install application,
> but when to choose a device as install source , the sdb1 device, USB disk,
> verified to be not available , what is the reason ,
> how should i do and do I have to make DVD disk to install?
Here is one method that I use when
On 06/22/2013 09:05 AM, Chuck Forsberg WA7KGX wrote:
> I have a SIIG USB keyboard with mechanical switches.
> The mechanical switches greatly reduce the error rate when I type.
>
> The p8z77-vle plus BIOS does not seem to have a problem with this keyboard.
> Once Fedora finishes booting the keyboa
On 06/19/2013 07:47 PM, Chris Murphy wrote:
>
> On Jun 19, 2013, at 8:44 PM, John Reiser wrote:
>
>> On 06/19/2013 06:04 PM, Chris Murphy wrote:
>>
>>> Hmm, neither the Fedora 18 or 19 Xorg.0.logs contain 'software renderer' or
>>> '
On 06/19/2013 06:04 PM, Chris Murphy wrote:
> Hmm, neither the Fedora 18 or 19 Xorg.0.logs contain 'software renderer' or
> 'llvmpipe'.
>
> https://dl.dropboxusercontent.com/u/3253801/F18_Xorg.0.log
> https://dl.dropboxusercontent.com/u/3253801/F19_Xorg.0.log
>
> For 'glxinfo' on both F18 and 1
>> Is there a more definitive way to tell if gnome-shell is or isn't offloading
>> onto the GPU?
During installation, look in /tmp/X.log for which modules get loaded.
Here is what I see during install for [R200] [RV280] (PCI 1002:5960) Radeon
9250 (9200 PRO)
where the installed Gnome3 system wil
> Is there a more definitive way to tell if gnome-shell is or isn't offloading
> onto the GPU?
$ glxinfo | grep renderer
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits)
"llvmpipe" is the software CPU (SSE2) renderer
OpenGL renderer string: Gallium 0.4 on AMD REDWOOD
> I did a pxeboot install of today's rsync using the anaconda from TC5.
> I ran top(1) during the install and did not notice any unusual CPU
> utilization.
> This is on a 32 GB 3770K.
Which video graphics card, and which driver?
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
> If I try to do this in KVM (2x CPU), I see gnome-shell taking 5%, X not even
> displayed in top, and all CPU power going to rsync (2x 10%) and loop3 (80%).
Please tell us how much virtual RAM was allocated to the KVM instance.
loop3 at 80% CPU for long periods is page thrashing: re-decompressin
> Here are the installation test cases which have not yet been run against
> any of the Final TCs for any arch:
> https://fedoraproject.org/wiki/QA:Testcase_install_to_PATA_device
I installed Fedora-19-Final-TC3-i386-DVD.iso MATE desktop to bare metal i686
having no SATA channels and two PATA cha
On 06/10/2013 08:37 AM, Joerg Lechner wrote:
> I have now disabled, all what there is to disable (including parallel and
> serial port, second and third boot device), enabled USB, PS2, first boot
> device - cdrom, network etc.. This bootloader process took now approximately
> 1 minute.
> What
On 06/09/2013 10:50 PM, Joerg Lechner wrote:
> I have made a new installation via "Final TC2 DVD iso" (4.2GB). First checked
> my BIOS settings. Found "Boot Up Floppy Seek" enabled, but I also don't have
> a Floppy. Setting to "disabled" shows now the time for "bootloader
> installieren" (German
Joerg Lechner wrote:
> ... on an old PC (524MB Ram, 1,6 GHz, board KVTA5, 2 disks: 20GB Fedora
> tests, 250GB Windows XP, PATA)
> ... The process installing the bootloader at the end of the installation
> process took about half an hour.
It is best to investigate using VT2. Type (where is
Fu
> The output of efibootmgr --verbose is:
>
> BootCurrent: 0007
> Timeout: 1 seconds
> BootOrder: ,0007,0008,0005,0003,0006,0004
So this time you booted from 0007 (DVD), and next time you will boot from
(Windows) unless you change it.
> Boot* Windows Boot Manager
> HD(2,96800,318
On 06/06/2013 06:54 AM, A.J. Werkman wrote:
>
> Op 6-6-2013 15:41, Kamil Paral schreef:
>>> >
>>> >Is this a Fedora problem or is hardware setup to be blamed?
>> I think mixing UEFI and BIOS is not expected to work. But you shouldn't have
>> any problem running both systems - just use your one-ti
On 05/26/2013 12:55 PM, Samuel Sieb wrote:
> On 05/26/2013 12:37 PM, John Reiser wrote:
>> What should I expect? I get no error, but no much more:
>>
>>$ fedora-easy-karma
>>Getting list of installed packages...
>>Getting list of packages in updates-t
> It would be a huge help if some more people could help with the
> feedback. This is how it works:
>
> a) Get a FAS account, https://admin.fedoraproject.org/accounts
> b) Update to F19 / install from scratch
> c) Run fedora-easy-karma on the command line daily
What should I expect? I get no
On 05/22/2013 05:23 PM, Samuel Sieb wrote:
> On 05/22/2013 01:45 PM, John Reiser wrote:
>> On 05/22/2013 01:24 PM, drago01 wrote:
>>> Which means you'd be better off with file system level compression.
>>
>> Yes, if you have administrator privileges and st
On 05/22/2013 01:24 PM, drago01 wrote:
> Which means you'd be better off with file system level compression.
Yes, if you have administrator privileges and strategic planning,
and if you can tolerate a read-only fs (or your fs can handle overwrites),
then compression of the filesystem itself often
On 05/22/2013 12:04 PM, Clemens Eisserer wrote:
> As UPX requires executeables to be decompressed during startup (and
> furthermore does not support ELF shared libraries),
An executable main program which has been compressed by UPX
*can* use ELF shared libraries, and nearly all programs on Linux
On 05/22/2013 08:30 AM, Jaroslav Reznik wrote:
> The old fedora-install-fedora.ks was used,
> 9d0717ccdad4151072a54d8f974367cad42c061d
> had to be picked up. The missing groups are part of environments, so
> these were dropped http://paste.fedoraproject.org/13689/69226468/
It would be nice if th
The delta .iso for the i386 netinst of RC2 does not work at all.
Please fix it, or flush it. 366MB download of the full netinst is not gigantic,
but there was the teaser of a 23MB .diso ...
Details:
> https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
The file
http://dl.fed
On 05/16/2013 09:30 PM, Lawrence Graves wrote:
> When will the anaconda fix be added to Fedora 19 Beta RC1 in order to
> complete an install.
You can use the workaround right now:
https://bugzilla.redhat.com/show_bug.cgi?id=963503#c29
RC2 has been initiated:
https://fedorahosted.org/rel-en
> I don't know how many people are still using telnet server. I would
> hope very few. SSH is much more secure and already enabled by
> default. ;)
There are local networks that truly are local, providing services
for the _development_ of small embedded devices (think microcontrollers)
where teln
> I do not see where any logs are for this.
Anaconda keeps its logs in /tmp, not in /var/log.
The syslog is not in /var/log/messages but instead is in /tmp/syslog.
--
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
> What is the exact kernel F19 is using? Since I can't boot it, and its name on
> the stick is just vmlinuz, I can't tell what it is.
"file vmlinuz" prints the kernel version.
--
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo
> 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84 [GeForce
> 8600M GT] [10de:0407] (rev a1)
A very ordinary card, somewhat older.
>
>
>> What does F18 say in syslog /var/log/messages regarding any 'conflict's
>> in address space during initialization of the linux kernel?
>
>
On 04/25/2013 06:44 PM, Chris Murphy wrote:
> I'm stumped on how to get more information during the boot process. At this
> point I don't have enough information to file a bug.
>
> F18 works OK on this computer. Even with 3.9 kernels with a regression
> related to fb or nouveau, I still get ker
On 04/22/2013 06:36 PM, Felix Miata wrote:
> On 2013-04-22 19:24 (GMT-0400) Fernando Cassia composed:
>
>> I remember Pentium III machines came from the USB 1.x era, not USB 2.0.
>> So likely your BIOS won't allow you to boot from a USB-anything port
>> using "mass storage devices".
>
> PIII pred
UEFI install of RC3 failed for me because of another instance of Bug 949786,
auto-reported as duplicate with new Comment. TC6 had succeeded for me.
A second attempt using RC3 also failed for the same reason.
This time I'll upload more files from /tmp.
--
--
test mailing list
test@lists.fedorap
> As per the Fedora 19 schedule [1], Fedora 19 Alpha Release Candidate 3
> (RC3) is now available for testing.
The Live spins do not have "-RC3-" in the name:
https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC3/Live/i386/
Fedora-Live-Desktop-i686-19-Alpha-1.iso 16-Apr-2013 01:40 963M
> I have such a machine. What kind of media should I test - usb, disc, pxe, all
> of the above? Should I report results here?
Anything which causes the installer to attempt to setup the installed system
so that the installed system boots using UEFI. Usually this means that
the installer itself
> One question: can I just download the netinst and point it at a local
> development/19 mirror, or do I need to download the full DVD?
>
> Alternately: is it sufficient to just boot from the images in my local
> development/19 mirror (so I don't have to download anything new)?
You must use bare
> My question remains. In cases such as this, what component get the bugzilla?
LiveCD - LXDE
--
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
>>> LXDE Live iso still not ok. Successful boot not possible.
>> Has a bug been filed?
> And for each bug you find you search for duplicates if none found file a
> report against the relevant component
The original poster asks for the *name* of the Component.
If the LXDE Live spin does not boot
On 03/29/2013, Adam Williamson wrote:
> Sure, we knew it was yum. But working around the problem using an F18 yum
> build wouldn't be a good way to go about things, because it's not like we can
> ship F19 or even the final Alpha with an F18 yum build.
What I had in mind was running yum.fc18 on
Early on 03/29/2013:
> *IMPORTANT*: All DVDs and Lives with the exception of Live KDE and Live
> SoaS are oversized, so will not fit on the standard media.
It would have helped me to add something like, "The pending fix for bug 923547
was used during construction of TC3, so all the Lives are now l
On 03/26/2013 07:10 AM, Bruno Wolff III wrote:
> On Tue, Mar 26, 2013 at 00:17:35 -0400,
> Andre Robatino wrote:
>> *IMPORTANT*: All DVDs and Lives are oversized, so will not fit on the
>> standard media.
> Does anyone know the reason for this? I see this is likely breaking
> the nightly compos
> So, new bug, but file it against kernel or xorg-x11-drv-nouveau?
If "kill -TERM " does restart the X server
and results in a graphical display, then perhaps -nouveau might be better?
This report:
[NVA8][Nouveau] GPU lockup - switching to software fbcon
https://bugzilla.redhat.com/sho
> # koji download-build --arch=$(arch) systemd-198-6.fc19
> # koji download-build --arch=$(arch) dracut-026-48.git20130315.fc19
> # rpm -Fvh systemd*.rpm dracut*.rpm
error: Failed dependencies:
systemd = 198-4.fc19 is needed by (installed) libgudev1-198-4.fc19.i686
--
--
test mailing li
> If anyone has some time and is willing to help out, could you try to get
> a rawhide install by booting a f18 dvd/netinstall and trying to enable
> just the rawhide repo and disable the rest. Does anaconda even allow
> you to do this anymore these days? Does it work?
I booted Fedora-18-x86_64-DV
> Is there magic for bugs against 18 that are also bugs in 19 once branch
> happens?
I have participated in several bugzilla reports of this kind (bug in Fedora N
remains unfixed as Fedora N+1 appears with "new" package) but I have not seen
any "magic". The original reporter, or some person with
> Yeah OK but the first media recommended is still DVD/CD which also doesn't
> allow for persistent user data. The modern equivalent is to dd to a USB
> stick. In fact I think this idea of burning actual media is immensely
> wasteful and archaic and shouldn't be the first recommended media anymo
> dd is recommended dead last, really?
Under some conditions, livecd-iso-to-disk can be a lot faster because it uses
rsync
to update an existing Packages directory. So if you have a USB stick of full
install
for RC1, then running livecd-iso-to-disk using RC2.iso will transfer only
updated
fil
On 01/08/2013 04:47 PM, Frantisek Hanzlik wrote:
> i'm trying install f18 on older i686 machine (1.8GHz P4 CPU/512 MB
> RAM/160 GB HDD/Radeon 9000 64MB graphics), doing NFS graphical
> installation with XFCE desktop (and several add-ons groups).
> Installation started from installation CD (images/b
> Is there a fix for this error message "TSC calibration failed"
> that shows up in the boot sequence on Fedora 18.
It is likely that this is an issue between the Linux kernel and your
hardware+BIOS, and has little to do with Fedora itself. I haven't seen
the message on any of three machines wit
> Brasero should be checking the size beforehand, checking available
> writable-by-user space,
including shell environment variable TMPDIR (colon-separated list of
directories)
> and doing the right thing for the user (including
> asking them where appropriate) ...
--
t
> The audio output in pavucontrol can be dynamically moved
> between my internal audio / speaker and the HDMI TV, the
> internal audio produces sound while the TV does not.
One of the problems that I had was the Configuration tab
displayed by pavucontrol had "Profile: Off" instead of
"Profile: Dig
> Maybe there should be two groups of packages: important (core or
> whatever) that must be installed and other (not important) that might
> fail to install?
It is a general failing of anaconda that there is no way to recover
from errors except by starting over from the beginning.
Meanwhile, freq
On 12/07/2012 06:47 AM, Richard Ryniker wrote:
> Probably not. There are too many possibilities to make reasonable any
> default except "do what the user explicitly says is desired".
Except that for many years installing has collected all discoverable
swap partitions, and put them into /etc/fstab
On 11/16/2012 12:02 PM, Adam Williamson wrote:
> On Fri, 2012-11-16 at 20:44 +0100, Mateusz Marzantowicz wrote:
>> Sorry, maybe it's obvious but where can I find list of changes made
>> between TC8 and TC9 releases? I've had some issues with anaconda and
>> don't know if anything has changed from t
> I suspect the use case is 'test every version of OS/distro that comes
> down the pipe'... if that's your goal, your choices are:
>
> 1) virt
> 2) LVM (note: Linux only)
> 3) pile'o'partitions
>
> For those that can't do #2, and don't feel like doing #1...
Yes. Customers want to do _their own_
On 11/10/2012 08:15 PM, Adam Williamson wrote:
> That's fine and interesting, but we switched to grub2 in F16. The original
> poster was comparing F18 to F16, and I compared F18 to F17 and found F18
> slower. grub2 vs. grub1 cannot logically explain differences between releases
> from F16 onward
>> If you have many partitions, then the grub2 operating system prober
>> takes a while to construct grub.cfg: more than half a minute for my
>> three dozen partitions. This is new with grub2 instead of grub.
> Is there a bug for this?
https://bugzilla.redhat.com/show_bug.cgi?id=875356
--
--
> 36 partitions? Really? I thought GPT's 128+ partitions is actually an inside
> joke, ergo "you know if we give users this particular hurt me button, some
> will actually try it."
45 partitions across 4 drives in one box, 40 partitions across 4 drives
in another. Several OS, several distros, m
>> I noticed the post install processing in f16 lasted only
>> a few seconds, not the seemingly interminable wait
>> a Fedora 18 install takes.
If you have many partitions, then the grub2 operating system prober
takes a while to construct grub.cfg: more than half a minute for my
three dozen partit
On 10/23/2012 05:54 AM, Andre Robatino wrote:
> Karel Volný redhat.com> writes:
>
>> why doesn't yum say
>> "Warning: Group virtualization has all packages installed.
>> Nothing to do"
>
> The corresponding message for a single package looks like
>
> Package virt-manager-0.9.4-1.fc17.noarch al
> Am looking at root drive.
>
> Can I /boot (ext4), / (btrfs),
> or do I need swap also?
Read the manual page "man swapon":
swapon may not work correctly when using a swap file with
some versions of btrfs.
Thus if you want to allow the kernel to swap, then using a
swap file that resides on
> I haven't found a way yet with Latest TC4 to install /home to /sdb.
One way that is supposed to work: choose custom partitioning,
select both drives as destinations (click once on each icon),
then proceed and assign mount points as desired.
--
--
test mailing list
test@lists.fedoraproject.or
On 10/14/2012 05:42 PM, Chuck Forsberg WA7KGX N2469R wrote:
> On 10/14/2012 05:25 PM, Chuck Forsberg WA7KGX N2469R wrote:
>> Cleanup: libuser-devel-0.57.6-2.fc18.x86_64 313/569
>>
>> Makes yum hang. Is there a fix? Killing yum leaves the yum database
>> corrupted and may
> I am booting from a DVD via a usb device. The computer only has a cd drive
> and the Live-Desktop image is > 700 MB so I have to use a DVD to boot the
> Desktop DVD.
One of my boxes has CD only, and USB1.1 only. I plug in an external DVD
with USB2.0 interface into a PCMCIA (cardbus) card whi
> dracut-initqueue[196]: Warning: could not boot
> dracut-initqueue[196]: Warning:
> /dev/disk/by-label/Fedora-18-BetaTC3-x86_64-Live-D does not exist
> dracut-initqueue[196]: Warning: /dev/mapper/live-rw does not exist
>
> Entering emergency mode. Exit the shell to continue
> Type "journa
> Installing : kernel-3.6.0-3.fc18.x86_64
>96/190
> grubby fatal error: unable to find a suitable template
>
>
> The new kernel is not added to the grub.cfg. This is
> grubby-8.20-1.fc18.x86_64.
One cause of this is having /boot be
> the proposed partitioning criteria for F18
> So that leaves Beta. Here's what I've come up with for Beta so far:
>
> * The installer must be able to complete an installation using automatic
> partitioning to a disk with sufficient empty space, using the empty
> space and leaving the existing pa
>>> Gnome3 is not putting any effort into fallback mode. So my Radeon 9250
>>> purchased new in 2006 as a mid-life upgrade for a box with 1.6GHz Pentium 4
>>> (well above the Fedora minimum CPU) also runs only XFCE. Gnome3 forces
>>> fallback mode, where some Desktop features are *dropped* instea
On 09/24/2012 02:59 PM, Adam Jackson wrote:
> On Mon, 2012-09-24 at 13:30 -0700, John Reiser wrote:
>>> Do you have any old or new graphic hardware, working or not? Join this test
>>> week and help us to hunt down driver bugs before Fedora 18 Beta release!
>>
>>
> Do you have any old or new graphic hardware, working or not? Join this test
> week and help us to hunt down driver bugs before Fedora 18 Beta release!
There is doubt about whether this particular test day is worth the time.
At a minimum, don't bother with any Radeon card that is less than a Ra
On 09/15/2012 12:57 AM, Chuck Forsberg WA7KGX N2469R wrote:
> I downloaded the 64 bit RC 3.1 and burned another DVD+R.
It seems to me that 3.1 was abandoned:
http://lists.fedoraproject.org/pipermail/test/2012-September/110061.html
Just to clarify, the Gold images (both install and lives) are 1
> so I'll measure Fedora 17 Release (x86_64) on 3GHz CPU, 8GB RAM, SATA II:
>
>Duration Activity
>
> 12m26s write DVD+RW (3.8GB; 4X)
> 5m00s write DVD+R (3.8GB; 16X)
> -=-=-=-
>
> 3m48s Boot DVD+R, go until "Starting installation process
On 09/08/2012 03:49 PM, Chuck Forsberg WA7KGX N2469R wrote:
> Lately I have been able to install new versions of Spherical Cow
> using pxeboot with the liveos squashfs. Installing over a
> gigabit Ethernet is orders of magnitude faster than burning
> a DVD-RW
That's a big problem right there. I
> ... as things stand, we're one bug away from an RC compose.
Please give an explicit list of the literal package names which would
go into the RC compose, at least the ones that are not in fedora +
fedora-updates.
About 8 hours ago pungi aborted when I tried to compose a DVD from fedora +
fedor
> http://imagebuilder.fedoraproject.org/testimage/18/pretc4-2/Fedora-18a-pretc4-2-x86_64-netinst.iso
> - anaconda-18.6.2-1.fc18
This package does not show up after a search for 'anaconda' on
https://admin.fedoraproject.org/updates . This prevents leaving karma.
Booting netinst.iso from DVD (wi
On 07/06/2012 12:11 PM, Jon Ciesla wrote:
> On Fri, Jul 6, 2012 at 2:10 PM, Andre Robatino
> wrote:
>> I attempted installation using Fedora-20120703-x86_64-916dfe7-netinst.iso and
>> found that it only allows choosing one desktop. ...
> No, they can still be installed after install, or at instal
> I would like to test a dual Monitor F17 system on a VM.
> I have access to VMWARE and QEMU ...
Please be more specific. Two monitors on the same graphics card?;
or: two monitors each on a different backplane graphics card?;
or: two monitors, one on a backplane graphics card, plus one
on a USB-c
>> I want to set non-plugable multiseat under fedora 17. i get the error
>> " no valid EDID" on one of the two monitors. I get this Error on LG
>> and SAMSUNG LCD monitors. Changing NVIIDA graphic card to ATI Radeon
>> was of mo use. the other card is INTEL on board.
https://bugs.freedesktop.org/s
> I want to set non-plugable multiseat under fedora 17. i get the error
> " no valid EDID" on one of the two monitors. I get this Error on LG
> and SAMSUNG LCD monitors. Changing NVIIDA graphic card to ATI Radeon
> was of mo use. the other card is INTEL on board.
Please tell us the model number of
Look at the time difference between blocker status (first bugzilla'd,
nominated for blocker, and/or confirmed) and the package revision
(culprit created, then fixed.) There might be some relationship
between problem packages and frequency of releases.
--
--
test mailing list
test@lists.fedorapr
On 06/04/2012 07:02 PM, Kevin Fenzi wrote:
> I usually wait a week or so around release, since I don't want people
> looking for f17 to grab them.
>
> I'll update and look at doing a batch tomorrow.
Anaconda newUI may be a significant customer of nightly builds for F18 rawhide.
See https://fed
> Peter, how in general do you want to proceed where we have documented
> cases of graphics mode setting failure in grub2? Do you want individual
> bug reports for each affected bit of hardware? Downstream, upstream?
> What kind of info should be included? Thanks!
What's not good enough about usin
On 05/03/2012 07:05 AM, Adam Jackson wrote:
> My personal opinion is that Core and up are pretty tolerable and anything
> less kind of isn't but also already kind of wasn't. But I no longer really
> have any idea whether my threshold for acceptable interactivity matches that
> of anyone else.
> Packages skipped because of dependency problems:
> 1:samba4-client-4.0.0-45alpha18.fc17.i686 from updates-testing
> 1:samba4-common-4.0.0-45alpha18.fc17.i686 from updates-testing
> 1:samba4-dc-4.0.0-45alpha18.fc17.i686 from updates-testing
> 1:samba4-dc-libs-4.0.0-45alpha18.fc17.i
> Palimsest in Fedora 16 reports a disk (MAXTOR STM3320620AS) as failing:
> "DISK HAS MANY BAD SECTORS" etc.
> SMART: 197 Current pending Sector Count Value -4 sectors.
>
> Palimsest in Fedora 17 beta reports the same disk (MAXTOR STM3320620AS) as
> "OK"
> SMART: 197 Current pending Sector Co
> how we could build a more friendly image
> building system to help the Fedora QA community during the testing
> phase.
Short latency tends to improve friendliness. By fiddling with pungi
environment, I'm down to about 9.5 minutes to create an install .iso
after downloads have finished.
If make
> you're not providing much useful data.
https://bugzilla.redhat.com/show_bug.cgi?id=816238
--
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
On 04/24/2012 02:56 PM, Tim Flink wrote:
> http://tflink.fedorapeople.org/iso/20120424_f17-preTC1-3.x64.boot.iso
> I haven't done a bare metal install with this iso yet but it boots for
> me on multiple EFI machines, so I'm pretty confident that the kinks
> have been worked out.
EFI booting that
> http://tflink.fedorapeople.org/iso/20120424_f17-preTC1.x64.boot.iso
EFI booting eventually fails. I see the splash screen (night sky with
aurorae), the 5-second count down, allocating 1239 pages, "[Linux-EFI,
setup=...]", some flashes similar to VGA reset, then the ordinary Grub
boot of my alre
> What is it you do not like about the defaults such that you are chainloading ?
I have a couple dozen different OS root partitions: back to Fedora 6 (some cases
with both 32-bit and 64-bit variants), back to Ubuntu 7.10, SuSE, Debian
testing,
plus that Other OS. I like to identify the OS by hos
> What can I do with it in Rawhide.
>
> Have been dumped there during bootup.
The shell itself has reasonable features,
but the executables in $PATH are few,
in order to make initramfs small.
Find the executables by: "echo $PATH; echo /*bin/*" etc.
--
--
test mailing list
test@lists.fedorapro
> What should I do to make rpmbuild work for --target=i686?
Does this work:
export CC="gcc -m32"
rpmbuild -ba --target=i686 ...
--
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
> However, they aren't recognized [mounted] at all (not even upon subsequent
> graphical
> login), and this is bad. See
> https://bugzilla.redhat.com/show_bug.cgi?id=722712
> where there is some argument whether udisks2 or gvfs should bear the blame.
Cold- or warm-plugged filesystem devices do
On 04/13/2012 06:48 AM, Bill Nottingham wrote:
> Release notes seem fine. Basically, removable media mounted in the
> user's session are now mounted in a user-specific directory.
There's still a problem: cold-plugged media, or even warm-plugged media.
Cold-plugged (before boot) should be mounted
> Has rescue mode been removed? If so, what can I use instead?
Append " rescue" to the end of the kernel boot command line.
With an install DVD: type 'e' to get the boot stanza, use the
keyboard arrow keys to move to the line which begins "kernel",
type another 'e' to edit the "kernel" line. Ap
On 04/10/2012 07:03 AM, Horst H. von Brand wrote:
> John Reiser wrote:
>> A close-to-optimal strategy for typical cable modem ISP is:
>> 1. Sort the download list by size of file to be downloaded.
>> 2. Run two parallel threads. The f
On 04/09/2012 10:05 PM, Dan Mashal top-posted:
> 1) Yum should be intelligent enough to recognize this
>
> 2) yum-plugin-fastestmirror solves this problem.
>
> 3) I think we all upgraded from 14.4k modems a few years ago.
Replying in "top post" style may work for a management discussion,
but for
On 04/09/2012 07:18 PM, Dan Mashal wrote:
> As I said in the meeting let's just deprecate it [in favor of yum+network].
The problems I have seen with using only yum+network to perform a distro
version upgrade are:
1. It's a poor idea to be running almost anything else on the box
at the sam
On 04/04/2012 12:13 PM, Chuck Forsberg WA7KGX N2469R wrote:
> On 04/04/2012 11:51 AM, John Reiser wrote:
>>> Does a pxeboot install from a freshly rsync'd f17 tree give the
>>> same kernel et al. as installing from the rc3 dvd?What about
>>> yum update?
> Does a pxeboot install from a freshly rsync'd f17 tree give the
> same kernel et al. as installing from the rc3 dvd?What about
> yum update? Which gets the latest??
No. RC3 gives kernel-3.3.0-1;
updates-testing has kernel-3.3.0-8.
--
--
test mailing list
test@lists.fedoraproject.
> How do I find the most recent image?
There is only one Release image ever made and distributed by Fedora,
so if the checksum matches then you have the latest official image.
Updates are distributed electronically via yum in the repository
that is designated in /etc/yum.repos.d/fedora-updates.r
1 - 100 of 104 matches
Mail list logo
