Re: trying to install bullseye for about 25th time.
On Friday, 10 June 2022 00:22:53 EDT David Wright wrote: > On Thu 09 Jun 2022 at 15:44:48 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 11:04:15 EDT David Wright wrote: > > > On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote: > > > > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > > > > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > > > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > > > I always install my systems in this manner from my normal > > > > > workstation. > > > > > > > > This IS my normal workstation. But I imagine that I could reverse > > > > the > > > > path from one of my Dells dedicated to a task. Only one has a > > > > comfy > > > > chair though, the one normally running my biggest milling > > > > machine, > > > > out in the garage. I'll take my coffee cup out and try this from > > > > there. > > > > > > Unsurprisingly, I use the second most convenient machine to install > > > onto that one. In addition, I lose the benefit of apt-cacher-ng for > > > that particular installation process. If I'm installing a new > > > release, > > > then I save the normal cache's contents, and later import all its > > > .deb > > > files into apt-cacher-ng on my workstation's new installation. > > > > > > One more convenience of installing like this is that you can have > > > the > > > release notes, your own aide-memoires, and other reference > > > documents, > > > open on the same machine while you're running the installer. > > > > Here is that partitioner menu snapshot, obtained by a network ssh > > login, smunched to 81kb base-64'd. Showing that d-i did not even > > recognize the disk I want to use for this new install. > > > > So how & what do I do to this virgin disk to make the d-i recognize > > it so I can install to it? > > Well, you already know what I would do as it's been posted on this > list before: partition it with my personal favourite, gdisk. > > But before I started, I would list /dev/disk/ to checkout all the > installed disks, and their correspondence with the /dev/sd* or > /dev/nvme0n* names. This avoid's mick's problem. > > I'd then write a GPT-style partition table, and the partitions > I wanted, create the EFI partition, and change the names of > the other partitions to my requirements. (All my disks are named, > and the partition LABELs and PARTLABELs are based on that name.) > > But I haven't used LVMs, and their users might have a different > strategy. > I had some nightmares with LVM back in its younger days, and have shied away from it since. But I'd assume its more stable now than it was in ext3 days long ago. > Cheers, > David. > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: 26th pass at installing 11-3, fails
On Friday, 10 June 2022 00:45:19 EDT David Wright wrote: > On Thu 09 Jun 2022 at 23:59:06 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 21:13:53 EDT mick crane wrote: > > > On 2022-06-09 22:15, gene heskett wrote: > > > > Posted once as the original .png of 81k, that didn't get thru the > > > > server, > > > > then I loaed it up in gimp and smunched it down to about 51k, > > > > ugly > > > > but > > > > still readable, and thats not made it thru the server either. > > > > > > Screenshot_1.jpg(~61 KB) was attached to your previous mail. > > > Noticed as you say that 3 disks were scsi7. > > > > That screenshot never came back to here. > > Is that perhaps because you sent it? (One of the big complaints about > some MUAs and some email providers.) > The second one did come back so I assume it was seen but kmails ability to find your own echo's in a mailing list folder are definitly not its strong point. The scroll scrolls too far per click, going right on by your posts echos. Pretty high torr rating for that suckage. ;o(> > > In the meantime, I have > > partitioned and formatted that new drive as ext4, gpt partition with > > gparted, the whole drive, then printed the info for it from fdisk, > > which give the UUID's, 2 different ones, so which should I see in > > the d-i partitioner, the type-UUID or just the UUID, they are > > different numbers, fdisk's info also shows the label as Name: > > slash26, and its is currently /dev/sdd1, but who knows what it might > > be to the installer? I'll plug in the drive with the d-i in it, and > > retry right now. > > I don't recall seeing UUIDs in the d-i, perhaps because they're so > long. I usually see the entries from /dev/disk/by-id/, or part thereof. There weren't any, but dmesg from another shell allowed me to ID the proper drive. So it now has a 1 partition install on it that won't boot. boot flag is set. And me is puzzled. boot files too far into the drive maybe? Thanks David. > But bear in mind that /dev/disk/ can be fully listed by the d-i from > the very start, by switching to a shell on Alt-F2/3. > > Cheers, > David. > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: 26th pass at installing 11-3, fails
On Friday, 10 June 2022 00:45:19 EDT David Wright wrote: > On Thu 09 Jun 2022 at 23:59:06 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 21:13:53 EDT mick crane wrote: > > > On 2022-06-09 22:15, gene heskett wrote: > > > > Posted once as the original .png of 81k, that didn't get thru the > > > > server, > > > > then I loaed it up in gimp and smunched it down to about 51k, > > > > ugly > > > > but > > > > still readable, and thats not made it thru the server either. > > > > > > Screenshot_1.jpg(~61 KB) was attached to your previous mail. > > > Noticed as you say that 3 disks were scsi7. > > > > That screenshot never came back to here. > > Is that perhaps because you sent it? (One of the big complaints about > some MUAs and some email providers.) > > > In the meantime, I have > > partitioned and formatted that new drive as ext4, gpt partition with > > gparted, the whole drive, then printed the info for it from fdisk, > > which give the UUID's, 2 different ones, so which should I see in > > the d-i partitioner, the type-UUID or just the UUID, they are > > different numbers, fdisk's info also shows the label as Name: > > slash26, and its is currently /dev/sdd1, but who knows what it might > > be to the installer? I'll plug in the drive with the d-i in it, and > > retry right now. > > I don't recall seeing UUIDs in the d-i, perhaps because they're so > long. I usually see the entries from /dev/disk/by-id/, or part thereof. > > But bear in mind that /dev/disk/ can be fully listed by the d-i from > the very start, by switching to a shell on Alt-F2/3. > > Cheers, > David. I made the install using your instructs. Used 3 of the tty's on another machine to get away from X, and did not install a desktop as I have a badly named trinity 14 file in my sources-list.d. But at reboot, its rebooted to the old install after spending an additional 30 seconds contemplating its sins, twice. No reports I can find. I have mounted it to /mnt/slash26 and it looks normal at first glance. I have grub installed on /dev/sda and on /dev/sdd, so it seems like I should be able to choose between them from the bios boot menu. Ideas? Thanks David. > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: 26th pass at installing 11-3, fails
On Thu 09 Jun 2022 at 23:59:06 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 21:13:53 EDT mick crane wrote: > > On 2022-06-09 22:15, gene heskett wrote: > > > Posted once as the original .png of 81k, that didn't get thru the > > > server, > > > then I loaed it up in gimp and smunched it down to about 51k, ugly > > > but > > > still readable, and thats not made it thru the server either. > > > > Screenshot_1.jpg(~61 KB) was attached to your previous mail. > > Noticed as you say that 3 disks were scsi7. > > That screenshot never came back to here. Is that perhaps because you sent it? (One of the big complaints about some MUAs and some email providers.) > In the meantime, I have > partitioned and formatted that new drive as ext4, gpt partition with > gparted, the whole drive, then printed the info for it from fdisk, which > give the UUID's, 2 different ones, so which should I see in the d-i > partitioner, the type-UUID or just the UUID, they are different numbers, > fdisk's info also shows the label as Name: slash26, and its is currently > /dev/sdd1, but who knows what it might be to the installer? I'll plug in > the drive with the d-i in it, and retry right now. I don't recall seeing UUIDs in the d-i, perhaps because they're so long. I usually see the entries from /dev/disk/by-id/, or part thereof. But bear in mind that /dev/disk/ can be fully listed by the d-i from the very start, by switching to a shell on Alt-F2/3. Cheers, David.
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 03:22:56 (-0400), Felix Miata wrote: > gene heskett composed on 2022-06-09 02:59 (UTC-0400): > > > Are you saying that I can partition this new drive with gparted and make > > the d-i use that? That would be the holy grail if so. > > This possibility became reality in antiquity. I never would have completed my > first Debian installation attempt if this were not the case. I can't remember > the > last Gnu/Linux installer I ran across that didn't have this capability. Unlike > David, who /usually/ partitions prior to starting up the Debian installer, I > *always* do. Only one partitioner is ever used on any of my partitionable > media. I > usually format first too, including any swap partition. Actually, I haven't partitioned in the installer since the mid-1990s, and back then, I would have written the first partition with DOS6.22, so that it could set a disk geometry satisfactory to itself. These were dual-boot machines, sort of, in that they booted linux from DOS's config.sys using loadlin IIRC. "I always prefer to …" means that I do something as a considered choice, a preference, rather than habit, instruction, or whatever. Others might advise some other course (eg Andrew, with LVM). Perhaps it's rather British. Cheers, David.
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 15:44:48 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 11:04:15 EDT David Wright wrote: > > On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote: > > > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > > > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > > I always install my systems in this manner from my normal > > > > workstation. > > > > > > This IS my normal workstation. But I imagine that I could reverse the > > > path from one of my Dells dedicated to a task. Only one has a comfy > > > chair though, the one normally running my biggest milling machine, > > > out in the garage. I'll take my coffee cup out and try this from > > > there. > > > > Unsurprisingly, I use the second most convenient machine to install > > onto that one. In addition, I lose the benefit of apt-cacher-ng for > > that particular installation process. If I'm installing a new release, > > then I save the normal cache's contents, and later import all its .deb > > files into apt-cacher-ng on my workstation's new installation. > > > > One more convenience of installing like this is that you can have the > > release notes, your own aide-memoires, and other reference documents, > > open on the same machine while you're running the installer. > > > Here is that partitioner menu snapshot, obtained by a network ssh login, > smunched to 81kb base-64'd. Showing that d-i did not even recognize the > disk I want to use for this new install. > > So how & what do I do to this virgin disk to make the d-i recognize it so > I can install to it? Well, you already know what I would do as it's been posted on this list before: partition it with my personal favourite, gdisk. But before I started, I would list /dev/disk/ to checkout all the installed disks, and their correspondence with the /dev/sd* or /dev/nvme0n* names. This avoid's mick's problem. I'd then write a GPT-style partition table, and the partitions I wanted, create the EFI partition, and change the names of the other partitions to my requirements. (All my disks are named, and the partition LABELs and PARTLABELs are based on that name.) But I haven't used LVMs, and their users might have a different strategy. Cheers, David.
Re: 26th pass at installing 11-3, fails
On Thursday, 9 June 2022 21:13:53 EDT mick crane wrote: > On 2022-06-09 22:15, gene heskett wrote: > > Posted once as the original .png of 81k, that didn't get thru the > > server, > > then I loaed it up in gimp and smunched it down to about 51k, ugly > > but > > still readable, and thats not made it thru the server either. > > Screenshot_1.jpg(~61 KB) was attached to your previous mail. > Noticed as you say that 3 disks were scsi7. That screenshot never came back to here. In the meantime, I have partitioned and formatted that new drive as ext4, gpt partition with gparted, the whole drive, then printed the info for it from fdisk, which give the UUID's, 2 different ones, so which should I see in the d-i partitioner, the type-UUID or just the UUID, they are different numbers, fdisk's info also shows the label as Name: slash26, and its is currently /dev/sdd1, but who knows what it might be to the installer? I'll plug in the drive with the d-i in it, and retry right now. > I have installed Debian to the wrong disk one time because of user > error. > The last time I think I physically disconnected other disks for > installation. > and added/identified others later by dmesg reported manufacturer and > size. > > good luck > mick > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: 26th pass at installing 11-3, fails
On Thu 09 Jun 2022 at 19:53:20 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 18:49:40 EDT Andy Smith wrote: > > On Thu, Jun 09, 2022 at 05:15:28PM -0400, gene heskett wrote: > > > So 26th reinstall attempt, following David's instructs to do an ssh > > > from another machine to install > > > > So can we see the copy and paste of this first screen that you have > > a problem with? > yes, the list server for debian-user see's the attachment and apparently > sends the whole msg to /dev/null. Neither msg has come back in aound 6 > hours. > > > > > So, how to I do a text copy/paste from that .png so I can insert the > > > cogent parts of the text in an email msg? > > > > I recommend not doing that at all and going with the text mode over > > SSH, because you are never going to be able to get non-text > > attachments to this list and it just seems harder in general. > > > Thats what I thought I was doing, by opening a konsole on the client > machine, but when I saved the screenshot, it was a png. x was running on > the client machine, so there needs to be a method to make it text also. > The installer was started in expert text mode, but ssh apparently > overrides that somehow when it finds x running on the client. Should I > have been running the client w/o x or wayland? I am not even sure how to > switch vt's away from x to whatever #2 or #3 is called. I don't understand what you're writing here. The screenshot shows that you were looking at a screenful of *text*, with some File/Edit/View/… menu items at the top that look graphical. You can see that the listing is text, because the "button" has these "< >" angle brackets. If it was a real GUI, you'd see a button with some sort of relief, colour or shading to distinguish it from the background. My instructions were "From your xterm, you can cut and paste text in the usual manner", and there's a world of difference between that and taking a screenshot. If you cut and paste, you can place the text in a post here, and we can quote it, copy it ourselves, and so on. You cut and paste by dragging the mouse over the text, and then clicking a different mouse button to paste it into a file that you can archive as part of your installation log. I keep a log for each of my disks, with partition listings from fdisk, gdisk and parted (they yield a variety of formats). Cheers, David.
Re: which X11 app can show wifi info
On Fri 10 Jun 2022 at 08:05:12 (+0800), lou wrote: > i want a small app that show wifi info, including connected network > name (wpa-ssid) > > hopefully it doesn't depend on qt as i don't use kde ( i use twm for buster) I would have thought that the program by which you connect would be able to show you all the information it, by definition, knows about the connection that it set up. For example, with iwd: $ systemctl status iwd.service ● iwd.service - Wireless service Loaded: loaded (/etc/systemd/system/iwd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2022-06-09 18:17:35 CDT; 3h 11min ago Main PID: 520 (iwd) Tasks: 1 (limit: 19018) Memory: 1.9M CPU: 742ms CGroup: /system.slice/iwd.service └─520 /usr/libexec/iwd -d Jun 09 21:28:18 ahost iwd[520]: src/scan.c:scan_notify() Scan notification New Scan Results(34) Jun 09 21:28:18 ahost iwd[520]: src/netdev.c:netdev_link_notify() event 16 on ifindex 3 Jun 09 21:28:18 ahost iwd[520]: src/scan.c:get_scan_callback() get_scan_callback Jun 09 21:28:18 ahost iwd[520]: src/scan.c:get_scan_callback() get_scan_callback Jun 09 21:28:18 ahost iwd[520]: src/scan.c:get_scan_callback() get_scan_callback Jun 09 21:28:18 ahost iwd[520]: src/scan.c:get_scan_callback() get_scan_callback Jun 09 21:28:18 ahost iwd[520]: src/scan.c:get_scan_callback() get_scan_callback Jun 09 21:28:18 ahost iwd[520]: src/scan.c:get_scan_done() get_scan_done Jun 09 21:28:18 ahost iwd[520]: src/station.c:station_roam_failed() 3 Jun 09 21:28:18 ahost iwd[520]: src/wiphy.c:wiphy_radio_work_done() Work item 224 done $ $ iwctl station wlan0 show Station: wlan0 Settable PropertyValue Scanningno State connected Connected network Cascade5G ConnectedBss33:55:77:99:bb:dd Frequency 5765 SecurityWPA2-Personal RSSI-70 dBm AverageRSSI -70 dBm RxMode 802.11n RxMCS 11 TxMode 802.11n TxMCS 12 TxBitrate 18 Kbit/s RxBitrate 108000 Kbit/s $ Is that the sort of information you want? Cheers, David.
Re: 26th pass at installing 11-3, fails
On 2022-06-09 22:15, gene heskett wrote: Posted once as the original .png of 81k, that didn't get thru the server, then I loaed it up in gimp and smunched it down to about 51k, ugly but still readable, and thats not made it thru the server either. Screenshot_1.jpg(~61 KB) was attached to your previous mail. Noticed as you say that 3 disks were scsi7. I have installed Debian to the wrong disk one time because of user error. The last time I think I physically disconnected other disks for installation. and added/identified others later by dmesg reported manufacturer and size. good luck mick
Re: disk mount problem
On Fri, 10 Jun 2022 at 05:09, ghe2001 wrote: > There are failures when I try to mount a disk. Fstab: > > # > > # / was on /dev/md0p1 (sda1 & sdc1) during installation > UUID=d1749d90-0fce-44a6-93db-5fbadc32911c / ext4 > errors=remount-ro 0 1 > # swap was on /dev/md0p5 during installation > UUID=4469f9d3-fbf6-463c-b286-69d3174b7360 noneswapsw > 0 0 > # > # the Western Digital 12T disk (/dev/sdb1) > ### UUID=21dcbfda-3884-404f-855f-693d1efa2f06 /blackHole ext4 > default 0 0 > # > # the Seagate 12T disk (/dev/sdd1) > ### UUID=2e7a5901-597e-4ea2-92fb-614d07280b20 /mnt1 ext4 > default 0 0 > I've never seen the first one fail, I've never tried the second, the third > and fifth work as expected, and the forth fails. (On boot, the /blackHole > line is commented out.) > > Any thoughts? Have I missed something? Check your own message from a month ago: https://lists.debian.org/debian-user/2022/05/msg00242.html
which X11 app can show wifi info
i want a small app that show wifi info, including connected network name (wpa-ssid) hopefully it doesn't depend on qt as i don't use kde ( i use twm for buster) Thanks!
Re: 26th pass at installing 11-3, fails
On Thursday, 9 June 2022 18:49:40 EDT Andy Smith wrote: > Hello, > > On Thu, Jun 09, 2022 at 05:15:28PM -0400, gene heskett wrote: > > So 26th reinstall attempt, following David's instructs to do an ssh > > from another machine to install > > So can we see the copy and paste of this first screen that you have > a problem with? yes, the list server for debian-user see's the attachment and apparently sends the whole msg to /dev/null. Neither msg has come back in aound 6 hours. > > > So, how to I do a text copy/paste from that .png so I can insert the > > cogent parts of the text in an email msg? > > I recommend not doing that at all and going with the text mode over > SSH, because you are never going to be able to get non-text > attachments to this list and it just seems harder in general. > > Cheers, > Andy Thats what I thought I was doing, by opening a konsole on the client machine, but when I saved the screenshot, it was a png. x was running on the client machine, so there needs to be a method to make it text also. The installer was started in expert text mode, but ssh apparently overrides that somehow when it finds x running on the client. Should I have been running the client w/o x or wayland? I am not even sure how to switch vt's away from x to whatever #2 or #3 is called. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: 26th pass at installing 11-3, fails
Hello, On Thu, Jun 09, 2022 at 05:15:28PM -0400, gene heskett wrote: > So 26th reinstall attempt, following David's instructs to do an ssh from > another machine to install So can we see the copy and paste of this first screen that you have a problem with? > So, how to I do a text copy/paste from thart .png so I can insert the > cogent parts of the text in an email msg? I recommend not doing that at all and going with the text mode over SSH, because you are never going to be able to get non-text attachments to this list and it just seems harder in general. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
26th pass at installing 11-3, fails
Hello all; I have now made two passes at posting a screenshot of the partitioner menu screen, showing that it does not even see the drive I want to use. It also shows 3 copies that make no sense as they are all called by the same name as SCSI7. they might be the raid, but that is 4 drives, not 3. Posted once as the original .png of 81k, that didn't get thru the server, then I loaed it up in gimp and smunched it down to about 51k, ugly but still readable, and thats not made it thru the server either. So 26th reinstall attempt, following David's instructs to do an ssh from another machine to install, after it froze up with under 2 days uptime. I've also found that its /dev/sdd for this bootup with 90% of the usb stuff unplugged. This reinstall driven by an x crash, the mouse and gkrellm were still alive, the mouse pointer moved but no button clicks worked. A logout worked, but logging back in, it was still frozen up. So I rebooted to the d-i and following David W. instructs, got to the partitioners menu & discovered it not one had sdb from a different drive now, but the drive I want to use is completely missing from the choices listed. Hence the wish to post the snapshot since I'm catching it from everybody by not showing it. So, how to I do a text copy/paste from thart .png so I can insert the cogent parts of the text in an email msg? Thanks all. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: disk mount problem [solved]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 --- Original Message --- On Thursday, June 9th, 2022 at 1:38 PM, Alexander V. Makartsev wrote: > > You have a typo in options. Should be: > > UUID=21dcbfda-3884-404f-855f-693d1efa2f06 /blackHole ext4 > defaults 0 0 Alexander is right; works now -- Thanks, and sorry to rattle your cage... -- Glenn English ⠀ -BEGIN PGP SIGNATURE- Version: ProtonMail wsBzBAEBCAAGBQJiolOJACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG MYKsjDKs/gf9E3cm9eJZtSHuk1VFvexORWCo/TmgrlTNQhCEGMpsYrGjdSFJ VU3y+pPvcWs3hujNsX40zoYrHbOG8keWbLOqYjE8ruZM3zDNjc77xctUImPY xcOVGg7eFYDrBOmyybSoK4TxOGEZFQPQj0Fd0wN5OqsO12PjSgv/0BE2OFPD WJHHC4FknWr9o9ptRtxdsyLzp7nbvRLwUmn2yTM9epwvVZRgzQ8Rpyqm7cfE mCLdZ4msSawO8Ap3vVy+fLLME/dhaQD/84nDyPdxdxd9AtI5gDdq1dzCUMhN NTCcy3hmrWLxcBf3mjOjvYQLivnu/wwauI60Iijw3V0kUgoFMK15eg== =wwGD -END PGP SIGNATURE-
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 11:04:15 EDT David Wright wrote: > On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > I always install my systems in this manner from my normal > > > workstation. > > > > This IS my normal workstation. But I imagine that I could reverse the > > path from one of my Dells dedicated to a task. Only one has a comfy > > chair though, the one normally running my biggest milling machine, > > out in the garage. I'll take my coffee cup out and try this from > > there. > > Unsurprisingly, I use the second most convenient machine to install > onto that one. In addition, I lose the benefit of apt-cacher-ng for > that particular installation process. If I'm installing a new release, > then I save the normal cache's contents, and later import all its .deb > files into apt-cacher-ng on my workstation's new installation. > > One more convenience of installing like this is that you can have the > release notes, your own aide-memoires, and other reference documents, > open on the same machine while you're running the installer. > > Cheers, > David. > > . Here is that partitioner menu snapshot, obtained by a network ssh login, smunched to 81kb base-64'd. Showing that d-i did not even recognize the disk I want to use for this new install. So how & what do I do to this virgin disk to make the d-i recognize it so I can install to it? Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: disk mount problem
ghe2001 wrote: > -BEGIN PGP SIGNED MESSAGE- > # > > # / was on /dev/md0p1 (sda1 & sdc1) during installation > UUID=d1749d90-0fce-44a6-93db-5fbadc32911c / ext4 > errors=remount-ro 0 1 > # swap was on /dev/md0p5 during installation > UUID=4469f9d3-fbf6-463c-b286-69d3174b7360 noneswapsw > 0 0 > # > # the Western Digital 12T disk (/dev/sdb1) > ### UUID=21dcbfda-3884-404f-855f-693d1efa2f06 /blackHole ext4default > 0 0 > # > # the Seagate 12T disk (/dev/sdd1) > ### UUID=2e7a5901-597e-4ea2-92fb-614d07280b20 /mnt1 ext4default > 0 0 > # > # the cdrom drive > /dev/sr0 > > The disk is a single partition 12TB WD (sdb1, aka > 21dcbfda-3884-404f-855f-693d1efa2f06). > > Command(s): > > mount /blackHole/ > mount: /blackHole: wrong fs type, bad option, bad superblock on /dev/sdb1, > missing codepage or helper program, or other error. > > mount UUID=21dcbfda-3884-404f-855f-693d1efa2f06 > mount: /blackHole: wrong fs type, bad option, bad superblock on /dev/sdb1, > missing codepage or helper program, or other error. > > mount UUID=21dcbfda-3884-404f-855f-693d1efa2f06 /blackHole/ > > mount /dev/sdb1 > mount: /blackHole: wrong fs type, bad option, bad superblock on /dev/sdb1, > missing codepage or helper program, or other error. > > mount /dev/sdb1 /blackHole/ > > I've never seen the first one fail, I've never tried the second, the third > and fifth work as expected, and the forth fails. (On boot, the /blackHole > line is commented out.) I'm going to guess that /dev/sdb1 is not, in fact, ext4, but is a filesystem that your kernel can mount. -dsr-
Re: disk mount problem
On 09.06.2022 23:52, ghe2001 wrote: Supermicro desktop, Debian bullseye There are failures when I try to mount a disk. Fstab: ... I've never seen the first one fail, I've never tried the second, the third and fifth work as expected, and the forth fails. (On boot, the /blackHole line is commented out.) Any thoughts? Have I missed something? You have a typo in options. Should be: UUID=21dcbfda-3884-404f-855f-693d1efa2f06 /blackHole ext4 defaults 0 0 -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 11:03:52 EDT David Wright wrote: > On Thu 09 Jun 2022 at 03:31:30 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 00:34:28 EDT David Wright wrote: > > > On Wed 08 Jun 2022 at 14:04:44 (-0400), gene heskett wrote: > > > > On Wednesday, 8 June 2022 08:33:56 EDT rhkra...@gmail.com wrote: > > > > > Or exchange the memory card (if you have an appropriate card > > > > > reader > > > > > for (one of) your computer(s))? > > > > > > > > I do. but dragging the card out of the camera's, all of them, is > > > > betting Murphy is on vacation, the power surges seem to like to > > > > trash the cards. > > > > > > Turn the camera off first? > > > > I don't think thats enough, Cannon, Nikon and Olympus (I have one of > > each) seem to power the card even when the mechanicals are turned > > off, so removing the battery first might be safe. All 3 have to be > > turned on before digikam can access them, but the card contacts are > > so buried I can't verify socket power. The Cannon is the only one > > that hasn't destroyed its original card and its usb socket is both > > fast and dependable, the usb socket is worn out on the other two. > > Its also the only one with a removable to recharge lithium battery. > > The other 2 have a quad of AA's in them. That remove to recharge is > > a pita, as the recharge takes 8 hours. And no one stocks that > > battery so you can have a ready spare. The cannon takes the best > > pix, but that rules it out for use by a wedding photog unless he's > > carrying a second, fully charged backup. Thats all immaterial to > > this though. > > That's remarkable. Do the cameras have real on/off switches, or are > they just soft? That said, my mobiles have never given me problems > with removing their cards, even though their on/off switches are soft. > IDK for sure, David, I'm going by the clue which is that I can remove the card, import to digikam from a reader, put the card back in the camera, turn the camera back on and the camera will not recognize it again, but I can put tha card back in the reader, and its all there, back in the camera, its not recognized again. In 2 earlier cameras, a new card it had no problems recognizing. Thats my clue. The cannons usb port is still functioning so the card has only been out of it once, before digikam grew a cannon driver with the buster release. How I interpret that clue is driven by my electronics troubleshooting history which starts in about 1950 when I quit school and went to work as a tech. That fed me well for the next 52 years, and still does. Thank you David. > Cheers, > David. > > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
disk mount problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Supermicro desktop, Debian bullseye There are failures when I try to mount a disk. Fstab: # # / was on /dev/md0p1 (sda1 & sdc1) during installation UUID=d1749d90-0fce-44a6-93db-5fbadc32911c / ext4 errors=remount-ro 0 1 # swap was on /dev/md0p5 during installation UUID=4469f9d3-fbf6-463c-b286-69d3174b7360 noneswapsw 0 0 # # the Western Digital 12T disk (/dev/sdb1) ### UUID=21dcbfda-3884-404f-855f-693d1efa2f06 /blackHole ext4default 0 0 # # the Seagate 12T disk (/dev/sdd1) ### UUID=2e7a5901-597e-4ea2-92fb-614d07280b20 /mnt1 ext4default 0 0 # # the cdrom drive /dev/sr0 The disk is a single partition 12TB WD (sdb1, aka 21dcbfda-3884-404f-855f-693d1efa2f06). Command(s): mount /blackHole/ mount: /blackHole: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. mount UUID=21dcbfda-3884-404f-855f-693d1efa2f06 mount: /blackHole: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. mount UUID=21dcbfda-3884-404f-855f-693d1efa2f06 /blackHole/ mount /dev/sdb1 mount: /blackHole: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. mount /dev/sdb1 /blackHole/ I've never seen the first one fail, I've never tried the second, the third and fifth work as expected, and the forth fails. (On boot, the /blackHole line is commented out.) Any thoughts? Have I missed something? -- Glenn English -BEGIN PGP SIGNATURE- Version: ProtonMail wsBzBAEBCAAGBQJiokFKACEJEObKK1bRaqt3FiEExEbtoeXBeE9fruv35sor VtFqq3frmggA1Y4A15rfo4nsmz8BbIaIz2jSMeCWIIGXUHVokM3SazuTtAdn D2lKrJtPgvBlKobu6luh4nq7NaHPAWo/77iV6C5ggiUfzofvHuxKNnSg1y56 6X78EyhZhRoFosSwdY9B24ZcyYjjsl6xC4+I92E1dzF4p0Sph5qw8GMYUCgM 7d6pXBb80TwZ5169DZtr/DlkC5wG7ZdWInbckDWifZohWv9v8TXjgz8m+/N/ 0vbaDdLYbf2vgw3SJ18WyBzfYlmozEnMX+G+FhhjwSUZoaQiXIbWCZZZ6bX+ rcAQSofUu9pLxqGNCqkiBe4B+8WeC2XsDGUH7ic8CraILCxumHiXkA== =Eh1q -END PGP SIGNATURE-
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 11:05:27 EDT David Wright wrote: > On Thu 09 Jun 2022 at 06:04:08 (-0400), gene heskett wrote: > > On Thursday, 9 June 2022 04:18:04 EDT Andrew M.A. Cater wrote: > > > On Thu, Jun 09, 2022 at 02:59:43AM -0400, gene heskett wrote: > > > > On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > > > > > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > > > > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > > > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > > The only way I know how to do that is take a screen shot with > > > > > > my > > > > > > camera. But thats not possible when running the D-I cuz w/o > > > > > > gimp, > > > > > > its at least 5 megs bigger than the server will accept. BTDT. > > > > > > > > > > I don't see why you need a screenshot to post the name(s) of > > > > > the > > > > > > > > > > disk(s) in the partitioner menu. It's just one line per disk, like: > > > > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > > > > > > > > > taken from the listing posted in: > > > > > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > > > > > > > > > I could label it, but the partitioner doesn't do > > > > > > > > > labels. > > > > > > > > > This drive is new, and has not anything written to it. > > > > > > > > > > > > > > > > Really? Which partitioner is that? > > > > > > > > > > > > The one in the D-I. > > > > > > > > > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > > > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home > > > > Andy, What good is a "partlabel" when it does not tell me which drive > > by the drives own readily found name as displayed by dmesg after a > > normal boot? With this drive showing up as ata-5 in dmesg, but > > somehow udev calls it /dev/sdb is confusing as can be. How the h--- > > does a drive plugged into ata-5 on the mobo, get to be named sdb > > when there are 8 other drives in front of it, 4 of them on a > > different controller in the discovery process? > > Come on, we've known for years that the /dev/sdX names for disks are > as good as random. On some machines, you can change the lettering of > their internal drives just by inserting USB sticks at boot. > > > I've zero guarantees that the d-i boot will detect THIS drive I want > > to use, the same as it did for an 11-1 install which generates the > > dmesg I am reading. The d-i shoots itself in the foot with excellent > > aim in this regard. > > For some reason, you won't show what the d-i partitioner /does/ call > it (assuming you're going to partition it with that, which I wouldn't). > > And the d-i will wind up doing a format on the raid10, destroying 6 > > month work, I'll have to reinvent. It did it unfailingly for many > > previous installs, because if I removed brltty, it would not boot > > past not find it in the reboot, which meant the only way I could > > reboot was to re-install yet again. > > I've already posted how to ensure that can't happen, by telling the > d-i not to use the raid10 stuff when installing Debian, and setting up > your real /home later. > > > To the d-i, my history is of no concern, do NOT forget that I've > > already done 25 damned installs trying to save my work. > > Could we! > > > I finally did figure out > > how to silence orca, without destroying the ability to reboot, but > > the > > uptime is 5 to 7 days. All because of seagates f-ing experiment with > > helium filled shingled drives which failed well within a year because > > they thought they could seal them well enough to keep the helium in > > them. > > > > If in 1960, a bank of monel metal bottles with 2" thick walls, went > > from 7200 psi to 4800 psi because it leaks thru 2" of monel from > > midnight to 7:30 when the day shift clocked in. That leakage cost > > the laboratory I was working for around $10,000 a day, we were > > validating the ullage tank presuure regulators for the Atlas missles > > that probably gave John Glen his first ride. > > > > Now seagate thinks they can keep it in a teeny hard drive so they can > > lower the flying height of the heads? The insanity in Oklahoma City > > knows no bounds. And I am out of the spinning rust camp forever, > > SSD's are faster AND far more dependable. > > > > I now have around 6 months work stored on that all SSD raid, and I'll > > be damned if I'll take a chance of losing it. But I'm convinced that > > I have to do one more install, clean of brltty and orca, to get > > uptimes past 8 days. I have repeatedly asked how to get rid of it > > totally, several times on this list and have yet to be advised of a > > way to remove it that doesn't destroy the system, the dependency's > > removed cascade all the way back to libc6. Tying a specialty > > function that deep into the OS that it cannot be removed, only > > half-a--ed disabled and kil
Re: debian app on UserLAnd: upgrading to bullseye
On 09.06.2022 19:41, agyaana...@yahoo.com wrote: i have installed debian (buster) on userland app (UserLAnd is an open-source app which allows you to run several Linux distributions like Ubuntu, Debian, and Kali.) i am keen to upgrade to bullseye. my action: * sudo apt-get update && apt-get full-upgrade * sudo nano /etc/apt/sources.list: replace buster with bullseye * sudo apt-get update && apt-get upgrade && apt-get dist-upgrade am i missing on something. i have limited data plan. hence, requesting opinion or suggestions here. In addition to suggestion from Andrew you should skim through Bullseye's release notes¹. [1] https://www.debian.org/releases/stable/amd64/release-notes/ -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: trying to install bullseye for about 25th time.
Hello, On Thu, Jun 09, 2022 at 11:30:26AM -0400, rhkra...@gmail.com wrote: > For Gene, he could conceivably just rename the RAID setup that he has mounted > under /home to some new top level mountpoint. (Although he probably has some > scripts or similar stuff that looks for stuff in /home/ that would > need to be modifed. For anyone with a number of machines, like Gene, there is a lot to be said for having one be in the role of file server. - One place to have a ton of storage, which isn't a usual role for a simple desktop daily driver machine. - One place to back up. - Access from anywhere you want. - Easier to keep your other machines up to date without worrying about all the precious data on your fileserver. Blow them away completely if you like. Be more free to experiment. It's a way of working that's served me well for about 25 years. It's hard to imagine going back to having data spread all over the place. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: debian app on UserLAnd: upgrading to bullseye
On Thu, Jun 09, 2022 at 02:41:40PM +, agyaana...@yahoo.com wrote: > i have installed debian (buster) on userland app (UserLAnd is an open-source > app which allows you to run several Linux distributions like Ubuntu, > Debian, and Kali.) > > i am keen to upgrade to bullseye. > my action: > * sudo apt-get update && apt-get full-upgrade > * sudo nano /etc/apt/sources.list: replace buster with bullseye > * sudo apt-get update && apt-get upgrade && apt-get dist-upgrade > > am i missing on something. i have limited data plan. hence, requesting > opinion or suggestions here. > > regards, > agyaan > Hi Agyaan One thing you _have_ to do is check your /etc/apt/sources.list as this changed slightly between buster and bullseye - https://wiki.debian.org/SourcesList refers to the changes. With every good wish, as ever, Andy Cater
Re: trying to install bullseye for about 25th time.
I want to make a comment on this thread that is at least a little bit (maybe a lot) off point, it is more a suggestion on what might be a better way next time (although it could be done this time with a little work, I believe). Because I don't see a good place to put this comment in context, I'm deleting almost all of the quoted material and then top posting. I avoid /home as much as I possibly (or at least reasonably) can. I did it for different reasons than the reason I'm going to suggest it now, so I won't go into those, at least for now (well, ok, basically, I got frustrated once when I did something that I thought was innocent and wiped out all my "real user data" (that is things like my documents, code, photos, etc.) when I did something dumb and wiped out home. I would suggest moving (or renaming) all of your "real user data" (for Gene that would presumably include CNC instructions for various things he makes on his machinery) -- put all of that in a new top level directory (mine, on different computers are variations of /nn). Let the system use /home/ for whatever it wants, and don't worry about it if it gets lost. Doing what I describe might require some gymnastics with respect to keeping things like mail out of /home, but I did that. And various databases and backups seem to get created in /home/, but it seems to be stuff that can be recreated and maybe is recreated automatically under some circumstances if it disappears. For Gene, he could conceivably just rename the RAID setup that he has mounted under /home to some new top level mountpoint. (Although he probably has some scripts or similar stuff that looks for stuff in /home/ that would need to be modifed. FWIW On Thursday, June 09, 2022 06:04:08 AM gene heskett wrote: ---< deleted >---
Re: google account say it will no longer deliver email
On Thursday, June 09, 2022 02:13:31 AM mick crane wrote: > I finally had to set up an app password for mail to work. > During the process of discovering what to click on there was the > statement. > "Google will never use the content of your emails in order to select > what ads you are shown." > or words to that effect. Ahh, good, I have a bridge to sell
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 06:04:08 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 04:18:04 EDT Andrew M.A. Cater wrote: > > On Thu, Jun 09, 2022 at 02:59:43AM -0400, gene heskett wrote: > > > On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > > > > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > > > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > The only way I know how to do that is take a screen shot with my > > > > > camera. But thats not possible when running the D-I cuz w/o gimp, > > > > > its at least 5 megs bigger than the server will accept. BTDT. > > > > > > > > I don't see why you need a screenshot to post the name(s) of the > > > > > > > > disk(s) in the partitioner menu. It's just one line per disk, like: > > > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > > > > > > > taken from the listing posted in: > > > > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > > > > > > > I could label it, but the partitioner doesn't do labels. > > > > > > > > This drive is new, and has not anything written to it. > > > > > > > > > > > > > > Really? Which partitioner is that? > > > > > > > > > > The one in the D-I. > > > > > > > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home > > Andy, What good is a "partlabel" when it does not tell me which drive by > the drives own readily found name as displayed by dmesg after a normal > boot? With this drive showing up as ata-5 in dmesg, but somehow udev > calls it /dev/sdb is confusing as can be. How the h--- does a drive > plugged into ata-5 on the mobo, get to be named sdb when there are 8 > other drives in front of it, 4 of them on a different controller in the > discovery process? Come on, we've known for years that the /dev/sdX names for disks are as good as random. On some machines, you can change the lettering of their internal drives just by inserting USB sticks at boot. > I've zero guarantees that the d-i boot will detect THIS drive I want to > use, the same as it did for an 11-1 install which generates the dmesg I > am reading. The d-i shoots itself in the foot with excellent aim in this > regard. For some reason, you won't show what the d-i partitioner /does/ call it (assuming you're going to partition it with that, which I wouldn't). > And the d-i will wind up doing a format on the raid10, destroying 6 month > work, I'll have to reinvent. It did it unfailingly for many previous > installs, because if I removed brltty, it would not boot past not find it > in the reboot, which meant the only way I could reboot was to re-install > yet again. I've already posted how to ensure that can't happen, by telling the d-i not to use the raid10 stuff when installing Debian, and setting up your real /home later. > To the d-i, my history is of no concern, do NOT forget that I've already > done 25 damned installs trying to save my work. Could we! > I finally did figure out > how to silence orca, without destroying the ability to reboot, but the > uptime is 5 to 7 days. All because of seagates f-ing experiment with > helium filled shingled drives which failed well within a year because > they thought they could seal them well enough to keep the helium in them. > > If in 1960, a bank of monel metal bottles with 2" thick walls, went from > 7200 psi to 4800 psi because it leaks thru 2" of monel from midnight to > 7:30 when the day shift clocked in. That leakage cost the laboratory I > was working for around $10,000 a day, we were validating the ullage tank > presuure regulators for the Atlas missles that probably gave John Glen > his first ride. > > Now seagate thinks they can keep it in a teeny hard drive so they can > lower the flying height of the heads? The insanity in Oklahoma City knows > no bounds. And I am out of the spinning rust camp forever, SSD's are > faster AND far more dependable. > > I now have around 6 months work stored on that all SSD raid, and I'll be > damned if I'll take a chance of losing it. But I'm convinced that I have > to do one more install, clean of brltty and orca, to get uptimes past 8 > days. I have repeatedly asked how to get rid of it totally, several times > on this list and have yet to be advised of a way to remove it that > doesn't destroy the system, the dependency's removed cascade all the way > back to libc6. Tying a specialty function that deep into the OS that it > cannot be removed, only half-a--ed disabled and killing the uptime > because it leaves a wild write someplace slowly destroying the system is > inexcusable. > > Thats bs, and I'm fresh out of patience. > > There should be a procedure to fix this, but the procedure so far is to > ignore my requests for help in this
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 03:46:12 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > I always install my systems in this manner from my normal workstation. > > This IS my normal workstation. But I imagine that I could reverse the > path from one of my Dells dedicated to a task. Only one has a comfy chair > though, the one normally running my biggest milling machine, out in the > garage. I'll take my coffee cup out and try this from there. Unsurprisingly, I use the second most convenient machine to install onto that one. In addition, I lose the benefit of apt-cacher-ng for that particular installation process. If I'm installing a new release, then I save the normal cache's contents, and later import all its .deb files into apt-cacher-ng on my workstation's new installation. One more convenience of installing like this is that you can have the release notes, your own aide-memoires, and other reference documents, open on the same machine while you're running the installer. Cheers, David.
Re: trying to install bullseye for about 25th time.
On Thu 09 Jun 2022 at 03:31:30 (-0400), gene heskett wrote: > On Thursday, 9 June 2022 00:34:28 EDT David Wright wrote: > > On Wed 08 Jun 2022 at 14:04:44 (-0400), gene heskett wrote: > > > On Wednesday, 8 June 2022 08:33:56 EDT rhkra...@gmail.com wrote: > > > > Or exchange the memory card (if you have an appropriate card reader > > > > for (one of) your computer(s))? > > > > > > I do. but dragging the card out of the camera's, all of them, is > > > betting Murphy is on vacation, the power surges seem to like to > > > trash the cards. > > Turn the camera off first? > > > I don't think thats enough, Cannon, Nikon and Olympus (I have one of > each) seem to power the card even when the mechanicals are turned off, so > removing the battery first might be safe. All 3 have to be turned on > before digikam can access them, but the card contacts are so buried I > can't verify socket power. The Cannon is the only one that hasn't > destroyed its original card and its usb socket is both fast and > dependable, the usb socket is worn out on the other two. Its also the > only one with a removable to recharge lithium battery. The other 2 have > a quad of AA's in them. That remove to recharge is a pita, as the > recharge takes 8 hours. And no one stocks that battery so you can have a > ready spare. The cannon takes the best pix, but that rules it out for use > by a wedding photog unless he's carrying a second, fully charged backup. > Thats all immaterial to this though. That's remarkable. Do the cameras have real on/off switches, or are they just soft? That said, my mobiles have never given me problems with removing their cards, even though their on/off switches are soft. Cheers, David.
Re: debian app on UserLAnd: upgrading to bullseye
On Thu, Jun 09, 2022 at 02:41:40PM +, agyaana...@yahoo.com wrote: > i have installed debian (buster) on userland app (UserLAnd is an open-source > app which allows you to run several Linux distributions like Ubuntu, > Debian, and Kali.) > > i am keen to upgrade to bullseye. > my action: > * sudo apt-get update && apt-get full-upgrade > * sudo nano /etc/apt/sources.list: replace buster with bullseye > * sudo apt-get update && apt-get upgrade && apt-get dist-upgrade > > am i missing on something. i have limited data plan. hence, requesting > opinion or suggestions here. > Have you read the release notes? That should be considered an obligatory step. Regards, -Roberto -- Roberto C. Sánchez
debian app on UserLAnd: upgrading to bullseye
i have installed debian (buster) on userland app (UserLAnd is an open-source app which allows you to run several Linux distributions like Ubuntu, Debian, and Kali.) i am keen to upgrade to bullseye. my action: * sudo apt-get update && apt-get full-upgrade * sudo nano /etc/apt/sources.list: replace buster with bullseye * sudo apt-get update && apt-get upgrade && apt-get dist-upgrade am i missing on something. i have limited data plan. hence, requesting opinion or suggestions here. regards, agyaan
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
On Thu, Jun 09, 2022 at 10:42:07AM +0200, Harald Dunkel wrote: > > If I have to hardwire the interface names to their Mac address as you > suggested, then I don't see a significant difference to the old-style > /etc/udev/rules.d/70-persistent-net.rules we had till Debian 10, except > that the former was auto-generated and easier to modify. Yes, that's correct. It's conceptually the same exact thing we used to do with udev. Only now it has to be done with systemd instead. Because someone decided to change it.
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 04:18:04 EDT Andrew M.A. Cater wrote: > On Thu, Jun 09, 2022 at 02:59:43AM -0400, gene heskett wrote: > > On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > > > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > > > But I've put another drive in, that I want to install a non > > > > > > > efi > > > > > > > system on too. > > > > > > > > > > > > > > The installer does not identify it by the same names, so > > > > > > > how do > > > > > > > I > > > > > > > install to this drive w/o touching any of the other 6 > > > > > > > samsung > > > > > > > EVO > > > > > > > series drives. > > > > > > > > > > > > > > I've never learn to love gnome, and the kde5 you offer is > > > > > > > buggier > > > > > > > than a 10 day old road kill in August, so this time is a > > > > > > > text > > > > > > > install to see if I can put TDE in for a desktop. > > > > > > > > > > > > > > How do I proceed? The partitioner does not identify the > > > > > > > drives > > > > > > > found > > > > > > > adequatly. The drive is plugged into the mainboard > > > > > > > controller, > > > > > > > I > > > > > > > think to port 5 of 6. > > > > > > > > > > > > Well, you post what it /does/ display. Then the experts here > > > > > > can > > > > > > make > > > > > > educated guesses, rather than just guessing. > > > > > > > > The only way I know how to do that is take a screen shot with my > > > > camera. But thats not possible when running the D-I cuz w/o gimp, > > > > its at least 5 megs bigger than the server will accept. BTDT. > > > > > > I don't see why you need a screenshot to post the name(s) of the > > > > > > disk(s) in the partitioner menu. It's just one line per disk, like: > > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > > > > > taken from the listing posted in: > > > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > > > > > I could label it, but the partitioner doesn't do labels. > > > > > > > This drive is new, and has not anything written to it. > > > > > > > > > > > > Really? Which partitioner is that? > > > > > > > > The one in the D-I. > > > > > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home Andy, What good is a "partlabel" when it does not tell me which drive by the drives own readily found name as displayed by dmesg after a normal boot? With this drive showing up as ata-5 in dmesg, but somehow udev calls it /dev/sdb is confusing as can be. How the h--- does a drive plugged into ata-5 on the mobo, get to be named sdb when there are 8 other drives in front of it, 4 of them on a different controller in the discovery process? I've zero guarantees that the d-i boot will detect THIS drive I want to use, the same as it did for an 11-1 install which generates the dmesg I am reading. The d-i shoots itself in the foot with excellent aim in this regard. > > > > > > But as your disk is new, I don't know what those PARTLABELs would > > > be > > > set to. If you booted a bullseye installation to capture the dmesg > > > you quoted, then it might be simplest to partition the new disk at > > > that time. You get the most flexibility that way. (I always prefer > > > to partition my disks before I let the d-i loose on them.) > > > > > > > > > I was rereading Andrew's reply in the other thread, and his > > > > > > appeal > > > > > > "The more you can tell us what _EXACTLY_ you are doing, what > > > > > > you > > > > > > see, > > > > > > what errors come up and what you have done to try and fix > > > > > > them, > > > > > > the > > > > > > easier we'll all find it to come up with suggestions or > > > > > > actual > > > > > > answers > > > > > > for you." > > > > > > > > > > > > And I was thinking, that's not enough. We only hear a summary > > > > > > of > > > > > > what > > > > > > you think you're doing. I had a hypothesis for why you > > > > > > couldn't > > > > > > avoid > > > > > > the speech synthesiser, but it would require knowing every > > > > > > keystroke > > > > > > you use from powering on the machine. No chance of that. > > > > > > > > Not to mention it would be TL,DR to most. > > > > > > It can hardly be /too/ long, as you claim that the speech > > > synthesiser > > > starts yakking almost straightaway. > > > > That, with only the keyboard and mouse plus a small b/w laser printer > > plugged in, did not occur this time giving me hope it won't install > > that crap. There is now, perhaps driven by my troubles, a manu > > selection for that I purposely have not gone near. > > > > Are you saying that I can partition this new drive with gparted and > > make the d-i use that? That would be the holy grail if so. Question > > then: Since /home w
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
If I have to hardwire the interface names to their Mac address as you suggested, then I don't see a significant difference to the old-style /etc/udev/rules.d/70-persistent-net.rules we had till Debian 10, except that the former was auto-generated and easier to modify. Regards Harri
Re: trying to install bullseye for about 25th time.
On Thu, Jun 09, 2022 at 02:59:43AM -0400, gene heskett wrote: > On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > > But I've put another drive in, that I want to install a non efi > > > > > > system on too. > > > > > > > > > > > > The installer does not identify it by the same names, so how do > > > > > > I > > > > > > install to this drive w/o touching any of the other 6 samsung > > > > > > EVO > > > > > > series drives. > > > > > > > > > > > > I've never learn to love gnome, and the kde5 you offer is > > > > > > buggier > > > > > > than a 10 day old road kill in August, so this time is a text > > > > > > install to see if I can put TDE in for a desktop. > > > > > > > > > > > > How do I proceed? The partitioner does not identify the drives > > > > > > found > > > > > > adequatly. The drive is plugged into the mainboard controller, > > > > > > I > > > > > > think to port 5 of 6. > > > > > > > > > > Well, you post what it /does/ display. Then the experts here can > > > > > make > > > > > educated guesses, rather than just guessing. > > > > > > The only way I know how to do that is take a screen shot with my > > > camera. But thats not possible when running the D-I cuz w/o gimp, > > > its at least 5 megs bigger than the server will accept. BTDT. > > > > I don't see why you need a screenshot to post the name(s) of the > > disk(s) in the partitioner menu. It's just one line per disk, like: > > > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > > > taken from the listing posted in: > > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > > > I could label it, but the partitioner doesn't do labels. > > > > > > This drive is new, and has not anything written to it. > > > > > > > > > > Really? Which partitioner is that? > > > > > > The one in the D-I. > > > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home > > > > But as your disk is new, I don't know what those PARTLABELs would be > > set to. If you booted a bullseye installation to capture the dmesg > > you quoted, then it might be simplest to partition the new disk at > > that time. You get the most flexibility that way. (I always prefer > > to partition my disks before I let the d-i loose on them.) > > > > > > > I was rereading Andrew's reply in the other thread, and his > > > > > appeal > > > > > "The more you can tell us what _EXACTLY_ you are doing, what you > > > > > see, > > > > > what errors come up and what you have done to try and fix them, > > > > > the > > > > > easier we'll all find it to come up with suggestions or actual > > > > > answers > > > > > for you." > > > > > > > > > > And I was thinking, that's not enough. We only hear a summary of > > > > > what > > > > > you think you're doing. I had a hypothesis for why you couldn't > > > > > avoid > > > > > the speech synthesiser, but it would require knowing every > > > > > keystroke > > > > > you use from powering on the machine. No chance of that. > > > > > > Not to mention it would be TL,DR to most. > > > > It can hardly be /too/ long, as you claim that the speech synthesiser > > starts yakking almost straightaway. > > That, with only the keyboard and mouse plus a small b/w laser printer > plugged in, did not occur this time giving me hope it won't install that > crap. There is now, perhaps driven by my troubles, a manu selection for > that I purposely have not gone near. > > Are you saying that I can partition this new drive with gparted and make > the d-i use that? That would be the holy grail if so. Question then: > Since /home would be just a mount point for the raid10, how big does that > partition actually have to be? Is a single 4096k inode big enough? I > assume it will have to be big enough for it to contain /etc/skel. > > > Cheers, > > David. > > Thanks David. > > . > Partition the disk as all in one: that will set up points on LVM for all directories. Separately, tag the RAID as mounting at /home - job done. There won't _be_ anything in /home until a user is set up and you've already told it to use a preexisting /home. Partitioning it with gparted will complicate matters: UEFI will set up the ESP partition for itself anyway. Andy Cater > > Cheers, Gene Heskett. > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author, 1940) > If we desire respect for the law, we must first make the law respectable. > - Louis D. Brandeis > > >
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 03:22:56 EDT Felix Miata wrote: > gene heskett composed on 2022-06-09 02:59 (UTC-0400): > > Are you saying that I can partition this new drive with gparted and > > make the d-i use that? That would be the holy grail if so. > > This possibility became reality in antiquity. I never would have > completed my first Debian installation attempt if this were not the > case. I can't remember the last Gnu/Linux installer I ran across that > didn't have this capability. Unlike David, who /usually/ partitions > prior to starting up the Debian installer, I *always* do. Only one > partitioner is ever used on any of my partitionable media. I usually > format first too, including any swap partition. > > > Question then: > > Since /home would be just a mount point for the raid10, how big does > > that partition actually have to be? Is a single 4096k inode big > > enough? > A mount point isn't a partition. It's a directory purposed for mounting > a separate filesystem. The directory, and its inode consumption, goes > on the root filesystem. Thanks Felix. That clarifies it. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 00:33:33 EDT David Wright wrote: > On Tue 07 Jun 2022 at 16:24:02 (-0400), gene heskett wrote: > > On Tuesday, 7 June 2022 15:16:16 EDT Andrew M.A. Cater wrote: > > > On Tue, Jun 07, 2022 at 02:17:08PM -0400, gene heskett wrote: > > > > > > Fourth: Use the text mode expert install. > > > > I have so far, but powered off to bail out when I couldn't figure out > > what to do next. Before it wrote anything. > > > > > Document this step by step: write yourself a tasklist and tick off > > > each small step as it completes. > > > > > > As someone who has done, conservatively, 500 installs - many with > > > the > > > text mode installer - it is not as hard as you seem to make it > > > every > > > single time. But, without knowing at what step you fail and > > > precisely > > > what you see when you do fail - what error messages, what it's > > > telling > > > you and what steps you are thinking of taking BEFORE you take them, > > > I'm at a loss to know. > > > > The D-I needs to grow the capability to mount an otherwise unused > > drive, and store as png's, snapshots of the screen. That way no one > > can accuse me of copy/paste fibbing. I can also take screen shots > > but the list server, even if I could figure out how to get it out of > > the camera and submit them, would justifiably balk at the 5+ megs a > > pix that would be. > As you're using the advanced text d-i, it's very simple to take > screenshots that you can include in your posts. They will look very > much like the ones I post, because this is how I generate them. > > When you get to this screen: > > ┌┤ [?] Load installer components from CD > ├┐ │ > │ │ All components of the installer > needed to complete the install will be loaded │ │ automatically and > are not listed here. Some other (optional) installer │ │ > components are shown below. They are probably not necessary, but may > be │ │ interesting to some users. > │ │ > │ │ Note that if you select a > component that requires others, those components │ │ will also be > loaded.│ │ > > │ │ Installer components to load: > │ │ >│ … … …… … …… … …… … … > … … …… … …… … …… … …… … … │[ ] > nbd-modules-4.9.0-7-686-di: Network Block Device modules > ▒ │ │[*] network-console: Continue installation remotely using > SSH ▒ │ │[ ] ntfs-modules-4.9.0-7-686-di: NTFS > filesystem support ▒ │ … … …… … …… … …… > … …… … …… … …… … …… … …… … … > > │ > │ │ >│ │ > │ > └─ > ┘ > > select "network-console" as shown above. > > When the network has been configured, select this option from > the main menu: > > Continue installation remotely using SSH > > It will ask you to type (twice) a password, and then tell you how to > connect to the d-i from another machine: > > ┌┤ [!!] Continue installation remotely using SSH > ├┐ │ > │ │ > Start SSH│ │ To continue the > installation, please use an SSH client to connect to the IP │ │ > address 192.168.1.xxx fe80::xxx::: and log in as the > "installer"│ │ user. For example: > │ │ > │ │ssh > instal...@192.168.1.xxx > │ │ >│ │ The fingerprint of this SSH server's host key is: > │ │ > │ │ > SHA256:xxx > │ │ > │ │ Please check this carefully against the > fingerprint reported by your SSH client.│ │ >
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 00:34:28 EDT David Wright wrote: > On Wed 08 Jun 2022 at 14:04:44 (-0400), gene heskett wrote: > > On Wednesday, 8 June 2022 08:33:56 EDT rhkra...@gmail.com wrote: > > > Or exchange the memory card (if you have an appropriate card reader > > > for (one of) your computer(s))? > > > > I do. but dragging the card out of the camera's, all of them, is > > betting Murphy is on vacation, the power surges seem to like to > > trash the cards. > Turn the camera off first? > I don't think thats enough, Cannon, Nikon and Olympus (I have one of each) seem to power the card even when the mechanicals are turned off, so removing the battery first might be safe. All 3 have to be turned on before digikam can access them, but the card contacts are so buried I can't verify socket power. The Cannon is the only one that hasn't destroyed its original card and its usb socket is both fast and dependable, the usb socket is worn out on the other two. Its also the only one with a removable to recharge lithium battery. The other 2 have a quad of AA's in them. That remove to recharge is a pita, as the recharge takes 8 hours. And no one stocks that battery so you can have a ready spare. The cannon takes the best pix, but that rules it out for use by a wedding photog unless he's carrying a second, fully charged backup. Thats all immaterial to this though. > Cheers, > David. Thanks David. Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
Re: trying to install bullseye for about 25th time.
gene heskett composed on 2022-06-09 02:59 (UTC-0400): > Are you saying that I can partition this new drive with gparted and make > the d-i use that? That would be the holy grail if so. This possibility became reality in antiquity. I never would have completed my first Debian installation attempt if this were not the case. I can't remember the last Gnu/Linux installer I ran across that didn't have this capability. Unlike David, who /usually/ partitions prior to starting up the Debian installer, I *always* do. Only one partitioner is ever used on any of my partitionable media. I usually format first too, including any swap partition. > Question then: > Since /home would be just a mount point for the raid10, how big does that > partition actually have to be? Is a single 4096k inode big enough? A mount point isn't a partition. It's a directory purposed for mounting a separate filesystem. The directory, and its inode consumption, goes on the root filesystem. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: trying to install bullseye for about 25th time.
On Thursday, 9 June 2022 00:31:55 EDT David Wright wrote: > On Tue 07 Jun 2022 at 16:07:13 (-0400), gene heskett wrote: > > On Tuesday, 7 June 2022 15:03:41 EDT gene heskett wrote: > > > On Tuesday, 7 June 2022 14:35:50 EDT David Wright wrote: > > > > On Tue 07 Jun 2022 at 14:17:08 (-0400), gene heskett wrote: > > > > > But I've put another drive in, that I want to install a non efi > > > > > system on too. > > > > > > > > > > The installer does not identify it by the same names, so how do > > > > > I > > > > > install to this drive w/o touching any of the other 6 samsung > > > > > EVO > > > > > series drives. > > > > > > > > > > I've never learn to love gnome, and the kde5 you offer is > > > > > buggier > > > > > than a 10 day old road kill in August, so this time is a text > > > > > install to see if I can put TDE in for a desktop. > > > > > > > > > > How do I proceed? The partitioner does not identify the drives > > > > > found > > > > > adequatly. The drive is plugged into the mainboard controller, > > > > > I > > > > > think to port 5 of 6. > > > > > > > > Well, you post what it /does/ display. Then the experts here can > > > > make > > > > educated guesses, rather than just guessing. > > > > The only way I know how to do that is take a screen shot with my > > camera. But thats not possible when running the D-I cuz w/o gimp, > > its at least 5 megs bigger than the server will accept. BTDT. > > I don't see why you need a screenshot to post the name(s) of the > disk(s) in the partitioner menu. It's just one line per disk, like: > >SCSI1 (0,0,0) (sda) - 500.1 GB ATA ST350AA > > taken from the listing posted in: > https://lists.debian.org/debian-user/2022/06/msg00055.html > > > > > > I could label it, but the partitioner doesn't do labels. > > > > > This drive is new, and has not anything written to it. > > > > > > > > Really? Which partitioner is that? > > > > The one in the D-I. > > The d-i partitioner lists PARTLABELs, as the cited listing showed: > > BIOS boot pa/BullBoot/Linux swap/Viva-A/Viva-B/Viva-Home > > But as your disk is new, I don't know what those PARTLABELs would be > set to. If you booted a bullseye installation to capture the dmesg > you quoted, then it might be simplest to partition the new disk at > that time. You get the most flexibility that way. (I always prefer > to partition my disks before I let the d-i loose on them.) > > > > > I was rereading Andrew's reply in the other thread, and his > > > > appeal > > > > "The more you can tell us what _EXACTLY_ you are doing, what you > > > > see, > > > > what errors come up and what you have done to try and fix them, > > > > the > > > > easier we'll all find it to come up with suggestions or actual > > > > answers > > > > for you." > > > > > > > > And I was thinking, that's not enough. We only hear a summary of > > > > what > > > > you think you're doing. I had a hypothesis for why you couldn't > > > > avoid > > > > the speech synthesiser, but it would require knowing every > > > > keystroke > > > > you use from powering on the machine. No chance of that. > > > > Not to mention it would be TL,DR to most. > > It can hardly be /too/ long, as you claim that the speech synthesiser > starts yakking almost straightaway. That, with only the keyboard and mouse plus a small b/w laser printer plugged in, did not occur this time giving me hope it won't install that crap. There is now, perhaps driven by my troubles, a manu selection for that I purposely have not gone near. Are you saying that I can partition this new drive with gparted and make the d-i use that? That would be the holy grail if so. Question then: Since /home would be just a mount point for the raid10, how big does that partition actually have to be? Is a single 4096k inode big enough? I assume it will have to be big enough for it to contain /etc/skel. > Cheers, > David. Thanks David. > . Cheers, Gene Heskett. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis
