-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC: Do we still need COPY_AS_IS+=( /dev ... ) ? #3028
Comments
For comparison: On the original system:
In the running recovery system:
Regarding '/dev/mqueue' see |
@pcahyna Nevertheless #2808 With this issue here a generic solution could be |
Stale issue message |
Stale issue message |
FYI: in RHEL 6 |
In skel/default/etc/scripts/boot we have this:
so, for older udev versions than 176 we won't mount |
On RHEL 7 there is no
so, how does |
Stale issue message |
Stale issue message |
Stale issue message |
ReaR version ("/usr/sbin/rear -V"):
current master code
Description of the issue (ideally so that others can reproduce it):
See
#3027 (comment)
We copy by default all in /dev/ into the recovery system
because in current master code there is
in usr/share/rear/conf/GNU/Linux.conf
https://github.com/rear/rear/blob/master/usr/share/rear/conf/GNU/Linux.conf#L231
without a comment why we copy all in /dev/
so I guess it was obvious why that is needed
at the time when it was implemented.
It is there since the beginning (at least since Mar 15 2009)
according to
so I guess copying all in /dev/ into the recovery system
is from older times where things in /dev/ had been static.
Meanwhile /dev/ is a mountpoint in the running recovery system:
So what there was copied from the original system in /dev/
into the recovery system is hidden behind what is now
mounted at /dev/ in the running recovery system.
The text was updated successfully, but these errors were encountered: