IRC Logs

Network: freenode Channel: #netbsd

	Enter your search terms Submit search form
	Web www.irclog.org

[00:02]<yjg_2ymjg>hello, I am new to netbsd, by default I have no package manager ?
[00:02]<yjg_2ymjg>because pkgsrc is not installed by default
[00:03]<vl77>ion_bidon: sure, man pkg_add and so on. Set your PKG_PATH to some NetBSD packages site. If you want to build packages from source too, install pkgsrc (I believe you'll find it on your NetBSD CD).
[00:03]<yjg_2ymjg>tp76: thanks, I was searching for pkgsrc
[00:04]<yjg_2ymjg>I have read the manual and it says that I can also install binary packages with pkgsrc. What do you suggest if I want to make a package for netbsd ?
[00:05]<vl77>ion_bidon: you want to make a binary package from your own sources?
[00:05]<yjg_2ymjg>tp76: yes, to distribute a package, I prefer binary package, rather than "source packages"
[00:06]<vl77>ion_bidon: have a look at pkg_create. Never done this myself in NetBSD so I don't know the details, sorry.
[00:06]<slwnw>swishy: okay
[00:06]<yjg_2ymjg>tp76: ok no problem :) thanks
[00:06]<swdsxd>sphex: and im refering to the *enterprise* versions ....
[00:07]<yjg_2ymjg>it's weird that I hadn't saw pkg_* on the documentation
[00:07]<yjg_2ymjg>I must have missed a chapter
[00:07]<slwnw>phadthai: might be a reason why they picked suse for the compat layer in pkgsrc? so that there's a lot of stuff included...
[00:08]<yjg_2ymjg>tp76: any idea if the pkg_* have something in common with those from openbsd ?
[00:08]<slwnw>swishy: all their versions gotta be pretty much the same anyway...
[00:09]<swdsxd>sphex: indeed
[00:09]<slwnw>ion_bidon: well openbsd's ports and pkgsrc, and their pkg_* tools overall work pretty similarly, somewhat. but IIRC, openbsd rewrote their pkg_* in Perl.
[00:10]<yjg_2ymjg>sphex: thanks for the info
[00:11]<yjg_2ymjg>o, so the pkg_* are in the pkgsrc guide
[00:12]<yjg_2ymjg>now I understand, I thought there were 2 different things
[00:14]<lxrmvxry>sphex: very probable
[00:15]<slwnw>ion_bidon: well, pkgsrc uses the pkg_* tools to manage the installations (and the whole installed packages DB stuff). in pkgsrc there's a framework in place that could allow pkgsrc to use other tools to do that, like say, RPM, or whatever the OS uses natively. but there's only code for pkg_* currently.
[00:15]<slwnw>... and that's what netbsd uses natively
[00:16]<yjg_2ymjg>sphex: cool, pkg_* are cool :)
[00:16]<slwnw>ayup
[00:19]<dzrajgyaus>Howdy.
[00:19]<yjg_2ymjg>netbsd pkg_* are written in what language ?
[00:19]<dzrajgyaus>Will netbsd work well on a Mac Classic? Also, is there any point putting it on a floppy-only machine with no internet connection? :P
[00:20]<slwnw>Draconicus: a netbsd computer without networking is a very, very sad computer. :(
[00:20]<slwnw>ion_bidon: C
[00:20]<dzrajgyaus>:(
[00:20]<yjg_2ymjg>sphex: o that's nice
[00:21]<dzrajgyaus>I'll have to find a network interface compatible with the mac classic, then.
[00:21]<yjg_2ymjg>I guess that's mainly for portability issues
[00:21]<yjg_2ymjg>and speed
[00:24]<slwnw>ion_bidon: yeah.. everything in the base system is either C, sh or awk, using only commands from the base system. there are some talks of importing some other scripting languages in the base, but I'd be surprised if there could ever be a consensus over which one.
[00:25]<dyfjsg>ofcourse python
[00:25]<dyfjsg>:)
[00:25]<yjg_2ymjg>sphex: yes, I think its quite enough C and sh. I like perl but it's quite slow
[00:26]<vl77>... and pretty ugly, too. But at least it's not as slow as Python.
[00:26]<lxrmvxry>most scripting languages would end up into gnu and add unnecessary base system bloat I think
[00:27]<slwnw>ion_bidon: problem with perl is mostly a portability thing. the build system is pretty complex... and I don't think it would still work on VAX and whatnot...
[00:27]<lxrmvxry>common and widely known ones at least
[00:27]<yjg_2ymjg>sphex: the build system is complex ? :O
[00:27]<yjg_2ymjg>I had no idea
[00:28]<dzrajgyaus>Would it be dificult to establish an ethernet over SCSI connection?
[00:29]<dzrajgyaus>Under netbsd, I mean.
[00:29]<dzrajgyaus>Regardless of that, do you think the classic will boot a netBSD installation floppy?
[00:30]<slwnw>Draconicus: does a mac classic usually can run UNIX-like systems?
[00:30]<dzrajgyaus>I'm pretty sure no Mac Classic has seen anything beyond the original Darwin kernels.
[00:30]<swdsxd>Draconicus: are the classics still m68k ?
[00:30]<dzrajgyaus>They are.
[00:30]<swdsxd>should do
[00:30]<swdsxd>just use the correct port
[00:30]<swdsxd>:)
[00:30]<slwnw>so that thing has an MMU?
[00:31]<vjymrrsv>Draconicus: There's no support for that, but if you have the hardware I think it could be hacked over a weeked.
[00:31]<lxrmvxry>Draconicus: hmm if there was an interface/device for genreal purpose parallel i/o over scsi adaptors, then I guess that plip could be used to provide network connectivity over scsi heh
[00:31]<swdsxd>phadthai: hehe
[00:31]<lxrmvxry>might need a new pseudo-device to be written though
[00:31]<dzrajgyaus>Aww. I was hoping it'd be fairly easy.
[00:32]<vjymrrsv>though there's no point now that there is gigabit ethernet
[00:32]<lxrmvxry>over paralel you could use plip right away I think
[00:32]<swdsxd>oh wait , what does the classic use bios wise ?
[00:32]<vjymrrsv>and 10g ethernet
[00:32]<lxrmvxry>or ppp or slip over rs232 serial port
[00:33]<dyfjsg>voidcast: i read some place that net over firewire actualy performs better than gig ethernet
[00:33]<zazmagaal>someone said that to me today, too
[00:33]<lxrmvxry>voidcast: probably unavailable on a mac classic however :)
[00:34]<dyfjsg>something to do with latency(?)
[00:34]<vjymrrsv>then that's a nic or driver issue
[00:34]<lxrmvxry>10mbit ethernet is available if one gets an old nubus one though
[00:34]<swdsxd>the protocol overhead via FW would be larger to start with
[00:35]<dyfjsg>i think it was article about setting up standalone postgres server
[00:36]<dyfjsg>where aplication pulls data over ethernet
[00:36]<dzrajgyaus>swishy: I'm not sure what the BIOS/Firmware is on the Classic.
[00:36]<dyfjsg>fw ethernet performed better ... anyway its l00nix test environment :)
[00:37]<zjvvyrrm>milosn, doesn't fw suffer the "cable's too long" syndrome?
[00:38]<dzrajgyaus>Hmm... It doesn't have a hard drive. It seems to boot from some kind of ROM, unless I have the more expensive model. I'll have to take it apart and find out. I'm off to tinker for a bit.
[00:39]<dyfjsg>rottingd: guess not in their setup ... colo, 1 app server + 1 db server
[00:40]<dyfjsg>whats cable length there 5cm :)?
[00:40]<zjvvyrrm>yeah :D
[00:45]<zjvvyrrm>nite :)
[00:45]<dyfjsg>well nite
[00:45]<dyfjsg>is young!
[00:46]<zjvvyrrm>not if you've got to be slightly productive in the morning ;)
[00:46]<dyfjsg>true
[00:47]<yjg_2ymjg>warning, package emacs-... was built for a different version of the 0S : ..3.0 vs. 3.0.1
[00:47]<yjg_2ymjg>do I have to panic ?
[00:47]<swdsxd>nope
[00:47]<dyfjsg>nope
[00:47]<dyfjsg>hmmm
[00:48]<yjg_2ymjg>ok thanks
[00:48]<dyfjsg>swishy ...
[00:48]<dyfjsg>stop stealing my lines
[00:48]<swdsxd>milosn: haha
[00:48]<dyfjsg>:)
[00:48]<swdsxd>:)
[00:49]<dzrajgyaus>Hmm..

Back to #netbsd
Or go to some related logs:
#suse
#gentoo
#gentoo
#ubuntu
#blender