Forum Debian Users Gang

A to przepraszam w takim razie. :)

Hal to zło. Tylko nie wszystko działa z devd, ale jest na tyle kompatybilne z udev, że reguły z niego działają.

Xorg bez hal/dbus

http://www.bsdguru.org/dyskusja/viewtopic.php?f=38&t=19150

Dla zainteresowanych.

Co prawda fstack-protector-strong dostepny jest od wersji gcc 4.9, ale pod FreeBSD 9.2 dla gcc 4.8, ktore jest w portach (lang/gcc48) jest juz dostepny patch, ktory pozwala uzyc opcji "strong":

http://www.freebsd.org/cgi/query-pr.cgi?pr=186852

FreeBSD has recently added the WITH_SSP_PORTS makefile option [1] which adds "-fstack-protector" and "-fstack-protector-all" compilation directives which adds extra code to check for buffer overflows to compiled ports [2].

While this is a good first step, those switches offer too little or too much protection and over 2 years ago, Google delivered "-fstack-protector-strong" [3] to try and solve the problem:
"The stack-protector option is over-simplified, which ignores pointer cast, address computation, while the stack-protector-all is over-killing, using this option brings too much performance overhead..." [4]

The new directive has been added to the 4.9 branch of gcc and several Linux distros have backported the patch, but so far, FreeBSD maintainer has decided not to do it, so here are patches which work against lang/gcc48.
There are based on the gcc 4.9 commits [5]

Do make.conf

WITH_SSP_PORTS=YES
SSP_CFLAGS=-fstack-protector-strong --param ssp-buffer-size=4

Dla Clang'a juz niebawem :)

Pzdr.

Ostatnio edytowany przez bryn1u (2014-02-24 09:11:19)

sysek napisał(-a):

zastanawiam się czasem czy by nie przejść na *BSD. Kiedyś tam instalowałem i się bawiłem, ale były problemmy z grafą. Teraaz mam Intel HD więc chyba nie będzie problemów, ale mam pytanie. Czy komuś z was udało się uruchomić natywnego steama ?

Wszystko to co jest pod linuxem mozesz uruchomic na freebsd. Ja odpalalem kiedys servery hlds, dzialaly bez problemu. Od wersji FreeBSD 10.0 (akutalna) jest wspierana wieksza ilosc sterownikow grafy. Steam tez powninien Ci dzialac bez zadnych problemow.

Ostatnio edytowany przez bryn1u (2014-02-24 12:46:09)

fervi napisał(-a):

Steam tez powninien Ci dzialac bez zadnych problemow.

Nigdy BSD nie używałem, ale takie cuda to przez Linux Compat chyba?

Ciekawe jak działa Linux Compat

Fervi

Tak, przez linux_compat. Dziala bardzo dobrze, wydajnie.

Ostatnio edytowany przez bryn1u (2014-02-24 15:17:31)

U mnie intel działa.

Yampress napisał(-a):

sysek napisał(-a):

zastanawiam się czasem czy by nie przejść na *BSD. Kiedyś tam instalowałem i się bawiłem, ale były problemmy z grafą. Teraaz mam Intel HD więc chyba nie będzie problemów, ale mam pytanie. Czy komuś z was udało się uruchomić natywnego steama ?

chyba  bachnę śmiechem. Pamiętam jeszcze twoje wyśmiewki na kanale #error odnośnie bsd.

zawsze pamiętasz jakieś dziwne rzeczy.

Również zainstalowałem pc-bds ogólnie pierwsze wrażenie super, to możemy się skumać z menel jako nowicjusze. Żeby nie zakładać nowego tematu, prosiłbym o nakierowanie jak zainstalować tam przeglądarkę z repo ewentualnie ustawić repo. Trochę czytałem o systemie, że jest inny niż linux. Potrzebuję przeglądarkę resztę doczytam, bo teraz jestem na drugim kompie.

pkg_add -r opera

Nie rozpoznaje komendy

Ostatnio edytowany przez tajwan (2014-03-04 12:17:19)

tajwan napisał(-a):

Potrzebuję przeglądarkę resztę doczytam, bo teraz jestem na drugim kompie.

Kod:

pkg_add -r opera

Nie rozpoznaje komendy

Nieoceniony Yampress podał:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html
Dopowiem, że masz pkg w systemie:

# pkg install packagename

# sysctl hw.realmem                  # Hardware memory
# sysctl -a | grep mem               # Kernel memory settings and info
# top                                # display and update the top cpu processes
# mpstat 1                           # display processors related statistics
# vmstat 2                           # display virtual memory statistics
# iostat 2                           # display I/O statistics (2 s intervals)
# systat -vmstat 1                   # BSD summary of system statistics (1 s intervals)
# systat -tcp 1                      # BSD tcp connections (try also -ip)
# systat -netstat 1                  # BSD active network connections
# systat -ifstat 1                   # BSD network traffic through active interfaces
# systat -iostat 1                   # BSD CPU and and disk throughput

