Salix Forums

try-alls wrote:I do have a partition left over from a previous install, so how would one mount that for permanent use as /home

Just add an entry to your /etc/fstab. Mine is:

Code: Select all

/dev/sda3       /home   xfs     defaults        1       2

ok seems simple even but now so that i can ensure that i understand the command fully the xfs is im guessing like extX an what does the default an 1 2 sections do.

try-alls wrote:also i will be copying my /root (root-home) for use in my general account i do not wish to 755 each files individually so can short track that,

You can chown all files to your new user, after you copy them.

Code: Select all

chown -R newuser:users /home/newuser

will this cover hidden files also what does the -R (i presume case-sensitive) do

EDIT: upon reading my fstab i noticed the floppy section can i erase that (safely) as my laptop doesn't have a floppy drive?

If you use it on the top level directory of your homedir, as I shown you, yes.

chown could easily be added to my top command list that, i have re-edited my last post as it came back in one long quote, lol my sections are now blue

Code: Select all

man fstab
man chown

will answer all your questions.

You can chown all files to your new user, after you copy them.

Code: Select all

chmod -R newuser:users /home/newuser

[/quote]

this command does not work invalid arguements

of course it wont work!
unless you named your user as newuser

try-alls wrote:2.. how does one use the "sbopkg" tool on salix

Since Salix' installpkg is different from slackware (as I was told) you'll need to install the created packages manually

(11:39:33 PM) slacker1: point remains, is libgtop installed?
(11:39:47 PM) zaza: not yet
(11:40:06 PM) zaza: I'm searching for the package
(11:41:36 PM) zaza: duh! /tmp/libgtop-2.24.0-i486-1_SBo.tgz
(11:42:01 PM) slacker2: zaza: execute 'head -2 /sbin/installpkg'
(11:42:23 PM) zaza: $ head -2 /sbin/installpkg
(11:42:23 PM) zaza: #!/bin/sh
(11:42:23 PM) zaza: /sbin/spkg -i "$@"
(11:42:33 PM) slacker1: heh
(11:42:39 PM) zaza:
(11:43:05 PM) slacker1: so much for it being slackware's installpkg
(11:43:14 PM) zaza: lol
(11:44:04 PM) zaza: but so far, all the software that I've installed from SBo (and slacky.eu) worked fine
(11:44:16 PM) slacker3: ah, that same argument.
(11:45:24 PM) slacker2: zaza: things that try to be compatible wrappers will often succeed but usually fail in a variety of corner cases
(11:45:48 PM) slacker2: in this case, I think it's that spkg doesn't support the 'foo%bar' syntax of the real pkgtools
(11:47:15 PM) slacker2: or maybe not - point is, it builds fine on slackware
(11:48:08 PM) thrice`: the bigger problem was figuring out whether or not you actually have software installed
(11:48:35 PM) zaza: ok, installed, but it is not showing fire :-\

Imagine how great it would be if we actually had a wiki page about that. Oh, wait...

gapan wrote:Imagine how great it would be if we actually had a wiki page about that. Oh, wait...

Well...

Why isn't there a modified package of the "binary" (script) in the salix repository? that would be better off than using text editor as root!

2) "upgradepkg --reinstall --install-new $OLDPKG%"$PKG"" is not there (new version)
there's "upgradepkg --reinstall --install-new $OLDPKG%$INSTDIR/$INSTPKG"

zAchAry wrote:Well... Why isn't there a modified package of the "binary" (script) in the salix repository? that would be better off than using text editor as root!

Is that an offer? I'm expecting your ticket with the package submission then.

Salix Forums

a few questions?

Re: a few questions?

Re: a few questions?

Re: a few questions?

Re: a few questions?

Re: a few questions?

Re: a few questions?

Re: a few questions?

Re: a few questions?

Re: a few questions?

Re: a few questions?