Recent Posts

1

Operating Systems and Porting / Re: Swiss finance regulator FINMA deputy CEO resigns, collateral damage from Debian?

« Last post by pocock on February 04, 2026, 04:56:10 pm »

If you are going to advocate for free speech, don't shut it down when others present information that disputes your positions.

You spoke and then you spoke the same thing again.  The first time you say something it is free speech but if you repeat it over again in two other threads it is a waste of disk space.

I do find it disingenuous that you were raising the issue of Google "astroturfing" when you characterize yourself as a "Debian developer,"

I resigned from some voluntary activities at a time when I lost two family members.  That does not make me any less of a Debian Developer.  Anybody insisting on putting their petty crusades over the privacy of my family is less than a real human though.

That might lead one to think you are associated with Debian, but are not.  Perhaps not the same as astroturfing, but deceptive none-the-less.

Copyright law says I'm associated with Debian until 70 years after I die.  Anybody telling you otherwise is deceiving you about copyright.

I am concerned about the obsession you have with Debian.  It seems ...

If a woman says no to sex, do you say the woman has an obsession with virginity?

They are imposing upon the privacy of my family.  My family and I did not consent to discussions about abuse.  To start such a discussion at a time of grief is even more obscene.

As long as they violate that privacy, it is like a rape in progress.  The obsession is not on my part.  They unilaterally imposed this upon my family.

2

Operating Systems and Porting / Re: Swiss finance regulator FINMA deputy CEO resigns, collateral damage from Debian?

« Last post by TimKelly on February 04, 2026, 03:08:01 pm »

Daniel, you keep locking threads after you post, preventing anyone from discussing it with you.  You also seem to have a habit of characterizing those discussions as "lies" when the person presents contrary evidence.  If you are going to advocate for free speech, don't shut it down when others present information that disputes your positions.

I do find it disingenuous that you were raising the issue of Google "astroturfing" when you characterize yourself as a "Debian developer," or had until this most recent post, and that you were forced to turn over dozens of domains that used the Debian name in them.  That might lead one to think you are associated with Debian, but are not.  Perhaps not the same as astroturfing, but deceptive none-the-less.

I am concerned about the obsession you have with Debian.  It seems extremely unhealthy and likely fills you with negative energy, affecting your health, and perhaps your loved ones as well.  I believe you would do better by creating the world you want to see, instead of trying to destroy the one others have built.  In the case of Debian, I see nothing but a sincere effort to create an inclusive and supportive community that welcomes diversity.  That certainly is a world I would want to see.

If you must campaign against injustice, and some people are compelled to, I do not think Debian is an embodiment of evil, unlike the persons controlling Executive Branch of the U.S. government and in other countries.  You should raise your voice against the institutional corruption practiced daily by the President of the most powerful country in the world.  There are many other organizations who do much greater harm to the world than Debian, even if one were to contemplate that perhaps they do (I do not).  Your focus could reveal the inherent corruption in authoritarian governments with close ties to large corporations that profit from such arrangements.

I do hope you find help for your needs, and I also hope that you see that many vulnerable people may be drawn into your efforts.  It is unfortunate that the far-right uses such vulnerabilities in people to try to find new recruits.  It seems that hate hates being alone, and I hope that is not your motivation.

tim
 

3

Operating Systems and Porting / Swiss finance regulator FINMA deputy CEO resigns, collateral damage from Debian?

« Last post by pocock on February 04, 2026, 01:57:33 pm »

When the Debianists first attacked the Software Freedom Institute in November 2021, I asked the legal insurance provider to assist me.  They failed to do their job.  I only publish this here because other people have raised questions about judgments.  In fact, there was no valid judgment.  In the absence of legal insurance, I simply canceled the trademark and neutralized the dispute.

If there are legal fees to be paid or reimbursed, the money should have been paid by the insurance company.

Moreover, I was able to prove the financial regulator knew about deficiencies in the illegal legal insurance scheme for a very long time.

I published the most compelling evidence between January 2025 and March 2025 on the site JuristGate.com.  Not only did the regulator fail to protect the public but it looks like they even took an active role in the cover up too.

The head of insurance supervision, who was also deputy head of FINMA, resigned after I put the emphasis on the cover-up.  They did not provide a reason for the resignation.  So I simply published the sequence of events and I let people draw their own conclusions about whether she resigned due to the way I reverse engineered a cover-up.

MIT DEDP MicroMasters online learner's blog post about cover-up linked to resignation of Swiss financial regulator

4

Operating Systems and Porting / Re: $15B federal lawsuit vs. Google astroturfing in open source communities

« Last post by pocock on February 04, 2026, 12:28:37 pm »

Welcome back, Daniel!  I was disappointed when you closed the thread containing our previous conversation.

You repeated the same lies multiple times and you have done so again here.  It is not productive for me to correct the same lies twice.

You left after I pointed out that your lawsuits, of which this is another, have forced Debian to spend a great deal of money, some of which might have been spent on lifejackets and prevented the drowning death of a volunteer at a Debian event.

When Chris Lamb attacked my family and I in September 2018, I asked him to meet me in person to discuss his concerns.  He refused to look me in the eye and spent many months writing nasty emails behind my back.  Various people disclosed some of them to me.

If the leader doesn't have time to look people in the eye then he can always resign and let somebody else do the job.

Just a reminder, you are continuing to use "Debian developer" in your signature in these forums, even though you were stripped of official developer status quite some time ago.  One might feel this is a misrepresentation of your position within the Debian community.

Under Copyright law, developers can sell our rights to other parties but nobody can be stripped of their right to recognition.  People making such claims are gaslighting.

Speaking of which, after our previous conversation wrapped up, I was able to also correspond with Tiago Bortoletto Vaz, who is an actual Debian developer.  He reviewed our correspondence, and besides confirming that Debian has tried to reconcile and mediate with you,

If he made such a claim, please ask him to publish the relevant correspondence.  I certainly haven't seen it.

he confirmed Debian has also spent a great deal of money defending against your assaults on them.

Assault is a serious crime.  There was no assault.  I published the original messages when Lamb started this dispute.  There is nothing in there about an assault.

The dead developers indicated they were under pressure from the group culture.  Read their emails.

  We were also able to discuss Debian attempting to offer mental health counseling for its community members, although I do not know if there was any follow-through on their part.

They originally discussed the need for group therapy due to their toxic culture.  They had that discussion shortly after Jens Schmalzinger died and before the Debian suicide cluster was in full swing.  The fact they knew the group needed therapy may increase their culpability in relation to the deaths after the psychiatrist discussion.  See the email I found on debian-private

They keep having to spend money defending against lawsuits, even some filed in European countries (both of which you lost).

I did not lose any lawsuit.  I canceled the trademark and so the lawsuit no longer had a purpose.

You say "both" lawsuits.  There was only one trademark lawsuit.

Remember, most organizations don't start lawsuits against a volunteer after the death of his father.  There is something very vindictive about the Debianists.  I told them they could simply apologize to my family and give me the $1,000 I paid for the trademark registration and that would have been the end of the dispute.  Instead, they chose to spend $120,000 because they wanted to scare everybody to be meek when Google employees are around.

You've had some pretty severe criticisms of alternative sexual orientations within the Debian community, as I recall.

No, that is not true.  In 2016, one of the other GSoC administrators, Nicolas Dandrimont, asked me to consider his partner for an Outreachy internship paid out of Debian funds.

The partner appears to be transgender, which raises very thorny ethical questions about giving money to an impressionable young person exploring their gender.  As money is involved it could be seen as grooming or indoctrination.  Some people would use stronger words to describe the presence of money in such a relationship.  There was a huge power imbalance between Dandrimont and his partner for multiple reasons: age difference, Dandrimont's status as an administrator, Dandrimont's involvement in DebConf travel opportunities/funding, the parallel employment in the CRANS lab. That is not the only problem.  The problem is also the obvious and insurmountable conflict of interest.

However, other transgenders started attacking me and spreading false rumours.  Then all the LGBT relationships were documented so people can see the conflicts of interest.  They attacked my family first and I have a right to defend myself whenever they do so.

Most of us don't care what they do in the bedroom.  When they gang up on straight people that is not fair and they create problems for themselves.

For example, you closed the thread to prevent any further discourse from me, after I brought up your support for authoritarian figures and the clearly unresolved feelings over the death of your father.

You started repeating the same points over and over again.  I posted my response to those points.  I did not delete any of the points you made, I left them intact for people to see your comments and my responses.  But it is pointless to continue a thread when you repeat the same points over and over again.

But I digress.  Back to your post.  In reviewing the link, I find that it appears to be a front for your campaign, not an actual independent effort.  I suggest readers review Daniel's past posts and campaigns, and consider if you are being misled about why you are being told the truth.

In this last comment, you do not give one example of how you think people are misled.  Therefore, it is not possible to engage in further discussion with you on whether I misled people or not.  People can watch the video for themselves.

5

Firmware / Migrating the build environment/true portability

« Last post by TimKelly on February 04, 2026, 12:04:30 pm »

Hi All,
I wanted to again express my appreciation to Raptor CS for access to the hardware. I used that access to do a lot of bare metal testing as well as access to the lowest levels of the firmware, in an effort to build a truly portable build environment.  This has been a fantastic learning experience.  I sent the following summary to Raptor a few months ago, but then took some time off from computers and failed to post the summary to the forums (unless my memory is worse than I remember).

I have done a lot of digging into the internal boot process, specifically the SBE, and while in theory the boot process can be replaced, in practice this appears to be extremely labor intensive.  I have been working with Public Domain POSIX Make

https://frippery.org/make/

to rewrite the Makefiles to be strict POSIX 2024.  The GNU syntax in the Makefiles ties the build process very closely to GNU toolchain.  They are not compatible with FreeBSD's make.  The solution is strict POSIX 2024, but there are 28 Makefiles and 30 .mk files that need to be rewritten.

Note that strict POSIX 2024 does not support out-of-tree building, where the source code is in one directory and the object files are in another.  The main cause (effect?) of this is that implicit target rules can not use variables, so $(OBJDIR).o: is not a valid target.  The IBM writers of the SBE Makefiles leaned very heavily on GNU's extensions, to the point where I would describe the effort as "lazy."  I suspect at least a few of the Makefiles were generated by scripts.

I have rewritten several Makefiles, enough to dig deeper into the SBE build process.  The C++ implementation/includes on FreeBSD are not compatible with Linux's C++ implementation.  The naming for #ifndef is different, leading to duplication of std functions.  In a particular case, xip, the two source files are .C, but one of them does not contain any C++ while the other only contains five lines total, out of 3,237 in the file.  That file fails to compile because of the duplicate:

In file included from p9_xip_tool.C:41:
In file included from /usr/include/c++/v1/string:591:
In file included from /usr/include/c++/v1/__algorithm/remove.h:12:
In file included from /usr/include/c++/v1/__algorithm/find.h:16:
In file included from /usr/include/c++/v1/__bit/countr.h:15:
In file included from /usr/include/c++/v1/__bit/rotate.h:15:
In file included from /usr/include/c++/v1/limits:581:
/home/tkelly/raptor/talos-sbe/src/import/chips/p9/procedures/ppe/pk/../include/std/type_traits:46:19: error: reference to 'integral_constant' is ambiguous
   46 |         const _Tp integral_constant<_Tp, __v>::value;
      |

This failure appears to trace to

std::string i_ddLevelStr;   //Same

which is used as

ddLevel = strtol(i_ddLevelStr.c_str(), NULL, 16);

or similar for a total of two assignments and four references.  Again, the word "lazy" comes to mind.

There are deeper uses of C++, of course, such as

numRingIds = P9_RID::NUM_RING_IDS;

The namespace for P9_RID can be found in

src/import/chips/p9/utils/imageProcs/p9_ringId.C

I do not see anything that could not have been accomplished with C99 or later.  I suspect these files were designed to be compatible with AIX and IBM's compiler, not to be portable.  I have never seen any C++ code that could not be accomplished with C and a simpler compiler.

There are 391 files in the SBE that have C++ :: operators, totaling 8,178 lines.  I do not see this as being readily portable to C, and as a result of conflicts with other operating system and compiler implementations of C++, not really portable at all.

The native Linux build environment for the SBE can not compile successfully.  I suspect that within Raptor the build environment has been steadily patched and an attempt to build from scratch has not been undertaken in some time.  I suspect that even simple changes upstream could have a devastating effect on Raptor, should it occur in certain places or if certain people leave (and their knowledge with them).  This is an unfortunately common experience, and in large software efforts can lead to terrible inertia.

The sheer complexity of the boot process and dependency on external parties leaves me with no choice but to stop development.  This is not an easy decision to make.  I am partial to PowerPC, and enjoy working so close to bare metal.  However, I can not see a path forward while maintaining the simplicity I am trying to implement.

I am deeply concerned about the performance limits with the RISC-V chips I have seen, but their simplicity and low cost offers the hint of a path forward.  Personally, I would really be excited to see Raptor hardware running multi-core RISC-V, if the "open" philosophy can be maintained.  I am deeply concerned that many of the major players in the RISC-V and Open Compute sphere are the very same players that have undermined openness in tech for decades.  I rarely find a RISC-V SBC that isn't actually tied to blobs required to run the proprietary peripherals, and even entire toolchains are vendor-dependent.  Don't even think about asking if the firmware can be replaced.

As I previously noted in another post, the SG2000 chip was actually a surprisingly good performer for the 1w of power it consumed, although something was clearly impeding it, possibly the i- and d-caches being very, very small.  However, Pine64 and Milk-V were able to deliver boards for as little as $13.

Say it was possible to scale up to a 64 RISC-V core like the SG2000 (which I think is embargoed in the U.S. now), and it consumed 64 watts at peak power.  From my (homemade real-world integer-based) benchmarks, it would take 1.4 times to complete a parallel task as would a 16 core Raptor system (running SMT4), at half the power consumption (each one takes 76 times the elapsed time on the 64 thread Raptor system).  To me this hints of a cost-effective opportunity to scale multi-CPU, with some hardware enhancements.  Just a thought.

Again, my many thanks to Raptor CS and their efforts.

tim

6

Operating Systems and Porting / Re: $15B federal lawsuit vs. Google astroturfing in open source communities

« Last post by TimKelly on February 04, 2026, 11:08:57 am »

Welcome back, Daniel!  I was disappointed when you closed the thread containing our previous conversation.  You left after I pointed out that your lawsuits, of which this is another, have forced Debian to spend a great deal of money, some of which might have been spent on lifejackets and prevented the drowning death of a volunteer at a Debian event.

Just a reminder, you are continuing to use "Debian developer" in your signature in these forums, even though you were stripped of official developer status quite some time ago.  One might feel this is a misrepresentation of your position within the Debian community.

Speaking of which, after our previous conversation wrapped up, I was able to also correspond with Tiago Bortoletto Vaz, who is an actual Debian developer.  He reviewed our correspondence, and besides confirming that Debian has tried to reconcile and mediate with you, he confirmed Debian has also spent a great deal of money defending against your assaults on them.  We were also able to discuss Debian attempting to offer mental health counseling for its community members, although I do not know if there was any follow-through on their part.  They keep having to spend money defending against lawsuits, even some filed in European countries (both of which you lost).

You and I can agree on the harm that Google is doing to open source movements.  In addition to accepting $1 billion from Israel in assisting in identifying "targets," otherwise known as Palestinians, Google subverts projects towards their own goals.  Firefox comes to mind.  Even simple traffic monitoring while using Firefox shows inappropriate traffic being sent to Google while using the browser.  I advise human rights defenders to avoid Mozilla products completely, as they can not be considered safe.

We can also agree on the dangers of censoring free speech, given that people are being executing in the U.S. and elsewhere for exercising their right to free speech.   Saying "Defend the Constitutional prohibitions against illegal search and seizures" gets one labeled a "domestic terrorist" and killed, while the people doing the executions are said to be the actual victims by the authoritarian government.  I am disappointed that the response by the public was different when the gun-packing white male was killed subsequent to the poetry-writing lesbian soccer mom.  You've had some pretty severe criticisms of alternative sexual orientations within the Debian community, as I recall.

Regretfully, many of those being targeted are done so at the hands of people you have defended in your blogs, and we do disagree over "free" vs. "hate" speech.  I am disappointed but not surprised how often the very people spewing hate while claiming free speech shut down free speech in opposition to authoritarian governments as soon as they have obtained the power to do so.  For example, you closed the thread to prevent any further discourse from me, after I brought up your support for authoritarian figures and the clearly unresolved feelings over the death of your father.

But I digress.  Back to your post.  In reviewing the link, I find that it appears to be a front for your campaign, not an actual independent effort.  I suggest readers review Daniel's past posts and campaigns, and consider if you are being misled about why you are being told the truth.

tim

7

Applications and Porting / Re: [GAMES] Doom 3 BFG bad ass game XD

« Last post by tle on February 04, 2026, 06:33:34 am »

I built dxc and it seems to be recognized by RBDOOM, but I'm getting a build error:
[ FAIL ] SPIRV builtin/lighting/interactionSM.vs.hlsl {main} {USE_GPU_SKINNING=1 LIGHT_POINT=1 LIGHT_PARALLEL=0 USE_PBR=1 USE_NORMAL_FMT_RGB8=1 USE_SHADOW_ATLAS=1}

I did not run into such issue,

```

# build dxc
git clone https://github.com/microsoft/DirectXShaderCompiler.git
cd DirectXShaderCompiler
git submodule update --init --recursive
mkdir build && cd build
cmake .. -C ../cmake/caches/PredefinedParams.cmake
make dxc -j
sudo make install-dxc
# build the shared library
make dxcompiler -j32
# install it
sudo make install-dxcompiler
# then update the library cache:
sudo ldconfig


# build game
git clone https://github.com/RobertBeckebans/RBDOOM-3-BFG.git
cd ./RBDOOM-3-BFG/
git submodule update --init --recursive
mkdir build && cd build
export DXC_CUSTOM_PATH=/usr/local/bin/dxc
../neo/cmake-linux-debug.sh
cd ../build
make -j32
```

8

Operating Systems and Porting / $15B federal lawsuit vs. Google astroturfing in open source communities

« Last post by pocock on February 03, 2026, 10:00:38 am »

GiveSendGo, which is known for resisting censorship and supporting controversial legal disputes, hosts a new crowdfunding campaign about social engineering and black money in open source communities, in other words, astroturfing.

Here is the link to share.  Some platforms are censoring it already.  It will only succeed if people use email, DM and other means to share the link.  The greylisting of this particular topic reveals a lot about social control media and the pestering campaigns.

https://www.givesendgo.com/censorship-privacy

The law suit has been filed in the same court hosting Nicolas Maduro. 70,000 internal emails from debian-private and diversity programs have been offered when crowdfunding milestones are reached, even if the case fails. Open source leaders will be subject to depositions about payments they received from the controlling corporations before denouncing various people over the years. Only if the community contributes enough money to fund the lawyers, they are not volunteers.

Click to see the video and campaign details

9

GPU Compute / Accelerators / Re: Intel Arc A770 - failed experiment

« Last post by lepidotos on January 30, 2026, 11:17:30 am »

I don't think anyone has tested it yet, did you end up doing so?

10

Applications and Porting / Re: [GAMES] Doom 3 BFG bad ass game XD

« Last post by power9mm on January 29, 2026, 01:09:41 pm »

dhewm3 starts for me to the main menu, but starting actual game crashes after loading the level.

yes this was my experience, I was able to load random maps and some i could play through them fully, try something like map game/mars_city2 for example. Another thing I had messed with was image_cachemegs as that sometimes would prevent crashes when set to a few GB or something. I posted my initial crash reports here https://github.com/dhewm/dhewm3/issues/508
When I have a PPC machine again I'm going to explore getting Half Life 2 to compile