10:43 <DC-IRC> [Discord] <human_urostor> I have a question about how the framework works. Right now, as I understand it there are 2 ways to configure the kernel. One is via issuing "kernel-config", another via running "compile.sh" and then tapping "Show a kernel configuration menu before compilation" (BTW this is ungrammatical - it should be "the kernel configuration menu". I think the second way is not supported now. S <clipped message>

10:43 <DC-IRC> [Discord] <human_urostor> hould it not just be removed?

10:43 <DC-IRC> [Discord] <human_urostor> I have a question about how the framework works. Right now, as I understand it there are 2 ways to configure the kernel. One is via issuing "kernel-config", another via running "compile.sh" and then tapping "Show a kernel configuration menu before compilation" (BTW this is ungrammatical - it should be "the kernel configuration menu"). I think the second way is not supported now. <clipped message>

10:43 <DC-IRC> [Discord] <human_urostor> Should it not just be removed?

10:49 <DC-IRC> [Discord] <Werner> Back in framework v1 KERNEL_CONFIGURE=yes was the way to go. At first place this was removed entirely in v2 but then was brought back to some extend due to backlash from users which were used to (me including lol) but I think it was marked deprecated since then. From developer perspective the `kernel-patch` way is better. From end-user POV `KERNEL_CONFIGURE` is more convenient.

10:56 <DC-IRC> [Discord] <human_urostor> But don't they break each other? ie isn't the config stored in a different file?

10:56 <DC-IRC> [Discord] <Werner> I don't know where KERNEL_CONFIGURE stores

10:59 <DC-IRC> [Discord] <human_urostor> I think there was some incompatibility. May be wrong, I stopped using this a while ago

11:52 <DC-IRC> [Discord] <rpardini> The files/mechanism is the same.

11:52 <DC-IRC> [Discord] <rpardini> The difference is in timing: when using `kernel-config`, only that (the actual configuration + file changes) is done and then process end. Only on the "next" build things will ever take effect.

11:52 <DC-IRC> [Discord] <rpardini> For `KERNEL_CONFIGURE=yes` (deprecated!), config is done "during" an image build which also has a kernel build, thus all the config-depend versions are invalid and forced to `000000` to enable that one invocation to somewhat work.

11:52 <DC-IRC> [Discord] <rpardini> It would be good to remove the deprecated way.

15:08 <DC-IRC> [Discord] <human_urostor> I see, there's someone in #ID:858684284070789130 who still uses it though. But armbian nicely deals with any differences in the compiled kernel so I think what he's doing may be unnecessary

15:12 <DC-IRC> [Discord] <rpardini> Person decides to eat glass, is told how that is bad multiple times, insists, then complains about bleeding. 🤷‍♂️

15:13 <DC-IRC> [Discord] <rpardini> yet another reason to completely remove it. (actually not remove, but check for old way trying to be used and explode).

15:14 <DC-IRC> [Discord] <Werner> `exit 1`. I mean it was marked deprecated for long enough

15:14 <DC-IRC> [Discord] <rpardini> `exit_with_error` but yes.

15:14 <DC-IRC> [Discord] <Werner> Guess the result is the same 😄

18:24 <DC-IRC> [Discord] <felix150147> Hi

18:32 <DC-IRC> [Discord] <Werner> hi

19:16 <DC-IRC> [Discord] <felix150147> Haw are you

20:35 <DC-IRC> [Discord] <wallex0100> I’ve been building in blockchain long enough to know that tooling matters just as much as ideas.

20:35 <DC-IRC> [Discord] <wallex0100> Most of my recent work is in **Solidity, TypeScript, Rust, Go, Python, Vyper, Cairo, Move, JavaScript, Bash, SQL, GraphQL, YAML, **.

20:35 <DC-IRC> [Discord] <wallex0100> I’ve shipped production systems across **Ethereum, Polygon, Optimism, Arbitrum, BNB Chain, Avalanche, Solana, Cosmos, Near, Aptos, Sui, Base, zkSync, Starknet, and Gnosis**.

20:35 <DC-IRC> [Discord] <wallex0100> On the platform side, I regularly work with **Hardhat, Foundry, Truffle, OpenZeppelin, The Graph, IPFS, Arweave, Alchemy, Infura, QuickNode, WalletConnect, MetaMask, Safe, Chainlink, Subgraph Studio, Docker, Kubernetes, and AWS**.

20:35 <DC-IRC> [Discord] <wallex0100> Most projects involve **smart contracts, gas optimization, audits, tokenomics, NFT marketplaces, AMMs, DAOs, bridges, oracles, indexers, dashboards, and governance systems**. I focus heavily on **security reviews, upgradeability, access control, and MEV awareness**.

20:35 <DC-IRC> [Discord] <wallex0100> Frontends are typically **React or Next.js**, with wallet-based auth and clean UX. Backends usually include **event-driven indexing, caching, and analytics pipelines**.

20:35 <DC-IRC> [Discord] <wallex0100> I prefer designing systems that survive scale rather than demos that break on mainnet. If you’re building something serious and want clean architecture from day one, happy to talk.

23:10 <_unreal_> trying to find a non klipper build for the BTT Pi V1.2.1