Hi everyone,
I installed some days ago Debian 10 with LVM inside LUKS and specific
formatting (4 logical volumes for /, /home, /var and swap) on my Lenovo
ThinkPad X390 in dual-boot configuration with Windows 10 (which came
preinstalled on this brand new laptop).
Everything went well except I
shirish शिरीष (12019-12-26):
> I haven't found any app, either subtitlecomposer or subtitleeditor or
> any other tool to transform to .srt.
ffmpeg can do that:
ffmpeg -i any_kind_of_text_sub out.srt
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
Dear all,
Please CC me if anybody has a solution.
I haven't found any app, either subtitlecomposer or subtitleeditor or
any other tool to transform to .srt. I have seen youtube (as an e.g.)
which uses web.vtt for subtitling work for most of the videos. And
this becomes infurtiating especially wh
Thanks for the reply and the useful explanations (and the expression of
limitation of your personal knowledge). I will add one question / comment
down below:
On Thursday, December 26, 2019 10:23:54 AM Greg Wooledge wrote:
> For most people, it comes down to "when you can't write to the device
>
Hi,
Greg Wooledge wrote:
> > > Remember, tar was designed for magnetic tapes,
> > > which are read sequentially. It provides no way for a reader to learn
> > > that file xyz is at byte offset 31337 and that it should skip ahead to
> > > that point if it only wants that one file.
rhkra...@gmail.c
On Thu, 26 Dec 2019 09:51:59 -0500
rhkra...@gmail.com wrote:
> Again, I assume (I know what assume does) that "USB mass-storage
> device that acts like a hard drive" is (or might be) a pen drive type
> of device. I've had a lot of bad luck (well, more bad luck than I'd
> like) with that kind of d
On Thu, Dec 26, 2019 at 09:51:59AM -0500, rhkra...@gmail.com wrote:
> Just to confirm, I assume that is true ("no way to skip ahead to byte 31337")
> even if the underlying media is a (somewhat random access) disk instead of
> (serial access) tape?
Correct. There's no central index inside the t
On 27/12/19 2:30 am, Greg Wooledge wrote:
> On Fri, Dec 27, 2019 at 12:58:18AM +1300, Richard Hector wrote:
>> $ sudo systemctl kill -s HUP rsyslog.service
>> Failed to kill unit rsyslog.service: Input/output error
>
>-s, --signal=
>When used with kill, choose which signal to s
Thanks for addressing this -- I have a few questions I want to ask for my own
edification / clarification:
On Thursday, December 26, 2019 08:18:12 AM Greg Wooledge wrote:
> The drawback of using tar is that it creates an *archive* of files -- that
> is, a single file (or byte stream) that contain
On Fri, Dec 27, 2019 at 12:58:18AM +1300, Richard Hector wrote:
> $ sudo systemctl kill -s HUP rsyslog.service
> Failed to kill unit rsyslog.service: Input/output error
-s, --signal=
When used with kill, choose which signal to send to selected
processes. Must be one of
On Thu, Dec 26, 2019 at 08:18:12AM -0500, Greg Wooledge wrote:
> On Wed, Dec 25, 2019 at 11:07:22AM -0800, David Christensen wrote:
> > > I was amazed that nobody yet considered tar.
Sorry... that sentence was actually written by Franco Martelli. I
replied to the wrong email.
On Wed, Dec 25, 2019 at 11:07:22AM -0800, David Christensen wrote:
> > I was amazed that nobody yet considered tar.
The best use case for tar is creating a full backup to removable media
(magnetic tapes are literally what it was designed for -- the "t" stands
for tape).
The drawback of using tar
Hi all,
I've got a problem in some of my LXC containers, running buster.
Logrotate can't HUP rsyslog with "systemctl kill -s HUP rsyslog.service":
$ sudo systemctl kill -s HUP rsyslog.service
Failed to kill unit rsyslog.service: Input/output error
I can HUP it fine manually, with:
$ sudo kill
13 matches
Mail list logo
