Patrick Bartek wrote:
> Actually, if I've understood what I've read over the past two weeks,
> that's not correct. You need a dedicated partition formatted in FAT32,
> marked ef00 partition-type with the "boot" flag enabled on it. Mounting
> that partition on /boot/efi (or somewhere else, depends
On 11.01.19 22:45, Jonathan Dowland wrote:
> EncFS should not be used for any new file encryption project, IMHO.
> There was the following report in 2014:
> https://defuse.ca/audits/encfs.htm
> This is referenced in the NEWS file in the EncFS package
> https://salsa.debian.org/debian/encfs/blob/de
On 12/01/19 4:47 PM, Richard Hector wrote:
> On 12/01/19 1:28 AM, David wrote:
>> Hi, I have no expertise in this, except to suggest that if I was
>> seeing your symptoms then I would investigate if the discussion
>> here might be relevant:
>> https://lists.debian.org/debian-devel/2018/12/msg00184.
On 12/01/19 1:28 AM, David wrote:
> Hi, I have no expertise in this, except to suggest that if I was
> seeing your symptoms then I would investigate if the discussion
> here might be relevant:
> https://lists.debian.org/debian-devel/2018/12/msg00184.html
Interesting, thanks - I'm going to try 4.19
On 12/01/19 3:41 AM, Michael Stone wrote:
> On Fri, Jan 11, 2019 at 02:03:44PM +1300, Richard Hector wrote:
>> According to dmesg, this is where it appears to hang:
>>
>> [ 2.717311] device-mapper: uevent: version 1.0.3
>> [ 2.717398] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23)
>> initial
On Fri, Jan 11, 2019 at 04:56:07PM -0800, Patrick Bartek wrote:
On Fri, 11 Jan 2019 07:13:30 -0500 Michael Stone wrote:
On Thu, Jan 10, 2019 at 03:53:11PM -0800, Patrick Bartek wrote:
>Plus, I
>want to have a common-shared /boot partition for possible future
>upgrades or expansions.
This is a
On Fri, 11 Jan 2019 08:38:52 +0100
deloptes wrote:
> Patrick Bartek wrote:
>
> >
> > Building a new UEFI system to supplant my "showing its age" 12 year old
> > non-UEFI, MBR-only system, and don't want to do a clean install of
> > Stretch. Cloning drive and converting to GPT is out. I want on
On Fri, 11 Jan 2019 07:13:30 -0500
Michael Stone wrote:
> On Thu, Jan 10, 2019 at 03:53:11PM -0800, Patrick Bartek wrote:
> >Plus, I
> >want to have a common-shared /boot partition for possible future
> >upgrades or expansions.
>
> This is a really bad idea, and will cause far more trouble th
On Fri, Jan 11, 2019 at 10:17:05PM +, mick crane wrote:
> I'm having a bit of bother with my home server thingy.
> does apache, roundcube, dovecot, cups.
> is buster.
> Is problem with roundcube communicating with dovecot or something. sending
> mail times out and the settings webpage isn't wor
I'm having a bit of bother with my home server thingy.
does apache, roundcube, dovecot, cups.
is buster.
Is problem with roundcube communicating with dovecot or something.
sending mail times out and the settings webpage isn't working whereas it
was fine a week ago.
It occurs to me I don't rea
Hi,
MENGUAL Jean-Philippe wrote:
> My purpose is having a USB stick splitted in 2 parts:
> 1. MBR + partitions: a Debian installer from an ISO
> 2. A blank partition to install data or whatver
>
> While I know to "burn" an iso on a key via dd, how can I do to have a clean
> installer but using key
If using Uefi installs you only need to have a vfat formated first
partition with a folder called efi and the appropriate efi
binary/substructure. You can use the rest of the disk as you like.
BIOS installers on the same can be achieved with syslinux in addition to
uefi. However I find that just h
On 1/11/19, Dan Ritter wrote:
> Cindy-Sue Causey wrote:
>> On 1/11/19, Dan Ritter wrote:
>> >
>> > As an experiment -- try this:
>> >
>> > echo udev_log=\"err\" >> /etc/udev/udev.conf
>> >
>> > (Or, alternatively, edit /etc/udef/udev.conf and insert/change
>> > that as necessary.)
>>
>>
>> Manual
On Wed, Jan 09, 2019 at 10:18:47PM -0500, Celejar wrote:
The standard encryption technology for linux is LUKS. It works on the
block device level, not the file level.
LUKS would be no good if the user wants to move/copy/share the encrypted
files, encrypted, elsewhere: they didn't say so explici
Hi,
My purpose is having a USB stick splitted in 2 parts:
1. MBR + partitions: a Debian installer from an ISO
2. A blank partition to install data or whatver
While I know to "burn" an iso on a key via dd, how can I do to have a
clean installer but using key for other usages?
Thanks very much
Hello,
On Fri, Jan 11, 2019 at 10:33:39PM +0300, Reco wrote:
> On Fri, Jan 11, 2019 at 08:28:18PM +0100, basti wrote:
> > is there a way to monitor processes that access /dev/urandom
>
> auditctl -w /dev/urandom -r
>
> remove it with
>
> auditctl -D
Note also that one should not really be conc
On Fri, Jan 11, 2019 at 08:28:18PM +0100, basti wrote:
> Hello,
>
> is there a way to monitor processes that access /dev/urandom
auditctl -w /dev/urandom -r
remove it with
auditctl -D
> and show how may entropy the get?
You'll probably need some advanced kernel-level tracing facility (such
as
Hello,
is there a way to monitor processes that access /dev/urandom and show
how may entropy the get?
I have try lsof /dev/urandom without luck.
Best regards,
Hi all, I'm inclined to file a bug for this but before I do the
reportbug GUI suggests I contact the list. I'm running Debian Buster
on a Dell XPS 13 9370 and using Gnome on Wayland.
I've checked 'Disable While Typing' in Tweaks -> Keyboard & Mouse ->
Touchpad and also confirmed with
hbarta@rocinan
David wrote:
> Hi, I have no expertise in this, except to suggest that if I was
> seeing your symptoms then I would investigate if the discussion
> here might be relevant:
> https://lists.debian.org/debian-devel/2018/12/msg00184.html
Good story - thanks and no comments!
Both Debian and CentOS are good choices for a server OS.
We use both in my workplace. We don't install a desktop.
It is not required and it is a waste of resources.
Debian is a good fit for developers, as there
is a great breadth of packages, and often more recent.
CentOS is easier to manage as
On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote:
I recently came across an inconsistency in sid that it seems difficult (to me)
to overcome.
A kernel package named linux-image-4.19.0-1-amd64-unsigned provides the running
kernel but, since few days ago, it creates conflicts with
On Fri, Jan 11, 2019 at 02:03:44PM +1300, Richard Hector wrote:
According to dmesg, this is where it appears to hang:
[2.717311] device-mapper: uevent: version 1.0.3
[2.717398] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23)
initialised: dm-d
e...@redhat.com
[2.978281] clocksource: S
On Fri, Jan 11, 2019 at 03:16:37PM +1300, Richard Hector wrote:
It turns out the later failures to boot probably weren't; it's just that
I had 'quiet' enabled in the kernel commandline. Disabling that enabled
me to see where it was hanging
Yeah, I hate that "quiet" is the default--in the best
Cindy-Sue Causey wrote:
> On 1/11/19, Dan Ritter wrote:
> > Richard Hector wrote:
> >> Hi all,
> >>
> >> This machine is taking ages to boot.
> >>
> >> It's a fresh install.
> >>
> >> According to dmesg, this is where it appears to hang:
> >>
> >> [2.717311] device-mapper: uevent: version 1.0
On Fri, 11 Jan 2019 at 12:04, Richard Hector wrote:
>
> This machine is taking ages to boot.
You could also try the 'systemd-analyze blame' tool.
On Fri, 11 Jan 2019 at 12:04, Richard Hector wrote:
>
> Hi all,
>
> This machine is taking ages to boot.
>
> It's a fresh install.
>
> According to dmesg, this is where it appears to hang:
>
> [2.717311] device-mapper: uevent: version 1.0.3
> [2.717398] device-mapper: ioctl: 4.35.0-ioctl (
On Thu, Jan 10, 2019 at 03:53:11PM -0800, Patrick Bartek wrote:
Plus, I
want to have a common-shared /boot partition for possible future
upgrades or expansions.
This is a really bad idea, and will cause far more trouble than it can
possibly save in the future. You do need one EFI partition pe
On 1/11/19, Dan Ritter wrote:
> Richard Hector wrote:
>> Hi all,
>>
>> This machine is taking ages to boot.
>>
>> It's a fresh install.
>>
>> According to dmesg, this is where it appears to hang:
>>
>> [2.717311] device-mapper: uevent: version 1.0.3
>> [2.717398] device-mapper: ioctl: 4.35
Richard Hector wrote:
> Hi all,
>
> This machine is taking ages to boot.
>
> It's a fresh install.
>
> According to dmesg, this is where it appears to hang:
>
> [2.717311] device-mapper: uevent: version 1.0.3
> [2.717398] device-mapper: ioctl: 4.35.0-ioctl (2016-06-23)
> initialised: d
I recently came across an inconsistency in sid that it seems difficult (to
me) to overcome.
A kernel package named linux-image-4.19.0-1-amd64-unsigned provides the
running kernel but, since few days ago, it creates conflicts with the
metapackage linux-image-amd64 (bercause it depends on
linux-imag
On 2019-01-11, Richard Hector wrote:
>
> Hints on where to look for the boot sequence in the kernel source, perhap=
> s?
>
If you're using systemd the output of
systemd-analyze blame
systemd-analyze critical-chain
might be informative.
32 matches
Mail list logo
