I don't have anything new there. Was it something you already sent that I have missed?

Anybody seen or heard from dizzie lately?

Quote from: dizzie on April 22, 2024, 06:22:08 AMShould be approx 10x faster now also 

Going to fast.com gives me 970, so we're good, will set up a user for you later, but I'm getting hammered by bots on port 22, so I'll change that to something stupid like 22960 or whatever

Bots are so stupid and annoying

And, you're welcome!

Trying to get in today to upload the new FSA's but I am having no luck connecting I am guessing it is because of no user or new port. I tried 22960 and it failed too

Quote from: dizzie on April 21, 2024, 09:47:06 AMDownload mirror is online again

Thank you dizzie!

Thank you dizzie! It is really appreciated!

Quote from: DeepDayze on April 18, 2024, 01:41:59 PMBummer. Fsarchiver as a backup/restore tool for BTRFS then is no bueno. There should be some sort of override so that you can restore a BTRFS .fsa with its original UUID.

It's really a security feature to make sure that you don't have multiple instances of the same UUID booting.. IMO, the ext4 part should do the same but does now.

You could try this format above using the uuid you want to see if it would work, I never tried to restore with the exact same uuid, it may be possible. I'll test this as well

There are 3 things IMO that should always be done and we detail them in the How To on the FSArchive page specifically with the following steps of 8 and 9

These things should be done once you boot and are logged into the new install the first time

8: Create your own user and /home

sudo adduser yourusername
9: Give sudo rights to your new user

sudo usermod -aG sudo yourusername
and the 3rd and equally most critical thing is to change the root PW to what you want it to be by doing this as root, so you might want to do this first.

passwd root
As RatMan pointed out, you definitely don't want to run a system as root.. as seasoned as some of us are here (RatMan, Jedi, Luke, dizzie and myself) we would never run as root all the time

In most of the layouts I have created for GMusicBrowser I have the double click option set to insert the desired track at the top of the queue instead of directly playing it. Jedi has asked on the IRC how to change that to option to play  it directly so I am going to detail it here

In whatever layout file you are using and in your favorite editor, find every instance of activate=queueinsert and replace it with PlayItem

Save the file and restart GmusicBrowser and you are set

I have also attached the edited file that Jedi needs

Relaxed. A little Carly and a little Ripley


 

Quote from: Gordon on April 06, 2024, 01:19:37 PMHi VastOne

having real problem trying to get to root VSIDO, no matter how I type VSIDO in for the password or if I use my own password it won't let me onto root vsido all i get is authentication failure. how i got onto root before is a mystery, must have been pure luck

cheers Gordon
 

vsido should be roots pw on any new install including the fsarchive. Of course it is always recommended changing that

Quote from: Gordon on April 04, 2024, 01:45:59 PMHi VastOne

if I log in as myself in root terminal and run smxi I get an error ( 8 ) message.
if I login in on VSIDO and cd / it changes to vsido@vsido:/$ and then use smxi I get an error ( 2 ) message. if I run terminal in vsido I get

Code Select Expand

vsido@vsido:~$ su
Password:
root@vsido:/home/vsido# smxi



if I reboot I'll end up in the same place

Cheers Gordon

As soon as you reboot and before you login, do your ctrl alt f1 to your tty1 and then run it as root (just like you did above as su)..that is how it must be done

Several things Gordon... Will you please post what exact command you are using from terminal to get the root error?

1: You cannot sudo as root, there is no need to
2: the 'up' command is an alias and has sudo as part of it. root does not have built in aliases as the normal users do and again, root does not need sudo
3: As you found out, smxi is not a debian package and you must install it from the smxi website and per their instructions
4: From a terminal or your tty1 or tty2, type in su and hit enter and then enter your password. Then follow those instructions from the website.

Quote from: Gordon on March 30, 2024, 10:44:47 AMHi Folks,
Me again, i'm having trouble with my screen resolution. I usually use smxi to do this as i have an old graphics card and it installs a nvidia driver. I have tried to use tty1 and tty2 but it says it's controlled by V-Ger and i can't get it to root to use it. How do i get over this problem please 

Are you sure you have sudo rights? In the How To step #9 details how you Give sudo rights to your new user (you).

Best way to test is from any terminal type in up from terminal, hit enter then enter your pw that will upgrade your system to the latest levels and tell us if you have sudo rights.

What you are seeing in tty1 &  tty2 (and all tty's) is just a tty label that I have set up.. It does not mean that V-ger has any control, it is just a label. So from tty1 you should be able to log in as you and run sudo smxi or login as root and run it on tty1. You also have to install smxi if you have not done so already as it is not something installed on VSIDO

Standard English keyboard layout is what is the default

You can also run the following from terminal to show you the layout

cat /etc/default/keyboard
It should show you the following

# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"

Quote from: Gordon on March 16, 2024, 03:05:04 PMHi Vastone.
I've installed VSIDO now using the fsarchiver but now I have other problems.
It won't  use "sudo adduser" keeps comming up with "Please enter a username matching the regular expression configued via the NAME_REGEX configuration variable. Use the --allow-bad-names option etc" no idea what it mene or what to do.
I also can't sign into vsido even though i'm logged in on my tablet
Cheers Gordon

On this page there are several solutions to what is happening. In short you are using an invalid character that can be used if you use the allow-bad-names variable. That link will explain it in more detail.