From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id B2DC41FF15C for ; Fri, 8 Aug 2025 10:45:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BC68E10CA5; Fri, 8 Aug 2025 10:47:17 +0200 (CEST) Date: Fri, 08 Aug 2025 10:46:40 +0200 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= To: pve-devel@lists.proxmox.com References: <401fb203-dc01-451c-89f1-ae148040e0b9@gulya.me> In-Reply-To: <401fb203-dc01-451c-89f1-ae148040e0b9@gulya.me> MIME-Version: 1.0 User-Agent: astroid/0.17.0 (https://github.com/astroidmail/astroid) Message-Id: <1754642580.9yu7vgyf68.astroid@yuna.none> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754642779759 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.049 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_SHORT 0.001 Use of a URL Shortener for very short URL RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com, ibug.io] Subject: Re: [pve-devel] Installer eMMC support contribution X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Cc: Ilya Gulya Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On August 5, 2025 8:23 am, Ilya Gulya wrote: > Hi! > > Currently Proxmox VE installer lacks support for installing on eMMC > (/dev/mmcblk). > > Users have to manually patch the installer code to make this happen: > > https://ibug.io/blog/2022/03/install-proxmox-ve-emmc/ > > I would like to contribute this to the Proxmox installer so that this no > longer required to be done by end users. > > Is it okay and what is the proper way to contribute? in the past, we've been a bit wary about supporting such devices because PVE is quite write intensive on /, and many such devices quickly wear out and fail.. I think there are more stable eMMC options around nowadays, so maybe we could include such a patch if it also adds a warning that this might be dangerous depending on the concrete hardware that is used? in general, you can find information on how to contribute patches to any of our projects here: https://pve.proxmox.com/wiki/Developer_Documentation in particular, the CLA part at the bottom is an important pre-requisite! thanks, Fabian _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel