All of lore.kernel.org
 help / color / mirror / Atom feed
From: keypair@tuta.io
To: Isaac Gonzalez <uribiel.gc@gmail.com>
Cc: Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Development environment discussion
Date: Wed, 17 Dec 2025 17:39:44 +0100 (CET)	[thread overview]
Message-ID: <OghAcaz--R-9@tuta.io> (raw)
In-Reply-To: <CABPNkoV6Di91sS0Pe_mpTNm2va8cJ4xYWJtDiBJaHNXPirhBBg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1029 bytes --]

Why would you use a mac for kernel dev? That's a horrible choice. Stick with bare metal linux.


Dec 17, 2025, 20:21 by uribiel.gc@gmail.com:

> Hello everyone, 
>
> I'm new posting to the newbies kernel list and currently learning kernel driver and subsystem development. 
>
> I am considering working on a Macbook air with virtual machines for my learning and experimentation process. Is it reasonable or would it be better to consider native development, especially while working remotely?
>
> I plan to use the macbook as a remote development environment with tools to work on code inside virtual machines and remotely (ssh) to a desktop with Ubuntu 24. It has been cumbersome getting the kernel to build due to configurations in Ubuntu for certificates which do not exist in the mainline kernel so any suggestions on any other host OS are appreciated. I have no issues switching between distributions and consider it a great part of the development learning process. 
>
> Thanks,
> Isaac Gonzalez
>


[-- Attachment #1.2: Type: text/html, Size: 2056 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2025-12-17 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 14:49 Development environment discussion Isaac Gonzalez
2025-12-17 16:39 ` keypair [this message]
2025-12-17 17:44   ` Billie Alsup (balsup)
2025-12-18  2:41     ` Isaac Gonzalez
2025-12-18  8:26 ` Louis
2025-12-18 13:50   ` keypair
2025-12-18 16:02     ` Raka Gunarto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OghAcaz--R-9@tuta.io \
    --to=keypair@tuta.io \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=uribiel.gc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.