hi! upgrade of mutt of sid made my mh system broken sound on optiplex gx190 is a bit weird(somewhat detuned higher) on sid and jaunty so was going to give up and reinstall intrepid then mbr got broken .. and had to do "o" in fdisk and do everythang all over again.. am beginnin to love live thangs anyway
>> the setup script is on that 1st vfat volume >> and from puppy-linux and oilinux(my customized deb-live) > > Just out of curiosity, what did you add/change in your custom deb-live > that you think could be useful in p:d? mine is just a newbie-testing-lh.iso and it's just debian with nothing added to sources.list it acutualy is a result of: lh_config -a i386 --categories "main contrib non-free" --packages "console-setup dvtm xine-console ecasound caca-utils ghc openjdk-6-jdk alsa-utils vim-nox htop mpg321 yatm vorbis-tools festival ncftp fetchmail procmail msmtp mutt podracer python csound sox faad python-pygame python-csound python-csoundac python-twitter jackd chuck" lh_build i acutually want youtube-dl and rubberband-cli too but adding -d sid always fails .. so yes it's lenny wanted to try if i could go simple i usually use x only for iceweasle,audacity,avidemux,(wanna go kluppe someday) and am not that realtime oriented so i'll be happy if python(maybe 3 is too early yet) and csound and lame works on p:d (on almost any kind of machines) oh so .. if am using p:d for updating the episode of my podcast i definately want ncftp or sshfs installed as default recently i found that we can directly algo-comp a .wav file with standard library of python so i think i will gradually move from music apps to general scripting languages people are talking abount haskell a lot now and i agree that hs is something when it comes to algo-dsp but setting up a system is a big pain for non dev-er(like me)..scvim used to be like that (and deb also seem to lack lots of things related to hs) SO if ghc, hsc3, hsndfile .. could be there in p:d .. maybe this distro would be the one and only distro that will have them ready to go? my friend built a way to do something like hsvim http://renick-bell.blogspot.com/2009/05/workaround-for-sendtorepl-and-ghci.html i think this will make lots of vim-live-coders happy but .. ghc might make the distro so phat..? then plz consider an another one named p:h oh and if booting the sys as cui 1st makes the process fast it'll be nice for ppl using netbooks on train am personally beginning to think that just running a script after a plain boot of any live distro to make the system yours (and keep that script in a top dir of ones usb-flash) makes thing simpler than making a persistent volume you can fix the script without booting the system and the script can survive forever even if the distro.iso get freaquently upgraded btw: when the live-rw volume on optilex's internal hdd was there i found that bootin from other dev-live seems to also activate it (that p:d-logo-cui comes up) maybe that's the default of lh_config (cuz i put nothing related to that) > (btw, this summer we will be working on some simple script that permit > to easily customize/remix pure:dyne) p:d is gettin better and better! >> and yes if i do ./setup after sudo su >> it says that there's no such command > > which filesystem is used? > is the partition mounted as rw? (type mount to check) this is on intrepid but: the /dev/sdb1 is vfat(rw) ~# mount /dev/sda2 on / type ext3 (rw,relatime,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) /proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) varrun on /var/run type tmpfs (rw,nosuid,mode=0755) varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) fusectl on /sys/fs/fuse/connections type fusectl (rw) lrm on /lib/modules/2.6.27-14-generic/volatile type tmpfs (rw,mode=755) securityfs on /sys/kernel/security type securityfs (rw) /dev/sdb1 on /root/padanida type vfat (rw) > did you check the file is what you think it is? (type file "filename" to > check) now it's renamed to "fire" but: fire: POSIX shell script text executable so .. well it seems to be what i thought i was doing ;) and it also does the job on puppy and debian-live(lenny based) > PS: about your certificate problem, just install the 2009 version of the > debian keyring package to get rid of the warning. thanx! -- SaRiGaMa's Oil Vending Orchestra is podcasting: http://sarigama.namaste.jp/podcast/rss.xml and supplying oil.py for free: http://oilpy.blogspot.com/ --- [email protected] irc.goto10.org #pure:dyne
