Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #265863 > unrolled thread
| Started by | gene heskett <gheskett@shentel.net> |
|---|---|
| First post | 2024-01-13 03:50 +0100 |
| Last post | 2024-01-19 21:10 +0100 |
| Articles | 20 on this page of 167 — 25 participants |
Back to article view | Back to linux.debian.user
smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-13 03:50 +0100
Re: smartctl cannot access my storage, need syntax help "Gareth Evans" <donotspam@fastmail.fm> - 2024-01-13 04:00 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-13 04:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-13 06:00 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-13 16:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-13 18:10 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-13 18:30 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-13 19:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-14 00:30 +0100
Re: smartctl cannot access my storage, need syntax help Steve McIntyre <steve@einval.com> - 2024-01-14 14:40 +0100
Re: smartctl cannot access my storage, need syntax help Nicolas George <george@nsup.org> - 2024-01-14 11:40 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-14 17:30 +0100
Re: smartctl cannot access my storage, need syntax help Charles Curley <charlescurley@charlescurley.com> - 2024-01-13 06:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-14 13:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-14 20:50 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-15 01:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 02:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 14:50 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-15 19:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 23:00 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-15 21:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 00:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 01:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 01:10 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 00:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 01:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 01:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 02:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 03:20 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-16 04:00 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 07:00 +0100
Re: smartctl cannot access my storage, need syntax help Tom Furie <tom@furie.org.uk> - 2024-01-16 09:20 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 12:10 +0100
Re: smartctl cannot access my storage, need syntax help Valerio Vanni <valerio.vanni@inwind.it> - 2024-01-16 13:40 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-17 01:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 03:00 +0100
Re: smartctl cannot access my storage, need syntax help Max Nikulin <manikulin@gmail.com> - 2024-01-16 16:00 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-16 15:10 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 15:40 +0100
Re: smartctl cannot access my storage, need syntax help Greg Wooledge <greg@wooledge.org> - 2024-01-16 15:50 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-17 01:20 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-16 17:10 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 03:20 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 07:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 15:30 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 18:10 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 18:30 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 20:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 21:40 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 22:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 22:40 +0100
normally start new xterms [was: Re: smartctl cannot access my storage, need syntax help] Max Nikulin <manikulin@gmail.com> - 2024-01-18 17:40 +0100
Re: normally start new xterms "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-18 20:10 +0100
Re: normally start new xterms conover@panix.com (John Conover) - 2024-01-18 20:20 +0100
Re: normally start new xterms "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-18 21:20 +0100
Re: normally start new xterms conover@panix.com (John Conover) - 2024-01-18 21:40 +0100
Re: normally start new xterms <tomas@tuxteam.de> - 2024-01-19 06:50 +0100
Re: normally start new xterms <tomas@tuxteam.de> - 2024-01-19 09:10 +0100
Re: normally start new xterms "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-19 10:20 +0100
Re: normally start new xterms <tomas@tuxteam.de> - 2024-01-19 10:40 +0100
Re: normally start new xterms "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-19 09:10 +0100
Re: normally start new xterms David Wright <deblis@lionunicorn.co.uk> - 2024-01-19 18:10 +0100
Re: normally start new xterms Henning Follmann <hfollmann@itcfollmann.com> - 2024-01-19 15:20 +0100
Re: normally start new xterms <tomas@tuxteam.de> - 2024-01-19 16:10 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-18 04:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 22:20 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 08:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 16:40 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 17:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 21:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 22:10 +0100
Re: smartctl cannot access my storage, need syntax help Curt <curty@free.fr> - 2024-01-17 17:40 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-17 18:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 21:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 22:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-18 01:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-18 02:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-18 05:30 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-18 07:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-18 07:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-18 10:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-18 12:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-18 22:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-19 07:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-19 08:30 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-19 22:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-20 01:20 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-20 02:30 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-20 06:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-20 08:00 +0100
Re: smartctl cannot access my storage, need syntax help Max Nikulin <manikulin@gmail.com> - 2024-01-20 16:30 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-20 21:30 +0100
Re: smartctl cannot access my storage, need syntax help Max Nikulin <manikulin@gmail.com> - 2024-01-21 06:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-21 07:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-21 12:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-21 22:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-21 23:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-22 00:30 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-22 06:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-22 10:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-22 12:30 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-22 19:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-22 20:40 +0100
Re: smartctl cannot access my storage, need syntax help Stefan Monnier <monnier@iro.umontreal.ca> - 2024-01-22 22:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-23 00:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 03:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-23 04:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 05:00 +0100
Powered USB hub [was: Re: smartctl cannot access my storage, need syntax help] Max Nikulin <manikulin@gmail.com> - 2024-01-23 05:20 +0100
Re: Powered USB hub [was: Re: smartctl cannot access my storage, needsyntax help] gene heskett <gheskett@shentel.net> - 2024-01-23 06:10 +0100
Re: Powered USB hub [was: Re: smartctl cannot access my storage, need syntax help] Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-25 11:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-23 08:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 12:10 +0100
Re: smartctl cannot access my storage, need syntax help Stefan Monnier <monnier@iro.umontreal.ca> - 2024-01-23 04:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 12:50 +0100
Re: smartctl cannot access my storage, need syntax help Karl Vogel <vogelke@pobox.com> - 2024-01-23 06:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 12:10 +0100
Re: smartctl cannot access my storage, need syntax help Gremlin <scott-andrews@columbus.rr.com> - 2024-01-23 12:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-23 12:40 +0100
Re: smartctl cannot access my storage, need syntax help Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-25 15:10 +0100
Re: smartctl cannot access my storage, need syntax help "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-01-25 18:20 +0100
Re: smartctl cannot access my storage, need syntax help Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-26 12:50 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-29 06:20 +0100
Re: smartctl cannot access my storage, need syntax help Karl Vogel <vogelke@pobox.com> - 2024-01-24 09:30 +0100
Re: smartctl cannot access my storage, need syntax help Max Nikulin <manikulin@gmail.com> - 2024-01-21 10:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-21 18:40 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-19 05:10 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-18 08:40 +0100
Re: smartctl cannot access my storage, need syntax help Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-19 09:20 +0100
Re: smartctl cannot access my storage, need syntax help "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-19 11:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-19 13:10 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-19 13:00 +0100
Re: smartctl cannot access my storage, need syntax help Curt <curty@free.fr> - 2024-01-18 17:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 21:20 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-17 18:10 +0100
Re: smartctl cannot access my storage, need syntax help Charles Curley <charlescurley@charlescurley.com> - 2024-01-18 08:20 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 02:10 +0100
Re: smartctl cannot access my storage, need syntax help David Wright <deblis@lionunicorn.co.uk> - 2024-01-17 03:00 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-17 05:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-15 08:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 15:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-15 23:00 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-16 00:40 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 00:50 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 07:10 +0100
Re: smartctl cannot access my storage, need syntax help Felix Miata <mrmazda@earthlink.net> - 2024-01-16 07:20 +0100
Re: smartctl cannot access my storage, need syntax help Andy Smith <andy@strugglers.net> - 2024-01-16 17:40 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 02:50 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-17 02:30 +0100
Re: smartctl cannot access my storage, need syntax help gene heskett <gheskett@shentel.net> - 2024-01-15 17:10 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 00:10 +0100
Re: smartctl cannot access my storage, need syntax help Franco Martelli <martellif67@gmail.com> - 2024-01-16 21:00 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-16 22:10 +0100
To partition or not to partition MD arrays (Was Re: smartctl cannot access my storage, need syntax help) Andy Smith <andy@strugglers.net> - 2024-01-16 22:40 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannot access my storage, need syntax help) Steve McIntyre <steve@einval.com> - 2024-01-18 02:00 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) gene heskett <gheskett@shentel.net> - 2024-01-18 04:40 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-01-18 17:30 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Andy Smith <andy@strugglers.net> - 2024-01-18 18:10 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannot access my storage, need syntax help) Andy Smith <andy@strugglers.net> - 2024-01-18 15:20 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannot access my storage, need syntax help) Steve McIntyre <steve@einval.com> - 2024-01-18 17:10 +0100
Re: mdraid construction and testing (was: smartctl cannot access my stor...) Felix Miata <mrmazda@earthlink.net> - 2024-01-16 23:00 +0100
Testing storage performance (Was Re: mdraid construction and testing (was: smartctl cannot access my stor...)) Andy Smith <andy@strugglers.net> - 2024-01-17 04:40 +0100
Re: smartctl cannot access my storage, need syntax help Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-01-19 09:10 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Franco Martelli <martellif67@gmail.com> - 2024-01-19 20:10 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Nicolas George <george@nsup.org> - 2024-01-19 20:20 +0100
Re: To partition or not to partition MD arrays (Was Re: smartctl cannotaccess my storage, need syntax help) Franco Martelli <martellif67@gmail.com> - 2024-01-19 20:50 +0100
Re: smartctl cannot access my storage, need syntax help David Christensen <dpchrist@holgerdanske.com> - 2024-01-19 21:10 +0100
Page 3 of 9 — ← Prev page 1 2 [3] 4 5 6 7 8 9 Next page →
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2024-01-17 01:20 +0100 |
| Message-ID | <HX1OV-3Aoi-1@gated-at.bofh.it> |
| In reply to | #266072 |
On Tue 16 Jan 2024 at 09:40:19 (-0500), Greg Wooledge wrote: > On Tue, Jan 16, 2024 at 09:31:54AM -0500, Felix Miata wrote: > > David Wright composed on 2024-01-16 08:05 (UTC-0600): > > > On Tue 16 Jan 2024 at 00:55:52 (-0500), Felix Miata wrote: > > >> gene heskett composed on 2024-01-15 17:56 (UTC-0500): > > > > >>> Thanks for that composition: but it will be word wrapped: > > >>> root@coyote:~# for j in /dev/disk/by-id/* ; do printf '%s\t%s\n' > > >>> "$(realpath "$j")" "$j" ; done > > >>> /dev/sr0 /dev/disk/by-id/ata-ATAPI_iHAS424_B_3524253_327133504865 > > >>> /dev/sdi /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146 > > >>> /dev/sdj1 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1 > > > > > It's right here at the top. > > > > I missed that, probably because i & j look similar in the big sea of > > alphanumerics, /and/ sdi has no partitions, while sdj1 has no parent disk. That > > seems to smell as much like a bug somewhere as two different disks with the same > > serial number, a cheap SATA port card maybe. Does ...1146 get duplication like > > that when connected to any/every available SATA port? > > I missed it too. It actually looks like someone copy/pasted the > pathnames on the right, but then manually typed the device names on > the left, and made a typo here. Or, somehow, the device names and > the pathnames got mixed together, and someone tried to separate them > manually, and got these two crossed. It's the sticky labels that convinced me. I had one last possibility in mind, that the serial numbers were being generated by the interfaces somehow, but they wouldn't be able to read the labels. I know nothing about Gene's interfaces, but my SD cards can appear with false by-id/ values depending on where they're plugged in: slots (on different PCs), via µSD-SD adapter, SD-USB adapter, etc. Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-16 17:10 +0100 |
| Message-ID | <HWUaJ-3vIY-25@gated-at.bofh.it> |
| In reply to | #266070 |
Hi, i, too, wondered where there should be a duplicate serial number. But indeed: David Wright wrote: > > /dev/sdi 53 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146 > > /dev/sdj1 54 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1 > ↑↑↑↑↑↑↑↑↑ that is /really/ bad! Does the number of 4 device files /dev/sd[h-k] match the number of installed ata-Gigastone_SSD devices ? Gene talked of "5, ordered in 2 separate orders". (Looking at https://lists.debian.org/debian-user/2024/01/msg00667.html) Now we see 3 to 4, depending on what one wants to believe. Wild ideas: One possible reason could be that a device is mapped to both, /dev/sdi and /dev/sdj. udev would then suffer a race condition when creating the /dev/disk/by-id. Another could be that udev's assessment of the drives derails and that serial number information spilled from the assessment of /dev/sdi to the assessment of /dev/sdj*. It would be interesting to see the output of ls -l /dev/sd[ij]* in order to learn about the existence of /dev/sdj and the the device numbers of sdi* and sdj*. Further one should inquire the serial numbers by lsblk -d -o NAME,MAJ:MIN,MODEL,SERIAL,WWN /dev/sd[hijk] Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-17 03:20 +0100 |
| Message-ID | <HX3H3-3Btl-3@gated-at.bofh.it> |
| In reply to | #266077 |
On 1/16/24 11:08, Thomas Schmitt wrote: > ls -l /dev/sd[ij]* oot@coyote:~# ls -l /dev/sd[ij]* brw-rw---- 1 root disk 8, 128 Jan 16 05:01 /dev/sdi brw-rw---- 1 root disk 8, 129 Jan 16 05:01 /dev/sdi1 brw-rw---- 1 root disk 8, 144 Jan 16 05:01 /dev/sdj brw-rw---- 1 root disk 8, 145 Jan 16 05:01 /dev/sdj1 root@coyote:~# lsblk -d -o NAME,MAJ:MIN,MODEL,SERIAL,WWN /dev/sd[hijkl] gene@coyote:~/src/klipper-docs$ lsblk -d -o NAME,MAJ:MIN,MODEL,SERIAL,WWN /dev/sd[hijkl] NAME MAJ:MIN MODEL SERIAL WWN sdh 8:112 Gigastone SSD GSTD02TB230102 sdi 8:128 Gigastone SSD GST02TBG221146 sdj 8:144 Gigastone SSD GST02TBG221146 sdk 8:160 Gigastone SSD GSTG02TB230206 sdl 8:176 Gigastone SSD GSTG02TB230206 note added l to get them all gene@coyote:~/src/klipper-docs$ 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
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-17 07:00 +0100 |
| Message-ID | <HX77X-3DyT-1@gated-at.bofh.it> |
| In reply to | #266099 |
On 1/16/24 17:08, gene heskett wrote: > lsblk, which I've published several times, shows 5 drives. by-id listing > only shows 3. The drive I've been trying to use bounces from /dev/sdd to > sde to sdh dependin on which controller it is curently plugged into. > > And I've since tried cp in addition to rsync, does the same thing, > killing the sysytem with the OOM but much quicker. cp using all system > memory (32Gb) in 1 minute, another 500K into swap adds another 15 secs, > and the OOM kills the system. So both cp and rsync act broken. > > rsync, with a --bwlimit=3m set, takes much longer to kill the system but > the amount of data moved is very similar, 13.5G from clean disk to > system freeze for rsync, 13.4G for cp. On 1/16/24 18:10, gene heskett wrote: > On 1/16/24 11:08, Thomas Schmitt wrote: >> ls -l /dev/sd[ij]* > oot@coyote:~# ls -l /dev/sd[ij]* > brw-rw---- 1 root disk 8, 128 Jan 16 05:01 /dev/sdi > brw-rw---- 1 root disk 8, 129 Jan 16 05:01 /dev/sdi1 > brw-rw---- 1 root disk 8, 144 Jan 16 05:01 /dev/sdj > brw-rw---- 1 root disk 8, 145 Jan 16 05:01 /dev/sdj1 > root@coyote:~# > > lsblk -d -o NAME,MAJ:MIN,MODEL,SERIAL,WWN /dev/sd[hijkl] > gene@coyote:~/src/klipper-docs$ lsblk -d -o > NAME,MAJ:MIN,MODEL,SERIAL,WWN /dev/sd[hijkl] > NAME MAJ:MIN MODEL SERIAL WWN > sdh 8:112 Gigastone SSD GSTD02TB230102 > sdi 8:128 Gigastone SSD GST02TBG221146 > sdj 8:144 Gigastone SSD GST02TBG221146 > sdk 8:160 Gigastone SSD GSTG02TB230206 > sdl 8:176 Gigastone SSD GSTG02TB230206 I suggest removing one GST02TBG221146 and one GSTG02TB230206. Put them on the shelf, in other computer(s), or sell them. Then perhaps copying the /home RAID10 2 TB to one Gigastone 2 TB SSD would work. David
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-17 15:30 +0100 |
| Message-ID | <HXf5v-3IsJ-1@gated-at.bofh.it> |
| In reply to | #266103 |
On 1/17/24 00:52, David Christensen wrote:
> On 1/16/24 17:08, gene heskett wrote:
> > lsblk, which I've published several times, shows 5 drives. by-id listing
> > only shows 3. The drive I've been trying to use bounces from /dev/sdd to
> > sde to sdh dependin on which controller it is curently plugged into.
> >
> > And I've since tried cp in addition to rsync, does the same thing,
> > killing the sysytem with the OOM but much quicker. cp using all system
> > memory (32Gb) in 1 minute, another 500K into swap adds another 15 secs,
> > and the OOM kills the system. So both cp and rsync act broken.
> >
> > rsync, with a --bwlimit=3m set, takes much longer to kill the system but
> > the amount of data moved is very similar, 13.5G from clean disk to
> > system freeze for rsync, 13.4G for cp.
>
>
> On 1/16/24 18:10, gene heskett wrote:
>> On 1/16/24 11:08, Thomas Schmitt wrote:
>>> ls -l /dev/sd[ij]*
>> oot@coyote:~# ls -l /dev/sd[ij]*
>> brw-rw---- 1 root disk 8, 128 Jan 16 05:01 /dev/sdi
>> brw-rw---- 1 root disk 8, 129 Jan 16 05:01 /dev/sdi1
>> brw-rw---- 1 root disk 8, 144 Jan 16 05:01 /dev/sdj
>> brw-rw---- 1 root disk 8, 145 Jan 16 05:01 /dev/sdj1
>> root@coyote:~#
>>
>> lsblk -d -o NAME,MAJ:MIN,MODEL,SERIAL,WWN /dev/sd[hijkl]
>> gene@coyote:~/src/klipper-docs$ lsblk -d -o
>> NAME,MAJ:MIN,MODEL,SERIAL,WWN /dev/sd[hijkl]
>> NAME MAJ:MIN MODEL SERIAL WWN
>> sdh 8:112 Gigastone SSD GSTD02TB230102
>> sdi 8:128 Gigastone SSD GST02TBG221146
>> sdj 8:144 Gigastone SSD GST02TBG221146
>> sdk 8:160 Gigastone SSD GSTG02TB230206
>> sdl 8:176 Gigastone SSD GSTG02TB230206
>
>
> I suggest removing one GST02TBG221146 and one GSTG02TB230206. Put them
> on the shelf, in other computer(s), or sell them. Then perhaps copying
> the /home RAID10 2 TB to one Gigastone 2 TB SSD would work.
>
>
> David
>
> .
Or LABEL them.
And I seem to be making some progress this morning. opening a konsole
and setting scrollback to 200 lines, limiting its use of memory, the tan
memory bar in htop if full scale and it a couple megs into swap out of
107G. and the system still feels normal.
in another multitabbed xfce4 shell, a "df && free" is showing this:
root@coyote:~# df && free
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16327704 0 16327704 0% /dev
tmpfs 3272684 1904 3270780 1% /run
/dev/sda1 863983352 22346276 797675428 3% /
tmpfs 16363420 1244 16362176 1% /dev/shm
tmpfs 5120 8 5112 1% /run/lock
/dev/sda3 47749868 580 45291280 1% /tmp
/dev/md0p1 1796382580 335100148 1369957456 20% /home
tmpfs 3272684 3752 3268932 1% /run/user/1000
/dev/sdh1 1967892164 23830812 1844025104 2% /mnt/homevol
total used free shared buff/cache
available
Mem: 32726840 3343048 218316 922196 30443960
29383792
Swap: 111902712 1536 111901176
root@coyote:~#
rsync has been stopped and restarted, 4 times, but stopping it has not
recovered the cache, so swap is increasing slowly.
That faint knocking sound? Me, knocking on wood... ;o)>
command line: rsync -a --bwlimit=10m --fsync --progress /home/ /mnt/homevol
So we'll eventually either git-r-done or crask the system but this is
farther than it ever got before in several days.
Thanks everybody.
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
[toc] | [prev] | [next] | [standalone]
| From | David Christensen <dpchrist@holgerdanske.com> |
|---|---|
| Date | 2024-01-17 18:10 +0100 |
| Message-ID | <HXhAm-3K1Z-23@gated-at.bofh.it> |
| In reply to | #266117 |
On 1/17/24 06:18, gene heskett wrote: > On 1/17/24 00:52, David Christensen wrote: >> I suggest removing one GST02TBG221146 and one GSTG02TB230206. Put >> them on the shelf, in other computer(s), or sell them. Then perhaps >> copying the /home RAID10 2 TB to one Gigastone 2 TB SSD would work. > > Or LABEL them. I suspect the conflicting serial numbers are causing problems in the kernel, as indicated by the /dev/disk/by-id/* problems. I would remove one each of the duplicate serial number disks to eliminate that possibility. David > Cheers, Gene Heskett.
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-17 18:30 +0100 |
| Message-ID | <HXhTH-3K8d-1@gated-at.bofh.it> |
| In reply to | #266125 |
Hi, David Christensen wrote: > I suspect the conflicting serial numbers are causing problems in the kernel, > as indicated by the /dev/disk/by-id/* problems. That's not in the kernel but in udev/systemd's process of creating the symbolic links in /dev/disk/by-id/. It gets /dev/sd[h-l] and /dev/sd[h-l]1 as kernel generated device files. But sd[ij] and also sd[hl] show pair-wise the same serial numbers. In case of sd[ij] the outcome is mixed: links to sdi and sdj1 survive. In case of sd[hl] we see a less strange outcome: sdh and sdh1, while sdl and sdl1 are missing. The open question (at least to me) is whether it's the disks or the controllers or the drivers which cause the duplication. Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-17 20:40 +0100 |
| Message-ID | <HXjVv-3Ljg-5@gated-at.bofh.it> |
| In reply to | #266127 |
Hi, i see that i messed up "h" and "k" in my explanation of the fight over the link targets in /dev/disk/by-id. So another attempt: sdh has a unique serial number GSTD02TB230102. Thus we see in https://lists.debian.org/debian-user/2024/01/msg00667.html these two links: /dev/sdh /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102 /dev/sdh1 /dev/disk/by-id/ata-Gigastone_SSD_GSTD02TB230102-part1 sdi and sdj share the serial number GST02TBG221146. So the concurrent attempts to create the links let only these two survive: /dev/sdi /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146 /dev/sdj1 /dev/disk/by-id/ata-Gigastone_SSD_GST02TBG221146-part1 sdk and sdl share GSTG02TB230206. The survivors are: /dev/sdk /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206 /dev/sdk1 /dev/disk/by-id/ata-Gigastone_SSD_GSTG02TB230206-part1 The next system startup might yield other survivors. Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-17 21:40 +0100 |
| Message-ID | <HXkRz-3LRz-1@gated-at.bofh.it> |
| In reply to | #266127 |
On 1/17/24 12:27, Thomas Schmitt wrote: > Hi, > > David Christensen wrote: >> I suspect the conflicting serial numbers are causing problems in the kernel, >> as indicated by the /dev/disk/by-id/* problems. > > That's not in the kernel but in udev/systemd's process of creating the > symbolic links in /dev/disk/by-id/. > It gets /dev/sd[h-l] and /dev/sd[h-l]1 as kernel generated device files. > But sd[ij] and also sd[hl] show pair-wise the same serial numbers. > In case of sd[ij] the outcome is mixed: links to sdi and sdj1 survive. > In case of sd[hl] we see a less strange outcome: sdh and sdh1, while > sdl and sdl1 are missing. > missing because the original command line did not look at sdl. I added the l and it showed up. No magic. > The open question (at least to me) is whether it's the disks or the > controllers or the drivers which cause the duplication. Neither, a typu in the original command. > > > Have a nice day :) > > Thomas > > . 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
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-17 22:20 +0100 |
| Message-ID | <HXluh-3Mkj-1@gated-at.bofh.it> |
| In reply to | #266143 |
Hi, i wrote: > > What did finally help ? Just the shorter terminal scroll back memory ? gene heskett wrote: > That, and possibly the --bwlimit=10m, giving the SSD time to keep their > stuff in one sock. Then i place my bet on the terminal alone. Linux is able to handle disk-to-disk copies that are larger than the available memory. This is a standard use case. > > How large was it set when your runs caused the OOM killer to act ? > different terminal, xfce4's is apparently unlimited but can't find it in the > config prefs. I normally start new xterms by xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb & The -sl option gives the number of lines to be memorized for scrollback. Black-on-wheat is a calmative color combination which does not overwork the eyes. Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | gene heskett <gheskett@shentel.net> |
|---|---|
| Date | 2024-01-17 22:40 +0100 |
| Message-ID | <HXlND-3Mq8-1@gated-at.bofh.it> |
| In reply to | #266146 |
On 1/17/24 16:16, Thomas Schmitt wrote: > Hi, > > i wrote: >>> What did finally help ? Just the shorter terminal scroll back memory ? > > gene heskett wrote: >> That, and possibly the --bwlimit=10m, giving the SSD time to keep their >> stuff in one sock. > > Then i place my bet on the terminal alone. > Linux is able to handle disk-to-disk copies that are larger than the > available memory. This is a standard use case. > > >>> How large was it set when your runs caused the OOM killer to act ? > >> different terminal, xfce4's is apparently unlimited but can't find it in the >> config prefs. > > I normally start new xterms by > > xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb & > > The -sl option gives the number of lines to be memorized for scrollback. > Black-on-wheat is a calmative color combination which does not overwork > the eyes. > Thank you, I did not know that. > > Have a nice day :) > > Thomas > > . 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
[toc] | [prev] | [next] | [standalone]
| From | Max Nikulin <manikulin@gmail.com> |
|---|---|
| Date | 2024-01-18 17:40 +0100 |
| Subject | normally start new xterms [was: Re: smartctl cannot access my storage, need syntax help] |
| Message-ID | <HXDAS-3XbX-11@gated-at.bofh.it> |
| In reply to | #266146 |
On 18/01/2024 04:20, Thomas Schmitt wrote: > > I normally start new xterms by > > xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb & Options may be put into ~/.Xresources xterm*vt100.saveLines: 10000 xterm*VT100.background: wheat xterm*VT100.foreground: black ! etc Use xrdb to merge changes without restarting X session. It is possible to have several presets (-name or -class), see /etc/X11/app-defaults/
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-18 20:10 +0100 |
| Subject | Re: normally start new xterms |
| Message-ID | <HXFW2-3YJ7-5@gated-at.bofh.it> |
| In reply to | #266213 |
Hi, i wrote: > > xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb & Max Nikulin wrote: > Options may be put into ~/.Xresources > xterm*vt100.saveLines: 10000 > xterm*VT100.background: wheat > xterm*VT100.foreground: black I have it in ~/.fvwm2rc as: *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb This causes a button in the button box which creates a new xterm when clicked. Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | conover@panix.com (John Conover) |
|---|---|
| Date | 2024-01-18 20:20 +0100 |
| Subject | Re: normally start new xterms |
| Message-ID | <HXG5H-3YM7-3@gated-at.bofh.it> |
| In reply to | #266226 |
Thomas Schmitt writes:
> Hi,
>
> i wrote:
> > > xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb &
>
> Max Nikulin wrote:
> > Options may be put into ~/.Xresources
> > xterm*vt100.saveLines: 10000
> > xterm*VT100.background: wheat
> > xterm*VT100.foreground: black
>
> I have it in ~/.fvwm2rc as:
>
> *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb
^^^^
Action 'Exec exec xterm ...'
Maybe
John
>
> This causes a button in the button box which creates a new xterm when
> clicked.
>
--
John Conover, conover@panix.com, http://www.johncon.com/
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-18 21:20 +0100 |
| Subject | Re: normally start new xterms |
| Message-ID | <HXH1M-3Zkd-5@gated-at.bofh.it> |
| In reply to | #266229 |
Hi, i wrote: > > *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb John Conover wrote: > ^^^^ > Action 'Exec exec xterm ...' The framework of this line probably stems from a SuSE Linux of 1999. It still works with the fvwm of Debian 11. I now read man 1 FvwmButtons. All applicable descriptions and examples demand the keyword "Action". The "exec" before "xterm" is used in some examples of the man page and mentioned already in my S.R.Bourne of 1983 (without "xterm", of course). As reasoning i found https://www.fvwm.org/Wiki/Tips/FvwmStartup/#33-use-exec-exec-to-prevent-unnecessary-dead-shell-processes I have 63 such processes lingering around. But there are 131 xterms. Many of them have process 1 as parent. Probably they stem from a script which i use to populate the 8 "desktops" by a handful of xterms when the system comes up. Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | conover@panix.com (John Conover) |
|---|---|
| Date | 2024-01-18 21:40 +0100 |
| Subject | Re: normally start new xterms |
| Message-ID | <HXHl7-3Zqk-7@gated-at.bofh.it> |
| In reply to | #266230 |
Thanks Thomas.
Have a good one ...
John
Thomas Schmitt writes:
> Hi,
>
> i wrote:
> > > *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb
>
> John Conover wrote:
> > ^^^^
> > Action 'Exec exec xterm ...'
>
> The framework of this line probably stems from a SuSE Linux of 1999.
> It still works with the fvwm of Debian 11.
>
> I now read man 1 FvwmButtons. All applicable descriptions and examples
> demand the keyword "Action".
>
> The "exec" before "xterm" is used in some examples of the man page and
> mentioned already in my S.R.Bourne of 1983 (without "xterm", of course).
> As reasoning i found
> https://www.fvwm.org/Wiki/Tips/FvwmStartup/#33-use-exec-exec-to-prevent-unnecessary-dead-shell-processes
> I have 63 such processes lingering around. But there are 131 xterms.
> Many of them have process 1 as parent. Probably they stem from a script
> which i use to populate the 8 "desktops" by a handful of xterms when the
> system comes up.
>
>
> Have a nice day :)
>
> Thomas
--
John Conover, conover@panix.com, http://www.johncon.com/
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-01-19 06:50 +0100 |
| Subject | Re: normally start new xterms |
| Message-ID | <HXPVn-44CY-1@gated-at.bofh.it> |
| In reply to | #266226 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Jan 18, 2024 at 08:06:24PM +0100, Thomas Schmitt wrote: [...] > I have it in ~/.fvwm2rc as: > > *FvwmButtons xterm_ts5 linuxterm.xpm Exec xterm -ls -geometry 80x24 -bg wheat -fg black -sl 10000 +sb > > This causes a button in the button box which creates a new xterm when > clicked. I coopted the otherwise useless "Windows" key (aka "Left Super" for WM things: Super-L makes an xterm: # Terminal Key "t" A 4 Exec exec xterm (The "4" is the modifier, i.e. Super L). There are more of them, like starting an Emacs frame, starting a special frame with a specific buffer for quick notes and things, moving to workspaces, maximizing/demaximizing,etc. Cheers -- t
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-01-19 09:10 +0100 |
| Subject | Re: normally start new xterms |
| Message-ID | <HXS6R-465v-5@gated-at.bofh.it> |
| In reply to | #266246 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Jan 19, 2024 at 09:06:05AM +0100, Thomas Schmitt wrote:
> Hi,
>
> tomas@tuxteam.de wrote:
> > I coopted the otherwise useless "Windows" key (aka "Left Super" for
> > WM things: Super-L makes an xterm:
> > # Terminal
> > Key "t" A 4 Exec exec xterm
>
> For me the Flying Windows keys pop up or push down the affected window:
>
> Key Super_L A N RaiseLower
> Key Super_R A N RaiseLower
>
> What i don't understand in your example is the Keyname "t".
> man fvwm points me to /usr/include/X11/keysymdef.h or
> /usr/X11R6/lib/X11/XKeysymDB (which seems not exist in Debian except
> a file "XKeysymDB" of ipackage "xemacs21-support").
>
> Do you know documentation which describes your "t" ?
It's Modifier (that Flying Window thing), aka "4" and the regular "t"
(my mnemonics: "terminal").
What I forgot to say is that I set up that key Whose Name Won't Be
Mentioned to act as a modifier:
setxkbmap -model pc105 \
-layout "de,el" \
-variant "deadtilde," \
-option "compose:caps" \
-option "altwin:alt_super_win" \
-option "terminate:ctrl_alt_bksp" \
-option "grp:shifts_toggle"
(the fifth line -- the others do other funny things ;-) This is
in my ~/.xinitrc, but could possibly go to /etc/default/keyboard;
too lazy to try out at the moment.
Cheers
--
t
[toc] | [prev] | [next] | [standalone]
| From | "Thomas Schmitt" <scdbackup@gmx.net> |
|---|---|
| Date | 2024-01-19 10:20 +0100 |
| Subject | Re: normally start new xterms |
| Message-ID | <HXTcB-46Gs-1@gated-at.bofh.it> |
| In reply to | #266254 |
Hi, tomas@tuxteam.de wrote: > > > I coopted the otherwise useless "Windows" key (aka "Left Super" for > > > WM things: Super-L makes an xterm: > > > # Terminal > > > Key "t" A 4 Exec exec xterm i wrote: > > For me the Flying Windows keys pop up or push down the affected window: > > Key Super_L A N RaiseLower > > Key Super_R A N RaiseLower > > What i don't understand in your example is the Keyname "t". tomas@tuxteam.de wrote: > It's Modifier (that Flying Window thing), aka "4" and the regular "t" > (my mnemonics: "terminal"). Ah. You use it as modifier for other keys, i use it as plain key. The quotation marks around "t" are only ornamental ? Have a nice day :) Thomas
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2024-01-19 10:40 +0100 |
| Subject | Re: normally start new xterms |
| Message-ID | <HXTvX-46Mr-3@gated-at.bofh.it> |
| In reply to | #266262 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Jan 19, 2024 at 10:16:56AM +0100, Thomas Schmitt wrote: > Hi, [...] > tomas@tuxteam.de wrote: > > It's Modifier (that Flying Window thing), aka "4" and the regular "t" > > (my mnemonics: "terminal"). > > Ah. You use it as modifier for other keys, i use it as plain key. Yes, I was avid for keys (small laptop here :) > The quotation marks around "t" are only ornamental ? Most probably yes. Most probably also cargo cult :-) Cheers -- t
[toc] | [prev] | [next] | [standalone]
Page 3 of 9 — ← Prev page 1 2 [3] 4 5 6 7 8 9 Next page →
Back to top | Article view | linux.debian.user
csiph-web