The install didn't switch it, and gnome won't show me the tools.
Help!
Cheers, Gene Heskett
On Tuesday 02 April 2019 20.11:04 Gene Heskett wrote:
The install didn't switch it, and gnome won't show me the tools.
Help!
Cheers, Gene Heskett
Hi Gene,
What do you exactly mean? I guess: you upgraded and you find yourself with Gnome 3?
If that's the case, to get tdm back do this:
dpkg-reconfigure gdm3 dpkg-reconfigure tdm-trinity
You should also manage to get to a login screen, to be able to choose a tde session.
Hope this helps,
Thierry
On Tuesday 02 April 2019 15:18:44 Thierry de Coulon wrote:
On Tuesday 02 April 2019 20.11:04 Gene Heskett wrote:
The install didn't switch it, and gnome won't show me the tools.
Help!
Cheers, Gene Heskett
Hi Gene,
What do you exactly mean? I guess: you upgraded and you find yourself with Gnome 3?
yes, from wheezy on sda, to stretch on sdb
If that's the case, to get tdm back do this:
dpkg-reconfigure gdm3 dpkg-reconfigure tdm-trinity
I assume this is as root while on stretch?
You should also manage to get to a login screen, to be able to choose a tde session.
ATM, it goes straight to a gnome login asking me for my user pw. I didn't note if there was a session clicker or not. My mistake I expect.
While I've been waiting, I've copied most of my wheezy homedir to the stretch homedir, so I should have all my Mail and such once I can run kmail.
Hope this helps,
Thierry
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
On Tuesday 02 April 2019 13:19:12 deloptes wrote:
Gene Heskett wrote:
If that's the case, to get tdm back do this:
dpkg-reconfigure gdm3 dpkg-reconfigure tdm-trinity
I assume this is as root while on stretch?
correct
When you were installing, did you click to allow root login? or is there some other program where you allow it, e.g.:
TCC / System Administration / Login Manager / Convenience (You must open as root to make these changes.)
Also, if you are in Debian, you can open a root shell and accomplish this by changing users and groups, etc. (By the way, since you were having problems with menus earlier, which seemed password-related, maybe this is more of the same, and points to a similar cause for both. Could be this was on a different system?) Also I seem to recall some gui thingie which can do it.
On Debian systems, I allow shadow passwords, but not root logins; at least, not on the first install. On another system, where I could have others occasionally getting into trouble, I might enable that, and disable sudo privileges for all users except myself; but on this, I am the only user, and there is nothing anybody could access on my system without actually sitting in my chair with my machine running ... which, unless it happens at gunpoint, seems unlikely.
Bill
On 04/02/2019 01:10 PM, Gene Heskett wrote:
ATM, it goes straight to a gnome login asking me for my user pw. I didn't note if there was a session clicker or not. My mistake I expect.
I don't know about gdm, but tdm and lightdm both will auto-login to whatever desktop you last logged in to. To switch, logout, then select the session type at the display manager's login screen, and login.
On Tuesday 02 April 2019 18:36:14 Dan Youngquist wrote:
On 04/02/2019 01:10 PM, Gene Heskett wrote:
ATM, it goes straight to a gnome login asking me for my user pw. I didn't note if there was a session clicker or not. My mistake I expect.
I don't know about gdm, but tdm and lightdm both will auto-login to whatever desktop you last logged in to. To switch, logout, then select the session type at the display manager's login screen, and login.
Well, ATM I'm ready to shoot all the neighborhood cats. Something is shutting the stretch system off in about 5 minutes of mouse or keyboard inactivity, so I've had to recompose an install list and restart synaptic 5 or 6 times now.
Then, to add insult to injury, the default system partition it sets up during the install for /, when you ask it for a separate /home, on a 2 terabyte drive is 30 GB. Hell's bells, my amanda database alone is 70GB, and its a backup of /usrlocal/etc/amanda and /usr/local/var/amanda! So I makes no sense to have less than 500GB for the / partition.
I have never had ant great success at pre-partitioning a drive, the installer never accepts what you so carefully lay out with gparted, and the SOB uses so archaic a syntax you never know exactly what you have until the install is done, but I've got to try one more time if I can't get gparted to move stuff around and make it work. Right now I've wasted 14 hours on this and have yet to see a tde login. I've got some tde stuff, but its all sitting on a gnome screen. Grrrrr. Later, as in sometime tomorrow IF gparted can fix it.
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
Gene Heskett composed on 2019-04-02 21:50 (UTC-0400):
I have never had ant great success at pre-partitioning a drive, the installer never accepts what you so carefully lay out
This should not be. I *always* partition in advance, never have a problem with any Debian installer using partitions as I specify. Maybe you should try again, but before trying installation, after partitioning, show us output from:
parted -l and/or fdisk -l
to see if that's where your trouble lies.
On Tuesday 02 April 2019 22:05:41 Felix Miata wrote:
Gene Heskett composed on 2019-04-02 21:50 (UTC-0400):
I have never had ant great success at pre-partitioning a drive, the installer never accepts what you so carefully lay out
This should not be. I *always* partition in advance, never have a problem with any Debian installer using partitions as I specify. Maybe you should try again, but before trying installation, after partitioning, show us output from:
parted -l
gene@coyote:~/Mail/emc$ parted -l Model: ATA ST1000VX000-1CU1 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 983GB 983GB primary ext4 boot 2 983GB 1000GB 17.2GB extended 5 983GB 1000GB 17.2GB logical linux-swap(v1)
Model: ATA ST2000DM006-2DM1 (scsi) Disk /dev/sdb: 2000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 524GB 524GB primary ext4 2 524GB 545GB 21.0GB primary linux-swap(v1) 3 545GB 2000GB 1455GB primary ext4
Model: ATA ST31000333AS (scsi) Disk /dev/sdc: 1000GB Sector size (logical/physical): 512B/512B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 525MB 524MB primary ext4 boot 2 525MB 1000GB 1000GB primary ext3
Model: ATA ST2000DM001-1ER1 (scsi) Disk /dev/sdd: 2000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos
Number Start End Size Type File system Flags 1 1049kB 6817MB 6816MB primary ext4 2 6817MB 2000GB 1994GB primary ext4
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0 has been opened read-only. Model: ATAPI iHAS424 B (scsi) Disk /dev/sr0: 306MB Sector size (logical/physical): 2048B/2048B Partition Table: mac
Number Start End Size File system Name Flags 1 8192B 24.6kB 16.4kB Apple 2 7725kB 9429kB 1704kB EFI
and/or fdisk -l
to see if that's where your trouble lies.
and fdisk -l: gene@coyote:~/Mail/emc$ sudo fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x000657ed
Device Boot Start End Blocks Id System /dev/sda1 * 2048 1919977471 959987712 83 Linux /dev/sda2 1919979518 1953523711 16772097 5 Extended Partition 2 does not start on physical sector boundary. /dev/sda5 1919979520 1953523711 16772096 82 Linux swap / Solaris
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x0006aa28
Device Boot Start End Blocks Id System /dev/sdc1 * 2048 1026047 512000 83 Linux /dev/sdc2 1026048 1953523711 976248832 83 Linux
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x8f7940d2
Device Boot Start End Blocks Id System /dev/sdb1 2048 1023999999 511998976 83 Linux /dev/sdb2 1024000000 1064959999 20480000 82 Linux swap / Solaris /dev/sdb3 1064960000 3907028991 1421034496 83 Linux
Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0000ec54
Device Boot Start End Blocks Id System /dev/sdd1 2048 13314047 6656000 83 Linux /dev/sdd2 13314048 3907026943 1946856448 83 Linux
/dev/sdb is the target disk, /dev/sda is current operating disk /dev/sdc is older, not in use amandatapes-1T disk, and /dev/sdd is currently used amandatapes-2T disk.
/dev/sdc has had 25 re-allocated sectors since day one, about 7 years back. Around 80,000 spinning hours on it now. Bad firmware when it came over the counter at staples when a 1T drive was state of the art. New firmware also upped its read and write speeds by about 40 megs/second.
Look this over please.
Cheers, Gene Heskett
Gene Heskett composed on 2019-04-03 08:16 (UTC-0400):
parted -l
gene@coyote:~/Mail/emc$ parted -l Model: ATA ST1000VX000-1CU1 (scsi)
...
Model: ATA ST2000DM006-2DM1 (scsi) Disk /dev/sdb: 2000GB
...
Model: ATA ST31000333AS (scsi) Disk /dev/sdc: 1000GB
Model: ATA ST2000DM001-1ER1 (scsi) Disk /dev/sdd: 2000GB
...
fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
...
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
...
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
...
Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
...
/dev/sdb is the target disk, /dev/sda is current operating disk /dev/sdc is older, not in use amandatapes-1T disk, and /dev/sdd is currently used amandatapes-2T disk.
Look this over please.
I see nothing in the partitioning itself that should prevent success. 500G+ for the / filesystem does seem to be at least somewhere around 200%-300% overkill. 20G-30G may well be too little for your needs, but surely 100G ought to cover it. If you're using big databases, they probably should be configured to store their data on a data partition rather than the / filesystem. I don't have any / filesystems as big as 20G (unless counting Mac or Windows, which are nevertheless under 3 digit G in size).
If the BIOS is old enough, more than around 504G for the / filesystem containing the bootloader could be another obstacle. A 200M to 500M primary partition at the start of disk just for /boot would avoid this mere potential, as should a slightly smaller / partition. My boot partitions are all EXT2. Writing to /boot is rather rare, making journaling on them arguably unnecessary overhead.
If that's Wheezy on sda, I suggest to consider to use it to format the partitions on sdb prior to installation, and ignore any objections you get from the Debian installer that it is not to be doing any formatting. Post-Wheezy at least one formerly optional/experimental formatting feature for EXT4 became default, 64bit. It's not a needed feature on smaller filesystems, as fit on a disk 2TB or smaller. Having Wheezy do the formatting will allow working with the new partitions post-installation. Alternatively, disabling 64bit (-O '^64bit') when formatting with newer mke2fs versions would have the same effect.
Questions remain as to bootloader configuration. Are sda and sdc to remain installed once successful installation is confirmed and data migration complete? If ultimately sda and sdc are to be retired, I suggest to disconnect them prior to installation, and reconnect for migration purposes only after installation success is confirmed. I might go further and temporarily disconnect sdd as well.
Is this a mix of SATA and PATA, all SATA, or all PATA? A different set of kernel and disk drivers could potentially reorder device assignments, making the order bootloader sees and the system sees differ. Booting using UUIDs or LABELs instead of device names is supposed to render any such differences of no import, but potential for confusion does remain, particularly from the perspective of an administrator's eyes.
On Wednesday 03 April 2019 12:38:12 Felix Miata wrote:
Gene Heskett composed on 2019-04-03 08:16 (UTC-0400):
parted -l
gene@coyote:~/Mail/emc$ parted -l Model: ATA ST1000VX000-1CU1 (scsi)
...
Model: ATA ST2000DM006-2DM1 (scsi) Disk /dev/sdb: 2000GB
...
Model: ATA ST31000333AS (scsi) Disk /dev/sdc: 1000GB
Model: ATA ST2000DM001-1ER1 (scsi) Disk /dev/sdd: 2000GB
...
fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
...
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
...
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
...
Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes
...
/dev/sdb is the target disk, /dev/sda is current operating disk /dev/sdc is older, not in use amandatapes-1T disk, and /dev/sdd is currently used amandatapes-2T disk.
Look this over please.
I see nothing in the partitioning itself that should prevent success. 500G+ for the / filesystem does seem to be at least somewhere around 200%-300% overkill. 20G-30G may well be too little for your needs, but surely 100G ought to cover it. If you're using big databases, they probably should be configured to store their data on a data partition rather than the / filesystem. I don't have any / filesystems as big as 20G (unless counting Mac or Windows, which are nevertheless under 3 digit G in size).
If the BIOS is old enough, more than around 504G for the / filesystem containing the bootloader could be another obstacle. A 200M to 500M primary partition at the start of disk just for /boot would avoid this mere potential, as should a slightly smaller / partition. My boot partitions are all EXT2. Writing to /boot is rather rare, making journaling on them arguably unnecessary overhead.
If that's Wheezy on sda, I suggest to consider to use it to format the partitions on sdb prior to installation, and ignore any objections you get from the Debian installer that it is not to be doing any formatting. Post-Wheezy at least one formerly optional/experimental formatting feature for EXT4 became default, 64bit. It's not a needed feature on smaller filesystems, as fit on a disk 2TB or smaller. Having Wheezy do the formatting will allow working with the new partitions post-installation. Alternatively, disabling 64bit (-O '^64bit') when formatting with newer mke2fs versions would have the same effect.
Questions remain as to bootloader configuration. Are sda and sdc to remain installed once successful installation is confirmed and data migration complete?
yes, sdc is a 2T for amanda's vtapes, and sda and sdb will be swapped so I'll be booting from the first hard drive again. This is a 10 second operation as I have an old tiger direct 3 drive hot swap drive cage, although in deference to the drives I move them only when its powered down.
And I've discovered that I can set "removeable" in the boot priority screen of the bios, so maybe it might boot from usb stick after all, but I don't have any of a suitable size for a dvd sub, netinstall maybe. Humm, just found a 16GB I don't think theres anything precious on.. But all I have is the jigdo stuffs. So it will take a while to grab dvd-1.
And the jigdo file is no good, its asking for a site that apparently no longer has a valid repo. Debian mirror [http://carroll.aset.psu.edu/pub/linux/distributions/debian/] resolves, but there is nothing there for jigdo.
I'm about burned out on this PITA. It seems to me that this problem could be fixed once and for all by simply installing grub while the partition was only at the minimal install stage, I think by waiting till the end of the install, grub is too far into the disk for a dumb messydos bios to find. Thats my theory at least. jigdo seems to be working but the mirror is stuck in molasses. This may take a day or more. And something has leaked, cups is AFU since the last failed install. Ah, usb cable didn't get plugged in again. My usb tree here if mapped, would resemble a fairly mature weeping willow. And this machine was down for a fresh psu last week.
If ultimately sda and sdc are to be retired, I suggest to disconnect them prior to installation, and reconnect for migration purposes only after installation success is confirmed. I might go further and temporarily disconnect sdd as well.
sdd is an older 1T seacrate and was used for amanda for around 85,000 hours, but has been in a hard mount slot since it was replaced with the 2T. I keep it spining so stiction doesn't lock it up. smartctl says its as good as new yet, except for the head flying hours.
Is this a mix of SATA and PATA, all SATA,
The latter. Even the floppy cable has been removed as the floppy is only used for sneaker net, and since this chipset dies, locking up the whole machine if a 256 byte/sector disk is inserted, its about as un-useful as can be here.
or all PATA? A different set of kernel and disk drivers could potentially reorder device assignments, making the order bootloader sees and the system sees differ. Booting using UUIDs or LABELs instead of device names is supposed to render any such differences of no import, but potential for confusion does remain, particularly from the perspective of an administrator's eyes.
Well, since I'm the one applying the disks partition labels, I trust them a lot farther than UUID's. I have had the simple replacemewnt of a failing disk change every UUID in the system, more than once.
Since stretch seems to have been OEL'd at most mirrors I guess I'll wait for Buster now.
Time to go change hats and play Chef.
Cheers, Gene Heskett
Gene Heskett composed on 2019-04-03 18:21 (UTC-0400):
It seems to me that this problem could be fixed once and for all by simply installing grub while the partition was only at the minimal install stage, I think by waiting till the end of the install, grub is too far into the disk for a dumb messydos bios to find. Thats my theory at least.
Valid theory when the BIOS is old and dumb enough.
With a new or wiped disk, order of things on MBR disks here is:
1-booted to live Knoppix, or with the disk in a different PC, partition completely 2-install generic MBR code 3-format all partitions intended for use by bootloader and initial OS installation 4-install and configure bootloader on primary partition below 504MB 5-begin first OS installation
For KISS leanings within the multiboot always environment here, the only bootloader I use on MBR systems without OS/2 on them is openSUSE's Grub Legacy with Gfxboot, which has adequate EXT4 support that Debian's last Grub Legacy versions lack. I suppose if it didn't work so well for me I might try something else, most likely rEFInd or syslinux. Grub2 is only used here for 2 PCs using UEFI mode.
I could hardly suggest the entirety of what I do for your single OS installation. Letting the Debian installer do with bootloader as it pleases should be quite sufficient once you've successfully navigated *manual* "partitioning", in which, since you've already partitioned and formatted, the only thing to do is select mount points and options. It's easy enough to select for formatting during this phase if you forgot to or chose not to format before beginning installation.
This selection process seems to be where people, including you, get flummoxed. When I first encountered it it did not seem intuitive or easy, but it really is logical, and easy enough. I looked for screenshots of these screens on debian.org just now and failed. I know I've seen some in the past, but apparently not in the Debian Handbook.
On Wednesday 03 April 2019 05:21:55 pm Gene Heskett wrote:
On Wednesday 03 April 2019 12:38:12 Felix Miata wrote:
Gene Heskett composed on 2019-04-03 08:16 (UTC-0400):
so maybe it might boot from usb stick after all, but
Hi All,
Okay I know about zero people on this list “need” this, as I’m sure we’re all familiar enough with dd, but I’m not adverse to getting some extra QC eyes to spot typo’s or bad copy/pastes ;) .
How to create a Bootable USB stick, with free space, from an ISO image http://inet-design.com/blogs/michael/how-create-bootable-usb-stick-iso-image...
Hopefully though, the ability to have free space for .bashrc, proprietary drivers, and whatnot on the USB after burning the ISO image will be useful to few of you.
Best, Michael
On Thursday 04 April 2019 07:33:18 Michael wrote:
On Wednesday 03 April 2019 05:21:55 pm Gene Heskett wrote:
On Wednesday 03 April 2019 12:38:12 Felix Miata wrote:
Gene Heskett composed on 2019-04-03 08:16 (UTC-0400):
so maybe it might boot from usb stick after all, but
Hi All,
Okay I know about zero people on this list “need” this, as I’m sure we’re all familiar enough with dd, but I’m not adverse to getting some extra QC eyes to spot typo’s or bad copy/pastes ;) .
How to create a Bootable USB stick, with free space, from an ISO image http://inet-design.com/blogs/michael/how-create-bootable-usb-stick-iso-imag e.html
Hopefully though, the ability to have free space for .bashrc, proprietary drivers, and whatnot on the USB after burning the ISO image will be useful to few of you.
Best, Michael
Already been there, done that, bought the T-shirt, about 2-3 years ago. I was booting a laptop from a 64 gb flash drive. I partitioned the flash drive with root, swap and home, and made it so that the laptop would not boot without it; which was interesting, but now it keeps looking for the flash drive that I don't want to use at present.
Anyway, an interesting experiment, to which I may yet return. My aim was to make a sort of portable mini-computer that I could take round in my pocket, and use it to boot up any computer (with permission, or one of my own). That way, I could always have a mini-clone of my running system, with everything available that I have here, and run it from any compatible computer, and have my system everywhere.
I did not, as some thought, merely make a bootable iso copy of an installation disc (using dd), but rather a complete working system, just with a smaller home partition, because I didn't want to keep anything there permanently.
Bill
P.S. I haven't got awake enough to get on the Internet yet and look at your page, but will do so after I make some coffee.
Michael wrote:
Okay I know about zero people on this list “need” this, as I’m sure we’re all familiar enough with dd, but I’m not adverse to getting some extra QC eyes to spot typo’s or bad copy/pastes ;) .
How to create a Bootable USB stick, with free space, from an ISO image
http://inet-design.com/blogs/michael/how-create-bootable-usb-stick-iso-image...
Hopefully though, the ability to have free space for .bashrc, proprietary drivers, and whatnot on the USB after burning the ISO image will be useful to few of you.
I personally use debootstrap. After debootstrap is done I chroot and do grub, fstab and so on. It takes like 15-30min. depends on how much customization is required.
If I would need iso from the usb, I recall there are tools to create the iso from a local directory, but never had to do this in the past 12+y.
The part where I failed last time, was trying to setup UEFI and after couple of tries and reads various docs I understood I have to have booted with UEFI in order to setup UEFI - like catch22.
regards
On Thursday 04 April 2019 20:03:09 deloptes wrote:
How to create a Bootable USB stick, with free space, from an ISO image :
unetbootin
Regards,
André
You have to be careful while I haven't had any issues with Debian and Unetbootin Rosa, Suse, and several others don't work well with this method.
On Thu, Apr 4, 2019 at 2:32 PM andre_debian@numericable.fr wrote:
On Thursday 04 April 2019 20:03:09 deloptes wrote:
How to create a Bootable USB stick, with free space, from an ISO image
:
unetbootin
Regards,
André
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thursday 04 April 2019 20:03:09 deloptes wrote:
How to create a Bootable USB stick, with free space, from an ISO image
On Thu, Apr 4, 2019 at 2:32 PM andre_debian@numericable.fr wrote:
unetbootin https://unetbootin.github.io/
On Thursday 04 April 2019 20:41:49 Pisini, John wrote:
You have to be careful while I haven't had any issues with Debian and Unetbootin Rosa, Suse, and several others don't work well with this method.
What happens, what do you mean by "don't work well" ?
André
They either don't boot or they boot but the installer fails usually after it has hosed the system.
On Thu, Apr 4, 2019 at 5:42 PM andre_debian@numericable.fr wrote:
On Thursday 04 April 2019 20:03:09 deloptes wrote:
How to create a Bootable USB stick, with free space, from an ISO
image
On Thu, Apr 4, 2019 at 2:32 PM andre_debian@numericable.fr wrote:
unetbootin https://unetbootin.github.io/
On Thursday 04 April 2019 20:41:49 Pisini, John wrote:
You have to be careful while I haven't had any issues with Debian and Unetbootin Rosa, Suse, and several others don't work well with this
method.
What happens, what do you mean by "don't work well" ?
André
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Friday 05 April 2019 07:24:51 Pisini, John wrote:
They either don't boot or they boot but the installer fails usually after it has hosed the system.
As you were nice enough not to point out the obvious, thats really helpfull NOT!
On Thu, Apr 4, 2019 at 5:42 PM andre_debian@numericable.fr wrote:
On Thursday 04 April 2019 20:03:09 deloptes wrote:
How to create a Bootable USB stick, with free space, from an ISO
image
On Thu, Apr 4, 2019 at 2:32 PM andre_debian@numericable.fr wrote:
unetbootin https://unetbootin.github.io/
On Thursday 04 April 2019 20:41:49 Pisini, John wrote:
You have to be careful while I haven't had any issues with Debian and Unetbootin Rosa, Suse, and several others don't work well with this
method.
What happens, what do you mean by "don't work well" ?
André
- To unsubscribe, e-mail:
trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
I would like to point out that was rude I was trying to help. I won't make that mistake again.
On Fri, Apr 5, 2019 at 7:46 AM Gene Heskett gheskett@shentel.net wrote:
On Friday 05 April 2019 07:24:51 Pisini, John wrote:
They either don't boot or they boot but the installer fails usually after it has hosed the system.
As you were nice enough not to point out the obvious, thats really helpfull NOT!
On Thu, Apr 4, 2019 at 5:42 PM andre_debian@numericable.fr wrote:
On Thursday 04 April 2019 20:03:09 deloptes wrote:
> How to create a Bootable USB stick, with free space, from an > ISO
image
On Thu, Apr 4, 2019 at 2:32 PM andre_debian@numericable.fr wrote:
unetbootin https://unetbootin.github.io/
On Thursday 04 April 2019 20:41:49 Pisini, John wrote:
You have to be careful while I haven't had any issues with Debian and Unetbootin Rosa, Suse, and several others don't work well with this
method.
What happens, what do you mean by "don't work well" ?
André
- To unsubscribe, e-mail:
trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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) Genes Web page http://geneslinuxbox.net:6309/gene
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Friday 05 April 2019 08:04:08 Pisini, John wrote:
I would like to point out that was rude I was trying to help. I won't make that mistake again.
I wasn't denigrating you John, I was just emphasising the hosed system part as not being helpfull. My apologies if you took that differently from what I intended to convey.
On Fri, Apr 5, 2019 at 7:46 AM Gene Heskett gheskett@shentel.net
wrote:
On Friday 05 April 2019 07:24:51 Pisini, John wrote:
They either don't boot or they boot but the installer fails usually after it has hosed the system.
As you were nice enough not to point out the obvious, thats really helpfull NOT!
On Thu, Apr 4, 2019 at 5:42 PM andre_debian@numericable.fr wrote:
On Thursday 04 April 2019 20:03:09 deloptes wrote: > > How to create a Bootable USB stick, with free space, > > from an ISO
image
On Thu, Apr 4, 2019 at 2:32 PM andre_debian@numericable.fr
wrote:
unetbootin https://unetbootin.github.io/
On Thursday 04 April 2019 20:41:49 Pisini, John wrote:
You have to be careful while I haven't had any issues with Debian and Unetbootin Rosa, Suse, and several others don't work well with this
method.
What happens, what do you mean by "don't work well" ?
André
---- - To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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) Genes Web page http://geneslinuxbox.net:6309/gene
- To unsubscribe, e-mail:
trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
On Friday 05 April 2019 05:04:08 Pisini, John wrote:
I would like to point out that was rude I was trying to help. I won't make that mistake again.
When we make jokes online, other people don't get to see our winks and nudges, or other cues, which tell us that we are supposed to laugh rather than take it as an insult.
Myself, I am obviously effin hilarious, but it doesn't always come through that way, and I am baffled when somebody imagines that I was trying to insult them. If I intend to insult somebody, I make sure that they know; I don't leave it open to interpretation.
So when somebody makes a joke, and others don't get it, let's just embrace the awkward weirdness and keep moving ahead. Assume the best of others; it works.
Gene is a great guy. Even the few people here who sometimes rub me the wrong way (there are only a couple, and it's not often) are better company than most of the "real" people that I meet when I leave my desk and venture forth into the outside world ... for example, when I go downstairs to get ice, or to check for mail.
We all ought to give one another enough space to speak without immediately taking offence.
Bill
On Fri, Apr 5, 2019 at 7:46 AM Gene Heskett gheskett@shentel.net wrote:
On Friday 05 April 2019 07:24:51 Pisini, John wrote:
They either don't boot or they boot but the installer fails usually after it has hosed the system.
As you were nice enough not to point out the obvious, thats really helpfull NOT!
On Thu, Apr 4, 2019 at 5:42 PM andre_debian@numericable.fr wrote:
On Thursday 04 April 2019 20:03:09 deloptes wrote: > > How to create a Bootable USB stick, with free space, from an > > ISO
image
On Thu, Apr 4, 2019 at 2:32 PM andre_debian@numericable.fr wrote:
unetbootin https://unetbootin.github.io/
On Thursday 04 April 2019 20:41:49 Pisini, John wrote:
You have to be careful while I haven't had any issues with Debian and Unetbootin Rosa, Suse, and several others don't work well with this
method.
What happens, what do you mean by "don't work well" ?
André
- To unsubscribe, e-mail:
trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
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) Genes Web page http://geneslinuxbox.net:6309/gene
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Thursday 04 April 2019 20:03:09 deloptes wrote:
How to create a Bootable USB stick, with free space, from an ISO
image
I may be jumping in late on this one.
What I've done in the past was disconnect the HD, boot off a DVD with the target USB stick inserted so it's the only "drive" on the machine, and install to it just like to a HD.
Plenty of extra space if the install took 2G on a 16G stick.
One could do the same thing, I expect, from a stick that's had the ISO dd'd to it as an install medium, to a blank USB stick or drive.
The Linux "everything is a block device" attitude works well in this regard.
Curt-
Gene Heskett composed on 2019-04-03 18:21 (UTC-0400):
Since stretch seems to have been OEL'd at most mirrors I guess I'll wait for Buster now.
Your brain is tired. Stretch is 9.x. Jessie is 8.x. Jessie would be the one leaving or having left the mirrors, the most recently obsoleted. Buster is 10.x, not yet "released".
On Thursday 04 April 2019 21:51:46 Felix Miata wrote:
Gene Heskett composed on 2019-04-03 18:21 (UTC-0400):
Since stretch seems to have been OEL'd at most mirrors I guess I'll wait for Buster now.
Your brain is tired. Stretch is 9.x. Jessie is 8.x. Jessie would be the one leaving or having left the mirrors, the most recently obsoleted. Buster is 10.x, not yet "released".
No, or maybe yes this time of the night, but I have the .jigdo files, and the .template files but the mirror has no files for me. It just times out but takes a long time per file. 30 minutes a file or more. I let it run for about 6 hours and only rx'd: 424941 Apr 3 17:55 debian-9.8.0-amd64-DVD-1.jigdo.unpacked
A half a megabyte in 6 hours? Somethings wrong someplace.
is there a master redirector that will find the stuff for jigdo?
I just tried it again: It chose a different site, but same story, its resolves, but is not there.
gene@coyote:~/LCNC-isos$ ping carroll.aset.psu.edu PING carroll.aset.psu.edu (128.118.2.96) 56(84) bytes of data. ^C --- carroll.aset.psu.edu ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 11086ms
Same as I got yesterday. Site needs brogan maintenance maybe?
Or the new version of net neutrality?
Cheers, Gene Heskett
Gene Heskett composed on 2019-04-04 22:24 (UTC-0400):
Felix Miata wrote:
Gene Heskett composed on 2019-04-03 18:21 (UTC-0400):
Since stretch seems to have been OEL'd at most mirrors I guess I'll wait for Buster now.
Your brain is tired. Stretch is 9.x. Jessie is 8.x. Jessie would be the one leaving or having left the mirrors, the most recently obsoleted. Buster is 10.x, not yet "released".
No, or maybe yes this time of the night, but I have the .jigdo files, and the .template files but the mirror has no files for me. It just times out but takes a long time per file. 30 minutes a file or more. I let it run for about 6 hours and only rx'd: 424941 Apr 3 17:55 debian-9.8.0-amd64-DVD-1.jigdo.unpacked
A half a megabyte in 6 hours? Somethings wrong someplace.
You betcha something's wrong: http://fm.no-ip.com/SS/debianMirror20190405.jpg
Same look at: http://debian.gtisc.gatech.edu/debian/dists/ http://mirror.us.leaseweb.net/debian/dists/ http://mirror.math.princeton.edu/pub/debian/dists/ http://mirrors.edge.kernel.org/debian/dists/ http://cdimage.debian.org/mirror/debian/dists/ http://ftp.debian.org/debian/dists/
is there a master redirector that will find the stuff for jigdo?
I just tried it again: It chose a different site, but same story, its resolves, but is not there.
gene@coyote:~/LCNC-isos$ ping carroll.aset.psu.edu PING carroll.aset.psu.edu (128.118.2.96) 56(84) bytes of data. ^C --- carroll.aset.psu.edu ping statistics --- 12 packets transmitted, 0 received, 100% packet loss, time 11086ms
carroll.aset.psu.edu appears to be absent from https://www.debian.org/mirror/list-full.en.html
Same as I got yesterday. Site needs brogan maintenance maybe?
Or the new version of net neutrality?
Too many ways to fail. :-( Jigdo methods I haven't tried.
On Wednesday 03 April 2019 03.50:15 Gene Heskett wrote:
On Tuesday 02 April 2019 18:36:14 Dan Youngquist wrote:
On 04/02/2019 01:10 PM, Gene Heskett wrote:
ATM, it goes straight to a gnome login asking me for my user pw. I didn't note if there was a session clicker or not. My mistake I expect.
I don't know about gdm, but tdm and lightdm both will auto-login to whatever desktop you last logged in to. To switch, logout, then select the session type at the display manager's login screen, and login.
Well, ATM I'm ready to shoot all the neighborhood cats. Something is shutting the stretch system off in about 5 minutes of mouse or keyboard inactivity, so I've had to recompose an install list and restart synaptic 5 or 6 times now.
Is this with Gnome? Yes, I've see that too. Get rid if Gnome
Then, to add insult to injury, the default system partition it sets up during the install for /, when you ask it for a separate /home, on a 2 terabyte drive is 30 GB.
(...)
I have never had ant great success at pre-partitioning a drive, the installer never accepts what you so carefully lay out with gparted,
From what you say I'd guess you're installing new. Then partitioning, then doing an "expert install" (I prefer the expert graphical install) should use your partitions (it takes some time to understand how to tell the installer where to install, but it works.
I do use a 30 GB home (I use 50GB for / and 15 - 30 GB for /home) as it makes backups faster and easier. I mount other partition on specific directories if necessary (for example on one machine .playonlinux is on a 200GB partition on another disc, I don't want to backup this everytime and I could live without the games). But this is you decision.
Thierry
On Wednesday 03 April 2019 01:20:51 Thierry de Coulon wrote:
On Wednesday 03 April 2019 03.50:15 Gene Heskett wrote:
On Tuesday 02 April 2019 18:36:14 Dan Youngquist wrote:
On 04/02/2019 01:10 PM, Gene Heskett wrote:
ATM, it goes straight to a gnome login asking me for my user pw. I didn't note if there was a session clicker or not. My mistake I expect.
I don't know about gdm, but tdm and lightdm both will auto-login to whatever desktop you last logged in to. To switch, logout, then select the session type at the display manager's login screen, and login.
Well, ATM I'm ready to shoot all the neighborhood cats. Something is shutting the stretch system off in about 5 minutes of mouse or keyboard inactivity, so I've had to recompose an install list and restart synaptic 5 or 6 times now.
Is this with Gnome? Yes, I've see that too. Get rid if Gnome
Not a lot of choices, xfce maybe.
Then, to add insult to injury, the default system partition it sets up during the install for /, when you ask it for a separate /home, on a 2 terabyte drive is 30 GB.
(...)
I have never had ant great success at pre-partitioning a drive, the installer never accepts what you so carefully lay out with gparted,
From what you say I'd guess you're installing new.
yes. I always install on a new drive, so my data is there, ready to copy over.
Then partitioning, then doing an "expert install" (I prefer the expert graphical install) should use your partitions (it takes some time to understand how to tell the installer where to install, but it works.
Tell me your secret incantations...
I do use a 30 GB home (I use 50GB for / and 15 - 30 GB for /home) as it makes backups faster and easier. I mount other partition on specific directories if necessary (for example on one machine .playonlinux is on a 200GB partition on another disc, I don't want to backup this everytime and I could live without the games). But this is you decision.
Generally I use ssh -Y for logins to the rest of my 8 machine network, and sshfs for file moving. I have a stanza in rc.local that mounts all that, or if need be a starter script that does them all. Those already mounted harmlessly error out, but if not mounted, it Just Works. One of them is a pi-3b, running 1400 lbs worth of a 70 yo Sheldon lathe. 3 more are intel boxes running similar cnc controlled machinery. This will be the first 64 bit install in the local system. I've put it off because LCNC doesn't run well with the 64 bits much longer IRQ latency's. Typically at least 4x longer on a 64 bit install. And lower priced setups using stepper motors cannot tolerate a late step, they'll stop and stall, making junk out of what could be a thousand dollar part. So the only thing this machine can do now is remotely monitor the others. Simulations are ok for writing code, but not much else.
Thierry
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett
Anno domini 2019 Tue, 2 Apr 14:11:04 -0400 Gene Heskett scripsit:
The install didn't switch it, and gnome won't show me the tools.
Yes, the gnomes won't let you go :-)
Help!
Cheers, Gene Heskett
On Wednesday 03 April 2019 03:09:11 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Tue, 2 Apr 14:11:04 -0400
Gene Heskett scripsit:
The install didn't switch it, and gnome won't show me the tools.
Yes, the gnomes won't let you go :-)
I think the installers only other choice is xfce, which I'll do this time. gnomes paranoia wears thin, very quickly. Even what they call a Konsole has been castrated. Thats unforgivable. I built this machine from scratch about a decade back, and I won't stand for their paranoia that just gets in the way of doing what I do with it. :(
Help!
Cheers, Gene Heskett
Cheers, Gene Heskett
Anno domini 2019 Wed, 3 Apr 08:48:05 -0400 Gene Heskett scripsit:
On Wednesday 03 April 2019 03:09:11 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Tue, 2 Apr 14:11:04 -0400
Gene Heskett scripsit:
The install didn't switch it, and gnome won't show me the tools.
Yes, the gnomes won't let you go :-)
I think the installers only other choice is xfce, which I'll do this time. gnomes paranoia wears thin, very quickly. Even what they call a Konsole has been castrated. Thats unforgivable. I built this machine from scratch about a decade back, and I won't stand for their paranoia that just gets in the way of doing what I do with it. :(
It's not paranoia, it's "making it easy". Guess, somebody is paying someone a lot of money for doing so.
Sorr, I missed a part of the original conversation. Which distribution are you going to install?
Nik
Help!
Cheers, Gene Heskett
Cheers, Gene Heskett
On Wednesday 03 April 2019 09:56:09 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Wed, 3 Apr 08:48:05 -0400
Gene Heskett scripsit:
On Wednesday 03 April 2019 03:09:11 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Tue, 2 Apr 14:11:04 -0400
Gene Heskett scripsit:
The install didn't switch it, and gnome won't show me the tools.
Yes, the gnomes won't let you go :-)
I think the installers only other choice is xfce, which I'll do this time. gnomes paranoia wears thin, very quickly. Even what they call a Konsole has been castrated. Thats unforgivable. I built this machine from scratch about a decade back, and I won't stand for their paranoia that just gets in the way of doing what I do with it. :(
It's not paranoia, it's "making it easy". Guess, somebody is paying someone a lot of money for doing so.
The hell its not being paranoid, Nik. Every time I get something working well, some paranoid sob plugs that hole in the next version as a security risk. Dammit, its my local network, all behind a dd-wrt router. In 15 years no one has come in from the outside tha I didn't invite and gave them the login credentials to do it with, no exceptions. So let me do as I please on my own local net.
I'll give you the ssh -Y remote cli login as a prime example. It wasn't user sensitive 10 years ago so a login Just Worked even if you've become root since logging in. Now we get "can't open display :10" errors unless you are first user all thru the systems, which I am not, there is no way on a raspian pi install to be other than pi as the first user #1000. BTDT spent weeks trying to work around that, finally gave up and just use ssh -Y pi@picnc.
So if I want to run synaptic on the pi, I either have to goto its keyboard, a back and neck killing standup job, or more recently I've found gksudo works. But login as pi, and simply "sudo synaptic" gets the display opening error. And even that doesn't work when I'm logged into a rock64 running stretch. Its MY local network, get the hell out of my way and let me see if I can actually get what s/b a pi killer, to do anything but browse the internet. I've built realtime kernels on that rock64 4 or 5 times now, but the instant I sudo -i to try to figure out how to install one of those realtime kernels, I'm blocked from doing almost anything but an ls -l. Its enough to make one clear out the stray cats in the neighborhood.
The point is, I build or buy this stuff for ME to use, whats wrong with that?
And despite going into this stretch netinstall with a well formatted drive ready for the install, the installer would NOT proceed past the partitioning AND formatting stage, so I was forced to do it again, losing the partition labels in the process.
Except I just ran blkid, and my labels survived!!!!!!! 'splain that one, but I like it! But mount -l can't find them... I had to use the /dev/sdb1 and sdb3 designators to mount them. Me, goes off scratching my thinning hair over that. Anyway, I've started copying stuff over, iuncludng the /opt directory. That oughtto be fun & games letting synaptic update all of the /opt/trinity directory to 64 bit stuff. :)
Thanks Nik, for reading my rant.
Sorr, I missed a part of the original conversation. Which distribution are you going to install?
Nik
Stretch, amd64 version. Just did but have not rebooted to it yet, thought I'd check the mail first.
Help!
Cheers, Gene Heskett
Cheers, Gene Heskett
Cheers, Gene Heskett
Hi Gene!
Anno domini 2019 Wed, 3 Apr 12:12:50 -0400 Gene Heskett scripsit:
On Wednesday 03 April 2019 09:56:09 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Wed, 3 Apr 08:48:05 -0400
Gene Heskett scripsit:
On Wednesday 03 April 2019 03:09:11 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Tue, 2 Apr 14:11:04 -0400
Gene Heskett scripsit:
The install didn't switch it, and gnome won't show me the tools.
Yes, the gnomes won't let you go :-)
I think the installers only other choice is xfce, which I'll do this time. gnomes paranoia wears thin, very quickly. Even what they call a Konsole has been castrated. Thats unforgivable. I built this machine from scratch about a decade back, and I won't stand for their paranoia that just gets in the way of doing what I do with it. :(
It's not paranoia, it's "making it easy". Guess, somebody is paying someone a lot of money for doing so.
The hell its not being paranoid, Nik. Every time I get something working well, some paranoid sob plugs that hole in the next version as a security risk. Dammit, its my local network, all behind a dd-wrt router. In 15 years no one has come in from the outside tha I didn't invite and gave them the login credentials to do it with, no exceptions. So let me do as I please on my own local net.
I'll give you the ssh -Y remote cli login as a prime example. It wasn't user sensitive 10 years ago so a login Just Worked even if you've become root since logging in. Now we get "can't open display :10" errors unless you are first user all thru the systems, which I am not, there is no way on a raspian pi install to be other than pi as the first user #1000. BTDT spent weeks trying to work around that, finally gave up and just use ssh -Y pi@picnc.
So if I want to run synaptic on the pi, I either have to goto its keyboard, a back and neck killing standup job, or more recently I've found gksudo works. But login as pi, and simply "sudo synaptic" gets the display opening error. And even that doesn't work when I'm logged into a rock64 running stretch. Its MY local network, get the hell out of my way and let me see if I can actually get what s/b a pi killer, to do anything but browse the internet. I've built realtime kernels on that rock64 4 or 5 times now, but the instant I sudo -i to try to figure out how to install one of those realtime kernels, I'm blocked from doing almost anything but an ls -l. Its enough to make one clear out the stray cats in the neighborhood.
The point is, I build or buy this stuff for ME to use, whats wrong with that?
And despite going into this stretch netinstall with a well formatted drive ready for the install, the installer would NOT proceed past the partitioning AND formatting stage, so I was forced to do it again, losing the partition labels in the process.
Except I just ran blkid, and my labels survived!!!!!!! 'splain that one, but I like it! But mount -l can't find them... I had to use the /dev/sdb1 and sdb3 designators to mount them. Me, goes off scratching my thinning hair over that. Anyway, I've started copying stuff over, iuncludng the /opt directory. That oughtto be fun & games letting synaptic update all of the /opt/trinity directory to 64 bit stuff. :)
Thanks Nik, for reading my rant.
Sorr, I missed a part of the original conversation. Which distribution are you going to install?
Nik
Stretch, amd64 version. Just did but have not rebooted to it yet, thought I'd check the mail first.
Ok ... thing one: don't use "sudo", use "su". "sudo" is like a choir of castrates: useless by default, unless you invest hords of time to set up things correctly and solve a problem that does not exist in the first place.
Second thing, IMO Debian bites you. All that workarounds to get systemd+gnome kindof working kill your "user experience". Note: if it works, you are fine, a bit slow when booting but you get shiny surface ... at least till it breaks, then the fun starts .. and break it will ..
(I already hear the bonfires roaring ..)
Nik
Help!
Cheers, Gene Heskett
Cheers, Gene Heskett
Cheers, Gene Heskett
On Thursday 04 April 2019 02:28:20 Dr. Nikolaus Klepp wrote:
Hi Gene!
Anno domini 2019 Wed, 3 Apr 12:12:50 -0400
Gene Heskett scripsit:
On Wednesday 03 April 2019 09:56:09 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Wed, 3 Apr 08:48:05 -0400
Gene Heskett scripsit:
On Wednesday 03 April 2019 03:09:11 Dr. Nikolaus Klepp wrote:
Anno domini 2019 Tue, 2 Apr 14:11:04 -0400
Gene Heskett scripsit:
The install didn't switch it, and gnome won't show me the tools.
Yes, the gnomes won't let you go :-)
I think the installers only other choice is xfce, which I'll do this time. gnomes paranoia wears thin, very quickly. Even what they call a Konsole has been castrated. Thats unforgivable. I built this machine from scratch about a decade back, and I won't stand for their paranoia that just gets in the way of doing what I do with it.
:(
It's not paranoia, it's "making it easy". Guess, somebody is paying someone a lot of money for doing so.
The hell its not being paranoid, Nik. Every time I get something working well, some paranoid sob plugs that hole in the next version as a security risk. Dammit, its my local network, all behind a dd-wrt router. In 15 years no one has come in from the outside tha I didn't invite and gave them the login credentials to do it with, no exceptions. So let me do as I please on my own local net.
I'll give you the ssh -Y remote cli login as a prime example. It wasn't user sensitive 10 years ago so a login Just Worked even if you've become root since logging in. Now we get "can't open display :10" errors unless you are first user all thru the systems, which I am not, there is no way on a raspian pi install to be other than pi as the first user #1000. BTDT spent weeks trying to work around that, finally gave up and just use ssh -Y pi@picnc.
So if I want to run synaptic on the pi, I either have to goto its keyboard, a back and neck killing standup job, or more recently I've found gksudo works. But login as pi, and simply "sudo synaptic" gets the display opening error. And even that doesn't work when I'm logged into a rock64 running stretch. Its MY local network, get the hell out of my way and let me see if I can actually get what s/b a pi killer, to do anything but browse the internet. I've built realtime kernels on that rock64 4 or 5 times now, but the instant I sudo -i to try to figure out how to install one of those realtime kernels, I'm blocked from doing almost anything but an ls -l. Its enough to make one clear out the stray cats in the neighborhood.
The point is, I build or buy this stuff for ME to use, whats wrong with that?
And despite going into this stretch netinstall with a well formatted drive ready for the install, the installer would NOT proceed past the partitioning AND formatting stage, so I was forced to do it again, losing the partition labels in the process.
Except I just ran blkid, and my labels survived!!!!!!! 'splain that one, but I like it! But mount -l can't find them... I had to use the /dev/sdb1 and sdb3 designators to mount them. Me, goes off scratching my thinning hair over that. Anyway, I've started copying stuff over, iuncludng the /opt directory. That oughtto be fun & games letting synaptic update all of the /opt/trinity directory to 64 bit stuff. :)
Thanks Nik, for reading my rant.
Sorr, I missed a part of the original conversation. Which distribution are you going to install?
Nik
Stretch, amd64 version. Just did but have not rebooted to it yet, thought I'd check the mail first.
And it won't boot, grub, by the time its installed, is too far into the drive, and this dumbassed bios can't find it. So I'got to rethink my partitioning scheme to add a 250 meg /boot up front...
Ok ... thing one: don't use "sudo", use "su". "sudo" is like a choir of castrates: useless by default, unless you invest hords of time to set up things correctly and solve a problem that does not exist in the first place.
Second thing, IMO Debian bites you. All that workarounds to get systemd+gnome kindof working kill your "user experience". Note: if it works, you are fine, a bit slow when booting but you get shiny surface ... at least till it breaks, then the fun starts .. and break it will ..
(I already hear the bonfires roaring ..)
And the chain saws snarling as they cut some more to feed the flames. Wheezy's paranoia was something you could work around most of the time without too much trouble until xhost got castrated. A good distribution. Jessie was a taste of whats to come. Stretch makes it worse. But we're gonna have to live with buster for a while, so we may as well figure out how to make it work, and sooner is better bause you get to run it longer. Actually. jessie on the pi wasn't too bad. I am actually getting things done with it. But info on the wintel stuff is common knowledge. Want to replace the armhf (pi) or arm64 (rock64) kernel with a realtime version? Nobody else sees the need, so your questions get ignored, not answered by the people who do have it all figured out. Thats BS.
And its why I'm back to an intel machine for my current build. The atom boards can run a 32 bit kernel with IRQ latencies in the 3 to 5 microsecond range, so simple machines can be run directly from the parport. Need more i/o than the 5 inputs that gives? Mesa has several boards for under a $100 bill for that, including SPI interfaced that run at 41 megabaud on the pi. Unforch its a 3.3 volt board, easily damaged by noise, so it needs 7i42TA buffer boards, 1 for each group of 24 lines, so by the time you've a full 72 line interface, you're at about $200. But you are also looking at bringing a wire to it, insert in hole and tighten the screw, so wiring it up is a piece of cake. Then on this latest build, I chose a $120 7i76 board, driven by an $80 5i25, gives me 5 axises worth of stepper controls, an isolated vfd spindle control, 32 inputs for machine status, and 16 more outputs to run pumps and such with. And thosee fpga boards take care of the high speed timings so it all runs on a 1 millisecond main IRQ loop. Power to throw away on a dual core atom. Plenty of time left to drive your eye candy which I am not allergic to writing. That also explains why those nearly decade old atom boards sell on ebay for more that they sold for new. Intel accidently made us machine tool people an ideal board.
But I'd better shaddup go see what the missus wants for breakfast.
Take care Nik.
Cheers, Gene Heskett
On Thursday 04 April 2019 07:01:11 am Gene Heskett wrote:
And it won't boot, grub, by the time its installed, is too far into the drive, and this dumbassed bios can't find it. So I'got to rethink my partitioning scheme to add a 250 meg /boot up front...
Here's my dumb bios partitions:
michael@local [/media/michael]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 243M 0 part /boot ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 465.5G 0 part └─sda5_crypt (dm-0) 252:0 0 465.5G 0 crypt ├─ubuntu--vg-root (dm-1) 252:1 0 461.5G 0 lvm / └─ubuntu--vg-swap_1 (dm-2) 252:2 0 4G 0 lvm [SWAP]
Hope that helps?? And that email doesn't eat it beyond readability...
Ok ... thing one: don't use "sudo", use "su". "sudo" is like a choir
In a sudo choked distribution you can use 'sudo -i' to open a root prompt.
{snip}
with. And thosee fpga boards take care of the high speed timings so it all runs on a 1 millisecond main IRQ loop. Power to throw away on a dual core atom. Plenty of time left to drive your eye candy which I am not allergic to writing. That also explains why those nearly decade old atom boards sell on ebay for more that they sold for new. Intel accidently made us machine tool people an ideal board.
But I'd better shaddup go see what the missus wants for breakfast.
Hi Gene,
I know most of what you write has no real relation to TDE, but please don't stop :) I for one find it fascinating and informative, especially since it all seems transferable and translatable to home automation control systems, of which I will be tinkering with in a few months.
Best, Michael
On Thu, 4 Apr 2019 08:01:11 -0400 Gene Heskett gheskett@shentel.net wrote:
Actually. jessie on the pi wasn't too bad. I am actually getting things done with it. But info on the wintel stuff is common knowledge. Want to replace the armhf (pi) or arm64 (rock64) kernel with a realtime version? Nobody else sees the need, so your questions get ignored, not answered by the people who do have it all figured out. Thats BS.
For the pi, shouldn't it just be a matter of following your distro's build-your- own-kernel instructions, using the pi-specific kernel sources and base config, and applying the rt patchset on top? Or does the patchset not apply cleanly or something? (Assuming you're building directly on the pi. If not, start with cross-compiler or qemu arm emulation setup, also per your distro. I went the qemu route.)
E. Liddell
On Thursday 04 April 2019 17:16:04 E. Liddell wrote:
On Thu, 4 Apr 2019 08:01:11 -0400
Gene Heskett gheskett@shentel.net wrote:
Actually. jessie on the pi wasn't too bad. I am actually getting things done with it. But info on the wintel stuff is common knowledge. Want to replace the armhf (pi) or arm64 (rock64) kernel with a realtime version? Nobody else sees the need, so your questions get ignored, not answered by the people who do have it all figured out. Thats BS.
For the pi, shouldn't it just be a matter of following your distro's build-your- own-kernel instructions, using the pi-specific kernel sources and base config, and applying the rt patchset on top?
No clue, I built it for the rock64, on the rock64, useing the patches from the linux-rt mailing list links, but when I asked how to install it, 3 times over about as many weeks, and got ignored, I gave up. Their propaganda says good support, but AFAIWC, there isn't any. But the pi is only very marginally better. Bulding an rt kernel on the pi is a several hour project, on the rock64 its about 30 minutes, which amply demo's the difference in speeds. Too bad I cannot use it. Neither has any docs available to aid the hacker. Those are proprietary designs. Run the linux they supply, or go pound sand.
Or does the patchset not apply cleanly or something? (Assuming you're building directly on the pi. If not, start with cross-compiler or qemu arm emulation setup, also per your distro. I went the qemu route.)
E. Liddell
Take care now, E. Liddell.
Cheers, Gene Heskett
Gene Heskett wrote:
No clue, I built it for the rock64, on the rock64, useing the patches from the linux-rt mailing list links, but when I asked how to install it, 3 times over about as many weeks, and got ignored, I gave up. Their propaganda says good support, but AFAIWC, there isn't any. But the pi is only very marginally better. Bulding an rt kernel on the pi is a several hour project, on the rock64 its about 30 minutes, which amply demo's the difference in speeds. Too bad I cannot use it. Neither has any docs available to aid the hacker. Those are proprietary designs. Run the linux they supply, or go pound sand.
Which one the rock64 or the PI ... I got already confused. For the PI there are very good descriptions of the boot process and what you need to have on the SD card ... I need to find the links I used. Also not necessary to build directly on the PI, but you can cross compile .... well might be easier for you to build directly on the PI.
regards
On Thursday 04 April 2019 19:03:46 deloptes wrote:
Gene Heskett wrote:
No clue, I built it for the rock64, on the rock64, useing the patches from the linux-rt mailing list links, but when I asked how to install it, 3 times over about as many weeks, and got ignored, I gave up. Their propaganda says good support, but AFAIWC, there isn't any. But the pi is only very marginally better. Bulding an rt kernel on the pi is a several hour project, on the rock64 its about 30 minutes, which amply demo's the difference in speeds. Too bad I cannot use it. Neither has any docs available to aid the hacker. Those are proprietary designs. Run the linux they supply, or go pound sand.
Which one the rock64 or the PI ... I got already confused.
Both. I wanted a comparison of build times, both done on the same usb2 interfaced SSD. I built it 4.something at the time, on the rock64, for arm64 then did a make clean, took the drive to the pi and changed the architecture to armhf, and built it on the pi.
For the PI there are very good descriptions of the boot process and what you need to have on the SD card ... I need to find the links I used. Also not necessary to build directly on the PI, but you can cross compile .... well might be easier for you to build directly on the PI.
regards
Cheers, Gene Heskett
Gene Heskett wrote:
On Thursday 04 April 2019 19:03:46 deloptes wrote:
Gene Heskett wrote:
No clue, I built it for the rock64, on the rock64, useing the patches from the linux-rt mailing list links, but when I asked how to install it, 3 times over about as many weeks, and got ignored, I gave up. Their propaganda says good support, but AFAIWC, there isn't any. But the pi is only very marginally better. Bulding an rt kernel on the pi is a several hour project, on the rock64 its about 30 minutes, which amply demo's the difference in speeds. Too bad I cannot use it. Neither has any docs available to aid the hacker. Those are proprietary designs. Run the linux they supply, or go pound sand.
Which one the rock64 or the PI ... I got already confused.
Both. I wanted a comparison of build times, both done on the same usb2 interfaced SSD. I built it 4.something at the time, on the rock64, for arm64 then did a make clean, took the drive to the pi and changed the architecture to armhf, and built it on the pi.
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/
On Thu, 4 Apr 2019 17:38:15 -0400 Gene Heskett gheskett@shentel.net wrote:
On Thursday 04 April 2019 17:16:04 E. Liddell wrote:
On Thu, 4 Apr 2019 08:01:11 -0400
Gene Heskett gheskett@shentel.net wrote:
Actually. jessie on the pi wasn't too bad. I am actually getting things done with it. But info on the wintel stuff is common knowledge. Want to replace the armhf (pi) or arm64 (rock64) kernel with a realtime version? Nobody else sees the need, so your questions get ignored, not answered by the people who do have it all figured out. Thats BS.
For the pi, shouldn't it just be a matter of following your distro's build-your- own-kernel instructions, using the pi-specific kernel sources and base config, and applying the rt patchset on top?
No clue, I built it for the rock64, on the rock64, useing the patches from the linux-rt mailing list links, but when I asked how to install it, 3 times over about as many weeks, and got ignored, I gave up. Their propaganda says good support, but AFAIWC, there isn't any. But the pi is only very marginally better. Bulding an rt kernel on the pi is a several hour project, on the rock64 its about 30 minutes, which amply demo's the difference in speeds. Too bad I cannot use it. Neither has any docs available to aid the hacker. Those are proprietary designs. Run the linux they supply, or go pound sand.
The pi is quite well-documented, except for the internals of a couple of hardware blobs. The rock64 . . . a quick search suggests much less documentation is available, and the detailed tech-spec stuff seems to be in Chinese, which is no help. Scour /boot for the existing kernel, that's all I can advise--it should be in there somewhere.
If you're still interested in setting up the pi, it expects to find the kernel with a fixed filename in the boot partition. It also needs some auxiliary files in there.
Here's what the boot section of the Gentoo image I assembled for my pi3 looks like:
ryu ~ # ls -l /mnt/data/armchroot/boot/ total 16376 -rw-r--r-- 1 root root 15992 Dec 6 19:22 bcm2710-rpi-3-b.dtb -rw-r--r-- 1 root root 50268 Dec 6 19:22 bootcode.bin -rw-r--r-- 1 root root 48 Dec 6 20:42 cmdline.txt -rw-r--r-- 1 root root 2527 Dec 6 19:22 fixup_cd.dat -rw-r--r-- 1 root root 6635 Dec 6 19:22 fixup.dat -rw-r--r-- 1 root root 9770 Dec 6 19:22 fixup_db.dat -rw-r--r-- 1 root root 9768 Dec 6 19:22 fixup_x.dat -rw-r--r-- 1 root root 4233216 Dec 6 19:09 kernel7.img drwxr-xr-x 2 root root 4096 Dec 6 19:22 overlays -rw-r--r-- 1 root root 641252 Dec 6 19:22 start_cd.elf -rw-r--r-- 1 root root 4974116 Dec 6 19:22 start_db.elf -rw-r--r-- 1 root root 2840612 Dec 6 19:22 start.elf -rw-r--r-- 1 root root 3923364 Dec 6 19:22 start_x.elf
The kernel is kernel7.img (older pis may expect kernel.img instead). The rest of the files are the pi's firmware packet, from github.
E. Liddell
Gene Heskett composed on 2019-04-03 08:48 (UTC-0400):
I think the installers only other choice is xfce
You think wrong. Neither Gnome nor XFCE ever gets installed on any Debian here. Whether Debian or any Debian derivative on which I want TDE, I include the following on the installation kernel's cmdline:
tasks=standard base-installer/install-recommends=false
This produces a minimal installation, from which I add TDE to sources.list, so that the only desktop becomes TDE after following the TDE Wiki instructions.
Typically before I add TDE I install the very light weight IceWM, to ensure I have a working X, and something to fall back to, if TDE or its repos seem to be broken.
-
andre_debian＠numericable.fr -
Curt Howland -
Dan Youngquist -
deloptes -
Dr. Nikolaus Klepp -
E. Liddell -
Felix Miata -
Gene Heskett -
Michael -
Pisini, John -
Thierry de Coulon -
William Morder