How to create a single 4GB large ramdisk?
by Clemens Eisserer
Hi,
I need a single ramdisk which is a real block device (unlike tmpfs),
so I found the ramdisk_size kernel boot parameter.
However, after invoking "MAKEDEV ram" I get hundreds of 16mb large
ramdisks, instead of a single 4GB large:
dd if=/dev/zero of=/dev/ram0 bs=1024k count=2048
dd: error writing ‘/dev/ram0’: No space left on device
17+0 records in
16+0 records out
16777216 bytes (17 MB) copied, 0.032487 s, 516 MB/s
Any idea how to get a single ramdisk instead, I am using Fedora20 on x86_64 btw.
Thank you in advance, Clemens
10 years
5tFTw: F21 on Track, FESCo Membership Change, More DNF vs. Yum, Reading VM Logs, and Wiki Infoboxes (2014-06-17)
by Matthew Miller
Reposted from <http://fedoramagazine.org/5tftw-2014-06-17/>.
Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn’t comprehensive news coverage — just quick summaries with links
to each. Here are the five things for June 17th, 2014:
Fedora 21 Is Not Delayed
------------------------
It might seem a bit funny to report on something that’s *not*
happening, but this got picked up by some of the tech press so I
thought it best to clarify the actual situation. Short version: we’re
*not* currently planning any delay from the established target of
October 14th, 2014.
Longer version: the Fedora Server Working Group is writing new code
which will provide a programmatic interface (an API) for provisioning
servers with certain Server Roles. This doesn’t compete with existing
config management tools like Puppet, Chef, or Ansible — it provides a
framework that they (or the new Cockpit web GUI) can talk to. That’s
taking a little bit longer than planned, especially because new input
from the CentOS Simple Linux Server SIG was incorporated. However, at
last week’s meeting, FESCo (the Fedora Engineering Steering Committee,
which manages the overall schedule) decided to allow *just* this Server
Role Deployment Framework]framework] to land a little late in the
Fedora Alpha schedule, but with no delay to the rest of the project or
change to the overall F21 schedule.
* http://fedoraproject.org/wiki/Server
* http://fedoraserver-wgblog.rhcloud.com/primary-goals-for-fedora-server-in...
* https://fedoraproject.org/wiki/Changes/FrameworkForServerRoleDeployment
* http://cockpit-project.org/
* http://wiki.centos.org/SpecialInterestGroup/SLS
* http://meetbot.fedoraproject.org/fedora-meeting/2014-06-11/fesco.2014-06-...
Bill Nottingham Steps Down From FESCo; Kyle McMartin Steps Up
-------------------------------------------------------------
Long-time and almost omnipresent Fedora contributor Bill Nottingham
has started a new day job at open source config-management company
Ansible, and resigned his Fedora Engineering Steering Committee
seat in order to be able to focus on that. Our election policy
states that open seats are offered to previous runners-up, which
means Kyle McMartin is our newest FESCo member (although not, by
any means new to Fedora). Thank you Bill for years of work on
Fedora in FESCo and elsewhere, and welcome Kyle!
P.S. We use Ansible quite heavily in Fedora Infrastructure. Also:
Former Fedora Project Leader Greg DeKoenigsberg is also joining
Ansible, which already boasts quite the slate of former Red Hatters and
Fedora contributors. I’m looking forward to further collaboration
across our open source projects.
* http://fedoraproject.org/wiki/User:Notting
* https://twitter.com/ansible/status/478518891665432576
* http://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations#K...
* http://www.slideshare.net/AdityaPatawari/ansible-33223245
* http://www.ansible.com/management-team
DNF as Yum Replacement, Continued
---------------------------------
Last week, I wrote about a proposal to replace Fedora’s Yum package
manager with DNF. That proposal — targeting next year’s Fedora 22,
_not_ Fedora 21 this fall — is now officially on the table for
discussion. That discussion continues on the Fedora devel mailing list.
Although there are several long threads, it looks like people are
generally open to the idea and advantages of the new code, but there
are differing opinions on whether DNF should keep that name or become
“Yum 4” — or even take a new generic name like `package`. Feel free to
join in, although please remember to be constructive and to follow the
Fedora Project Code of Conduct (which, basically, boils down to “be
excellent to each other”.
* http://fedoramagazine.org/5tftw-2014-06-10/
* http://yum.baseurl.org/
* http://dnf.baseurl.org/
* https://fedorahosted.org/fesco/ticket/1312
* https://lists.fedoraproject.org/pipermail/devel/2014-June/thread.html
* https://fedoraproject.org/code-of-conduct
Coming Soon to libguestfs: Smart Log Reading
--------------------------------------------
The systemd journal brings a lot of useful features, including
structured log formats and reliable connection of messages to the
services they came from. But, its binary log format can be less
convenient when you’re not working *on* the system where the logs
reside.
This is often the case when using libguestfs, an almost-magically-
powerful tool for working with virtual machine disk images. Developer
Richard W.M. Jones blogs about a new feature: virt-log. This command
automatically does the right thing with several different guest system
log possibilities, including understanding the journald format, knowing
that Debian-based systems use `/var/log/syslog` instead of our
`/var/log/messages`, and in the future will even read the Microsoft
Windows Event Log.
* http://0pointer.de/blog/projects/journalctl.html
* http://libguestfs.org/
* http://rwmj.wordpress.com/2014/06/14/new-in-libguestfs-virt-log/
Add an Infobox to Your Fedora Wiki User Page
--------------------------------------------
Our wiki serves many purposes (maybe too many!), but one of the the
most useful is providing simple autobiographical and contact
information for contributors. A neat little thing I stumbled across
this week is the Infobox template, defined and documented at
<https://fedoraproject.org/wiki/Template:Infobox_user>. Follow these
instructions and add the template to your page for a clean, consistent
presentation of your Fedora-relevant details.
As a bonus, display your Fedora Badges with `{{ #fedorabadges: fasname }}`
* https://fedoraproject.org/wiki/Template:Infobox_user
* https://badges.fedoraproject.org/
* http://fedoramagazine.org/wp-content/uploads/2014/06/badges.png
* https://badges.fedoraproject.org/user/mattdm
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
10 years
Error while updating system
by Someone
I ran "sudo yum update -y" a few days ago, as I often do, and I saw the
following error:
Error: Package:
kmod-VirtualBox-3.14.6-200.fc20.x86_64-4.3.12-1.fc20.2.x86_64
(rpmfusion-free-updates)
Requires: kernel-uname-r = 3.14.6-200.fc20.x86_64
Installed: kernel-3.14.4-200.fc20.x86_64 (@updates)
kernel-uname-r = 3.14.4-200.fc20.x86_64
Installed: kernel-3.14.5-200.fc20.x86_64 (@updates)
kernel-uname-r = 3.14.5-200.fc20.x86_64
Installed: kernel-3.14.7-200.fc20.x86_64 (@updates)
kernel-uname-r = 3.14.7-200.fc20.x86_64
Available: kernel-3.11.10-301.fc20.x86_64 (fedora)
kernel-uname-r = 3.11.10-301.fc20.x86_64
Available: kernel-debug-3.11.10-301.fc20.x86_64 (fedora)
kernel-uname-r = 3.11.10-301.fc20.x86_64+debug
Available: kernel-debug-3.14.7-200.fc20.x86_64 (updates)
kernel-uname-r = 3.14.7-200.fc20.x86_64+debug
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
So I ran "sudo yum update -y --skip-broken", as suggested, and the
update completed without incident. Then I left my machine alone for a
few days, and came back to it figuring that I should run another update,
so I did, and I received the same error. Does this indicate that
anything worrisome is wrong? And, regardless, is there anything I could
do to rectify the issue so that I don't keep having to run yum update
commands with the --skip-broken option?
Thanks
10 years
Selinux Packaging [WAS: Wifi connection issues with Intel?]
by Richard Shaw
On Mon, Jun 16, 2014 at 1:08 PM, Daniel J Walsh <dwalsh(a)redhat.com> wrote:
>
> On 06/16/2014 01:35 PM, Richard Shaw wrote:
>
> On Mon, Jun 16, 2014 at 12:19 PM, Daniel J Walsh <dwalsh(a)redhat.com>
> wrote:
>
>>
>> On 06/12/2014 10:14 AM, Richard Shaw wrote:
>>
>> On Thu, Jun 12, 2014 at 6:56 AM, Daniel J Walsh <dwalsh(a)redhat.com>
>> wrote:
>>
>>> The full unifi software is java with a mongodb database backend and
>>> works fine. I have a RPM I created, the only problem I haven't been able to
>>> fix is the selinux issues, one for the private mongodb instance, and then
>>> the ports it binds to.
>>>
>>> Please open a bugzilla for the SELinux issues.
>>>
>>
>> Before I open a BZ, here's what I have in my spec file which from what
>> I understand should be persistent...
>>
>> %posttrans
>> /usr/sbin/semanage fcontext -e /var/lib/mongod "/var/lib/unifi/logs(/.*)?"
>> /usr/sbin/semanage fcontext -e /var/lib/mongod "/var/lib/unifi/data(/.*)?"
>> /usr/sbin/semanage port -m -t mongod_port_t 27117
>>
>> Or should this be handled in a policy?
>>
>> Thanks,
>> Richard
>>
>>
>> I think your post install should look like.
>>
>> /usr/sbin/semanage fcontext -e /var/log/mongod "/var/lib/unifi/logs"
>> /usr/sbin/semanage fcontext -e /var/lib/mongod "/var/lib/unifi/data"
>> /usr/sbin/semanage port -m -t mongod_port_t 27117
>>
>> Don't use the regex. Also I would figure the logs should be labeled
>> mongod_log_t rather then mongod_lib_t.
>>
>
> What is the concern with regex?
>
>
> It is specific to packaging? Most of the examples I found online used
> that method... As far as the label, since everything is getting dumped in
> /var/lib I figured that would be OK.
>
>
> Not a concern with regex. it just will not work. The examples you have
> seen on line, were not using equivalence. They were using generic
> labelling.
>
> Equivalence tells SELinux to swap the second part of the path with the
> first. You code would only match file paths that began with
> /var/lib/unifi/logs(/.*?) Not /var/lib/unifi/logs/foobar.log
>
>
> If this is a standard location for this code, we should put it into the
>> base package.
>>
>
> There is not a standard install location, the install will "work" as
> long as everything stays in the same relative location (the unifi
> directory). Since it writes a lot of stuff I figured /var was the best
> (only?) real option.
>
> Yes
>
> Following the example of a draft wiki I can't find anymore I had
> modified the scripts to this instead of using %posttrans:
> %post
> semanage fcontext -a -t mongod_var_lib_t \
> "%{_sharedstatedir}/unifi/logs(/.*)?" 2>/dev/null || :
> semanage fcontext -a -t mongod_var_lib_t \
> "%{_sharedstatedir}/unifi/data(/.*)?" 2>/dev/null || :
> restorecon -R %{_sharedstatedir}/unifi/logs || :
> restorecon -R %{_sharedstatedir}/unifi/data || :
> semanage port -m -t mongod_port_t 27117 || :
>
> %postun
> if [ $1 -eq 0 ] ; then # final removal
> semanage fcontext -d -t mongod_var_lib_t \
> "%{_sharedstatedir}/unifi/logs(/.*)?" 2>/dev/null || :
> semanage fcontext -d -t mongod_var_lib_t \
> "%{_sharedstatedir}/unifi/data(/.*)?" 2>/dev/null || :
> fi
>
>
> That should work. You could speed it up by combining both semange
> fcontext lines into a single transaction. Something like.
>
> semanage -S targeted -i - << _EOF
>
> fcontext -a -t mongod_var_lib_t "%{_sharedstatedir}/unifi/logs(/.*)?"
> fcontext -a -t mongod_var_lib_t "%{_sharedstatedir}/unifi/data(/.*)?"
> _EOF 2>/dev/null || :
>
Ok, just to be clear, I still need to remove the (/.*)? parts? I found the
packaging draft I referred to:
http://fedoraproject.org/wiki/PackagingDrafts/SELinux
Which shows including it.
Thanks,
Richard
10 years
problems with a high res display
by Dave Bremer
I have a Dell M4800 with a 3200x1800 display, an nVidia Quadro 2100M,
and Fedora 20. It was working very well. But after installing
updates today, the gnome display manager cannot start. Anyone know of
a fix?
10 years
Wifi connection issues with Intel?
by Richard Shaw
I looked though the last update and nothing jumped out at me... Tried
journalctl --this-boot and paged through it, nothing jumped out at me.
I've also tried all 3 installed kernels with the same result: Flakey
wireless
When I bring up the connection details (which takes to many clicks/menus) I
see connection speeds of 1, 18, 24, or 54Mbit but this is a n device and
has connected reliably at 108Mbit before now and the AP is less than 20
feet away.
Sometimes connections get stuck at "resolving host" and other times it
works.
Anyone seeing the same issue?
Thanks,
Richard
10 years
Firefox 30 and NTLM auth
by Dario Lesca
After last firefox update the NTLM auth do not work anymore.
I have download the previous version of FF from Fedora old repo
(firefox-29.0.1-1.fc20.x86_64.rpm) and install it: NTLM auth work.
(NOTE: "yum downgrade firefox" do not work with this error)
> Resolving Dependencies
> --> Running transaction check
> ---> Package firefox.x86_64 0:25.0-3.fc20 will be a downgrade
> --> Processing Dependency: libxul.so(xul25.0)(64bit) for package: firefox-25.0-3.fc20.x86_64
> ---> Package firefox.x86_64 0:30.0-4.fc20 will be erased
> --> Processing Conflict: firefox-25.0-3.fc20.x86_64 conflicts xulrunner(x86-64) > 25.1
> --> Finished Dependency Resolution
> Error: firefox conflicts with xulrunner-30.0-1.fc20.x86_64
I have also download FF from FF web site and the problem is the same:
FF30 do not work, FF 29 work.
Some suggest ?
Thanks
--
Dario Lesca
(inviato dal mio Linux Fedora 20 con Gnome 3.10.4)
10 years
dnf v.s. yum
by Ed Greshko
OK.... I read FAQ.....
http://akozumpl.github.io/dnf/user_faq.html#why-do-i-get-different-result...
And the one following it.... "Is it possible to force DNF to get the latest metadata on dnf upgrade?"
Running KDE and the notifications in the systray showed there are 12 updates available. Figured I give dnf a try, which I've done from time to time, but it showed no packages to update. OK....so clean metadata for both yum and dnf....
ran both "yum check-update" and "dnf check-update".
yum listed the 12
[root@meimei ~]# dnf check-update
google-earth 74 kB/s | 4.8 kB 00:00
Fedora 20 - x86_64 - VirtualBox 38 kB/s | 44 kB 00:01
Fedora 20 - x86_64 2.2 MB/s | 36 MB 00:15
RPM Fusion for Fedora 20 - Free - Updates 241 kB/s | 346 kB 00:01
Adobe Systems Incorporated 2.7 kB/s | 1.8 kB 00:00
RPM Fusion for Fedora 20 - Nonfree - Updates 116 kB/s | 100 kB 00:00
RPM Fusion for Fedora 20 - Free 325 kB/s | 487 kB 00:01
Fedora 20 - x86_64 - Updates 2.0 MB/s | 23 MB 00:11
RPM Fusion for Fedora 20 - Nonfree 19 kB/s | 289 kB 00:15
[root@meimei ~]#
--
Do not condemn the judgment of another because it differs from your own. You may both be wrong. -- Dandemis
10 years
pulseaudio - pactl parse volume
by poma
- pactl v4 - fc20:
pactl parse_volume() cannot read negatives
https://bugs.freedesktop.org/show_bug.cgi?id=77108
$ rpm -qf /usr/bin/pactl
pulseaudio-utils-4.0-13.gitf81e3.fc20.x86_64
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 39315 / 60% / -13.32 dB, front-right: 39315 / 60% / -13.32 dB
$ pactl set-sink-volume 0 +10%
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 45868 / 70% / -9.30 dB, front-right: 45868 / 70% / -9.30 dB
$ pactl set-sink-volume 0 -10%
pactl: invalid option -- '1'
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 45868 / 70% / -9.30 dB, front-right: 45868 / 70% / -9.30 dB
pactl: Stop parsing option when the first non-option is encountered
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=997e369
...
error: Installed (but unpackaged) file(s) found:
/usr/lib64/pulse-4.0/modules/module-xenpv-sink.so
RPM build errors:
Installed (but unpackaged) file(s) found:
/usr/lib64/pulse-4.0/modules/module-xenpv-sink.so
$ rpm -qf /usr/bin/pactl
pulseaudio-utils-4.0-15.gitf81e3.fc20.x86_64
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 45868 / 70% / -9.30 dB, front-right: 45868 / 70% / -9.30 dB
$ pactl set-sink-volume 0 +10%
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 52421 / 80% / -5.82 dB, front-right: 52421 / 80% / -5.82 dB
$ pactl set-sink-volume 0 -10%
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 45867 / 70% / -9.30 dB, front-right: 45867 / 70% / -9.30 dB
~~~~~~~~~~~~~~~~~~
- pactl v5 - fc21:
pactl parse_volume() cannot read negatives
https://bugs.freedesktop.org/show_bug.cgi?id=77108
$ rpm -qf /usr/bin/pactl
pulseaudio-utils-5.0-5.fc21.x86_64
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 36041 / 55% / -15.58 dB, front-right: 36041 / 55% / -15.58 dB
$ pactl set-sink-volume 0 +10%
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 42594 / 65% / -11.23 dB, front-right: 42594 / 65% / -11.23 dB
$ pactl set-sink-volume 0 -10%
pactl: invalid option -- '1'
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 42594 / 65% / -11.23 dB, front-right: 42594 / 65% / -11.23 dB
pactl: Stop parsing option when the first non-option is encountered
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=997e369
$ rpm -qf /usr/bin/pactl
pulseaudio-utils-5.0-7.fc21.x86_64
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 42594 / 65% / -11.23 dB, front-right: 42594 / 65% / -11.23 dB
$ pactl set-sink-volume 0 +10%
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 49147 / 75% / -7.50 dB, front-right: 49147 / 75% / -7.50 dB
$ pactl set-sink-volume 0 -10%
$ pactl list sinks | grep Volume:\ front
Volume: front-left: 42593 / 65% / -11.23 dB, front-right: 42593 / 65% / -11.23 dB
poma
10 years
Re: DNF utils package?
by poma
There is DNF builddep Plugin
http://akozumpl.github.io/dnf-plugins-core/builddep.html
however it is not the same as yum-builddep.
# yum-builddep pulseaudio
...
Getting requirements for pulseaudio-4.0-13.gitf81e3.fc20.src
--> Already installed : ...
...
No uninstalled build requires
# dnf builddep pulseaudio
Config time: 0.008
cachedir: /var/cache/dnf/x86_64/20
Loaded plugins: debuginfo-install, generate_completion_cache, copr, playground, download, kickstart, noroot, builddep
initialized DebuginfoInstall plugin
initialized Copr plugin
initialized Playground plugin
initialized Noroot plugin
initialized BuildDep plugin
dnf version: 0.5.2
Command: dnf builddep pulseaudio
Installroot: /
Base command: builddep
Extra commands: [u'pulseaudio']
hawkey sack setup time: 0.023
Error: Failed to open: 'pulseaudio', not a valid spec file.
Cleaning up.
yum can work without "actual" local files i.e. yum will find them for us which is super huge!
Long live the yum!
poma
10 years