Wy prostej rzeczy nie potraficie zrozumieć. Pcbsd wczytuje mnóstwo sterowników aby jak na największej liczbie maszyn działało. I pożera zasoby.
Prędkość dopiero widać na czystym freebsd nie na klonach dla lamerów. Bo to chodzi ładnie  ale zużywa zasoby. Koszt przystosowania freebsd pod "większość" desktopów. Inwidualna personalizacja pod konkretną maszynę tego nie robi. Teraz trzeba się pomęczyć aby odchudzić system.  Czyli dojść do pyunktu tego jaki osiąga czyste freebsd zaraz po instalacji...

http://www.freebsd.org/doc/en/books/handbook/mount-unmount.html

Wiesz bsd to nie linux.

http://www.freebsd.org/cgi/man.cgi?fstab(5)
http://daemonforums.org/showthread.php?t=4378


FFS Mount Types

Unlike Windows filesystems, FreeBSD treats FFS partitions differently
depending on how they’re mounted. The manner in which a partition is
mounted is called the mount type. If you’re mounting a partition manually,
you can specify mount options on the command line, but if you’re using
/etc/fstab to mount it, you must specify any choice in the Options column.
Use -o mounttype to specify a mount type on the command line, or specify
the option in /etc/fstab in the Options column.
Read-Only Mounts
If you want to look at the contents of a disk but not write to it, mount the
partition read-only. In most cases, this is the safest and the most useless way
to mount a disk, because you cannot alter the data on the disk or write any
new data.
Many system administrators mount the root partition, and perhaps even
/usr, as read-only to minimize potential system damage from a loss of power
or software problems. Even if you lose the physical hard drive due to a power
surge or other hardware failure, the data on the platters remains intact.
That’s the advantage of read-only mounts. The disadvantage is that system
maintenance becomes much more difficult because you cannot write to read-
only disks!
Read-only mounts are especially valuable when your computer is
damaged. While FreeBSD won’t let you perform a standard read-write
mount on a damaged or dirty filesystem, it can perform a read-only mount
most of the time. This gives you a chance to recover data from a dying system.
To mount a filesystem read-only, use one of the options rdonly or ro.
Both work identically.
Synchronous Mounts
Synchronous (or sync) mounts are the old-fashioned way of mounting file-
systems. When you write to a synchronously mounted disk, the kernel waits
to see whether the write is actually completed before informing the program.
If the write did not complete successfully, the program can choose to act
accordingly.
Synchronous mounts provide the greatest data integrity in the case of a
crash, but they are also slow. Admittedly, “slow” is relative today, when even a
cheap disk outperforms what was the high end several years ago. Consider
using synchronous mounting when you wish to be truly pedantic on data
integrity, but in almost all cases it’s an overkill.
To mount a partition synchronously, use the option sync.
Asynchronous Mounts
While asynchronous mounts are pretty much supplanted by soft updates,
you’ll still hear about them. For faster data access at higher risk, mount your
partitions asynchronously. When a disk is asynchronously mounted, the kernel
writes data to the disk and tells the writing program that the write succeeded
without waiting for the disk to confirm that the data was actually written.
Asynchronous mounting is fine on disposable machines, but don’t use it with
important data. The performance difference between asynchronous mounts
and noasync with soft updates is very small.
To mount a partition asynchronously, use the option async.
Noasync Mounts
Finally, we have a method that combines sync and async mounts, called
noasync. This is FreeBSD’s default. When using noasync mounts, data that
affects inodes is written to the disk synchronously, while actual data is handled
asynchronously. Combined with soft updates (see later in this chapter), a
noasync mount creates a very robust filesystem.
Noasync mounts are the default, and you don’t need to specify anything.

FFS Mount Options

FreeBSD supports several mount options in addition to the mount types.
These options change the behavior of mounted filesystems.
noatime
Every file in FFS includes an access-time stamp, called the atime, which
records when the file was last accessed. If you have a large number of files
and don’t need this data, you can mount the disk noatime so that FFS does
not update this timestamp. This is most useful for flash media or disks that
suffer from heavy load, such as Usenet news spool drives.
noexec
The noexec mount option prevents any binaries from being executed on this
partition. Mounting /home noexec can help prevent users from running their
own programs, but for it to be effective, be sure to also mount /tmp, /var/tmp,
and anywhere else users can write their own files noexec as well. Also note
that a noexec mount doesn’t prevent a user from running a shell script,
which is just a set of instructions for a program elsewhere in the system.
Another common use for a noexec mount is when you have on your server
binaries for a different operating system or a different hardware architecture
and you don’t want anyone to execute them.
nosuid
The nosuid option prevents setuid programs from running on your system.
Setuid programs allow users to run programs as if they’re another user. For
example, programs such as login(1) must perform actions as root but must
be run by regular users. Setuid programs obviously must be written carefully
so that intruders cannot exploit them to get unauthorized access to your
system. Many system administrators habitually disable all unneeded setuid
programs. You can use nosuid to disable setuid programs on a partition, but
script wrappers like suidperl get around this.
nosymfollow
The nosymfollow option disables symlinks, or aliases to files. Symlinks are
mainly used to create aliases to files that reside on other partitions. To create
an alias to another file on the same partition, use a regular link instead. See
ln(1) for a discussion of links.
Aliases to directories are always symlinks; you cannot use a hard link
for that.

O systemach plików w pamięci było już gdzieś w tym temacie. Poszukaj