Forum Home
Press F1
Thread ID: 147647	2019-02-18 01:44:00	And Now ---> Back On The Mint Side Of My 'Puter........	SurferJoe46 (51)	Press F1

Post ID	Timestamp	Content	User
1458401	2019-02-20 20:14:00	Just last night I plugged what I thought was a blank SSD into a new (to me) system and it booted into windows 10 (oops). It had an install from an i5 3470 on it and booted up with an AMD E350 - very different hardware :) so yes windows 10 is much better than previous versions at migrating onto different hardware. Still better to start over though. I've used MINT XFCE a few times now and rather like it for the low resource requirements, on the aforementioned E350 for example it runs quite well and that's a 15W dual core AMD competitor to Atom CPUs. On windows 10 the CPU was sitting @ 100% just running the malware service for 10 minutes until I gave up on it, on a fresh XFCE install it idles around 7% CPU. To be fair windows would eventually have settled down but I was just experimenting with some new hardware destined to be a NAS running open-e dss or OMV so I wasn't going to wait. From my understanding anything based on Ubuntu should be able to share the same packages, I install them on MINT often enough. I leave more helpful stuff to others thugh, I barely scratch the surface with my linux knowledge.	dugimodo (138)
1458402	2019-02-21 02:58:00	On re-reading your post I may have misunderstood your question here. If you mean "can you add these repositories to your Linux Lite install?" ... the answer is yes. Because both Mint and Lite are based on Debian/Ubuntu it should be possible. Not really -- good try though! I was wondering if I left the HDD alone and just ran another Ubuntu distro, could those two troublemakers cross over and mess with my newest installation. Having typed that question --- now it looks like a dumb thought and I am quite sure that it is locked into the distro where it resides and can't jump fences. I'm really liking LITE and may want to stay with it, although Ubuntu is also on this hdd. Dumb question for the next 24 hours----> Can just ONE distro be removed from a multi-boot hdd? One big thing I am having to overcome is teaching LITE all my passwords.	SurferJoe46 (51)
1458403	2019-02-21 03:30:00	I think you can just boot to another distro and carefully delete the partitions of the one you want to remove and then edit grub to remove the entry. But how you go about Identifying which partitions I don't know. I never boot more than 2 OSes and one is always windows so I haven't played with grub much. I like to install linux, create some empty unpartitioned space, install windows, then edit the windows boot menu to point at linux as a second option. That way windows updates don't mess with grub, and Linux is easily removed later without upsetting windows, and I also just like the windows menu better.	dugimodo (138)
1458404	2019-02-21 03:49:00	But how you go about Identifying which partitions I don't know. To help with identification it's best to use labels on the partitions. So, you boot a live Linux distro, run either Gparted or KDE Partition Manager, figure out from there which partition is which and from the partition properties dialog you can create/change the label. Then, when you want to remove an installed Linux just run Gparted again from a Live boot and delete the partition with the label on it. You don't need to edit Grub these days ... just execute sudo update-grub and Grub will see that the install has been removed and it will disappear from the boot menu.	Rod J (451)
1458405	2019-02-21 03:53:00	Uh huh --- IDENTIFYING partitions is gonna be the killer. I shouldda paid more attention to the names of the partitions as I installed the new distros. The learning curve is almost vertical sometimes.	SurferJoe46 (51)
1458406	2019-02-22 04:03:00	Probably the easiest way to identify and label partitions in Linux is to install the gui program "gnome-disk-utility". In the Start menu it is identified as "Disks". It's pretty much the Linux equivalent of the Windows Disk Management tool. It may already be installed in Mint (but probably not). When run it shows the partitions for each drive. You can see what the system identifies the partition as (/dev/sd* and the UUID of the partition, etc). You can change the Label of a partition by first clicking on the partition in question and then clicking on the button just below the partition list called "Additional Partition Options" and choosing "Edit filesystem". That pops up a little dialog enabling you to create/change the filesystem label. Easy peasy! A word of warning though: be careful what you do with this powerful tool ... you could really mess things up if you're not careful!	Rod J (451)
1458407	2019-02-22 06:29:00	I like what you said . I Google'd and found that many Ubuntu sites recommend using GParted, which I already have as an . iso in my Firefox Download Manager from burning a couple of iso's this afternoon for a friend . Here's the problem - ain't there ALWAYS a problem? After following the commands to perfection, I got the following . . . . . . . . . . . . . . Welcome to Linux Lite 4 . 2 linuxlite Thursday 21 February 2019, 21:49:40 Memory Usage: 1279/1983MB (64 . 50%) Disk Usage: 15/56GB (29%) Support - . linuxliteos . com/forums/" target="_blank">www . linuxliteos . com (Right click, Open Link) linuxlite  ~  lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465 . 8G 0 disk ├─sda1 8:1 0 245 . 6G 0 part /media/linuxlite/ff049e57-c8bd-480b-920b-0f574b ├─sda2 8:2 0 1K 0 part ├─sda5 8:5 0 2G 0 part ├─sda6 8:6 0 56 . 5G 0 part / └─sda7 8:7 0 161 . 7G 0 part /media/linuxlite/ea5fc8a9-dd89-47d6-9334-179293 sdb 8:16 1 952 . 5M 0 disk └─sdb1 8:17 1 952 . 4M 0 part /media/linuxlite/KODAK sdc 8:32 1 1 . 9G 0 disk └─sdc1 8:33 1 1 . 9G 0 part /media/linuxlite/2 GIG SAVE sr0 11:0 1 2K 0 rom linuxlite  ~  sudo parted /dev/sdb1 [sudo] password for linuxlite: Using /dev/sdb1 NOTE: the SD card (^) is called: sdb * sdb1/media/linuxlite/KODAK So-o-o working on the SD called KODAK . . . . . . . . I got no results b/o the SD being MOUNTED . I Google'd how to format via The Terminal, and I found there's so many convoluted command line entries in Linux Terminal to format, unmount and remount an SD card --- that I just pulled the SD outta my card reader and had a giant brain epiphany . . . . . . . . . . . . . . . . I stuck the SD in my Kodak camera and formatted it from there . Then I stuck it back in my card reader on my Linux Lite machine . Again, in the terminal, I tried the lsblk G-Parted command, and got that I had inserted a mounted SD card and GParted can only work with UNmounted volumes . So-o-o next I went to the desktop icon for the SD Card and right-clocked the KODAK SD and clicked on UNMOUNT . Then I re-s stuck the SD in the reader and going back to the terminal again I ran lsblk and now I got this: Welcome to Linux Lite 4 . 2 linuxlite Thursday 21 February 2019, 22:43:56 Memory Usage: 1266/1983MB (63 . 84%) Disk Usage: 15/56GB (29%) Support - . linuxliteos . com/forums/" target="_blank">www . linuxliteos . com (Right click, Open Link) linuxlite  ~  lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465 . 8G 0 disk ├─sda1 8:1 0 245 . 6G 0 part /media/linuxlite/ff049e57-c8bd-480b-920b-0f574b ├─sda2 8:2 0 1K 0 part ├─sda5 8:5 0 2G 0 part ├─sda6 8:6 0 56 . 5G 0 part / └─sda7 8:7 0 161 . 7G 0 part /media/linuxlite/ea5fc8a9-dd89-47d6-9334-179293 sdb 8:16 1 1 . 9G 0 disk └─sdb1 8:17 1 1 . 9G 0 part /media/linuxlite/KODAK sr0 11:0 1 2K 0 rom linuxlite  ~  sudo mkfs . vfat /dev/sdb1 [sudo] password for linuxlite: mkfs . fat 4 . 1 (2017-01-24) mkfs . vfat: /dev/sdb1 contains a mounted filesystem . linuxlite  ~  sudo mkfs . vfat /dev/sdb1 mkfs . fat 4 . 1 (2017-01-24) linuxlite  ~  lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465 . 8G 0 disk ├─sda1 8:1 0 245 . 6G 0 part /media/linuxlite/ff049e57-c8bd-480b-920b-0f574b ├─sda2 8:2 0 1K 0 part ├─sda5 8:5 0 2G 0 part ├─sda6 8:6 0 56 . 5G 0 part / └─sda7 8:7 0 161 . 7G 0 part /media/linuxlite/ea5fc8a9-dd89-47d6-9334-179293 sdb 8:16 1 1 . 9G 0 disk └─sdb1 8:17 1 1 . 9G 0 part sr0 11:0 1 2K 0 rom linuxlite  ~  Notice that I left the results posted for you to see/read where I screwed up and got told I had to UNmount the SD first . mkfs . vfat: /dev/sdb1 contains a mounted filesystem . linuxlite  ~  sudo mkfs . vfat /dev/sdb1 The partition sdb1 is now empty . sdb 8:16 1 1 . 9G 0 disk └─sdb1 8:17 1 1 . 9G 0 part Next - I want to put an . iso file on it now . . . . and once I can get my burner to recognize the SD - I think i've learned some new tricks . When does it end --- learning tricks, that is?	SurferJoe46 (51)
1458408	2019-02-22 06:38:00	You don’t need to boot the live disto to run gparted, it’s just an app that you can install and run in any distro (from your package manager). Or just use whatever ‘disk tool’ mint supplies. The live version that your ISO is can be handy for moving/resizing/deleting partitions that would normally be mounted if running from the installed system, but that’s not necessary for your simple naming operation.	fred_fish (15241)
1458409	2019-02-22 06:40:00	You don’t need to boot the live disto to run gparted, it’s just an app that you can install and run in any distro (from your package manager). Or just use whatever ‘disk tool’ mint supplies. The live version that your ISO is can be handy for moving/resizing/deleting partitions that would normally be mounted if running from the installed system, but that’s not necessary for your simple naming operation. I just thought I'd keep it as LIVE since I've already got it and I can burn it to DVDs for other people. Now I've gotta put Ubuntu 18.1 on the SD Card and I'm gonna try to hammer that out.	SurferJoe46 (51)
1 2 3