On 23/11/20 10:10 pm, Walter Dnes wrote:
> On Sun, Nov 22, 2020 at 04:39:44PM -0700, the...@sys-concept.com wrote
>> Duplicating was easy, but when I try to recompile a kernel I get an error:
>>
>> make menuconfig
>> HOSTCC script/kconfig/mconf.o
>> : internal compiler error: Illegal instruction
On Mon, 23 Nov 2020 14:31:26 -0600, Matt Connell (Gmail) wrote:
> > And correct me if I'm wrong but with rsync if something dies in
> > process you can usually start it back up and complete the job without
> > starting over from scratch.
>
> If you use the --partial flag, yes. I don't think th
On Mon, 23 Nov 2020 20:57:34 +, antlists wrote:
> > And correct me if I'm wrong but with rsync if something dies in
> > process you can usually start it back up and complete the job without
> > starting over from scratch.
>
> If you dd the partition (which I'm planning to do), then there's
Jack wrote:
> On 2020.11.23 15:00, Dale wrote:
>> Matt Connell (Gmail) wrote:
>> > On Mon, 2020-11-23 at 19:24 +0100, Dr Rainer Woitok wrote:
>> >> *blush* Even though I'm using "date" since umpteen years, up to
>> now I
>> >> was not aware of this "@..." syntax. You're perfectly right,
>> that
On 2020.11.23 15:00, Dale wrote:
Matt Connell (Gmail) wrote:
> On Mon, 2020-11-23 at 19:24 +0100, Dr Rainer Woitok wrote:
>> *blush* Even though I'm using "date" since umpteen years, up to
now I
>> was not aware of this "@..." syntax. You're perfectly right,
that's ex-
>> actly what I wa
Neil Bothwick wrote:
> On Mon, 23 Nov 2020 13:51:26 -0600, Dale wrote:
>
>> If UUID is something you don't want to spend time learning right now,
>> try using labels at least. Just make sure YOU use unique labels for
>> each one. Hint. home-old, home-new works pretty well at times. At
>> least
On 23/11/2020 20:25, Mark Knecht wrote:
> I agree on labels, they are far more readable. But I'm starting to think
> that duplicating partitions like this is asking for trouble. I think it
> would be better to create the partitions and filesystems you want on the
> new disk, then mount both a
On Mon, 2020-11-23 at 13:25 -0700, Mark Knecht wrote:
> And correct me if I'm wrong but with rsync if something dies in process
> you can usually start it back up and complete the job without starting over
> from scratch.
If you use the --partial flag, yes. I don't think that is enabled by
defaul
On Mon, Nov 23, 2020 at 1:11 PM Neil Bothwick wrote:
>
> On Mon, 23 Nov 2020 13:51:26 -0600, Dale wrote:
>
> > If UUID is something you don't want to spend time learning right now,
> > try using labels at least. Just make sure YOU use unique labels for
> > each one. Hint. home-old, home-new wor
On Mon, 23 Nov 2020 13:51:26 -0600, Dale wrote:
> If UUID is something you don't want to spend time learning right now,
> try using labels at least. Just make sure YOU use unique labels for
> each one. Hint. home-old, home-new works pretty well at times. At
> least you know it is home and whic
Matt Connell (Gmail) wrote:
> On Mon, 2020-11-23 at 19:24 +0100, Dr Rainer Woitok wrote:
>> *blush* Even though I'm using "date" since umpteen years, up to now I
>> was not aware of this "@..." syntax. You're perfectly right, that's ex-
>> actly what I was looking for.
> I wasn't either, until
antlists wrote:
> On 23/11/2020 10:37, Michael wrote:
Have you changed the UUIDs on the new partitions?
>
>>> Never used UUID in fstab. Do I just run: blkid|grep UUID
>>> and copy it to fstab.
>
>> I warned you about UUIDs. The block device of /dev/sda* could be
>> pointing at
>> a partition
On 23/11/2020 10:37, Michael wrote:
Have you changed the UUIDs on the new partitions?
Never used UUID in fstab. Do I just run: blkid|grep UUID
and copy it to fstab.
I warned you about UUIDs. The block device of /dev/sda* could be pointing at
a partition either on the old, or the new disk.
On Mon, 2020-11-23 at 19:24 +0100, Dr Rainer Woitok wrote:
> *blush* Even though I'm using "date" since umpteen years, up to now I
> was not aware of this "@..." syntax. You're perfectly right, that's ex-
> actly what I was looking for.
I wasn't either, until I read the man page. Just goes to
Matt and also Mathew,
On Monday, 2020-11-23 11:46:56 -0600, Matt Connell (Gmail) wrote:
> ...
> Is the basic `date` from coreutils sufficient? If so, no need to
> reinvent the wheel, unless I'm misunderstanding your need.
>
> Example:
>
> $ date --date='@21'
> 2037-12-14T17:00:44 CST
On Mon, 2020-11-23 at 18:28 +0100, Dr Rainer Woitok wrote:
> looking for a small, fast utility (preferably written in C) accepting a
> Unix time (seconds since 1970-01-01) as argument and printing the corr-
> esponding local time to standard output.
Is the basic `date` from coreutils sufficient?
You might be able to use this shell command:
TZ=US/Pacific date --date='@2147483647'
- Matthew
On 11/23/20 12:28 PM, Dr Rainer Woitok wrote:
Greetings,
looking for a small, fast utility (preferably written in C) accepting a
Unix time (seconds since 1970-01-01) as argument and printing the corr-
esponding local time to standard output.
Any pointers?
Sincerely,
Rainer
I'm not aware
Greetings,
looking for a small, fast utility (preferably written in C) accepting a
Unix time (seconds since 1970-01-01) as argument and printing the corr-
esponding local time to standard output.
Any pointers?
Sincerely,
Rainer
On Mon, Nov 23, 2020 at 9:10 AM Walter Dnes wrote:
>
>
> Ouch! Are the CPUs exactly identical? If not, then you may get the
> "Illegal instruction" error. This is a "feature" of Gentoo, which is
> often user-optimized for a specific CPU.
This "feature" has nothing to do with Gentoo, but just
On Sun, Nov 22, 2020 at 04:39:44PM -0700, the...@sys-concept.com wrote
>
> Duplicating was easy, but when I try to recompile a kernel I get an error:
>
> make menuconfig
> HOSTCC script/kconfig/mconf.o
> : internal compiler error: Illegal instruction
>
> Even if I try to run: emerge --info I g
On Monday, 23 November 2020 01:09:16 GMT the...@sys-concept.com wrote:
> On 11/22/2020 05:25 PM, Michael wrote:
> > Do you have both disks connected to the MoBo when you're trying to boot
> > from the new disk?
>
> Yes, they are both connected
In this case the /dev/sda* you see could well be on
On Sun, 22 Nov 2020 18:27:53 -0700, the...@sys-concept.com wrote:
> > I would confirm that you are really booted from the new disk and not
> > the old one. It is possible that the MBR from the new disk was used
> > to boot, but if /etc/fstab says /boot is mounted from /dev/sda1 then
> > that does
23 matches
Mail list logo
