On Saturday, 11 June 2022 14:53:29 EDT David Wright wrote: > On Sat 11 Jun 2022 at 07:31:36 (-0400), gene heskett wrote: > > On Saturday, 11 June 2022 05:39:22 EDT gene heskett wrote: > > > On Saturday, 11 June 2022 00:49:57 EDT David Wright wrote: > > > > On Fri 10 Jun 2022 at 08:44:22 (+0000), Andrew M.A. Cater wrote: > > > > > On Thu, Jun 09, 2022 at 07:53:20PM -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. > > > > > > > > > > Ctrl-alt-F1, F2 I think > > > > > > > > Keystrokes like these are appropriate both for a locally running > > > > graphical installer, and for an installation running X (can't > > > > speak > > > > for Wayland), but not for the combination of a text installer on > > > > a > > > > target machine being controlled from a client running X. You can > > > > run the installer and several shells on the target machine from > > > > the client, without requiring any unusual interactions beyond > > > > what > > > > you normally do when you run X. > > > > > > > > But I can't tell Gene the individual keystrokes and mouse > > > > movements > > > > to > > > > make, as he's using weird things like TDE, konsole, and kmail, > > > > that > > > > I've never seen or used. > > > > > > > > > Part of this at least is why I suggested using text mode > > > > > install > > > > > directly on the machine if you could. > > > > > > > > AFAIK, there's no way of recording the screens if you use text > > > > mode > > > > locally, rather than remotely. Hence the instructions I have been > > > > posting. However, it's difficult to write those instructions for > > > > someone to follow when it appears that they have forgotten how > > > > to cut and paste text from a terminal screen into a file or an > > > > editor's buffer, or think that you can cut and paste from a PNG. > > > > That limit is very easy to see, there is no mouse in those remote > > text > > screens to use to highlight what you might want to paste into nano > > and > > keep. Or is there some other method I've forgotten since I did my > > first install in late '98, on a 400 mhz k6 from the floppies in the > > red hat 5.0 book? A machine I built from parts. So is this one FWIW. > > Presumably you're confusing VC text screens and xterm text > screens. You've been asked to use the latter type of screens > on the remote machine. > > > > > > Graphical expert mode would probably work as well and you could > > > > > save > > > > > the screenshots but I prefer completely text mode to be sure > > > > > not to > > > > > load problematic graphics. > > > > What good are screenshots so big they can't be posted? > > Well, take a look at the PNG you posted at Thu, 09 Jun 2022 15:44:48 > -0400, which is 1366x768 in colour. Now look at the information > contained therein, probably about 500x200. If I were taking a > screenshot, I'd frame the relevant part. > I tried to do that in gimp before I sent it, but all the menu's are changed from what I am used to, I could select and save what I wanted, clear the frame and paste what I'd outlined and saved, but I got the whole thing back when I pasted, several times so I'm going to have to learn gimp all over again.
> But the point is, you don't want to post a screenshot when the > information itself is non-graphical. There are about 500 characters > in that partition listing. > > > > > But using screenshots then opens a debate on where they are > > > > stored, > > > > why they disappear when posted here, how big they are, which > > > > software > > > > to use to reduce their size, how to use pastebins (and whether > > > > people > > > > will bother to look at them when not inline), and how to quote > > > > them. > > > > > > > > As I've been installing Debian in text mode since the days when > > > > the > > > > d-i's part 1 came on five floppies, I've never felt the need. I > > > > just > > > > tried an 11.3 i386 netinst USB stick on an old Acer laptop, > > > > selected > > > > graphical expert mode, and got a text screen. Memory limitation > > > > (512MB) I suppose, or it doesn't like the graphics card (Radeon). > > > > > > That didn't boot, but reverted to the old problematic boot, twice. > > > Then I recalled once before that since I'd done it to one big, > > > full drive, and grub is the ast thing installed, its probably too > > > far into the drive and grub can't find its boot files. > > > > > > So I'm about to repartition the drive for a 12 or 13G /boot as a > > > seperate partition and make a 27th attempt. > > > Something like this from fdisk /dev/sdd, then p > > > Command (m for help): p > > > Disk /dev/sdd: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors > > > Disk model: Samsung SSD 870 > > > Units: sectors of 1 * 512 = 512 bytes > > > Sector size (logical/physical): 512 bytes / 512 bytes > > > I/O size (minimum/optimal): 512 bytes / 512 bytes > > > Disklabel type: gpt > > > Disk identifier: 9CEFADE5-AA85-4242-8630-5CA906D8DDB3 > > > > > > Device Start End Sectors Size Type > > > /dev/sdd1 2048 27351039 27348992 13G Linux filesystem > > > /dev/sdd2 27351040 154478591 127127552 60.6G Linux swap > > > /dev/sdd3 154478592 1953523711 1799045120 857.9G Linux filesystem > > > > > > Which ought to keep grub's stuff within reach. And it should stop > > > it > > > from using a slower swap file too, not that this current setup with > > > 32G of dram uses much swap unless I screw up with OpenSCAD. > > > > > > And I'd better get to it, I'm running out of uptime since nut > > > doesn't > > > like no permissions to access /dev/ttyUSB1, and heyu doesn't like > > > being locked out of /dev/ttyUSB0 for the same rediculous reason. > > > Right now their cables are unplugged to prevent the automatic > > > braile install w/o asking. > > > > > > And nobody can tell me, and grep can't find it, what udev rule sets > > > the permissions on ttyUSB serial ports. Making heyu and nut > > > members of group root SHOULD NOT BE REQUIRED. Nor should a root > > > session be required to reset the perms on those 2 devices as part > > > of a reboot setup, it takes me 20+ minutes even with scripts > > > driving my network setup everytime I reboot. I'm short one machine > > > that didn't survive a power glitch yesterday morning in this df > > > report: > > > Filesystem 1K-blocks Used Available Use% Mounted on > > > udev 16360160 0 16360160 0% /dev > > > tmpfs 3274336 1592 3272744 1% /run > > > /dev/sda5 286294368 12318980 259359428 5% / > > > tmpfs 16371672 17328 16354344 1% /dev/shm > > > tmpfs 5120 4 5116 1% /run/lock > > > /dev/sda1 1020896 61224 889632 7% /boot > > > /dev/sda6 95534500 2280532 88354848 3% /var > > > /dev/sda7 95541668 108 90642080 1% /tmp > > > /dev/md0p1 1796382580 220867652 1484189952 13% /home > > > tmpfs 3274332 3952 3270380 1% /run/user/1000 > > > gene@GO704:/ 28704676 11867328 15356184 44% /sshnet/GO704 > > > pi@rpi4:/ 61064956 21624400 36877792 37% /sshnet/rpi4 > > > gene@dddprint:/ 99795040 5095124 89584372 6% > > > /sshnet/dddprint > > > gene@sixty40:/ 235203512 15272432 207913672 7% > > > /sshnet/sixty40 > > > But I'd better get to it. And find out if it will reboot to the new > > > drive when I'm finished. > > > > Which, see my previous post, failed, it won't set the bootable flag. > > Does anyone know why? > > Your reaction to a post like this would be "Is it beer-thirty yet?" Well, I tore the box down and re-arranged drives, removing 3 that weren't in use including the last seagate that died in the night back in october. So now, with 2 drives on the mobo sockets, and 4 more on the 2nd controller for the raid10, it FIMALLY see's both drives. I've edited new blkid's where needed in /etc/fstab so all that is working. So my question tonight is: are these blkid's stable enough that I can copy this fstab over the one in the new install and expect it to work when I boot to the bigger drive & install I just did? The one I'm booted to is a 500G Samsung 860 EVO, the new drive is also a Samsung 1Tb, 870 QVC. Everything else non-optical is gone. Thanks 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
