tried to safely bring down a crashed Fedora 21 machine today, but M-sysrq
didn't do anything. After bringing the machine up again, the logs showed
that M-sysrq functionality was disabled. After investigating further, it seemed
that only Sysrq-S (emergency save) was actually working. In /etc/sysctl.d/01-sysctl.conf,
"kernel.sysrq=1" was present. It took me nearly 30 min. to find out that systemd
has it's own sysctl definitions, gladly ignoring/overwriting /etc/sysctl.d. In
/usr/lib/sysctl.d/50-default.conf, "kernel.sysrq=16" was set, which is what crippled
full sysrq functionality.
In addition, I'm curious what happens when the next systemd update gets pulled in.
Most probably, my manual settings will be overwritten with what systemd thinks
is good for the user..
1. Anaconda changes X in sdaX. If you make a choice on order of /boot, swap,
and / partitions, Anaconda changes the order. As long as layout is valid why
does Anaconda has to change it.
2. 4 primary partitions are allowed on a disk. If I do that Anaconda changes
it to 3 primary and 1 logical partition. Why?
3. There is no option to create a partition and leave it for future use. How
do I create a partition and not have to use it immediately.
5577 8CDB A059 085D 1D60 807F 8C00 45D9 F5EF C394.
Firefox has three different possibilities in Edit -> Preferences -> General
to chose from what should happen when Firefox starts:
1. Show my homepage
2. Show a blank page
3. Show my windows and tabs from last time
When using 3., for a short time the "default home page" (start.fedoraproject.org) loads,
disappears and my tabs from last time get loaded. The same happens when I previously closed
Firefox with nothing opened: the default home pages flashes up, followed by a blank screen.
This didn't happen before, and the behaviour is f*** annoying. Tried to user-set browser.startup.homepage
without any effect, the default homepage came automagically back.
Can anybody see the same phenomenon? Does anybody know when this has been introduced?
On 01/30/2015 11:47 AM, Terry Polzin wrote:
> On Fri, 2015-01-30 at 10:53 -0500, Paul Cartwright wrote:
>> I finally let the boot sequence error out, took about 5 minutes. I got
>> this line:
>> Dracut-initqueue Warning: Cancelling resume operation. device not
>> then the next line showed the UUID, ending in c063. That was the OLD
>> swap partition. I rebuilt the swap partition, did the swapon, and added
>> that UUID to /etc/fstab. Still errored out with same error. I removed
>> the 3.18.3-201 kernel & headers & module, reinstalled them, and now it
>> works. where is that old swap info kept, if not in /etc/fstab?? I
>> grepped for c063 in /boot and found entries in System.map-3.18.3-201...
>> but I am not sure it was the actual swap partition.
>>> running fedora 21 x86_64
>>> I was redoing my drive partitions, reran grub2-install, and now I get
>>> stuck, and the boot won't complete when I select any 3.17 or 3.18
>>> kernel. I have the latest 3.18.3-201 installed. 3.16 kernel booted..
>>> I see what looks like dracut errors. Not sure what to do, google wasn't
>>> much help.
>>> /var/log/messages shows:
>>> Jan 29 03:00:05 pauls-server systemd: Started dracut pre-mount hook.
>>> Jan 29 03:00:05 pauls-server systemd: Started dracut mount hook.
>>> Jan 29 03:00:05 pauls-server systemd: Starting dracut pre-pivot and
>>> cleanup hook...
>>> Jan 29 03:00:05 pauls-server systemd: Started dracut pre-pivot and
>>> cleanup hook.
>>> Jan 29 03:00:05 pauls-server systemd: Stopping dracut pre-pivot and
>>> cleanup hook...
>>> not very descriptive.. suggestions on where to look or what is wrong?
>>> right now I am booted into fedora 20, using the same /home.. it's just
>>> that not everything works..
>>> uname -a
>>> Linux pauls-server 3.16.7-200.fc20.x86_64 #1 SMP Thu Oct 30 18:12:41 UTC
>>> 2014 x86_64 x86_64 x86_64 GNU/Linux
>> Paul Cartwright
>> Registered Linux User #367800 and new counter #561587
> Isn't it buried someplace in the /boot/grub2/grub.cfg file? That's why
> reinstall of the kernel fixed it.
I looked in grub.cfg didn't find it..
Registered Linux User #367800 and new counter #561587
I have an Alienware 17-1 laptop that I would like to run Fedora linux
on. The laptop has 2TB of disk, 32GB of ram and NVIDIA GeForce GTX 880M
graphics, so I thought it would make a great development platform. I
inserted the Fedora live DVD and booted. It asked If I wanted to check
the disk, which I did. Next I started Fedora. It got to the point where
the fedora logo is on the screen, and then disappeared. The fans came
on, so I assumed it was doing something, but after about 5 minutes the
system appeared to be still in the same state.
In the past there has been an install image that is about 4.3GB large
that guides the installation. I cannot find an similar image for F21. I
have been away for awhile, so if this is well known please forgive me. I
looked at the documentation and did not see any mention.
Will Fedora work on an Alienware laptop? I though the since it was Dell
it should. If so, what is the best way to load Fedora onto it? Is the
fact that the live DVD failed telling me I am out of luck?
| Don Fisher hdf3(a)comcast.net |
| 865 W. Cresta Loma Dr. VOICE: (520)888-7613 |
| Tucson, AZ. 85704-3705 |
Many years ago I built a server on Fedora 8 which became my core network
server running all the network servers (DNS etc) as well as a host of custom
services over inetd, However it's main purpose was to service Samba shares.
That server is now failing so I've just spent a week building a new F20 server
and converting everything from F8 to F20 - amazing number of changes needed
but also an amazing number of things are still the same.
Last of the things to move because the old server is still live and serving is
SAMBA. This is where I need the help.
All of my servers run the same type of setup and it's all based
around "security = share". Why is this so universally declared as bad??
I know when I built some F16 servers it said that "security = share" was
depreciated but it still let me use it. Now with F20 it just refuses.
The problem is that security = share did *exactly* what I wanted and now I
can't seem to achieve the same effect any other way.
Very simply, I use the [homes] section and have about 10 users defined on the
server - service, parts, admin etc.
Then for each user PC (approx 120 - 150) I then map a network drive to each
service that is required. Many only have one or two but some people such as
admin have access to sales, accounts, wages and admin.
All very simple and faultless for 8 years.
Now, when I try some of the examples found online, client PCs seem to be able
to connect to the first share ok but then whenever I try to connect a second
share it complains about having to log out of the first share first.
Can anyone please help me here. If I can't get it working I'll have to scrap
my week's work and install F16 on this box.
Lukáš 'Allo 'Allo
I see that some people are trying to "modernize" Fedora.
But what about RHEL relictum - initscripts, particularly now that we have NetworkManager/ModemManager and systemd-networkd,
when will this package "fall off"?
Every time I use abrt to try to report a problem, it crashes with an
error in libreport. Unfortunately, I can't report that because
attempting to do so crashes abrt.
Is it just me or are others seeing this problem?
Fedora 15 Hard drive. ext4
# e2fsck -b 8193 /dev/sdb
e2fsck 1.42.8 (20-Jun-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
What command should I use to overcome this ?
I'm using Fedora 20 to check the hard drive.
I just realized that my wireless computers can't ping each other.
Wireless to wired and vice versa is just fine. The IP addresses (DHCP)
are all on the same subnet. If I switch to wired the computer can then
ping a wired or wireless. The computers can all access the Internet at
any time (either wired or wireless). I did some research and have
determined the problem might be my router.
I use a LinkSys E3000 which I have had for a very long time. I checked
their site and looked at the Release Notes for firmware upgrades. No
mention of this issue and so I am hesitant to perform it (I did however
download the latest file). I got into their Live Chat and the guy said
since the unit is no longer in warranty I would have to pay to get
assistance. I thought about doing this, but he could not guarantee
success and the payment is not refundable. I thought that sucked and
told him so.
So, does anyone have any ideas about how I might solve this? I am going
to be rather surprised if the problem is not the router. If it matters
here is my hardware:
Fedora 14 - wired desktop
Fedora 20 - wireless laptop
Fedora 21 - wireless laptop (or wired)
Fedora 21 - wireless laptop (or wired)
Ubuntu 12.04.2 LTS - wireless (practically unusable because of Gnome 3)