January 29, 2015, 07:58:26 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1] 2 3 ... 10
 on: January 27, 2015, 04:23:48 am 
Started by Pita - Last post by nightflier
The dd method works well, but going the fat32/syslinux way has advantages. You end up with a simple, single storage volume where you can stash additional files and carry with you. There is less danger of borking your system.

If you dig a little deeper into syslinux, you can put several distros on one thumb drive and create a startup menu with several options, and still have space left over for other data.

 on: January 26, 2015, 09:14:59 pm 
Started by uelsk8s - Last post by vincent
I'm kinda liking rc3 for vlocity 7.1

some of the programs won't install like google-chrome without care in the commandline

but I installed other programs and they work just fine!

still fiddling with guake to get it going

but mail works and I like the animation, I've wanted an animated bootscreen for like everrr... and I'm gonna edittheheck out of it when I'm good enough to find it:)

probably be rolling a kernel,

and anyway, just stopped by to say Hi, I'm liking the new digs

 on: January 26, 2015, 07:22:01 am 
Started by uelsk8s - Last post by Megamieuwsel
Quoting yourself: "Speak English or die!" Cheesy

Hey, welcome back. I answered most of your concerns in the bug tracker.
That'd be: "quoting yourself, quoting Bruce Dickinson"
And yes: The default US-map is insufficient for covering the whole of English as well as the other European tongues... ;-)

 on: January 26, 2015, 06:34:09 am 
Started by uelsk8s - Last post by rbistolfi
-Localisation is CRAP! Still stuck with the retarded default US-keymap. Not even the [intl], let alone the ones with deadkeys(with or without the choice for the Alt-Gr option...)

Quoting yourself: "Speak English or die!" Cheesy

Hey, welcome back. I answered most of your concerns in the bug tracker.

 on: January 26, 2015, 03:24:25 am 
Started by Pita - Last post by Megamieuwsel
Or you could simply jump to the directory where you DL-ed the iso to and then issue (on the prompt):
dd if=<your iso> of=<mountpoint of your USB-drive>
Can't get simpler/easier than this.
Works always.

Note: the usb-drive will be wiped completely before writing the install-bootdisk to it, so back up any stuff on it you want to keep first.
Some people actually wiped a harddrive, doing this due to using the wrong mountpoint(address).

 on: January 25, 2015, 11:35:08 pm 
Started by uelsk8s - Last post by Megamieuwsel
OK, I admit that I've been out of the loop for a while, but here's my take on the RC3.1 of vl7.1 64-bit:


-First off: ANIMATION during startup?!?... A system should be RELIABLE, not the show-off-case of childish games.
 I assume showing a nice graph is ok, but wasting resources on something as useless as an animation is NOT looking professional.

-The install-interface looks nice&clean, but I got no option to create a user; had to do that post-install.
 And the "advanced" option didn't offer any advanced options; I take it, this Work In Progress.

So far: nothing really serious.Annoying but no biggie.

-Localisation is CRAP! Still stuck with the retarded default US-keymap. Not even the [intl], let alone the ones with deadkeys(with or without the choice for the Alt-Gr option...)

-Permissions of some of the programs, installed through GSLAPT are not set right; Chrome had to be adjusted manually and the installed binary was not in the path.
 gparted is missing dependencies.

-The default vesa-driver doesn't work well with my Geforce 8400GS(Screen blacks out for some seconds at irregular interfalls...) and that brings me to:

Starting up in TUI won't let me in; It refuses to accept ANY login, be it root-account or regular user.
Issuing <init 2> or <init 3> gives me the (nice, admitted) Vlocity-graph, but no prompt whatsoever
And what happened to good 'ole "killx"?...
Did I mention, the NVIDIA-driver doesn't install when in an X-environment?...

- The system is actually slower than my 7.0 32 bit install....
 Trust me: The AMD AThlon quad-core really is a 64-bit processor...

This after a mere 2 hours of joshing around with it.
This is NOT a release-candidate.
Calling it "beta" would be a stretch...

 on: January 23, 2015, 09:55:49 am 
Started by denbid - Last post by polaris96
Based on the brevity of the question and the (unintentional?) poll, I believe you're a first time user?

if so:

1 partition only.  ext4 filesystem.  use default mount options, if asked.

If you're looking deeper please give us more information to work with.

 on: January 22, 2015, 12:30:09 pm 
Started by polaris96 - Last post by polaris96
I'm flattered and interested.

I'm writing a more comprehensive document.  I just ask a bit of time because I don't have much to spare Sad

Watch the the doc above.  I'm adding a changelog to document tweaks.  When It's acceptable as a reference I'll post the whole thread into the "How To" section.

You are most welcome to use any or all of it as you see fit.  I'm glad to contribute.

Give me a bit of time to finish the tutorial to an acceptable standard and I'll push you rst and latex versions.

 on: January 22, 2015, 09:54:28 am 
Started by polaris96 - Last post by M0E-lnx
Nice.  I'd like to see this officially documented.  If you'd be kind enough to write it in rst syntax, we could include it in the vlcore documentation.

 on: January 21, 2015, 05:01:39 pm 
Started by polaris96 - Last post by polaris96
22 January 2015:   Added fstab entries and corrected spelling / grammar.  Also added some comments and background material to procedures.

24 January 2015:  Added a bit on changing HOSTNAME and a few more spelling corrections.  Suggested 8G or bigger usb stick.  Added sample syntax for the lvm share entry in grub.cfg

Hello, $ALL;

I'm a new VL user.  I like LVM. A LOT.  Pleased to say it was very straightforward migrating VL to an LVM share.  I'll write a PROPER how to as soon as I have the time to do so.  Here's a quick and dirty for any that want to mess around with it right away.


1.  This will not make sense to some very new linux users.  As I mentioned above I will be writing a more comprehensive how to when I get time.
2.  I'm using Grub2, here.  Lilo would probably work, but I have no experience tweaking lilo.


1.  You must alread have a basic understanding of GRUB2 ( or Legacy ) and LVM.  You must also know the general qualities of a POSIX system.


1.  Boot VL Live

2.  Grab a 8G or larger USB stick and Install VL from the choice on the Live image GUI. ([menu][system][install VL])
      A.  Install to the USB Stick
      B.  Make sure you select all available services when installing.  I thought I could get away without Inet  and boxed my Dbus connection to the X server (No mouse and keyboard).  VL is small.  Don't cut corners to save more space.  It's counterproductive.
      C.  Install the mkinitrd package from the slackware 13.37 repo (google it.  URL to follow in proper tutorial)
      D.  using a terminal:
mount /dev/sd[$whatever your USB is] /mnt
mount --rbind /dev /mnt/dev
mount -t proc /proc /mnt/proc
mount -t sysfs /mnt/sys
chroot /mnt
you should see the usual text the VL prints on a login.  You are now operating inside the new install environment (cool, huh?).  
This means your root directory(/) within the chroot terminal is actually /mnt/.  Any changes you make to the system will be made within the chroot environment (usb stick) and not the system you booted on startup.

3.  edit the file /etc/minitrd.conf (this will initially be saved in /etc/initrd.conf.sample.  use nano to edit it and save as mkinitrd.conf)
Nano is very easy to use (think I'm lying?  Try vi then get back to me.).  If you need more info there's a manpage and plenty of how tos on the web.
nano /etc/mkinitrd.conf.sample
you will see
# mkinitrd.conf.sample
# See "man mkinitrd.conf" for details on the syntax of this file
ROOTDEV="/dev/$USB_PATH" # replace $USB_PATH with your actual device node
OK, it won't look EXACTLY like that.  I'm on my slack64 machine now.  Here's what you need to do:
LVM="1" you can live without this if you only want the USB system.  If you want LVM, you need it.
WAIT="10" (usb drives are slow to come up in early boot space.  your initrd will crash if you don't wait for root to appear)
ROOTDEV="$DEV-PATH-TO-ROOT"  this is the address for the usb stick you just installed to.  (ex. /dev/sdf1 )
OUTPUT_IMAGE="/boot/slack/initrd.gz"  this is the location of the ramdisk you will be making.  It's wise to sign your work.  The path should be the location of you vmlinuz, config.sys, and files.  You might try "/boot/initrd-usbvector.gz".  I like to name my ramdisks because I usually have several in my bootdir.
Also, make sure there are no comment marks ("#") in front of the lines you need to change

4.  Make the ramdisk
mkinitrd -F
Then open your boot directory and look for the $INITRD you specified in OUTPUT_IMAGE.

5.  Leave the chroot and unmount the usb system
cd /
umount /mnt
cat /etc/mtab
Check the contents of mtab, making sure your usb device isn't mounted on /mnt anymore

6.  Edit /boot/grub.cfg (this is normally a gigantic No-No, but I've always preferred to edit grub.cfg and not run update-grub until I know the system will run as routed.  more on that in the real tutorial)
nano /boot/grub.d/grub.cfg
then add something like this:
menuentry "Vector 3.0.8" --class linux --class gnu --class os {
insmod part_msdos
insmod $FILESYSTEM #replace the variable with the proper FS for your USB system
set root='(hd0,msdos1)' #This needs to be the correct root partition.  google grub setup if you need to
linux /slack/vmlinuz root=/dev/$USBPATH ro rootdelay=9 #Rootdelay is a nice feature that can hold the root mount without waiting in initrd.  You don't need it if you set up initrd as above
initrd /slack/initrd.gz  #All of these paths need to be corrected for your actual devices.  I will go deeper when I have time

7.  Reboot and select "Vector 3.0.8" from the grub2 menu.  If everything was done correctly, you're now into "Normal" VL 7 system mounted on a USB stick (This makes an awesome rescue disk and it's fun to show off to your geeky pals)
pvcreate /dev/hda   # this identifies your HDD to the lvm abstraction layer
vgcreate VCTRVG   # this creates a "Volume Group" from which you can create LVs
lvcreate -n $NAME -L $SIZE VCTRVG   # Create a logical volume
mkfs -t $FSTYPE /dev/VCTRVG/$NAME   # Create a filesystem on the LV
mount /dev/VCTRVG/$NAME /mnt  # mount the partition so you can write to it.

8.  Next, we need some rules for rsync.  rsync is a flexible and powerful file synchronizing utility.  We're going to "mirror" our usb setup onto the logical volume.  We need to make sure it doesn't go into a tailspin by trying to copy the directory we're writing to (/mnt), or waste a lot of space copying data that isn't really stored (/proc, /dev, /sys) or that we don't need at all (/tmp).
cat <<EOF > mirror-root.rules  #we're using the cat command with an stdin redirect to write our rules file
>- /proc
>- /sys
>- /dev
>- /tmp
>- /mnt
> -*.iso

9.  Before we mirror, customize the system if you want.  You don't have to, but I liked my Vector USB system so much I pretty much created the laptop LVM system I was looking for, utility and graphics wise.  Now I have two exactly similar systems.

10.  Now use rsync.  Do a dry run first
rsync -nav --filter="merge ./mirror-root.rules" / /mnt

11.  You should see gibberish- LOTS of gibberish.  if you see ERROR statements or if it terminates quickly, check your syntax.  Otherwise, run it for real.
rsync -av --filter="merge ./mirror-root.rules" / /mnt

12.  Now, create the missing folders
cd /mnt
mkdir proc mnt dev tmp sys # if the kernel deosn't see all these folders it will halt the boot before root gets mounted.

13. set up another chroot
mount --rbind /dev /mnt/dev
mount -t proc /proc /mnt/proc
mount -t sysfs /mnt/sys
chroot /mnt

14.  edit the /etc/initrd file to add the correct path to the lvm share:
nano /etc/mkinitrd.conf
you need to change the ROOTDEVICE parameter and make sure lvm is enabled also
ROOTDEV="/dev/mapper/VGVCTR/$NAME"  #usually lvm shares can be assigned as "/dev/mapper/$VG/$LV" or sometimes "/dev/mapper/$VG-$LV"

15.  Edit fstab.  You need to tell root where the fs mounts are
nano /etc/fstab
you need something like:
/dev/mapper/VCTRVG-RootVector / ext4 defaults 1 1
You should be ok with all of the other entries in fstab

16.  Change the hostname, if you want

17.  Change grub.cfg again.  You can C/P the entry above and alter the paths to your lvm share, but make sure to add an "insmod lvm" line to the other insmod statements.

Here's a sample Grub.cfg entry
menuentry 'Vector LVM' --class gnu --class os {
insmod gzio
insmod part_msdos
insmod lvm
set root=lvm/X60--vg-Vector  #PAY CLOSE ATTENTION TO THIS SYNTAX "lvm/$VG-$LV"
echo 'Loading Vector Linux 7...'
linux /boot/vmlinuz-3.0.8 root=/dev/mapper/X60--vg-Vector ro
echo 'Loading initial ramdisk ...'
initrd /boot/initrd-polarisLVM.gz


OK, I know this is sketch, but I'll write more when I can.  Fell free to ask questions and I'll do my best to return answers, but, like I said, I'll be doing a better tutorial when I can



Pages: [1] 2 3 ... 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!