** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
** Changed in: mountall (Ubuntu)
Status: New => Confirmed
--
can't enter a password for my encrypted home directory
https://bugs.launchpad.n
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mountall (Ubuntu)
Status: New => Confirmed
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
mountall and cryptsetup will fight for the console when not using usplash
https
Thanks for sorting it out.
The issue Andreas Lieser an I commented on "can't enter a password for
my encrypted home directory" is now Bug #497682
and "mountall and cryptsetup will fight for the console when not using
usplash" is now Bug #497684
--
mountall 0.2.5 and cryptsetup fail to boot whe
Public bug reported:
Binary package hint: mountall
reporting as another bug as summuarized by
Steve Langasek in
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/456274/comments/39
"on the second prompt (for /home)" ... it should be reported as a
separate bug
it's ... known that mou
Public bug reported:
Binary package hint: mountall
separate bug originally posted as comment
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/456274/comments/34
by Andreas Lieser on 2009-12-06:
I did a fresh Karmic install 2 weeks ago, too, and I still got this bug.
I have two encrypt
In addition to what Andreas Lieser wrote on 2009-12-06: #34
Splash turned off (workaround), on the second prompt (for /home):
Entering the pw never works for me on the first time. I now just hit
Enter once. Only on the second time the pw is accepted.
--
mountall 0.2.5 and cryptsetup fa
the turn into a question button requires it to be valid
** Changed in: nethogs (Ubuntu)
Status: Invalid => New
** Changed in: nethogs (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/nethogs/+question/94220
--
nethogs openi
Public bug reported:
Binary package hint: mdadm
The dependencies are not checked, it looks into /proc/mdstat and uses "mdadm
--assemble --scan --run".
(Additionaly a legacy non-hotplug command.)
The best way to fix the so many mdadm bugs is probably to adopt the event
driven upstart/mountall
https://wiki.ubuntu.com/ReliableRaid updated. See rationale.
--
server guide: warn about using ubuntu with raid or provide reliable raid config
https://bugs.launchpad.net/bugs/496478
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Hm, Ok :-(
Thank you for finding that out.
The reason is to be able to log and identify connections from arbitrary
running processes.
Is that now not supported in linux?
--
PID and CMD filtering missing
https://bugs.launchpad.net/bugs/492612
You received this bug notification because you are a
Hi,
from what I have gathered now, two things are generally expected (as in
just works on in other distros) but is missing functionality in ubuntu:
1) No handling of raid degration during boot for non-root filesystems (at all).
(Boot simply stops at a recovery console)
2) Only limited an
> There's no such thing as a "hotplug timeout"
Hmm, then we would need a watchdog like thing that checks if necessary
md devices have come up for a while? (Degrading the array after a
timout, but otherwile similar to what mountall is doing?)
--
mounts fail because degraded raid is not beeing sta
Ok, mdadm would need a way to be invoked after a hotplug timeout.
Do you have a recommendation how to do this right in the upstart
perspective/configuration, maybe?
--
mounts fail because degraded raid is not beeing started
https://bugs.launchpad.net/bugs/496461
You received this bug notificati
Public bug reported:
Binary package hint: ubuntu-docs
As long as we do not provide a reliable raid setup,
https://wiki.ubuntu.com/ReliableRaid
the server guide should contain a big fat warning about setting up raid.
https://help.ubuntu.com/9.10/serverguide/C/advanced-installation.html
** Affec
Public bug reported:
Binary package hint: mountall
Mountall or upstart? do not spell a timeout over raid devices that are
neccessary to boot.
After a timeout without the md device being (fully) assembled by udev,
mountall/upstart needs to try running the array deggraded. Then the
mount can suc
Confirming what Andreas Lieser wrote on 2009-12-06.
cryptsetup of /home broken again
--
mountall 0.2.5 and cryptsetup fail to boot when using usplash
https://bugs.launchpad.net/bugs/456274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Disabling/locking a user account will not prevent a user from logging into your
server remotely if they have previously set up public key authentication.
A workaround is to restrict access to a sshlogin group and parallely
maintaining it,
https://help.ubuntu.com/9.10/serve
Sorry typo has made it unclear: I mean "a proper fix should now be
to..."
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
This failure to load with domain names in the config may have arisen
with the network now set up by upstarts native /etc/init mechanism
(instead of with symlinks in/ets/rc?.d) or been present all the time.
However, a proper fix should no be now to ship two firehol upstart
definitions:
One /etc/i
Corresponding --log-pid, --log-sid and --log-cmd options (like --log-
uid) for iptables are also missing.
--
PID and CMD filtering missing
https://bugs.launchpad.net/bugs/492612
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Public bug reported:
Binary package hint: iptables
iptables (and the kernel probably) are not compiled with support for pid and
cmd filtering.
So it can not grant connections only for selected processes or commands.
--pid-owner processid
Matches if the packet was created by a process with
the
I got the firehol output into a file by modifying the init script.
The iptables commands fail because domains are not being resolved to ip
addresses.
Now I am not sure. Starting the firewall before the network is up might
be adequate behaviour. How can the init scripts handle this? Do firehol
sav
> Why would you not simply set a policy of suspending the laptop on lid
close, instead of turning on laptop-mode?
Because laptop-mode (with all the additional disk idleing features of
the laptop-mode-tools) is different from suspending into a unresponsive
state.
And doesn't gnome-power provide on
Thanks, for getting back and finding out about /etc/power.
I'm sure we want to give a good impression of tidy, easily
understandable and functional ubuntu packages for acpi, powermanagment
and disk idleing (laptop-mode) support unlike with the bugload
unfortunately introduced before.
-> Because l
If the /etc/acpi/events/lm_lid script has been removed from the ubuntu
package of laptop-mode-tools (as the laptop-mode-tools are adapted to
the invocation by pm-utils used in ubuntu), do pm-tools not provide a
replacement hook for the lid closed event?
I wonder because as aunt carry would have sa
96laptop-mode as in sleep.d might be correct
--
not following numbering scheme in /usr/lib/pm-utils/power.d
https://bugs.launchpad.net/bugs/491831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Public bug reported:
Binary package hint: laptop-mode-tools
Because letters sort after numbers it is not possible to adequately sort
a script like "anacon" behind it using numbers.
** Affects: laptop-mode-tools (Ubuntu)
Importance: Undecided
Status: New
--
not following numbering
This bug as about the ENABLE_LAPTOP_MODE having nothing to do in package
acpi-support (another package).
(It was introduced there because some ubuntu dev once stuck an old unmaintained
laptop_mode scipt into acpi-support instead of using proper laptop-mode-tools
package, and later laptop-mode-to
The package might just wrongly restrict the installation of /etc/default
/laptop-mode only to powerpc instead of restricting the install of
/etc/power only to powerpc.
--
/etc/power/ directory and files (used on powerpc) get installed on all platforms
https://bugs.launchpad.net/bugs/491804
You re
Public bug reported:
Binary package hint: laptop-mode-tools
Steve Langasek wrote (https://bugs.launchpad.net/ubuntu/+source/laptop-
mode-tools/+bug/244844/comments/16)
/etc/power/ appears to be a configuration directory for the pbbuttonsd
daemon, which is powerpc-specific
** Affects: laptop-mod
What about using the event driven upstart mechanisms within initramfs,
too? (LP: #491463)
(We need somthing that can handle any hotplugging sequence and stacking
of lvm,raid,crypt,...)
--
boot impossible due to missing initramfs failure hook integration
https://bugs.launchpad.net/bugs/251164
You
Public bug reported:
Binary package hint: upstart
Many problems arise from the current initramfs scripts not being event
driven or a flexible state machine.
Might it be reasonable to use upstart code and configs within the
initramfs to get the rootfs up instead of reimplementing and maintaining
Public bug reported:
Binary package hint: mdadm
When mdadm monitors arrays and an event occurs it should not only send out an
email (not configured by default) but use "wall" and libnotify/notify-send to
to promt local (console/desktop) users.
** Affects: mdadm (Ubuntu)
Importance: Undec
I second this,
and note that as different deamons exist already (notification-daemon,
notify-osd) patching wall might be preferable.
** Summary changed:
- [wishlist] notify-osd support for wall
+ [wishlist] desktop notification support for wall
--
[wishlist] desktop notification support for w
please forward upstream wherever that is
--
option to notify other/all users needed
https://bugs.launchpad.net/bugs/491433
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Public bug reported:
Scripts that monitor system health for example need a way to notify all
users.
But libnotify and notify-send currently only support to notify the user
under which ID it is running.
So something like notify-send --broadcast or --to-user is needed.
** Affects: libnotify (Ubun
Didn't mention this is on a *fresh* 9.10 installation.
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
See the following wiki page for more info about managing user
collaboration and related bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
/etc/login.defs propagates incorrect information
https://bugs.launchpad.net/bugs/487729
You received this bug notification because you are a member of Ubun
*** This bug is a duplicate of bug 487729 ***
https://bugs.launchpad.net/bugs/487729
** This bug has been marked a duplicate of bug 487729
/etc/login.defs propagates incorrect information
--
/etc/login.defs umask cleanup
https://bugs.launchpad.net/bugs/71295
You received this bug notifica
*** This bug is a duplicate of bug 244844 ***
https://bugs.launchpad.net/bugs/244844
pm-utils no longer ships on laptop-mode script
** Changed in: pm-utils (Ubuntu)
Status: New => Fix Released
--
pm-utils has laptop-tools script which conflicts with laptop-mode-tools
https://bugs.lau
*** This bug is a duplicate of bug 59695 ***
https://bugs.launchpad.net/bugs/59695
In 9.10: /etc/acpi/power.sh rightly so does not mess with hdparm any
more.
I can't test if hdparm -B is set correctly after a resume by another
package, if not open new bug on that package.
** Changed in: acp
According to
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/239419/comments/5
the kernel's laptop_mode has been hardcoded to be enabled on battery all the
time anyway.
So it should be fine to just remove checking ENABLE_LAPTOP_MODE
in /etc/default/acpi-support from /etc/init.d/laptop-mod
According to
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/239419/comments/5
the kernel's laptop_mode has been hardcoded to be enabled on battery all the
time anyway.
So it should be fine to just remove checking ENABLE_LAPTOP_MODE
in /etc/default/acpi-support from /etc/init.d/laptop-mod
*** This bug is a duplicate of bug 59695 ***
https://bugs.launchpad.net/bugs/59695
In 9.10: hdparm -B gets set correctly (from another package apparently,
/etc/acpi/power.sh rightly so does not mess with this any more)
** Changed in: acpi-support (Ubuntu)
Status: Incomplete => Fix Rele
Micheal (Rooney), was that a desktop/server machine or a laptop on
battery where the disk failed to spin up again?
--
remove laptop-mode settings from /etc/default/acpi-support
https://bugs.launchpad.net/bugs/244838
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi Steve,
thank you for working on this. I have checked the integration in 9.10.
My observation is:
* laptop-mode-tools ships with scripts under /etc/power/*. Is this location
still valid in some way or are scripts supposed
to be installed under /etc/pm/* now (as /etc/ scripts to override
*** This bug is a duplicate of bug 250938 ***
https://bugs.launchpad.net/bugs/250938
not present in 9.10 anymore
** Changed in: acpi-support (Ubuntu)
Status: New => Fix Released
--
/etc/acpi/power.sh overrides user scripts
https://bugs.launchpad.net/bugs/244831
You received this bug
*** This bug is a duplicate of bug 250938 ***
https://bugs.launchpad.net/bugs/250938
** Changed in: acpi-support (Ubuntu)
Status: New => Fix Released
--
/etc/acpi/power.sh overrides user settings
https://bugs.launchpad.net/bugs/244836
You received this bug notification because you are
*** This bug is a duplicate of bug 490317 ***
https://bugs.launchpad.net/bugs/490317
maybe related: http://sourcecode.de/content/fun-upstart
--
compat: upstart not starting /etc/init.d/firehol and no log available
https://bugs.launchpad.net/bugs/490286
You received this bug notification beca
Johnathon, can you reproduce this bug?
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
maybe related: http://sourcecode.de/content/fun-upstart
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
*** This bug is a duplicate of bug 490317 ***
https://bugs.launchpad.net/bugs/490317
AFAIK the firehol init script is present and has not changed. (And works
as expected when called.)
The suspecting package IMHO may well be an incomplete/broken upstart /
-compat init procedure.
--
compat: u
AFAIK the firehol init script is present and has not changed.
The suspecting package IMHO may well be an incomplete/broken upstart /
-compat init procedure.
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because y
affects set to upstart-compat-sysv (ubuntu)
--
compat: upstart not starting /etc/init.d/firehol and no log available
https://bugs.launchpad.net/bugs/490286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Thanks for pointing out that the bug belongs to the compat scripts then.
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Package changed: firehol (Ubuntu) => ubuntu
** Summary changed:
- upstart not starting /etc/init.d/firehol and no log available
+ compat: ups
Public bug reported:
Binary package hint: gnome-system-monitor
The monitor shows network activity over time (last x seconds)
It should also show the list of processes that had network traffic (in
the last x seconds).
Possibly clicking on a traffic peak in the network graph could identify
the co
Public bug reported:
Binary package hint: firehol
ubuntu 9.10
* /etc/init.d/firehol script is there
* /etc/firehol/firehol.conf is in place
* firehol can be started with "/etc/init.d/firehol start"
(START_FIREHOL in /etc/defaults/firehol is set to yes) and the iptables
are set ok.
* symli
Public bug reported:
Binary package hint: nautilus
9.10: Nautilus 2.28.1
A file/directory without write permissions shows a lock emblem even
though you can access it.
And this icon/emblem just looks the same as a file/directory that can
not even be read.
The difference in permissions should re
I have had a look into /usr/share/system-tools-
backends-2.0/scripts/Users/Users.pm. Unfortunatly I am not at all
familliar with perl.
If it is currently reading in settings from /etc/adduser.conf it should
work with a linked profile as well, what you mean is probably reading in
other installed pr
status could check if current iptables match those firehol generates
from its configuration ("firehol debug") else dispay the diff.
--
init.d script not supporting option "status"
https://bugs.launchpad.net/bugs/185978
You received this bug notification because you are a member of Ubuntu
Bugs, wh
howto at: https://wiki.ubuntu.com/InitScriptStatusActions
--
init.d script not supporting option "status"
https://bugs.launchpad.net/bugs/185978
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Does what the reporter posted mean that NIS/NFS scipts are flushing
iptables?
--
The rcS.d script for firehol starts before NFS and NIS
https://bugs.launchpad.net/bugs/28906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
firhol should be made to source firehol.conf and parts from a directory
like /etc/firehol.d, where other packages can drop config snippets.
While firehol still sets up the firewall as early a possible in the boot
up process.
--
The rcS.d script for firehol starts before NFS and NIS
https://bugs.
** Summary changed:
- The rcS.d script for firehol is missing some options
+ init.d script not supporting option "status"
** Description changed:
Binary package hint: firehol
- DISTRIB_ID=Ubuntu
- DISTRIB_RELEASE=7.10
- DISTRIB_CODENAME=gutsy
- DISTRIB_DESCRIPTION="Ubuntu 7.10"
+ The init.d
The init script should handle/pass on the status option as expected from
an init script. For the other options howeverver, calling the firehol
script directly seems just all right.
# firehol panic
--
init.d script not supporting option "status"
https://bugs.launchpad.net/bugs/185978
You received
I have actually produced a patch to adduser now, as far as I could.
Since it is my first one I'd appreciate any feedback. Its in LP: #489136
--
users-admin profiles default to force [GU]ID, home dir, shell and groups to
adduser
https://bugs.launchpad.net/bugs/488913
You received this bug notific
This is my first try at using bzr.
I created an own branch from the lucid brach, changed what I could while
browsing through the files, committed and used send -o to produce the
attatched file. Was that correct?
Any recomendations welcome.
** Attachment added: "initial patch to support adduser
Changing package because the profiles with default groups in ubuntu are
currently maintained in g-s-t (not adduser).
** Package changed: pam (Ubuntu) => gnome-system-tools (Ubuntu)
** Changed in: gnome-system-tools (Ubuntu)
Status: Invalid => New
** Description changed:
-
Current beha
** Description changed:
- Ubuntu uses private user groups.
+
+ Current behaviour is:
+ The "users" group exists but when setting up a (set group ID) groupdirectory
(i.e. /home/group/users) it does not work as expected, because the users group
is not populated (empty).
+
+ Changed behaviour wou
** Summary changed:
- Let groupadd create /home/group/ sgid directories
+ addgroup option to create /home/group/ sgid directories
** Description changed:
-
- Let groupadd have the option to create /home/group/ sgid
directories.
+ Let groupadd have the option to create /home/group/ sgid
+ direc
addgroup is implemented within adduser
** Package changed: shadow (Ubuntu) => adduser (Ubuntu)
--
Let groupadd create /home/group/ sgid directories
https://bugs.launchpad.net/bugs/379421
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I could not reproduce this on 9.10.
** Changed in: adduser (Ubuntu)
Status: New => Incomplete
--
adduser silently removes users from groups
https://bugs.launchpad.net/bugs/260086
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
In order to mimic the user profiles currently shiped with gnome-system-
tools:
* mv /etc/adduser.conf /etc/adduser.conf.unprivileged
* create adduser.conf.desktop
- with EXTRA_GROUPS="cdrom floppy dialout tape dip adm plugdev fax audio
scanner fuse video"
- andADD_EXTRA_GROUPS=1
* create
Public bug reported:
Binary package hint: adduser
Currently different frontends have implement and configure user profiles
differently, easily leading to inconsistencies when users are created with
different tools. Even if they use adduser to create users, they have override
much, somtimes ev
Just came across this answer.
http://lists.alioth.debian.org/pipermail/adduser-devel/2008-February/003161.html
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Alternativly adduser.conf can be shipped as a symlink to a
adduser.conf.dist (distribution) profile.
This allows to switch the symlink to an admin provided profile, so that
it will be used as a adduser default, without having to touch the .dist
profile.
--
users-admin profiles default to force [
s / remove that user from the list / remove that checkbox from the list
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
>From viewing users I created with adduser I just noticed that in the
g-s-t edit group window the users name is of course not checked when
viewing any UPG created with adduser.
It may be nice to remove that user from the list and have some sort of
indicator that a group is a (possibly private) pri
Oh, I just realized that adduser supports user profiles, maybe even
since its first version.
System wide profiles can be provided as adduser.conf. and the profile
is selected with:
# adduser --conf adduser.conf.
--
users-admin profiles default to force [GU]ID, home dir, shell and groups to
ad
Even better then. :)
(yes adduser.conf and adduser.local.conf together provide only "one
profile" )
** Summary changed:
- users-admin's profiles feature forces [GU]ID, home dir, shell and groups to
adduser
+ users-admin profiles default to force [GU]ID, home dir, shell and groups to
adduser
-
You can refer to the relevant discussion in
Bug:488158 users-admin should leave adduser handle main group creation
and
Bug:488913 users-admin defaults to override system wide defaults from
/etc/login.defs, /adduser.conf
--
kuser is violating debian policy
https://bugs.launchpad.net/bugs/3793
All right, has been a pleasure.
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
Public bug reported:
Binary package hint: gnome-system-tools
splitting this from #488158
>we implement user profiles in users-admin. Those allow the
distribution/admin to present users with typical account types, which
set sensible default values for home dir, shell, groups membership (esp.
admi
Hi,
what a nice coincidence. :) Thank you for your feedback. I have now updated the
wiki to match the adduser behaviour as well.
I've seen now, that only useradd/groupadd is part of the debian passwd
package, but adduser uses it.
> (But still, adduser could be smarter and remove the group if the
Concerning the UPG group membership: As it is not necessary (and
redundant) and gives problems I believe users should not be made members
of their main groups.
As a result of adding the user to its main group deluser thinks the
primary group is not one adduser has created automatically as a user
p
please don't set invalid instead of giving a reason and reassigning
appropriately
** Description changed:
-
Ubuntu uses private user groups.
In order for the users to belong be added to the users group by default
- /etc/security/groups needs to contain a line like this one:
+ two solution
Could someone please reassign, and please provide an argument for a
solution that may be harder to modify and activate for existing users by
admins and control scripts alike.
--
users not belonging to users group
https://bugs.launchpad.net/bugs/253103
You received this bug notification because yo
Uh, oh, I got that feeling you know ;-)
Seriously, exactly as you write I was seeing the user being added to his
primary private group.
"adduser tester" produces this group entry: "tester:x:1006:"
where users-admin produced: "test:x:1005:test"
I had experienced much trouble before because of ano
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
[gutsy] mdadm, initramfs missing ARRAY lines
https://bugs.launchpad.net/bugs/136252
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
--incremental --scan --run does not start anything
https://bugs.launchpad.net/bugs/244808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
inconsistency with the --no-degraded option
https://bugs.launchpad.net/bugs/244810
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
boot impossible due to missing initramfs failure hook integration
https://bugs.launchpad.net/bugs/251164
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
option to start selected arrays in "auto-read" mode (like --incremental)
https://bugs.launchpad.net/bugs/251646
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents hotplug
autodetection
https://bugs.launchpad.net/bugs/252345
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
encrypted root initialisation races/fails on hotplug devices (does not wait)
https://bugs.launchpad.net/bugs/247153
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
--incremental not creating device nodes
https://bugs.launchpad.net/bugs/251663
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Current state of ubuntu systems with md raid:
https://wiki.ubuntu.com/ReliableRaid
--
installed system fails to boot with degraded raid holding cryptdisk
https://bugs.launchpad.net/bugs/488317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Hi,
In 9.10 someone changed the mdadm udev rules to use --incremental without
considering all the consequences that were already reported.
https://wiki.ubuntu.com/ReliableRaid
--
udev not using mdadm incremental
https://bugs.launchpad.net/bugs/157981
You received this bug notification because y
yeah, right a umask setting the exec bit ;-)
** Changed in: coreutils (Ubuntu)
Status: Incomplete => Confirmed
--
cp preserves mode with --no-preserve=mode
https://bugs.launchpad.net/bugs/379233
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Two external drives containig a raid1 (storage for digicam) do not get
detected and mounted when connected to another machine.
** Summary changed:
- mdadm.conf is crated with explicit ARRAY statements prevents hotplug
autodetection
+ mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any
801 - 900 of 1101 matches
Mail list logo
