HI,
> Besides: I'm not sure where you got the impression I owe you anything.
Any user writing a reasonable bug report deserves to be treated with
respect, and deserves a useful answer (spam and duplicate reports are
an obvious exception).
Not just a "no" (which is an unwritten "f... off")
Otherwi
may consider a freeze exception for
this: we've all seen the amount of discussion on how to avoid
installing with systemd.
If this patch can make a non-systemd installation easy, it is worth
consideration, isn't it?
Regards,
Erich
From 4499a0a4ffe884e9da65f05b85ec0d5ee2ca8ef3 Mon Sep 17
reopen 770812
thanks
Hello,
Read the QUESTION.
Not only the word "systemd".
You are still not listening to my actual question, only raising your
sysvinit-shields.
I'm asking if a TASK can solve this maybe more nicely than the other
proposed approaches.
Bug #668001 does not mention this possibi
d the mail?
On Mon, Nov 24, 2014 at 2:06 PM, Cyril Brulebois wrote:
> Erich Schubert (2014-11-24):
>> Package: tasksel
>> Version: 3.29
>> Severity: wishlist
>>
>> Hello,
>> It has been argued that late changes to the debian installer should be
>> avoide
Package: tasksel
Version: 3.29
Severity: wishlist
Hello,
It has been argued that late changes to the debian installer should be
avoided, and the maintainers have clearly expressed that they do not want
to add another debconf question:
https://lists.debian.org/debian-boot/2014/11/msg00408.html
My
Package: keyboard-configuration
Version: 1.47
Severity: normal
found 536683 1.47
thanks
This still happens here for me.
Moving xorg.conf out of the way doesn't help.
Note: I just realized that this bug was reported against console-setup
while I'm seeing it in keyboard-configuration with console-
adm_r, staff_r, user_r), whereas
when logging into the imap server this differentiation is not necessary.
(well, I could imagine we would need it in courier and dovecot when
storing the mail in the users home folder?)
We definitely need some selinux wizard for that.
best regards,
Erich Schuber
ke it a "selinuxify" package, which
will assist you in enabling selinux. Actually there is already some code
in selinux-basics (it's just not used yet), that can for example disable
chroots in postfix. this could be extended to changes such
as /etc/pam.d/login and some /etc/default
l work properly for him. This would make more sense for
switching between strict and targeted policy. The key bootup files such
as /sbin/init have the same labels in these, so switching should work
with a single reboot. For experienced users even without a reboot.
best regards,
Erich Schubert
--
Package: discover1
Severity: normal
discover1 doesn't work with SELinux strict policy, because it's writing
to the /lib/discover directory. This should be resolvable by writing
SELinux policy for discover.
(Don't reassign this to the selinux policy packages. We're using
usertags to keep track of
Package: debian-installer
Severity: normal
Hi,
i just tried to setup a system with software raid.
Creating the devices etc. was all fine, but installing the base system
failed - the kernel (2.6.x) requires raidtools2 to be installed
(it's mkinitrd that is complaining)
-- System Information:
Debia
11 matches
Mail list logo
