Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!
Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.
Wprawdzie na stronie głównej projektu [url=http://netbsd.org/]NetBSD[/url] nie ma jeszcze żadnego anonsu, natomiast na ich serwerze ftp, znajduje się folder z nową wersją systemu linii 6.1 i 6.0 tj. [url=ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-6.1.3/]6.1.3[/url], [url=ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-6.0.4/]6.0.4[/url]
Ostatnio edytowany przez $pwd (2014-01-23 17:57:31)
Offline
Jak kogos to interesi są juz obrazy Pryka Bysdyka 10 Stable wiec juz mam na plytce wypalone to nara
Offline
EdgeBSD. Nowy system z rodziny BSD oparty na NetBSD.
http://osworld.pl/edgebsd-nowy-system-bsd/
Offline
Nigdy nie wybiore żadnego klona o chwilowym czasie bycia.
Wszystkie porty będą wspierać ??
Port CPU Machines Latest Release
acorn26 arm Acorn Archimedes, A-series and R-series systems 6.1.2
acorn32 arm Acorn RiscPC/A7000/NC and compatibles 6.1.2
algor mips Algorithmics MIPS evaluation boards 6.1.2
alpha alpha Digital Alpha (64-bit) 6.1.2
amiga m68k Commodore Amiga, MacroSystem DraCo 6.1.2
amigappc powerpc PowerPC-based Amiga boards 6.1.2
arc mips Machines following the Advanced RISC Computing spec 6.1.2
atari m68k Atari TT030, Falcon, Hades 6.1.2
bebox powerpc Be Inc's BeBox 6.1.2
cats arm Chalice Technology's Strong Arm evaluation board 6.1.2
cesfic m68k CES's FIC8234 VME processor board 6.1.2
cobalt mips Cobalt Networks' Microservers 6.1.2
dreamcast sh3 Sega Dreamcast game console 6.1.2
emips mips Machines based on "Extensible MIPS" 6.1.2
evbsh3 sh3 Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs 6.1.2
ews4800mips mips NEC's MIPS based EWS4800 workstations 6.1.2
hp300 m68k Hewlett-Packard 9000/300 and 400 series 6.1.2
hp700 hppa Hewlett-Packard 9000/700 series 6.1.2
hpcmips mips MIPS based Windows CE PDA machines 6.1.2
hpcsh sh3 Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines 6.1.2
ia64 itanium Itanium family of processors none
ibmnws powerpc IBM Network Station Series 1000 6.1.2
iyonix arm Iyonix ARM pc 6.1.2
landisk sh3 SH4 based NAS appliances by I-O DATA 6.1.2
luna68k m68k OMRON Tateisi Electronics' LUNA series 6.1.2
mac68k m68k Apple Macintosh 6.1.2
macppc powerpc Apple Power Macintosh and clones 6.1.2
mipsco mips Mips family of workstations and servers 6.1.2
mmeye sh3 Brains' mmEye Multi Media Server 6.1.2
mvme68k m68k Motorola MVME 68k SBCs 6.1.2
mvmeppc powerpc Motorola MVME PowerPC SBCs 6.1.2
netwinder arm StrongARM based NetWinder machines 6.1.2
news68k m68k Sony's m68k based "NET WORK STATION" series 6.1.2
newsmips mips Sony's MIPS based "NET WORK STATION" series 6.1.2
next68k m68k NeXT 68k 'black' hardware 6.1.2
ofppc powerpc Generic OpenFirmware compliant PowerPC machines 6.1.2
pmax mips Digital MIPS-based DECstations and DECsystems 6.1.2
prep powerpc PReP (PowerPC Reference Platform) and CHRP machines 6.1.2
rs6000 powerpc MCA-based IBM RS/6000 workstations 6.1.2
sandpoint powerpc Motorola Sandpoint reference platform 6.1.2
sbmips mips Broadcom SiByte evaluation boards 6.1.2
sgimips mips Silicon Graphics' MIPS-based workstations 6.1.2
shark arm Digital DNARD ("shark") 6.1.2
sparc sparc Sun SPARC (32-bit) 6.1.2
sun2 m68k Sun 2 6.1.2
sun3 m68k Sun 3 and 3x 6.1.2
vax vax Digital VAX 6.1.2
x68k m68k Sharp X680x0 series 6.1.2
zaurus arm Sharp C7x0/C860/C1000/C3x00 series PDA 6.1.2[/quote]amd64 x86_64 64-bit x86-family machines with AMD and Intel CPUs 6.1.2
evbarm arm ARM evaluation boards 6.1.2
evbmips mips MIPS-based evaluation boards 6.1.2
evbppc powerpc PowerPC-based evaluation boards 6.1.2
hpcarm arm StrongARM based Windows CE PDA machines 6.1.2
i386 i386 32-bit x86-family generic machines ("PC clones") 6.1.2
sparc64 sparc Sun UltraSPARC (64-bit) 6.1.2
xen i386, x86_64 Xen Virtual Machine Monitor 6.1.2[/quote]Offline
Nie wiem może jestem zbyt głupi, ale jak patrzę na takie projekty http://osworld.pl/edgebsd-nowy-system-bsd/ to nasuwa mi się tylko jedno pytanie -po co?
Offline
446
Ostatnio edytowany przez uzytkownikubunt (2016-12-01 00:44:56)
Offline
Przeszukaj sobie na http://openbsd.org/plus.html
Offline
Pc-BSD jak narazie u mnie chodzi lepiej niz debian szybciej, chodziasz system uruchamia sie dluzej. Tylko chyba zaraz mi sie ramy skoncza bo juz mam 2,5gb zajete.
Offline
A freebsd chodzi jeszcze szybciej
Offline
Zanim użyjesz "normalnej wersji" powiedz jak sprawdzasz to użycie pamięci?
Podejrzewam, że w monitorze systemu, czy jak to się nazywa.
Sprawdź jeszcze w "normalnym programie" do tego służącym i porównaj.
Offline
No właśnie, teraz porównałem u siebie (Debian Wheezy) i rzeczywiście Monitor systemu pokazuje zupełnie inne zużycie pamięci niż np. top. Z czego to wynika? Coś jest nie tak z Monitorem systemu (ksysguard)?
EDIT: Chodzi pewnie o to: https://bugs.kde.org/show_bug.cgi?id=316171
Ksysguard nie liczy "cached memory" jako zużywanej pamięci przez program. Top z kolei liczy to jako pomięć zużywaną.
Ostatnio edytowany przez davidoski (2014-03-05 07:20:46)
Offline
Z jakim systemem porównujesz debiana?
Jak porównuje w konsoli...
http://forum.dug.net.pl/viewtopic.php?id=16211&p=27 wpis numer #672 Wczoraj 21:14:52
Offline
Nie porównuję systemów tylko porównuję wskazania zużycia pamięci w ksysguard względem top na tym samym systemie (debian). Podpiąłem się pod post einsam, ponieważ od pewnego czasu walczę ze sterownikiem grafiki do kart Intel i żyję w przekonaniu, że powoduje on wyciek pamięci, a wygląda na to, że nie ma wycieku, tylko ksysguard pokazuje błędne wskazania. W ksysguard po uruchomieniu systemu zużycie pamięci przez xorg wynosi ok. 15 MB i z każdym dniem rośnie, aż osiąga ponad 100 MB (i potem już nie wiem, bo zwykle restartuję system). Natomiast w top zużycie jest cały czas takie samo, o czym dopiero teraz się przekonałem.
Offline
pamięci może mniej fbsd bierze, ale za to obciążenie klocka lekko w górę...
Offline
592
Ostatnio edytowany przez uzytkownikubunt (2016-12-01 00:48:09)
Offline
594
Ostatnio edytowany przez uzytkownikubunt (2016-12-01 00:48:12)
Offline
A jak się upgrejtuje z wersji beta na produkcyjną?
Offline
595
Ostatnio edytowany przez uzytkownikubunt (2016-12-01 00:48:13)
Offline
598
Ostatnio edytowany przez uzytkownikubunt (2016-12-01 00:48:17)
Offline
Tu jest zapytanie : czy mogę uruchamiać binarki openbsd i386 na openbsd amd64 -> No
http://www.openbsd.org/faq/faq9.html#Interact
9.4 - Running Linux binaries on OpenBSD
[quote=uzytkownikubunt][quote=Yampress]A jak się upgrejtuje z wersji beta na produkcyjną?[/quote]
Jeszcze nie jestem pewien, jak wyjdzie OpenBSD 5.5-stable to się dowiem czy dobrze rozumiem :D[/quote]
Lepiej dowiedz się [b]już[/b]. Bo przewiduje Ci instalacje od nowa wszystkiego :P
http://www.openbsd.org/faq/upgrade54.html
[b]Versions of OpenBSD[/b]
Developers from around the world are continually making minor changes to the master OpenBSD source code repository. If you download the OpenBSD source code in the morning and download it again in the afternoon, you'll get two slightly different versions of the source code. This makes the traditional release numbering used by proprietary software less than practical. At any given moment, you can get a few different versions of OpenBSD: releases, -current, -stable, and snapshots.
[b]Current[/b]
OpenBSD-current is simply the most recent development version of OpenBSD and contains code that is just making its public debut. OpenBSD-current is where much initial public review takes place and, at times, -current sees radical changes of the sort that give experienced systems administrators headaches. If a change in current temporarily breaks Web browsers, games, and database programs running on -current, but the change is for the long-term good, that's perfectly fine. These programs will work again before the next release of OpenBSD, but there's no requirement to have every program working perfectly at all times.
OpenBSD-current is available to the public at large, but it is intended for use by developers, testers, and interested parties. Support for generic UNIX user questions about -current is rather slim, because users are expected to be able to read the source code, fix problems, and contribute their work back to the community. If you can't read C, shell, and Perl, or don't feel like debugging your computer whenever something behaves in a manner you don't expect, or just don't like being left hanging until some volunteer somewhere finds the time to fix something that broke, -current is not for you.
Current is expected to work at all times, however. While it might break on occasion, those breaks are considered serious problems, and the OpenBSD team loses sleep over them. You might have to recompile your Web browser, but the project team requires a functioning core operating system at all times.
So, with all this, why would you want to run -current? One excellent reason to run -current is to test the operating system in your environment. If your new OpenBSD-current system panics under certain conditions, the OpenBSD group wants to know about it. You certainly run a risk by doing this, but the only way the operating system can be enhanced is when volunteers test the improvements in a variety of environments. If you can provide a good bug report, the developers want to hear about your crash.
If this doesn't sound like your idea of a good time, then don't run -current.
[b]Snapshots[/b]
Every few days, the OpenBSD team builds a release from the latest -current code and puts it up on a FTP server. This interim release is a snapshot and is identified only by the date it is made available. There's nothing special about a snapshot, as compared to -current; it's just the state of -current at such-and-such a time. While the developers make a reasonable effort to not build a snapshot on a day that -current is utterly unusable, it may have any of the usual problems you'll see in tracking -current. There is no real quality-assurance process for snapshots.
Snapshots are mainly provided for installation convenience. It's much easier to upgrade to the latest OpenBSD-current from the most recent snapshot than it is to upgrade to -current from the most recent release.
[b]Releases[/b]
Every six months, the pace of OpenBSD-current development is deliberately slowed. New features are polished and thoroughly tested, and public requests are made for beta testers of the latest snapshots. When the OpenBSD team is satisfied as to the quality of the software, a CVS tag (see CVS) is laid down, and a high-quality snapshot is built from that tag. This snapshot is called a release and is issued a number. This is almost certainly what you initially installed.
OpenBSD releases are numbered sequentially, starting with 2.0 and incrementing .1 with every release. Unlike most software products, a .0 release has no special meaning; it's just a point along a long path.
Once you have a release installed, you can start to follow the OpenBSD-stable patch branch.
[b]Stable[/b]
OpenBSD-stable is simply OpenBSD-release with very minor patches. These patches are generally the "errata" for the release, including security fixes, things that are of great importance, or things that affect a lot of people. OpenBSD-stable is expected to be calm and reliable, requiring little user attention. According to Theo de Raadt, "The -stable tree must never get worse. It must never break. The fixes must be simple, even if hackjobs. They must not fail." This is an excellent choice for a production environment.
The only way to get OpenBSD-stable is to update the system from source. You can get effectively the same OS as -stable by applying the errata for a release, however.[/quote]
Offline
601
Ostatnio edytowany przez uzytkownikubunt (2016-12-01 00:48:20)
Offline
Release za tydzień.
Ciekawe co nowego będzie podane w announce dla 5.5 . Co nowego dodali...
Offline
605
Ostatnio edytowany przez uzytkownikubunt (2016-12-01 00:48:25)
Offline
A ja wczoraj chciałem sobie aktualizować opena do 5.5. Podchodziłem kilka razy i za każdym razem dziwiłem się czemu tam ciągle wyskakiwało -current. W końcu się obudziłem,że opena 5.5 wydają dopiero 1 maja, a nie pierwszego kwietnia.
Cóż za prima aprilisowy żart ]:>
Offline
Time (s) | Query |
---|---|
0.00010 | SET CHARSET latin2 |
0.00004 | SET NAMES latin2 |
0.00102 | SELECT u.*, g.*, o.logged FROM punbb_users AS u INNER JOIN punbb_groups AS g ON u.group_id=g.g_id LEFT JOIN punbb_online AS o ON o.ident='18.118.33.98' WHERE u.id=1 |
0.00130 | UPDATE punbb_online SET logged=1733999221 WHERE ident='18.118.33.98' |
0.00051 | SELECT * FROM punbb_online WHERE logged<1733998921 |
0.00050 | SELECT topic_id FROM punbb_posts WHERE id=260945 |
0.00010 | SELECT id FROM punbb_posts WHERE topic_id=20635 ORDER BY posted |
0.00061 | SELECT t.subject, t.closed, t.num_replies, t.sticky, f.id AS forum_id, f.forum_name, f.moderators, fp.post_replies, 0 FROM punbb_topics AS t INNER JOIN punbb_forums AS f ON f.id=t.forum_id LEFT JOIN punbb_forum_perms AS fp ON (fp.forum_id=f.id AND fp.group_id=3) WHERE (fp.read_forum IS NULL OR fp.read_forum=1) AND t.id=20635 AND t.moved_to IS NULL |
0.00006 | SELECT search_for, replace_with FROM punbb_censoring |
0.02563 | SELECT u.email, u.title, u.url, u.location, u.use_avatar, u.signature, u.email_setting, u.num_posts, u.registered, u.admin_note, p.id, p.poster AS username, p.poster_id, p.poster_ip, p.poster_email, p.message, p.hide_smilies, p.posted, p.edited, p.edited_by, g.g_id, g.g_user_title, o.user_id AS is_online FROM punbb_posts AS p INNER JOIN punbb_users AS u ON u.id=p.poster_id INNER JOIN punbb_groups AS g ON g.g_id=u.group_id LEFT JOIN punbb_online AS o ON (o.user_id=u.id AND o.user_id!=1 AND o.idle=0) WHERE p.topic_id=20635 ORDER BY p.id LIMIT 150,25 |
0.00178 | UPDATE punbb_topics SET num_views=num_views+1 WHERE id=20635 |
Total query time: 0.03165 s |