Building Linux on a ram disk with 64 cores goes SCAT.

(I think terminal display speed may be slowing it down!)

--
-v

On Sat, 04 May 2024 03:26:56 +0000, 🌈💐🌻🌺🌹🌻💐🌷🌺🌈Jen🌈💐🌻🌺🌹🌻💐
🌷🌺🌈 Dershmender
💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 <root@127.0.0.1> wrote in
<=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?=3DF0=3D9F=3D8C=3DBA?
=3DxFO7FKIsCGqIcl0@41.95.18.241=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?
=3DF0=3D9F=3D8C=3DBA?=3D>:

> So redirect stdin and stderr to a file on ram disk, then.

Now how is it I don't have you kf'ed here?

You are correct: And nohup(1) does the dirty work.

Next problem is, I had to copy the Linux source tree
back to the NAS before rebooting...and that seems
to take longer than the build(!).

Anyway:

$ uname -a
Linux lm 6.8.9 #1 SMP PREEMPT_DYNAMIC Fri May 3 19:22:25 PDT 2024 x86_64
x86_64 x86_64 GNU/Linux

Now it's time for some high-performance computing with
realtime graphics rendering... (Got a few things I'm
doing with the background galaxy simulation (BGS).)

A ship I've parked for now:

https://imgur.com/pB0Xtk0

--
-v

On Sat, 4 May 2024 04:16:33 -0000 (UTC), vallor wrote:

> ... nohup(1) does the dirty work.

setsid > nohup.

On Sat, 4 May 2024 04:42:24 -0000 (UTC), Lawrence D'Oliveiro
<ldo@nz.invalid> wrote in <v14ebg$11iqd$1@dont-email.me>:

> On Sat, 4 May 2024 04:16:33 -0000 (UTC), vallor wrote:
>
>> ... nohup(1) does the dirty work.
>
> setsid > nohup.

I'm surprised at you.

The idea is that nohup(1) is a lazy way to redirect
all the output. Basically, "> nohup.out 2>&1"

setsid(1) does not do that.

--
-v

On Sat, 04 May 2024 09:58:26 +0000, 🌈💐🌻🌺🌹🌻💐🌷🌺🌈Jen🌈💐🌻🌺🌹🌻💐
🌷🌺🌈 Dershmender
💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 <root@127.0.0.1> wrote in
<=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?=3DF0=3D9F=3D8C=3DBA?
=3Dgjl74YZUzrZ04$1@236.14.59.32=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?
=3DF0=3D9F=3D8C=3DBA?=3D>:

> On Sat, 4 May 2024 04:16:33 -0000 (UTC), LO AND BEHOLD; vallor
> <vallor@cultnix.org> determined that the following was of great
> importance to vallor <vallor@cultnix.org> and subsequently decided to
> freely share it with us in <v14cr0$10vd5$1@dont-email.me>:
>> Now how is it I don't have you kf'ed
> here?
>
> Now how is it that I DON'T GIVE A FUCK, SCOTT.

I can tell by the all-caps how much you "don't
give a fuck".

>> You are correct: And nohup(1) does the
>> dirty work.
>
> No i wasn't.

Okay, you weren't.

> It's stdout.

What about it?

nohup(1) automagically redirects stdout and stderr.

>> Next problem is, I had to copy the
>> Linux source tree back to the NAS
>> before rebooting...and that seems to take longer than the build(!).
>
> Perhaps you've found why there's no economy in "faster builds", but I
> suspect you'll carry on...

Nobody said anything about economy -- I'm just wrenching
on my hot rod.

>> A ship I've parked for now:
>>
>> https://imgur.com/pB0Xtk0
>
> Don't get mad that I'm not interested in your fantastic
> "time suck" and won't be clicking.

Except you were interested enough to say something about
it.

"Try not to think about an elephant."

So...why are you in a Linux advocacy group, except to
follow me around, Ms. Stalker?

ObLinux: I knew about lscpu(1), didn't know about lsmem(1):

$ lsmem
RANGE SIZE STATE REMOVABLE BLOCK
0x0000000000000000-0x000000407fffffff 258G online yes 0-128

Memory block size: 2G
Total online memory: 258G
Total offline memory: 0B

--
-v

On Sat, 04 May 2024 23:52:46 +0000, 🌈💐🌻🌺🌹🌻💐🌷🌺🌈Jen🌈💐🌻🌺🌹🌻💐
🌷🌺🌈 Dershmender
💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 <root@127.0.0.1> wrote in
<=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?=3DF0=3D9F=3D8C=3DBA?
=3DKCLHYs2.jAkJQ8$@45.203.143.5=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?
=3DF0=3D9F=3D8C=3DBA?=3D>:

> On Sat, 4 May 2024 22:49:22 -0000 (UTC), LO AND BEHOLD; vallor
> <vallor@cultnix.org> determined that the following was of great
> importance to vallor <vallor@cultnix.org> and subsequently decided to
> freely share it with us in <v16e1i$1e3ds$3@dont-email.me>:
>
>
> Are you trying to be a usenet newsgroup gatekeeping Edgelord again?

No. Would be wonderful if you'd talk more about Linux, and
less about me. Up to you, of course.

> I've been using Linux since 1996 and before that it was
> VAX/Ultrix/SparcOS/SunOs. Not much DOS. Just Apple ][e/][GS. I
> whitehat hacked some Novell in high school.

Our high school computer lab had Apple ][+'s connected
to a Corvus hard drive, a whopping 20MB of storage. The
OS had a fundamental insecurity that was a bit of a
bother: one could type "CATALOG V###" to change
to someone else's volume. I patched the Corvus DOS 3.3
RWTS routine to reset the computer if people tried that
trick. This turned into a bit of an "arms race", where
I think those involved learned more about computing than
the Pascal programs we were writing for AP Computer Science.

This has nothing to do with Linux, of course. Are you satisfied?

> One thing I can tell you about straying away from distro-supplied
> kernels is that you're eventually going to break something

I didn't realize you were a soothsayer.

I'm not doing anything I haven't done for many years previous
to running Mint. (There was a bit of a hiatus when I started
running Mint, but now the "bug" has bit me again.)

The only difference between then and now is that I'm posting
more about building kernels and running them. I've been scanning
the patches and reading the release notes, which more often than not I
used to forgo. (Linus has a policy of not changing syscalls without
very good reason because he doesn't like to break userspace.)

> and possibly
> brick your system pretty well when some low level driver compiles but
> doesn't catch all of its proper dependencies and linking library
> versions and nobody has caught it because 97% of the user base went
> through the documented distro upgrade paths and testing phases whereas
> you like to "live dangerously".

(That was a long sentence, and I'm not sure I understand it...)

Low-level drivers aren't linked against userspace libraries. Probably
the biggest issue would be the version of gcc I'm using (11) -- but
if a kernel doesn't boot, I can use grub to boot an earlier kernel.
(I'd like to build with "-march=native" at some point, but that's
slightly outside of my comfort zone right now.)

>
> Hope you have good and recent backups.

Yes, I have Timeshift keeping backups on a separate drive, and that
gets backed up to the NAS. Protip: Timeshift doesn't back up one's
home directory, so I have a cron job that rsyncs /home to
the NAS.

I will note that the biggest issue I've had with Linux itself
was with btrfs, which I once used for my / partition. It
got itself into a state where it couldn't be repaired. Someday
I may try it again -- say in five years? (Beats me.)

--
-v

🌈💐🌻🌺🌹🌻💐🌷🌺🌈 Jen 🌈💐🌻🌺🌹🌻💐🌷🌺🌈 Dershmender
💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 wrote:
> On Sun, 5 May 2024 01:37:13 -0000 (UTC), LO AND BEHOLD; vallor
> <vallor@cultnix.org> determined that the following was of great
> importance to vallor <vallor@cultnix.org> and subsequently decided to
> freely share it with us in <v16ns9$1fto9$1@dont-email.me>:
>
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= On Sat, 04 May 2024 23:52:46 +0000,
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= 🌈💐🌻🌺🌹🌻💐🌷🌺🌈Jen🌈💐🌻🌺🌹🌻💐
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= 🌷🌺🌈 Dershmender
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= 💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= 🌺🌈 <root@127.0.0.1> wrote in
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= <=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?=3DF0=3D9F=3D8C=3DBA?
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =3DKCLHYs2.jAkJQ8$@45.203.143.5=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =3DF0=3D9F=3D8C=3DBA?=3D>:
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= On Sat, 4 May 2024 22:49:22 -0000 (UTC), LO AND BEHOLD; vallor
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= <vallor@cultnix.org> determined that the following was of great
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= importance to vallor <vallor@cultnix.org> and subsequently decided to
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= freely share it with us in <v16e1i$1e3ds$3@dont-email.me>: Are you
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= trying to be a usenet newsgroup gatekeeping Edgelord again?
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= No. Would be wonderful if you'd talk more about Linux,
>
> Pay me, then.
>
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= and less about
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= me. Up to you, of course.
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= I've been using Linux since 1996 and before that it was
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= VAX/Ultrix/SparcOS/SunOs. Not much DOS. Just Apple ][e/][GS. I
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= whitehat hacked some Novell in high school.
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= Our high school computer lab had Apple ][+'s connected to a Corvus hard
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= drive, a whopping 20MB of storage. The OS had a fundamental insecurity
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= that was a bit of a bother: one could type "CATALOG V###" to change to
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= someone else's volume. I patched the Corvus DOS 3.3 RWTS routine to
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= reset the computer if people tried that trick. This turned into a bit
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= of an "arms race", where I think those involved learned more about
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= computing than the Pascal programs we were writing for AP Computer
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= Science.
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= This has nothing to do with Linux, of course. Are you satisfied?
>
> Are you talking to me or yourself?
>
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= One thing I can tell you about straying away from distro-supplied
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= kernels is that you're eventually going to break something
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= I didn't realize you were a soothsayer.
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= I'm not doing anything I haven't done for many years previous to running
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= Mint. (There was a bit of a hiatus when I started running Mint, but
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= now the "bug" has bit me again.)
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= The only difference between then and now is that I'm posting more about
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= building kernels and running them. I've been scanning the patches and
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= reading the release notes, which more often than not I used to forgo.
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= (Linus has a policy of not changing syscalls without very good reason
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= because he doesn't like to break userspace.)
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= and possibly brick your system pretty well when some low level driver
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= compiles but doesn't catch all of its proper dependencies and linking
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= library versions and nobody has caught it because 97% of the user base
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= went through the documented distro upgrade paths and testing phases
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= whereas you like to "live dangerously".
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= (That was a long sentence, and I'm not sure I understand it...)
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= Low-level drivers aren't linked against userspace libraries. Probably
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= the biggest issue would be the version of gcc I'm using (11) -- but if
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= a kernel doesn't boot, I can use grub to boot an earlier kernel. (I'd
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= like to build with "-march=native" at some point, but that's slightly
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= outside of my comfort zone right now.)
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= Hope you have good and recent backups.
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= Yes, I have Timeshift keeping backups on a separate drive, and that gets
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= backed up to the NAS. Protip: Timeshift doesn't back up one's home
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= directory, so I have a cron job that rsyncs /home to the NAS.
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= I will note that the biggest issue I've had with Linux itself was with
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= btrfs, which I once used for my / partition. It got itself into a
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= state where it couldn't be repaired. Someday I may try it again -- say
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?= in five years? (Beats me.)
> =?UTF-8?B?8J+Ps++4j+KAjfCfjIg=?=
>
> I wouldn't waste my time. Whatever is the default fs for your distro for / is what you should use and xfs is all that anyone needs for extremely large volumes who demands reliability, last I heard.
>
> I don't use Linux as a "playground" though, I use it to solve real-world mission-critical stuff that operates 24/7/365.
>
> You and Snit can have a Snit-off, IDC.
>
you left out the checkmate

On Sun, 5 May 2024 01:37:13 -0000 (UTC), vallor wrote:

> I will note that the biggest issue I've had with Linux itself was with
> btrfs, which I once used for my / partition. It got itself into a state
> where it couldn't be repaired. Someday I may try it again -- say in
> five years? (Beats me.)

My OpenSUSE 13.2 install defaulted to btrfs and it didn't go well. It
would start to boot and go off to a black screen. I reformatted to ext4
which worked perfectly and never looked back. I'd been using reiserfs but
there was some sort of problem with the way Reiser solved his marital
problems that orphaned the project.

On 5/4/2024 11:11 PM, rbowman wrote:

> there was some sort of problem with the way Reiser solved his marital
> problems that orphaned the project.

He choked his wife out, and later said he was embarrassed at the
chokehold technique he used. What a Linux man!

I met Reiser's father Ramon in a Barnes & Noble bookstore in Snellville
GA a while back. Chatted with him for about 10 minutes.

Very nice, but a kook. Insisted Hans was innocent.

On 5 May 2024 03:11:37 GMT, rbowman <bowman@montana.com> wrote in
<l9obn9FnjifU1@mid.individual.net>:

> On Sun, 5 May 2024 01:37:13 -0000 (UTC), vallor wrote:
>
>> I will note that the biggest issue I've had with Linux itself was with
>> btrfs, which I once used for my / partition. It got itself into a
>> state where it couldn't be repaired. Someday I may try it again -- say
>> in five years? (Beats me.)
>
> My OpenSUSE 13.2 install defaulted to btrfs and it didn't go well. It
> would start to boot and go off to a black screen. I reformatted to ext4
> which worked perfectly and never looked back. I'd been using reiserfs
> but there was some sort of problem with the way Reiser solved his
> marital problems that orphaned the project.

Linux Mint has btrfs as an option for / on installation. The snapshot
feature is why I wanted to try it.

Now I use ext4.

--
-v

On 2024-05-05, rbowman wrote:
> On Sun, 5 May 2024 01:37:13 -0000 (UTC), vallor wrote:
>
>> I will note that the biggest issue I've had with Linux itself was with
>> btrfs, which I once used for my / partition. It got itself into a state
>> where it couldn't be repaired. Someday I may try it again -- say in
>> five years? (Beats me.)
>
> My OpenSUSE 13.2 install defaulted to btrfs and it didn't go well. It
> would start to boot and go off to a black screen. I reformatted to ext4
> which worked perfectly and never looked back. I'd been using reiserfs but
> there was some sort of problem with the way Reiser solved his marital
> problems that orphaned the project.
Well, yes, that was a major factor in continuing both with the project and also
deciding if you wanted to utilise his work.

--
Simon

RLU: 222126

On 2024-05-04 11:30 p.m., DFS wrote:
> On 5/4/2024 11:11 PM, rbowman wrote:
>
>> there was some sort of problem with the way Reiser solved his marital
>> problems that orphaned the project.
>
>
> He choked his wife out, and later said he was embarrassed at the
> chokehold technique he used.  What a Linux man!

Was it an unethical choking hold?

> I met Reiser's father Ramon in a Barnes & Noble bookstore in Snellville
> GA a while back.  Chatted with him for about 10 minutes.
>
> Very nice, but a kook.  Insisted Hans was innocent.

Was this a random encounter? How did you just randomly bump into the
father or a convicted murderer?

--
Andrzej (Andre) Matuch
TG: @AndrzejMatuch
Catholic, paleoconservative, Christ is king.

On 5/5/2024 8:03 AM, Andrzej Matuch wrote:
> On 2024-05-04 11:30 p.m., DFS wrote:
>> On 5/4/2024 11:11 PM, rbowman wrote:
>>
>>> there was some sort of problem with the way Reiser solved his marital
>>> problems that orphaned the project.
>>
>>
>> He choked his wife out, and later said he was embarrassed at the
>> chokehold technique he used.  What a Linux man!
>
> Was it an unethical choking hold?

It was from behind. And it was also notable because he was the first
Linux dweeb to ever have a wife.

>> I met Reiser's father Ramon in a Barnes & Noble bookstore in
>> Snellville GA a while back.  Chatted with him for about 10 minutes.
>>
>> Very nice, but a kook.  Insisted Hans was innocent.
>
> Was this a random encounter? How did you just randomly bump into the
> father or a convicted murderer?

Completely random. Jan 2020, so a little over 4 years ago.

And he spoke to me first, while I was browsing the music mags (which are
off-camera to the left - see pic below). He quickly brought up his
son's predicament, without saying any names, and after a short while I
realized he was talking about Hans Reiser. We still hadn't introduced
ourselves, but I remember saying "Then you're Hans Reiser's father."

He said Hans and [murdered ex-wife] Nina's conflicts started over her
wanting 80% of the company. Said she embezzled $250K blah blah blah.
Said she and her boyfriend were grooming the kids, etc etc. Mentioned
the name Rory several times (their oldest child).

He let me take a pic: https://imgur.com/a/lYKNO1g

Notice there's a cane/crutch near his right hand, and he's hiding his
right leg. It's because it was amputated just above the knee. Bus
accident as I recall.

On 5/4/2024 9:58 PM, Jen Dershmender wrote:
> vallor <vallor@cultnix.org> wrote:

>> Would be wonderful if you'd talk more about Linux,
>
> Pay me, then.

How about you and the rest of you checkmate lusers pay everyone on cola
for your stupid, irrelevant crossposts, and your stupid names?

🌈💐🌻🌺🌹🌻💐🌷🌺🌈 Jen 🌈💐🌻🌺🌹🌻💐🌷🌺🌈 Dershmender
💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 <root@127.0.0.1>

What an idiot. Stay out.

On 2024-05-05, rbowman <bowman@montana.com> wrote:
> On Sun, 5 May 2024 01:37:13 -0000 (UTC), vallor wrote:
>
>> I will note that the biggest issue I've had with Linux itself was with
>> btrfs, which I once used for my / partition. It got itself into a state
>> where it couldn't be repaired. Someday I may try it again -- say in
>> five years? (Beats me.)
>
> My OpenSUSE 13.2 install defaulted to btrfs and it didn't go well. It
> would start to boot and go off to a black screen. I reformatted to ext4
> which worked perfectly and never looked back. I'd been using reiserfs but
> there was some sort of problem with the way Reiser solved his marital
> problems that orphaned the project.

If I remember right, my Fedora 39 installation used btrfs by default. It
seems to be working fine. (Let me double check that.) ...

Yes, the main partition is btrfs. I'm not smart enough to know the
difference.

--
[Self-centered, Woke] "pride is a life of self-destructive fakery, an
entrapment to a false and self-created matrix of twisted unreality."
"It was pride that changed angels into devils..." — St. Augustine

On 2024-05-05 9:29 a.m., DFS wrote:
> On 5/5/2024 8:03 AM, Andrzej Matuch wrote:
>> On 2024-05-04 11:30 p.m., DFS wrote:
>>> On 5/4/2024 11:11 PM, rbowman wrote:
>>>
>>>> there was some sort of problem with the way Reiser solved his marital
>>>> problems that orphaned the project.
>>>
>>>
>>> He choked his wife out, and later said he was embarrassed at the
>>> chokehold technique he used.  What a Linux man!
>>
>> Was it an unethical choking hold?
>
> It was from behind.  And it was also notable because he was the first
> Linux dweeb to ever have a wife.
>
>
>>> I met Reiser's father Ramon in a Barnes & Noble bookstore in
>>> Snellville GA a while back.  Chatted with him for about 10 minutes.
>>>
>>> Very nice, but a kook.  Insisted Hans was innocent.
>>
>> Was this a random encounter? How did you just randomly bump into the
>> father or a convicted murderer?
>
>
> Completely random.  Jan 2020, so a little over 4 years ago.
>
> And he spoke to me first, while I was browsing the music mags (which are
> off-camera to the left - see pic below).  He quickly brought up his
> son's predicament, without saying any names, and after a short while I
> realized he was talking about Hans Reiser.  We still hadn't introduced
> ourselves, but I remember saying "Then you're Hans Reiser's father."
>
> He said Hans and [murdered ex-wife] Nina's conflicts started over her
> wanting 80% of the company.  Said she embezzled $250K blah blah blah.
> Said she and her boyfriend were grooming the kids, etc etc.  Mentioned
> the name Rory several times (their oldest child).
>
> He let me take a pic:  https://imgur.com/a/lYKNO1g
>
> Notice there's a cane/crutch near his right hand, and he's hiding his
> right leg.  It's because it was amputated just above the knee.  Bus
> accident as I recall.

It's quite possible that he's telling the truth and that there is lots
more to the story of Hans Reiser. The fact remains that he killed his
wife though. Regardless of the background, he committed the deed.

--
Andrzej (Andre) Matuch
TG: @AndrzejMatuch
Catholic, paleoconservative, Christ is king.

On Sun, 05 May 2024 13:19:28 +0000, Jen wrote:

> If you want snapshots just use LVM.

That isn't an option when installing Linux Mint.

(I'm happy using Timeshift to rsync to physically-separate
media -- safer that way, they are "real" backups.)

--
-v

On Sun, 5 May 2024 15:21:31 -0000 (UTC), RonB wrote:

> If I remember right, my Fedora 39 installation used btrfs by default. It
> seems to be working fine. (Let me double check that.) ...
>
> Yes, the main partition is btrfs. I'm not smart enough to know the
> difference.
>

My Fedora 40 is also btfrs for the main but /boot is ext4. The Ubuntu box
came with Windows 11 so it has /boot/efi which is vfat. The Fedora box is
the old Dell before UEFI was a thing.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/
html/installation_guide/s2-diskpartrecommend-x86

"The /boot and / (root) partition in Red Hat Enterprise Linux 6.9 can only
use the ext2, ext3, and ext4 (recommended) file systems. You cannot use
any other file system for this partition, such as Btrfs, XFS, or VFAT. "

Interesting. I did the OpenSUSE install as a dual boot with Windows 7. The
symptom was it got as far as grub and went into outer space. I didn't do a
lot of research at the time, just changed to ext4. Ironically SUSE was
one of the early adopters of reiserfs.
File systems are another one of those things I don't worry about as long
as they work. It's been a while since I've done anything other than point
the installer at the drive and let it do its own thing.

Why haven't any of you propeller heads tried an NTFS distro ?

Relf <Usenet@Jeff-Relf.Me> wrote at 20:25 this Sunday (GMT):
> Why haven't any of you propeller heads tried an NTFS distro ?

Because NTFS isn't as supported as most filesystems.
--
user <candycane> is generated from /dev/urandom

On Sun, 05 May 2024 13:25:27 -0700 (Seattle), Relf wrote:

> Why haven't any of you propeller heads tried an NTFS distro ?

https://www.theregister.com/2021/10/13/how_ntfs_finally_made_it/

You (rBowman) replied ( to me ):
> > Why haven't any of you propeller heads tried an NTFS distro ?
>
> https://www.theregister.com/2021/10/13/how_ntfs_finally_made_it/

No one has tried it, apparently.

"Relf" <Usenet@Jeff-Relf.Me> wrote:

>You (rBowman) replied ( to me ):
>> > Why haven't any of you propeller heads tried an NTFS distro ?
>>
>> https://www.theregister.com/2021/10/13/how_ntfs_finally_made_it/
>
>No one has tried it, apparently.

https://www.paragon-software.com/us/home/ntfs-linux-professional/#

--
Joel W. Crump

Amendment XIV
Section 1.

[...] No state shall make or enforce any law which shall
abridge the privileges or immunities of citizens of the
United States; nor shall any state deprive any person of
life, liberty, or property, without due process of law;
nor deny to any person within its jurisdiction the equal
protection of the laws.

Dobbs rewrites this, it is invalid precedent. States are
liable for denying needed abortions, e.g. TX.

You (Crump) replied ( to me ):
> > > > Why haven't any of you propeller heads tried an NTFS distro ?
>
> https://www.paragon-software.com/us/home/ntfs-linux-professional/#

That's proprietary software that lets you mount an NTFS drive.

You can't name an NTFS distro.

"Relf" <Usenet@Jeff-Relf.Me> wrote:

>You (Crump) replied ( to me ):
>> > > > Why haven't any of you propeller heads tried an NTFS distro ?
>>
>> https://www.paragon-software.com/us/home/ntfs-linux-professional/#
>
>That's proprietary software that lets you mount an NTFS drive.

It provides support more so than the open source NTFS driver.

>You can't name an NTFS distro.

Don't need one.

--
Joel W. Crump

Amendment XIV
Section 1.

[...] No state shall make or enforce any law which shall
abridge the privileges or immunities of citizens of the
United States; nor shall any state deprive any person of
life, liberty, or property, without due process of law;
nor deny to any person within its jurisdiction the equal
protection of the laws.

Dobbs rewrites this, it is invalid precedent. States are
liable for denying needed abortions, e.g. TX.