Suggestion for the teleconference:
Talkshoe.com
Talkshoe is free. It has a web client too with a chat log when the
conference call starts.
Someone make an account. It's got SIP and a US number.
That way nobody get's everyone ease's IP addresses and nobody can play
funny buggers with a firewall
m.storchak at gmail dot com wrote:
Is there a reason to use full path specification? Why can't
mkfs.ext{2|4} be called and whichever is found first in PATH gets
executed? In this case only one of e2fsprogs and busybox implementations
should be required. Let busybox be default, but please leave an
On 7/3/16 00:26, Luke McKee wrote:
> For some further background...
>
> the original procd zram patch uses ext2 :)
>
> https://dev.openwrt.org/ticket/19586#comment:9
> https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/029587.html
>
> It shows you what happens when someone enables
On 07/03/2016 01:24 PM, John Crispin wrote:
> Hi,
>
> few comments
>
> 1) the patch needs to be split into 2, ext2 change/lzo change
> 2) send them inline please and not as attachement
> 3) the V3 needs to be in the subject prefix [PATCH V3] procd: ...
> 4) the Signed-off-by: line is missing
>
>
Hi,
few comments
1) the patch needs to be split into 2, ext2 change/lzo change
2) send them inline please and not as attachement
3) the V3 needs to be in the subject prefix [PATCH V3] procd: ...
4) the Signed-off-by: line is missing
John
On 03/07/2016 08:14, Luke McKee wrote:
> To
To quote Arjen:
If the only reason to switch to ext2 is to remove the journal, why not
just add
-O ^has_journal
to the mount options?
That's not a mount option. That's a tune2fs option.
Journaling isn't the the only problem. The biggest problem is BLOAT.
You need libext2+e2fsprogs
