Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #275930 > unrolled thread
| Started by | "Roy J. Tellason, Sr." <roy@rtellason.com> |
|---|---|
| First post | 2024-12-21 18:50 +0100 |
| Last post | 2024-12-22 17:20 +0100 |
| Articles | 12 on this page of 132 — 31 participants |
Back to article view | Back to linux.debian.user
new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-21 18:50 +0100
Re: new computer arriving soon "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-21 20:30 +0100
Re: new computer arriving soon Joe <joe@jretrading.com> - 2024-12-21 21:20 +0100
Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-22 02:20 +0100
Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-22 02:20 +0100
UEFI, Export from Virtualbox [WAS Re: new computer arriving soon] "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-22 09:50 +0100
Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-26 20:40 +0100
Re: new computer arriving soon David Christensen <dpchrist@holgerdanske.com> - 2024-12-26 23:40 +0100
Re: new computer arriving soon David Wright <deblis@lionunicorn.co.uk> - 2024-12-27 17:30 +0100
Re: new computer arriving soon Marc Shapiro <marcnshap@gmail.com> - 2024-12-31 05:10 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2024-12-31 05:40 +0100
Re: new computer arriving soon "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-31 19:00 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2024-12-31 23:00 +0100
Re: new computer arriving soon "Andrew M.A. Cater" <amacater@einval.com> - 2025-01-01 00:00 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-01 01:00 +0100
Re: new computer arriving soon pocket@homemail.com - 2025-01-01 15:00 +0100
Re: new computer arriving soon Frank Guthausen <fg.debian@shimps.de> - 2025-01-01 15:30 +0100
Re: new computer arriving soon pocket@homemail.com - 2025-01-01 15:40 +0100
Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-01 16:40 +0100
Re: new computer arriving soon pocket@homemail.com - 2025-01-01 17:20 +0100
Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-01 18:00 +0100
Re: new computer arriving soon pocket@homemail.com - 2025-01-01 18:00 +0100
Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 03:10 +0100
Re: new computer arriving soon pocket@homemail.com - 2025-01-02 03:40 +0100
Re: new computer arriving soon Charles Curley <charlescurley@charlescurley.com> - 2025-01-01 17:30 +0100
Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-01 18:20 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-01 22:00 +0100
Re: new computer arriving soon Joe <joe@jretrading.com> - 2025-01-01 19:50 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-01 22:50 +0100
Re: new computer arriving soon Andy Smith <andy@strugglers.net> - 2025-01-02 14:50 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-03 04:00 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-03 17:30 +0100
Re: new computer arriving soon Andy Smith <andy@strugglers.net> - 2025-01-03 13:10 +0100
Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 03:30 +0100
Re: new computer arriving soon pocket@homemail.com - 2025-01-02 03:40 +0100
Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 04:30 +0100
Re: new computer arriving soon pocket@homemail.com - 2025-01-02 04:50 +0100
Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 16:40 +0100
Re: new computer arriving soon pocket@homemail.com - 2025-01-02 17:10 +0100
Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-04 05:00 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-04 11:20 +0100
Gene and networkmanager (was: Re: new computer arriving soon) Max Nikulin <manikulin@gmail.com> - 2025-01-05 04:50 +0100
Re: Gene and networkmanager (was: Re: new computer arriving soon) gene heskett <gheskett@shentel.net> - 2025-01-05 17:20 +0100
/dev/serial/by-id (was: Re: new computer arriving soon) Max Nikulin <manikulin@gmail.com> - 2025-01-05 05:00 +0100
Re: /dev/serial/by-id (was: Re: new computer arriving soon) gene heskett <gheskett@shentel.net> - 2025-01-05 17:30 +0100
Re: /dev/serial/by-id Max Nikulin <manikulin@gmail.com> - 2025-01-06 03:30 +0100
Re: /dev/serial/by-id gene heskett <gheskett@shentel.net> - 2025-01-06 08:20 +0100
Re: /dev/serial/by-id Max Nikulin <manikulin@gmail.com> - 2025-01-07 04:20 +0100
Re: /dev/serial/by-id gene heskett <gheskett@shentel.net> - 2025-01-07 10:00 +0100
Re: /dev/serial/by-id gene heskett <gheskett@shentel.net> - 2025-01-07 14:50 +0100
Mass storage sizes (was: /dev/serial/by-id) Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-07 16:10 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Dan Purgert <dan@djph.net> - 2025-01-07 16:50 +0100
Re: Mass storage sizes eben@gmx.us - 2025-01-07 17:10 +0100
Re: Mass storage sizes <tomas@tuxteam.de> - 2025-01-07 17:40 +0100
Re: Mass storage sizes eben@gmx.us - 2025-01-07 18:00 +0100
Re: Mass storage sizes Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-07 20:40 +0100
Re: Mass storage sizes <tomas@tuxteam.de> - 2025-01-08 06:30 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Michael Stone <mstone@debian.org> - 2025-01-07 17:10 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Michael Stone <mstone@debian.org> - 2025-01-07 17:30 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Dan Purgert <dan@djph.net> - 2025-01-07 18:10 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Nicholas Geovanis <nickgeovanis@gmail.com> - 2025-01-09 04:10 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Michael Stone <mstone@debian.org> - 2025-01-09 05:50 +0100
Re: Mass storage sizes Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-09 16:30 +0100
Re: Mass storage sizes Dan Purgert <dan@djph.net> - 2025-01-09 18:10 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Nicolas George <george@nsup.org> - 2025-01-09 21:50 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Michael Stone <mstone@debian.org> - 2025-01-10 00:50 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Jeffrey Walton <noloader@gmail.com> - 2025-01-10 01:10 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2025-01-10 02:10 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Dan Purgert <dan@djph.net> - 2025-01-10 11:00 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) gene heskett <gheskett@shentel.net> - 2025-01-10 15:10 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) <tomas@tuxteam.de> - 2025-01-10 07:30 +0100
Re: Mass storage sizes John Hasler <john@sugarbit.com> - 2025-01-10 15:50 +0100
Re: Mass storage sizes eben@gmx.us - 2025-01-10 21:40 +0100
Re: Mass storage sizes gene heskett <gheskett@shentel.net> - 2025-01-11 01:50 +0100
Re: Mass storage sizes Jeffrey Walton <noloader@gmail.com> - 2025-01-11 01:40 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Heriberto Avelino <heriberto.avelino@gmail.com> - 2025-01-10 01:30 +0100
Re: Mass storage sizes Kushal Kumaran <kushal@locationd.net> - 2025-01-07 20:20 +0100
Re: Mass storage sizes Nicolas George <george@nsup.org> - 2025-01-07 21:10 +0100
Re: Mass storage sizes Michael Stone <mstone@debian.org> - 2025-01-07 23:10 +0100
Re: Mass storage sizes Urs Thuermann <urs@isnogud.escape.de> - 2025-01-10 03:00 +0100
Re: Mass storage sizes Michael Stone <mstone@debian.org> - 2025-01-10 05:30 +0100
Re: Mass storage sizes Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-10 15:40 +0100
Re: Mass storage sizes Charles Curley <charlescurley@charlescurley.com> - 2025-01-07 23:10 +0100
Re: Mass storage sizes gene heskett <gheskett@shentel.net> - 2025-01-08 00:30 +0100
Re: Mass storage sizes "Thomas Schmitt" <scdbackup@gmx.net> - 2025-01-07 17:40 +0100
Re: Mass storage sizes Stefan Monnier <monnier@iro.umontreal.ca> - 2025-01-07 20:30 +0100
Re: Mass storage sizes (was: /dev/serial/by-id) Jeffrey Walton <noloader@gmail.com> - 2025-01-09 08:40 +0100
Re: /dev/serial/by-id Max Nikulin <manikulin@gmail.com> - 2025-01-08 04:00 +0100
Re: /dev/serial/by-id Max Nikulin <manikulin@gmail.com> - 2025-01-08 04:10 +0100
Re: /dev/serial/by-id Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2025-01-07 11:20 +0100
Specific mdadm instructions for Gene [WAS Re: new computer arriving soon] "Andrew M.A. Cater" <amacater@einval.com> - 2025-01-02 17:00 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computer arrivingsoon] gene heskett <gheskett@shentel.net> - 2025-01-02 23:10 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computer arrivingsoon] Andy Smith <andy@strugglers.net> - 2025-01-02 23:20 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computer arrivingsoon] Nicolas George <george@nsup.org> - 2025-01-02 23:30 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computer arrivingsoon] Michael Stone <mstone@debian.org> - 2025-01-03 00:10 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computer arrivingsoon] Jeffrey Walton <noloader@gmail.com> - 2025-01-03 04:00 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computerarrivingsoon] gene heskett <gheskett@shentel.net> - 2025-01-03 05:00 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computerarrivingsoon] Andy Smith <andy@strugglers.net> - 2025-01-03 14:00 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computer arrivingsoon] Max Nikulin <manikulin@gmail.com> - 2025-01-03 03:40 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computerarrivingsoon] gene heskett <gheskett@shentel.net> - 2025-01-03 05:10 +0100
Re: Specific mdadm instructions for Gene [WAS Re: new computerarrivingsoon] Max Nikulin <manikulin@gmail.com> - 2025-01-04 04:30 +0100
Re: Specific mdadm instructions for Gene [WAS Re: newcomputerarrivingsoon] gene heskett <gheskett@shentel.net> - 2025-01-04 04:50 +0100
sgdisk missing under Armbian for Gene [WAS Specific mdadm instructions for Gene] "Andrew M.A. Cater" <amacater@einval.com> - 2025-01-03 12:40 +0100
Re: sgdisk missing under Armbian for Gene [WAS Specific mdadm instructions for Gene] Nicolas George <george@nsup.org> - 2025-01-03 12:50 +0100
Re: sgdisk missing under Armbian for Gene [WAS Specific mdadminstructions for Gene] gene heskett <gheskett@shentel.net> - 2025-01-03 17:40 +0100
Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 04:00 +0100
Re: new computer arriving soon gene heskett <gheskett@shentel.net> - 2025-01-02 05:30 +0100
Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-02 08:30 +0100
Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-02 23:40 +0100
Re: new computer arriving soon fxkl47BF@protonmail.com - 2025-01-02 23:50 +0100
Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-03 00:00 +0100
Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-03 00:20 +0100
Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-03 00:50 +0100
Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2025-01-03 17:00 +0100
Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-03 17:20 +0100
Re: new computer arriving soon David Wright <deblis@lionunicorn.co.uk> - 2025-01-10 05:50 +0100
Re: new computer arriving soon Greg Wooledge <greg@wooledge.org> - 2025-01-03 00:10 +0100
Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-03 00:00 +0100
Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-03 00:00 +0100
Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2025-01-03 00:40 +0100
Re: new computer arriving soon Andy Smith <andy@strugglers.net> - 2025-01-03 00:50 +0100
Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2025-01-03 17:00 +0100
Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 16:30 +0100
Re: new computer arriving soon Frank Guthausen <fg.debian@shimps.de> - 2024-12-31 20:20 +0100
Re: new computer arriving soon Max Nikulin <manikulin@gmail.com> - 2025-01-02 04:10 +0100
Re: new computer arriving soon Michael Stone <mstone@debian.org> - 2025-01-02 23:50 +0100
Re: new computer arriving soon Marc Shapiro <marcnshap@gmail.com> - 2025-01-06 06:10 +0100
Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-27 20:20 +0100
Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2024-12-22 00:40 +0100
Re: new computer arriving soon "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-12-22 02:30 +0100
Re: new computer arriving soon George at Clug <Clug@goproject.info> - 2024-12-22 05:50 +0100
Re: new computer arriving soon songbird <songbird@anthive.com> - 2024-12-22 17:20 +0100
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2025-01-03 00:50 +0100 |
| Message-ID | <K0D6V-56Gx-3@gated-at.bofh.it> |
| In reply to | #276320 |
Hi,
On Fri, Jan 03, 2025 at 10:34:47AM +1100, George at Clug wrote:
> On Friday, 03-01-2025 at 09:57 Michael Stone wrote:
> > Spinning disks are slow; 8 hours for 3TB is about 100MB/s and 8h is
> > about how much time I'd expect it to take to write a commodity disk that
> > size. It becomes really painful on a 24TB drive (8 times as large, 8
> > times as long;
>
> 24TB drive - WOW - just thinking about that hurts.
Even several models of NVMe are available now at ~61TB with ~122TB
coming soon. š
https://www.servethehome.com/the-samsung-bm1743-is-a-61-44tb-today-with-a-122-88tb-drive-possible/
(Just take out a mortgage to buy a pair)
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | "Roy J. Tellason, Sr." <roy@rtellason.com> |
|---|---|
| Date | 2025-01-03 17:00 +0100 |
| Message-ID | <K0SfD-5mIV-1@gated-at.bofh.it> |
| In reply to | #276321 |
On Thursday 02 January 2025 06:48:20 pm Andy Smith wrote: > > Ā 24TB drive - WOW - just thinking about that hurts. > > Even several models of NVMe are available now at ~61TB with ~122TB > coming soon. š > > Ā Ā https://www.servethehome.com/the-samsung-bm1743-is-a-61-44tb-today-with-a-122-88tb-drive-possible/ > > (Just take out a mortgage to buy a pair) > And you'd need a pair, to back the first one up... I'm quite content at this point to be in the process of filling up the 4TB drive that's in my server. :-) -- Member of the toughest, meanest, deadliest, most unrelenting -- and ablest -- form of life in this section of space, Ā a critter that can be killed but can't be tamed. Ā --Robert A. Heinlein, "The Puppet Masters" - Information is more dangerous than cannon to a society ruled by lies. --James M Dakin
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2025-01-02 16:30 +0100 |
| Message-ID | <K0vj3-50SI-5@gated-at.bofh.it> |
| In reply to | #276278 |
On 02/01/2025 11:22, gene heskett wrote: > On 1/1/25 21:57, Max Nikulin wrote: >> The problem is that he can not use some search engine to find guides >> related to LVM. He believes that everything must be documented in man >> pages, but he ignores any tool that may help to find locally installed >> man pages. > Sensible spelling of the utility's that do that would help that search > effort considerably. I note that I've rx'd detailed help assuming I am > using the installer, but no one has offered to teach me exactly what to > type into a bash shell on a system that is booted to a working cli. I > want to make a raid10 of nearly 8T out a 4 of these 4T drives.Ā Do I > even need LVM for a raid10 out of 4, 4T drives?. > > Cheers, Gene Heskett, CET. If you are unsure what you really need then ask Google or some other search engine. For local docs, first of all, use "apt search" with proper keyword to see if you need to install relevant *-doc packages then check /usr/share/doc content for that package names. Project web site and various blogs may be a better source if you need overview. "man" often may offer a reference, not a guide. It is suitable to get details concerning specific command options. Skim through "man man", it describes what search options are available.
[toc] | [prev] | [next] | [standalone]
| From | Frank Guthausen <fg.debian@shimps.de> |
|---|---|
| Date | 2024-12-31 20:20 +0100 |
| Message-ID | <JZPWy-4sDG-9@gated-at.bofh.it> |
| In reply to | #276208 |
[Multipart message ā attachments visible in raw view] — view raw
On Mon, 30 Dec 2024 20:01:41 -0800 Marc Shapiro <marcnshap@gmail.com> wrote: > > What about LVM?Ā Is it usable (or even useful) with UEFI? UEFI has an effect on installing and finding the bootloader. The bootloader will boot the kernel as it does on legacy BIOS systems. Then the kernel is in charge and assembles devices, e.g. partitions, softraid, lvm related stuff and finally it handles filesystems. This is not the job of UEFI. It is possible and in many usecases useful to use LVM on UEFI systems. -- kind regards Frank
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2025-01-02 04:10 +0100 |
| Message-ID | <K0jKV-4Tx7-1@gated-at.bofh.it> |
| In reply to | #276208 |
On 31/12/2024 11:01, Marc Shapiro wrote: > What about LVM?Ā Is it usable (or even useful) with UEFI? Do you expect expect UEFI boot from purely LVM drives? Out of the box EFI system partition (fat) must be outside of LVM volumes. There is a chance that somebody has written a LVM driver for UEFI and your machine allows to install it. I am unsure if grub images signed for Secure Boot include LVM drivers or /boot should be outside of LVM as well. I do not expect real obstacles with LVM with separate ESP and /boot partitions. Perhaps you may avoid even dedicated /boot. Why do you believe that LVM is incompatible with UEFI?
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2025-01-02 23:50 +0100 |
| Message-ID | <K0CaS-564r-9@gated-at.bofh.it> |
| In reply to | #276273 |
On Thu, Jan 02, 2025 at 10:04:51AM +0700, Max Nikulin wrote: >I am unsure if grub images signed for Secure Boot include LVM drivers >or /boot should be outside of LVM as well. grub should work fine these days without /boot being a separate partition, unless you encrypt / (in which case you need the initrd to be on a separate unencrypted partition). Separate /boot is actually one of my pet peeves because it's either stupidly large or it fills up. (And if it's a partition at the start of the disk, resizing it is a PITA.) That's somewhat improved by the current behavior of autoremoving unneeded kernels, but still more trouble than benefit in the common case.
[toc] | [prev] | [next] | [standalone]
| From | Marc Shapiro <marcnshap@gmail.com> |
|---|---|
| Date | 2025-01-06 06:10 +0100 |
| Message-ID | <K1Nxf-66BQ-3@gated-at.bofh.it> |
| In reply to | #276273 |
On 1/1/25 7:04 PM, Max Nikulin wrote: > On 31/12/2024 11:01, Marc Shapiro wrote: >> What about LVM?Ā Is it usable (or even useful) with UEFI? > > Do you expect expect UEFI boot from purely LVM drives? Out of the box > EFI system partition (fat) must be outside of LVM volumes. There is a > chance that somebody has written a LVM driver for UEFI and your > machine allows to install it. > > I am unsure if grub images signed for Secure Boot include LVM drivers > or /boot should be outside of LVM as well. > > I do not expect real obstacles with LVM with separate ESP and /boot > partitions. Perhaps you may avoid even dedicated /boot. Why do you > believe that LVM is incompatible with UEFI? > I didn't mean to imply that LVM was incompatible with UEFI, but I can see, now, why my wording might have left you with that impression. Marc
[toc] | [prev] | [next] | [standalone]
| From | "Roy J. Tellason, Sr." <roy@rtellason.com> |
|---|---|
| Date | 2024-12-27 20:20 +0100 |
| Message-ID | <JYo2l-3gNg-1@gated-at.bofh.it> |
| In reply to | #276032 |
On Thursday 26 December 2024 05:30:38 pm David Christensen wrote: > > It's a real PITA to switch which input this monitor is using, Ā taking many button presses on buttons that I can't even see because they're under the front of the monitor. > > So, you have two computers, two keyboards, and two mice, but one monitor > with the computers connected to different inputs? Ā Have you considered > getting a KVM switch? I believe there are some around here somewhere, but VGA only. This setup is temporary, and once I complete moving stuff over this machine is going to another room and will be put to different uses, so I guess I'll just put up with the inconvenience in the meantime... Dunno why they had to make it that way, instead of having those buttons where I can see them. -- Member of the toughest, meanest, deadliest, most unrelenting -- and ablest -- form of life in this section of space, Ā a critter that can be killed but can't be tamed. Ā --Robert A. Heinlein, "The Puppet Masters" - Information is more dangerous than cannon to a society ruled by lies. --James M Dakin
[toc] | [prev] | [next] | [standalone]
| From | George at Clug <Clug@goproject.info> |
|---|---|
| Date | 2024-12-22 00:40 +0100 |
| Message-ID | <JWheF-1r7F-13@gated-at.bofh.it> |
| In reply to | #275930 |
Roy, If you do not mind me asking, what is the make and model of the Video card (GPU) that will be in the new workstation? Will you be using two GPUs in the computer? I would also be interested in knowing what brand and type of CPU is in the computer. These will affect virtualisation software. Do you know what do you want to achieve with virtualisation software? Do you want to just run CLI interfaces to virtualised servers? Will you want to run Windows or Linux with GUIs like KDE Plasma or Gnome using X11 and/or Wayland? Do you want to watch video from the guests (i.e. virtual machines) ? Will you want to hear sound from the virtual machines ? Do you want to run any 3D programs and/or games running within the virtual machines ? Do you want to be able to do GPU passthrough for any specific virtual machines? Do you want to implement nested virtualisation so you can run virtualised hypervisors? George. On Sunday, 22-12-2024 at 04:44 Roy J. Tellason, Sr. wrote: > So I have a DVD with 12.something on it, not too old. I plan to install that, and then see what's on this workstation that I also might want to install, and then go from there. I'm currently using virtualbox on this machine, but would like to explore some other options for virtualization on the new box. > > Any suggestions as to how I might proceed to making things current and what other software I might want to include are welcomed... > > > -- > Member of the toughest, meanest, deadliest, most unrelenting -- and > ablest -- form of life in this section of space, Ā a critter that can > be killed but can't be tamed. Ā --Robert A. Heinlein, "The Puppet Masters" > - > Information is more dangerous than cannon to a society ruled by lies. --James > M Dakin > >
[toc] | [prev] | [next] | [standalone]
| From | "Roy J. Tellason, Sr." <roy@rtellason.com> |
|---|---|
| Date | 2024-12-22 02:30 +0100 |
| Message-ID | <JWiX7-1seb-1@gated-at.bofh.it> |
| In reply to | #275933 |
On Saturday 21 December 2024 06:29:29 pm George at Clug wrote: > Roy, > > If you do not mind me asking, what is the make and model of the Video card (GPU) that will be in the new workstation? Will you be using two GPUs in the computer? It's whatever is on the MB in the machine. The page where I selected stuff mentions these: Intel® Core⢠i9-14900: UHD Graphics 770 Intel® Core⢠i7-14700: UHD Graphics 770 Intel® Core⢠i9-12900: UHD Graphics 770 Intel® Core⢠i7-12700: UHD Graphics 770 Intel® Core⢠i5-12500: UHD Graphics 770 Intel® Core⢠i3-12100: UHD Graphics 730 Intel® Celeron® G6900: UHD Graphics 710 I'm not sure which one I'm gonna end up with. > I would also be interested in knowing what brand and type of CPU is in the computer. Intel 6-core I5-12500 is what I selected. > These will affect virtualisation software. I'm currently running a rather old version of Slackware in this VM, which is where I do my email. > Do you know what do you want to achieve with virtualisation software? Pretty much the same thing, and maybe trying out some alternatives in other VMs since I'm going to have nontrivially more RAM to work with. > Do you want to just run CLI interfaces to virtualised servers? Nope. > Will you want to run Windows or Linux with GUIs like KDE Plasma or Gnome using X11 and/or Wayland? One of the reasons I'm running what I am here is to use a rather old version of KDE, which doesn't go off in directions I don't care for like the newer stuff does. I'm not completely clear about that whole X11 vs. Wayland stuff, though I've seen both of them mentioned in here. > Do you want to watch video from the guests (i.e. virtual machines) ? I tend to do that in the host OS here. > Will you want to hear sound from the virtual machines ? Maybe. > Do you want to run any 3D programs and/or games running within the virtual machines ? Not likely. > Do you want to be able to do GPU passthrough for any specific virtual machines? I'm not sure where I'd need that. > Do you want to implement nested virtualisation so you can run virtualised hypervisors? Nor that... -- Member of the toughest, meanest, deadliest, most unrelenting -- and ablest -- form of life in this section of space,  a critter that can be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters" - Information is more dangerous than cannon to a society ruled by lies. --James M Dakin
[toc] | [prev] | [next] | [standalone]
| From | George at Clug <Clug@goproject.info> |
|---|---|
| Date | 2024-12-22 05:50 +0100 |
| Message-ID | <JWm4F-1uAl-1@gated-at.bofh.it> |
| In reply to | #275936 |
[Multipart message ā attachments visible in raw view] — view raw
Roy, I don't know what words I should use to say how nice I find your choice. To keep it simple: 'Capable and cost effective'. I usually like the i7 range, but this CPU has everything I look for when choosing a computer to act as a Hypervisor, particularly for my primary PC on which I test a number of Linux distributions, and/or for running Windows in a VM, and a choice that would be cost effective, and not a waste of funds. I expect your new computer will run KVM/QEMU and Virtual Machine Manger very well. As I guess you know, please ensure that "Intel® Virtualization Technology" is enabled in BIOS (preferably before installing Debian 12). https://wiki.debian.org/KVM $ sudo apt install qemu-system libvirt-daemon-system virt-manager If you use virtio drivers for the VM's video, I expect that you will be able to enable OpenGL (Listen type to None) and 3D acceleration, if you wanted to do so. I have only needed to do so to run a VM with Cinnamon without software rendering. https://www.intel.com/content/www/us/en/products/sku/96144/intel-core-i512500-processor-18m-cache-up-to-4-60-ghz/specifications.html Max Memory Size (dependent on memory type): 128 GB Total Cores: 6    # of Performance-cores: 6    # of Efficient-cores: 0 Total Threads: 12 Max Turbo Frequency: 4.60 GHz Performance-core Base Frequency: 3.00 GHz Max Memory Size (dependent on memory type): 128 GB GPU Name: Intel® UHD Graphics 770 DirectX* Support: 12 OpenGL* Support: 4.5 OpenCL* Support: 3.0 Intel® Hyper-Threading Technology: Yes Intel® Virtualization Technology with Redirect Protection (VT-rp): Yes Intel® Virtualization Technology (VT-x): Yes Intel® Virtualization Technology for Directed I/O (VT-d): Yes Intel® VT-x with Extended Page Tables (EPT): Yes On Sunday, 22-12-2024 at 12:28 Roy J. Tellason, Sr. wrote: On Saturday 21 December 2024 06:29:29 pm George at Clug wrote: > Roy, > > If you do not mind me asking, what is the make and model of the Video card (GPU) that will be in the new workstation?  Will you be using two GPUs in the computer? It's whatever is on the MB in the machine.  The page where I selected stuff mentions these: Intel® Core⢠i9-14900: UHD Graphics 770 Intel® Core⢠i7-14700: UHD Graphics 770 Intel® Core⢠i9-12900: UHD Graphics 770 Intel® Core⢠i7-12700: UHD Graphics 770 Intel® Core⢠i5-12500: UHD Graphics 770 Intel® Core⢠i3-12100: UHD Graphics 730 Intel® Celeron® G6900: UHD Graphics 710 I'm not sure which one I'm gonna end up with. > I would also be interested in knowing what brand and type of CPU is in the computer. Intel 6-core I5-12500 is what I selected. > These will affect virtualisation software. I'm currently running a rather old version of Slackware in this VM,  which is where I do my email. > Do you know what do you want to achieve with virtualisation software? Pretty much the same thing,  and maybe trying out some alternatives in other VMs since I'm going to have nontrivially more RAM to work with. > Do you want to just run CLI interfaces to virtualised servers? Nope. > Will you want to run Windows or Linux with GUIs like KDE Plasma or Gnome using X11 and/or Wayland? One of the reasons I'm running what I am here is to use a rather old version of KDE,  which doesn't go off in directions I don't care for like the newer stuff does.  I'm not completely clear about that whole X11 vs. Wayland stuff,  though I've seen both of them mentioned in here. > Do you want to watch video from the guests (i.e. virtual machines) ? I tend to do that in the host OS here. > Will you want to hear sound from the virtual machines ? Maybe. > Do you want to run any 3D programs and/or games running within the virtual machines ? Not likely. > Do you want to be able to do GPU passthrough for any specific virtual machines? I'm not sure where I'd need that. > Do you want to implement nested virtualisation so you can run virtualised hypervisors? Nor that... -- Member of the toughest, meanest, deadliest, most unrelenting -- and ablest -- form of life in this section of space,  a critter that can be killed but can't be tamed.  --Robert A. Heinlein, "The Puppet Masters" - Information is more dangerous than cannon to a society ruled by lies. --James M Dakin
[toc] | [prev] | [next] | [standalone]
| From | songbird <songbird@anthive.com> |
|---|---|
| Date | 2024-12-22 17:20 +0100 |
| Message-ID | <JWwQq-1BBN-17@gated-at.bofh.it> |
| In reply to | #275930 |
Roy J. Tellason, Sr. wrote: > So I have a DVD with 12.something on it, not too old. I plan to install that, and then see what's on this workstation that I also might want to install, and then go from there. I'm currently using virtualbox on this machine, but would like to explore some other options for virtualization on the new box. > > Any suggestions as to how I might proceed to making things current and what other software I might want to include are welcomed... 12.something is stable. yet you say you want current... ? are you fairly confident with your skills that it wouldn't be an issue to try some things? ordering a barebones machine with no OS implies to me that you're likely to be ok with playing around a bit. :) if you have a USB stick available i would suggest just doing the copy of the most recent stable iso version to it and go from there. or even better yet for more current would be a testing iso. between some changes and security updates you can avoid any extra cruft this way. the reason for doing this is that a newer machine may have more recent hardware that might not be recognized by the installer or the older kernels may not have the best drivers. i see you mention running a pretty light desktop management system so that also indicates someone who's more into command line things. songbird
[toc] | [prev] | [standalone]
Page 7 of 7 — ← Prev page 1 2 3 4 5 6 [7]
Back to top | Article view | linux.debian.user
csiph-web