Re: F21: why Fedora still has not alternative init?
On 05/04/2015 06:20 AM, Matthew Miller wrote: journald automatically scales its usage to its idea of available memory That's an explanation that's somewhat less troubling. I read the man page for journald.conf and was not enlightened. Which values am I looking at? I see references to in-memory filesystems, but that doesn't relate to resident size, does it? -- 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: F21: why Fedora still has not alternative init?
On 05/03/2015 04:13 PM, Frantisek Hanzlik wrote: Gordon Messmer wrote: SysV init scripts are here for ages They were large, inconsistent, and burdensome to maintain. The people who maintained them decided that there was a better option. If you are willing to maintain them, then you can do the work to provide an alternate init system. If you're not doing the work, then at some point you have to trust that the people who are doing the work know better than you do. We have lot of alternatives in Linux system (several desktop WMs etc) already, alternative init is in this case (IMO) just small piece of all system SW. init is a small piece of code, yes. But it's not just code, it's an interface. Lots of programs interface with systemd. If you want an alternative, you have to address all of those dependencies. To me, your interest in an alternative appears to be evidence that you lack familiarity with the scope of the work. Although I understand that there are features which are interesting for some Linux users, they are not too important to me. GNU/Linux systems *can* be tailored to individual needs. That's one of the great things about them. However, no specific distribution can be all things to all people. If you are interested in a GNU/Linux system that contains exactly the components you like, maybe try Linux From Scratch. Seriously. The education that it provides will improve your input and contributions. -- 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: /var/lib/mlocate/mlocate.db perms
On 05/03/2015 04:47 PM, jd1008 wrote: I distrust suid programs. Skepticism toward SUID root is sometimes merited. Evaluating your own needs for such programs is reasonable. Distrusting the mechanism itself is tin-foil-hat-crazy. I find it strange that a security minded system needs an suid program to do something as simple as locate a file. It's not SUID, it's SGID to "slocate". The locate file will only allow users to locate files they have access to. In order to enforce that restriction, users have to be prevented from reading the database directly. -- 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: F21: why Fedora still has not alternative init?
Forget it, Dan. It's Chinatown. RBM On Tue, 2015-05-05 at 08:07 +1000, Dan Irwin wrote: > I find the attitude of many of the senior fedora people quite > disappointing. There is no freedom, there is ZERO choice on this > issue. It's a dictatorship. > > > My observations are that the systemd people are not the best people > for the job. In fact, they are probably at the complete other end of > the spectrum. They don't appear to listen to users. They appear to > focus their effort on starting laptop computers, while ignoring the > majority of linux use cases. > > > > systemd is not for servers. But apparently, it's not for embedded, > mobile phone, or tablet either. In fact, systemd doesn't run on > anything that doesn't run glibc. Now i know these are not relevant to > fedora. Lately I have been questioning the relevance of fedora anyway. > Mailing list volume has reduced to a trickle. Diminishing users. We > really are only a beta for RHEL. > > > Honestly, systemd is already irrelevant in the grand scheme of linux. > It was a nice experiment, and has some great ideas. What was sold to > us way back in 2010 is NOT what we have today. We were sold an init > replacement. Instead, we have a madman taking over every aspect of the > computer with lots of new, untested code, full of half baked ideas. > > > It's not enterprise. And anyone who says it is clearly doesn't do > enterprise linux for a living. > > > > > On Tue, May 5, 2015 at 3:13 AM, Tim > wrote: > Allegedly, on or about 03 May 2015, Marko Vojinovic sent: > > Oooh, I see, writing buggy and ill-documented code is > (ultimately) > > better for the market survival of the software company! > > Isn't that how Microsoft made their millions? > > -- > > > All mail to my mailbox is automatically deleted, there is no > point > trying to privately email me, I will only read messages posted > to the > public lists. > > ZNQR LBH YBBX > > > > -- > 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 -- 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: F21: why Fedora still has not alternative init?
I find the attitude of many of the senior fedora people quite disappointing. There is no freedom, there is ZERO choice on this issue. It's a dictatorship. My observations are that the systemd people are not the best people for the job. In fact, they are probably at the complete other end of the spectrum. They don't appear to listen to users. They appear to focus their effort on starting laptop computers, while ignoring the majority of linux use cases. systemd is not for servers. But apparently, it's not for embedded, mobile phone, or tablet either. In fact, systemd doesn't run on anything that doesn't run glibc. Now i know these are not relevant to fedora. Lately I have been questioning the relevance of fedora anyway. Mailing list volume has reduced to a trickle. Diminishing users. We really are only a beta for RHEL. Honestly, systemd is already irrelevant in the grand scheme of linux. It was a nice experiment, and has some great ideas. What was sold to us way back in 2010 is NOT what we have today. We were sold an init replacement. Instead, we have a madman taking over every aspect of the computer with lots of new, untested code, full of half baked ideas. It's not enterprise. And anyone who says it is clearly doesn't do enterprise linux for a living. On Tue, May 5, 2015 at 3:13 AM, Tim wrote: > Allegedly, on or about 03 May 2015, Marko Vojinovic sent: > > Oooh, I see, writing buggy and ill-documented code is (ultimately) > > better for the market survival of the software company! > > Isn't that how Microsoft made their millions? > > -- > > > All mail to my mailbox is automatically deleted, there is no point > trying to privately email me, I will only read messages posted to the > public lists. > > ZNQR LBH YBBX > > > > -- > 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
Re: Nouveau trouble
On Thu, 30 Apr 2015 09:24:52 +0200 Anders Wegge Keller wrote: > On Tue, 28 Apr 2015 09:18:02 +0200 > Anders Wegge Keller wrote: > > > On Mon, 27 Apr 2015 20:24:28 -0400 > > Matthew Miller wrote: > > >> I just ran into this with Fedora 22, and was pointed to a libdrm 2.4.60 > >> bug. If you downgrade to libdrm-2.4.59 (perhaps this build > >> http://koji.fedoraproject.org/koji/buildinfo?buildID=606048), can you > >> reproduce? > > > I have installed the previous version of libdrm, and will try to see if > > I can reproduce it, after the next reboot. As an added information, I've > > found that using the channel popup-menus in X-Chat is a pretty surefire > > way of provoking the fault, so it should be easy enough to see if the > > behaviour changes. > > So far, it looks like downgrading to libdrm-2.4.59 has fixed the problems. > I haven't seen X lock up until now. After a week with 2.4.59, and no errors, I upgraded t 2.4.60 again. After a few hours I had the same symptoms, so there's definitely an indication of a problem with the 2.4.60 release. -- //Wegge -- 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: failed systemctl services?
On Mon, May 04, 2015 at 12:48:46PM -0700, stan wrote: > Those were interesting reads. It seems the infrastructure is in place > to deal with the problem of service failure, but operational inertia is > slowing adoption. In other words, just a normal human system. :-) > The one thing I didn't see addressed was the comment requesting some > notification if a service became a chronic (ab)user of the restart > feature, so remedial action could be taken or requested. Well, it's logged but, yeah. In general, we don't have a standard, integrated monitoring/alerting service for Fedora, except for desktop notifications, which aren't ideal for many cases. (Like, basically anything but a single-user desktop.) Working on fixing this would be an interesting project — maybe under Fedora Server... > It should be a simple matter for the OP to put the recommended > Restart=on-failure command into the service file under the [Service] > section for the failing services and see what happens. Yep. And note, by the way, that you shouldn't edit the files in /usr/lib/systemd/system/ — instead, create new ones in /etc/systemd/system/ with the same name. These will be merged, with values from /etc taking precedence. (And in recent systemd, you can use `systemctl cat` to show the merged files, or `systemctl edit` as a handy way to call your prefered editor to edit the config snippets.) -- Matthew Miller 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
Re: The spamming servers
On Mon, 4 May 2015 19:56:12 +0200 Heinz Diehl wrote: > On 04.05.2015, stan wrote: > > > I don't see a defense against such exploits as long as people can > > install software on their systems. The alternative is Mac on > > steroids, only the software that big brother approves of and allows > > you to use. > > The choice is yours. Either you stick with straight Fedora software > (and blame the Fedora folks when you got infected :-) ) or you > install software on your own, and take the risk. Nothing's wrong with > either ways, that's what free sofware is all about. > > Oh, and there's no such thing as 100% security. We agree! And I'm not in the 'all your hardware are belong to us' camp. -- 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: failed systemctl services?
On Mon, 4 May 2015 11:51:08 -0400 Matthew Miller wrote: > Actually, *systemd* is that process. That's one of its huge features > missing in the old init system. Take a look at the man page for > systemd.service — search for "Restart=". > > However, we don't configure most things that way out of the box... > yet. There was discussion about this three years ago, reopened a year > ago... > > https://fedorahosted.org/fpc/ticket/191 > > and the current guidelines > > https://fedoraproject.org/wiki/Packaging:Systemd?rd=Packaging:Guidelines:Systemd#Automatic_restarting > > but as far as I know there hasn't been a big effort to bring existing > services in line. (Seems like a worthwhile project if anyone's > interested.) Those were interesting reads. It seems the infrastructure is in place to deal with the problem of service failure, but operational inertia is slowing adoption. In other words, just a normal human system. :-) The one thing I didn't see addressed was the comment requesting some notification if a service became a chronic (ab)user of the restart feature, so remedial action could be taken or requested. It should be a simple matter for the OP to put the recommended Restart=on-failure command into the service file under the [Service] section for the failing services and see what happens. -- 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: Tainted kernels
On 05/04/2015 01:23 AM, Aleksandar Kostadinov wrote: FYI if you get on oop and then another one, then kernel would show tainted by the initial oop. That makes it sometimes hard to report an issue. Yes. Two or sometimes three, all of them generally "tainted." Or, if the first one isn't, there's something else generally wrong. Next time I fire up my laptop, I'll make a note of it and report it here. In the oops reporter you can see capital letters flags about the taintedness of the kernel. There was some doc documented what each flag means. Always GW. -- 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: The spamming servers
On 04.05.2015, stan wrote: > I don't see a defense against such exploits as long as people can > install software on their systems. The alternative is Mac on steroids, > only the software that big brother approves of and allows you to use. The choice is yours. Either you stick with straight Fedora software (and blame the Fedora folks when you got infected :-) ) or you install software on your own, and take the risk. Nothing's wrong with either ways, that's what free sofware is all about. Oh, and there's no such thing as 100% security. -- 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: F21: why Fedora still has not alternative init?
Allegedly, on or about 03 May 2015, Marko Vojinovic sent: > Oooh, I see, writing buggy and ill-documented code is (ultimately) > better for the market survival of the software company! Isn't that how Microsoft made their millions? -- All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. ZNQR LBH YBBX -- 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: failed systemctl services?
On 4 May 2015 at 11:51, Matthew Miller wrote: Date sent: Mon, 4 May 2015 11:51:08 -0400 From: Matthew Miller To: Community support for Fedora users Copies to: "Michael D. Setzer II" Subject:Re: failed systemctl services? > On Mon, May 04, 2015 at 07:57:57AM -0700, stan wrote: > > > Is there a process that automatically will try to restart failed > > > systemctl services, or would it be worth creating something to do so? > > > Perhaps in cron.hourly? > > I'm no expert, but my understanding is that there is not. > > Actually, *systemd* is that process. That's one of its huge features > missing in the old init system. Take a look at the man page for > systemd.service — search for "Restart=". > As a test, just check the 20 machines in my classroom after a restart, and found that 2 of the machines had a total of 3 services that had failed after the reboot. Created a script to test restarting the failed services, and it seemed to work fine. systemctl restart `systemctl --state=failed | grep failed | cut -f 2 -d\ ` In both machine cases, the systemctl then reported everything was working. The vboxdrv issue earlier would have just failed again, since the modules would still be missing. > However, we don't configure most things that way out of the box... yet. > There was discussion about this three years ago, reopened a year ago... > > https://fedorahosted.org/fpc/ticket/191 > > and the current guidelines > > https://fedoraproject.org/wiki/Packaging:Systemd?rd=Packaging:Guidelines:Systemd#Automatic_restarting > > but as far as I know there hasn't been a big effort to bring existing > services in line. (Seems like a worthwhile project if anyone's > interested.) > > > > > > Might be these are harmless, but not sure. > > > > It doesn't seem harmless that services that the user expects to be > > started, and are configured properly, fail. > > > > It would be good if you opened a bugzilla against systemd for an RFE > > requesting such a utility. > > -- > > 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 > > -- > Matthew Miller > > Fedora Project Leader +--+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mi...@kuentos.guam.net mailto:msetze...@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +--+ http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489) BOINC@HOME CREDITS ROSETTA 28926945.864031 | SETI51036191.422589 ABC 16613838.513356 | EINSTEIN59683310.706700 -- 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: grub2
On 05/04/2015 12:01 PM, Patrick Dupre wrote: > Hello, > > There is also a tool > Super grub. > very nice! not much difference in these 2 apps, super grub was last updated May 2014.. boot-repair was updated November 2014.. http://sourceforge.net/projects/boot-repair-cd/files/ http://www.supergrubdisk.org/ -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- 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: grub2
Hello, There is also a tool Super grub. === Patrick DUPRÉ | | email: pdu...@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 === > Sent: Monday, May 04, 2015 at 2:40 PM > From: "Klaus-Peter Schrage" > To: "Community support for Fedora users" > Subject: Re: grub2 > > Am 04.05.2015 um 14:18 schrieb Paul Cartwright: > > On 05/04/2015 08:13 AM, Klaus-Peter Schrage wrote: > >>> > >> Usually, I don't have to fiddle with grub. The cases I remember were > >> when I had repaired windows installations (in a dual boot situation) > >> which refused to boot. By restoring the windows boot mechanism via the > >> rescue console, the MBR had been overwritten, and I had to re-install > >> grub to get back dual booting; and I did that in the order I had > >> mentioned: grub2-install first, then grub2-mkconfig. Perhaps the > >> reversed order might work as well in this use case, but I never tried > >> that. > > I found a very nice utility called boot-repair. I boot from that CD & it > > remakes the boot file including all bootable OSes on the drive(S). > > I have fedora booting from sdb & windows booting from sda, and I also > > had that issue when I tried to reinstall windows. > > > > http://sourceforge.net/projects/boot-repair-cd/ > > > Thank you, that looks very promising. I hope not to have to use it, but > you never know ... > -- > 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
Re: failed systemctl services?
On Mon, May 04, 2015 at 07:57:57AM -0700, stan wrote: > > Is there a process that automatically will try to restart failed > > systemctl services, or would it be worth creating something to do so? > > Perhaps in cron.hourly? > I'm no expert, but my understanding is that there is not. Actually, *systemd* is that process. That's one of its huge features missing in the old init system. Take a look at the man page for systemd.service — search for "Restart=". However, we don't configure most things that way out of the box... yet. There was discussion about this three years ago, reopened a year ago... https://fedorahosted.org/fpc/ticket/191 and the current guidelines https://fedoraproject.org/wiki/Packaging:Systemd?rd=Packaging:Guidelines:Systemd#Automatic_restarting but as far as I know there hasn't been a big effort to bring existing services in line. (Seems like a worthwhile project if anyone's interested.) > > > Might be these are harmless, but not sure. > > It doesn't seem harmless that services that the user expects to be > started, and are configured properly, fail. > > It would be good if you opened a bugzilla against systemd for an RFE > requesting such a utility. > -- > 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 -- Matthew Miller 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
Re: failed systemctl services?
On Mon, 04 May 2015 16:40:49 +1000 "Michael D. Setzer II" wrote: > I was checking on systemctl status and found some that were listed as > failed? > One was caused since the vboxdrv modules for 3.19.5 kernel were not > being installed by yum for some reason. They didn't show up in the > list, but was able to locate and manually install it to correct that > error. Sounds like a packaging error. You should probably open a bugzilla against either the kernel or vboxdrv. > The others I'm not sure of. Network-wait-online would report failed > after boot on some systems, but running a systemctl restart would fix > the issue, ended up changing the timeout from 30 to 90, and reboots > seem to result in no failures. > > On a few machines got udisks2.service failed with Cannot allocate > memory message, but a restart on that also resulted in success. This sounds like timing issues. IIRC, systemd uses threaded processing in order to speed up the boot process. Lots of opportunity for failure there: race, blocking, timing, etc. > Is there a process that automatically will try to restart failed > systemctl services, or would it be worth creating something to do so? > Perhaps in cron.hourly? I'm no expert, but my understanding is that there is not. > Might be these are harmless, but not sure. It doesn't seem harmless that services that the user expects to be started, and are configured properly, fail. It would be good if you opened a bugzilla against systemd for an RFE requesting such a utility. -- 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: The spamming servers
On Sun, 03 May 2015 12:33:43 -0600 jd1008 wrote: > Has anyone else seen this: Unnoticed for years, malware turned Linux > and BSD servers into spamming machines > > http://www.net-security.org/malware_news.php?id=3030 > freebsd-questions@freebsd.orgmailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > So I asked: > > More importantly, how do we disinfect? Reinstall the system? > But the infiltration was done to a freshly installed system. > We need to know what filenames are involved!! Perhaps I misread, but this exploit is only possible by installing an infected piece of software. A spam mailer. So, if you haven't installed the cracked or commercial version of their software, you are not infected or vulnerable to infection. The method used was ingenious. A clever someone had a lot of time on his hands. And the forensic effort that discovered and documented this was impressive. Hats off to them! I don't see a defense against such exploits as long as people can install software on their systems. The alternative is Mac on steroids, only the software that big brother approves of and allows you to use. -- 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: grub2
On Mon, 04 May 2015 08:07:44 -0400 Paul Cartwright wrote: > I'm not sure but I think doing yum update, if you get a new kernel, it > runs mkconfig. I think kernel updates run a program called grubby to update the grub.cfg file. I always run grub2-mkconfig -o grub.cfg in the /boot/grub2 directory when I install kernels. That scans the entire system and brings everything up to date. -- 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: grub2
On 05/04/2015 08:40 AM, Klaus-Peter Schrage wrote: >> >> http://sourceforge.net/projects/boot-repair-cd/ >> > Thank you, that looks very promising. I hope not to have to use it, > but you never know ... my sda drive wouldn't boot, but the partitions were still there, so I replaced sda with a new drive, a 3TB Seagate. Windows didn't like it, maybe if I had the right driver it would, but I never figured it out. I ended up copying my old windows files over to the new drive anyway, even though it wouldn't install, then I ran the boot-repair and it actually picked up the windows installation! Since I had Windows 7, windows 10 is a free upgrade, so I installed windows 10 in a VM on fedora, installed my windows apps that I need, and that is how I am using windows for now. the latest release of Windows 10 also has to new IE replacement browser called Spartan. Very much Chrome-ish.. -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- 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: F21: why Fedora still has not alternative init?
On Sun, May 03, 2015 at 02:57:57PM -0700, Gordon Messmer wrote: > I tend to think that's a better question. 2.5M of memory is > trivial, but I have systems where the RSS of systemd-journald is > 30M+ The very high variability of the memory size for that process > makes me worry about memory leaks. journald automatically scales its usage to its idea of available memory (and manages disk usage similarly — an important thing for sysadmins to be aware of). You can tune how it does this with values in /etc/systemd/journald.conf -- see the journald.conf man page for details. -- Matthew Miller 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
Re: SV: Re: F21: why Fedora still has not alternative init?
On Mon, May 04, 2015 at 01:48:57AM +0200, Frantisek Hanzlik wrote: > Hmm, I guess You want advice me, to bought some strictly limited (maybe > commercial) OS - and then shut up and be satisfied with I have. But this > fortunately is not Linux case... Fundamentally, if you want something to be different in Linux — and in Fedora — you absolutely can do it. However, you can't really tell other people that _they_ ought to do a thing. Or rather, you can, but unless you can convince them that there's value in doing the work, you won't get anywhere with that. So, while "everyone is happy with systemd" is clearly a joke, there's really a kernel of truth — it works well enough and has enough virtues that no one has seriously invested the work into building something different. If that someone is you, go for it. Until then, systemd is what we have. And, as I've noted before, going in circles complaining about it is off-topic here. If you're serious about working on packaging and integrating an alternative init system, the devel list is the place for you. If you're interested in getting or providing advice on working with Fedora as it is, this list is great. (For example, on writing systemd unit files for the services you want to manage.) -- Matthew Miller 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
Re: SV: Re: F21: why Fedora still has not alternative init?
ma., 04.05.2015 kl. 01.48 +0200, skrev Frantisek Hanzlik: > > Hmm, I guess You want advice me, to bought some strictly limited > (maybe > commercial) OS - and then shut up and be satisfied with I have. But > this > fortunately is not Linux case... That was not what I wrote at all. I gave reasons why a distro does not want to support multiple init systems as it becomes a big burden on package maintainers. If you really want a fedora with another init system you need to look at making a respin. That respin needs to provide init files for all packages that now use unit files. I still remember back when people thought sysvinit was wasteful on resources, overly complex and not the unix way compared to the single rc.local script... > Regarding cgroups/btrfs/selinux - they may be used independently of > systemd. And although I think SELinux is good thing and I use it > (regardless of systemd), things as cgroups and btrfs I never needed > (regardless of systemd). And I not want to 'play' with, I want to > foolproof system - and in my experience, systemd does not fall with > (after 4+ years of 'playing'). > You mentioned yourself that one of your reasons was a need to run multiple versions of services like sshd. one sshd for users, one for admin. How about making the one for admin run off its own read-only btrfs volume, wrapped up in cgroups and selinux? No access to the full file system at all. Only the parts relevant to sshd are present. And the only way to add new ssh keys, set passwords or whatever is from the host system. A sshd container that isn't exploitable in any way. It can only be used to initiate a new ssh into some internal system. I did that as my first ever venture into new functionality in systemd service files. It took me a few hours, documentation was good, and it worked! With even debian and ubuntu switching to systemd you have to dismiss the red hat conspiracy theories. systemd is actually a good thing in this time of container-based thinking. I do have my reservations about some of the current container implementations (like docker), but the basic principles are sound for any server. And we have to acknowledge that linux is a server OS. Systemd lets me containerize any service without setting up the whole framework for such services. I can haz full control! -- 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: grub2
Am 04.05.2015 um 14:18 schrieb Paul Cartwright: On 05/04/2015 08:13 AM, Klaus-Peter Schrage wrote: Usually, I don't have to fiddle with grub. The cases I remember were when I had repaired windows installations (in a dual boot situation) which refused to boot. By restoring the windows boot mechanism via the rescue console, the MBR had been overwritten, and I had to re-install grub to get back dual booting; and I did that in the order I had mentioned: grub2-install first, then grub2-mkconfig. Perhaps the reversed order might work as well in this use case, but I never tried that. I found a very nice utility called boot-repair. I boot from that CD & it remakes the boot file including all bootable OSes on the drive(S). I have fedora booting from sdb & windows booting from sda, and I also had that issue when I tried to reinstall windows. http://sourceforge.net/projects/boot-repair-cd/ Thank you, that looks very promising. I hope not to have to use it, but you never know ... -- 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: F21: why Fedora still has not alternative init?
On Sun, 2015-05-03 at 09:41 -0400, Tom Horsley wrote: > See "Tip 3" in: > > http://home.comcast.net/~tomhorsley/game/systemd.html While I can see that attitude in closed source software, as yet another vendor lock-in, I'm more inclined to go with a point I saw raised, elsewhere, about ADD programmers (attention deficit disorder)... When a thing doesn't work, rather than work on it, debug it, and make it better. Just reinvent the wheel, make yet another thing from scratch, and hope that it's better. Rinse, lather, repeat. Sure, as someone who does electronics engineering, I can understand situations where you look at a thing, and decide that there's just no way that you can modify it to make it good, so you do need to start over. But it really smacks of incompetence if there's a stream of things being handled in this manner, one after another. And then there's the ego of "I didn't invent it, so it's no good, and I want everyone to fawn over me, instead," attitude. I've come across programmers with huge egos, but no real surprise there. If they didn't think they were better than someone else, they wouldn't be inventing something new that does the same job as something else. The real trouble is when their /thing/ doesn't work that well, and they won't accept criticism, nor do anything to fix it off their own bat. You don't even get the cranky, "well if you're so good, tell me exactly what to change to fix it," you get the "if you don't like it, go away bulldust." (In this case, it was some closed-source Windows software I used, over a decade ago. So nobody needs to get their knickers in a twist that this was a veiled slur at anyone in particular on this list.) -- tim@localhost ~]$ uname -rsvp Linux 3.19.5-100.fc20.i686 #1 SMP Mon Apr 20 20:28:39 UTC 2015 i686 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- 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: F21: why Fedora still has not alternative init?
On Sun, 2015-05-03 at 14:04 +0200, Frantisek Hanzlik wrote: > Why hasn't Fedora alternative (upstart/openrc) init? Wasn't upstart the (ironically named) new thing that was utterly despised in Ubuntu, many years ago? -- tim@localhost ~]$ uname -rsvp Linux 3.19.5-100.fc20.i686 #1 SMP Mon Apr 20 20:28:39 UTC 2015 i686 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- 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: grub2
On 05/04/2015 08:13 AM, Klaus-Peter Schrage wrote: >> >> > Usually, I don't have to fiddle with grub. The cases I remember were > when I had repaired windows installations (in a dual boot situation) > which refused to boot. By restoring the windows boot mechanism via the > rescue console, the MBR had been overwritten, and I had to re-install > grub to get back dual booting; and I did that in the order I had > mentioned: grub2-install first, then grub2-mkconfig. Perhaps the > reversed order might work as well in this use case, but I never tried > that. I found a very nice utility called boot-repair. I boot from that CD & it remakes the boot file including all bootable OSes on the drive(S). I have fedora booting from sdb & windows booting from sda, and I also had that issue when I tried to reinstall windows. http://sourceforge.net/projects/boot-repair-cd/ -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- 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: grub2
Am 04.05.2015 um 13:19 schrieb Paul Cartwright: mmm, well if it has already been installed , why would you ever have to run grub-2-install again?? all you would have to do is modify the grub.cfg whenever you add a new kernel.. I guess the only way to test would be to add/remove a kernel, then JUST run grub2-mkconfig, reboot & see if the changes were updated.. or am I missing the point.. Usually, I don't have to fiddle with grub. The cases I remember were when I had repaired windows installations (in a dual boot situation) which refused to boot. By restoring the windows boot mechanism via the rescue console, the MBR had been overwritten, and I had to re-install grub to get back dual booting; and I did that in the order I had mentioned: grub2-install first, then grub2-mkconfig. Perhaps the reversed order might work as well in this use case, but I never tried that. -- 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: grub2
I have 3 OSes booting- WIndows, Fedora 20 & fedora 21. But I always try to default to the fedora 21 install, so I don't have to press any keys when it boots. so running mkconfig always picks up the latest version & kernels from all installs.. but I only run it from fedora 21. I'm not sure but I think doing yum update, if you get a new kernel, it runs mkconfig. > You may avoid to do it. > But I have a multiboot system. > I may have to manage which grub.cfg file needs to be read when booting. > grub-install let me do it. > > === > Patrick DUPRÉ | | email: pdu...@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 > === > > >> Sent: Monday, May 04, 2015 at 1:19 PM >> From: "Paul Cartwright" >> To: users@lists.fedoraproject.org >> Subject: Re: grub2 >> >> mmm, well if it has already been installed , why would you ever have to >> run grub-2-install again?? all you would have to do is modify the >> grub.cfg whenever you add a new kernel.. I guess the only way to test >> would be to add/remove a kernel, then JUST run grub2-mkconfig, reboot & >> see if the changes were updated.. >> or am I missing the point.. >> >>> Hello, >>> >>> In my opinion, it odes not matter. >>> after grub-install /dev/sda >>> grub knows that it has to read the file >>> /boot/grub2/grub.cfg >>> Then you can change it, it will use the chnaged file. >>> There is no copy of the copy in /dev/sdx >>> >>> >>> === >>> Patrick DUPRÉ | | email: pdu...@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 >>> === >>> >>> Sent: Monday, May 04, 2015 at 11:07 AM From: "Klaus-Peter Schrage" To: users@lists.fedoraproject.org Subject: Re: grub2 Am 03.05.2015 um 20:42 schrieb Paul Cartwright: > On 05/03/2015 11:02 AM, Klaus-Peter Schrage wrote: >> Am 03.05.2015 um 15:59 schrieb Patrick Dupre: >>> Hello, >>> >>> After I run >>> grub2-mkconfig -o /boot/grub2/grub.cfg >>> grub2-install /dev/sda >> First thought: Shouldn't these two commands be interchanged? > no, you run the mkconfig FIRST, then install it in /dev/sda .. > > I am a bit stumbled: I always thought that it is a good idea to install a feature before configuring it ... Following Fedora's Grub2 documentation, I did it this way for quite a long time whenever I needed to update my grub configuration: "The configuration format has evolved over time, and a new configuration file might be slightly incompatible with the old bootloader. It is thus often/always a good idea to run grub2-install before grub2-mkconfig for some reason is run." But, I admit, in most situations the order of the two command may not matter. -- 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 >> >> -- >> Paul Cartwright >> Registered Linux User #367800 and new counter #561587 >> >> -- >> 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 >> > -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- 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: grub2
You may avoid to do it. But I have a multiboot system. I may have to manage which grub.cfg file needs to be read when booting. grub-install let me do it. === Patrick DUPRÉ | | email: pdu...@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 === > Sent: Monday, May 04, 2015 at 1:19 PM > From: "Paul Cartwright" > To: users@lists.fedoraproject.org > Subject: Re: grub2 > > mmm, well if it has already been installed , why would you ever have to > run grub-2-install again?? all you would have to do is modify the > grub.cfg whenever you add a new kernel.. I guess the only way to test > would be to add/remove a kernel, then JUST run grub2-mkconfig, reboot & > see if the changes were updated.. > or am I missing the point.. > > > Hello, > > > > In my opinion, it odes not matter. > > after grub-install /dev/sda > > grub knows that it has to read the file > > /boot/grub2/grub.cfg > > Then you can change it, it will use the chnaged file. > > There is no copy of the copy in /dev/sdx > > > > > > === > > Patrick DUPRÉ | | email: pdu...@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 > > === > > > > > >> Sent: Monday, May 04, 2015 at 11:07 AM > >> From: "Klaus-Peter Schrage" > >> To: users@lists.fedoraproject.org > >> Subject: Re: grub2 > >> > >> Am 03.05.2015 um 20:42 schrieb Paul Cartwright: > >>> On 05/03/2015 11:02 AM, Klaus-Peter Schrage wrote: > Am 03.05.2015 um 15:59 schrieb Patrick Dupre: > > Hello, > > > > After I run > > grub2-mkconfig -o /boot/grub2/grub.cfg > > grub2-install /dev/sda > First thought: Shouldn't these two commands be interchanged? > >>> no, you run the mkconfig FIRST, then install it in /dev/sda .. > >>> > >>> > >> I am a bit stumbled: I always thought that it is a good idea to install > >> a feature before configuring it ... Following Fedora's Grub2 > >> documentation, I did it this way for quite a long time whenever I needed > >> to update my grub configuration: > >> "The configuration format has evolved over time, and a new configuration > >> file might be slightly incompatible with the old bootloader. It is thus > >> often/always a good idea to run grub2-install before grub2-mkconfig for > >> some reason is run." > >> But, I admit, in most situations the order of the two command may not > >> matter. > >> -- > >> 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 > >> > > > -- > Paul Cartwright > Registered Linux User #367800 and new counter #561587 > > -- > 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
Re: /var/lib/mlocate/mlocate.db perms
On Sun, 2015-05-03 at 17:47 -0600, jd1008 wrote: > > [egreshko@meimei ~]$ ll /bin/locate > > -rwx--s--x. 1 root slocate 40528 Aug 18 2014 /bin/locate > I distrust suid programs. > I find it strange that a security minded system needs an suid > program to do something as simple as locate a file. To locate the file it needs to be able to read the directory tree. poc -- 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: grub2
mmm, well if it has already been installed , why would you ever have to run grub-2-install again?? all you would have to do is modify the grub.cfg whenever you add a new kernel.. I guess the only way to test would be to add/remove a kernel, then JUST run grub2-mkconfig, reboot & see if the changes were updated.. or am I missing the point.. > Hello, > > In my opinion, it odes not matter. > after grub-install /dev/sda > grub knows that it has to read the file > /boot/grub2/grub.cfg > Then you can change it, it will use the chnaged file. > There is no copy of the copy in /dev/sdx > > > === > Patrick DUPRÉ | | email: pdu...@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 > === > > >> Sent: Monday, May 04, 2015 at 11:07 AM >> From: "Klaus-Peter Schrage" >> To: users@lists.fedoraproject.org >> Subject: Re: grub2 >> >> Am 03.05.2015 um 20:42 schrieb Paul Cartwright: >>> On 05/03/2015 11:02 AM, Klaus-Peter Schrage wrote: Am 03.05.2015 um 15:59 schrieb Patrick Dupre: > Hello, > > After I run > grub2-mkconfig -o /boot/grub2/grub.cfg > grub2-install /dev/sda First thought: Shouldn't these two commands be interchanged? >>> no, you run the mkconfig FIRST, then install it in /dev/sda .. >>> >>> >> I am a bit stumbled: I always thought that it is a good idea to install >> a feature before configuring it ... Following Fedora's Grub2 >> documentation, I did it this way for quite a long time whenever I needed >> to update my grub configuration: >> "The configuration format has evolved over time, and a new configuration >> file might be slightly incompatible with the old bootloader. It is thus >> often/always a good idea to run grub2-install before grub2-mkconfig for >> some reason is run." >> But, I admit, in most situations the order of the two command may not >> matter. >> -- >> 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 >> -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- 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: grub2
Hello, In my opinion, it odes not matter. after grub-install /dev/sda grub knows that it has to read the file /boot/grub2/grub.cfg Then you can change it, it will use the chnaged file. There is no copy of the copy in /dev/sdx === Patrick DUPRÉ | | email: pdu...@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 === > Sent: Monday, May 04, 2015 at 11:07 AM > From: "Klaus-Peter Schrage" > To: users@lists.fedoraproject.org > Subject: Re: grub2 > > Am 03.05.2015 um 20:42 schrieb Paul Cartwright: > > On 05/03/2015 11:02 AM, Klaus-Peter Schrage wrote: > >> Am 03.05.2015 um 15:59 schrieb Patrick Dupre: > >>> Hello, > >>> > >>> After I run > >>> grub2-mkconfig -o /boot/grub2/grub.cfg > >>> grub2-install /dev/sda > >> First thought: Shouldn't these two commands be interchanged? > > no, you run the mkconfig FIRST, then install it in /dev/sda .. > > > > > > I am a bit stumbled: I always thought that it is a good idea to install > a feature before configuring it ... Following Fedora's Grub2 > documentation, I did it this way for quite a long time whenever I needed > to update my grub configuration: > "The configuration format has evolved over time, and a new configuration > file might be slightly incompatible with the old bootloader. It is thus > often/always a good idea to run grub2-install before grub2-mkconfig for > some reason is run." > But, I admit, in most situations the order of the two command may not > matter. > -- > 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
Re: grub2
Am 03.05.2015 um 20:42 schrieb Paul Cartwright: On 05/03/2015 11:02 AM, Klaus-Peter Schrage wrote: Am 03.05.2015 um 15:59 schrieb Patrick Dupre: Hello, After I run grub2-mkconfig -o /boot/grub2/grub.cfg grub2-install /dev/sda First thought: Shouldn't these two commands be interchanged? no, you run the mkconfig FIRST, then install it in /dev/sda .. I am a bit stumbled: I always thought that it is a good idea to install a feature before configuring it ... Following Fedora's Grub2 documentation, I did it this way for quite a long time whenever I needed to update my grub configuration: "The configuration format has evolved over time, and a new configuration file might be slightly incompatible with the old bootloader. It is thus often/always a good idea to run grub2-install before grub2-mkconfig for some reason is run." But, I admit, in most situations the order of the two command may not matter. -- 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: Tainted kernels
FYI if you get on oop and then another one, then kernel would show tainted by the initial oop. That makes it sometimes hard to report an issue. In the oops reporter you can see capital letters flags about the taintedness of the kernel. There was some doc documented what each flag means. Joe Zeff wrote on 04/28/2015 10:53 PM: Earlier, I'd asked about what was causing abrt to claim that my laptop's kernel was tainted, even though I don't know of anything that would cause this. Somebody asked me to check a certain location in /proc, which turned out not to exist on the laptop. I'd like to check again, and check it on my desktop as well because I know the desktop's kernel is tainted by kmod-nvidia, and that would give me a good way to compare a known-tainted kernel with my laptop's. Alas, I've lost the email with the pointer in it. If anybody remembers what I'm supposed to check, please let me know. Thanx! -- 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
