I tried your solution for connecting to my samba shares without success.

I don't know if this will help, but my server is running SMS (superb mini server) based on slackware 13.37.

Here's my samba.conf

Code:

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba HOWTO Collection.
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]
log file = /var/log/samba.%m
printer = HP_Deskjet_1050_J410_series
restrict anonymous = no
ldap ssl = No
max protocol = NT1
server string = SMS
path = /var/spool
acl compatibility = winnt
workgroup = WORKGROUP
server signing = Auto
os level = 20
domain master = no
public = yes
security = share
preferred master = no
max log size = 50
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.10.0 127.0.0.0

I like this distro don't see any problems but the screen size is way to off and changing the resolution is not helping the bottom and the right side is off other than that no bugs for someone who goes on the Internet and plays some games.

EDIT: I found a fix to the screen problem you go to the Terminal and then you type in XorgWizard after you then chose vesa and then your screen resoultion wanted now there are not any bugs for Virtual Box.Last edited by Goku on Sun 24 Feb 2013, 12:27; edited 1 time in total

Yes, adding sec=ntlm to the options in YASSM solves the problem of connecting to Puppy machines on the network!

This is unfortunately not possible from the GUI in pnethood, but I will try adding this in the script and report back.

@BarryK

Adding the missing file version.h whether via symbolic link or by simply copying the missing file to the expected location does not make it possible to compile the nvidia driver. There must be some other (additional) problem.

By default the ls command displays its lists in monochrome. This is so that all terminals are supported -- even antiques from the 1980s that don't support color and relics from the 1970s that would be confused by the ANSI escape sequences needed to set text colors.

But the Linux console and terminal emulators like xterm (and those it inspired, like rxvt and urxvt) support ANSI escape sequences and color. And most folks prefer the color-coded lists (as long as the colors are well chosen), so it has been common practice for distro builders to include the "alias ls='ls --color=auto'" in a bash configuration file at least since the mid-1990s.

We all know that Puppy users like to make good use of old hardware rather than consigning it to a landfill. But I'll bet not many of us connect our Puppies to monochrome terminals. And those that do probably have terminals that are younger than three decades in age and support ANSI, so would simply display the lists in monochrome without choking on escape sequences.

So removing that line from Puppies and requiring those who want colored lists to add it back to a bash configuration file, or type "ls --color" all the time, is not necessary, nor do I expect that it would be a popular change.

As to the bright yellow on white text that ls displays for devices, I totally agree with you that it is hard to read.

But if you prefer the current white background, you can simply change the background color that ls uses to list block devices and character devices.

Add this line to your ~/.bashrc file:

Code:

export LS_COLORS='bd=40;33;01:cd=40;33;01'

Alternatively, you could put it in your /etc/profile.local file or in an appropriate line in your /etc/profile file.

Perhaps if Barry thinks that is an improvement, he might include it in /etc/profile. If not, it is an easy customization to make.

I chose bright yellow on black because that combination may look familiar to anyone that uses a distro that sets LS_COLORS using the dircolors utility. This is for consistency. This way, when you go to help your friend who is running another distro, you don't have to relearn the colors. Also, using black for a background won't affect users who already have black backgrounds. But you may use any colors you like by substituting other values for 40 and 33, and/or removing 01:

My example uses 01 to make the foreground color bright. If you don't want a bright color remove the 01 and the preceding semicolon (e.g., cd=40;33).

Likewise, for the default foreground or background colors, you don't need to use 39 or 49. Instead you may simply not set a foreground or background color by omitting the number and the semicolon (e.g., cd=33).

There does exist a dircolor utility which is helpful if you would like to make a lot of changes to LS_COLORS, but it is overkill if you just want to change a couple of things. It creates a very long string of over a thousand characters for LS_COLORS, some of which just set colors that are default anyway. Better to just set the few that you want to change.

(If you decide to try dircolor, be sure that the version you get isn't newer than your version of ls ("ls --version"). If dircolors is newer it may use new codes that the older ls doesn't understand, and you will get no colors at all.)

By default the ls command displays its lists in monochrome. This is so that all terminals are supported -- even antiques from the 1980s that don't support color and relics from the 1970s that would be confused by the ANSI escape sequences needed to set text colors.

But the Linux console and terminal emulators like xterm (and those it inspired, like rxvt and urxvt) support ANSI escape sequences and color. And most folks prefer the color-coded lists (as long as the colors are well chosen), so it has been common practice for distro builders to include the "alias ls='ls --color=auto'" in a bash configuration file at least since the mid-1990s.

We all know that Puppy users like to make good use of old hardware rather than consigning it to a landfill. But I'll bet not many of us connect our Puppies to monochrome terminals. And those that do probably have terminals that are younger than three decades in age and support ANSI, so would simply display the lists in monochrome without choking on escape sequences.

So removing that line from Puppies and requiring those who want colored lists to add it back to a bash configuration file, or type "ls --color" all the time, is not necessary, nor do I expect that it would be a popular change.

As to the bright yellow on white text that ls displays for devices, I totally agree with you that it is hard to read.

But if you prefer the current white background, you can simply change the background color that ls uses to list block devices and character devices.

Add this line to your ~/.bashrc file:

Code:

export LS_COLORS='bd=40;33;01:cd=40;33;01'

Alternatively, you could put it in your /etc/profile.local file or in an appropriate line in your /etc/profile file.

Perhaps if Barry thinks that is an improvement, he might include it in /etc/profile. If not, it is an easy customization to make.

I chose bright yellow on black because that combination may look familiar to anyone that uses a distro that sets LS_COLORS using the dircolors utility. This is for consistency. This way, when you go to help your friend who is running another distro, you don't have to relearn the colors. Also, using black for a background won't affect users who already have black backgrounds. But you may use any colors you like by substituting other values for 40 and 33, and/or removing 01:

My example uses 01 to make the foreground color bright. If you don't want a bright color remove the 01 and the preceding semicolon (e.g., cd=40;33).

Likewise, for the default foreground or background colors, you don't need to use 39 or 49. Instead you may simply not set a foreground or background color by omitting the number and the semicolon (e.g., cd=33).

There does exist a dircolor utility which is helpful if you would like to make a lot of changes to LS_COLORS, but it is overkill if you just want to change a couple of things. It creates a very long string of over a thousand characters for LS_COLORS, some of which just set colors that are default anyway. Better to just set the few that you want to change.

(If you decide to try dircolor, be sure that the version you get isn't newer than your version of ls ("ls --version"). If dircolors is newer it may use new codes that the older ls doesn't understand, and you will get no colors at all.)

I test recompiled 3.8 kernel. I did add bunch of multimedia - dvb drivers. I unticked first the automatic creation button in make menuconfig ....under multimedia ( I dont remember the exact name of that tickable option )....and then I did tick manually the drivers in multimedia section. I got the missing ivtv with hauppage pvr drivers. The problem Billtoo posted.
Brcmsmac was added just by ticking it, since it was now tickable option...due to bcma.ko inclusion.

I provide here the diff comparision of those drivers I was able to add. I am sure there are some multimedia drivers which are not needed, but anyway....there were alot useful drivers left out.

Poulsbo.ko should be left out. It interferes the /kernel/drivers/gpu/drm/gma500/gma500_gfx.ko usage if and when the modesetting_drv.so ( in /usr/lib/x/drivers-alternate ) version 0.6.0 has been added and the cedarview fix pet by 01micko has been added/installed.

As aarf posted. Modesetting for intel atom with gma graphics does not work atm.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum