On 4/18/20 3:53 AM, Ed Greshko wrote:
On 2020-04-18 18:46, Sreyan Chakravarty wrote:
2) After hibernating successfully a couple of times, I can SELinux back to
enforcing and it doesn't cause any problems. I have no clue why ?
Well, since selinux operates on file/directory contexts and no
> e.g. A swap file on an encrypted partition.
I am already using it in an encrypted partition. It does not give any
problems.
On Sat, Apr 18, 2020 at 8:29 PM Tim via users
wrote:
> Tim:
> >> To be able to do that, it has to be able to read within a
> >> filesystem by itself. There's probably
On Sun, 2020-04-19 at 00:28 +0930, Tim via users wrote:
> Tim:
> > > To be able to do that, it has to be able to read within a
> > > filesystem by itself. There's probably only a small set of
> > > filesystems it can handle.
>
> Samuel Sieb:
> > No, you point the kernel at the offset of the
Tim:
>> To be able to do that, it has to be able to read within a
>> filesystem by itself. There's probably only a small set of
>> filesystems it can handle.
Samuel Sieb:
> No, you point the kernel at the offset of the header within the
> partition. The header contains pointers to the rest of
Am 18.04.2020 um 14:12 schrieb bruce:
This whole thread is why this email list is a great example of how this
thing called the net can actually be a great resource for weird tech stuff,
and for helping others!
Yes, this is a mailing list and covered by guidelines like the good old
etiquette
This whole thread is why this email list is a great example of how this
thing called the net can actually be a great resource for weird tech stuff,
and for helping others!
Does the list sometimes veer off to snarky stuff.. very rarely.
OJ to all!
On Sat, Apr 18, 2020 at 8:08 AM Patrick
On Sat, 2020-04-18 at 11:04 +, Sreyan Chakravarty wrote:
> > On Fri, 2020-04-17 at 15:03 -0700, Samuel Sieb wrote:
> >
> > Yes, that's exactly my point. However it does mean that the filesystem
> > has to be one that the initial system understands.
> >
> > poc
>
> Sorry but let me confuse
> On Fri, 2020-04-17 at 15:03 -0700, Samuel Sieb wrote:
>
> Yes, that's exactly my point. However it does mean that the filesystem
> has to be one that the initial system understands.
>
> poc
Sorry but let me confuse you further.
If the initial ramdisk does not understand the filesystem, then
> On 2020-04-18 18:46, Sreyan Chakravarty wrote:
>
> Well, since selinux operates on file/directory contexts and no files or
> directories are
> involved as mentioned bySamuel: "The header contains pointers to the rest of
> the
> data. It doesn't have to know anything about the filesystem." And
On 2020-04-18 18:46, Sreyan Chakravarty wrote:
> 2) After hibernating successfully a couple of times, I can SELinux back to
> enforcing and it doesn't cause any problems. I have no clue why ?
Well, since selinux operates on file/directory contexts and no files or
directories are involved as
> On 4/17/20 11:20 PM, Tim via users wrote:
>
> No, you point the kernel at the offset of the header within the
> partition. The header contains pointers to the rest of the data. It
> doesn't have to know anything about the filesystem.
You know there are 2 things that struck me as odd:
1)
On Sat, 2020-04-18 at 00:44 -0700, Samuel Sieb wrote:
> On 4/17/20 11:20 PM, Tim via users wrote:
> > On Fri, 2020-04-17 at 15:03 -0700, Samuel Sieb wrote:
> > > During resume, the filesystem *can't* be mounted. All the
> > > filesystem state is in the hibernation image which you are trying to
>
On Fri, 2020-04-17 at 15:03 -0700, Samuel Sieb wrote:
> On 4/17/20 2:42 PM, Patrick O'Callaghan wrote:
> > On Fri, 2020-04-17 at 14:25 -0700, Samuel Sieb wrote:
> > > On 4/17/20 2:11 PM, Roger Heflin wrote:
> > > > For the vg/offset to work the file must be contiguous (only 1
> > > >
On 4/17/20 11:20 PM, Tim via users wrote:
On Fri, 2020-04-17 at 15:03 -0700, Samuel Sieb wrote:
During resume, the filesystem *can't* be mounted. All the
filesystem state is in the hibernation image which you are trying to
load. It's one of those fun chicken and egg challenges. That's why
On Fri, 2020-04-17 at 15:03 -0700, Samuel Sieb wrote:
> During resume, the filesystem *can't* be mounted. All the
> filesystem state is in the hibernation image which you are trying to
> load. It's one of those fun chicken and egg challenges. That's why
> there has to be enough info in the swap
On 4/17/20 2:42 PM, Patrick O'Callaghan wrote:
On Fri, 2020-04-17 at 14:25 -0700, Samuel Sieb wrote:
On 4/17/20 2:11 PM, Roger Heflin wrote:
For the vg/offset to work the file must be contiguous (only 1
section/extent in the file). I don't see that mentioned in
archlinux.
I tried to find
On Fri, 2020-04-17 at 14:25 -0700, Samuel Sieb wrote:
> On 4/17/20 2:11 PM, Roger Heflin wrote:
> > For the vg/offset to work the file must be contiguous (only 1
> > section/extent in the file). I don't see that mentioned in
> > archlinux.
>
> I tried to find out the on-disk format for swap
On 4/17/20 2:11 PM, Roger Heflin wrote:
For the vg/offset to work the file must be contiguous (only 1
section/extent in the file). I don't see that mentioned in
archlinux.
I tried to find out the on-disk format for swap files, but wasn't able
to. But from the doc at
For the vg/offset to work the file must be contiguous (only 1
section/extent in the file). I don't see that mentioned in
archlinux.
What does filefrag show and what does du against the swap file show?
The hibernate restore is starting up the vg/lv and going to that
offset and expecting it to
On Fri, 17 Apr 2020 15:47:41 +0530
Sreyan Chakravarty wrote:
> This is my /etc/fstab:
>
> /dev/mapper/vgfedora-fedora / ext4
^
> GRUB_TIMEOUT=10
> GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
> GRUB_DEFAULT=saved
>
Ah! saw your message in the other thread, continuing over there.
Sorry for the confusion.
On Fri, Apr 17, 2020 at 4:36 PM Patrick O'Callaghan
wrote:
> On Fri, 2020-04-17 at 15:47 +0530, Sreyan Chakravarty wrote:
> > I have Fedora 31 installed in VirtualBox, and I am trying to test out
> >
Can that partition be encrypted ? Why can't I use a swap file ? I mean is
the Arch wiki wrong ?
On Fri, Apr 17, 2020 at 4:36 PM Patrick O'Callaghan
wrote:
> On Fri, 2020-04-17 at 15:47 +0530, Sreyan Chakravarty wrote:
> > I have Fedora 31 installed in VirtualBox, and I am trying to test out
> >
On Fri, 2020-04-17 at 15:47 +0530, Sreyan Chakravarty wrote:
> I have Fedora 31 installed in VirtualBox, and I am trying to test out
> hibernation with a swap file, but no matter what I do I am unable to get
> Hibernation to work.
As has already been explained when you asked before, you can't use
I have Fedora 31 installed in VirtualBox, and I am trying to test out
hibernation with a swap file, but no matter what I do I am unable to get
Hibernation to work.
I am using a 6GB swap file with the RAM allocated to the VM is 5GB, so the
file should be sufficient for a successful hibernate.
24 matches
Mail list logo
