Thread: [Pcbsd-developer] Re: PCBSD-Developer digest, Vol 1 #40 - 2 msgs

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I agree will at least all addons that I know you suggested (CPU, PF,
IPFW, etc...)

Charles.

=DChel kenal p=E4eval (laup=E4ev 27 mai 2006 3:02 pm) kirjutas Andrei Kolu:
> Hello!
>

In case someone missed:

HXC wrote:
  I have added the following lines to fstab:=20
Code:
  /dev/ad1s1    /mnt/ad1s1           msdosfs    rw    0 0
  . This works and every boot my fat partition gets mounted. However only r=
oot=20
can read/write and I would like that every user can do that. How can I=20
achieve this?

antik wrote:
add user to group "operator" and fill files with following info:=20
=20
 /etc/devfs.rules=20
=20
Code:
  [devfsrules_common=3D7]=20
 add path 'ad*'  mode 666 group operator=20
 add path 'acd*'  mode 660 group operator=20
 add path 'cd*'   mode 660 group operator=20
 add path 'pass*' mode 660 group operator=20
 add path 'xpt*'  mode 660 group operator
  =20
=20
 /etc/rc.conf:=20
=20
Code:
  devd_enable=3D"YES"=20
 devfs_system_ruleset=3D"devfsrules_common"
  =20
=20
 or something like this...

On 5/28/06, Andrei Kolu <an...@gm...> wrote:
>
> =DChel kenal p=E4eval (laup=E4ev 27 mai 2006 3:02 pm) kirjutas Andrei Kol=
u:
> > Hello!
> >
>
> In case someone missed:
>
> HXC wrote:
>   I have added the following lines to fstab:
> Code:
>   /dev/ad1s1    /mnt/ad1s1           msdosfs    rw    0 0
>   . This works and every boot my fat partition gets mounted. However only
> root
> can read/write and I would like that every user can do that. How can I
> achieve this?
>
> antik wrote:
> add user to group "operator" and fill files with following info:
>
> /etc/devfs.rules
>
> Code:
>   [devfsrules_common=3D7]
> add path 'ad*'  mode 666 group operator
> add path 'acd*'  mode 660 group operator
> add path 'cd*'   mode 660 group operator
> add path 'pass*' mode 660 group operator
> add path 'xpt*'  mode 660 group operator
>
>
> /etc/rc.conf:
>
> Code:
>   devd_enable=3D"YES"
> devfs_system_ruleset=3D"devfsrules_common"
>
>
> or something like this...

You could also use the -u and -g options of mount, eg:
mount_msdos -u 1001 -g 1001 /dev/ad0s1 /mnt/msdos
That will make the owner the uid and gid you specify.
I'm not quite sure howto do this in the fstab though.

-------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications i=
n
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=107521&bid$8729&dat=121642
> _______________________________________________
> PCBSD-Developer mailing list
> PCB...@li...
> https://lists.sourceforge.net/lists/listinfo/pcbsd-developer
>

Hello guys!

I am installed pcbsd 1.1 onto my laptop now and I would say I am dissapointed, 
where is updates?:

1. long list of old packages, major ones like dejavu fonts, lots of 
improvements in fonts readability is missed now.. kde packages not updated, 

dejavu-2.4.1                        <   needs updating (port has 2.6)
gstreamer-0.8.11_2                  <   needs updating (port has 0.10.6)
gstreamer-plugins-0.8.11_2          <   needs updating (port has 0.10.7)
kaffeine-0.8                        <   needs updating (port has 0.8.1)
kdemultimedia-3.5.2                 <   needs updating (port has 3.5.2_1)
kdepim-3.5.2                        <   needs updating (port has 3.5.2_1)
kdeutils-3.5.2                      <   needs updating (port has 3.5.2_1)
xorg-server-6.9.0_1                 <   needs updating (port has 6.9.0_3)

2. some 3D card support is not included in kernel
3. network manager is a joke- it can't show even nics from rc.conf
4. portsnap in system manager still can't show proper download status.
5. Installer still won't let you customize installation partitions.
6. no timezone selector within installer
7. bugzilla shows no progress in squizing bugs
8. still no plans for the future, timeline, goals
9. not enough information for community- what's going on- I see only surprise 
releases coming along...oops... test, test and test again...

This is not the way of doing business, gentlemens. To me it seems 
unprofessional here. If these areas shows no improvement in recent future 
then I start my own fork of BSD desktop. I see all pcbsd developers busy 
making money out of community efforts and even selling forums like support 
for customers. Nobody want's half assed product IMHO.

Andrei

I think part of the reason you are disappointed is that you 
misunderstand my intent with updates such as 1.1. 1.1 is not meant to be 
an entire "System Transformation", but rather a small update to bring 
the core OS up to FreeBSD 6.1. (And fix the online update manager) 
Things such as redoing the system installer, changing network manager, 
portsnap etc are functionality updates. These are things that should be, 
and will be upgraded at the next major release point of PC-BSD, probably 
2.0. This isn't to say that some things will not be fixed, For example, 
some of the ports will be updated, etc.

The network manager is really just a frontend to "ifconfig", so if you 
run ifconfig, and it doesn't see a device, then the network manager will 
not as well. This needs to be changed, but that is more than just a 
"bugfix", but rather a lot of new functionality needs to be added in, 
such as WIFI support, etc. I have a document here with a huge list of 
the TODO's that need to be done for the next *major* release of PC-BSD, 
and I'll be fixing it up over the next week and posting it online for 
comments and feedback here shortly.

I would just ask that folks be patient. Windows XP and Mac OS X weren't 
built overnight, but rather are the results of years of full-time 
dedicated teams of developers to make them as powerful as they are. (You 
could throw RedHat & SuSE in there as well) As of now, PC-BSD has 
primarily two C++ developers, Tim and I. With neither of us employed 
full-time by PC-BSD, it takes time to get these things done. But when 
you consider where we are now, from only 1 year ago, when Charles saw my 
pitiful website and stepped in, it's a huge leap :) I look forward to 
seeing how PC-BSD has matured a year from now as well!

If anybody reading this has some skill with C++ / QT or any other 
developer ability, I welcome them to volunteer! With the new subversion 
server setup, we can get developers added quickly and get them rolling 
on these nice updates.

- Kris Moore

Andrei Kolu wrote:
> Hello guys!
> 
> I am installed pcbsd 1.1 onto my laptop now and I would say I am dissapointed, 
> where is updates?:
> 
> 1. long list of old packages, major ones like dejavu fonts, lots of 
> improvements in fonts readability is missed now.. kde packages not updated, 
> 
> dejavu-2.4.1                        <   needs updating (port has 2.6)
> gstreamer-0.8.11_2                  <   needs updating (port has 0.10.6)
> gstreamer-plugins-0.8.11_2          <   needs updating (port has 0.10.7)
> kaffeine-0.8                        <   needs updating (port has 0.8.1)
> kdemultimedia-3.5.2                 <   needs updating (port has 3.5.2_1)
> kdepim-3.5.2                        <   needs updating (port has 3.5.2_1)
> kdeutils-3.5.2                      <   needs updating (port has 3.5.2_1)
> xorg-server-6.9.0_1                 <   needs updating (port has 6.9.0_3)
> 
> 2. some 3D card support is not included in kernel
> 3. network manager is a joke- it can't show even nics from rc.conf
> 4. portsnap in system manager still can't show proper download status.
> 5. Installer still won't let you customize installation partitions.
> 6. no timezone selector within installer
> 7. bugzilla shows no progress in squizing bugs
> 8. still no plans for the future, timeline, goals
> 9. not enough information for community- what's going on- I see only surprise 
> releases coming along...oops... test, test and test again...
> 
> This is not the way of doing business, gentlemens. To me it seems 
> unprofessional here. If these areas shows no improvement in recent future 
> then I start my own fork of BSD desktop. I see all pcbsd developers busy 
> making money out of community efforts and even selling forums like support 
> for customers. Nobody want's half assed product IMHO.
> 
> Andrei
> 
> 
> -------------------------------------------------------
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> _______________________________________________
> PCBSD-Developer mailing list
> PCB...@li...
> https://lists.sourceforge.net/lists/listinfo/pcbsd-developer
> 
> 

=DChel kenal p=E4eval (kolmap=E4ev 31 mai 2006 3:44 am) kirjutas Kris Moore=
 - PC-BSD=20
Software:
> I think part of the reason you are disappointed is that you
> misunderstand my intent with updates such as 1.1. 1.1 is not meant to be
> an entire "System Transformation", but rather a small update to bring
> the core OS up to FreeBSD 6.1. (And fix the online update manager)
> Things such as redoing the system installer, changing network manager,
> portsnap etc are functionality updates. These are things that should be,
> and will be upgraded at the next major release point of PC-BSD, probably
> 2.0. This isn't to say that some things will not be fixed, For example,
> some of the ports will be updated, etc.
Of course I misunderstand when there is no information about what is going =
on=20
and why there is such a rush about releasing untested updates?

Another thing that is bothering me is "Official Changelog for PC-BSD"=20

 * Upgraded Online Update Utility to display status + plus major bugfixes.
 * Added DRM / ATI support to default kernel.=20
 * Misc bugfixes.

What major bugfix, what Misc. bugfixes?? Bugzilla is your friend but I see=
=20
nowhere mention about it.

DRM stands for Direct Rendering Modules and is the kernel modules installed=
 by=20
the drm-kmod port. You have to explain it to users, most of em would think=
=20
now that PC-BSD is DRM (Digital Rights Management) infested.

More facts please.

> The network manager is really just a frontend to "ifconfig", so if you
> run ifconfig, and it doesn't see a device, then the network manager will
> not as well.=20

Detected Network Adapters:
ral0 (Ralink Technology RT2500)
Device Status:
nothing !!!

Device Properties:
Static IP Address
IP Address: nothing !!!
Netmask: 255.255.255.0 !!!

Now the real ifconfig:
ral0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
=A0 =A0 =A0 =A0 inet6 fe80::20e:2eff:fe4f:dd90%ral0 prefixlen 64 scopeid 0x5
=A0 =A0 =A0 =A0 inet 192.168.1.2 netmask 0xfffffff0 broadcast 192.168.1.15
=A0 =A0 =A0 =A0 ether 00:0e:2e:4f:dd:90
=A0 =A0 =A0 =A0 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
=A0 =A0 =A0 =A0 status: associated
=A0 =A0 =A0 =A0 ssid turvaauk channel 11 bssid 00:05:5d:xx:xx:xx
=A0 =A0 =A0 =A0 authmode OPEN privacy OFF txpowmax 100 protmode CTS bintval=
 100

Explanation:
IP Address: 192.168.1.2
Netmask: 255.255.255.240

Yes I don`t have WPA right now I use pppoe encryption.

> This needs to be changed, but that is more than just a=20
> "bugfix", but rather a lot of new functionality needs to be added in,
> such as WIFI support, etc. I have a document here with a huge list of
> the TODO's that need to be done for the next *major* release of PC-BSD,
> and I'll be fixing it up over the next week and posting it online for
> comments and feedback here shortly.

Wifi is configured via ifconfig novadays.
Post this ToDo to developers list please.

> I would just ask that folks be patient. Windows XP and Mac OS X weren't
> built overnight, but rather are the results of years of full-time
> dedicated teams of developers to make them as powerful as they are. (You
> could throw RedHat & SuSE in there as well) As of now, PC-BSD has
> primarily two C++ developers, Tim and I. With neither of us employed
> full-time by PC-BSD, it takes time to get these things done. But when
> you consider where we are now, from only 1 year ago, when Charles saw my
> pitiful website and stepped in, it's a huge leap :) I look forward to
> seeing how PC-BSD has matured a year from now as well!

I know all developers work hard for this project but lack of information is=
 a=20
killer. And it would be nice to have more information about PC-BSD Software=
=2E=20
Is this a company of some sort or what? To me DesktopBSD development seems=
=20
more professional and transparent, learn from em. I think PC-BSD primary go=
al=20
must be documentation and only then development of miscellaneous tools.=20
Current PC-BSD Network Manager tool is useless and I`d never release it unt=
il=20
it become feature complete. Now it just confuse newcomers and make it hard =
to=20
use this overall great distribution.=20

PC-BSD is beta quality product now and marking it with 1.0 and 1.1 release=
=20
number is just plain stupid. If it is beta then call it appropriately. It=20
reminds me Microsoft with their shitty product line with enormous sheet of=
=20
bugs never fixed...

Online update utility downloading in background is BAD idea IMHO. Microsoft=
=20
once did this mistake with Windows 95 and I remember what happened- these=20
days nobody trust microsoft anymore. Users must have more choices, they wan=
t=20
to know what their OS is doing.

> If anybody reading this has some skill with C++ / QT or any other
> developer ability, I welcome them to volunteer! With the new subversion
> server setup, we can get developers added quickly and get them rolling
> on these nice updates.

If you want more developers you have to have right tools for work. Bugzilla=
 is=20
useless if nobody use it for bug tracking. And if users in forum ask=20
developers about something and nobody is replying then this is bad=20
imagemaking. If you don`t know something or this exact feature is not your=
=20
primary goal then say so.

Simple revision control for impatient:
# touch /bin/rvi=20
# ee /bin/rvi

type in file these lines:
#!/bin/sh=20
 co -l $1=20
 vi $1=20
 rcsdiff -u $1=20
 ci -u $1

Now make it work:
# chmod 555 /bin/rvi=20
# rehash
# cd /etc/
# mkdir RCS
# rvi rc.conf
follow the instructions.

If you want file with some revision number then:
# co -r1.5 rc.conf

=46or more information:
# apropos rcs

Kris you have done great job and now you have to be responsible for it to w=
ork=20
further. One man army is not an option. My english not fluent enough to say=
=20
it more smooth way, but I think all of you understand what I mean by this=20
criticism of mine.

P.S. I am 30 years old and work with unix based systems from 1994. Started =
my=20
first company while 20 years old. My CV is 4 pages long and I have=20
experiences from webdesign, hardware diagnostics, customer services,=20
webhosting, managing large networks, server manufacturing, business/project=
=20
management. etc. and I am not a programmer- I know how to program, but I ha=
ve=20
no time for this.

Yours Truly
Andrei

Hi! I played here with Xorg autodetection and made this litle script for 
testing- it may work on all computers I think. Xorg detects your video card 
and creates config file that is much better than PC-BSD current one. You can 
set resolution and colour depth from command line:

# pimpmyvga.sh resolution depth
# pimpmyvga.sh 1280x1024 24

TODO: 
1. Add fonts path not included in autodetected config file. 
2. Make graphical interface for setting resolution, colour and refreshrate.
3. Make script for testing current config file within 15 seconds where user 
can interact with gui and press accept button if it works. If failed itt 
would be reverted back to more conservative default resolution as 1024x768 or 
vesa driver.

I don't know is it my problem or 6.1 USB engine is broken:

---------------------------------------------------------------
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <Samsung DSC DKJ2 > Removable Direct Access SCSI-0 device
da0: 1.000MB/s transfers
da0: 488MB (1000448 512 byte sectors: 64H 32S/T 488C)
umass0: Phase Error, residue = 0
(da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status 
== 0x0
umass0: Phase Error, residue = 0
(da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x4, scsi status 
== 0x0
umass0: Phase Error, residue = 0
---------------------------------------------------------------
with 6.0 it worked just fine.

After major upgrade I can't mount filesystems automatically anymore- only 
manually :( Device insertion detection works but just can't mount anything.

Kernel changes:
----------------------------------------------------------------------------------------------
machine         i386
#cpu            I486_CPU
#cpu            I586_CPU
cpu             I686_CPU
ident           NEWPCBSD

# To statically compile in device wiring instead of /boot/device.hints
#hints          "GENERIC.hints"         # Default places to look for devices.

#makeoptions    DEBUG=-g                # Build kernel with gdb(1) debug 
symbols

options         SCHED_ULE               # ULE scheduler
#options        SCHED_4BSD              # 4BSD scheduler

options         VESA            # Vesa Support for Splash
options         SC_PIXEL_MODE   # add support for the raster tex

# Direct Rendering modules for 3D acceleration.
device          drm             # DRM core module required by DRM drivers
device          i915drm         # Intel i830 through i915
device          mach64drm       # ATI Rage Pro, Rage Mobility P/M, Rage XL
device          mgadrm          # AGP Matrox G200, G400, G450, G550
device          r128drm         # ATI Rage 128
device          radeondrm       # ATI Radeon
device          savagedrm       # S3 Savage3D, Savage4
device          sisdrm          # SiS 300/305, 540, 630
device          tdfxdrm         # 3dfx Voodoo 3/4/5 and Banshee
#!!!options         DRM_DEBUG       # Include debug printfs (slow)

options         HZ=1000
options         DEVICE_POLLING

# PF firewall
device pf
device pflog
device pfsync

# PF ALTQ
options         ALTQ
options         ALTQ_CBQ        # Class Bases Queuing (CBQ)
options         ALTQ_RED        # Random Early Detection (RED)
options         ALTQ_RIO        # RED In/Out
options         ALTQ_HFSC       # Hierarchical Packet Scheduler (HFSC)
options         ALTQ_PRIQ       # Priority Queuing (PRIQ)
options         ALTQ_NOPCC      # Required for SMP build
----------------------------------------------------------------------------------------------

/etc/devfs.rules
----------------------------------------------------------------------------------------------
[devfsrules_common=7]
add path 'acd*'  mode 660 group operator
add path 'cd*'   mode 660 group operator
add path 'pass*' mode 660 group operator
add path 'xpt*'  mode 660 group operator
----------------------------------------------------------------------------------------------

/etc/rc.conf
----------------------------------------------------------------------------------------------
background_dhclient="YES"
hostname="localhost.my.domain"
compat5x_enable="YES"

NIC="de em ixgb txp vx bfe bge dc fxp lge nge pcn re rl sf sis sk ste ti tl tx 
vge vr wb xl cs ed ex ep fe ie lnc sn xe an awi wi nve"

for i in $NIC; do
      eval ifconfig_${i}0="DHCP"
      eval ifconfig_${i}1="DHCP"
done

blanktime="180"
saver="logo"
sshd_enable="YES"
usbd_enable="YES"
moused_type="auto"
moused_enable="YES"

#Enable samba server
samba_enable="NO"

# Disable LPD
lpd_enable="NO"

# Enable CUPS
cupsd_enable="NO"
background_cupsd="YES"
enable_linux="YES"

# FSCK Enhancements
fsck_y_enable="YES"
background_fsck="YES"

tmpmfs="YES"
tmpsize="777m"
#tmpmfs_flags="-S -o noatime,noexec,nosuid,nosymfollow"
tmpmfs_flags="-S"
nfs_server_enable="NO"
sendmail_enable="NONE"

pf_enable="Yes"
pf_logd="Yes"
pf_conf="/etc/pf.conf"

#Disable probing of idle TCP connections to verify the peer is up and 
reachable:
tcp_keepalive="YES"
#ICMP error response bandwith limiting. Helps protect against DoS attacks:
icmp_bandlim="YES"

devd_enable="YES"
devfs_system_ruleset="devfsrules_common"
removable_interfaces="an0 cbb0 cbb1 ed0 ed1 fd0 cd0 da0"
usbd_enable="YES"
ugen_load="YES"
umass_load="YES"
----------------------------------------------------------------------------------------------

/etc/pf.conf
----------------------------------------------------------------------------------------------
scrub in all
pass in all
pass out all
----------------------------------------------------------------------------------------------

/etc/hosts
----------------------------------------------------------------------------------------------
::1                     localhost localhost.my.domain
127.0.0.1               localhost localhost.my.domain
----------------------------------------------------------------------------------------------

Hello!

I have been busy testing 1.1 patch that Kris made and now I write down all 
mistakes, bugs and suggestions. I already posted some on forums, but in case 
somebody miss em, I double it here:

############## 1.1 patch pbroblems:

1. hostname is doubled again in /etc/rc.conf.
2. kldload ntfs screams that hints file is old. 
3. same problem with linprocfs 

Code:
 warning: KLD '/boot/kernel/ntfs.ko' is newer than the linker.hints file 
 warning: KLD '/boot/kernel/linprocfs.ko' is newer than the linker.hints file

linux compat may be wise to move from module to kernel for speed and I presume 
that ntfs module is loaded automatically when access to filesystem is made...

4. Xorg official config file is xorc.conf 

Code:
 ls /etc/X11 
 XF86Config

5. "nve" DHCP config still missing from /etc/rc.conf 
6. What for is this> compat5x_enable="YES"? 

My kernel does not have any older 4 and 5 compat options in kernel right now.

7. /etc/resolv.conf.save 

Code:
  search had1.wa.comcast.net. 
 nameserver 68.87.69.146 
 nameserver 68.87.85.98 

This file overwrites current dns servers served by ISP or local router 
in /etc/resolv.conf and causing loose of internet connections. I think I got 
it when upgraded 6.0 installation manually to 6.1 and missed some config with 
mergemaster but in never hurts to point out this issue.

############Some thoughts about InstallLiveCD:

1. Name it PC-BSD instead of FreeSBIE, it is not hard, I know.
2. LiveInstallCD kernel and default installation kernel MUST be the same. It 
is pitty that some users are able to run installer but stuck with unbootable 
operating system.
3. Enable "options ATA_STATIC_ID   # Static device numbering" in kernel- it is 
good for SATA drives with their nonstandard device numbering.

Thank You for Your Patience
Andrei

http://raidon.eu