Re: fedup 20 - 21 - 22 - Plasma closed unexpectedly
On 07/25/2015 07:01 PM, Ed Greshko wrote: After reboot, login from a different machine and create a fresh user. Then login as that new user to see if you have the same issue. Either that or simply change to a text console without logging in at the GUI. And, while you're at it, activate the Magic SysRq key and test it (Different mobos require different combinations of keys to activate it.) so that if it locks up again, you can reboot easier. -- users mailing list users@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
Re: unmaintained bugs
Chris Murphy ha scritto il 24/07/2015 alle 16:47: On Fri, Jul 24, 2015 at 7:58 AM, Matthew Miller mat...@fedoraproject.org wrote: On Fri, Jul 24, 2015 at 08:36:05AM +0200, antonio montagnani wrote: * If a package maintainer appears to be totally unresponsive to bug reports, follow the process here: https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers and when you contact him, you get the answer not to contact him on his personal mail (that is the same as in bugzilla)??? https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers#Notes_for_invalid_email_addresses responsive |riˈspänsiv| adjective 1 reacting quickly and positively I'd say a maintainer who responds to an email saying not to contact him on that email, is non-responsive. I find really silly that when you are encharged of a bug, there is no kind of supervisor checking if you are are working on it and any problem arisingImagine it at Nasa, ehi guy, I have no time to check your bug and don't bother me :-) -- Antonio M Skype: amontag52 Linux Fedora F22 (Twenty two) on Fujitsu Lifebook A512 http://lugsaronno.altervista.org http://campingmonterosa.altervista.org -- users mailing list users@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
Re: unmaintained bugs
On Sat, 25 Jul 2015 11:02:11 +0200 antonio montagnani antonio.montagn...@alice.it wrote: I find really silly that when you are encharged of a bug, there is no kind of supervisor checking if you are are working on it and any problem arisingImagine it at Nasa, ehi guy, I have no time to check your bug and don't bother me :-) Thats not how open source projects work. ;) Keep in mind that maintainers of Fedora packages are largely doing so in their spare time for their own reasons. They may like/use the package, or they may want to help out other people who do, or any of a number of other reasons. Additionally, bugs/issues are present in all software, and maintainers need to figure out where to spend their time. I find http://www.rants.org/2010/01/10/bugs-users-and-tech-debt/ to be a great read on this. :) As to the responsive question and emails, personally I would surely respond to a personal email asking if I was still around/working on some package, but I would very much dislike getting bugs directly on personal email. It's bad for a lot of reasons for bug fixing purposes: * It doesn't allow easy filtering into one place so you can work on bugs in the time you have set aside to do so. * It cuts out all co-maintainers of a package from the conversation, some of which may be more active or know the solution to your bug. * It's hard to notify anyone who might be interested in a fix. * It doesn't allow easy transfer. If a maintainer decides to hand a package off to another maintainer(s) they may not have those emails or know anything about those bugs. So, please do file bugs or issues in bugzilla. kevin pgpI8o2JNAEfn.pgp Description: OpenPGP digital signature -- users mailing list users@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
Re: fedora 22 live
On 07/25/2015 10:09 AM, Beartooth wrote: It's certainly what a lot of us who gave up on Gnome3 are running. Fwiw, one of us on another list posted that he had been running xfce4 till his machine began to resemble cold molasses, then tried lxde and was very pleased. It'll be interesting to see if that happens a lot. When that happened to me, I asked myself why and realized that I didn't have enough RAM, or a fast enough chip for today's systems. As it happened, I had enough spare cash for an upgrade, and am still running Xfce with Compiz. (Gnome 3 doesn't play nice with Compiz, although Gnome 2 did.) -- users mailing list users@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
fedup 20 - 21 - No X
Ah, fedora upgrades using fedup ... Starting with Fedora 20, did yum update and then fedup --network 21 --product=nonproduct Took a while but there were no issues but remember, as root export PATH=$PATH:$HOME/bin:/sbin:/usr/sbin or use su - to become root otherwise fedup has an issue. So, now rebooted and it started. I have all my machines in multi-user mode just in case there is an issue with X. Now tried to start X ... and there was an issue. From bottom of /var/log/Xorg.0.log [53.686] (II) Module dri2 already built-in [53.686] (EE) NOUVEAU(0): [drm] failed to set drm interface version. [53.686] (EE) NOUVEAU(0): [drm] error opening the drm [53.686] (EE) NOUVEAU(0): 892: [53.686] (II) UnloadModule: nouveau [53.686] (EE) Screen(s) found, but none have a usable configuration. [53.686] (EE) Fatal server error: [53.686] (EE) no screens found(EE) START ALL /var/log/Xorg.0.log [67.937] X.Org X Server 1.16.3 Release Date: 2014-12-20 [67.937] X Protocol Version 11, Revision 0 [67.937] Build Operating System: 3.17.8-300.bz1178975.fc21.x86_64 [67.937] Current Operating System: Linux localhost.localdomain 4.0.8-200.fc21.x86_64 #1 SMP Fri Jul 10 21:09:54 UTC 2015 x86_64 [67.937] Kernel command line: BOOT_IMAGE=/vmlinuz-4.0.8-200.fc21.x86_64 root=/dev/mapper/luks-2a80faec-d21d-4a06-80fe-ad5a445d8aa1 ro rd.luks.uuid=luks-2a80faec-d21d-4a06-80fe-ad5a445d8aa1 vconsole.font=latarcyrheb-sun16 rd.luks.uuid=luks-8597ed23-e47c-427d-834c-e2fc5ec21bd3 rhgb quiet LANG=en_US.UTF-8 [67.937] Build Date: 31 January 2015 11:23:27PM [67.937] Build ID: xorg-x11-server 1.16.3-2.fc21 [67.937] Current version of pixman: 0.32.6 [67.937]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [67.937] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [67.937] (==) Log file: /var/log/Xorg.0.log, Time: Fri Jul 24 21:05:21 2015 [67.937] (==) Using config directory: /etc/X11/xorg.conf.d [67.937] (==) Using system config directory /usr/share/X11/xorg.conf.d [67.938] (==) No Layout section. Using the first Screen section. [67.938] (==) No screen section available. Using defaults. [67.938] (**) |--Screen Default Screen Section (0) [67.938] (**) | |--Monitor default monitor [67.938] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [67.938] (==) Automatically adding devices [67.938] (==) Automatically enabling devices [67.938] (==) Automatically adding GPU devices [67.938] (==) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins [67.938] (==) ModulePath set to /usr/lib64/xorg/modules [67.938] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [67.938] (II) Loader magic: 0x81de40 [67.938] (II) Module ABI versions: [67.938]X.Org ANSI C Emulation: 0.4 [67.938]X.Org Video Driver: 18.0 [67.938]X.Org XInput driver : 21.0 [67.938]X.Org Server Extension : 8.0 [67.943] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [67.944] (II) xfree86: Adding drm device (/dev/dri/card0) [67.944] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 10 paused 0 [67.946] (--) PCI:*(0:6:0:0) 10de:0649:1462:7220 rev 161, Mem @ 0xfd00/16777216, 0xd000/268435456, 0xfa00/33554432, I/O @ 0xec00/128, BIOS @ 0x/524288 [67.946] (II) LoadModule: glx [67.946] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [67.948] (II) Module glx: vendor=X.Org Foundation [67.948]compiled for 1.16.3, module version = 1.0.0 [67.948]ABI class: X.Org Server Extension, version 8.0 [67.948] (==) AIGLX enabled [67.948] (==) Matched nouveau as autoconfigured driver 0 [67.948] (==) Matched nv as autoconfigured driver 1 [67.948] (==) Matched nouveau as autoconfigured driver 2 [67.948] (==) Matched nv as autoconfigured driver 3 [67.948] (==) Matched modesetting as autoconfigured driver 4 [67.948] (==) Matched fbdev as autoconfigured driver 5 [67.948] (==) Matched vesa as autoconfigured driver 6 [67.948] (==) Assigned the driver to the xf86ConfigLayout [67.948] (II) LoadModule: nouveau [67.991] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [67.991] (II) Module nouveau: vendor=X.Org Foundation [67.991]compiled for 1.16.1, module version = 1.0.11 [67.991]Module class: X.Org Video Driver [67.991]ABI class: X.Org Video Driver, version 18.0 [67.991] (II) LoadModule: nv [67.991] (WW) Warning, couldn't open module nv [67.991] (II) UnloadModule:
Re: unmaintained bugs
Roger Heflin ha scritto il 25/07/2015 alle 17:54: You are assuming that the maintainers are employed/paid to maintain that project. In quite a number of cases they are not paid for it, so given that you may or may not get it fixed. And if I was a volunteer for a project and my supervisor started harassing me, then you would need a new maintainer for that project. Remember they are not being paid and you are not paying for the product. Even when one has an expensive paid support contract getting some things fix is still often impossible/difficult and in that case there is some limited contract requirements for the support organization to help you. Remember most of the less used parts are volunteers they may or may not have time to fix the bug. I have fixed a few bugs that were in stuff that I used and that I was pretty sure there was no paid person to maintain. I submitted the fix/patch back to fedora and they fairly quickly put that patch into an update. This is how open source generally can work, others see the bug, figure out the fix and submit the fix. On Sat, Jul 25, 2015 at 4:02 AM, antonio montagnani antonio.montagn...@alice.it wrote: Chris Murphy ha scritto il 24/07/2015 alle 16:47: On Fri, Jul 24, 2015 at 7:58 AM, Matthew Miller mat...@fedoraproject.org wrote: On Fri, Jul 24, 2015 at 08:36:05AM +0200, antonio montagnani wrote: * If a package maintainer appears to be totally unresponsive to bug reports, follow the process here: https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers and when you contact him, you get the answer not to contact him on his personal mail (that is the same as in bugzilla)??? https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers#Notes_for_invalid_email_addresses responsive |riˈspänsiv| adjective 1 reacting quickly and positively I'd say a maintainer who responds to an email saying not to contact him on that email, is non-responsive. no, I am not assuming that maintainers are paid, but when you are a volunteer you must be honest to you and other people to say when you cannot continue to be a volunteer. And the circle is broken when the final user reports a bug but nobody seems to be working on it for a long time and you have no feedback -- Antonio M Skype: amontag52 Linux Fedora F22 (Twenty two) on Fujitsu Lifebook A512 http://lugsaronno.altervista.org http://campingmonterosa.altervista.org -- users mailing list users@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
printing impossible
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, What wrong with cups/ghostscript? I am unable to print on my system (fedora 21) message: ghostscript quit unexpectedly ghostscript-core 9.15.6.fc21.x86_64 Thank you. - -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYFAlWzw8QACgkQdE6C2dhV2JUi/wCeNULg8AaaWO9w5MiEMz5yNJLd WdAAn1JE2rgY0+uszvHtr+3ego3MFdBb =EIZ8 -END PGP SIGNATURE- -- users mailing list users@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
Re: fedup 20 - 21 - No X
On Sat, 25 Jul 2015 06:37:10 -0700
Rich Emberson emberson.r...@gmail.com wrote:
Ah, fedora upgrades using fedup ...
Starting with Fedora 20, did
yum update
and then
fedup --network 21 --product=nonproduct
Took a while but there were no issues but
remember, as root
export PATH=$PATH:$HOME/bin:/sbin:/usr/sbin
or use
su -
to become root otherwise fedup has an issue.
So, now rebooted and it started.
I have all my machines in multi-user mode just
in case there is an issue with X.
Now tried to start X ... and there was an issue.
[snip]
[2.969504] fbcon: nouveaufb (fb0) is primary device
[3.284089] nouveau :06:00.0: fb0: nouveaufb frame buffer
device [3.284091] nouveau :06:00.0: registered panic notifier
[3.290053] [drm] Initialized nouveau 1.2.1 20120801 for
:06:00.0 on minor 0
END dmesg
So, fedup somehow blew away something.
The Question is what?
rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
kmod-libs 19-1.fc21 x86_64
kmod 19-1.fc21 x86_64
What did fedup change and how can I recover?
If you're using kmod, that means you've been using the rpmfusion nvidia
binary driver, right? But it looks like the kernel is trying to use the
nouveau open source driver. They're incompatible.
Maybe you need to set up to use the nvidia binary blob again. I think
this involves blacklisting nouveau and installing the nvidia driver for
your kernel. There should be instructions you can find online, or in
the archives of this list, for how to do this.
--
users mailing list
users@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
Re: fedora 22 live
On Fri, 24 Jul 2015 12:56:03 -0700, Rick Stevens wrote: On 07/24/2015 12:36 PM, Patrick Dupre wrote: Hello, In Fedora 22 live, which version is almost a gnome 3 version? Mate, LXDE, or ? IMHO, XFCE (at least that's what I use). It's certainly what a lot of us who gave up on Gnome3 are running. Fwiw, one of us on another list posted that he had been running xfce4 till his machine began to resemble cold molasses, then tried lxde and was very pleased. It'll be interesting to see if that happens a lot. -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is. -- users mailing list users@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
Re: New linux kernel getrandom call seems to be missing in Fedora. Anyone know why?
On Sat, Jul 25, 2015 at 10:18 AM, stan stanl-fedorau...@vfemail.net wrote: There's a new getrandom call in the kernel since 3.19. When I look in the /usr/include/linux/random.h, it is there, but commented out. Since this call uses /dev/urandom or /dev/random, it is far better than the rand () and random () calls, which are linear congruential and repeat after only 2**31 calls. The PRNG in the kernel is a modified mersenne twister, and the repeat is, from memory, ~2**1700. Not to mention that it is modified, and so is better. Here's a link to an online man page. http://man7.org/linux/man-pages/man2/getrandom.2.html Was there a security issue? Or is it just not ready for prime time? I don't know, but if there's no answer by Tuesday consider posting the inquiry to the (Fedora) kernel list. -- Chris Murphy -- users mailing list users@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
Re: unmaintained bugs
You are assuming that the maintainers are employed/paid to maintain that project. In quite a number of cases they are not paid for it, so given that you may or may not get it fixed. And if I was a volunteer for a project and my supervisor started harassing me, then you would need a new maintainer for that project. Remember they are not being paid and you are not paying for the product. Even when one has an expensive paid support contract getting some things fix is still often impossible/difficult and in that case there is some limited contract requirements for the support organization to help you. Remember most of the less used parts are volunteers they may or may not have time to fix the bug. I have fixed a few bugs that were in stuff that I used and that I was pretty sure there was no paid person to maintain. I submitted the fix/patch back to fedora and they fairly quickly put that patch into an update. This is how open source generally can work, others see the bug, figure out the fix and submit the fix. On Sat, Jul 25, 2015 at 4:02 AM, antonio montagnani antonio.montagn...@alice.it wrote: Chris Murphy ha scritto il 24/07/2015 alle 16:47: On Fri, Jul 24, 2015 at 7:58 AM, Matthew Miller mat...@fedoraproject.org wrote: On Fri, Jul 24, 2015 at 08:36:05AM +0200, antonio montagnani wrote: * If a package maintainer appears to be totally unresponsive to bug reports, follow the process here: https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers and when you contact him, you get the answer not to contact him on his personal mail (that is the same as in bugzilla)??? https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers#Notes_for_invalid_email_addresses responsive |riˈspänsiv| adjective 1 reacting quickly and positively I'd say a maintainer who responds to an email saying not to contact him on that email, is non-responsive. I find really silly that when you are encharged of a bug, there is no kind of supervisor checking if you are are working on it and any problem arisingImagine it at Nasa, ehi guy, I have no time to check your bug and don't bother me :-) -- Antonio M Skype: amontag52 Linux Fedora F22 (Twenty two) on Fujitsu Lifebook A512 http://lugsaronno.altervista.org http://campingmonterosa.altervista.org -- users mailing list users@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 -- users mailing list users@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
New linux kernel getrandom call seems to be missing in Fedora. Anyone know why?
There's a new getrandom call in the kernel since 3.19. When I look in the /usr/include/linux/random.h, it is there, but commented out. Since this call uses /dev/urandom or /dev/random, it is far better than the rand () and random () calls, which are linear congruential and repeat after only 2**31 calls. The PRNG in the kernel is a modified mersenne twister, and the repeat is, from memory, ~2**1700. Not to mention that it is modified, and so is better. Here's a link to an online man page. http://man7.org/linux/man-pages/man2/getrandom.2.html Was there a security issue? Or is it just not ready for prime time? -- users mailing list users@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
Re: OT - NFS group ignored
On 07/26/15 03:41, Emmett Culley wrote: I just noticed that when accessing an NFS mount, the group is ignored. For example, on the server that shares the files via NFS that lists from the NFS client as: $ ls -l/nfs/web -rw-rw-r-- 1 root web_prog 491 Oct 16 2012 parse.php $ mount web:/ on /lvh1/web type nfs4 (rw,noatime,vers=4.0,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.6.12,local_lock=none,addr=192.168.6.232) A user on the client machine that is a member of group web_prog cannot write the file (parse.php). If the user is changed from root to the client user's UID via chown on the server, the user on the client machine can then write the file. The server is on CentOS 7 and the client is on Fedora 21. If I do the same test from a CentOS 7 or CentOS 6 machine client, it works as expected. That is, the group permissions are honoured by the NFS client on those non-Fedora machines. So, I figure there is something wrong with my Fedora NFS configuration. Nothing shows up that is related to this issue when searching the Internet. What I have tried: Insure that Domain in /etc/idmapd.conf is the same on both client and server. Though the fact that the user ID is honoured would indicate that is correct. Insured that the numerical user ID and group ID match on both client and server, even though until now I always assumed that idmapd did not require the numerical IDs to match with NFS4 Any help would be appreciated. What is the output of ls -l /nfs/we after you have performed the mount? Remember, the UID/GID are held in the file system itself. Before you mount, it will be the UID/GID of the mount point and after you mount it will be the UID/GID held by the newly mounted file system. -- If I wanted a blog or social media I'd go elsewhere -- users mailing list users@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
USB serial /dev/ttyUSB0 not set to group 'dialout' in F22
Since I've upgraded to F22 x86_64, I haven't been able to access serial ports from a user account in the dialout group. Doing an ls /dev/ttyUSB0 shows that the device special file is there, but the group is not set to dialout: $ ls -l /dev/ttyUSB0 crw-rw-r--. 1 root root 188, 0 Jul 25 03:29 /dev/ttyUSB0 Since the device file exists, udev is obviously finding the hardware, which is an FTDI TTL-232R, and it works fine for root. The udev rule to set the device's group to dialout appears to be present: $ grep dialout /usr/lib/udev/rules.d/*.rules /usr/lib/udev/rules.d/50-udev-default.rules:KERNEL==tty[A-Z]*[0-9]|pppox[0-9]*|ircomm[0-9]*|noz[0-9]*|rfcomm[0-9]*, GROUP=dialout Has anyone else seen this problem? Any ideas on why it's not getting set to dialout? -- users mailing list users@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
Re: OT - NFS group ignored
On 07/26/15 05:01, Ed Greshko wrote: What is the output of ls -l /nfs/we after you have performed the mount? Too early for me to be answering questions... :-) You probably want ls -ld /lvh1/web to make it easier to see. -- If I wanted a blog or social media I'd go elsewhere -- users mailing list users@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
Re: OT - NFS group ignored
On 07/25/2015 02:01 PM, Ed Greshko wrote: On 07/26/15 03:41, Emmett Culley wrote: I just noticed that when accessing an NFS mount, the group is ignored. For example, on the server that shares the files via NFS that lists from the NFS client as: $ ls -l/nfs/web -rw-rw-r-- 1 root web_prog 491 Oct 16 2012 parse.php $ mount web:/ on /lvh1/web type nfs4 (rw,noatime,vers=4.0,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.6.12,local_lock=none,addr=192.168.6.232) A user on the client machine that is a member of group web_prog cannot write the file (parse.php). If the user is changed from root to the client user's UID via chown on the server, the user on the client machine can then write the file. The server is on CentOS 7 and the client is on Fedora 21. If I do the same test from a CentOS 7 or CentOS 6 machine client, it works as expected. That is, the group permissions are honoured by the NFS client on those non-Fedora machines. So, I figure there is something wrong with my Fedora NFS configuration. Nothing shows up that is related to this issue when searching the Internet. What I have tried: Insure that Domain in /etc/idmapd.conf is the same on both client and server. Though the fact that the user ID is honoured would indicate that is correct. Insured that the numerical user ID and group ID match on both client and server, even though until now I always assumed that idmapd did not require the numerical IDs to match with NFS4 Any help would be appreciated. What is the output of ls -l /nfs/we after you have performed the mount? Remember, the UID/GID are held in the file system itself. Before you mount, it will be the UID/GID of the mount point and after you mount it will be the UID/GID held by the newly mounted file system. The results of ls -l on a file in the NFS share is provided above (from the client machine). The results of ls -ld (from the client machine) is: drwxrwsr-x 12 root web_prog 4096 Jul 25 13:28 /nsf/web My fedora user is definitely a member of the web_prog group and both the client and the server have the same numeric GID for that group. I don't know if this is something new as I recently moved some files to a new server (CentOS 6 to CentOS 7), and previous to the move my Fedora user owned those files on the old server. And I only just now discovered this issue. I also reinstalled Fedora 21 from scratch after attempting to try Fedora 22, and finding Fedora 22 not ready for prime time. Which further makes me suspect a configuration issue. BTW, am I wrong that idmapd should not require synchronized UIDs and GIDs between client and server, at least for NFS4? Emmett -- users mailing list users@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
Re: OT - NFS group ignored
On 07/26/15 07:38, Emmett Culley wrote: On 07/25/2015 02:01 PM, Ed Greshko wrote: On 07/26/15 03:41, Emmett Culley wrote: I just noticed that when accessing an NFS mount, the group is ignored. For example, on the server that shares the files via NFS that lists from the NFS client as: $ ls -l/nfs/web -rw-rw-r-- 1 root web_prog 491 Oct 16 2012 parse.php $ mount web:/ on /lvh1/web type nfs4 (rw,noatime,vers=4.0,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.6.12,local_lock=none,addr=192.168.6.232) A user on the client machine that is a member of group web_prog cannot write the file (parse.php). If the user is changed from root to the client user's UID via chown on the server, the user on the client machine can then write the file. The server is on CentOS 7 and the client is on Fedora 21. If I do the same test from a CentOS 7 or CentOS 6 machine client, it works as expected. That is, the group permissions are honoured by the NFS client on those non-Fedora machines. So, I figure there is something wrong with my Fedora NFS configuration. Nothing shows up that is related to this issue when searching the Internet. What I have tried: Insure that Domain in /etc/idmapd.conf is the same on both client and server. Though the fact that the user ID is honoured would indicate that is correct. Insured that the numerical user ID and group ID match on both client and server, even though until now I always assumed that idmapd did not require the numerical IDs to match with NFS4 Any help would be appreciated. What is the output of ls -l /nfs/we after you have performed the mount? Remember, the UID/GID are held in the file system itself. Before you mount, it will be the UID/GID of the mount point and after you mount it will be the UID/GID held by the newly mounted file system. The results of ls -l on a file in the NFS share is provided above (from the client machine). The results of ls -ld (from the client machine) is: drwxrwsr-x 12 root web_prog 4096 Jul 25 13:28 /nsf/web Does it help if you remove the sticky bit on the mounted directory? My fedora user is definitely a member of the web_prog group and both the client and the server have the same numeric GID for that group. I don't know if this is something new as I recently moved some files to a new server (CentOS 6 to CentOS 7), and previous to the move my Fedora user owned those files on the old server. And I only just now discovered this issue. I also reinstalled Fedora 21 from scratch after attempting to try Fedora 22, and finding Fedora 22 not ready for prime time. Which further makes me suspect a configuration issue. BTW, am I wrong that idmapd should not require synchronized UIDs and GIDs between client and server, at least for NFS4? The only thing I've needed to change in the default idmapd.conf is the Domain setting. -- If I wanted a blog or social media I'd go elsewhere -- users mailing list users@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
Re: unmaintained bugs
On Sat, Jul 25, 2015 at 11:02:11AM +0200, antonio montagnani wrote: I find really silly that when you are encharged of a bug, there is no kind of supervisor checking if you are are working on it and any problem arisingImagine it at Nasa, ehi guy, I have no time to check your bug and don't bother me :-) Note that this basically _is_ the case when you pay for Red Hat Enterprise Linux and create a support request through the official channels for that. And, for Red Hatters where _that_ is their primary job but they work on Fedora too, those cases will therefore always necessarily take precedence. That doesn't mean that people don't care about the bug reports from other channels, but they can't always be the top priority. And that's just for maintainers who happen to work at Red Hat — for others, it's not their day-job at all. Maintainers _should_ address bugs — that's why we have that unresponsive maintainer process, after all — but there's no SLA. There's really no way you can get that *anywhere* without paying for it. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- users mailing list users@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
OT - NFS group ignored
I just noticed that when accessing an NFS mount, the group is ignored. For example, on the server that shares the files via NFS that lists from the NFS client as: $ ls -l/nfs/web -rw-rw-r-- 1 root web_prog 491 Oct 16 2012 parse.php $ mount web:/ on /lvh1/web type nfs4 (rw,noatime,vers=4.0,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.6.12,local_lock=none,addr=192.168.6.232) A user on the client machine that is a member of group web_prog cannot write the file (parse.php). If the user is changed from root to the client user's UID via chown on the server, the user on the client machine can then write the file. The server is on CentOS 7 and the client is on Fedora 21. If I do the same test from a CentOS 7 or CentOS 6 machine client, it works as expected. That is, the group permissions are honoured by the NFS client on those non-Fedora machines. So, I figure there is something wrong with my Fedora NFS configuration. Nothing shows up that is related to this issue when searching the Internet. What I have tried: Insure that Domain in /etc/idmapd.conf is the same on both client and server. Though the fact that the user ID is honoured would indicate that is correct. Insured that the numerical user ID and group ID match on both client and server, even though until now I always assumed that idmapd did not require the numerical IDs to match with NFS4 Any help would be appreciated. Emmett -- users mailing list users@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
Re: fedup 20 - 21 - 22 - Plasma closed unexpectedly
On 07/26/15 09:51, Rich Emberson wrote: X starts but there is no mouse control (pointer on screen but the mouse does not move it) and after a minute or less I get an widget stating that the Plasma desktop closed unexpectedly. I have to login from another machine to do a reboot. You're a KDE user and quite a bit has changed. One question and one suggestion Q. Just for information... Are you using kdm or sddm as your display manager? Suggestion After reboot, login from a different machine and create a fresh user. Then login as that new user to see if you have the same issue. -- If I wanted a blog or social media I'd go elsewhere -- users mailing list users@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
Re: OT - NFS group ignored
On 07/26/15 07:46, Ed Greshko wrote: Does it help if you remove the sticky bit on the mounted directory? Sorry, I meant the setgid bit. But, FWIW, I'm trying to replicate a failure here and can't. ds:/volume1/syntegra on /syntegra type nfs4 (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0, timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.18,local_lock=none,addr=192.168.1.152) [egreshko@meimei /]$ ll -d syntegra/ drwxrwsr-x. 5 egreshko egreshko 4096 Jul 26 07:58 syntegra/ [egreshko@meimei /]$ grep ^egreshko /etc/group egreshko:x:65539:maria Login as maria [maria@meimei syntegra]$ cd /syntegra/ [maria@meimei syntegra]$ ll total 12 drwxr-xr-x. 3 egreshko egreshko 4096 May 28 11:08 backups drwxrwxrwx. 3 root root 4096 Jul 6 11:40 @eaDir drwxrwxr-x. 5 egreshko egreshko 4096 Apr 9 11:36 linux-releases [maria@meimei syntegra]$ touch x [maria@meimei syntegra]$ ll total 12 drwxr-xr-x. 3 egreshko egreshko 4096 May 28 11:08 backups drwxrwxrwx. 3 root root 4096 Jul 6 11:40 @eaDir drwxrwxr-x. 5 egreshko egreshko 4096 Apr 9 11:36 linux-releases -rw-rw-r--. 1 nobody egreshko0 Jul 26 08:05 x -- If I wanted a blog or social media I'd go elsewhere -- users mailing list users@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
Re: unmaintained bugs
Hi On Sat, Jul 25, 2015 at 1:15 PM, antonio montagnani wrote: no, I am not assuming that maintainers are paid, but when you are a volunteer you must be honest to you and other people to say when you cannot continue to be a volunteer This is much more tricky than you apparently assume it to be. Here is just a few different cases to consider from my own experience: 1) When a package becomes orphaned, sometimes you pick it up because you are using it or a component you are using it depends on it but then updates start coming in and people report bugs and you realize you don't have the time for maintaining the library itself even though the software that you do want to maintain, depends on it. 2) You bring a new package into Fedora with the idea that you are going to use it actively. A few months later, something better suited for you pops out and you aren't paying as much attention to the package you brought in. 3) Your volunteer time decreases because you switched jobs, moved places, got promoted etc and you don't have the time but you don't want to cut off involvement either. You look for co-maintainers but your package is obscure enough that only a few people even use it and noone is interested in maintaining it with you. Your choice is between abandoning the package with the understanding that you are going to have to maintain it privately for your own use (private repo before or copr these days) or maintain it with the understanding that you aren't going to have the time to answer every bug report immediately. Rahul -- users mailing list users@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
fedup 20 - 21 - 22 - Plasma closed unexpectedly
Again, fedora upgrades using fedup ...
Starting with Fedora 20, did
... stuff ...
fedup --network 21 --product=nonproduct
... stuff ...
fedup --network 22 --product=nonproduct
So, now rebooted and it started.
I have all my machines in multi-user mode just
in case there is an issue with X.
Now tried to start X ... and there was an issue.
X starts but there is no mouse control (pointer on screen
but the mouse does not move it) and after a minute or
less I get an widget stating that the Plasma desktop
closed unexpectedly.
I have to login from another machine to do a reboot.
rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep plasma
plasma-workspace 5.3.2-2.fc22 x86_64
plasma-nm-openswan 5.3.2-1.fc22 x86_64
plasma-nm-vpnc 5.3.2-1.fc22 x86_64
plasma-nm-openvpn 5.3.2-1.fc22 x86_64
plasma-milou 5.3.2-1.fc22 x86_64
plasma-breeze-common 5.3.2-1.fc22 noarch
plasma-breeze 5.3.2-1.fc22 x86_64
plasma-nm-openconnect 5.3.2-1.fc22 x86_64
kf5-plasma 5.11.0-1.fc22 x86_64
plasma-nm 5.3.2-1.fc22 x86_64
kdeplasma-addons 5.3.2-1.fc22 x86_64
plasma-desktop 5.3.2-3.fc22 x86_64
plasma-pk-updates 0.2-1.fc22 x86_64
kde-settings-plasma 22-11.fc22 noarch
plasma-nm-l2tp 5.3.2-1.fc22 x86_64
plasma-desktop-doc 5.3.2-3.fc22 noarch
plasma-nm-pptp 5.3.2-1.fc22 x86_64
plasma-systemsettings 5.3.2-1.fc22 x86_64
rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
akmod-nvidia-340xx 340.76-2.fc22.12 x86_64
kmod-libs 21-1.fc22 x86_64
akmods 0.5.3-2.fc22 noarch
kmodtool 1-23.fc22 noarch
kmod 21-1.fc22 x86_64
xorg-x11-drv-nvidia-340xx-kmodsrc 340.76-1.fc22 x86_64
As user (not root):
qdbus --system
:1.0
org.freedesktop.systemd1
:1.1
org.freedesktop.login1
:1.10
:1.15
:1.2
org.freedesktop.Avahi
:1.3
org.freedesktop.ModemManager1
:1.4
org.freedesktop.problems.daemon
:1.5
org.fedoraproject.FirewallD1
:1.6
com.redhat.ifcfgrh1
org.freedesktop.NetworkManager
:1.7
:1.8
org.freedesktop.PolicyKit1
org.freedesktop.DBus
dmesg | grep -i nouv
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.0.8-300.fc22.x86_64
root=UUID=19fd15d5-0e5d-4019-bf06-4dac9744be1b ro
rd.luks.uuid=luks-2a80faec-d21d-4a06-80fe-ad5a445d8aa1
vconsole.font=latarcyrheb-sun16
rd.luks.uuid=luks-8597ed23-e47c-427d-834c-e2fc5ec21bd3 rhgb quiet
nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off
[0.00] Kernel command line:
BOOT_IMAGE=/vmlinuz-4.0.8-300.fc22.x86_64
root=UUID=19fd15d5-0e5d-4019-bf06-4dac9744be1b ro
rd.luks.uuid=luks-2a80faec-d21d-4a06-80fe-ad5a445d8aa1
vconsole.font=latarcyrheb-sun16
rd.luks.uuid=luks-8597ed23-e47c-427d-834c-e2fc5ec21bd3 rhgb quiet
nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off
/sbin/lsmod |grep nouveau
nothing returned
I notice that there were some mail threads discussing
something like this but I could not find one this
the solution.
Thanks
Richard
--
users mailing list
users@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
Re: OT - NFS group ignored
On 26Jul2015 08:06, Ed Greshko ed.gres...@greshko.com wrote: But, FWIW, I'm trying to replicate a failure here and can't. My standard question in this situation is: how many groups is the user in on the client machine? Cheers, Cameron Simpson c...@zip.com.au Music journalism: People who can't write interviewing people who can't talk for people who can't read. - Frank Zappa -- users mailing list users@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
Re: OT - NFS group ignored
On 07/26/15 10:34, Cameron Simpson wrote: On 26Jul2015 08:06, Ed Greshko ed.gres...@greshko.com wrote: But, FWIW, I'm trying to replicate a failure here and can't. My standard question in this situation is: how many groups is the user in on the client machine? Well, in my non-failing case, just 2. Not heard of a limitation in that area. -- If I wanted a blog or social media I'd go elsewhere -- users mailing list users@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
Sending a desktop to a big screen
Hi there, imagine a medium sized office room, where four engineers hack away (all of them currently have Fedora 22 workstations, to stay on topic.) On that room there's a fifth PC, hooked to a big TV on the wall (also running F22) that has Firefox running full screen with some visualization of sorts (dashboard thingy). Those five computers are all on the company wired network... nothing you haven't seen a thousand times before. Now, Sally, one of the engineers wants to share her desktop with the others and uses application XYZ to project/cast/extend/send it to the big TV (via its PC, of course). All of them discuss whatever was on her mind, and five minutes later, she closes application XYZ and the office goes back as it was before. Fred wants to do the same, and he does. Actually all of them can. They asked me what is XYZ. I was thinking on a member of the VNC family, but what they want to do is the reverse of what one normally do with VNC. To make things more... interesting? XYZ must never go out of the corporate LAN and if it were Open Source, the better. Any ideas on XYZ? Best regards, Amit. PS. Erm... one last thing. If there's a solution, could it include sending the audio as well? -- users mailing list users@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
Re: OT - NFS group ignored
On 26Jul2015 10:39, Ed Greshko ed.gres...@greshko.com wrote: On 07/26/15 10:34, Cameron Simpson wrote: On 26Jul2015 08:06, Ed Greshko ed.gres...@greshko.com wrote: But, FWIW, I'm trying to replicate a failure here and can't. My standard question in this situation is: how many groups is the user in on the client machine? Well, in my non-failing case, just 2. Not heard of a limitation in that area. Historically there was a 16 group protocol limit on what the client passed to the NFS server, so unless the file's group was in your first 15 secondary groups it would not be consulted for file access. Let's see what the OP has to deal with. Cheers, Cameron Simpson c...@zip.com.au -- users mailing list users@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
Convert system to multiboot to test rawhide
Hi, I was reading https://fedoraproject.org/wiki/Releases/Rawhide where it mentions that one suggested way to use rawhide is to use it On a multiboot system, alongside a stable release of Fedora or another operating system. Is there a guide to convert a stable Fedora system into a multiboot one? Thanks, R Mercado -- users mailing list users@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
Re: Disk partition
On 07/19/15 16:55, Robert Nichols wrote: On 07/19/2015 02:44 PM, Gordon Messmer wrote: On 07/19/2015 11:36 AM, g wrote: Logical partitions within the extended partition will always be numbered consecutively starting with 5. If you delete or merge some logical partitions, all of the higher partition numbers will shift down. if you can post a mutual site that i can upload a jpg, i would be more than happy to upload a shot of 'disk utility' showing; sdb1sdb2 sdb3sdb6sdb5 12 GB NTFS 2.1 GB Swap 11 GB ext4 32 GB ext4 23 GB ext4 In your case, sdb5 appears to be listed in the logical partition table before sdb6, but describe an area that appears further into the disk. That doesn't contradict what Robert wrote. Indeed. Partitions 5 and 6 are _numbered_ consecutively, they just aren't _arranged_ consecutively on the disk. Some tools will list them in disk order, some in numerical order. A GUI tool that shows a graphical map of the disk will, of course, be showing them in disk order. robert gorden, you both are correct. after reading your replies, i decided to look at partitions to see what i may have been doing to have such partitions. iirc, sdb5 was actually a part of sdb3 before i decided to cut down size of sdb3. while looking at what was on partitions, i decide to move files to a better place and get rid of the no longer need ntfs. new config is; sdb1sdb5 sdb6 sdb7 2 GB /boot 2.1 GB swap 11 GB / 65 GB /home with further cutting up of sdb1 for a fedora install, after i finish reading up on 'efi' and going back thru all the post about 'efi' partitioning. -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g . -- users mailing list users@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
Re: Convert system to multiboot to test rawhide
On 07/25/15 05:05, R Mercado wrote: Hi, I was reading https://fedoraproject.org/wiki/Releases/Rawhide where it mentions that one suggested way to use rawhide is to use it On a multiboot system, alongside a stable release of Fedora or another operating system. Is there a guide to convert a stable Fedora system into a multiboot one? Thanks, R Mercado . https://docs.fedoraproject.org/en-US/Fedora/22/html/Multiboot_Guide/index.html -- If Bill Gates got a dime for every time Windows crashes... ...oh, wait. He does. THAT explains it! -+- in a world with out fences, who needs gates. CentOS GNU/Linux 6.6 tc,hago. g . -- users mailing list users@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
