http://bugzilla.opensuse.org/show_bug.cgi?id=1073809http://bugzilla.opensuse.org/show_bug.cgi?id=1073809#c5
--- Comment #5 from flo gleixner <gleixner(a)lrz.de> ---
I'm not sure, if MAC cloning directly is triggering the bug. I'm not using MAC
cloning on both machines and i have the problem. But i'm using kvm/libvirtd
which creates a virtual bridge that has the e1000e interface plugged.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1069847http://bugzilla.opensuse.org/show_bug.cgi?id=1069847#c1
Antoine Belvire <antoine.belvire(a)opensuse.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |antoine.belvire(a)opensuse.or
| |g
--- Comment #1 from Antoine Belvire <antoine.belvire(a)opensuse.org> ---
With the recently added systemd units, btrfs-balance and btrfs-scrub cannot run
simultaneously:
~> systemctl cat btrfs-balance
# /usr/lib/systemd/system/btrfs-balance.service
[Unit]
Description=Balance block groups on a btrfs filesystem
Documentation=man:btrfs-balance
After=fstrim.service btrfs-trim.service btrfs-scrub.service
[Service]
Type=oneshot
ExecStart=/usr/share/btrfsmaintenance/btrfs-balance.sh
IOSchedulingClass=idle
CPUSchedulingPolicy=idle
~>
(Thanks to the After= field.)
So I guess this bug can be closed.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=1072055http://bugzilla.novell.com/show_bug.cgi?id=1072055#c1
Luke Jones <jones_ld(a)protonmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Luke Jones <jones_ld(a)protonmail.com> ---
This is correct behaviour - if someone is developing on a limited architecture
such as ARM and is writing only small/basic programs/embedded they will not
need the rust-std libs.
The libs contain such things as the String and Vec data types and macros such
as println!.
Neither of these (and more) are required functionality for writing a rust
program, especially not for embedded applications where space use is critical.
Closing as not a bug.
--
You are receiving this mail because:
You are on the CC list for the bug.