Vectorlinux 7.2 RC2 is released. More testing requested.

[mtbvfr]

I should have mentioned that Secure Boot is disabled.

[nightflier]

No.. unetbootin does not look like an option, don't see anything about EFI on the USB stick.

[mtbvfr]

don't see anything about EFI on the USB stick.

Not sure what you are trying to indicate with this comment.

The 2 images I posted are for Void and Vector on the same USB Flash Drive.

[nightflier]

The image showing Void linux has a "grub_uefi" part.
I assume your computer will only boot uefi images.
VL iso is not configured for uefi boot.
Unetbootin did not configure the USB stick for uefi boot, I did not pursue it any further than that.

Unfortunately, I'm out of ideas, sorry.

[mtbvfr]

VL iso is not configured for uefi boot.

UEFI has been around for at least 5 years.

Why is the VL iso not configured for UEFI?

[Doug Brunelle]

One suggestion I have for the installation process- on this old emachines M6809 notebook, I had three partitions- Windows XP, Lubuntu 17.04, and Vector Linux LIGHT 7.1, and unallocated space of about 15GB for installation of VL 7.2 x64 RC2. 

I started the installation, and chose 'automatic' for the disk & partition selection, thinking that it would figure out that three partitions are in use, and there's unallocated space, so it will use the unallocated space by default, right?  But NOooooooo..!  the VL install wiped out all the other partitions and created one partition for the OS, much as you'd expect Windows to do. 

Now, it's no big deal- I didn't have anything important in those other partitions.  I just think that the installer, when evaluating the existing partitions, should use the unallocated space for the current install and leave existing partitions alone; in other words, the user might not be aware that an 'automatic' installation will destroy his existing partitions.  To me, the OS install should DO THE LEAST DESTRUCTIVE THING BY DEFAULT.  Or at least warn the user just before partitioning that the option he chose will wipe out all partitions on the disk for the current install.

--Doug

[nightflier]

Doug, good feedback. Thank you. Will pass that on to the devs responsible for the installer.

[overthere]

Is this mainly for running the XFCE desktop as root, or does it affect a regular user?

The faenza-cupertino icons are missing from the folder in /usr/share/icons but the theme and folders remain

thus if a user selects faenza-cupertino from settings/appearance/icons nothing changes as the icons are missing. the blue folder icons are or have been a Vector standard.

rather than include them in following iso, the option was changed to faenza dark as default but the option remains.

simply adding the icons to the folder solves the issue. however if it is the desire of Vector to revert to classic brown folders after many years of matching Vector blue, then the option should be removed as it is an option that does not work due to the missing icon set.

this affects the user and likely root as well

[nightflier]

Got it, overthere, thanks!

[overthere]

If thunar is opened as user you can see a devices list ie optical drive additional partitions and usb drives when plugged in and mount and unmount at will.

In terminal su to root and open thunar no devices are listed at all. thus root user has no access to devices in file manager.

E.this may be by design and I am thinking of another system. if so oops

[overthere]

How is this supposed to be installed to a USB Flash Drive so that you can boot from it before attempting an install to a Hard Drive? Is that what you should be able to do?

No, this is not a live media, it is an install media. on newer computers it will require secure boot to be disabled and legacy mode selected as I understand it

alternatively you may install to a virtual box.

[nightflier]

If thunar is opened as user you can see a devices list ie optical drive additional partitions and usb drives when plugged in and mount and unmount at will.

In terminal su to root and open thunar no devices are listed at all. thus root user has no access to devices in file manager.

E.this may be by design and I am thinking of another system. if so oops

Got the word - "that's just the way it is". 

[overthere]

Thanks, understood, and always a light if that is a tunnel for anyone

[Dark Rider]

I'm Back after a few years. Looking forward to trying 7.2. Glad to see you guys are still here, glad to see I remembered my login and password. Ha!

[retired1af]

No bueno on the install to my desktop. Doesn't even get to the installer. ISO fires up and ends up at a completely locked text screen as root.

Going to download the ISO again and give it another shot just in case it was a borked download.

Edit -

Nope. Still won't install. And I can't use the previous beta either that's already installed on the drive.

The drive was transferred from my notebook to a new desktop rig. UEFI is active which I suspect is the cause of the issue.

System info:

Machine:   Mobo: ASRock model: H110M-DGS R3.0 Bios: American Megatrends v: P1.20 date: 05/10/2017
CPU:       Quad core Intel Core i7-6700 (-HT-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 27264
           clock speeds: min/max: 800/4000 MHz 1: 799 MHz 2: 799 MHz 3: 799 MHz 4: 799 MHz 5: 963 MHz
           6: 799 MHz 7: 1161 MHz 8: 799 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Device 67df bus-ID: 01:00.0 chip-ID: 1002:67df
           Display Server: X.Org 1.18.4 drivers: ati,amdgpu (unloaded: fbdev,vesa,radeon)
           Resolution: 1920x1080@60.00hz
           GLX Renderer: AMD Radeon RX 480 Graphics
           GLX Version: 4.5.13474 - CPC 17.10.2 Direct Rendering: Yes
Audio:     Card-1 Advanced Micro Devices [AMD/ATI] Device aaf0
           driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 1002:aaf0
           Card-2 Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:a170
           Sound: Advanced Linux Sound Architecture v: k4.8.0-58-generic
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168
           IF: enp3s0 state: down mac: <filter>
Drives:    HDD Total Size: 1750.4GB (4.0% used)
           ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB serial: 37C6XNHNS
ID-2: /dev/sdb model: WDC_WD7500BPKT size: 750.2GB serial: WD-WXS1E62NHXK4