Slack速度性能都佳，archer们换不？
vbox文件被移到sun的下载中心去了，没找到，就没装得上。
[贴图] Slack + Flux
-
aBiNg
- 帖子： 1331
- 注册时间： 2006-07-09 12:22
- 来自： 南京
[贴图] Slack + Flux
搞了一天，差不多可以凑合着用了。
Slack速度性能都佳，archer们换不？
vbox文件被移到sun的下载中心去了，没找到，就没装得上。
Slack速度性能都佳，archer们换不？
vbox文件被移到sun的下载中心去了，没找到，就没装得上。
- 附件
-
- Slack + Fluxbox
-
zhuqin_83
- 帖子： 10606
- 注册时间： 2006-05-13 4:02
- 联系：
Arch vs Slackware
Slackware and Arch are quite similar in that both are simple distributions focused on elegance and minimalism. Both use BSD-style init scripts. Arch supplies a package management system in pacman which, unlike Slackware's standard tools, offers automatic dependency resolution and allows for easy system upgrades. Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them. Arch is a rolling-release system. Slackware is seen as more conservative in its release cycle, preferring proven stable packages. Arch is more 'bleeding edge' in this respect. Arch is i686 and x86_64 whereas Slackware can run on i486 systems. Both have a ports-like system available in addition to their regular package managers- the (unofficial) Slackbuild system is very similar to the Arch Build System (ABS), the latter being slightly more automated. Arch is a very good system for Slack users who want package management with automatic dependency resolution and/or more current packages.
Slackware and Arch are quite similar in that both are simple distributions focused on elegance and minimalism. Both use BSD-style init scripts. Arch supplies a package management system in pacman which, unlike Slackware's standard tools, offers automatic dependency resolution and allows for easy system upgrades. Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them. Arch is a rolling-release system. Slackware is seen as more conservative in its release cycle, preferring proven stable packages. Arch is more 'bleeding edge' in this respect. Arch is i686 and x86_64 whereas Slackware can run on i486 systems. Both have a ports-like system available in addition to their regular package managers- the (unofficial) Slackbuild system is very similar to the Arch Build System (ABS), the latter being slightly more automated. Arch is a very good system for Slack users who want package management with automatic dependency resolution and/or more current packages.
HP Pavilion DV6-2064CA: AMD Turion II Ultra Dual-Core Mobile M640, HD4650, 2GBx2 DDR2-800, Seagate 500GB 7200RPM SATA, BD-ROM
DELL UltraSharp 2209WA
Arch64, Testing repo
DELL UltraSharp 2209WA
Arch64, Testing repo
-
zhuqin_83
- 帖子： 10606
- 注册时间： 2006-05-13 4:02
- 联系：
-
aBiNg
- 帖子： 1331
- 注册时间： 2006-07-09 12:22
- 来自： 南京
zhuqin_83
同一个wm下，速度上猪亲兄先别忙着吹你的arch，那应该是个客观存在，不必多言，哈哈。
嗯，Slack依赖关系是要用户自己解决，但让很多人不解的是，Slack依赖的问题事实上大多数情况下并不存在；编译安装时，Slack并不像人们想像中那样缺包严重。我所使用的大多数常用软件，是编译安装的，自我感觉要比ubuntu下顺畅很多。
至于倒退了还是进步了，并非一时能看得出，倘若猪亲兄一眼能看穿，我也无话可说了，哈哈。作为最古老的distro，Slack的桌面用户确实在减少，但不至于就是一种倒退。
我想借ubuntu-cn这地儿，表达一下我的两个微不足道的观点：一是历史从来就不具有倒退的属性；二是用户确确实实不是上帝。:D
eexpress
tray是Flux自带的。
xiooli
你的意思是批评我的桌面不漂亮啊，努力奋力ing...
rhfcaesar
承诺的enligtenment for Flux的主题呢？:D
同一个wm下，速度上猪亲兄先别忙着吹你的arch，那应该是个客观存在，不必多言，哈哈。
嗯，Slack依赖关系是要用户自己解决，但让很多人不解的是，Slack依赖的问题事实上大多数情况下并不存在；编译安装时，Slack并不像人们想像中那样缺包严重。我所使用的大多数常用软件，是编译安装的，自我感觉要比ubuntu下顺畅很多。
至于倒退了还是进步了，并非一时能看得出，倘若猪亲兄一眼能看穿，我也无话可说了，哈哈。作为最古老的distro，Slack的桌面用户确实在减少，但不至于就是一种倒退。
我想借ubuntu-cn这地儿，表达一下我的两个微不足道的观点：一是历史从来就不具有倒退的属性；二是用户确确实实不是上帝。:D
eexpress
tray是Flux自带的。
xiooli
你的意思是批评我的桌面不漂亮啊，努力奋力ing...
rhfcaesar
承诺的enligtenment for Flux的主题呢？:D
-
lovewine
- 帖子： 1233
- 注册时间： 2006-03-25 10:36
- 联系：
-
dyj057
- 帖子： 114
- 注册时间： 2007-10-20 14:15
